Users Guide

• Replace a failing or failed server by moving the I/O identity of the server to another spare server.
• Deploy additional servers to increase the computing capability during high workload.
The Deployment portal allows you to perform the following tasks that are required to manage the virtual I/O identity of a server:
• Create virtual I/O pools
• Create compute pools
• Deploy a server
• Reclaim the virtual I/O identity of a server
• Replace a server
Overview of Stateless Deployment
The steps that you must perform to deploy a device conguration template with virtual I/O attributes on target devices are as
follows:
1. Create a device conguration template — Use the Create Template task in the Common Tasks pane to create a device
conguration template. You can choose to create the template from either a conguration le or a reference device.
2. Edit the device conguration template — Select the template from the Templates pane, and edit the desired conguration
attributes displayed in the right pane.
3. Create Virtual I/O Pool — Use the Create Virtual I/O Pool task in the Common Tasks pane to create a pool of one or more
virtual I/O identity types. The virtual I/O identity pool is used to assign virtual I/O identities to the target devices.
4. Create Compute Pool — Use the Create Compute Pool task in the Common Tasks pane to create a group of servers that
you want to use for a specic purpose. You can associate a device conguration template and virtual I/O pool to the compute
pool.
5. Deploy the device conguration template on target devices — Use the Deploy Template task in the Common Tasks pane to
deploy the device conguration template and virtual I/O identities on the target devices.
Related links
Getting started for device conguration deployment
Creating a device deployment template
Editing a device deployment template
Creating a Virtual Input-Output Pool
Creating a Compute Pool
Deploying a device conguration template—Stateless deployment
Virtual Input-Output Pools
A virtual I/O pool is a collection of one or more virtual I/O identity types that are required for network communication. A virtual I/O
pool can contain a combination of any of the following virtual I/O identity types:
• Ethernet identity which is dened by the Media Access Control (MAC) address. MAC addresses are required for Ethernet (LAN)
communications.
• Fibre Channel (FC) identity which is dened by the World Wide Node Name (WWNN) and World Wide Port Name (WWPN). A
WWNN identity is assigned to a node (device) in an FC fabric and may be shared by some or all ports of a device. A WWPN
identity is assigned to each port in an FC fabric and is unique to each port. WWNN and WWPN identities are required to support
boot-from-SAN and for data access using FC and Fibre Channel over Ethernet (FCoE) protocols.
• iSCSI identity which is dened by the iSCSI Qualied Name (IQN). IQN identities are required to support boot-from-SAN using
the iSCSI protocol.
OpenManage Essentials utilizes the virtual I/O pools to automatically assign virtual I/O identities to the device conguration template
that is used for deploying a server.
NOTE: A virtual I/O pool can be associated with one or more compute pools.
142