Skip to main content
ONTAP MetroCluster

Updating firmware on a FibreBridge bridge

Contributors netapp-aoife netapp-pcarriga netapp-aaron-holt netapp-thomi netapp-martyh netapp-cgoff netapp-folivia netapp-ranuk netapp-aherbin
PDFs

The procedure for updating the bridge firmware depends on your bridge model and ONTAP version.

About this task

Enable console logging before performing this task.

Updating firmware on FibreBridge 7600N or 7500N bridges on configurations running ONTAP 9.4 and later

You might need to update the firmware on your FibreBridge bridges to ensure that you have the latest features or to resolve possible issues. This procedure should be used for FibreBridge 7600N or 7500N bridges on configurations running ONTAP 9.4 and later.

  • The MetroCluster configuration must be operating normally.

  • All of the FibreBridge bridges in the MetroCluster configuration must be up and operating.

  • All of the storage paths must be available.

  • You need the admin password and access to an HTTP, FTP, SFTP, or Trivial File Transfer Protocol (TFTP) server.

  • You must be using a supported firmware version.

    NetApp Interoperability Matrix Tool

    In the IMT, you can use the Storage Solution field to select your MetroCluster solution. You use the Component Explorer to select the components and ONTAP version to refine your search. You can click Show Results to display the list of supported configurations that match the criteria.

  • You can use this task only on FibreBridge 7600N or 7500N bridges in configurations running ONTAP 9.4 or later.

  • You must perform this task on each FibreBridge bridge in the MetroCluster configuration, so that all of the bridges are running the same firmware version.

Note This procedure is nondisruptive and takes approximately 30 minutes to complete.
Note Beginning with ONTAP 9.8, the system bridge command replaces the storage bridge. The following steps show the system bridge command, but if you're running a version earlier than ONTAP 9.8, you should use the storage bridge command.
Steps

  1. Invoke an AutoSupport message indicating the start of the maintenance:

    system node autosupport invoke -node * -type all -message MAINT=maintenance-window-in-hours

    “maintenance-window-in-hours” specifies the length of the maintenance window, with a maximum of 72 hours. If the maintenance is completed before the time has elapsed, you can invoke an AutoSupport message indicating the end of the maintenance period:

    system node autosupport invoke -node * -type all -message MAINT=end

  2. Go to the ATTO FibreBridge page and select the appropriate firmware for your bridge.

    ATTO FibreBridge Firmware Download Page

  3. Review the Caution/MustRead and End User Agreement, and click the check box to indicate acceptance and proceed.

  4. Place the firmware file in a network location that is network accessible to the controller modules.

    You can enter the commands in the remaining steps from the console of either controller module.

  5. Change to the advanced privilege level:

    set -privilege advanced

    You must respond with “y” when prompted to continue into advanced mode and see the advanced mode prompt (*>).

  6. Update the bridge firmware.

    Beginning in ONTAP 9.16.1, you can use credentials to update the bridge firmware if they are required by the server to download the firmware package.

    If credentials are not required:

    1. Update the bridge firmware:

    system bridge firmware update -bridge <name> -uri <URL-of-firmware-package>
    Example
    cluster_A> system bridge firmware update -bridge bridge_A_1a -uri http://192.168.132.97/firmware.ZBD
    If credentials are required:

    1. Update the bridge firmware and specify the required user name:

      system bridge firmware update -bridge <name> -uri <URL-of-firmware-package> -username <name>

    2. Enter the password when prompted in the output, as shown in the following example:

    Example
    cluster_A> system bridge firmware update -bridge bridge_A_1a -uri http://192.168.132.97/firmware.ZBD -username abc

(system bridge)

Enter the password:

[Job 70] Job is queued: System bridge firmware update job.

  7. Return to the admin privilege level:

    set -privilege admin

  8. Verify that the firmware upgrade is complete:

    job show -name "<job_name>"

    The following example shows that the job “system bridge firmware update” is still running:

    cluster_A> job show -name "system bridge firmware update"
