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.
This chapter includes the following sections:
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.
In a cluster configuration, a named VSAN can be configured to be accessible only to the Fibre Channel uplink ports on one fabric interconnect or to the Fibre Channel uplink ports on both fabric interconnects.
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:
You can configure Fibre Channel uplink trunking for the named VSANs on each fabric interconnect. If you enable trunking on a fabric interconnect, all named VSANs in a Cisco UCS instance are allowed on all Fibre Channel uplink ports on that fabric interconnect.
The following guidelines and recommendations apply to all named VSANs, including storage VSANs.
Do not configure a VSAN as 4079. This VSAN is reserved and cannot be used in either FC switch mode or FC end-host mode.
If you create a named VSAN with ID 4079, Cisco UCS Manager marks that VSAN with an error and raises a fault.
If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3040 to 4078.
VSANs in that range are not operational if the fabric interconnects are configured to operate in FC switch mode. Cisco UCS Manager marks that VSAN with an error and raises a fault.
If you plan to use FC end-host mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3840 to 4079.
VSANs in that range are not operational if the following conditions exist in a Cisco UCS domain:
If these configurations exist, Cisco UCS Manager does the following:
If you disable Fibre Channel trunking and delete any existing SAN port channels, Cisco UCS Manager returns all VSANs in the range from 3840 to 4078 to an operational state and restores any associated vHBAs back to those VSANs.
If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs in the range from 3040 to 4078.
When a fabric interconnect operating in FC switch mode is connected to MDS as the upstream switch, VSANs configured in Cisco UCS Manager in the range from 3040 to 4078 and assigned as port VSANs cannot be created in MDS. This configuration results in a possible port VSAN mismatch.
Note |
FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. |
You can create a named VSAN with IDs from 1 to 4093, except for those in the following reserved ranges:
You can create a named VSAN with IDs from 1 to 4093, except for those in the following reserved ranges:
Step 1 | In the Navigation pane, click the SAN tab. | ||||||||||||
Step 2 | On the SAN tab, expand . | ||||||||||||
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:
|
||||||||||||
Step 6 |
Click OK. Cisco UCS Manager GUI adds the VSAN to one of the following VSANs nodes: |
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.
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 |
Click one of the following subtabs, depending upon what type of VSAN you want to delete:
|
||||||||||
Step 5 |
In the table, click the VSAN you want to delete. You can use the Shift key or Ctrl key to select multiple entries. |
||||||||||
Step 6 | Right-click the highlighted VSAN or VSANs and choose Delete. | ||||||||||
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Note |
FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. |
Step 1 | In the Navigation pane, click the SAN tab. |
Step 2 | On the SAN tab, expand . |
Step 3 | Choose the VSAN for which you want to modify the FCoE VLAN ID. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the FCoE VLAN field, enter the desired VLAN ID. |
Step 6 | Click Save Changes. |
Note |
If the fabric interconnects are configured for Fibre Channel end-host mode, enabling Fibre Channel uplink trunking renders all VSANs with an ID in the range from 3840 to 4079 non-operational. |
Step 1 | In the Navigation pane, click the SAN tab. |
Step 2 | On the SAN tab, expand . |
Step 3 | Click the node for the fabric where you want to enable FC uplink trunking. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Enable FC Uplink Trunking. |
Step 6 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Step 1 | In the Navigation pane, click the SAN tab. |
Step 2 | On the SAN tab, expand . |
Step 3 | Click the node for the fabric where you want to disable Fibre Channel uplink trunking. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Disable FC Uplink Trunking. |
Step 6 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |