Skip to main content

Creating and configuring VSANs on Cisco FC switches

You must create a VSAN for the FC-VI ports and a VSAN for the storage ports on each FC switch in the MetroCluster configuration. The VSANs should have a unique number and name. You must do additional configuration if you are using two ISLs with in-order delivery of frames.

The examples here use the following naming conventions:

Switch fabricVSAN nameID number
1FCVI_1_1010
STOR_1_2020
2FCVI_2_3030
STOR_2_2040

This task must be performed on each FC switch fabric.

  1. Configure the FC-VI VSAN:
    1. Enter configuration mode if you have not done so already: config t
    2. Edit the VSAN database: vsan database
    3. Set the VSAN ID: vsan vsan-ID
    4. Set the VSAN name: vsan vsan-ID name vsan_name
  2. Add ports to the FC-VI VSAN:
    1. Add the interfaces for each port in the VSAN: vsan vsan-ID interface interface_name

      For the FC-VI VSAN, the ports connecting the local FC-VI ports will be added.
    2. Exit configuration mode: end
    3. Copy the running-config to the startup-config: copy running-config startup-config

    In the following example, the ports are fc1/1 and fc1/13:
    FC_switch_A_1# conf t
    FC_switch_A_1(config)# vsan database
    FC_switch_A_1(config)# vsan 10 interface fc1/1
    FC_switch_A_1(config)# vsan 10 interface fc1/13
    FC_switch_A_1(config)# end
    FC_switch_A_1# copy running-config startup-config
    FC_switch_B_1# conf t
    FC_switch_B_1(config)# vsan database
    FC_switch_B_1(config)# vsan 10 interface fc1/1
    FC_switch_B_1(config)# vsan 10 interface fc1/13
    FC_switch_B_1(config)# end
    FC_switch_B_1# copy running-config startup-config
  3. Verify port membership of the VSAN: show vsan member 

    FC_switch_A_1# show vsan member
    FC_switch_B_1# show vsan member
  4. Configure the VSAN to guarantee in-order delivery of frames or out-of-order 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 to configure in-order delivery of frames:

      1. Enter configuration mode: conf t

      2. Enable the in-order guarantee of exchanges for the VSAN: in-order-guarantee vsan vsan-ID

        Attention
        For FC-VI VSANs (FCVI_1_10 and FCVI_2_30), you must enable in-order guarantee of frames and exchanges only on VSAN 10 .

      3. Enable load balancing for the VSAN: vsan vsan-ID loadbalancing src-dst-id

      4. Exit configuration mode: end

      5. Copy the running-config to the startup-config: copy running-config startup-config

        The commands to configure in-order delivery of frames on FC_switch_A_1:
        FC_switch_A_1# config t
        FC_switch_A_1(config)# in-order-guarantee vsan 10
        FC_switch_A_1(config)# vsan database
        FC_switch_A_1(config-vsan-db)# vsan 10 loadbalancing src-dst-id
        FC_switch_A_1(config-vsan-db)# end
        FC_switch_A_1# copy running-config startup-config

        The commands to configure in-order delivery of frames on FC_switch_B_1:
        FC_switch_B_1# config t
        FC_switch_B_1(config)# in-order-guarantee vsan 10
        FC_switch_B_1(config)# vsan database
        FC_switch_B_1(config-vsan-db)# vsan 10 loadbalancing src-dst-id
        FC_switch_B_1(config-vsan-db)# end
        FC_switch_B_1# copy running-config startup-config
    • The following steps must be performed to configure out-of-order delivery of frames:

      1. Enter configuration mode: conf t

      2. Disable the in-order guarantee of exchanges for the VSAN: no in-order-guarantee vsan vsan-ID

      3. Enable load balancing for the VSAN: vsan vsan-ID loadbalancing src-dst-id

      4. Exit configuration mode: end

      5. Copy the running-config to the startup-config: copy running-config startup-config

        The commands to configure out-of-order delivery of frames on FC_switch_A_1:
        FC_switch_A_1# config t
        FC_switch_A_1(config)# no in-order-guarantee vsan 10
        FC_switch_A_1(config)# vsan database
        FC_switch_A_1(config-vsan-db)# vsan 10 loadbalancing src-dst-id
        FC_switch_A_1(config-vsan-db)# end
        FC_switch_A_1# copy running-config startup-config

        The commands to configure out-of-order delivery of frames on FC_switch_B_1:
        FC_switch_B_1# config t
        FC_switch_B_1(config)# no in-order-guarantee vsan 10
        FC_switch_B_1(config)# vsan database
        FC_switch_B_1(config-vsan-db)# vsan 10 loadbalancing src-dst-id
        FC_switch_B_1(config-vsan-db)# end
        FC_switch_B_1# copy running-config startup-config
      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

  5. Set QoS policies for the FC-VI VSAN:
    1. Enter configuration mode: conf t
    2. Enable the QoS and create a class map by entering the following commands in sequence: qos enable qos class-map class_name match-any
    3. Add the class map created in a previous step to the policy map: class class_name
    4. Set the priority: priority high
    5. Add the VSAN to the policy map created previously in this procedure: qos service policy policy_name vsan vsanid
    6. Copy the updated configuration to the startup configuration: copy running-config startup-config

    The commands to set the QoS policies on FC_switch_A_1:
    FC_switch_A_1# conf t
    FC_switch_A_1(config)# qos enable
    FC_switch_A_1(config)# qos class-map FCVI_1_10_Class match-any
    FC_switch_A_1(config)# qos policy-map FCVI_1_10_Policy
    FC_switch_A_1(config-pmap)# class FCVI_1_10_Class
    FC_switch_A_1(config-pmap-c)# priority high
    FC_switch_A_1(config-pmap-c)# exit
    FC_switch_A_1(config)# exit
    FC_switch_A_1(config)# qos service policy FCVI_1_10_Policy vsan 10
    FC_switch_A_1(config)# end
    FC_switch_A_1# copy running-config startup-config
    The commands to set the QoS policies on FC_switch_B_1:
    FC_switch_B_1# conf t
    FC_switch_B_1(config)# qos enable
    FC_switch_B_1(config)# qos class-map FCVI_1_10_Class match-any
    FC_switch_B_1(config)# qos policy-map FCVI_1_10_Policy
    FC_switch_B_1(config-pmap)# class FCVI_1_10_Class
    FC_switch_B_1(config-pmap-c)# priority high
    FC_switch_B_1(config-pmap-c)# exit
    FC_switch_B_1(config)# exit
    FC_switch_B_1(config)# qos service policy FCVI_1_10_Policy vsan 10
    FC_switch_B_1(config)# end
    FC_switch_B_1# copy running-config startup-config
  6. Configure the storage VSAN:
    1. Set the VSAN ID: vsan vsan-ID
    2. Set the VSAN name: vsan vsan-ID name vsan_name

    The commands to configure the storage VSAN on FC_switch_A_1:
    FC_switch_A_1# conf t
    FC_switch_A_1(config)# vsan database
    FC_switch_A_1(config-vsan-db)# vsan 20
    FC_switch_A_1(config-vsan-db)# vsan 20 name STOR_1_20
    FC_switch_A_1(config-vsan-db)# end
    FC_switch_A_1# copy running-config startup-config
    The commands to configure the storage VSAN on FC_switch_B_1:
    FC_switch_B_1# conf t
    FC_switch_B_1(config)# vsan database
    FC_switch_B_1(config-vsan-db)# vsan 20
    FC_switch_B_1(config-vsan-db)# vsan 20 name STOR_1_20
    FC_switch_B_1(config-vsan-db)# end
    FC_switch_B_1# copy running-config startup-config
  7. Add ports to the storage VSAN.

    For the storage VSAN, all ports connecting HBA or FC-to-SAS bridges must be added. In this example fc1/5, fc1/9, fc1/17, fc1/21. fc1/25, fc1/29, fc1/33, and fc1/37 are being added.

    The commands to add ports to the storage VSAN on FC_switch_A_1:
    FC_switch_A_1# conf t
    FC_switch_A_1(config)# vsan database
    FC_switch_A_1(config)# vsan 20 interface fc1/5
    FC_switch_A_1(config)# vsan 20 interface fc1/9
    FC_switch_A_1(config)# vsan 20 interface fc1/17
    FC_switch_A_1(config)# vsan 20 interface fc1/21
    FC_switch_A_1(config)# vsan 20 interface fc1/25
    FC_switch_A_1(config)# vsan 20 interface fc1/29
    FC_switch_A_1(config)# vsan 20 interface fc1/33
    FC_switch_A_1(config)# vsan 20 interface fc1/37
    FC_switch_A_1(config)# end
    FC_switch_A_1# copy running-config startup-config
    The commands to add ports to the storage VSAN on FC_switch_B_1:
    FC_switch_B_1# conf t
    FC_switch_B_1(config)# vsan database
    FC_switch_B_1(config)# vsan 20 interface fc1/5
    FC_switch_B_1(config)# vsan 20 interface fc1/9
    FC_switch_B_1(config)# vsan 20 interface fc1/17
    FC_switch_B_1(config)# vsan 20 interface fc1/21
    FC_switch_B_1(config)# vsan 20 interface fc1/25
    FC_switch_B_1(config)# vsan 20 interface fc1/29
    FC_switch_B_1(config)# vsan 20 interface fc1/33
    FC_switch_B_1(config)# vsan 20 interface fc1/37
    FC_switch_B_1(config)# end
    FC_switch_B_1# copy running-config startup-config