Multiple network connections for a server port, Defining server vlan mappings – HP 1.10GB Virtual Connect Ethernet Module for c-Class BladeSystem User Manual
Page 104
Server management 104
CAUTION:
To avoid storage networking issues and potential loss of data associated with
duplicate WWNs on a FC SAN fabric, plan carefully when allowing Virtual Connect to
assign server blade WWNs so that the configured range of WWNs is used only once within
the environment.
Multiple network connections for a server port
Server port connections to virtual networks are defined on the Define Server Profile screen (on page
Previous to Virtual Connect Manager v1.31, each server port could only be connected to a single virtual
network. With v1.31 and higher, each server port can be connected to multiple virtual networks, each
using a unique server VLAN ID for virtual network mapping.
To use this shared server links feature, under Ethernet Network Connections, select Unassigned or a
network name, click the down-arrow, and then select Multiple Networks from the drop-down list. This
option is available only if the 'Map VLAN Tags' option is selected on the Ethernet Settings (Advanced
Settings) screen (on page
). When the 'Multiple Networks' option is selected, a separate window is
displayed to enable the defining and editing of virtual networks and VID mappings.
Defining server VLAN mappings
Forced VLAN Mappings
If the 'Force same VLAN mappings as Shared Uplink Sets' option is selected, server VLAN mappings are
the same as the shared uplink set VLAN mappings. Users can choose only from a list of shared uplink sets
when selecting Multiple Networks. After selecting a shared uplink set from the drop-down list, a list of
vNets that belong to the chosen shared uplink set is displayed. Next to each network is a checkbox to
allow the user to select or deselect individual networks to be connected to the server. If the shared uplink
set has more than 28 networks, only the first 28 are selected to enforce the maximum number of VLAN
mappings supported on a server.
The server VLAN mappings are the same as those used on the shared uplink set, which are automatically
displayed and cannot be changed. One of the networks can also be selected as the 'Untagged' network,
which means that untagged packets are placed on that vNet, and the VC-Enet module also transmits
untagged to the server for that network.
The 'untagged' network defaults to be the 'Native' network, but it does not have to be the same as the
'Native' network on the shared uplink set. In fact, each server port can designate a different untagged
network. The external VLAN mapping is ignored when the network is untagged.