Dell EMC OpenManage Enterprise-Modular Edition Version 1.20.10 for PowerEdge MX7000 Chassis User's Guide Jan 2021 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2018 -2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Revision history Date Document revision Description of changes 5 Jan 2021 Rev A02 Revised BIOS 2.8.2 to BIOS 2.9.4 in OME-Modular 1.20.10 baseline.
Contents Revision history..........................................................................................................................................................................3 Chapter 1: Overview...................................................................................................................... 9 Key features...................................................................................................................................................................
Creating chassis filters...............................................................................................................................................35 Viewing chassis overview..........................................................................................................................................35 Wiring chassis...............................................................................................................................................................
Extracting IOM logs.................................................................................................................................................... 67 Chapter 6: Managing templates...................................................................................................68 Viewing template details..................................................................................................................................................68 Creating templates...................
Deleting fabric.....................................................................................................................................................................91 VLANs for SmartFabric and FCoE................................................................................................................................. 91 Defining VLANs for FCoE...........................................................................................................................................
Viewing job details......................................................................................................................................................110 Running jobs................................................................................................................................................................. 111 Stopping jobs....................................................................................................................................................
1 Overview The Dell EMC OpenManage Enterprise Modular (OME-Modular) application runs on the PowerEdge M9002m management module (MM) firmware. OME-Modular facilitates configuration and management of a standalone PowerEdge MX chassis or group of MX chassis using a single Graphical User Interface (GUI). You can use OME-Modular to deploy servers and update firmware.
New in this release This release of OME-Modular supports: ● Added support for Quad-Port Ethernet adapters in up to 5 MX7000 chassis in a Scalable Fabric. ● Increased the VLAN scale for SmartFabric services. ● Additional topologies for Fabric Expander Module connectivity. ● Added a new compliance status Unknown in the Compliance Report. The Unknown status highlights the component or device firmware that is missing from the catalog and must be compared manually for compliance.
Table 1. List of other documents for reference Name of the document Brief introduction of the document OpenManage Enterprise Modular RACADM Command Line Reference Guide This document contains information about the RACADM subcommands, supported interfaces, and property database groups and object definitions.
Positioning OME-Modular with other Dell EMC applications OME–Modular works with the following applications to manage, simplify, and streamline operations: ● OME–Modular discovers and inventories MX7000 chassis in the data center using the OME–Modular REST API commands. ● integrated Dell Remote Access Controller (iDRAC)—OME–Modular manages virtual consoles through iDRAC. ● Repository Manager—OME–Modular uses Repository Manager to create custom repositories in shared networks for creating catalogs.
2 Updating firmware for PowerEdge MX solution Component and device firmware for the MX solution are rigorously tested as a validated solution stack or firmware baseline. The details are listed in the table Updating MX7000 components using OME-Modular containing current and previous baselines. When the Dell update packages (DUPs) are available on https://www.dell.com/support , a validated solution stack of the chassis firmware catalog referencing them is published.
Table 2. MX7000—OME-Modular 1.20.10 and previous solution baselines (continued) Component v1.10.20 v1.20.00 v1.20.10 Catalog exceptions Mellanox ConnectX-4 Lx Ethernet Adapter Firmware 14.25.80.00 14.26.60.00 14.27.61.22 Intel NIC Family Version 19.5.x Firmware for X710, XXV710, and XL710 adapters 19.5.12 19.5.12 19.5.12 Emulex Fibre Channel Adapter Firmware. 03.02.18 03.02.18 03.02.18 OpenManage Enterprise Modular 1.10.20 1.20.00 1.20.10 MX9116n Fabric Switching Engine OS10 10.5.0.
Component update order WARNING: Read the update instructions before implementing the update procedure. Collate the current versions of the MX7000 components in your environment and note any special instructions that may be called out in the update procedure. Contact Dell support for assistance with upgrading the MX7000 components as it is a complex procedure. It is recommended that you update all components within a scheduled single maintenance window.
4. Select the Baseline option and select the required baseline from the drop-down. 5. Select the OME–Modular component from the comparison report. The supported components are displayed. 6. Select the required components, for example: OME–Modular, and click Update to start the firmware update. 7. Go to the Monitor > Jobs page to view the job status. NOTE: Use the Add option on the Configuration > Firmware > Catalog Management option to download the catalog from https://www.dell.com/support.
Updating management module firmware NOTE: Ensure that you upgrade the OME-Modular firmware before upgrading OS10. You can update the management module firmware using the following methods: 1. Individual package method—Through OME–Modular web interface or RESTful API 2. Catalog-based compliance method To update the firmware using the Individual package method: 1. Download the DUP from the www.dell.com/support/drivers. 2.
Table 4. OS10 firmware update matrix (continued) To OS10 version 10.4.0E( R3SP2) 10.4.0E(R4 10.5.0.1 SP2) 10.4.0E(R4S P2) Yes* 10.5.0.1 10.5.0.3P1 10.5.0.5 10.5.0.7 Yes* Yes* Yes* Yes Yes Yes Yes Yes 10.5.0.3P1 10.5.0.5 10.5.1.6 Yes 10.5.0.7 Yes** *—Upgrading IOM VLT peers from 10.4.X to 10.5.X version impacts traffic. Regular maintenance window is recommended for this activity. **—Upgrading IOMs in SmartFabric mode to OS10.5.1.6 with VLAN 1 as tagged, disrupts traffic.
3 Logging in to OME-Modular You can log in to OME–Modular as a local, Active Directory, or generic Lightweight Directory Access Protocol (LDAP) user. OME–Modular supports a maximum of two Active Directory or LDAP server configurations, each.
● Configure your account. ● Change the password. ● Recover the root password. Integrating directory services in OME-Modular You can use Directory Services to import directory groups from AD or LDAP for use on the web interface. OME-Modular supports integration of the following directory services: 1. Windows Active Directory 2. Windows AD-LDS 3. OpenLDAP 4. PHP LDAP Supported attributes and pre-requisites for LDAP Integration Table 5.
2. From the Type of Directory, select the option, AD or LDAP. The default option is AD. 3. Enter the Directory Name. 4. Select the Domain Controller Lookup. If the Domain Controller Lookup type is DNS and the directory type is AD, enter the domain name and group domain. For the AD directory type, if the Domain Controller Lookup type is DNS, enter the domain name and group domain. If the Domain Controller Lookup type is Manual, enter the FQDN or IP addresses of the domain controllers.
● Provided the Primary and Alternate DNS server addresses. After you enter the domain name, OME-Modular searches the SRV records on the DNS servers to fetch the details of the domain controllers in that domain. If you know the IP address or FQDN of the domain controllers, you can use the Manual domain controller lookup type. 5. Enter the Bind DN and Bind Password. NOTE: Anonymous bind is not supported for AD LDS. 6.
In the Find a Group text box, enter the first few letters of the group name available in the tested directory. A list of all groups names that begin with the text you entered, is displayed below under the GROUP NAME column. 4. Select a group and click >>. The selected group is displayed under Groups to be Imported. To remove groups, select the check box corresponding to the group you want to remove and click <<. 5.
Search feature in OME-Modular The search feature enables you to look for information about jobs, devices, alerts, links, alert policies, users, and audit logs. The feature works in English only and is case insensitive. You can search for records as you type. For example: If you are looking for alerts and start entering the word, OME-Modular suggests the matching terms. The search feature supports: ● A maximum of 255 characters including special characters.
Page name Fields ● ● ● ● ● IP Address Message Message Interface Severity User Name Help ● Title ● Content Alert Policy ● Name ● Description ● Enabled/Disabled Users ● ● ● ● ● ● All Devices ● ● ● ● ● ● ● ● ● ● ● Global Status Model Identifier Type Power State IP Address Asset Tag Associated Chassis Service Tag Inventory Location—Description, Name, Details Software—Description, Instance ID, PCI Device ID, Software Type, Status, Sub Device ID, Sub Vendor ID, Vendor ID, Version ● License—Assigned Dev
Multi-chassis management dashboard Multiple chassis are grouped to form domains called Multi-Chassis Management (MCM) groups. An MCM group can have 20 chassis, where one is the lead and the remaining 19 are members. OME–Modular supports wired MCM groups where the chassis are daisy-chained through a redundant port on the management controller. In a multi-chassis management (MCM) group, the number of events and jobs for the entire group is displayed.
Setting up chassis When you log in to the OME–Modular web interface for the first time, the configuration wizard is displayed. If you close the wizard, you can access it again by clicking Configure > Initial Configuration. This option is displayed only if the chassis is not yet configured. To configure the chassis: 1. Log into OME–Modular. The Home page is displayed. 2. Click Configure > Initial Configuration. The Chassis Deployment Wizard is displayed. For further steps, see Initial configuration.
9. Enter a name for the catalog, select the catalog source, and click Finish to save the changes and return to the Chassis Deployment Wizard. 10. Click Next to view the Proxy tab and configure the proxy settings. OME–Modular uses the proxy settings to access the Dell EMC website for the latest catalogs. You can also enable the HTTPS proxy settings and proxy authentication. 11. Click Next to view the Group Definition tab. 12. Select Create Group to configure the chassis group settings. 13.
● PSU redundancy is inactive. ● Power budget of the system configuration exceeds the PSU output capacity. ● Grid Redundancy Policy is not selected. The MX7000 PSUs support the Hot Spare feature with three PSU pairs. The feature enables a PSU pair to have one active PSU and one PSU in sleep mode while the enclosure power consumption is low, and the three PSU pairs meet all the power requirements for the enclosure. This enables efficient power utilization when the overall enclosure power requirement is low.
Table 6. Top of the Rack Support Matrix for management module and management module uplink (continued) Top of the Rack Switch Configuration Management Module Configuration Supported for Management Module Uplink (YES or NO) Auto Neg ON Auto Negotiation ON YES 100 Mbps (Auto negotiation OFF) Auto Negotiation ON NO 10 Mbps (Auto negotiation OFF) Auto Negotiation ON NO Auto Negotiation ON 100 Mbps (Auto negotiation OFF) NO Auto Negotiation ON 10 Mbps (Auto negotiation OFF) NO 5.
Configure chassis network services The chassis network services configuration consists of SNMP, SSH, and remote RACADM settings. To configure network services: 1. Click Devices > Chassis > View Details > Settings > Network Services. The Network Services section is expanded. 2. In the SNMP Settings section, select the Enabled check box to enable the SNMP settings and select the Port Number. The port number can be 10-65535.
NOTE: The Timeout Limit option is available only if the Enable Inactivity Timeout is selected. 5. Select Enable Read Authentication to use your user credentials to read the inventory in a secure data center. By default, this option is selected. If you clear this check box, you cannot access the secure data center. 6. Select Enable Quick Sync Wi-Fi to use WiFi to communicate with the chassis. By default, the Enable Quick Sync Wi-Fi check box is selected. 7.
MX7000 chassis. On successful connection, LED under the micro-USB on the right control panel of MX7000 chassis turns green and USB Ethernet adapter is displayed on the host. The chassis is automatically configured with an IPV4 and IPV6 address. After ensuring that the addresses are configured, open a web browser and enter the URL, https://ome-m.local in the address bar.
The Location supports up to 128 characters. It is supported for backward compatibility. The Data Center, Aisle, Rack, and Rack Slot properties replace this property. Use these properties to describe the physical location of the chassis. 4. Click Apply to save the location settings. Configure Quick Deploy settings The Quick Deploy feature enables you to configure the password to access the iDRAC user interface, IOMs, and IPv4 and IPv6 settings.
● Static ● DHCP 12. If the IPv6 Network Type is Static, select the IPv6 Prefix Length and enter the IPv6 Gateway. 13. Click Apply to save the Quick Deploy settings. Managing chassis You can view the list of chassis and the chassis details on the Chassis page. The details are—health, power state, name, IP address, service tag, and model of the chassis. You can also select a chassis to view the graphical representation and summary of the chassis, on the right side of the Chassis page.
NOTE: The temperature statistics timestamp remains unchanged after a failover or management module reboot. ● Recent Alerts—Displays the number and details of the tasks that are performed in the chassis. Click View All to view the list of all alerts that are related to the compute sled on the Chassis > Alerts page. ● Recent Activity—Displays the status of the jobs that are performed in the compute sled. ● Server Subsystems—Displays a summary of information about the server sub systems.
The following image is a representation of the two-chassis wiring: Chassis groups You can group many chassis to form a multi-chassis management (MCM) group. An MCM group can have one lead chassis and 19 member chassis. You can use any management module to create an MCM group. The management module that is used for creating the MCM is the leader of the group, by default. The MCM group is of wired type, where the chassis is daisy-chained or wired through a redundant port on the management module.
You can add member chassis to an MCM group in two ways: ● Automatic—Enables automatic inclusion of the member to the chassis group. The automatic inclusion process does not require approval from the chassis administrator. ● Manual—Mandates approval by the chassis administrator to include the member chassis to the chassis group.
Creating chassis groups To create a chassis group: 1. On the chassis dashboard, click Overview > Configure > Create Chassis Group. The Create a Group and Configure Lead Chassis wizard is displayed. 2. Enter a name and description for the chassis group you want to create. The group names can contain letters and numbers and must be fewer than 48 characters. However, the group names cannot contain spaces and special characters. 3. Select the onboarding permission type. 4.
● ● ● ● ● ● Alert Destination—Email, SNMP trap, system log Time Settings—Date, time, time zone, NTP Proxy Settings—All settings Security Settings—Login IP range, log on lockout policy Network Services—SNMP, SSH, remote RACADM, web server Local Access Configuration—Chassis power button, quick sync, KVM, LCD, serial access 5. Click Next to view the summary of the group. The dashboard of a leader chassis displays a summary of the health information, recent activity, and recent alerts of the member chassis.
4. Click Additional Information to view details about enabling the virtual IP. The details are: ● ● ● ● ● Modifying the network settings may impact the virtual IP configuration Disabling the NIC will also disable the virtual IP Disabling IPv4 will not disable the virtual IP Enabling VLAN will leave the virtual IP accessible only within the specified VLAN Enabling/disabling DHCP for IPv4 will reconfigure the virtual IP to match the new subnet mask and gateway Also, see the section, Use case scenarios.
baseline report. To resolve this limitation, rerun the compliance check on the promoted lead after the retire job is completed so that the old lead devices are listed in the compliance or baseline report. After the retire lead task is completed, the system runs some internal tasks to complete the association of the groups that may take some time.
● ● ● ● OME–Modular network settings Users settings Security settings Alert settings You can use the backed-up configuration in other chassis. To create a chassis backup: 1. On the chassis Overview page, click More Actions > Backup. The Backup Chassis window is displayed. 2. In Backup File Location, select the Share Type where you want to store the chassis backup file. The available options are: ● CIFS ● NFS 3. Enter the Network Share Address and Network Share Filepath. 4.
Managing chassis failover Failover is applicable in dual management module configuration and is the process of transferring the active role to the standby management module. Reboot the active management module and re-initialize the stand-by management module to assume the active role. The failover operation takes up to 10 minutes for completion. OME–Modular is unavailable during this process. You must have the chassis administrator privilege to start a failover.
Table 8. Management module Interfaces (continued) Interface Description and uses the HTTPs channel. The –r option runs the RACADM command over a network. ● Firmware RACADM is accessible by logging in to OME–Modular using SSH or telnet. You can run the firmware RACADM commands without specifying the OME– Modular IP, user name, or password. After you enter the RACADM prompt, you can directly run the commands without the RACADM prefix.
Table 8. Management module Interfaces (continued) Interface Description Chassis Direct The Chassis Direct feature enables you to access management consoles such as iDRAC and management module of devices on the MX7000 chassis. Viewing chassis hardware On the OME–Modular home page, click Hardware to view details of the hardware components that are installed in the chassis. You can also view the chassis hardware details by clicking Devices > Chassis > View Details > Hardware.
Viewing chassis hardware logs The logs of activities performed on the hardware components associated with the chassis are displayed on the OME–Modular Hardware Logs page. The log details that are displayed include severity, message ID, category, timestamp, and description. You can also view the chassis hardware logs by clicking Devices > Chassis > View Details > Hardware Logs.
If you customize the https port, OME-Modular tries to redirect to the new port automatically. However, the redirection may not work owing to security limitations of the browser. In such cases, open a new window or tab of the browser and enter the OME-Modular URL using the customized port. For example, https://10.0.0.1:1443 NOTE: Disabling the OME-Modular web server does not affect the launching of OME-Modular GUI on the phonebook page while using Chassis USB Direct.
To configure the time and alert destination: 1. Click Application Settings > Network > IOM Synchronization Configuration. 2. Select the Replicate Time Configuration from Chassis and Replicate Alert Destination Configuration from Chassis check boxes. ● MXG610s supports only three SNMP destination unlike OS10 which supports four SNMP destinations. ○ Using SNMP, IPV4 and IPV6 replication is supported from OME-Modular to IOM.
Table 9. Ports and protocols that are supported in OME-Modular (continued) Port number Protocol Port type Maximum encryption level Source Direction Destination Usage on (if enabled). 137, 138, 139, 445 CIFS UDP/TCP None OME-Modular Out CIFS Share To import firmware catalogs from CIFS share. 161* SNMP UDP None External Application In OpenManage Enterprise Modular For SNMP queries.
Configuring users and user settings In OME–Modular, you can create up to 64 local users and assign them specific roles and privileges. Using the options available under Application Settings > Users, you can add and edit users, import a directory group, and view and terminate active user sessions. NOTE: You can create, delete, enable, or disable users only if you have the security setup privilege. Viewing and editing user accounts 1.
Recovering passwords in single OME-Modular controller 1. From the chassis, remove the single OME–Modular controller. 2. Locate the Jumper, see the board location—P57 RESET PASSWORD, and then insert the Jumper. 3. Reinsert the controller into the chassis. 4. When OME–Modular is available, login with the user name as "root" and password as "calvin". 5. After the root user authentication, change the password for the root user on the Application Settings > Users page. 6.
Table 10.
a. Lockout Fail Count: The number of failed login attempts. Valid values are between 2 and 16. b. Lockout Fail Window: The time within which subsequent failed logins are registered. Valid time is between 2 seconds and 65,535 seconds. c. Lockout Penalty Time: Time for which the logins are restricted. Valid time is between 2 seconds and 65,535 seconds. If the IP is still unavailable, ensure that: ● The network cable is connected.
2. Click Email Configuration 3. Enter the SMTP Server Network Address. NOTE: The SMTP server network address can have a maximum length of 255 characters. 4. If the server requires authentication, select Enable Authentication. NOTE: If Enable Authentication is selected, you must provide the user name and password to access the SMTP server. 5. Enter SMTP Port Number. 6. If the SMTP server is configured to use SSL, select the SSL option.
4 Managing compute sleds OME–Modular enables you to allocate and manage compute sleds to balance workload demands. You can view the list and details of compute sleds on the Compute page. The details are—health, power state, name, IP address, service tag, and model of the chassis. You can also select a compute sled to view the graphical representation and summary of the compute sled, on the right side of the Compute page. Select a compute sled from the list to view a summary of the sled on the right side.
Table 11. Profile association Slot Profile Name Device Profile Name Displayed Value profile1 - slot - profile1 device profile1 profile1 slot and device The midsection of the Overview page displays the number of different Recent Alerts triggered in the compute. The details of the alerts are displayed below. Below the Recent Alerts is the Recent Activity section, which displays the list of recent activities that are associated with the compute.
○ Power On—Turns on the server power, which is equivalent to pressing the power button when the server is turned off. This option is disabled if the server is already turned on. ● Extract SupportAssist logs and reset iDRAC using Troubleshoot. SupportAssist is used to collate hardware, operating system, and RAID controller logs and store the logs in the NFS or CIFS share location. iDRAC reset helps in troubleshooting when iDRAC is noncommunicative. ● Turn-on or turn off LEDs using Blink LED.
Configuring compute management settings To configure the compute management settings: 1. Click Devices > Compute > View Details > Settings > Management. 2. Configure the password to access the iDRAC console and select IPMI over LAN to enable access from OME–Modular to iDRAC, through BIOS. Replacing compute sleds The rip-and-replace feature of OME-Modular enables you to replace a failed compute sled, storage sled, or IOM, and apply the configuration automatically.
Table 12. Compute sled replacement - Behavior of OME-Modular and LCD panel OME-Modular behavior LCD behavior Case 1 Enables users to clear all mappings to the compute sled. Enables users to clear all mappings to the compute sled. Case 2 Enables users to clear or retain all mappings to the compute sled. Enables users to clear or retain all mappings to the compute sled.
● ● ● ● End Date Category Subcategory Message Select an alert to view the summary on the right side of the Alerts. You can also perform the following activities on the Alerts page.
5 Managing storage This chapter describes the Storage and IOM features of OME–Modular. It also provides details about performing various storage-related tasks. The SAS IOMs manage the storage enclosures. SAS IOMs facilitate communication between storage and compute sled and also help in assigning the storage to the compute sleds.
1. From the Devices drop-down menu, select Storage. 2. Select the storage sled. 3. Click Blink LED and click Turn On. To turn off the LED blinking: 1. From the Devices drop-down menu, select Storage. 2. Select the storage sled. 3. Click Blink LED and click Turn Off. You can pull out the storage sled trays from the chassis to access the storage sled drives.
Current Mode—Indicates if the hard drive is assigned to an enclosure or to a single compute node slot. ● Enclosure-Assigned—In this mode, you can assign an entire storage sled to one or more compute node slot. NOTE: You cannot assign storage when a redundant SAS IOM setup is temporarily degraded to nonredundant state. NOTE: The storage enclosure is assigned to the slots of the compute slots and not to the sled itself.
To assign an enclosure: 1. From the Devices drop-down list, select Storage. 2. Select the storage sled from the list of the storage devices. 3. Click View Details. The storage Overview page is displayed. 4. Click Hardware and select Enclosure-Assigned. A warning message about loss of data while selecting this mode is displayed. 5. Select I understand that reseting this assignment could result in data loss and click Ok. 6. Select the compute sled slots and click Assign.
○ Reboot server immediately—Select this check box to send the update and reboot the server immediately. You can select the reboot options from the drop-down, the available options are: ￭ Graceful Reboot with Forced Shutdown ￭ Graceful Reboot without Forced Shutdown ￭ Power Cycle ○ Stage for next server reboot—Select this check box to send the update to the server. However, the update is installed only the next time the server is rebooted. a.
● ● ● ● ● ● ○ Power Cycle—The Power Cycle option initiates a warm reboot of the IOM. In this instance, the power is not removed from the IOM and the core systems of the IOM reboot. ○ System Reseat—The System Reseat option removes the IOM virtually. In this instance, the power is removed from the IOM and the IOM reboots. NOTE: After the power reseat of the SAS IOM, the IOM turns on within a minute.
6 Managing templates OME–Modular allows you to configure servers based on templates. A server template is a consolidation of configuration parameters that are extracted from a server and used for replicating the configuration to multiple servers quickly. A server profile is a combination of template and identity settings that are applied to a specific or multiple servers, or saved for later use. You must have the template management privilege to create templates.
Creating templates You can create templates in the following ways: ● Clone from an existing server—Reference Device ● Import from an external source—Import from File To create a template from a reference device: 1. On the Deploy page, click Create Template and select From Reference Device. The Create Template wizard is displayed. 2. Enter the name and description for the template and click Next. The Reference Device tab is displayed. 3.
2. Select the target slot or device on which you want to deploy the template, enter the ISO path and location details, configure the iDRAC management IP settings, select the Do not forcefully reboot the host OS if the graceful reboot fails option. If you select an occupied sled slot, the Immediately Apply Template to Compute Sleds check box is displayed. Select the check box to reseat the compute sled immediately and deploy the template on it.
Refer to the network adapter or operating system documentation for detailed NIC teaming instructions. The available NIC teaming options are: ● No Teaming—NICs are not bonded and provide no load balancing or redundancy. ● LACP—Also referred to as Switch Dependent, 802.3ad or Dynamic Link Aggregation. The LACP teaming method uses the LACP protocol to understand the teaming topology. It provides Active-Active teaming with load balancing and redundancy.
7 Managing identity pools Identity pools are used in template-based deployment of servers. They facilitate virtualization of network identities that are required for accessing systems using Ethernet, iSCSI, FCoE, or Fibre Channel (FC). You can enter the information that is required for managing the I/O identities. The identities, in turn, are managed by chassis management applications such as OME– Modular.
If the identity is assigned, the information about the assigned server and NIC Identifier is displayed. If the identity is reserved, the information about the assigned slot in the chassis is displayed. You can create an identity pool with only the name and description and configure the details later. NOTE: You can clear identities by disabling the I/O Identity Optimization option in iDRAC. To create identity pools: 1. Click Configuration > Identity Pools.
Editing identity pools You can modify the number of entries in the identity pool. However, you cannot reduce the size of the identities that are already assigned or reserved. For example, in a pool of 100 MAC addresses, if 94 of the addresses are assigned or reserved, you cannot reduce the number of MAC addresses to less than 94. To edit an identity pool: 1. On the Identity Pools page, select the identity pool and click Edit. The Edit Identity Pool window is displayed. 2. Make the required changes.
8 Ethernet IO Modules The MX7000 supports the following Ethernet I/O Modules (IOMs): ● Managed Ethernet switches: ○ MX9116n Fabric Switching Engine ○ MX5108n Ethernet Switch ● Unmanaged devices: ○ MX7116n Fabric Expander Module ○ PowerEdge MX 25 Gb Ethernet Pass-Through Module ○ PowerEdge MX 10GBASE-T Ethernet Pass-Through Module Ethernet IOMs are supported in Fabrics A and B. For details about the supported IOM slots, see Supported slot configurations for IOMs.
NOTE: When a switch changes between Full Switch and Fabric modes, it reboots. NOTE: If the compute sled and fabric IOM mismatch, the health status of the compute or IOM is displayed as "Warning" in the chassis subsystem health. However, the health status is not displayed in the chassis graphical representation on the Chassis page, I/O Modules, and Compute pages.
To configure the networking settings: 1. Click All Devices > I/O Modules > View Details > Settings > Network or Devices > I/O Modules > View Details > Settings > Network. 2. In the IPv4 Settings section, select Enable IPv4. 3. Enter the IP Address, Subnet Mask, and Gateway for the management port. The IP Address, Subnet Mask, and Gateway options are enabled only if the Enable DHCP check box is cleared.
1. Click All Devices > I/O Modules > View Details > Settings > Monitoring or Devices > I/O Modules > View Details > Settings > Monitoring. 2. Select the Enable SNMP checkbox to enable of disable the SNMP. 3. From SNMP Version, select SNMP v1 or SNMP v2. 4. Enter the Read Community String to fetch requests from the OME Modular daemon directed at the IOM. 5. Click Apply to save the monitoring settings or click Discard to clear the changes and go back to the previous settings.
Configuring admin status You can switch the admin status for all ports, which is enabled by default. For the MX9116n FSE port groups 1/1/15 and 1/1/16, when you breakout the fiber channel ports, the admin status is disabled by default. Enable the status if required. To switch the admin status: Select the port and click Toggle Admin State. The Toggle Admin State window is displayed.
To configure FEC: 1. On the Port Information page, expand the physical port group, and select the Ethernet port . 2. Click Configure FEC. The Configure Forward Error Correction window is displayed. 3. Select the FEC Type. The available options are: ● Auto—Applies FEC based on the cable or optic connected ● Off—Disables FEC ● CL74-FC— Configures CL74-RS FEC and supports 25G and 50G ● CL91-RS—Configures CL91-RS FEC and supports 100G ● CL108-RS—Configures CL108-RS FEC and supports 25G and 50G 4.
9 MX Scalable Fabric architecture The scalable fabric architecture ties multiple MX7000 chassis into a single network domain to behave like a single logical chassis from a networking perspective.
Recommended physical topology The recommended minimum design for a scalable fabric is two chassis with Fabric A populated with redundant IOMs. Ideally, the two chassis are located in separate racks on separate power circuits to provide the highest redundancy. Additional chassis only have FEMs and the appear as the image below. Table 13.
Restrictions and guidelines The following restrictions and guidelines are applicable when building a scalable fabric: ● Mixing switch types in the same fabric is not supported. For example: MX9116n in slot A1 and MX5108n in slot A2 ● Mixing switch types across fabrics is supported. For example: MX9116n in slots A1& A2 and MX5108n in slots B1 & B2 ● All FSE and FEM IOMs in a scalable fabric must be in the same OME–Modular MCM group.
10 SmartFabric Services SmartFabric Services is a capability of Dell EMC Networking OS10 Enterprise Edition running on Ethernet switches that are designed for the PowerEdge MX platform. A SmartFabric is a logical entity containing a collection of physical resources such as servers and switches and logical resources —networks, templates, and uplinks.
• • • • • • NIC teaming restrictions OS10 CLI commands available in SmartFabric mode Viewing fabric details Adding SmartFabric Deleting fabric VLANs for SmartFabric and FCoE Guidelines for operating in SmartFabric mode The guidelines and restrictions while operating in SmartFabric mode are as follows: ● When operating with multiple chassis, ensure that the switches in A1/A2 or B1/B2 in one chassis are interconnected only with other A1/A2 or B1/B2 switches respectively.
In SmartFabric mode, ports 9 and 10 are automatically configured in a VLT at 40GbE speed. For port 10, use a cable or optic that supports 40GbE and not 100GbE. 2 x MX9116n Fabric Switching Engines in the same chassis Use this placement in environments with a single chassis. The switches must be placed in either slots A1/A2 or slots B1/B2. A SmartFabric cannot include a switch in Fab A and a switch in Fab B.
NOTE: You cannot select the ports, and the connection topology is enforced by SmartFabric Services. NOTE: VLT is supported only on Ethernet and not on FCoE. Physically separate uplinks for LAN and FCoE traffic are required for MX5108n and MX9116n switches. Upstream network switch requirements It is recommended, but not required, that PowerEdge MX switches are connected to a pair of redundant upstream switches.
2. If NPAR IS in use, only Switch Independent teaming methods are supported. Switch-Dependent teaming is NOT supported. The following restrictions are applicable to Switch Dependent (LACP) teaming: 1. The IDRAC shared LOM feature can only be used if “Failover” option on IDRAC is enabled. 2. If the host operating system is Windows, the LACP timer MUST be set to “slow” (also referred to as “normal”).
Adding uplinks To add uplinks: 1. From the Devices drop-down, select Fabric. The Fabric page is displayed. 2. From the fabrics table, select the fabric and click View Details. The Fabric Details page is displayed. 3. From the Uplinks section, click Add Uplink. The Add Uplink window is displayed. 4. Enter Name, Description, select the Uplink Type. The available options are: ● Ethernet - No Spanning Tree— You must pick at least one Ethernet port from each switch to form a LAG.
The Fabric page is displayed. 2. From the fabrics table, select the fabric and click View Details. The Fabric Details page is displayed. 3. From the Uplinks section, click Add Uplink. The Add Uplink window is displayed. 4. Click Add Network. The Define Network window is displayed. 5. Enter Name, Description, VLAN ID and select the Network Type. For the network types, see the Online Help. Editing uplink To edit an existing uplink: 1. From the Devices drop-down, select Fabric. The Fabric page is displayed.
3. In the uplinks table, select the uplink to be deleted. 4. Click Delete. Click Yes to confirm the deletion. Deleting fabric To delete an existing fabric: 1. From the Devices drop-down, select Fabric. The Fabric page is displayed. 2. From the fabrics table, select the fabric that you want to delete. 3. Click Delete. A message is displayed prompting you to confirm the deletion. 4. Click Yes to proceed. After the fabric is deleted, the IOMs will reboot and start in Full Switch mode.
3. In the left pane, select Servers and select the required servers. 4. Click Edit Networks. 5. Select one of the following options: ● NIC teaming from LACP ● No Teaming ● Other 6. Define the tagged and untagged VLANs to modify the VLAN selections as required. 7. Select VLANs on Tagged and Untagged Network for each Mezzanine card port. 8. Click Save.
11 Managing networks You can configure logical networks that represent your environment, for the tagged and untagged VLANs. These logical networks are used to provision the appropriate VLANs on the associated switch port for the physical server NIC port. NOTE: VLANs are only assigned to servers connected to switches in SmartFabric mode. For servers connected to switches in Full Switch mode, the VLAN information is ignored. In tagged networks, a port handles multiple VLANs.
Table 19. Network traffic types - QoS settings (continued) Network Traffic Type Description QoS Setting Storage - FCoE Used for FCoE VLANs 5 Storage - Data Replication Used for VLANssupporting storage data replication such as for VMware VSAN 5 VM Migration Used for VLANs supporting vMotion and similar technologies 5 VMWare FT Logging Used for VLANs supporting VMware Fault Tolerance 5 Defining networks To configure a logical network: 1. Click Configuration > VLANs. The VLANs page is displayed.
Importing VLANs To import VLANs: 1. On the Networks page, select the desired network and click Import, and select Import from File. The Import from File window is displayed. 2. Click Select a File to browse and import the file from the destination. The supported file types are .csv and.json. 3. Click Finish to import the VLANs. Deleting VLANs To delete a VLAN: On the Networks page, select the VLAN and click Delete.
12 Managing Fibre Channel IOMs The MXG610s Fibre Channel (FC) switch is designed for mission critical applications accessing data on external storage. It is optimized for flash storage and virtualized server environments. The FC switch enables organizations to dynamically scale connectivity and bandwidth Ports-on-Demand (PoD). It enhances operations with consolidated management and simple server and storage connectivity. OME–Modular makes the management of the MXG610s simple.
13 Managing firmware The firmware feature in OME–Modular helps you to update the firmware of all the components in the chassis. The components include compute sleds, ethernet IOMs, storage IOMs, and SAS IOMs. The firmware updates can be sources from the Dell website or a custom repository setup using Repository Manager. You must have the chassis administrator role and the device update privilege for the chassis to update the firmware on the chassis.
Managing catalogs The catalog management feature in OME–Modular lets you choose the list of DUPs to use with baselines to determine firmware compliance. The catalogs can be sourced from the following locations: ● Newest validated stacks of chassis firmware on Dell.com—Component and device firmware for the MX solution are rigorously tested together as an end to end validated solution stack or firmware baseline. NOTE: You must configure the HTTPS proxy as covered in Initial Configuration.
● Newest validated stacks of chassis firmware on Dell.com—The versions of firmware in this catalog have been tested together as part of the latest OME - Modular firmware release. NOTE: When the validated stacks option is selected, the details will be available only after the data is persisted to the database. ● Latest component firmware versions on Dell.com— This catalog is updated on the second and fourth Friday of every month with new firmware.
Deleting catalogs You can only delete catalogs that are not associated with a baseline. If you attempt deleting a catalog that is associated with a baseline, an error message is displayed. To delete a catalog: On the Catalog Management page, select the catalog that you want to delete and click Delete. Creating baselines To create a firmware baseline: 1. Click Configuration > Firmware Compliance > Create Baseline . The Create Firmware Baseline window is displayed. 2.
● Warning—The firmware version on the device is older than the catalog firmware version and the status of the firmware update in the catalog is critical. ● Ok—The firmware version on the device and the catalog firmware version are identical. ● Downgrade—The firmware version on the device is later than the catalog firmware version. ● Unknown—The firmware version for the component or device is not available in the catalog.
1. On the Firmware page, click Rollback Firmware. The Rollback Firmware window is displayed. 2. Select the component for which you want to roll back the firmware and click Rollback. NOTE: The device is always updated with individual DUP and is never updated or downgraded as part of catalog or baselines. But, when the device is associated with any baseline and an update is available as part of that catalog or baseline, by default the catalog option is given for the Rollback as it is a secure option.
14 Monitoring alerts and logs You can view and manage the alerts that are generated in the management system environment. You can filter alerts and perform the appropriate actions. Every chassis in the MCM group receives Fabric alerts, irrespective of whether the MX5108N or MX9116N IOMs present in the chassis to accommodate new MX5108N or MX9116N IOMs in the chassis. To view the alerts page, from the menu bar, click Alerts.
Acknowledging alert logs You can acknowledge alert logs that are not already acknowledged. Acknowledging an alert prevents storing the same event in the system. For example, if a device is noisy and is generating the same event multiple times, you can ignore further recording of the alert by acknowledging the events that are received from the device. And, no events of the same type are recorded further.
● ● ● ● Edit alert policies Enable alert policies Disable alert policies Delete alert policies OME–Modular also offers pre-defined alert policies for monitoring the systems, after the alert destinations are configured. Creating alert policies To receive Fabrics or Uplink related alerts from the source Fabric Manager, on the configured external destinations, select Network IOM or All Devices as Groups instead of Devices while configuring the alert policy. To create an alert policy: 1.
A confirmation message is displayed. Editing alert policies You can edit alert policies. To edit alert policies: On the Alert Policies page, select the alerts that you want to edit and click Edit. A confirmation message is displayed. Disabling alert policies You can disable alert policies that are enabled. You can disable more than one alert policy at a time. To disable alert policies: On the Alert Policies page, select the alerts that you want to disable and click Disable.
● Message—To view alerts containing a specific numeric or alphanumeric character. ● Category and Subcategory—To view alerts of specific category. ● Severity—To view all alerts with specific severity level. Selections that are made in the filters are applied at real time. 4. To reset the filters, click Clear All Filters.
15 Monitoring audit logs The audit log feature in OME–Modular enables you to monitor log entries related to: ● Log in attempts ● Appliance setup ● Chassis configuration change using RESTful API ● Change in alert filter configuration On the Audit Log page, you can perform the following tasks: ● Sort the audit logs using the Advanced Filter. ● Export all the audit logs in .csv format to a network share or local drive on your system.
Monitoring jobs You can view the status of and details of jobs that are initiated in the chassis and its subcomponents, on the Jobs page. The jobs include firmware update and inventory refresh for devices. To view the Jobs page, from the menu bar, click Monitor > Jobs. You can perform the following tasks on the Jobs page: ● ● ● ● ● ● ● Filter jobs using Advanced Filter View a summary of the job.
○ MCM Assign Backup Lead ○ MCM Group ○ MCM OffBoarding ○ MCM OnBoarding ○ MCM Promote Backup Lead ○ MCM Reassign Backup Lead ○ MCM Retire Lead ○ MCM Settings Propagation ○ MCM Unassign Backup Lead ○ Profile Update ○ Quick Deploy ○ Restore ○ Settings Update ○ Software Rollback ○ SyncronizeDate Task ○ Time Settings ○ Update ● Last Run Start Date and Last Run End Date—To view jobs based on the last run period. ● Source—To view jobs based on the source.
Exporting job execution details You can export the details of the job execution in a .txt format to a local drive on your system. To export the job details: On the Job Details page, click Export under the Execution Details tab. The execution details are downloaded to a local drive on your system, in .txt format. The job execution details are—start and end dates of the job, status, elapsed time, target system where the job is run, and message of the job. NOTE: Always download the report in .txt format.
16 Use case scenarios Use case scenarios for the backup lead chassis feature are described in this chapter. Topics: • • Assigning backup to the MCM Lead Scenarios when backup lead can take over as lead chassis Assigning backup to the MCM Lead The backup lead chassis feature facilitates management of systems in the chassis group when the existing lead chassis fails.
Initially, the backup health status is displayed as "Critical" while the configuration data is being synchronized before changing to "OK". Wait for the backup health to transition to "OK" before proceeding. If the backup health continues to report "Critical" or "Warning" even after 30 minutes of the assign task, it is an indication that there are persistent communication issues. Unassign the backup and repeat the Step 5 to choose another member as the new backup.
Figure 2. Network and power outage—flowchart The alert, CDEV4007, is related to network or power issues that can be classified as: ● Intermittent/recoverable issues—Momentary power or network outages. The administrator can identify these types of failures and perform recovery actions locally or remotely. Do not promote the backup lead. Allow the lead chassis to recover connectivity automatically or the administrator fixes the power or network issues.
1. Before running the "promote" task on the backup lead chassis: a. The "promote" task is a disruptive operation and must be used only when there are no means to recover the inaccessible lead chassis. In partial failures of the lead chassis, for example; if only the management modules are nonresponsive, but the computes are working, running the promote task disrupts workloads that are still running on the lead chassis computes.
URI: /api/ApplicationService/Actions/ApplicationService.ResetApplication Method: POST Payload: {"ResetType": "RESET_ALL", "ForceReset": true} d. Relocate the working components of the old lead to other chassis in the group: i. Relocate network switches from the old lead to the new lead or member chassis in the group to restore the health of the fabrics. ii. Relocate computes from the old lead to the new lead or member chassis in the group.
17 Troubleshooting This section describes the tasks for troubleshooting and resolving issues using the OME–Modular user interface.
2. A non-SAS IOM is detected. 3. An inconsistency is detected in the subcomponent firmware. Drives on compute sled are not visible 1. If the compute sled is configured with a PERC controller and the drives have been reseated or moved, they are rediscovered as "Foreign". 2. If the drives are removed from the storage sled, they cannot be discovered. 3. If a storage sled is replaced, the storage configuration of the earlier sled cannot be applied to the replaced sled.
3. Connect the stacking cable and add the stand-alone member to the same or different chassis group.
A Recommended slot configurations for IOMs The table below contains the recommended IOM slot configurations. Table 20.
Table 21.
B Upgrading networking switch using different DUP versions The following sections provide you the information to upgrade OS10 using different DUP versions. NOTE: When you upgrade VLT peers from 10.4.0E (R3S or R4S) to 10.5.0.1 or later during the maintenance window, it may impact traffic during the upgrade. NOTE: The DUP update procedure is recommended to upgrade OS10 on the MX9116n and MX5108n. Topics: • • • Upgrading networking switch to 10.5.0.7 using DUP Prerequisites for upgrading from 10.5.0.
2. Go to linux prompt using the commands: a. system bash b. sudo -i 3. Go to the SmartFabric Services CLI prompt using the command: python /opt/dell/os10/bin/rest-service/tool/dnv_cli.py 4.
C Upgrading networking switch using CLI NOTE: You can update any network switch with lower versions to 10.5.0.7 directly. However, upgrading to version 10.5.1.6 can be done only from 10.5.0.7. NOTE: Upgrade the MX9116n and MX5108n switches to 10.5.1.6 only if the switches are running 10.5.0.7 or later. While updating, ensure that the IOMs in the group are not more than six per upgrade job. NOTE: To upgrade the networking switch from 10.4.0E (R3S or R4S), upgrade and reload both the VLT nodes simultaneously.
Table 25. Command description Command Description OS10# show image status View the current software download status. e. Install the 10.5.0.5 software image in EXEC mode. Table 26. Command description Command Description OS10# image install image-url Install the software image. Example: OS10# image install image://filename.bin f. (Optional) View the status of the current software install in EXEC mode. Table 27.
NOTE: During the image upgrade process in a VLT setup, when the VLT peers are running different software versions, no configuration changes should be done in any of the VLT peers. Ensure that both the nodes are upgraded to the same version before you make any configuration change.
