Operating Environment Software User Manual

◦ Power management settings such as capping and regulation
◦ WOL settings
◦ WSMAN settings
◦ UID LED settings
◦ Network settings (LAN, SSH and web ports)
◦ Access settings (telnet/ssh/web)
◦ Inactivity timeouts
◦ DNS settings
◦ Time and date
◦ Serial port settings
◦ Logs
Defining portability groups
Use the Modify→Logical Server Portability Groups… screen to define a greater range of mobility
for logical servers. When you create a logical server and include it in a particular portability group,
you can potentially move the logical server to any target system within the portability group (as
long as you choose storage and a network that are visible across all targets) without regard to the
target’s underlying technology.
Logical server resource constraints, for example, CPU and memory requirements and network/SAN
connectivity, are evaluated solely within the context of the portability group with which the logical
server is associated.
There are two classes of portability groups: Default and User-defined.
Default portability groups:
• Each Virtual Connect domain group
• Each Operations Orchestration Workflow physical server
• All ESX Virtual Machine Hosts
• All Hyper-V Virtual Machine Hosts
• All HP Integrity VM Virtual Machine Hosts
(Optional) User-defined portability groups:
• A single Virtual Connect Domain Group
• A set of ESX Virtual Machine Hosts
• A set of Hyper-V Virtual Machine Hosts
• A set of HP Integrity VM Virtual Machine Hosts
• A set consisting of a single Virtual Connect Domain Group and a set of ESX Virtual Machine
Hosts
A logical server created in this type of portability group is a cross-technology logical server.
Specify a unique name for your user-defined portability group. The default portability group names
are displayed on the Manage Portability Groups screen so you can avoid selecting one of those
names for your user-defined portability group.
Defining portability groups 35