Dell Brocade 5100 Brocade 7.4.0 Fabric OS Software Upgrade Guide - Page 30

Firmware Download Scenarios 1. Verify that the Ethernet interfaces located on CP0 and CP1 are plugged into your network. If the switch has a BP, verify that the BP console is accessible. 2. Verify that the FTP, SFTP, or SSH server is running on the host server and that you have a user ID on that server. 3. Obtain the firmware file from the Brocade website at http://www.brocade.com and store the file on the FTP or SSH server. 4. Unpack the compressed files preserving directory structures. The firmware is in the form of RPM packages with names defined in a .plist file. The .plist file contains specific firmware information and the names of packages of the firmware to be downloaded. 5. Connect to the chassis IP management interface or active CP and log in using an account with admin permissions. 6. Use the firmwareShow command to check the current firmware version on connected switches. Upgrade the firmware, if necessary, before proceeding with upgrading this switch. Refer to Connected switches on page 26. 7. Enter the haShow command to confirm that the two CP blades are synchronized. In the following example, the active CP blade is CP0 and the standby CP blade is CP1: ecp:admin> hashow Local CP (Slot 5, CP0): Active, Warm Recovered Remote CP (Slot 6, CP1): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized CP blades must be synchronized and running Fabric OS v7.2.0 or later to provide a nondisruptive download. If the two CP blades are not synchronized, enter the haSyncStart command to synchronize them. If the CPs still are not synchronized, contact your switch service provider. For further troubleshooting, refer to the Fabric OS Troubleshooting and Diagnostics Guide. 8. Enter the firmwareDownload command and respond to the interactive prompts. 9. At the "Do you want to continue [y/n]" prompt, enter y. The firmware is downloaded to one CP blade at a time, beginning with the standby CP blade. During the process, the active CP blade fails over. After the firmware is downloaded, a firmware commit starts on both CP blades. The entire firmware download and commit process takes approximately 17 minutes. If an AP blade is present : At the point of the failover, an autoleveling process is activated. Autoleveling is triggered when the active CP detects a blade that contains a different version of the firmware, regardless of which version is older. Autoleveling downloads firmware to the AP blade, swaps partitions, reboots the blade, and copies the new firmware from the primary partition to the secondary partition. If you have multiple AP blades, they are updated simultaneously; however, the downloads can occur at different rates. Autoleveling takes place in parallel with the firmware download being performed on the CPs, but does not impact performance. Fibre Channel traffic is not disrupted during autoleveling, but GbE traffic on AP blades may be affected. If there is an active FCIP tunnel on the FX8-24 blade, the FCIP tunnel traffic will be impacted for at least two minutes. ecp:admin> firmwaredownload Server Name or IP Address: 10.1.2.3 User Name: userfoo File Name: /home/userfoo/v7.4.0 Network Protocol (1-auto-select, 2-FTP, 3-SCP, 4-SFTP)) [1]: Password: Checking version compatibility... Version compatibility check passed. The following AP blades are installed in the system. Slot Name Versions Traffic Disrupted 2 FS8-18 v7.4.0 Encrypted Traffic 30 Fabric OS Upgrade Guide 53-1003515-01