Problem (Highlighted in Red Color Below) in Enabling Chassis Cluster on SRX 5800

Problem (highlighted in red color below) in enabling chassis cluster on SRX 5800

Steps followed:

1. Connected the Cables for Control & Data link

2. Configured control interfaces.

On Node 0 set chassis cluster control-ports fpc 1 port 0

On Node 1 set chassis cluster control-ports fpc 1 port 0 ( Please note that I cant put fpc 13 port 0 here as it will not accept as slot 13 does not exists)

3. Now enabling chassis cluster.

On Node 0 set chassis cluster cluster-id 1 node 0 reboot

On Node 1 set chassis cluster cluster-id 1 node 1 reboot

4. After the reboot, login to Node 1

Now changing the control ports as below set chassis cluster control-ports fpc 13 port 0

After doing this control-port (link) immediately comes up. 5. Node 1 becomes the primary now

6. The Node 1 is sending Heartbeat packets but not receiving it.

primary:node1} root@SRX-5800I-FW2> show chassis cluster control-plane statistics Control link statistics: Control link 0: Heartbeat packets sent: 103 Heartbeat packets received: 0 Heartbeat packet errors: 0 Control link 1: Heartbeat packets sent: 0 Heartbeat packets received: 0 Heartbeat packet errors: 0 Fabric link statistics: Probes sent: 102 Probes received: 0 Probe errors: 0

{primary:node1} root@SRX-5800-FW2> show chassis cluster control-plane statistics Control link statistics: Control link 0: Heartbeat packets sent: 105 Heartbeat packets received: 0 Heartbeat packet errors: 0 Control link 1: Heartbeat packets sent: 0 Heartbeat packets received: 0 Heartbeat packet errors: 0 Fabric link statistics: Probes sent: 104 Probes received: 0 Probe errors: 0

7. Problem is that on Node 0, SPC in slot 1, it shows amber light on it however the port 0 on this SPC shows active (green color). Grey color shows that interface is up.

{hold:node0} root@SRX-5800-FW1> show interfaces terse Interface Admin Link Proto Local Remote dsc up up em0 up up em0.0 up up inet 129.16.0.1/2 tnp 0x1100004 em1 up up em1.0 up up inet 129.16.0.1/2 tnp 0x1100004 fxp0 up down fxp0.0 up down inet 10.155.4.84/29 gre up up ipip up up lo0 up up lo0.0 up up inet 127.0.0.1 --> 0/0 lo0.16384 up up inet 127.0.0.1 --> 0/0 lo0.16385 up up inet lsi up up mtun up up pimd up up pime up up tap up up

{hold:node0}

Another problem is that this node goes into hold state which is the initial state upon boot in which RE is prepares to join the cluster, which never happens

8. The fabric (data) link remains down on both firewalls as the interface on PIC 11 (xe-11/0/0) on Node 0 doesn't come up.