HP Virtual Connect Enterprise Manager Software - Manual (Page 13)

To establish server connections to LANs and SANs, VC uses server connection profiles in
combination with dynamic pools of unique media access control (MAC) addresses and world wide
names (WWN). A VC server profile is a logical grouping of server connection attributes that can
be assigned to any bay in a BladeSystem enclosure. When assigned to an enclosure bay, the
server in that bay assumes the attributes of the server profile which can include:
•
MAC addresses for all NICs
•
WWNs for all HBAs
•
Fibre Channel boot from SAN parameters
•
Logical serial numbers
An important benefit of VC is that server connection profiles and associated attributes are assigned
to BladeSystem enclosure bays and not hard wired to individual servers. The physical server in
each bay uses the MAC and WWN assignments in the associated server connection profile instead
of its default burned-in NIC or HBA addresses. Using this model, even if a server is replaced, the
MAC and WWN assignments for the enclosure bay remain constant, and the change is invisible
to the network.
During VC installation, the LAN and SAN administrators are still responsible for defining the
networks, subnets, and storage LUNs the servers will use, but they no longer must be involved in
every server-centric change. Once implemented, VC allows system administrators to be more
self-sufficient, so they can add, replace, and modify servers in minutes without affecting LAN and
SAN availability or burdening network administration staff.
Managing HP Virtual Connect
To configure and manage VC resources, HP provides options for both small and large VC
environments.
HP Virtual Connect Manager
VCM is a simple web console built into the firmware of each VC Ethernet module, and is designed
to configure and manage a single VC Domain. A typical environment is up to 4 VC enclosures
that you do not plan to expand further.
HP Virtual Connect Enterprise Manager
VCEM is HP’s primary application that centrally manages server connections and provides workload
mobility for up to 250 VC Domains and thousands of servers across the datacenter.
A typical environment involves BladeSystems with more than one rack of enclosures. VCEM is
designed to scale as the infrastructure grows and simplifies the addition of new and bare metal
enclosures. Small configurations with goals to expand beyond a single server rack should use
VCEM from the beginning to get the most benefit. VCEM is designed for the following environments:
•
Medium to large HP BladeSystem configurations using VC CMS
•
HP BladeSystem environments extending to multiple locations
•
Organizations requiring centralized control of server-to-network connectivity
•
Organizations requiring rapid server workload assignment and recovery across enclosures.
Understanding VCEM operations
VCEM aggregates network connection management and workload mobility for hundreds of VC
Domains and thousands of blade servers into a single console. This scalable solution delivers
advanced VC management that builds on and integrates with other HP management tools, including
HP Systems Insight Manager, VC hardware, and the Onboard Administrator integrated into HP
BladeSystem c-Class enclosures. VCEM can be installed in a variety of configurations that include
Managing HP Virtual Connect 13