Owning

Job ID Name                 Vserver    Node           State
------ -------------------- ---------- -------------- ----------
2246   job-name
                            cluster_A
                                       node_A_1
                                                      Running
Description: System bridge firmware update job

    After approximately 10 minutes, the new firmware is fully installed and the job state will be Success:

    cluster_A> job show -name "system bridge firmware update"

                            Owning
Job ID Name                 Vserver    Node           State
------ -------------------- ---------- -------------- ----------
2246   System bridge firmware update
                            cluster_A
                                       node_A_1
                                                      Success
Description: System bridge firmware update job

  9. Complete the steps according to whether in-band management is enabled and which version of ONTAP your system is running:

    • If you are running ONTAP 9.4, in-band management is not supported and the command must be issued from the bridge console:

      1. Run the flashimages command on the console of the bridge and confirm that the correct firmware versions are displayed.

        Note The example shows that primary flash image shows the new firmware image, while the secondary flash image shows the old image. 
    flashimages

 ;Type Version
;=====================================================
Primary 3.16 001H
Secondary 3.15 002S
Ready.

    1. Reboot the bridge by running the firmwarerestart command from the bridge.

      • If you are running ONTAP 9.5 or later, in-band management is supported and the command can be issued from the cluster prompt:

    2. Run the system bridge run-cli -name <bridge_name> -command FlashImages command.

      Note The example shows that primary flash image shows the new firmware image, while the secondary flash image shows the old image. 
      cluster_A> system bridge run-cli -name ATTO_7500N_IB_1 -command FlashImages

[Job 2257]

;Type         Version
;=====================================================
Primary 3.16 001H
Secondary 3.15 002S
Ready.


[Job 2257] Job succeeded.

    3. If necessary, restart the bridge:

      system bridge run-cli -name ATTO_7500N_IB_1 -command FirmwareRestart

      Note Beginning with ATTO firmware version 2.95 the bridge will restart automatically and this step is not required.

  10. Verify that the bridge restarted correctly:

    sysconfig

    The system should be cabled for multipath high availability (both controllers have access through the bridges to the disk shelves in each stack).

    cluster_A> node run -node cluster_A-01 -command sysconfig
NetApp Release 9.6P8: Sat May 23 16:20:55 EDT 2020
System ID: 1234567890 (cluster_A-01); partner ID: 0123456789 (cluster_A-02)
System Serial Number: 200012345678 (cluster_A-01)
System Rev: A4
System Storage Configuration: Quad-Path HA

  11. Verify that the FibreBridge firmware was updated:

    system bridge show -fields fw-version,symbolic-name

    cluster_A> system bridge show -fields fw-version,symbolic-name
name fw-version symbolic-name
----------------- ----------------- -------------
ATTO_20000010affeaffe 3.10 A06X bridge_A_1a
ATTO_20000010affeffae 3.10 A06X bridge_A_1b
ATTO_20000010affeafff 3.10 A06X bridge_A_2a
ATTO_20000010affeaffa 3.10 A06X bridge_A_2b
4 entries were displayed.

  12. Verify the partitions are updated from the bridge's prompt:

    flashimages

    The primary flash image displays the new firmware image, while the secondary flash image displays the old image.

    Ready.
flashimages

;Type         Version
;=====================================================
   Primary    3.16 001H
 Secondary    3.15 002S

 Ready.

  13. Repeat steps 5 to 10 to ensure that both flash images are updated to the same version.

  14. Verify that both flash images are updated to the same version.

    flashimages

    The output should show the same version for both partitions.

    Ready.
flashimages

;Type         Version
;=====================================================
   Primary    3.16 001H
 Secondary    3.16 001H

 Ready.

  15. Repeat steps 5 to 13 on the next bridge until all of the bridges in the MetroCluster configuration have been updated.