Skip to main content

Configuring basic switch settings

You must configure basic global settings, including the domain ID, for Brocade switches.

This task contains steps that must be performed on each switch at both of the MetroCluster sites.

In this procedure, you set the unique domain ID for each switch as shown in the following example. In the example, domain IDs 5 and 7 form fabric_1, and domain IDs 6 and 8 form fabric_2.

  • FC_switch_A_1 is assigned to domain ID 5

  • FC_switch_A_2 is assigned to domain ID 6

  • FC_switch_B_1 is assigned to domain ID 7

  • FC_switch_B_2 is assigned to domain ID 8

  1. Enter configuration mode: configure
  2. Proceed through the prompts:
    1. Set the domain ID for the switch.
    2. Press Enter in response to the prompts until you get to RDP Polling Cycle, and then set that value to 0 to disable the polling.
    3. Press Enter until you return to the switch prompt.

      FC_switch_A_1:admin> configure
      Fabric parameters = y
      Domain_id = 5
      .
      .

      RSCN Transmission Mode [yes, y, no, no: [no] y

      End-device RSCN Transmission Mode
       (0 = RSCN with single PID, 1 = RSCN with multiple PIDs, 2 = Fabric RSCN): (0..2) [1]
      Domain RSCN To End-device for switch IP address or name change
       (0 = disabled, 1 = enabled): (0..1) [0] 1

      .
      .
      RDP Polling Cycle(hours)[0 = Disable Polling]: (0..24) [1] 0


  3. If you are using two or more ISLs per fabric, then you can configure either in-order delivery (IOD) of frames or out-of-order (OOD) delivery of frames.

    Note
    The standard IOD settings are recommended. You should configure OOD only if necessary.

    Considerations for using TDM/WDM equipment with fabric-attached MetroCluster configurations

    • The following steps must be performed on each switch fabric to configure IOD of frames:

      1. Enable IOD: iodset

      2. Set the Advanced Performance Tuning (APT) policy to 1 : aptpolicy 1

      3. Disable Dynamic Load Sharing (DLS): dlsreset

      4. Verify the IOD settings by using the iodshow, aptpolicy, and dlsshow commands.

        For example, issue the following commands on FC_switch_A_1:

        FC_switch_A_1:admin> iodshow
            IOD is set
            
            FC_switch_A_1:admin> aptpolicy
            Current Policy: 1 0(ap)

        3 0(ap) : Default Policy
            1: Port Based Routing Policy
            3: Exchange Based Routing Policy
                 0: AP Shared Link Policy 
                 1: AP Dedicated Link Policy 
            command aptpolicy completed
            
            FC_switch_A_1:admin> dlsshow
            DLS is not set

      5. Repeat these steps on the second switch fabric.

    • The following steps must be performed on each switch fabric to configure OOD of frames:

      1. Enable OOD: iodreset

      2. Set the Advanced Performance Tuning (APT) policy to 3 : aptpolicy 3

      3. Disable Dynamic Load Sharing (DLS): dlsreset

      4. Verify the OOD settings by using the iodshow, aptpolicy and dlsshow commands.

        For example, issue the following commands on FC_switch_A_1:

        FC_switch_A_1:admin> iodshow
            IOD is not set
            
            FC_switch_A_1:admin> aptpolicy
            Current Policy: 3 0(ap)
            3 0(ap) : Default Policy
            1: Port Based Routing Policy
            3: Exchange Based Routing Policy
            0: AP Shared Link Policy 
            1: AP Dedicated Link Policy 
            command aptpolicy completed

            
            FC_switch_A_1:admin> dlsshow
            DLS is set by default with current routing policy

      5. Repeat these steps on the second switch fabric.

      Note
      When configuring ONTAP on the controller modules, OOD must be explicitly configured on each controller module in the MetroCluster configuration.

      Configuring in-order delivery or out-of-order delivery of frames on ONTAP software

  4. Verify that the switch is using the dynamic port licensing method.
    1. Run the licensePort --show command.

      FC_switch_A_1:admin> licenseport -show 
      24 ports are available in this switch 
      Full POD license is installed 
      Dynamic POD method is in use
      Note
      FabOS versions before 8.0 run the following commands as admin and versions 8.0 and later run them as root.
    2. Enable the root user.

      If the root user is already disabled by Brocade, enable the root user as shown in the following example:

      FC_switch_A_1:admin> userconfig --change root -e yes
      FC_switch_A_1:admin> rootaccess --set consoleonly
    3. Run the license command: licensePort --show 

      FC_switch_A_1:root> licenseport -show
      24 ports are available in this switch
      Full POD license is installed
      Dynamic POD method is in use
    4. Change the license method to dynamic: licenseport --method dynamic

      Note
      If the dynamic license method is not in use (if the method is static), you must change the license method to dynamic. Skip this step if the dynamic license method is in use.

      FC_switch_A_1:admin> licenseport --method dynamic
      The POD method has been changed to dynamic.
      Please reboot the switch now for this change to take effect
  5. Enable the trap for T11-FC-ZONE-SERVER-MIB to provide successful health monitoring of the switches in ONTAP:
    1. Enable the T11-FC-ZONE-SERVER-MIB: snmpconfig --set mibCapability -mib_name T11-FC-ZONE-SERVER-MIB -bitmask 0x3f
    2. Enable the T11-FC-ZONE-SERVER-MIB trap: snmpconfig --enable mibcapability -mib_name SW-MIB -trap_name swZoneConfigChangeTrap
    3. Repeat the previous steps on the second switch fabric.
  6. Optional: If you set the community string to a value other than public, you must configure the ONTAP Health Monitors using the community string you specify:
    1. Change the existing community string: snmpconfig --set snmpv1
    2. Press Enter until you see the Community (ro): [public] text.
    3. Enter the desired community string.

    On FC_switch_A_1:

    FC_switch_A_1:admin> snmpconfig --set snmpv1
    SNMP community and trap recipient configuration:
    Community (rw): [Secret C0de]
    Trap Recipient's IP address : [0.0.0.0]
    Community (rw): [OrigEquipMfr]
    Trap Recipient's IP address : [0.0.0.0]
    Community (rw): [private]
    Trap Recipient's IP address : [0.0.0.0]
    Community (ro): [public] mcchm                        <<<<<<<<<<<<< change the community string to the 
    desired value, in this example it is set to 'mcchm'
    Trap Recipient's IP address : [0.0.0.0]
    Community (ro): [common]
    Trap Recipient's IP address : [0.0.0.0]
    Community (ro): [FibreChannel]
    Trap Recipient's IP address : [0.0.0.0]
    Committing configuration.....done.
    FC_switch_A_1:admin>

    On FC_switch_B_1:
    FC_switch_B_1:admin> snmpconfig --set snmpv1
    SNMP community and trap recipient configuration:
    Community (rw): [Secret C0de]
    Trap Recipient's IP address : [0.0.0.0]
    Community (rw): [OrigEquipMfr]
    Trap Recipient's IP address : [0.0.0.0]
    Community (rw): [private]
    Trap Recipient's IP address : [0.0.0.0]
    Community (ro): [public] mcchm                        <<<<<<<<<<<<< change the community string to the 
    desired value, in this example it is set to 'mcchm'
    Trap Recipient's IP address : [0.0.0.0]
    Community (ro): [common]
    Trap Recipient's IP address : [0.0.0.0]
    Community (ro): [FibreChannel]
    Trap Recipient's IP address : [0.0.0.0]
    Committing configuration.....done.
    FC_switch_B_1:admin>

  7. Reboot the switch: reboot

    On FC_switch_A_1:
    FC_switch_A_1:admin> reboot
    On FC_switch_B_1:
    FC_switch_B_1:admin> reboot
  8. Persistently enable the switch: switchcfgpersistentenable

    On FC_switch_A_1:
    FC_switch_A_1:admin> switchcfgpersistentenable
    On FC_switch_B_1:
    FC_switch_B_1:admin> switchcfgpersistentenable