Brocade Communications Systems 53-1001763-02 Administrator's Manual page 245

Testing different firmware versions on enterprise-class platforms
1. Connect to the Brocade enterprise-class platform IP address.
2. Enter the ipAddrShow command and note the address of CP0 and CP1.
3. Enter the haShow command and note which CP is active and which CP is standby. Verify that
4. Enter the firmwareShow command and confirm that the current firmware on both partitions on
5. Exit the session.
6. Update the firmware on the standby CP.
7.
CAUTION
If you are downgrading from Fabric OS v6.2.0 to v6.1.0, your CPs will not gain synchronization
and this will be a disruptive firmware download. Refer to
information on synchronization states.
8. Verify the failover.
Fabric OS Administrator's Guide
53-1001763-02
both CPs are in sync.
both CPs is listed as expected.
a. Connect to the enterprise-class platform and log in as admin to the standby CP.
b. Enter the firmwareDownload -s command and respond to the prompts.
At this point, the firmware should download to the standby CP only. When it has completed
the download to that CP, reboot it. The current enterprise-class platform session will be
disconnected.
Fail over to the standby CP.
a. Connect to the enterprise-class platform on the active CP.
b. Enter the haShow command to verify that HA synchronization is complete. It will take a
minute or two for the standby CP to reboot and synchronize with the active CP.
c. Enter the firmwareShow command to confirm that the primary partition of the standby CP
contains the new firmware.
d. Enter the haFailover command. The active CP will reboot and the current enterprise-class
platform session will be disconnected.
If an AP blade is present: At the point of the failover an autoleveling process is activated.
See, "Enterprise-class platform firmware download process overview"
details about autoleveling.
a. Connect to the enterprise-class platform on the active CP, which is the former standby CP.
b. Enter the haShow command to verify that the HA synchronization is complete. It will take a
minute or two for the standby CP, which is the old active CP, to reboot and synchronize with
the active CP.
NOTE
If the CPs fail to synchronize, you can still proceed because the version being tested is already
present on the active CP, and subsequent steps will ensure that the standby CP is updated to
the same version as the active CP.
Test and restore firmware on enterprise-class platforms
Table 44 on page 191 for more
on page 196 for
9
205