Administrator Guide

6 PowerEdge MX7000 Server Configuration using OME Modular
Stage 1: Please refer to OpenManage Enterprise Modular User’s Guide for
wizard/workflow details on below steps:
❖ Create a server configuration Template either via “Reference Device” or “Import
Template”.
❖ Create an Identity Pool with Ethernet MAC addresses, iSCSI MAC addresses,
FCoE identity and FC identity as required.
❖ Create Network with VLANs as required.
Stage 2: Edit the Template created in stage 1 and associate it with the Identity Pool and
VLANs as required.
Stage 3: Now the Template is ready to be deployed. As described above, we have two
choices here, deploy the Template directly to a server as a “device profile” or attach it to
a slot as a “slot profile”.
Stage 4 (Device Profile): A Template can be deployed as a “device profile” directly to
the server as in box 4 → box 5 in the Figure 1. After a successful deployment, following
options are available for further lifecycle management.
❖ Figure 1 (box 5 → box 6): Move server:
o Physically move the server to another slot in the same chassis: server
will retain the MAC/WWNs. OME Modular Identity Pools usage will
reflect the updated slot.
o Physically move the server to a different chassis in the same domain:
server will retain the MAC/WWNs but because of a known issue in
OME Modular, the Identity Pools usage does not reflect the server
movement and also shows the provisioned MAC/WWNs as available.
Please refer to “FAQ and Recommended usage” section of this article
for more details. Note: It is assumed that the server moved to a slot
that does not have a slot-profile attached to it.
o Physically move the server to a different chassis not in the same
domain: server will retain the MAC/WWM unless the new chassis
domain it moved to does its own deployment. As OME Modular only
knows that the server moved, it will continue to show the Identity Pools
usage as assigned to the moved server, this will continue to be the
case until user performs a force reclaim via the REST API or the
automatic cleanup triggers (after 7 days of device removal). Note: It is
assumed that the server moved to a slot that does not have a slot-
profile attached to it.
❖ Figure 1 (box 5 → box 7): Detach profile: