02-01-2018 05:55 AM
I have a customer that upgraded 5 switches in 1 fabric to FOS v 8.2.0
After upgrading the fabric they see some issues
The zone configuration (Zone Config) saving aborts generating the "checksum error" and refreshes the ‘zoneconfig’ which refreshes the recently made changes. There is no hardware error on the switch and it seems to be working fine.
Customer tried to downgrade one of the switches to 8.1.2a but still facing the same issue
02-01-2018 06:57 AM
checksum mismatch error, are related to Compact Flash.
did you try to repeat a operation from a from anothe switch in the same fabric ?
If the error persist, i would suggest in any case to open a TAC with the Vendor.
02-26-2018 05:37 PM
Do all switches in the fabric observe the same error message. Be aware that this database is a distributed one which means that the management service of the switch where the change is made is responsible for making the DB entries. It then sends out a so called ACA (Aqcuire Change Authorisation) which basically means that it wants to lock the management databases on each switch in the fabric, thereafter it will send a SFC (Stage Fabric Configuration) on which it will perform the actual distribution of the change. Then a UFC (Update Fabric Configuration) is send which instructs each switch to actually apply that zone-database after which it sends a RCA (Release Change Authorisation) .
On each step the remote switches will need to send out an accept or reject based on the observations. If you receive an error which shows the checksum has failed you might want to check the ISL's and see if any of them observe issues. If a frame containing the zone-changes is being corrupted the receiving port will just chuck that away. If then an UFC comes in with a checksum of the database which to apply the recieving switch will see there is a discrepancy and will (or should) send a reject back and log an error.
There may be other issues but this is one of the most common ones.