
Dell Technologies PowerEdge MX Platform: Backing Up and Restoring the MX Platform
Fri, 09 Dec 2022 20:24:42 -0000
|Read Time: 0 minutes
An essential part of any data center disaster recovery plan is the ability to back up and restore the infrastructure. As a best practice, logs, server settings, routing information, and switch configurations should be backed up, with several copies secured in multiple locations.
The Dell Technologies PowerEdge MX Platform OME-M 1.40.00 release includes a significant new addition to the backup and restore feature: SmartFabric settings are now included.
This blog describes the full network backup and restore process, with emphasis on the SmartFabric settings and complete IOM startup.xml configuration.
Backing up the MX7000 chassis
In the following scenarios, you might need to restore the MX7000 chassis:
- The chassis was misconfigured
- The MX platform is unresponsive or malfunctioning
- Configurations were deleted due to disaster or human error
Note: If the MX chassis is in a MultiChassis Management (MCM) group, the backup will only be performed on the lead chassis. Member chassis do not need to be backed up because they inherit the configuration from the lead chassis.
MX Chassis, OME-M, and SmartFabric settings and configurations
MX platform backups include the following configurations and settings:
- Application settings
- Setup configuration
- Power configuration
- Chassis network configuration
- Local access configuration
- Location configuration
- Slot configuration
- OME Modular network settings
- User's settings
- Security settings
- Alert settings
OME-M 1.40.00 introduces the following:
- System configuration
- Templates
- Profiles
- Identity pools and VLANs
- Catalogs and baselines
- Alert policies
- SmartFabric
- MCM configuration
Back up the MX platform
The OME-M Chassis Backup wizard includes chassis settings and configurations, but it does not include the I/O Modules (IOMs) configuration. Let’s get started by backing up the IOM configurations manually through the CLI.
Manual backup of IOM configuration provides a backup of the running configuration. The running configuration contains the current OS10 system configuration and consists of a series of OS10 commands in a text file that you can view and edit with a text editor. Copy the configuration file to a remote server or local directory as a backup or for viewing and editing.
- In the CLI, run the following command to manually save each IOM switch configuration:
OS10# copy running-configuration startup-configuration
- Back up the startup file to the local directory or on external resources such as an TFTP server, an FTP server, or a USB drive.
In the example below, the configuration is saved on a local directory of the switch by running the following CLI:OS10# copy config://startup.xml config://backup-3-22.xml
- Access the MX lead chassis Overview page and click More Actions > Backup.
The Chassis Backup wizard is displayed. - On the Introduction page, review the settings that are included in the backup file and click Next.
The Backup File Settings page is displayed. - In Backup File Location, select the Share Type where you want to store the chassis backup file.
The available options are CIFS and NFS.
In this example, NFS is selected. Therefore, the NFS server should be preconfigured and the network connection should be tested before starting the backup process. - Enter the Network Share Address and the Network Share FilePath name of the backup file after a forward slash. For example /MXbackup
The Network Share Address is the NFS server NIC IP. The Network Share FilePath must be predefined on the NFS server, the file path, or the folder where the backup file will be saved. - Enter a name for the Backup File.
In this example, MXbackup-Feb is entered. - (Optional) Select Test connection. If the MX chassis and NFS server are in the same network, you can skip this step.
- (Optional) To allow users to include passwords while backing up the chassis, select Sensitive Data.
For more information about sensitive data, see Chassis Backup and Restore. - In Backup File Password, enter a password in the Encryption Password and Confirm Encryption Password textboxes.
The backup file is encrypted and cannot be edited. Only authorized users can retrieve and restore the file on the chassis. Provide the password and secure it in a safe place.
Note: The password must be 8 to 32 characters long and must be a combination of an uppercase, a lowercase, a special character (+, &, ?, >, -, }, |, ., !, (, ', ,, _, [, ", @, #, ), *, ;, $, ], /, §, %, =, <, :, {, I) , and a number.
- In the Ethernet Switch Backup Instructions, select the check box to confirm that you have manually saved the Ethernet switch backup settings.
For more detailed information about all Ethernet switch CLI settings, see CLI commands not part of chassis backup.- When the MX7000 chassis is in SmartFabric mode, the backup process does not include some switch settings.
- In Full Switch mode, the chassis backup process does not include any switch settings.
- To start the backup, click Finish.
- (Optional) To view the progress of the backup operation:
- Click Monitor > Jobs.
- Select the appropriate job and click View Details.
Available information includes current task status, percentage complete, elapsed time, and much more.
Restore the MX platform
This section describes the steps to restore an MX chassis and the IOM configuration.
You can use the OME-M GUI to restore the MX chassis working configuration with the backup file we created in the previous section.
The GUI doesn’t restore the IOM configuration, so you can manually restore the IOM configuration through the CLI.
Before you start the restore operation, make sure you have network access to the location where the backup file has been saved.
Restore the system
As a best practice, verify network connectivity to the location where the backup file has been saved.
You can restore the chassis through the OME-M GUI. The GUI doesn’t restore the IOM configuration, so the IOM configuration must be restored manually through the CLI.
- From the lead chassis, open the OME-M GUI and browse to Overview > More Actions > Restore.
The Introduction page displays. - Read the process and click the Learn More link in point 5 (shown in the figure above) to see more information about the Ethernet switch restore.
Note: Do not click Next. The Ethernet switch configuration must be manually restored before proceeding to the next step in the restore wizard. - Access the MX IOM CLI of each switch and restore the Ethernet Switch configuration.
The IOMs can be restored manually from the local directory on the switch or from external resources such as an TFTP server, an FTP server, or a USB drive. In this example, the IOMs manually restore through the CLI from the local directory on the switch.
In the CLI, run the following command:OS10# copy config://backup-3-22.xml config://startup.xml
OS10# reload
Proceed to reboot the system? [confirm yes/no]:yes
System configuration has been modified. Save? [yes/no]:no
Caution: Reload the IOMs immediately after restoring the startup configuration, because the running configuration is automatically written to the startup.xml every 30 minutes. Reloading the IOM immediately after each startup configuration restore avoids the startup.xml being overwritten.
- After the IOMs are restored and reloaded successfully, resume the restore process in the OME-M GUI. Click Next on the Introduction page.
The Upload File page displays. - Enter the restore file location details and enter the encryption password.
- In the Restore File section, enter the appropriate information.
Field
Input
Share Type
Select the share type where the configuration backup file is located.
In our example, since we selected the NFS server option for our backup, select NFS.
Network Share Address
Provide the NFS server NIC IP.
Network Share Filepath
Enter the same Network Share Filepath used for the backup file, including a forward slash: /MXbackup
Backup Filename
Type the Backup Filename with extension as shown in the figure above: MXbackup-Feb.bin.
- In the Restore File Password section, provide the same Encryption Password used during the backup process. The encryption password prevents unauthorized access.
- In the Restore File section, enter the appropriate information.
- To validate the chassis connectivity with the NFS server or location where backup file is saved, click Validate.
After the validation completes successfully, the Optional Components section is displayed.
- (Optional) On the Optional components page, you can choose to restore files on the selected components.
The following table provides details about the available options:Component
Description
Restore File Validation Status
Displays the validation status of the restore files
- Backup and restore chassis firmware version
Note: The restore chassis firmware version must match the firmware version that was installed when the backup file was created. - Backup and restore chassis service tag information
- The role of the backup chassis and the restore chassis
Optional Components
Displays the components that you can select for the restore operation.
Mandatory Components
Displays mandatory components, if applicable.
A restoring chassis that is in the MCM group is a Mandatory Component. Mandatory components restore automatically in the restore process.
Unavailable Components
Displays all other components that were not backed up during the backup process and are therefore unavailable for the restore operation.
- Backup and restore chassis firmware version
- Click Restore to start the chassis restore process.
- (Optional) To view the progress of the restore operation:
- Click Monitor > Jobs.
- Select the appropriate job and click View Details.
Available information includes current task status, percentage complete, elapsed time, and much more.
Notes:
- The restore process may take several hours, depending on the network settings and configuration.
- Once the MCM lead chassis has been restored, set the backup lead manually by assigning a backup lead chassis.
Resources
Dell Technologies PowerEdge MX7000 Networking Deployment Guide
Dell Technologies OME-M for PowerEdge MX7000 Chassis User’s Guide
Dell Technologies PowerEdge MX7000 Networking Interactive Demos
Related Blog Posts

Dell Technologies PowerEdge MX with Cisco ACI Integration
Thu, 09 Feb 2023 20:05:01 -0000
|Read Time: 0 minutes
Introduction
This paper provides an example of integrating the Dell PowerEdge MX platform running Dell SmartFabric Services (SFS) with Cisco Application Centric Infrastructure (ACI).
The example in this blog assumes that the PowerEdge MX7000 chassis are configured in a Multi Chassis Management Group (MCM) and that you have a basic understanding of the PowerEdge MX platform.
As part of the PowerEdge MX platform, the SmartFabric OS10 network operating system includes SmartFabric Services, a network automation and orchestration solution that is fully integrated with the MX platform.
Configuration Requirements
Configuration of SmartFabric on PowerEdge MX with Cisco ACI makes the following assumptions:
- All MX7000 chassis and management modules are cabled correctly and in an MCM group.
- VLTi cables between MX Fabric Switching Engines (FSE) and Fabric Expander Modules (FEM) are connected correctly.
- PowerEdge and Cisco ACI platforms are in healthy status and are running updated software.
The example setup is validated using the following software versions:
- MX chassis: 2.00.00
- MX IOMs (MX9116n): 10.5.4.1.29
- Cisco APIC: 5.2(6e).
- Cisco leaf switches: 4.2(7u)
Refer to the Dell Networking Support and Interoperability Matrix for the latest validated versions.
Hardware and Logical Topology
The validated Cisco ACI environment includes a pair of Nexus C93180YC-EX switches as leafs. These switches are connected to a single Nexus C9336-PQ switch as the spine using 40GbE connections. MX9116n FSE switches are connected to the C93180YC-EX leafs using 100GbE cables.
The following section provides an overview of the topology and configuration steps. For detailed configuration instructions, refer to the Dell EMC PowerEdge MX SmartFabric and Cisco ACI Integration Guide.
Caution: The connection of an MX switch directly to the ACI spine is not supported.
Figure 1 Validated SmartFabric and ACI environment logical topology
This blog is categorized into four major parts:
- Cisco Application Policy Infrastructure Controller (APIC)
- Dell PowerEdge MX OpenManage Enterprise-Modular (OME-M)
- VMware vCenter Server Appliance (VCSA)
- Dell OpenManage Network Integration (OMNI)
Cisco APIC
Cisco APIC provides a single point of automation and fabric element management in both virtual and physical environments. It helps the operators build fully automated and scalable multi-tenant networks.
To understand the required protocols, policies, and features that you must configure to set up the Cisco ACI, log in to the Cisco APIC controller and complete the steps shown in the following flowcharts.
CAUTION: Ensure all the required hardware is in place and all the connections are made as shown in the above logical topology.
Note: If a storage area network protocol (such as FCoE) is configured, Dell Technologies suggest that you use CDP as a discovery protocol on ACI and vCenter, while LLDP remains disabled on the MX SmartFabric.
PowerEdge MX OME-M
The PowerEdge MX platform is a unified, high-performance data center infrastructure. It provides the agility, resiliency, and efficiency to optimize a wide variety of traditional and new, emerging data center workloads and applications. With its kinetic architecture and agile management, PowerEdge MX dynamically configures compute, storage, and fabric; increases team effectiveness; and accelerates operations. The responsive design delivers the innovation and longevity that customers need for their IT and digital business transformations.
VMware vCenter
VMware vCenter is an advanced management centralized platform application. The flowchart below assumes that you have completed the following prerequisites:
- Install the vCenter server appliance on the ESXi MGMT server.
- Install the ESXi VMvisor on the ESXi host servers for the MX SmartFabric and Cisco ACI integration environment.
OMNI
OMNI is an external plug-in for VMware vCenter that is designed to complement SFS by integrating with VMware vCenter to perform fabric automation. This integration automates VLAN changes that occur in VMware vCenter and propagates those changes into the related SFS instances running on the MX platform, as shown in the following flowchart figure.
The combination of OMNI and Cisco ACI vCenter integration creates a fully automated solution. OMNI and the Cisco APIC recognize and allow a VLAN change to be made in vCenter, and this change will flow through the entire solution without any manual intervention.
For more information about OMNI, see the SmartFabric Services for OpenManage Network Integration User Guide on the Dell EMC OpenManage Network Integration for VMware vCenter documentation page.
Figure 2 OMNI integration workflow
MX Single Chassis Deployment for ACI Integration
A single MX7000 chassis may also join an existing Cisco ACI environment by using the MX5108n ethernet switch. The MX chassis in this example has two MX5108n ethernet switches and two MX compute sleds.
The connections between the ACI environment and the MX chassis are made using a double-sided multi-chassis link aggregation group (MLAG). The MLAG is called a vPC on the Cisco ACI side and a VLT on the PowerEdge MX side. The following figure shows the environment.
Figure 3 SmartFabric and ACI environment using MX5108n Ethernet switches logical topology
Reference
List of Acronyms
ACI: Cisco Application Centric Infrastructure (ACI) AEP: Attachable Access Entity Profile APIC: Cisco Application Policy Infrastructure Controller CDP: Cisco Discovery Protocol EPG: End Point Groups LLDP: Link Local Discovery Protocol MCP: Mis-Cabling Protocol MCM: Multi Chassis Management Group MLAG: Multi-chassis link aggregation group MX FSE: Dell MX Fabric Switching Engines MX FEM: Dell MX Fabric Expander Modules MX IOMs: Dell MX I/O Modules | MX MCM: Dell MX Multichassis Management Group OME-M: Dell OpenManage Enterprise-Modular OMNI: Dell OpenManage Network Integration PC: Port Channel STP: Spanning Tree Protocol VCSA: VMware vCenter Server Appliance vDS: Virtual Distributed Switch VLAN: Virtual Local Area Network VM: virtual machine VMM: VMware Virtual Machine Manager vPC: Virtual Port Channel VRF: Virtual Routing Forwarding |
Documentation and Support
Dell EMC PowerEdge MX Networking Deployment Guide
Dell EMC PowerEdge MX SmartFabric and Cisco ACI Integration Guide.
Networking Support & Interoperability Matrix
Dell EMC PowerEdge MX VMware ESXi with SmartFabric Services Deployment Guide

Integrate Dell PowerEdge MX with Cisco ACI
Thu, 09 Feb 2023 20:05:01 -0000
|Read Time: 0 minutes
You can integrate the Dell PowerEdge MX platform running Dell SmartFabric Services (SFS) with Cisco Application Centric Infrastructure (ACI). This blog shows an example setup using PowerEdge MX7000 chassis that are configured in a Multi Chassis Management Group (MCM).
We validated the example setup using the following software versions:
- MX chassis: 2.00.00
- MX IOMs (MX9116n): 10.5.4.1.29
- Cisco APIC: 5.2(6e).
- Cisco leaf switches: 4.2(7u)
The validated Cisco ACI environment includes a pair of Nexus C93180YC-EX switches as leafs. We connected these switches to a single Nexus C9336-PQ switch as the spine using 40GbE connections. We connected MX9116n FSE switches to the C93180YC-EX leafs using 100GbE cables.
Configuration
The Dell Technologies PowerEdge MX with Cisco ACI Integration blog provides an overview of the configuration steps for each of the components:
- Cisco Application Policy Infrastructure Controller (APIC)
- Dell PowerEdge MX OpenManage Enterprise-Modular (OME-M)
- VMware vCenter Server Appliance (VCSA)
- Dell OpenManage Network Integration (OMNI)
For more detailed configuration instructions, refer to the Dell EMC PowerEdge MX SmartFabric and Cisco ACI Integration Guide.
Resources
Dell EMC PowerEdge MX Networking Deployment Guide
Dell EMC PowerEdge MX SmartFabric and Cisco ACI Integration Guide.
Networking Support & Interoperability Matrix
Dell EMC PowerEdge MX VMware ESXi with SmartFabric Services Deployment Guide