05-25-2017 01:30 AM
On a 6510 switch (FOS 7.1.0c), we performed a hareboot, to recover from "Chassis is not ready for management now" error when trying to access it via WebTools (also was unreachable for Network Advisor).
Hareboot took about 1 minute and the switch was back accessible with https, just as we wanted.
Is the "out of sync" message that the hareboot finished with something to be expected, or a reason to worry?
2017/05/25-09:27:25, [FSSM-1002], 27, CHASSIS, INFO, IBM_2498_F48, HA State is in sync.
2017/05/25-09:27:32, [FSSM-1003], 28, CHASSIS, WARNING, IBM_2498_F48, HA State out of sync.
2017/05/25-09:27:33, [RAS-1007], 29, CHASSIS, INFO, IBM_2498_F48, System is about to reboot.
2017/05/25-09:28:14, [HAM-1004], 30, CHASSIS, INFO, IBM_2498_F48, Processor rebooted - FirmwareDownload.
2017/05/25-09:28:51, [FSSM-1002], 32, CHASSIS, INFO, IBM_2498_F48, HA State is in sync.
2017/05/25-09:28:54, [FSSM-1003], 33, CHASSIS, WARNING, IBM_2498_F48, HA State out of sync.
I would think, that if it started in "HA State is in sync" state, it should also end in this state.
Solved! Go to Solution.
05-25-2017 07:55 AM
05-25-2017 10:15 PM
05-25-2017 11:51 PM
FOS v7.1.0c is a FICON Qualified Release ( however this is not a cause for the issue )
Is mandatory that you use this Release ? if not I would suggest to try a FOS upgrade to next Higher Release v7.1.1a/b/ or c
if is mandatory and you are in a FICON environments then upgrade from current v7.1.0c to-> v7.2.1d .
additional, I would suggest to start the upgrade from CLI.
If the problem persist after Upgarde, then you have to open a Call with the support.
05-26-2017 02:01 AM
05-28-2017 08:22 AM
Hi, For single CP switches we can ignore these messages.
I have done recently the FOS upgrade of Brocade 5100 and 6510 switches from v7.3.x to v7.4.1e, it shows simialr message after the switch reboot. I think these errors might throwing beacuse the FOS using for both sigle CP switch and director class switch is same, and its doing similar kind of checks for all type of switches after each reboot.
Regards / Rahul
05-29-2017 04:22 AM
I can confirm this is working as designed and can be ignored.