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

•
Fibre Channel boot from SAN parameters
•
Logical serial numbers
An important benefit of Virtual Connect 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 network interface (NIC) or host bus adapter (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 Virtual Connect installation, the LAN and SAN administrators are still responsible for defining
the networks, subnets, and storage LUNs that the servers will use, but they no longer have to be
involved in every server-centric change. Once implemented, Virtual Connect 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 Virtual Connect resources, HP provides options for both small and large
Virtual Connect environments.
HP Virtual Connect Manager
Virtual Connect Manager is a simple web console built into the firmware of each Virtual Connect
Ethernet module, and is designed to configure and manage a single Virtual Connect Domain. A
typical environment is up to 4 Virtual Connect Domains that have no plans 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 Virtual Connect 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 very beginning to get the most benefit. VCEM is designed for the following
environments:
•
Medium to large HP BladeSystem configurations that use Virtual Connect CMS
•
HP BladeSystem environments that extend to multiple locations
•
Organizations that require centralized control of server-to-network connectivity
•
Organizations that require rapid server workload assignment and recovery across enclosures.
Understanding VCEM operations
VCEM aggregates network connection management and workload mobility for hundreds of Virtual
Connect Domains and thousands of blade servers into a single console. This scalable solution
delivers advanced Virtual Connect management that builds upon and integrates with other HP
management tools, including HP Systems Insight Manager, Virtual Connect hardware, and the
Onboard Administrator integrated into HP BladeSystem c-Class enclosures. VCEM can be installed
in a variety of configurations that include a physical stand-alone console, as a plug-in to System
Insight Manager, and as a virtual server guest.
The majority of VCEM operations are accessed through a dedicated homepage which includes
the following core tasks:
•
Discover and import existing VC Domains without system downtime.
•
Aggregates individual Virtual Connect address names for LAN and SAN connectivity into a
centrally administered VCEM address repository.
Managing HP Virtual Connect 11