Skip to main content

Powering on the MetroCluster configuration and returning to normal operation

After maintenance has been completed or the site has been moved, you must power on the site and reestablish the MetroCluster configuration.

  1. Power on the switches.

    Switches should be powered on first. They might have been powered on during the previous step if the site was relocated.
    1. Reconfigure the Inter-Switch Link (ISL) if required or if this was not completed as part of the relocation.
    2. Enable the ISL if fencing was completed.
    3. Verify the ISL.
  2. Power on the shelves and allow enough time for them to power on completely.
  3. Power on the FibreBridge bridges.

    Note
    You can skip this step if your configuration is a MetroCluster IP configuration.
    1. On the FC switches, verify that the ports connecting the bridges are coming online.

      You can use a command such as switchshow for Brocade switches, and show interface brief for Cisco switches.
    2. Verify that the shelves and disks on the bridges are clearly visible.

      You can use a command such as sastargets on the ATTO command-line interface (CLI).
  4. Enable the ISLs on the FC switches.

    Note
    Skip this step if your configuration is a MetroCluster IP configuration.
    Enable the ports based on whether you are using Brocade or Cisco switches as shown in the following table:
    Switch typeCommand

    If the FC Switches are Brocade switches...

    1. Enter the portcfgpersistentenable port command to persistently enable the ports. This must be done on both switches at the surviving site.

      The following example shows ports 14 and 15 being enabled on Switch_A_1:


        
       Switch_A_1:admin> portcfgpersistentenable 14
       Switch_A_1:admin> portcfgpersistentenable 15
       Switch_A_1:admin>

    2. Verify that the switch port is enabled using the switchshow command:

    switch_A_1:admin> switchshow
     switchName:Switch_A_1
     switchType:109.1
     switchState:Online   
     switchMode:Native
     switchRole:Principal
     switchDomain:2
     switchId:fffc02
     switchWwn:10:00:00:05:33:88:9c:68
     zoning:ON (T5_T6)
     switchBeacon:OFF
     FC Router:OFF
     FC Router BB Fabric ID:128
     Address Mode:0
     
    Index Port Address Media Speed State   Proto
    ==============================================
     ...
    14  14   020e00   id    16G   Online   FC  E-Port  10:00:00:05:33:86:89:cb "Switch_A_1"
    15  15   020f00   id    16G   Online   FC  E-Port  10:00:00:05:33:86:89:cb "Switch_A_1" (downstream) 
       ...
     switch_A_1:admin>

    If the FC Switches are Cisco switches...

    1. Use the interface command to enable the ports.

      The following example shows port fc1/14 and fc1/15 being enabled on Switch A_1:


       switch_A_1# conf t
       switch_A_1(config)# interface fc1/14-15
       switch_A_1(config)# no shut
       switch_A_1(config-if)# end
       switch_A_1# copy running-config startup-config

    2. Verify that the switch port is disabled:

    switch_A_1# show interface brief
    switch_A_1#
  5. Verify that the storage is now visible.

    Select the appropriate method of determining whether the storage is visible based on whether you have a MetroCluster IP or FC configuration:
    ConfigurationStep

    If your configuration is a MetroCluster IP...

    Verify that the local storage is visible from the node Maintenance mode.

    If your configuration is a MetroCluster FC...

    Verify that the storage is visible from the surviving site. Put the offline plexes back online. This restarts the resync operations and reestablishes the SyncMirror.

  6. Reestablish the MetroCluster configuration.

    Follow the instructions in the MetroCluster Disaster and Recovery Guide to perform healing and switchback operations according to your MetroCluster configuration.

    MetroCluster management and disaster recovery