Unable to add Brocade switch to SANnav
Applies to
- Brocade X6
- Brocade switch FOS 8.2.x
- SANnav 2.2.1
Issue
- While adding Brocade switch to SANnav with enterprise license, below error observed on SANnav server
[root@xxxsannavxxx ~]$ curl -k http: //10.70.xxx.xx
<HTML> <HEAD><TITLE>Status: 503 Chassis not ready for management</TITLE></HEAD><BODY BCOLOR="#c0c0c0"> <P> <H1>Chassis is not ready for management now. <BR>Please try after some time.</H1></P></BODY></HTML>
- IPv4 is used on the switches
- Verify if HA is in sync using command
hashowon the switch as shown below:
Local CP (Slot 2, CP1): Active, Cold Recovered
Remote CP (Slot 1, CP0): Standby, Healthy
HA enabled, Heartbeat Up, HA State not in sync
- If HA is not in sync, try to reboot\reseat the CP using below procedure
- Login directly to standby CP and execute the “
reboot” command to reboot the Standby CP - On the Active CP, wait for about 5 to 10 minutes and then execute “
slotshow” and “hashow” command a few time to check if the CP0 is back online and also if the HA state is now in sync - If the HA state is not in sync then execute “
hasyncstart” command on the Active CP (CP1) and execute the “hashow” command a few time to find out if the HA is able to sync - If the HA state is still unable to sync then schedule a maintenance window to reboot or power cycle the Brocade switch to restart all the switch daemons
- Login directly to standby CP and execute the “
- In the above procedure if the 1st step didnt work i.e., reboot of standby CP is unsuccessful then reseat\replace the standby CP
Logging into STANDBY CP, not all commands are fully supported !!
*****************************************************************
POL_X6_A_Default:FID128:admin> hashow
fabos not yet initialized: -1
- If reseat\replace of standby CP also didnt work then proceed with the solution