HP 6125XLG R2306-HP 6125XLG Blade Switch FCoE Configuration Guide - Page 53

Configuring VSAN, VSAN fundamentals, Trunk VSAN in an FC network

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 53 highlights

Configuring VSAN The virtual storage area network (VSAN) technology breaks a physical SAN into multiple VSANs, and provides more secure, reliable, and flexible services. Devices in a VSAN cannot get information about any other VSAN and devices in any other VSAN. Each VSAN performs the following operations independently: selecting a principal switch, assigning domain IDs, running routing protocols, maintaining routing table and FIB table, and providing services. The VSAN technology delivers the following benefits: • Improved security-VSANs are isolated from each other. • Improved adaptability-Each VSAN independently runs and provides services. Different VSANs can use the same address space so that network capacity is improved. • Flexibility-You can assign interfaces to different VSANs without changing the physical connections of the SAN. VSAN fundamentals VFC interfaces on the switch can only work as trunk ports. A trunk port can belong to multiple VSANs. Trunk VSAN in an FC network The trunk VSAN technology implements logical isolation among VSANs. The trunk VSAN works as follows: The trunk VSAN adds a Virtual Fabric Tagging Header (VFT_Header, also known as VSAN tag) to the FC frames. The VFT_Header contains a VF_ID (also known as "VSAN ID") field to indicate the VSAN of the FC frames. In this way, FC frames within different VF_IDs are contained in their respective VSANs, and different VSANs cannot communicate with each other. VSAN tags are added to and removed from an FC frame during transmission. A switch supports multiple VSANs one physical interface, thus reducing physical connections and implementing logical isolation in a physically connected SAN. 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 need to be mapped to VLANs as configured by the user, and the FIB table for a VSAN is also stored on the relevant VLAN. FCoE packets 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, and its trunk VLAN list must include the VLANs mapped to each VSAN in the VSAN trunk list of the VFC interface. An FCoE packet transmitted from a VFC interface can use the VLAN ID in VLAN_Header to identify the VLAN to which it belongs. 47

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
47
Configuring VSAN
The virtual storage area network (VSAN) technology breaks a physical SAN into multiple VSANs, and
provides more secure, reliable, and flexible services.
Devices in a VSAN cannot get information about any other VSAN and devices in any other VSAN. Each
VSAN performs the following operations independently: selecting a principal switch, assigning domain
IDs, running routing protocols, maintaining routing table and FIB table, and providing services.
The VSAN technology delivers the following benefits:
•
Improved security
—VSANs are isolated from each other.
•
Improved adaptability
—Each VSAN independently runs and provides services. Different VSANs
can use the same address space so that network capacity is improved.
•
Flexibility
—You can assign interfaces to different VSANs without changing the physical
connections of the SAN.
VSAN fundamentals
VFC interfaces on the switch can only work as trunk ports. A trunk port can belong to multiple VSANs.
Trunk VSAN in an FC network
The trunk VSAN technology implements logical isolation among VSANs. The trunk VSAN works as
follows: The trunk VSAN adds a Virtual Fabric Tagging Header (VFT_Header, also known as VSAN tag)
to the FC frames. The VFT_Header contains a VF_ID (also known as "VSAN ID") field to indicate the
VSAN of the FC frames. In this way, FC frames within different VF_IDs are contained in their respective
VSANs, and different VSANs cannot communicate with each other. VSAN tags are added to and
removed from an FC frame during transmission. A switch supports multiple VSANs one physical interface,
thus reducing physical connections and implementing logical isolation in a physically connected SAN.
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 need to be mapped to VLANs as
configured by the user, and the FIB table for a VSAN is also stored on the relevant VLAN. FCoE packets
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, and its trunk VLAN list must include the VLANs mapped to each VSAN in the VSAN trunk
list of the VFC interface. An FCoE packet transmitted from a VFC interface can use the VLAN ID in
VLAN_Header to identify the VLAN to which it belongs.