Cisco UCS Manager GUI Configuration Guide, Release 1.3(1)

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Results

Configuring Named VSANs

This chapter includes the following sections:

Named VSANs
Creating a Named VSAN
Deleting a Named VSAN

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

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

Procedure

Step 1

In the Navigation pane, click the SAN tab.

Step 2

In the SAN tab, click the SAN node.

Step 3

In the Work pane, click the VSANs tab.

Step 4

On the icon bar to the right of the table, click +.

If the + icon is disabled, click an entry in the table to enable it.

Step 5

In the Create VSAN dialog box, complete the following fields:

Name	Description
Name field	The name assigned to the network. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved.
Type radio button	Click the radio button to determine how the VSAN should be configured. You can choose: Common/Global—The VSAN maps to the same VSAN ID in all available fabrics. Fabric A—The VSAN maps to the a VSAN ID that exists only in fabric A. Fabric B—The VSAN maps to the a VSAN ID that exists only in fabric B. Both Fabrics Configured Differently—The VSAN maps to a different VSAN ID in each available fabric. If you choose this option, Cisco UCS Manager GUI displays a VSAN ID field and a FCoE VLAN field for each fabric.
VSAN ID field	The unique identifier assigned to the network. The ID can be between 1 and 4093.
FCoE VLAN field	The unique identifier assigned to the VLAN used for Fibre Channel connections. 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.

Step 6

Click OK.

Cisco UCS Manager GUI adds the VSAN to one of the following VSANs nodes:

The SAN Cloud > VSANs node for a VSAN accessible to both fabric interconnects.
The FC Uplinks - Switch_Name > VSANs node for a VSAN accessible to only one fabric interconnect.

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.