Skip to main content

Hot-swapping a FibreBridge 7500N with a 7600N bridge

You can hot-swap a FibreBridge 7500N bridge with a 7600N bridge.

About this task

If you will be using in-band management of the bridge rather than IP management, the steps for configuring the Ethernet port and IP settings can be skipped, as noted in the relevant steps.

Note
Starting with ONTAP 9.8, the storage bridge command is replaced with system bridge. The following steps show the storage bridge command but if you are running ONTAP 9.8 or later the system bridge command is preferred.
  1. If the bridge is in a fabric-attached MetroCluster configuration, disable all of the switch ports that connect to the bridge FC port or ports.
  2. From the ONTAP cluster prompt, remove the bridge undergoing maintenance from health monitoring:
    1. Remove the bridge:storage bridge remove -name bridge-name
    2. View the list of monitored bridges and confirm that the removed bridge is not present:storage bridge show
  3. Properly ground yourself.
  4. Remove the power cables connected to the bridge to power down the bridge.
  5. Disconnect the cables that are connected to the old bridge.

    You should make note of the port to which each cable was connected.
  6. Remove the old bridge from the rack.
  7. Install the new bridge into the rack.
  8. Reconnect the power cord and shielded Ethernet cable.

    Attention
    You must not reconnect the SAS or FC cables at this time.
  9. Connect the bridge to a power source, and then turn it on.

    The bridge Ready LED might take up to 30 seconds to illuminate, indicating that the bridge has completed its power-on self test sequence.
  10. If configuring for in-band management, connect a cable from FibreBridge RS-232 serial port to the serial (COM) port on a personal computer.

    The serial connection will be used for initial configuration, and then in-band management via ONTAP and the FC ports can be used to monitor and manage the bridge.
  11. If configuring for in-band management, connect a cable from FibreBridge RS-232 serial port to the serial (COM) port on a personal computer.

    The serial connection will be used for initial configuration, and then in-band management via ONTAP and the FC ports can be used to monitor and manage the bridge.
  12. If configuring for IP management, configure the Ethernet management 1 port for each bridge by following the procedure in section 2.0 of the ATTO FibreBridge Installation and Operation Manual for your bridge model.

    In systems running ONTAP 9.5 or later, in-band management can be used to access the bridge via the FC ports rather than the Ethernet port.

    When running QuickNAV to configure an Ethernet management port, only the Ethernet management port that is connected by the Ethernet cable is configured. For example, if you also wanted to configure the Ethernet management 2 port, you would need to connect the Ethernet cable to port 2 and run QuickNAV.

  13. Configure the bridges.

    Be sure to make note of the user name and password that you designate.

    The ATTO FibreBridge Installation and Operation Manual for your bridge model has the most current information on available commands and how to use them.

    Note
    Do not configure time synchronization on FibreBridge 7600N. The time synchronization for FibreBridge 7600N is set to the cluster time after the bridge is discovered by ONTAP. It is also synchronized periodically once a day. The time zone used is GMT and is not changeable.
    1. If configuring for IP management, configure the IP settings of the bridge.

      To set the IP address without the QuickNAV utility, you need to have a serial connection to the FibreBridge.

      If using the CLI, you must run the following commands:set ipaddress mp1 ip-address set ipsubnetmask mp1 subnet-mask set ipgateway mp1 x.x.x.x set ipdhcp mp1 disabled set ethernetspeed mp1 1000
    2. Configure the bridge name.

      The bridges should each have a unique name within the MetroCluster configuration.
      Example bridge names for one stack group on each site:

      • bridge_A_1a

      • bridge_A_1b

      • bridge_B_1a

      • bridge_B_1b

      If using the CLI, you must run the following command:set bridgename" bridgename
    3. If running ONTAP 9.4, enable SNMP on the bridge: set SNMP enabled

      If running ONTAP 9.5 or later, ONTAP will use in-band monitoring via the FC connection to the bridge, so you should leave SNMP disabled.
  14. Configure the bridge FC ports.
    1. Configure the data rate/speed of the bridge FC ports.

      The supported FC data rate depends on your model bridge.

      • The FibreBridge 7600 bridge supports up to 32, 16, or 8 Gbps.

      • The FibreBridge 6500 bridge supports up to 8, 4, or 2 Gbps.

      Note
      The FCDataRate speed you select is limited to the maximum speed supported by both the bridge and the FC port of the controller module or switch to which the bridge port connects. Cabling distances must not exceed the limitations of the SFPs and other hardware.

      If using the CLI, you must run the following command: set FCDataRate port-number port-speed
    2. You must configure or disable the FC2 port.

      • If you are using the second port, you must repeat the previous substeps for the FC2 port.

      • If you are not using the second port, then you must disable the unused port:

        FCPortDisable port-number

      The following example shows the disabling of FC port 2:
      <kbd className="ph userinput linebreak">FCPortDisable 2</kbd>

      Fibre Channel Port 2 has been disabled.
    3. Disable the unused SAS ports: SASPortDisable sas-port

      Note
      SAS ports A through D are enabled by default. You must disable the SAS ports that are not being used.

      If only SAS port A is used, then SAS ports B, C, and D must be disabled. The following example shows disabling of SAS port B. You must similarly disable SAS ports C and D:
      <kbd className="ph userinput linebreak">SASPortDisable b</kbd>

      SAS Port B has been disabled.
  15. Secure access to the bridge and save the bridge's configuration.
    1. From the controller prompt check the status of the bridges: storage bridge show

      The output shows which bridge is not secured.

    2. Check the status of the unsecured bridge's ports: info
      The output shows the status of Ethernet ports MP1 and MP2.
    3. If Ethernet port MP1 is enabled, run the following command: set EthernetPort mp1 disabled
      Note
      If Ethernet port MP2 is also enabled, repeat the previous substep for port MP2.
    4. Save the bridge's configuration.
      You must run the following commands: SaveConfigurationFirmwareRestart
      You are prompted to restart the bridge.
  16. Update the FibreBridge firmware on each bridge.

    Updating firmware on FibreBridge 7600N bridge on configurations running ONTAP 9.4 and later

  17. Reconnect the SAS and FC cables to the same ports on the new bridge.

    Note
    Wait at least 10 seconds before connecting the port. The SAS cable connectors are keyed; when oriented correctly into a SAS port, the connector clicks into place and the disk shelf SAS port LNK LED illuminates green. For disk shelves, you insert a SAS cable connector with the pull tab oriented down (on the underside of the connector). For controllers, the orientation of SAS ports can vary depending on the platform model; therefore, the correct orientation of the SAS cable connector varies.
  18. Verify that each bridge can see all of the disk drives and disk shelves to which the bridge is connected:sastargets

    The output shows the devices (disks and disk shelves) to which the bridge is connected. The output lines are sequentially numbered so that you can quickly count the devices.

    Example

    The following output shows that 10 disks are connected:
    Tgt VendorID ProductID        Type        SerialNumber
      0 LENOVO   X410_S15K6288A15 DISK        3QP1CLE300009940UHJV
      1 LENOVO   X410_S15K6288A15 DISK        3QP1ELF600009940V1BV
      2 LENOVO   X410_S15K6288A15 DISK        3QP1G3EW00009940U2M0
      3 LENOVO   X410_S15K6288A15 DISK        3QP1EWMP00009940U1X5
      4 LENOVO   X410_S15K6288A15 DISK        3QP1FZLE00009940G8YU
      5 LENOVO   X410_S15K6288A15 DISK        3QP1FZLF00009940TZKZ
      6 LENOVO   X410_S15K6288A15 DISK        3QP1CEB400009939MGXL
      7 LENOVO   X410_S15K6288A15 DISK        3QP1G7A900009939FNTT
      8 LENOVO   X410_S15K6288A15 DISK        3QP1FY0T00009940G8PA
      9 LENOVO   X410_S15K6288A15 DISK        3QP1FXW600009940VERQ
  19. Verify that the command output shows that the bridge is connected to all of the appropriate disks and disk shelves in the stack.
    If the output is...Then...
    CorrectRepeat the previous step for each remaining bridge.
    Not correct

    1. Check for loose SAS cables or correct the SAS cabling by repeating Step 17.

    2. Repeat the previous step.

  20. If the bridge is in a fabric-attached MetroCluster configuration, reenable the FC switch port that you disabled at the beginning of this procedure.

    This should be the port that connects to the bridge.
  21. From the system console of both controller modules, verify that all of the controller modules have access through the new bridge to the disk shelves (that is, that the system is cabled for Multipath HA): run local sysconfig

    Note
    It might take up to a minute for the system to complete discovery.

    If the output does not indicate Multipath HA, you must correct the SAS and FC cabling because not all of the disk drives are accessible through the new bridge.

    Example

    The following output states that the system is cabled for Multipath HA:
    Lenovo Release 9.6P5: Fri Dec 13 13:23:47 EST 2019
    System ID: 1231231231 (node_A_1); partner ID: 4564564564 (node_A_2) 
    System Serial Number: 700000123123 (node_A_1); partner Serial Number: 700000456456 (node_A_2) 
    System Rev: A4 
    System Storage Configuration: Multi-Path HA
    System ACP Connectivity: Inband Active

    Attention
    When the system is not cabled as Multipath HA, restarting a bridge might cause loss of access to the disk drives and result in a multi-disk panic.
  22. If running ONTAP 9.4 or earlier, verify that the bridge is configured for SNMP.

    If you are using the bridge CLI, run the following command:
    get snmp
  23. From the ONTAP cluster prompt, add the bridge to health monitoring:
    1. Add the bridge, using the command for your version of ONTAP:

      ONTAP versionCommand
      9.5 and laterstorage bridge add -address 0.0.0.0 -managed-by in-band -name bridge-name
      9.4storage bridge add -address bridge-ip-address -name bridge-name
    2. Verify that the bridge has been added and is properly configured: storage bridge show

      It might take as long as 15 minutes to reflect all data because of the polling interval. The ONTAP health monitor can contact and monitor the bridge if the value in the Status column is ok, and other information, such as the worldwide name (WWN), is displayed.

      Example

      The following example shows that the FC-to-SAS bridges are configured:
      controller_A_1::> storage bridge show

      Bridge              Symbolic Name Is Monitored  Monitor Status  Vendor Model                Bridge WWN
      ------------------  ------------- ------------  --------------  ------ -----------------    ----------
      ATTO_10.10.20.10  atto01        true          ok              Atto   FibreBridge 7600N   20000010867038c0     
      ATTO_10.10.20.11  atto02        true          ok              Atto   FibreBridge 7600N   20000010867033c0
      ATTO_10.10.20.12  atto03        true          ok              Atto   FibreBridge 7600N   20000010867030c0
      ATTO_10.10.20.13  atto04        true          ok              Atto   FibreBridge 7600N   2000001086703b80

      4 entries were displayed

       controller_A_1::>

  24. 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
Related concepts