HP Virtual Connect Manager Command Line Interface for c-Class BladeSystem Version 4.01 User Guide

Configuring the Virtual Connect domain using the CLI 163
Virtual Connect places no special restrictions on which VLAN identifiers can be used, so the VLAN IDs
already used for the networks in the data center can be used on these shared uplinks. To configure a shared
uplink set for VLAN tagging, obtain a list of the network names and their VLAN IDs.
A shared uplink set enables multiple ports to be included to support port aggregation and link failover with
a consistent set of VLAN tags.
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.
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 outgoing
Ethernet packets are VLAN-tagged.
Modifying shared uplink sets
To modify shared uplink sets, use the set uplink command:
>set uplinkset UplinkSet-1 ConnectionMode=Auto LacpTimer=Long
Displaying shared uplink sets
To display shared uplink sets, use the show uplinkset command:
• Summary for all shared uplink sets
>show uplinkset
• Details for all shared uplink sets
>show uplinkset *
• Details for a single shared uplink set
>show uplinkset MyUplinkSetName
Adding uplink ports to a shared uplink set
To add uplink ports to a shared uplink set, use the add uplinkport command:
>add uplinkport enc0:1:2 uplinkset=MyUplinkSetName
Creating a network that uses a shared uplink set
To create a network that uses a shared uplink set, use the add network command:
>add network MyNewNetworkName uplinkset=MyUplinkSetName vlanid=156
Creating multiple networks that use a shared uplink set
To create multiple networks that use a shared uplink set, use the add network-range command:
>add network-range UplinkSet=SUS1 VLANIds=156-160
Server VLAN Tagging Support
Each server port can be connected to multiple virtual networks, each using a unique server VLAN ID for virtual
network mapping.
The translation of Server VLAN tags to internal network VLAN and again to external data center VLAN tags,
and the reverse, on incoming and outgoing frames can result in a configuration where the server VLANs
might not match the external VLANs used on uplinks. To avoid this scenario, the server connections can be