Dell EMC OpenManage Enterprise-Modular Edition Version 1.20.00 for PowerEdge MX7000 Chassis User's Guide June 2020 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.
Contents Chapter 1: Overview...................................................................................................................... 8 Key features..........................................................................................................................................................................8 New in this release..............................................................................................................................................................
MCM dashboard.......................................................................................................................................................... 37 Controlling chassis power................................................................................................................................................37 Backing up chassis.......................................................................................................................................................
Deploying templates......................................................................................................................................................... 66 Deploying templates from Template Details page............................................................................................... 67 Editing templates...............................................................................................................................................................
Chapter 11: Managing networks................................................................................................... 89 SmartFabric VLAN management and automated QoS.............................................................................................89 Defining networks............................................................................................................................................................. 90 Editing VLANs................................................
Deleting jobs................................................................................................................................................................106 Chapter 16: Use case scenarios.................................................................................................. 107 Assigning backup to the MCM Lead........................................................................................................................... 107 Creating chassis group with backup lead...
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: ● ● ● ● ● ● ● ● ● ● ● ● ● ● Deploying templates on empty slots or slots that compute sleds occupy. Reclaiming MAC identities after removing profiles that are associated with blade servers. Synchronizing VLAN definitions of OME-Modular and OpenManage Enterprise. Alert notifications when a chassis is onboarded. Configuring Forward Error Correction (FEC) for SmartFabrics. Propagating VLANs without server reboot.
Other documents you may need For more information about managing your system, access the following documents: 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 MX 7000 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 the management module firmware The methods of updating the management module firmware and the MX7000 firmware components are described in this chapter. In MCM environment, perform the firmware update for all devices from the lead chassis. Also, select the IOMs and storage sleds as individual devices and not as chassis components, for a successful firmware update. NOTE: Ensure that you upgrade the OME-Modular firmware before upgrading OS10.
Updating MX7000 components using OME-Modular 1.20.00 You can upgrade the following components of MX7000 using OME-Modular 1.20.00. The following table lists the new versions of the MX7000 components: Table 2. MX7000—OME-Modular 1.20.00 solution baselines Component Version iDRAC with Lifecycle Controller 4.20.20.20 Dell EMC Server BIOS PowerEdge MX740c 2.8.2 Dell EMC Server BIOS PowerEdge MX840c 2.8.2 QLogic 26XX series Fibre Channel adapters 15.05.14 QLogic 27XX series Fibre Channel adapters 15.
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 the scheduled single maintenance window. Before proceeding with the update, review and resolve any recurring port alerts that are reported on the OME-Modular Alerts page. NOTE: The message ID for an operational port is NINT0001 and that for a not operational port, NINT0002. Update the components in the following order: 1.
Emulex Picard-16/Picard-32 adapters, as applicable. Go to dell.com to download the latest device drivers associated with the firmware update. Updating OME-Modular to 1.20.00 If the current version is 1.00.01 or 1.00.10, update OME-Modular to 1.10.00 or 1.10.10 before updating to 1.10.20. You can update to OME-Modular 1.20.00 only if the existing version of OME-Modular on your system is 1.10.20. For more information, see Updating OME-Modular to 1.10.10 and Updating OME-Modular to 1.10.
For steps to upgrade from different versions, see the sections, Upgrading from 10.5.0.5 and Upgrading from versions earlier than 10.5.0.5. 7. Go to Monitoring > Jobs page, to view the job status. Upgrading from 10.5.0.5 ● When updating, ensure to update the IOMs in groups no larger than four per upgrade job. ● If there are two switches in a full-switch mode VLT, each switch should be part of different upgrade batch for redundancy. ● If there are two switches in a SmartFabric, select only one switch.
3 Logging in to OME-Modular You can log in to OME–Modular as a local, Active Directory, or generic LDAP user. OME–Modular supports a maximum of two Active Directory or LDAP server configurations, each.
Logging in to OME-Modular as Active Directory or LDAP user To log in to OME–Modular as an Active Directory (AD) or LDAP user: 1. Add directory service 2. Import directory group 3. Log in with directory user credentials To add directory service: 1. From the menu bar in the OME–Modular web interface, click Application Settings > Users > Directory Services > Add. The Connect to Directory Service window is displayed. 2. Select AD or LDAP, and enter the appropriate information. 3.
● Help icon ● Information icon The home page displays a dashboard with high-level information about the system and the subcomponents. You can also view the job activity and events. To view the job activity, click and to view events, click . To return to the OME–Modular home page, click the OME–Modular logo or click Home. ● Chassis graphical view—On left of the page, a graphical view of the front and rear chassis is displayed.
The most relevant results are displayed in a list. Click Show More to the view all the records. Select or clear check boxes of the components which you want to include or exclude from the search results. By default, all the options are selected. Click a search result record to go to the Alerts Log page. You can use the search feature as described in the following examples: ● ● ● ● ● Search Search Search Search Search for jobs using Job IDs.
Page name Fields ● ● ● ● ● ● ● 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 Device, Entitlement ID, Description, License Type Device Management Info ● ● ● ● MAC Address Network Address Device Name Discovery Profile Viewing alerts The Alerts section displays the specific types of alerts such as Critic
NOTE: If a member chassis is added to a chassis group based on a "Join Group" request from the member chassis, the status of the member chassis is displayed as "Unknown" for some time, on the MCM dashboard. Viewing lists of chassis in an MCM group On the OME–Modular home page, the list of chassis that are part of the group is displayed on the left. The list displays the model, IP address, and the Service Tag of the chassis. The lead chassis is labeled for easy identification.
Component Count Identity pool 501 Network (VLAN) 214 Catalog 50 Baseline 50 To configure a chassis: 1. Click Devices > Chassis > View Details > Configure > Initial Configuration. The Chassis Deployment Wizard is displayed. NOTE: You can configure the chassis using an existing chassis profile. 2. In the Import Profile tab, click Import to open the Import Profile window. Enter details of the network share, where the chassis profile is located and click Import. 3.
Configure chassis power To configure the chassis power settings: 1. Click Devices > Chassis > View Details > Settings > Power. The Power configuration section is expanded. 2. Select Enable Power Cap to specify the maximum power consumption capacity for the chassis. The Power Cap limits the power consumption of the chassis. When the power cap is reached, the sleds are throttled based on their power priority. You can specify the capacity in Watts, BTU/h, or percentage.
1. Click Devices > Chassis > View Details > Settings > Network. The Network configuration section is expanded. 2. In the General Settings section, you can enable or disable NIC, Register with DNS, and Auto Negotiation. By default, the Enable NIC check box is selected. If you enable Register with DNS, then enter the DNS Name of the chassis that you want to register with a DNS server. You can access OME-Modular using the existing FQDN even after the Register with DNS option is disabled in the application.
● ● ● ● ● ● ● Enable Autoconfiguration IPv6 Address Prefix Length Gateway Use DHCPv6 to Obtain DNS Server Addresses Static Preferred DNS Server Static Alternate DNS Server NOTE: The static IPv6 IP address that is already configured is applied and displayed in OME–Modular when the configuration is changed from static to DHCP IP. 7. Enable or disable the VLAN for the chassis. You can configure the VLAN settings only if the Register with DNS check box is cleared.
You can view the remote RACADM option on the web interface only if you have the chassis administrator privilege. NOTE: A log for remote RACADM session (login or logout) is displayed in the Audit Logs page, irrespective of the remote RACADM status. If the remote RACADM option is disabled, the feature does not work. NOTE: Any change in the attribute settings leads to IP drop or unavailability of the OME–Modular web interface for some time. However, the OME–Modular web interface recovers automatically. 9.
● ● ● ● ● ● English French Spanish German Japanese Chinese By default, the text is displayed in English. 11. Select the Enable Chassis Direct Access text box to enable accessing the MX7000 chassis from a host such as a laptop or server, using a USB On-The-Go (OTG) cable. If the Enable Chassis Direct Access check box is cleared, the existing chassis direct sessions are disconnected and the Chassis Direct LED turns off. When the feature is disabled, you cannot connect the laptop to the chassis.
Table 4. Chassis Direct—LED blink status and description (continued) Error code Chassis Direct LED blink status Description and resolution 2 Amber The USB network link does not come up as the chassis internal USB operation failed. Resolution—If the issue persists, reattach the USB cable to the laptop or perform and AC power cycle of the chassis. 3 Amber The USB network link fails to come up owing to an issue on the host laptop. Resolution—If the issue persists, reattach the USB cable.
To configure the Quick Deploy settings: 1. Click Devices > Chassis > View Details > Settings > Quick Deploy. The Quick Deploy configuration section is expanded. 2. Enter and confirm the password to access the iDRAC user interface. The password can be up to 20 characters in length. NOTE: If any iDRAC IP configuration is modified, the SSO for the SLEDs is functional from the OME-Modular console only after the default inventory task or manual inventory refresh is complete. 3.
NOTE: When a chassis is power cycled, the inventory of the compute sleds and IOMs may be displayed in the OME– Modular web interface after three to five minutes. NOTE: Maintain a minimum interval of two minutes between removing and inserting each device. NOTE: After a chassis power off, the compute SLEDs are polled based on the event from the chassis. Each event from the chassis triggers a health-poll. You may see multiple connection loss events from compute SLEDs.
NOTE: When the chassis is power cycled all devices in the chassis are also powered cycled. The management module does not get power cycled. However, the alerts logged may report that the connectivity was lost due to a power cycle operation. ○ Power Off (Graceful)—Notifies the server operating system to turn off the chassis. This option is disabled if the chassis is already turned off.
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.
Before creating an MCM group, ensure that the MX7000 management networks are wired together in a stacked configuration. The stacked configuration helps in surviving: ● ● ● ● A single network cable failure A single management module failure Power loss owing to any chassis in the stack Failover of a chassis in the stack NOTE: If any of the issues that are listed above occur, the management network access to all components in the daisychained group may be interrupted for up to 10 minutes.
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. Select the configuration settings that you want to propagate to the member chassis.
Assigning backup lead In a multi-chassis environment, the lead chassis may sometimes fail temporarily or retire. In such situations, it is necessary to nominate a member chassis in the MCM group as a backup to the lead chassis. The backup lead chassis is promoted as a lead chassis when the existing lead chassis fails or retires. 1. On the MCM dashboard, click Configure > Edit Backup Lead Settings. The Edit Backup Lead Settings window is displayed.
Retiring lead chassis You can use the retirement process of the existing lead chassis to make it a member chassis of the existing group or a standalone chassis. 1. On the MCM dashboard, click Configure > Retire Lead Chassis. The Retire Lead Chassis window is displayed. 2. Select one of the following options: ● Make it a member of the current group. ● Make it a stand-alone chassis. 3. Click Retire. Also, see the section, Use case scenarios.
○ DHCP is configured, ensure that the cable is connected to a Top of Rack (TOR) switch that has connectivity to the DHCP server. A message is displayed prompting you to confirm your action. 2. Click Confirm to proceed. Backing up chassis Back up the chassis and compute sled configuration for later use. To backup the chassis, you must have administrator access with the device configuration privilege.
5. If the Share Type is CIFS, enter the Domain, Username, and Password to access shared location. Else, go to step 6. 6. In the Restore File Password section, enter the Encryption Password to open the encrypted backup file. 7. Click Restore to restore the chassis. A message is displayed indicating that the chassis is successfully restored. You can check the status and details of the restore process on the Montitoring > Jobs page.
Interfaces to access OME-Modular After configuring the network settings in OME–Modular, you can remotely access OME-Modular using various interfaces. The following table lists the interfaces that you can use to remotely access OME–Modular. Table 5. Management module Interfaces Interface Description Web interface Provides remote access to OME–Modular using a graphical user interface.
Table 5. Management module Interfaces (continued) Interface Description Redfish provides the following benefits over existing server management methods: ● ● ● ● Increased simplicity and usability High data security Programmable interface that can be easily scripted Follows widely used standards For more information, see the OME and OME - Modular RESTful API Guide available at https://www.dell.com/openmanagemanuals. SNMP Use SNMP to: 1. Download the OME-Modular MIB file from the https://www.dell.
Viewing chassis alerts On the OME–Modular home page, click Alerts to view details of the alerts triggered for the events that occurred in the chassis. You can also view the chassis hardware details by clicking Devices > Chassis > View Details > Alerts. You can sort the list of alerts based on the following advanced filters: ● ● ● ● ● ● ● ● Severity Acknowledge Start Date End Date Source Name Category Subcategory Message Select an alert to view the summary of the alert.
2. Ensure that the Enable NIC option is selected. 3. Enable the required IP version-IPv4 or IPv6. NOTE: The IOM and OME–Modular must be registered in the DNS. Else, the message, "Warning: Unit file of rsyslog.service changed on disk, 'systemctl daemon-reload' recommended.", is displayed. NOTE: After rebooting OME–Modular, the public interface with the OME–Modular IP is available after 12 minutes approximately. 4. Enable the DHCP option, and enter the IP address and other details.
Configuring OME–Modular date and time settings 1. Click Application Settings > Network > Time Configuration. 2. Select the Use NTP check box, if required, and enter the NTP server details. 3. Select the required time zone. NOTE: Any change in the attribute settings leads to IP drop or unavailability of the OME–Modular web interface for some time. However, the OME–Modular web interface recovers automatically. Configuring OME–Modular proxy settings 1.
Table 6. Ports and protocols that are supported in OME-Modular Port number Protocol Port type Maximum encryption level Source Direction Destination 22 SSH TCP 256-bit External application In OME-Modular Required for incoming only if FSD is used. OME-Modular administrator must enable this port only while interacting with Dell EMC. 25 SMTP TCP None OME-Modular Out External Application To receive email alerts from OpenManage Enterprise.
Table 6. Ports and protocols that are supported in OME-Modular (continued) Port number Protocol Port type Maximum encryption level Source Direction Destination Usage the web interface. 514** Syslog TCP None OME-Modular Out Syslog Server To send alert and audit log information to Syslog server 546 DHCP TCP None OME-Modular Out 636 LDAPS TCP None OME-Modular Out External Application AD/ LDAP login for Global Catalog.
NOTE: Do not use "system" as a user name. 4. Enter the Password and Confirm Password. The password can be 8-32 characters long and contain at least one of the following: ● Number ● Special character—The supported special characters are - +, &, ?, >, -, }, |, ., !, (, ', ,, _, [, ", @, #, ), *, ;, $, ], /, %, =, <, :, {, I ● Uppercase letter ● Lowercase letter 5. Select a role. 6. Select Enabled to enable the account immediately after you create it.
User roles and privileges Table 7.
Terminating user sessions 1. On the Users page, click User Sessions. You can view the details of the users who are logged in. 2. Select the user from the list and click Terminate. A message is displayed prompting you to confirm the termination. Importing Directory Group You can import Active Directory groups and map them to the existing OME–Modular groups. To import the Active Directory groups: 1. On the Users list page, click Import Directory Group. The Import Directory window is displayed. 2.
a. If you have selected the directory type as AD, enter the following details: ● ● ● ● Server Port number—The server port number can be between 1 and 65535 Network Timeout and Search Timeout in seconds Select the Certificate Validation checkbox Click Select a file to browse and upload a certificate b.
Enabling FIPS mode The United States government agencies and contractors use the FIPS standards. FIPS Mode is intended to meet the requirements of FIPS 140-2 level 1. To enable FIPS mode, click Application Settings > Security > Federal Information Processing Standards (FIPS) NOTE: After enabling the FIPS mode or reset configuration operation, wait for sometime for the application to become stable. Managing certificates You can view details of the SSL certificates on the Certificates page.
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. Configuring SNMP alerts The SNMP alerts contain the service tag of the chassis as one of the parameters in the trap. Third-party consoles can use this information to correlate the traps with the system.
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 8. 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 9. 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.
● ● ● ● ● ● ○ Turn on or turn off—When you turn off the IOM, the status of the IOM is "Offline". As a result, status of the peer IOM may be "Active". When you power cycle the IOM, it causes a warm reboot of the IOM. ○ 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.
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.
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. NOTE: For MX5108n and MX9116n IOMs, the default prefix length of the DHCP IP is 128 bits, though the DHCP server is configured for 64 bits. 4. In the IPv6 Settings section, select Enable IPv6. 5. Enter the IPv6 Address, select the Prefix Length.
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 OS10 administrator password The OS10 admin user account is the default administrator account that is used to configure OS10. To configure the OS10 administrator account password: 1.
Select the port and click Toggle Admin State. The Toggle Admin State window is displayed. Configuring Maximum Transmission Unit You can configure the Maximum Transmission Unit (MTU) for full-switch and fabric mode IOMs. To configure MTU: 1. Click Devices > I/O Modules > View Details > Hardware > Port Information. 2. Select the Ethernet port and click MTU. The Configure MTU window is displayed. 3. Select the MTU Size. The approximate value for MTU is 1500 bytes.
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.
Additional chassis only have FEMs and the appear as the image below. Table 10. Fabric topology Chassis Slot Module Chassis 1 A1 MX9116n FSE A2 MX7116n FEM A1 MX7116n FEM A2 MX9116n FSE A1 MX7116n FEM A2 MX7116n FEM Chassis 2 Chassis 3-10 You can also use Fabric B to create a second scalable fabric: NOTE: The OME-Modular firmware version 1.20.00 supports additional but complex topologies. For more information, see the PowerEdge MX Network Architecture Guide available at https://www.dell.
The following restrictions are applicable when implementing a scalable fabric in both fabric slot A and fabric slot B: ● IOM placement for each scalable fabric must be the same within the same chassis. For example, if the FSE for the first scalable fabric is in Slot A1, then the second FSE must be in slot B1 in the same chassis, and so on. ● For chassis that only contain FEMs, all four FEMs must connect to the same chassis with the FSEs.
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.
• • • • • 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.
1. If NPAR is NOT in use, both Switch-Dependent (LACP) and Switch Independent teaming methods are supported. 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.
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. 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.
2. In the fabrics table, select any fabric and click View Details. 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.
2. Select the fabric for which you want to add or remove the VLAN. 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 14. Network traffic types - QoS settings (continued) Network Traffic Type Description QoS Setting Storage - iSCSI Used for iSCSI VLANs 5 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.
On the Networks page, select the desired network and click Export. The network details are exported in a .csv format to a local drive on your system. 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.
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 web site 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.
The Add Firmware Catalog window is displayed. 4. Select the catalog source. 5. In the Create Firmware Baseline window, select the devices and groups for which you want to create the baseline. After the baseline is created, a message is displayed and a compliance check is performed on the baseline. The status of the job is displayed on the Firmware page. NOTE: If the baseline is created from the catalog, the information of the associated baseline is displayed.
downloading it, the modified catalog is not downloaded. If the repository type is NFS and the catalog file is not available on the specified NFS server, the system uses the catalog file that was last fetched. To view the list of catalogs: On the Firmware Compliance page, click Catalog Management. The Catalog Management page is displayed. You can select a catalog to view the summary on the right-side.
NOTE: The HTTPS share feature with proxy does not work when authentication is enabled for both the proxy and HTTPS share. 4. Select the mode of updating the catalog. The available options are: ● Manually ● Automatically The default mode is manual. 5. Select the Update Frequency. ● Daily ● Weekly The time can be in HH:MM format. Editing catalogs You can only modify the catalog name, network share address, and catalog filepath. To edit catalogs: 1.
2. Select the Update Now option to update the firmware immediately or Schedule Later to update the firmware on the chosen date and time. NOTE: If the system displays the local clock on the Time Configuration page even after you configured the NTP servers, reconfigure the NTP servers. NOTE: During firmware update, when the active MM reboots and the standby MM is active, some messages on the Execution Details page for the firmware update are not displayed.
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.
On the Alert Policies page, select the alerts that you want to enable and click Enable. 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.
● ● ● ● Message Contains—To view alerts containing a specific word in the message column. 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.
○ Inventory ○ 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.
Sometimes after a firmware update, racreset or management module failover, a message stating that the alerts could not be retrieved is displayed. The message that is displayed does not impact the functionality of OME–Modular. 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.
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.
iv. Do not delete fabrics from the old lead chassis as deleting the fabrics can lead to network loss once the old lead is added back to the network. v. On the old lead, run a force “reset configuration” using the following REST API payload: 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.
17 Troubleshooting This section describes the tasks for troubleshooting and resolving issues using the OME–Modular user interface.
1. One or more subcomponents are faulty. 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.
The lead chassis becomes a stand-alone chassis. 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 15.
Table 16.
B Updating OME-Modular to 1.10.10 If the current version of OME-Modular on your system is 1.00.01 or 1.00.10, you must first update the OME-Modular version to 1.10.10 before updating to OME-Modular 1.10.20. Perform the following steps to update to 1.10.10: 1. Click Devices > Chassis. A list of all the available chassis is displayed. 2. In the list header, select the checkbox to select all the chassis on the current page. If there are multiple pages, then go to each page and select the checkbox. 3.
C Updating OME-Modular to 1.10.20 If the existing version of OME-Modular on your system is 1.00.01, 1.10.00 or 1.10.10, you must update the version to 1.10.20 before updating to 1.20.00. To update the OME-Modular version 1.10.20: 1. Click Devices > Chassis. A list of all the available chassis is displayed. 2. In the list header, select the checkbox to select all the chassis on the current page. If there are multiple pages, then go to each page and select the checkbox. 3.
D Updating Fabric Switching Engine and Ethernet Switch Gather following information required to run the updates. NOTE: For the network switch versions 10.4.0.R3S and 10.4.0.R4S, skip steps 1 and 2 and go to step 3. 1. Identify and note down the Switch SERVICE-TAG and its ROLE in the smart fabric cluster by running the command, show smartfabric cluster, on the Switch CLI. Run this command on all the Switches in a single chassis or chassis group.
ip_address: fde1:53ba:e9a0:de14:2204:fff:fe21:9f49 Chassis Tag ARH0009 IOM Service Tag HRA0036 Role BACKUP IP Address fde1:53ba:e9a0:de14:2204:fff:fe20:56c9 Chassis Tag ARH0005 IOM Service Tag HRA0017 Role BACKUP IP Address fde1:53ba:e9a0:de14:2204:fff:fe21:9f49 Chassis Tag ARH0010 IOM Service Tag HRA0037 Role BACKUP IP Address fde1:53ba:e9a0:de14:2204:fff:fe12:e8c3 Chassis Tag ARH0005 IOM Service Tag HRA0020 Role MASTER IP Address fde1:53ba:e9a0:de14:2204:fff:fe21:e749 dnv$ This command is applicable to ne
E Upgrading networking switch using CLI 1. Upgrade the master Networking I/O Module after all the members in the chassis-group are upgraded. 2. If the chassis-group has MX5108n and MX9116n, then upgrade the MX5108n Networking I/O Modules first (non-Master) followed by upgrade of the MX9116n Networking I/O Modules. 3. If you want to upgrade multiple Networking I/O Modules, ensure that not more than two Networking I/O Modules are upgraded concurrently.
f. (Optional) View the status of the current software install in EXEC mode. Table 22. Command description Command Description OS10# show image status View the status of the current software install. g. Change the next boot partition to the standby partition in EXEC mode. Use the active parameter to set the next boot partition from standby to active. Table 23. Command description Command Description OS10# boot system standby Change the next boot partition to standby. h.
