11-01-2016 06:30 AM - edited 03-01-2019 12:57 PM
For every Out-of-band IP assigned, The switch is having ARP overwrite issues. The MAC addresses for the out-of-band ips switch between the MAC of the management port of FI-A and the MAC of the management port of FI-B.
These FIs are being hosted of a Juniper network. Any ideas?
Solved! Go to Solution.
11-02-2016 08:30 AM
Greetings.
Are you saying this is a constant, ongoing flapping? There are some circumstances under which a blade's CIMC 'managing Instance' may get changed to the other FI, but this should be rare, and not a repeating event.
For the blades, who's OOB IP appears to be flapping, does the 'managing instance' change ? (Equipment view, Server, General Tab, CIMC connection Details towards bottom of right pane)
For each FI run the following:
#connect local-mgmt (A|B)
#show mgmt-ip-debug ifconfig
check to see if your offending macs are listed in both sets of output. If they are, try changing the cluster lead after confirming your cluster state is healthy:
(local-mgmt#show cluster extended-state
....make sure no errors on either FI
From Cluster that is the primary, issue the cluster lead change:
(local-mgmt#cluster lead b (assuming A is currently the primary)
You'll get kicked out of putty/ssh, if connected to the VIP address, and the GUI as well, and will need to log back in.
Recheck your mgmt-ip-debug ifconfig output, and see if both still have the duplicate entries.
If you do list duplicate entries still, I would open a TAC case.
Kirk...
11-02-2016 08:30 AM
Greetings.
Are you saying this is a constant, ongoing flapping? There are some circumstances under which a blade's CIMC 'managing Instance' may get changed to the other FI, but this should be rare, and not a repeating event.
For the blades, who's OOB IP appears to be flapping, does the 'managing instance' change ? (Equipment view, Server, General Tab, CIMC connection Details towards bottom of right pane)
For each FI run the following:
#connect local-mgmt (A|B)
#show mgmt-ip-debug ifconfig
check to see if your offending macs are listed in both sets of output. If they are, try changing the cluster lead after confirming your cluster state is healthy:
(local-mgmt#show cluster extended-state
....make sure no errors on either FI
From Cluster that is the primary, issue the cluster lead change:
(local-mgmt#cluster lead b (assuming A is currently the primary)
You'll get kicked out of putty/ssh, if connected to the VIP address, and the GUI as well, and will need to log back in.
Recheck your mgmt-ip-debug ifconfig output, and see if both still have the duplicate entries.
If you do list duplicate entries still, I would open a TAC case.
Kirk...
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: