Skip to main content

Upgrading or downgrading the firmware on a Brocade FC switch

To upgrade or downgrade the firmware on a Brocade FC switch, you must use the Brocade-specific commands to disable the switch, perform and verify the firmware change, and reboot and reenable the switch.

Before you begin

  • You must have the firmware files.

  • The system must be properly cabled.

  • All paths to the storage shelves must be available.

  • The disk shelf stacks must be stable.

  • The FC switch fabric must be healthy.

  • No failed components can be present in the system.

  • The system must be operating normally.

  • You must have the admin password and access to an FTP or SCP server.

About this task

The switch fabric is disabled during a firmware upgrade or downgrade, and the MetroCluster configuration relies on the second fabric to continue operation.

This task must be performed on each of the switch fabrics in succession so that all switches are running the same firmware version.

Note
This procedure is nondisruptive and takes approximately one hour to complete.
  1. Log in to each of the switches in the fabric.

    The examples in the following steps use the switch FC_switch_A_1.
  2. Disable each of the switches in the fabric: switchCfgPersistentDisable

    If this command is not available, then run the switchDisable command.

    Example

    FC_switch_A_1:admin> switchCfgPersistentDisable
  3. Download the desired firmware version: firmwareDownload

    When prompted for the file name, you must specify the subdirectory or relative path to the firmware file.

    You can run the firmwareDownload command at the same time on both switches, but you must allow the firmware to download and commit properly before moving to the next step.

    Example

    FC_switch_A_1:admin> firmwaredownload
    Server Name or IP Address: 10.64.203.188 
    User Name: test 
    File Name: v7.3.1b 
    Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]: 2
    Password:
    Server IP: 10.64.203.188, Protocol IPv4 
    Checking system settings for firmwaredownload...
    System settings check passed.

  4. Verify that the firmware was downloaded and committed to both partitions: firmwareShow

    Example

    The following example shows that the firmware download is complete as both images are updated:
    FC_switch_A_1:admin> firmwareShow
    Appl     Primary/Secondary Versions

    ------------------------------------------

    FOS      v7.3.1b

             v7.3.1b

  5. Reboot the switches: reboot

    Some firmware versions automatically perform an haReboot operation after the firmware download is finished. The reboot in this step is required even if the haReboot has been performed.

    Example

    FC_switch_A_1:admin> reboot
  6. Check whether the new firmware is for an intermediate firmware level or for a final specified release.

    If the download is for the intermediate firmware level, then perform the previous two steps until the specified release is installed.
  7. Enable the switches: switchCfgPersistentEnable

    If this command is not available, then the switch should be in the enabled state after the reboot command is executed.

    Example

    FC_switch_A_1:admin> switchCfgPersistentEnable
  8. Verify that the switches are online and that all of the devices are properly logged in: switchShow

    Example

    FC_switch_A_1:admin> switchShow
  9. Verify that the buffer usage information for a port group or all of the port groups in the switch is displayed properly: portbuffershow

    Example

    FC_switch_A_1:admin> portbuffershow
  10. Verify that the current configuration of a port is displayed properly: portcfgshow

    Example

    FC_switch_A_1:admin> portcfgshow

    Verify the port settings, such as speed, mode, trunking, encryption, and compression, in the Inter-Switch Link (ISL) output. Verify that the port settings were not affected by the firmware download.
  11. Verify the operation of the MetroCluster configuration in ONTAP:
    1. Check whether the system is multipathed: node run -node node-name sysconfig -a
    2. Check for any health alerts on both clusters: system health alert show
    3. Confirm the MetroCluster configuration and that the operational mode is normal: metrocluster show
    4. Perform a MetroCluster check: metrocluster check run
    5. Display the results of the MetroCluster check:metrocluster check show
    6. Check for any health alerts on the switches (if present): storage switch show
  12. Repeat this procedure for the second switch fabric.