 |
» |
|
|
|
Following are the new features in Logical Server Management
for this release. For more information about these features, see the online help
for Virtualization Manager. Expanded Technology Support Architecture: Integrity blades You can
now create and manage logical servers on HP Integrity blade servers
(running HP-UX, Linux, and Windows), in addition to HP ProLiant servers
(running Linux and Windows). Platform Type: Hyper-V You can now create
logical servers on Hyper-V hypervisors, in addition to ESX Virtual
Machine hypervisors and Virtual Connect server blade platform types. HP Insight Recovery This release contains
support for HP Insight Recovery, which provides an automated disaster
recovery solution for logical servers by allowing applications to
be recovered at a remote site in minutes in the event of a site-wide
disaster at the primary site. Insight Recovery is an add-on product
based on HP Insight Dynamics — VSE, and is a plug-in to HP
SIM. A logical server that is managed by Insight Recovery displays
this icon ![[tornado]](./img/tornado.png) in the logical
server compartment in the Virtualization Manager Visualization tab.
Logical servers that are marked DT Protected (for
disaster tolerant) are configured on the primary site. Those marked
with DT Protected-DT Disabled are configured
on the recovery site. HP Insight Orchestration This release
contains support for Insight Orchestration, which provides life cycle
services for groups of physical or virtual servers. Insight Orchestration
allows automated operating system provisioning of a logical server
with both boot and data storage. In addition, it provides you with
access to the logical server utility as well as an allotment of resources,
such as servers, and provides a set of templates that can be used
as blueprints for server provisioning. A logical server that is managed by Insight Orchestration displays
this icon ![[LSU]](./img/lsu.png) in the logical server compartment
in the Virtualization Manager Visualization tab. Multiple Networks (VLAN Trunking) This
release contains read-only support in Virtual Connect blade logical
servers for multiple networks. Multiple networks are a list of networks,
some of which might be VLANs, assigned to a single network port. Assigning
multiple networks to a single network port is also called VLAN trunking. Note that you can import a Virtual Connect server blade that
has a multiple network port, but you cannot modify or delete the multiple
network port using logical server management operations.
Storage Validation and Storage Pools Storage validation This release allows
you to optionally validate your Virtual Connect blade logical server
storage configuration by performing on-demand checking of Enterprise
Virtual Array (EVA) and Modular Smart Array (MSA) storage. Validation allows you to identify and correct errors by confirming
the existence of each storage WWN and LUN ID pair. It also compares
each storage volume attribute by displaying the user defined value
with the actual value. See “Configuring HP SIM for SAN Storage Validation” for important setup information. Storage pools Each logical server can
have multiple storage pool entries. When you add a new storage pool
entry to a logical server, the next HBA port is activated and the
server WWN is programmed into it. Multiple logical servers can share the same storage pool entry.
After creating a logical server and specifying a storage pool entry
as the storage configuration, when you activate the logical server
a profile is allocated, server WWNs from the GUID server from all
pool entries are programmed into the profile, and the profile is assigned
to a server blade. When you create or modify a storage pool entry, you can specify
the number of logical servers that can share the pool entry. Storage
pool entries that contain boot volumes are not shareable. Modify storage definition with pre-presented LUNs This release allows you to modify an inactive Virtual Connect
blade logical server storage configuration to add a new LUN to the
list of storage volumes. (Note that you cannot modify the size of,
or “grow,” an existing LUN.) This feature is useful if applications running on the logical
server require additional storage, or new applications are added to
the logical server. In addition, many operating system deployment
tools (such as RDP) require that only one path be visible when installing
the operating system. This allows you to create the logical server
with only the boot volume, then later modify the logical server to
add a data volume. In the previous release, you could not modify your Virtual Connect
blade logical server storage configuration after activation without
first deactivating and removing the allocated server WWNs (VC profile),
reallocating the server WWNs, and asking the storage administrator
to correct access information for the original LUNs as well as the
newly added LUN.
Logical Server Moves In the previous release
of VSE, moving a logical server created a list of target hosts that
were required to exactly match the filter criteria (for example, number
of CPUs, CPU frequency, and amount of memory). In this release, you can choose a target host that is an exact
match (best fit) to the source logical server, and you can also select
a target host (acceptable fit) that may have been shown in the Rejected Target Hosts table in the previous release. This
acceptable target host is shown in the Target Hosts table with inverted orange triangle symbols or yellow triangle symbols
in the table columns to denote soft errors. Hovering over these symbols
displays a message that allows you to decide if you want to override
the filter criteria by selecting the target host. This release also allows you to choose the type of move operation
you want performed using a drop-down menu on the Move: Assign Logical
Servers to Target Hosts screen. See “Performing Actions that Affect Logical Servers” for
a description of available move types. Easier Imports of Logical Servers This
release lifts restrictions on importing Virtual Connect server blades
and virtual machines to a logical server. The following changes to the import operation have been made
in this release: The VM guest or Virtual Connect server blade does
not need to be provisioned with an operating system before it is imported. The VM guest or Virtual Connect server blade can have
multiple IP addresses configured. For Virtual Connect blade logical servers, Fibre Channel
paths can be set to disabled, in addition to primary or secondary. For Virtual Connect blade logical servers, LAN cards
can have a PXE boot setting of Use Bios.
Power Logical Server On or Off In this
release, you can use a menu selection to power on or off a virtual
machine or a server blade bay on which a logical server was activated
or moved. Status Enhancements Logical server job
status messages are now provided for Copy, Create, and Import logical
server operations, in addition to Activate, Deactivate, Delete, and
Move, which were included in the previous release. You can also specify
the refresh rate of the View Logical Server Job Status screen. In addition, status messages have been improved to provide more
detailed information. LSMUTIL Database Utility This release
contains enhanced support for lsmutil.pl, a perl
script that can be run from the command line or from a MS-DOS bat
file. This script reads information from the logical servers tables
in the VSE database. Based on the option selected, the script looks
up information in the tables or performs basic database operations,
such as creating and deleting logical servers tables in the VSE database.
You can also use this script to display the active and inactive logical
servers and shared storage pools in the logical servers tables. The LSMUTIL command is lsmutil --option. If you do not specify an option, the default option of --help is used, which lists the valid options for the LSMUTIL
script.
|
Printable version
