Stimmen - 0, Durchschnittliche Bewertung: 0
(
)
)
|
Dieses Gerät hat auch andere Anweisungen:
Software - HP Virtual Connect Enterprise Manager BLc3000 24x7 Support No Media 1-encl Lic (940.96 kb)
Anleitung Zusammenfassung
VCEM Operation Model and Key Concepts
VCEM provides a central point of server profile management for HP BladeSystem Virtual Connect
domains.
Virtual Connect (VC) technology offers substantial benefits to System/LAN/SAN Administrators by
providing unique features like server profile and FlexNIC. Virtual Connect configures LAN/SAN
connectivity of the server blades inside HP BladeSystem enclosures. A Virtual Connect server profile is a
logical grouping of server connection attributes that can be assigned to any bay within a BladeSystem
enclosure. When assigned to an enclosure bay, the server in that bay assumes the attributes of the
server profile. Each HP BladeSystem enclosure equipped with Virtual Connect is managed by VC’s
embedded Virtual Connect Manager (VCM). VCM allows IT Administrators to stack up to 4 enclosures to
form a single VC Domain.
VCM and VC stacking technology can have some operation overhead when more enclosures are
deployed. VCEM is the product to address these overheads. You can leverage VCEM benefit when you
want to deploy two and more enclosures. The demo setup of this white paper uses two HP c7000
enclosures.
The following table is a comparison of managing multiple Virtual Connect enclosures using VCM vs.
VCEM
Using VCM
Using VCEM
Need to access individual VC domain to
Manage server profiles from multiple domains with
configure and manage server profiles
a centralized VCEM console.
Server Profile mobility is contained in a Virtual
Server profile can be applied, moved and copied
Connect domain, which is 1 HP BladeSystem
across multiple enclosures. VCEM can control up to
enclosure without VC stacking and up to 4
250 Virtual Connect Domains, 1000 BladeSystem
enclosures with VC stacking
Enclosures. VCEM allows profile movement from
one VC domain to another VC domain within the
same or different domain group
Without a central pool allocation, Administrators
VCEM assigns MAC/WWN addresses to various
must plan accordingly to ensure each VC
VC domains from a central pool so duplicate
domain has a unique range of MAC/WWN
MAC/WWN addresses won’t occur.
address pool assignment so we don’t have
duplicate addresses when deploying more VC
domains.
The same LAN/SAN configuration must
The existing LAN/SAN VC configuration will be
repetitively be provisioned when trying to set up
automatically synched to new enclosures when they
a new enclosure.
are imported into the same VCEM domain group.
If there is a change to VC LAN/SAN
Any change to the LAN/SAN VC configuration
configuration, such as adding a new VLAN into
needs to be only done once at an enclosure and the
an existing VC network trunk, the same
change will be synched to all the enclosures in the
configuration has to be applied to each
same VCEM domain group.
enclosure separately by logging into each VC
domain.
It’s also important that readers understand the implementation model of VCEM when it controls multiple
VC domains and there are some important concepts associated with VCEM deployment.
Concepts
Notes
A VC domain defines a BladeSystem LAN/SAN connections and
VC Domain
server profiles created for the servers inside the enclosure.
4
...Dieses Handbuch ist für folgende Modelle:
Software - HP Virtual Connect Enterprise Manager including 1yr 24x7 Support Flexible Qty c7000 Enclosure Lic (6.87 mb)
Software - HP Virtual Connect Enterprise Manager including 1yr 24x7 Support Single c7000 Enclosure Lic (6.87 mb)