Hp virtual connect enterprise manager, Vcem operations – HP Virtual Connect Enterprise Manager Software User Manual
Page 14
HP Virtual Connect Enterprise Manager
VCEM is HP’s primary application for managing Virtual Connect environments. It provides centralized
group-based management for up to 250 Virtual Connect domains with the VCEM 6.0 release, administers
a total of 256K LAN and SAN addresses from a central pool, and enables server profile movement across
the datacenter.
Typical Environment
Multiple rack or distributed BladeSystem environments with more than one rack of enclosures and with plans
to expand. VCEM is designed to scale as the infrastructure grows and simplifies the addition of new and
bare metal enclosures. Small environments with goals to expand should use VCEM from the very beginning
to get the most benefit.
•
Medium to large HP BladeSystem environments that use Virtual Connect.
•
BladeSystem environments that extend to multiple locations.
•
Organizations that require centralized control of server-to-network connectivity.
•
Organizations that require rapid server movement between enclosures.
For more information about Virtual Connect and Virtual Connect Manager, see the
HP Virtual Connect for
c-Class BladeSystem User Guide.
VCEM operations
VCEM aggregates Virtual Connect technology with a single console that aggregates the management and
control of multiple VC Domains into a single console. This intuitive solution delivers advanced Virtual Connect
management that leverages and integrates with other HP management tools, including HP SIM, 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 HP SIM 6.0 or later, and as a virtual machine.
VCEM presents its own dedicated homepage to perform the following core tasks:
•
Discover and import existing VC Domains.
•
Aggregate individual Virtual Connect address names for LAN and SAN connectivity into a centrally
administered VCEM address repository.
•
Create VC Domain Groups.
•
Assign and unassign VC Domains to VC Domain Groups.
•
Define server profiles and link to available LAN and SAN resources.
•
Assign server profiles to BladeSystem enclosures, enclosure bays, and VC Domain Groups.
•
Change, reassign, and automatically failover server profiles to spare servers.
•
Rapidly install new bare-metal HP BladeSystem enclosures by assigning to a VC Domain Group.
14
Introduction