HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 97)

Virtual Connect networks 97
You can tunnel VLAN tags and map VLAN tags in the same domain. As of VC 3.30, tunneling and mapping
is configured at the network level, not at the domain level. Server VLAN tunneling is supported only on
networks with dedicated uplinks and cannot be used with shared uplink sets.
Server VLAN tagging support
When the 'Force server connections to use same VLAN mappings as shared uplink sets' check box is
selected, server ports connected to multiple VC Ethernet networks are forced to use the same VLAN mappings
as those used for the corresponding shared uplink sets. This action forces all server connections mapped to
multiple networks to be linked to a shared uplink set. Server administrators cannot override this selection
when creating or editing a profile. When this check box is selected, server network connections can only be
selected from a single shared uplink set.
When the 'Force server connections to use same VLAN mappings as shared uplink sets' check box is not
selected, server network connections can be selected from any VC Ethernet network and the external VLAN
ID mappings can be manually edited. However, administrators must ensure that no server connection VLAN
ID conflict exists.
The 'Force server connections to use the same VLAN mappings as shared uplink sets' check box can be
selected if no server profile connections are assigned to multiple networks that are not linked to a shared
uplink set.
VLAN Capacity
When creating a new domain in VC 3.70 or higher, the option to select Legacy VLAN Capacity mode is
disabled and reverting from Expanded VLAN Capacity mode to Legacy VLAN Capacity mode is not
allowed. Domains containing the Legacy VLAN Capacity mode setting that are upgraded from VC 3.30 are
upgraded to Expanded VLAN Capacity mode as part of the VC 3.70 or higher firmware upgrade. To
maintain compatibility with VC 3.30 domains that have Legacy VLAN Capacity mode enabled, the VCM CLI
maintains the current functionality for the VLAN mode. This also allows the use of existing scripts that
manipulate the VLAN capacity. Enabling expanded VLAN capacity on a domain is non-disruptive.
Expanded VLAN Capacity mode allows up to 1000 VLANs per domain. The number of VLANs per shared
uplink set is restricted to 1000. In addition, up to 162 VLANs are allowed per physical server port, with no
restriction on how those VLANs are distributed among the server connections mapped to the same physical
server port. There is also a limit of 162 VLANs per server connection. However, you must take care not to
exceed the limit per physical server port. For example, if you configure 150 VLAN mappings for a server
connection (FlexNIC-a) of a Flex-10 physical server port, then you can map only 12 VLANs to the remaining
three server connections (FlexNIC-b, FlexNIC-c, and FlexNIC-d) of the same physical server port. If you
exceed the 162 VLAN limit, the physical server port is disabled and the four server connections are marked
as Failed. Virtual Connect limits the number of private networks to 128 per domain.
Multiple Networks Link Speed Settings
When using mapped VLAN tags (multiple networks over a single link), these settings are used for the overall
link speed control. Select the checkbox next to each item to set the value.
These settings affect only newly created profiles.
Versions of VC prior to v4.01 used the "preferred speed" to control bandwidth allocation. When existing
profiles are upgraded to VC v4.01, the "maximum speed" from the network is set automatically on the
connection. If no maximum speed was configured prior to the upgrade, then the maximum speed will be 10
Gb for Ethernet connections and 8Gb for FCoE connections. The pre-4.01 behavior can be retained by
setting "maximum speed" to the same value as "preferred speed".