Hello Experts,
I have noticed the the management SSH access is flapping between primary and secondary node every minutes.
{primary:node0} root@FW-01> Write failed: Broken pipe [user@sys ~]$ ssh root@10.10.10.10.10 Password: --- JUNOS 15.1X49-D60.7 built 2016-09-13 23:16:14 UTC root@FW-01% cli {secondary:node1} root@FW-01>
I am wondering why this is happening.
root@FW-01> show chassis cluster status Monitor Failure codes: CS Cold Sync monitoring FL Fabric Connection monitoring GR GRES monitoring HW Hardware monitoring IF Interface monitoring IP IP monitoring LB Loopback monitoring MB Mbuf monitoring NH Nexthop monitoring NP NPC monitoring SP SPU monitoring SM Schedule monitoring CF Config Sync monitoring Cluster ID: 1 Node Priority Status Preempt Manual Monitor-failures Redundancy group: 0 , Failover count: 2 node0 255 primary no yes None node1 1 secondary no yes None Redundancy group: 1 , Failover count: 1 node0 0 secondary yes no IF node1 0 primary yes no IF Redundancy group: 2 , Failover count: 0 node0 254 primary yes no None node1 1 secondary yes no None Redundancy group: 3 , Failover count: 0 node0 254 primary yes no None node1 1 secondary yes no None {secondary:node1} root@FW-01>
Is there any chance its related to this error?
Apr 29 14:06:40 FW-01 /kernel: KERN_ARP_DUPLICATE_ADDR: duplicate IP address 10.10.10.10! sent from address: 44:f4:77:41:5d:1a (error count = 380) Apr 29 14:29:10 FW-01 /kernel: KERN_ARP_DUPLICATE_ADDR: duplicate IP address 10.10.10.10! sent from address: 44:f4:77:41:5d:1a (error count = 381) Apr 29 14:44:38 FW-01 /kernel: KERN_ARP_DUPLICATE_ADDR: duplicate IP address 10.10.10.10! sent from address: 44:f4:77:41:5d:1a (error count = 382)
How can I avoid both primary and secondary claiming this address?