Administrator Guide

4 PowerEdge MX7000 Server Configuration using OME Modular
Lifecycle and Best Practices of
Templates/Profiles/IO-Identities Deployment
There are two types of profile deployments. A profile deployed to a server directly
(referred as device profile deployment) and a profile attached to a slot which later gets
deployed to the inserted server (referred as slot profile).
Device profile:
• A profile created from a template is directly deployed on a server.
• Device profile deployment enables the server to retain any virtual identities
(MAC/WWNs) part of the profile when the server relocates to another slot
(assuming no slot profile is assigned) in the same chassis or a new chassis.
Device profile also supports migration of profile to allow rapid workload
recovery to a spare server in the domain (same chassis or another chassis in
the Chassis Group).
Slot profile:
• A profile created from a template is first attached to the slot and then later
deployed to the server inserted into the slot.
• Slot profile deployment enables the slot to own the profile and any virtual
identities (MAC/WWNs) part of the profile. Any server inserted into the slot is
guaranteed to get the same attached profile and virtual identities
(MAC/WWNs) deployed. This enables rip & replace of servers in the slot and
have the same attached profile (with MAC/WWNs) deployed on every new
server inserted into the slot.
What follows next is the process of creating templates, identity pools, VLANs and
deploying them as a device profile or slot profile. The below steps refer to numbers (0,
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 and 12) in Figure 1 to help navigate the various steps
applicable through the lifecycle of the profile deployment.