Cisco UCS Manager CLI Configuration Guide, Release 1.3(1)
Configuring Named VSANs
Downloads: This chapterpdf (PDF - 429.0KB) The complete bookPDF (PDF - 4.5MB) | Feedback

Configuring Named VSANs

Configuring Named VSANs

This chapter includes the following sections:

Named VSANs

A named VSAN creates a connection to a specific external SAN. The VSAN isolates traffic to that external SAN, including broadcast traffic. The traffic on one named VSAN knows that the traffic on another named VSAN exists, but cannot read or access that traffic.

Like a named VLAN, the name that you assign to a VSAN ID adds a layer of abstraction that allows you to globally update all servers associated with service profiles that use the named VSAN. You do not need to reconfigure the servers individually to maintain communication with the external SAN. You can create more than one named VSAN with the same VSAN ID.

Named VSANs in Cluster Configurations

In a cluster configuration, a named VSAN can be configured to be accessible only to the FC uplinks on one fabric interconnect or to the FC Uplinks on both fabric interconnects.

Named VSANs and the FCoE VLAN ID

You must configure each named VSAN with an FCoE VLAN ID. This property determines which VLAN is used for transporting the VSAN and its Fibre Channel packets.

For FIP capable, converged network adapters, such as the Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters.

In the following sample configuration, a service profile with a vNIC and vHBA mapped to fabric A is associated with a server that has FIP capable, converged network adapters:


  • The vNIC is configured to use VLAN 10.

  • VLAN 10 is also designated as the native VLAN for the vNIC.

  • The vHBA is configured to use VSAN 2.

  • Therefore, VSAN 2 cannot be configured with VLAN 10 as the FCoE VLAN ID. VSAN 2 can be mapped to any other VLAN configured on fabric A.

Creating a Named VSAN Accessible to Both Fabric Interconnects

You can create a named VSAN with IDs from 1 to 4093.

Procedure
  Command or Action Purpose
Step 1 UCS-A# scope fc-uplink  

Enters Fibre Channel uplink mode.

 
Step 2 UCS-A /fc-uplink # create vsan vsan-name vsan-id fcoe-id  

Creates the specified named VSAN, specifies the VSAN name, VSAN ID and FCoE VLAN ID, and enters Fibre Channel uplink VSAN mode.

 
Step 3 UCS-A /fc-uplink/vsan # commit-buffer  

Commits the transaction to the system configuration.

 

The following example creates a named VSAN for both fabric interconnects, names the VSAN accounting, assigns the VSAN ID 2112, assigns the FCoE VLAN ID 4021, and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /eth-uplink* # create vsan accounting 2112 4021
UCS-A /eth-uplink/vsan* # commit-buffer
UCS-A /eth-uplink/vsan # 

Creating a Named VSAN Accessible to One Fabric Interconnect

You can create a named VSAN with IDs from 1 to 4093.

Procedure
  Command or Action Purpose
Step 1 UCS-A# scope fc-uplink  

Enters Fibre Channel uplink mode.

 
Step 2 UCS-A /fc-uplink # scope fabric {a | b}  

Enters Fibre Channel uplink fabric interconnect mode for the specified fabric interconnect (A or B).

 
Step 3 UCS-A /fc-uplink/fabric # create vsan vsan-name vsan-id fcoe-id  

Creates the specified named VSAN, specifies the VSAN name, VSAN ID, and FCoE VLAN ID, and enters Fibre Channel uplink VSAN mode.

 
Step 4 UCS-A /fc-uplink/fabric/vsan # commit-buffer  

Commits the transaction to the system configuration.

 

The following example creates a named VSAN for fabric interconnect A, names the VSAN finance, assigns the VSAN ID 3955, assigns the FCoE VLAN ID 2221, and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create vsan finance 3955 2221
UCS-A /fc-uplink/fabric/vsan* # commit-buffer
UCS-A /fc-uplink/fabric/vsan # 

Deleting a Named VSAN

If Cisco UCS Manager includes a named VSAN with the same VSAN ID as the one you delete, the VSAN is not removed from the fabric interconnect configuration until all named VSANs with that ID are deleted.

Procedure
  Command or Action Purpose
Step 1 UCS-A# scope eth-uplink  

Enters Ethernet uplink mode.

 
Step 2 UCS-A /fc-uplink # delete vsan vsan-name  

Deletes the specified named VSAN.

 
Step 3 UCS-A /fc-uplink # commit-buffer  

Commits the transaction to the system configuration.

 

The following example deletes a named VSAN and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # delete vsan finance
UCS-A /fc-uplink* # commit-buffer
UCS-A /fc-uplink #