HP Virtual Connect 1.10Gb-F Ethernet Module for c-Class BladeSystem - Manual (Page 46)

Configuring the Virtual Connect domain using the CLI 46
Because VLAN tags are added or removed when Ethernet packets leave or enter the VC-Enet shared
uplink, the VLAN tags have no relevance after the Ethernet packet enters the enclosure.
IMPORTANT: If you are deploying a server where VLAN tags will be used (added) on the
server itself, do not connect the server Ethernet port carrying VLAN-tagged traffic to a shared
uplink set.
Identifying an associated network as the native VLAN causes all untagged incoming Ethernet packets to
be placed onto this network. Only one associated network can be designated as the native VLAN. All out-
going Ethernet packets are VLAN tagged.
Displaying shared uplink port sets
• Summary display
>show uplinkset
• Detailed display
>show uplinkset *
• Single uplinkset display
>show uplinkset MyUplinkSetName
Adding uplink ports to a shared uplink port set
To add uplink ports to a shared uplink port set, use the
add uplinkport
command:
>add uplinkport enc0:1:2 uplinkset=MyUplinkSetName
Creating a network that uses a shared uplink port set
To create a network that uses a shared uplink port set, use the
add network
command:
>add network MyNewNetworkName uplinkset=MyUplinkSetName vlanid=156
Fibre Channel setup
To configure external Fibre Channel connectivity for the HP BladeSystem c-Class enclosure, do the
following:
1. Identify WWNs to be used on the server blades deployed within this Virtual Connect Domain.
2. Define available SAN fabrics.
Configuring WWN address ranges
• VC-Defined
>set domain WwnType=VC-Defined WwnPool=5
• Factory-Default
>set domain WwnType=Factory-Default
Each server blade FC HBA mezzanine card ships with factory default port and node WWNs for each FC
HBA port. Each WWN is a 64-bit number that uniquely identifies the FC HBA port/node to other devices
on the network. While the hardware ships with default WWNs, Virtual Connect has the ability to assign
WWNs that will override the factory default WWNs while the server remains in that Virtual Connect
enclosure. When configured to assign WWNs, Virtual Connect securely manages the WWNs by