Dell MX7000 User Manual
Whitepaper
PowerEdge MX7000 Server Configuration using OpenManage Enterprise Modular
Abstract
The purpose of this document is to provide the following information:
1.The basic lifecycle and best practices of MX7000 Templates/Profiles/VirtualIdentities(MAC/WWNs) deployment
2.Deploying profiles with virtual identities on MX7000 to achieve same functionality as M1000e FlexAddress
3.FAQ and Recommended usage
4.Preview of enhancements in the upcoming releases
This document will not cover GUI wizard/workflow details, please refer to the following documents for more details on how to use GUI workflows and wizards in configuring the Templates/Profiles/Virtual-Identities(MAC/WWNs):
•OpenManage Enterprise Modular User’s Guide: https://topics- cdn.dell.com/pdf/openmanage-enterprise-modular-v10001-poweredge- mx7000_users-guide4_en-us.pdf
•Advanced Server Configuration in Dell EMC OpenManage Enterprise 3.0 : https://downloads.dell.com/manuals/all- products/esuprt_software/esuprt_ent_sys_mgmt/dell-openmanage-enterprise- v32_white-papers5_en-us.pdf
•PowerEdge MX7000 Templates and Profiles : https://downloads.dell.com/manuals/common/dellemc_mx7000_templates_profile s.pdf
1 PowerEdge MX7000 Server Configuration using OME Modular
Revisions
Date |
Description |
|
|
4/9/2020 |
Initial release version 1.1 |
|
|
Acknowledgements
This paper was produced by the following:
Name
Prakash Nara |
Dell EMC |
|
|
|
|
|
|
|
|
|
|
2 PowerEdge MX7000 Server Configuration using OME Modular
Contents |
|
Abstract.......................................................................................................................................... |
1 |
Lifecycle and Best Practices of Templates/Profiles/IO-Identities Deployment................... |
4 |
Deploying Profiles with Virtual Identities on MX7000 to Achieve Same Functionality as |
|
M1000e FlexAddress................................................................................................................... |
9 |
Preview of enhancements in the upcoming releases ........................................................... |
15 |
3 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.
4 PowerEdge MX7000 Server Configuration using OME Modular
Figure 1: Lifecycle of Template/Profile/IO-Identity configuration
0
Start
Create
Identity Pool
Identity Pool
1
Associate Pool
to Template
Deploy to Server
5 Profile deployed to server as
a device profile
Moved server to |
Move |
|
server |
||
|
new (chassis/slot).
Server retains 6 MAC/WWNs
7 |
|
Detach |
|
profile |
|
MAC/WWNs |
|
|
reclaimed from |
|
|
|
|
|
server |
|
|
8 |
Profile with |
|
Migrate |
|
profile |
||
MAC/WWNs moved |
|
||
|
|
||
|
from old server |
|
|
|
to new server |
|
|
|
Create |
|
|
Create |
|
|
|
|
|||
|
Template |
|
|
VLAN |
|
|
|
|
|
|
|
Template |
|
Network (VLANs) |
|||
2 |
|
3 |
|||
|
Edit |
|
|
|
|
|
|
|
|
||
|
Network |
|
|
|
|
|
|
|
Update LANs in |
|
|
4 |
|
|
|||
|
Template |
|
|||
Now Template is |
|
||||
associated with |
|
|
|
||
|
|
|
|||
IO Pool and VLANs |
|
|
|
||
Decide on |
|
|
|
||
implementa |
|
|
Attach |
||
|
|
||||
tion |
|
||||
|
To Slot |
||||
|
|
|
|
||
|
|
|
|
|
|
9
Attached to a chassis slot
Insert server in empty slot OR Remove existing server and insert new server
Profile deployed to server
10 as slot profile
Move
server
Moved server to new (chassis/slot).
11 Server drops MAC/WWNs
Detach |
|
|
Profile |
|
Removes the profile |
|
|
|
|
|
from slot, further |
|
|
steps needed to |
|
|
12 cleanup |
5 PowerEdge MX7000 Server Configuration using OME Modular
Loading...