Administrator Guide

ManualsBrandsDell ManualsC SeriesPowerEdge MX7000

1 PowerEdge MX7000 Server Configuration using OME Modular

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/Virtual-

Identities(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

Summary of content (16 pages)

PAGE 1
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.
PAGE 2
Revisions Date Description 4/9/2020 Initial release version 1.
PAGE 3
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 ...................................................................................................................
PAGE 4
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.
PAGE 5
Figure 1: Lifecycle of Template/Profile/IO-Identity configuration 0 Start Create VLAN Create Template Create Identity Pool Identity Pool 1 Template Network (VLANs) 3 2 Edit Network Associate Pool to Template Decide on implementa tion Deploy to Server 5 Moved server to new (chassis/slot).
PAGE 6
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.
PAGE 7
o Detach profile can be performed via the server overview page (Overview → Configuration Profile → Detach Profile). Detach profile will force reclaim any provisioned MAC/WWNs from the server and remove all references to the profile. The reclaimed MAC/WWNs will be made available in the Identity Pool for new deployments. As the identities are moved back to the available pool, any new deployments to the same server in future will not guarantee same MAC/WWNs.
PAGE 8
server and insert it back without re-triggering the deployment template. o Remove (C 1) and insert a new server (C 2): Inserting a new server will trigger a fresh deployment of the same profile with same virtual identities (MAC/WWNs) to the newly inserted server.
PAGE 9
Deploying Profiles with Virtual Identities on MX7000 to Achieve Same Functionality as M1000e FlexAddress The important aspect of the M1000e FlexAddress was to have pre-assigned MAC/WWNs so that when a server is inserted into the slot its gets deployed with the pre-assigned MAC/WWNs. Since the identities (MAC/WWNs) are bound to chassis slots, they are persistent across Rip & Replace of servers and thus reducing the application/workload downtime.
PAGE 10
FAQ and Recommended usage - Do not override a device profile with a slot profile and vice versa: There are limited checks in the deployment wizard/workflows in the current release to block/fail any conflicting deployments, for example: It is highly recommended to not override a slot profile deployment with a device profile deployment and vice versa. Depending on the deployment use case, either a device profile or a slot profile should satisfy the requirement.
PAGE 11
- What are the possible states for Virtual Identities (MAC/WWNs) in Identity Pools? o Available: Indicates that the virtual identity value is not being used by any device. o Reserved: Indicates that the virtual identity value is reserved for deployment to a target device. Once OpenManage Enterprise Modular deploys the identity to the target device, and confirms that it was successfully applied on the device, it will change its state to Assigned.
PAGE 12
IOID112 The initiator properties of the Port are successfully configured. None. IOID113 Unable to configure the initiator properties of Port . IOID114 The target settings properties of the Port are successfully configured. Unable to configure the target settings properties of the Port . Make sure that the iSCSI or FCoE partition of the network port is enabled.
PAGE 13
then a physical removal and reinsertion of the server is required for the deployment of the attached profile to the server. This is a limitation in the current version and there is a plan to address it in the future version, please refer to “Preview of enhancements in the upcoming releases” section of this article. - Slot Profile: Deploying a slot profile to MX840c: As MX840c occupies 2 slots, it can only be inserted into slots (1-2, 3-4, 5-6, 7-8).
PAGE 14
- Device Profile: Associate to Slot: This option was intended for server part replacement in the context of device profile. Because of a known issue, this option does not fully support the part replacement use case and hence it is not recommended to be used. - Device Profile: NIC part replacement: In some cases it may be required to replace a server NIC card with an identical NIC to resolve hardware issues.
PAGE 15
Preview of enhancements in the upcoming releases OME Modular 1.20.00 : Following are some of the bug fixes/enhancements in this release: - Ability to physically move a server with a device profile deployed to a different chassis in the same domain: The enhanced behavior allows movement of the server with a device profile to a different chassis in the same domain and continue to report the virtual identities (MAC/WWNs) as assigned to the server as expected.
PAGE 16
- Edit Template and propagate changes to all deployed profiles: This feature allows to make changes to existing attributes and/or include new attributes on top of existing attributes in the Template. This enables administrators to fix any problems with existing deployment and also add new functionality in increments.