
OPERATIONAL DEFECT DATABASE
...

...
Code upgrade The Standby CP is in a faulty state after a firmware upgrade from 7.2.1c1 to 7.3.1. After reseating the standby CP, it becomes enabled, but the CPs are running different codes. The Standby CP upgrade does not start and gives an error message "Sanity check failed because firmwareDownload is already in progress" as seen below: [EM-1033], 3605, SLOT 7 | CHASSIS,, CP in Slot 6 set to faulty because CP ERROR asserted.[SULB-1011], 3649, SLOT 7 | CHASSIS, INFO,Firmwaredownload command failed. Active and Standby CPs failed to gain HA synchronization within 10 minutes. Firmwaredownload is aborted..[EM-1033], 4226, SLOT 7 | CHASSIS, ERROR, CP in Slot 6 set to faulty because CP ERROR asserted.firmwareshowSlot Name Appl Primary/Secondary Versions Status-------------------------------------------------------------------------- 6 CP0 FOS v7.2.1c1 STANDBY v7.2.1c1 7 CP1 FOS v7.3.1 ACTIVE * v7.3.1* Local CPWARNING: The local CP and remote CP have different versions f firmware, please retry firmwaredownload command.slotshowSlot Blade Type ID Status 6 CP BLADE 50 FAULTY (53) - possible RRD 7 CP BLADE 50 ENABLEDWARNING: The local CP and remote CP have different versions of firmware, please retry firmwaredownload command.*****************************************************************Logging into STANDBY CP, not all commands are fully supported !!*****************************************************************firmwaredownload -sServer Name or IP Address: X.X.X.XUser Name: anonymousFile Name: v7.3.1Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]:Password:Do Auto-Commit after Reboot [Y]:Reboot system after download [N]:Server IP: x.x.x.x, Protocol IPv4Checking system settings for firmwaredownload...Sanity check failed because firmwareDownload is already in progress.
The firmwaredownload command process stops responding after the Standby CP is reseated.
Log in to the standby CP and run the firmwarecommit command on the Standby CP.Check if you can start the upgrade on the Standby CP using the firmwaredownload -s command.If the Standby CP is good, wait until it finishes and check the status after the upgrade finishes by using the firmwareshow command.Confirm both CPs are on the same version. If the issue still exists, try to do the following: Run the hashow command. Check that the HA is enabled, the Heartbeat is Up, and the HA State is synchronized and that they are ok.Run the hafailover command. Wait 10 minutes.Run the hashow command. Check that the HA is enabled, the Heartbeat is Up, and the HA State is synchronized.Run the hafailover command so the switch is in the same position.Run the hashow command. Check that the HA is enabled, the Heartbeat is Up, and the HA State is synchronized.Log in to the standby CP and upgrade with firmwaredownload -s command. If the issue still exists, contact your Dell Customer Service representative or the Dell Customer Support Center for technical support. Upload the switch logs to the service request, so that support staff can check them and provide feedback. Quote this solution ID.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.