HP Virtual Connect Flex-10 10Gb Ethernet Module for c-Class BladeSystem - Manual (Page 174)

Configuring the Virtual Connect domain using the CLI 174
• When iSCSI connections are used, Virtual Connect assigns a MAC address to each iSCSI connection
in the profile.
Assigned MAC addresses
The MAC address range used by the Virtual Connect domain must be unique within the environment. HP
provides a set of pre-defined ranges that are for use by VCM and do not conflict with server factory default
MAC addresses.
When using the HP-defined MAC address ranges, be sure that each range is used only once within the
environment.
Selecting VC-assigned MAC address ranges
When using VC-assigned MAC addresses, you can choose between using an HP pre-defined MAC address
range or using a user-defined MAC address range.
• HP pre-defined MAC address range (recommended). These pre-defined ranges are reserved and are
not the factory default on any hardware. There are 64 ranges of 1024 unique addresses to choose
from. Be sure to use each range only once within a data center.
1024 unique addresses might not be enough for a large configuration (multiple enclosures with many
Flex-10 NICs). If you plan a domain of this type, determine the number of MAC addresses you are likely
to use, and then select an option that provides the domain with sufficient MAC addresses.
• User-defined MAC address range. To avoid potential conflict with other hardware MAC addresses in
the environment, consider using a subrange of MAC addresses reserved by the IEEE for
locally-administered MAC addresses. Ensure that the range does not conflict with any Ethernet device
already deployed within the enterprise.
IMPORTANT: If you plan to use Insight Control Server Deployment for RedHat Linux installation
and also plan to use User- or HP-defined MAC addresses, you must import the enclosure and
assign profiles before running Insight Control Server Deployment.
NOTE: After any server profiles are deployed using a selected MAC address range, that range
cannot be changed until all server profiles are deleted.
Creating a network access group
Before VC 3.30, any server profile could be assigned any set of networks. If policy dictated that some
networks should not be accessed by a system that accessed other networks (for example, the Intranet and the
Extranet) there was no way to enforce that policy automatically.
With VC 3.30 and later, network access groups are defined by the network administrator and associated
with a set of networks that can be shared by a single server. Each server profile is associated with one
network access group. A network cannot be assigned to the server profile unless it is a member of the network
access group associated with that server profile. A network access group can contain multiple networks.
Up to 128 network access groups are supported in the domain. Ethernet networks and server profiles that are
not assigned to a specific network access group are added to the domain Default network access group
automatically. The Default network access group is predefined by VCM and cannot be removed or renamed.
If you are updating to VC 3.30 or later, all current networks are added to the Default network access group
and all server profiles are set to use the Default network access group. Network communication within the