Hi all ,
i did not find anything about how to configure HA on SRX 1500 .
Despite the numbering system, the new SRX1500 is not quite branch and not quite high end DC. These are the instructions for chassis cluster on the SRX1500; SRX550 and vSRX models.
Your help is appreciated 🙂
To configure chassis cluster for SRX 1500 you can follow the same procedure as used for the SRX 1400. There is not much difference as far as configuration is considered to have chassis cluster for SRX 1500 in comparison to SRX 1400.
On the hardware level there is a dedicated control port on SRX 1500 to be used for control link. Also it cannot be configured like on SRX 1400 as well but it needs to be connected while configuring cluster on SRX 1500.
Please mark my response as Solution Accepted if it Helps, Kudos are Appreciated too.
SRX1500 devices use dedicated control ports.
And for fabric link connection must be any pair of either Gigabit Ethernet or 10-Gigabit Ethernet interfaces on all SRX Series devices.
could you tell me if it's possible to have dual control links at the SRX1500?
SRX 1500 uses dedicated control ports and it cannot be configured and there is only one port for HA control link on SRX 1500 so dual control links is not possible on SRX 1500.
Thanks,Pulkit BhandariPlease mark my response as Solution Accepted if it Helps, Kudos are Appreciated too. 🙂
Does the HA control link for SRX 1500 have to be fiber? I am staging a pair with copper SFPs and looks like both nodes are sending heartbeats but not receiving:
root> show interfaces em0 extensivePhysical interface: em0 , Enabled, Physical link is Up Interface index: 8, SNMP ifIndex: 17, Generation: 1 Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified, Speed: 1000mbps Device flags : Present Running Interface flags: SNMP-Traps Link type : Full-Duplex Physical info : Unspecified Hold-times : Up 0 ms, Down 0 ms Current address: 02:00:00:01:01:04, Hardware address: 02:00:00:01:01:04 Alternate link address: Unspecified Last flapped : Never Statistics last cleared: Never Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 67167 Output packets: 75284 Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0, Resource errors: 0 Output errors: Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors: 0
root> show chassis cluster statisticsControl link statistics: Control link 0: Heartbeat packets sent: 3288 Heartbeat packets received: 0 Heartbeat packet errors: 0Fabric link statistics: Child link 0 Probes sent: 0 Probes received: 0 Child link 1 Probes sent: 0 Probes received: 0
root> show chassis cluster interfacesControl link status: Down
Control interfaces: Index Interface Monitored-Status Internal-SA 0 em0 Down Disabled
Fabric link status: Down
Fabric interfaces: Name Child-interface Status (Physical/Monitored) fab0 fab0
Redundant-pseudo-interface Information: Name Status Redundancy-group lo0 Up 0
root> show chassis cluster informationnode0:--------------------------------------------------------------------------Redundancy Group Information:
Redundancy Group 0 , Current State: primary, Weight: 255
Time From To Reason Jul 8 20:56:30 hold secondary Hold timer expired Jul 8 20:56:46 secondary primary Only node present
Chassis cluster LED information: Current LED color: Red Last LED change reason: Peer node: node1 is not present
Control-link Failure Information: Link Status: Monitor Failed Dual Control Link Status: Unsupported
Interface Physical / Monitored Status em0 Up / Down
Do you have the fabric link also configured and cabled?
Do you have a cross over cable on your copper port control links?