H3C Technologies H3C S10500 Series Switches - Manual (Page 38)

27
frames to the N_Ports of different disk devices. The frames from the disk devices to the server are
processed in the same way and finally reach the servers.
Figure 16 Trunk VSAN network
During the transmission process, VFT_Headers are added to and removed from the frames. A switch can
use the same physical interface to support multiple VSANs. The trunk VSAN technology reduces the
number of physical connections, actually implementing logical isolation in a physical network.
Trunk VSAN in an FCoE network
FCoE carries FC over Ethernet. In an FCoE network:
• VSANs in FC must be mapped to VLANs as configured by the user.
• The FIB table for a VSAN is also stored on the relevant VLAN.
FCoE frames use VLAN_Header in place of VFT_Header in FC frames and are forwarded based on the
VLAN ID in VLAN_Header.
A VFC interface can only work as a trunk port. The bound Ethernet interface must also be configured as
a trunk port. Its trunk VLAN list must include the VLANs mapped to each VSAN in the trunk VSAN list of
the VFC interface. An FCoE frame transmitted from a VFC interface can use the VLAN ID in
VLAN_Header to identify the VLAN to which it belongs.
Creating a VSAN
Initially, only the default VSAN (VSAN 1) exists. You cannot create or delete VSAN 1. You can create
VSANs 2 to 3839.
To create a VSAN:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create a VSAN and enter VSAN view. vsan vsan-id
By default, only the default VSAN
(VSAN 1) exists.
F_Port
F_Port
F_Port
F_Port
N_Port
N_Port N_Port
N_Port
VSAN 1
E_Port E_Port
VSAN 1
VSAN 2 VSAN 2
FC Fabric
Server A
Server B
Disk A
Disk B
FC switch B FC switch A