Dell EMC OpenManage Enterprise-Modular Edition Version 1.00.
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 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Overview........................................................................................................................................................ 8 Key features........................................................................................................................................................................ 8 New in this release........................................................................................................................................
Interfaces to access OME-Modular...............................................................................................................................28 Viewing chassis hardware............................................................................................................................................... 29 Viewing chassis alerts......................................................................................................................................................
Editing template networks.............................................................................................................................................. 52 Cloning templates............................................................................................................................................................ 52 Exporting templates.................................................................................................................................................
Viewing topology details............................................................................................................................................72 Editing fabric details...................................................................................................................................................72 Deleting uplinks...........................................................................................................................................................
Filtering jobs................................................................................................................................................................89 Viewing job details..................................................................................................................................................... 90 Running 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.
• Multiple chassis management using a single interface—web or RESTful interface. • Management of network IOMs and SmartFabric Services. • Usage of the automation and security features of iDRAC9. New in this release This release of OME-Modular supports: • 20 chassis in a multi-chassis management (MCM) group • Editing VLANs that are already deployed to a server, using a template • Federal Information Processing Standard (FIPS) 140-2 standards. For details, see certificate #2861 at csrc.nist.
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 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. You can update the management module firmware using the following methods: 1 Individual package method—Through OME–Modular web interface or RESTful API.
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.
To log in as a local, Active Directory, or LDAP user: 1 Enter the Username. 2 Enter the Password. 3 Click Login.
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. It shows all the modules (sleds, fans, power supplies, IOMs, and MMs) present in the chassis. A mouse over on each module displays a brief description and health status of the module. Click View Devices to see more details about the modules present in the chassis.
– Topology of the group using View Topology – Name, IP address, and service tag of the lead chassis – Name, IP address, and service tag of the member chassis • Device Health—Displays the health status of the chassis subsystems—chassis, compute sled, networking, and storage. You can click the health status of the individual devices or click All Devices, to view a summary of the devices in the All Devices page.
Initial configuration Dell EMC recommends the following configuration threshold for better performance of the chassis. If the configuration exceeds the threshold, then some features including firmware update, backup, and restore may not work as expected. This may also affect system performance.
NOTE: After setting the time in the lead chassis, wait for the lead chassis time and the member chassis time to synchronize before performing any operation. The time configuration can be disruptive.
The Network configuration section is expanded. 2 In the General Settings section, you can enable or disable NIC, Register with DNS and Auto Negotiation. If you enable Register with DNS, then enter the DNS Name and enable or disable the Use DHCP for DNS Domain Name option. If Auto Negotiation is false or disabled, you can choose network port speed. If the Use DHCP for DNS Domain Name is disabled, then enter the DNS Domain Name.
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 between 10 and 65535. NOTE: For SNMP operations, configure the timeout parameter on the client to facilitate successful completion of the task. You may have to adjust the timeout parameter based on the network latency.
Configuring chassis location To configure the location of the chassis: 1 Click Devices > Chassis > View Details > Settings > Location. The Location configuration section is expanded. 2 Enter the location names for the Data Center, Room, Aisle, and Rack. 3 Enter the number of the Rack Slot and the name of the Location where the rack is located.
• Blink LED • Refresh chassis inventory • Filter the chassis list 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.
– Power Off (Non-graceful)—Turns off the server power, which is equivalent to pressing the power button when the server is turned on. This option is disabled if the server is already turned off. It does not notify the server operating system. – Power Cycle System (Cold Boot)—Turns off and then restarts the server (cold boot). This option is disabled if the server is already turned off. NOTE: When the chassis is power cycled all devices in the chassis are also powered cycled.
• Ensure that the chassis settings are selected for applying to the other chassis—Power, user authentication, alert destination, time, proxy, security, network services, local access. 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.
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. 3 Select the onboarding permission type. 4 Select the configuration settings that you want to propagate to the member chassis.
If the MCM group is created with automatic on boarding policy, no approval is required from the lead chassis. The individual chassis is automatically added to the MCM group to become a member chassis. 4 Log in to the lead chassis and approve the request of the member chassis to join the chassis group.
The backup file is encrypted and cannot be edited. 6 In Optional Devices, select the compute sleds in the chassis that you want backup. The number of selected devices is displayed in the bottom left corner of the Backup Chassis window. 7 Click Backup. A message is displayed indicating that the backup is successful and the chassis Overview page is displayed. You can check the status and details of the backup process on the Montitoring > Jobs page.
A message is displayed stating that the system cannot be accessed during a failover. Troubleshooting in chassis The Troubleshoot option on the OME–Modular home page enables you to use the following options to resolve issues that occur in the chassis: • Extract Log—Use this option to extract application logs and save them to the NFS or CIFS locations on the network. • Diagnostic Commands—Use this option to run diagnostic commands and parameters to troubleshoot the chassis network.
Interface Description • • • • • View alerts, OME–Modular IP or MAC address. Set DHCP Configure OME–Modular static IP settings. View OME–Modular MAC address for the active MM. View the OME–Modular VLAN ID appended to the end of MM IP, if the VLAN is already configured. For more information about the LCD touch panel, see the Dell EMC PowerEdge MX7000 Enclosure Installation and Service Manual. SSH Use SSH to connect to the MX7000 chassis and run RACADM commands locally.
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.
Viewing current configuration Click Application Settings > Network > Current Settings. The current network, IPv4, and IPv6 settings are displayed. Configuring OME–Modular IP address 1 Click Application Settings > Network > Address Configuration. 2 Ensure that the Enable NIC option is selected. 3 Enable the desired 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.
Changing device naming and preference 1 Click Application Settings > Network > Device Name Preference. 2 Select the naming preference. 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.
A list of user account is displayed. 2 Select the account, and then click the required option above the list of accounts. Recovering passwords You must have physical access to the chassis to reset the login credentials to defaults. 1 If a chassis has dual OME–Modular controllers, remove both the modules from the chassis. Else, remove the single OME–Modular controller. 2 On one of the modules, locate the Jumper, refer to the board location—P57 RESET PASSWORD, and then, insert the Jumper.
User Role Chassis Administrator Compute Manager Storage Manager Fabric Manager Viewer Updating device firmware Yes Yes Yes Yes No Creating and managing device templates, identity pools, and logical networks Yes Yes Yes Yes No Managing firmware Yes catalogs and baseline policies Yes Yes Yes No Power budget configuration and management Yes No No No Yes Managing user sessions You can view and terminate existing user sessions using the User Sessions page, if you have the chassis adm
Adding directory services You can create directory services with details. 1 From the main menu, click Application Settings > Users > Directory Services > Add. The Connect to Directory Service window is displayed. 2 Select the directory type from the Type of Directory drop-down list. The available options are: • 3 AD • LDAP Enter a name for the directory service in the Directory Name field. NOTE: The directory name can have a maximum of 255 characters.
Deleting directory services To delete directory services: 1 From the main menu, click Application Settings > Users > Directory Services. 2 Select the directory service that you want to delete and click Delete. Configuring login security settings OME–Modular supports IP range-based access restriction. You can restrict access to only a specified range of IP addresses. You can also configure lockout policies that enforce delays after certain number of failed login attempts.
• The validity of the certificate If you have the security setup privilege, you can perform the following tasks: • • • View the SSL certificate that is deployed. Generate a new certificate signing request (CSR) Upload the server certificate, based on the CSR generated, to replace the default or currently deployed certificate. Uploading certificates To upload the certificate: 1 Click Application Settings > Security > Certificates. 2 Click Upload to browse and upload the certificate.
To configure SNMP alerts, perform the following steps: 1 From the main menu, select Application Settings > Alerts. 2 Click SNMP Configuration. 3 Select Enable to enable the configuration. 4 Enter the Destination Address. You can configure up to four SNMP destinations. 5 Select the SNMP Version. The available SNMP versions are: • SNMP V1 • SNMP V2 NOTE: For MX9116n or MX5108n IOMs, only SNMP V2, is supported. 6 Enter the Community String.
4 Managing compute sleds OME–Modular allows 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.
You can also see information under the following sections: • Operating System Information—Displays the name, version, and hostname of the operating system installed on the compute sled. • Location Information—Displays the location details of the compute sled. • Chassis Information—Displays the details of the chassis on which the compute sled is placed. Click View All to view the list of all activities in the Jobs page.
– 1 Minute – 10 Minutes – 30 Minutes – 1 Hour – Indefinitely • Configuration Profile tasks: – Associate server profiles—You can associate profiles to blade servers. The profile is extracted from the server and is attached to the slot containing the server. – Migrate server profiles—You can migrate a profile from one server to another. The system unassigns the identity from the first server before the migration. If the unassignment fails, the system displays a critical error.
The details include name of the device or component, impact assessment, current version, and baseline version. You can perform the following tasks on the Firmware page: • Update the existing firmware on the compute using Update Firmware. • Downgrade the updated firmware version to the previous version using Rollback Firmware. • Export the firmware baseline report in a .csv format using Export.
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.
NOTE: The storage sled, if assigned to compute sleds that are powered on, causes input/output disruption. Blinking LED You can locate a storage sled within a chassis by making the sled LED blink. This is helpful in identifying a system. To turn on the LED blinking: 1 From the Devices drop down menu, select Storage. 2 Select the storage sled. 3 Click on 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.
Viewing drive details To view the list of drives in the storage sled, click Hardware > Hard Drives. You can assign individual hard drive to a compute sleds. You can update firmware of these drives using iDRAC web interface. 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.
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.
Downgrading storage enclosure firmware Follow these steps to roll back the firmware for a storage enclosure: 1 On the OME–Modular web interface, go to Devices > Storage. 2 Select the system and click View Details. 3 Click Rollback Firmware. 4 Select the available version of the firmware and click Confirm to continue. Managing SAS IOMs The internal connection of the storage subsystem is called "Fabric C", which serves as a communication mode between compute sleds and storage enclosures.
– 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 initiates a cold reboot of the IOM. In this instance, the power is removed from the IOM and the IOM reboots. • Blink LED—Turn on or turn off to identify the IOM LEDs. • Clear Configuration—Delete the storage IOM configuration.
Extracting IOM logs You can collect a log bundle for support by selecting Extract Log. The log bundle collected from the SAS IOM also contains the associated logs from all storage enclosures that are discovered by the IOM even if they are not currently present in the chassis.
6 Managing templates OME–Modular allows you do configure servers based on templates. A server template is a consolidation of configuration parameters 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.
The details that are displayed are—name and description of the template, timestamp when the template was last updated, and the name of the user who last updated it. You can also view the configuration details such as server profile and BIOS information.
If the template has identity attributes, but is not associated with a virtual identity pool, a message is displayed that the physical identities are used for the deployment. Else, the Deploy Template wizard 2 Select the target device on which you want to deploy the template, configure the iDRAC management IP settings, and schedule the deployment. Deploying templates from Template Details page To deploy a template from the Template Details page: 1 On the Template Details page, click Deploy Template.
A message is displayed prompting you to confirm the deletion. 2 Click Yes to proceed. When a template is deleted, the unassigned identity pools in the template are restored to the identity pool.
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.
• • There are errors such as overlap in identity values with an existing pool. Syntax errors while entering the MAC, IQN, or network addresses. Each identity pool provides information about the state of each identity in the pool. The states could be: • • Assigned Reserved 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.
address pool, if the values are within the specified IP address range. The Gateway, Primary DNS, and Secondary DNS server values serve as exclusions from the specified IP Address Range, when applicable. 8 You can select the Include FCoE Identity to enter the Starting MAC Address and select the number of Number of FCoE Identities you want. The WWPN/WWNN values are generated from the MAC address. The WWPN address is prefixed with 0x2001 while the WWNN address is prefixed with 0x2000.
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 25Gb 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.
• Refresh Inventory You must have the device configuration privileges to set up network IOMs and perform configuration tasks on them. 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.
Configuring IOM network settings The network settings for IOMs include configuring the public management IP for the selected management port. 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.
Configuring advanced settings To configure the advanced IOM settings: 1 Click All Devices > I/O Modules > View Details > Settings > Advanced or Devices > I/O Modules > View Details > Settings > Advanced. 2 Select the options to replicate the chassis time and alert settings to the IOM. Configuring ports You can configure breakout, admin status, and MTUs for IOMs. You can configure breakout only for port groups. NOTE: The port description is applicable only to full-switch mode IOMs.
Configuring auto negotiation You can switch auto negotiation (AutoNeg). For DAC cabling, the AutoNeg is enabled by default. For AOC (fiber), the AutoNeg is disabled by default. To switch the AutoNeg: Select the port and click Toggle AutoNeg. The Toggle AutoNeg window is displayed. If Ethernet links are not displayed automatically, switch the auto negotiation setting.
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 4.
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 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.
• • • • • • • • • Guidelines for operating in SmartFabric mode SmartFabric network topologies Switch to switch cabling Upstream network switch requirements NIC teaming restrictions CLI commands available in Fabric mode Viewing fabric details Adding fabric Deleting fabric 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 switches in A1/A2 or B1/B2 in one chassis are i
2 x MX5108n Ethernet Switches in the same chassis The MX5108n Ethernet Switch is supported only in single chassis configurations. The switches must be placed in slots A1/A2 or slots B1/B2. A SmartFabric cannot include a switch in Fab A and a switch in Fab B. 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.
For the MX5108n, ports 9 and 10 are used. Port 10 operates at 40GbE instead of 100GbE because all VLT links must run at the same speed. Ensure that you use a cable or optic fibre that supports 40GbE. 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.
NIC teaming restrictions NIC teaming is suggested for redundancy unless a particular implementation recommends against it. There are two main kinds of NIC teaming: 1 Switch Dependent—Also referred to as 802.3ad or Dynamic Link Aggregation. The switch dependent teaming method uses the LACP protocol to understand the teaming topology. This teaming method provides Active-Active teaming and requires the switch to support LACP teaming.
– mode— Enable a spanning-tree mode, such as RSTP or MST. – mst— Configure multiple spanning-tree (MST) mode. – rstp— Configure rapid spanning-tree protocol (RSTP) mode. – vlan— Configure spanning-tree on a VLAN range. Viewing fabric details To view details an existing fabric: • From the Devices drop down, select Fabric. • From the fabrics table, select the fabric and click View Details. The Fabric Details page is displayed. Adding fabric To add a fabric: 1 Click Devices > Fabric .
4 Enter Name, Description, select the Uplink Type, and then click Next. The available options are: • Ethernet—You can pick one or more Ethernet ports across switches to form a LAG. The network can be of any type. For example: Ethernet. • FCoE—You can pick one port from an IOM and associate a single network of FCoE type. This is for FCoE connectivity that connects to another switch that connects to the FC network. For single fabric, you can have two FCoE uplink, one from each IOM.
5 Select the necessary Switch Ports and select any Tagged Networks or Untagged Networks. To configure new network other than the existing ones, click Add Network and enter the network details. For more details see, Adding Network. NOTE: You cannot edit the ports or networks when uplinks are in FCoE, FC Gateway, or FC Direct Attach modes. Viewing topology details The fabric topology image displays only the operational status of the ports. If the operational status is "up", a check mark is displayed.
After the fabric is deleted, the IOM reboots.
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 Fabric mode. For servers connected to switches in Full Switch mode, the VLAN information is ignored. In tagged networks, a port handles multiple VLANs.
Network Traffic Type Description QoS Setting Cluster Interconnect Used for cluster heartbeat VLANs 5 Hypervisor Management Used for hypervisor management connections such as the ESXi management VLAN 5 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 sup
NOTE: In fabric mode, do not delete VLAN from OME–Modular, if the VLAN is associated with any uplink. Exporting network configurations To export the network configuration: 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. Deleting network configurations To delete a network: On the Networks page, select the network 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 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.
• Deleting firmware Creating baselines To create a firmware baseline: 1 Click Configuration > Firmware > Create Baseline . The Create Firmware Baseline window is displayed. 2 Select the catalog type, enter a name and description for the baseline. 3 Click Add. 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.
The catalogs can be sourced from the following locations: • Dell website—You can specify the proxy parameters. to enable the application to access the internet from your network. The proxy parameters include network address and optional credentials—user name and password. The proxy settings are configured during initial setup or on the Application Settings > Network page. Multiple catalogs could be posted on the Dell website.
• Network Path Editing catalogs You can only modify the catalog name, network share address, and catalog filepath. To edit catalogs: 1 On the Catalog Management page, select the catalog that you want to edit and click Edit. The Edit Firmware Catalog window is displayed. 2 Make the required changes. 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.
• You can browse for a firmware package that has the previous firmware version. For Network IOMs, the availability of rollback information depends on the status of the Network IOM (Full Switch or Fabric) and the firmware update method. If the firmware is updated on nodes in the fabric, the rollback information is available on the node on which the firmware update is initiated.
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.
• Start Date and End Date—To view alerts from a specific period. • Source Name—To view the alerts from a specific system. • Category and Subcategory—To view alerts of specific category. • Message—To view alerts containing a specific word in the message column. Selections that are made in the filters are applied at real time. 4 To reset the filters, click Clear All Filters. Acknowledging alert logs You can acknowledge alert logs that are not already acknowledged.
The alert logs are exported in .csv format. Deleting alert logs You can delete one or multiple alert logs. To delete alert logs: On the Alert Log page, select the alert logs that you want to delete and click Delete. A message is displayed prompting to you confirm the action. Alert policies The alert policies feature enables you to view critical alerts and perform specific tasks. To view the list of alert policies, click Alerts > Alert Policies.
The available options are: • All • Unknown • Info • Normal • Warning • Critical The Actions tab is displayed. 8 Select the alert action and click Next. The available options are: • Email (Enable)—Click Enable to view the Email Configuration window where you can configure the email settings for the alert. • SNMP Trap Forwarding (Enable)—Click Enable to view the SNMP Configuration window where you can configure the SNMP settings for the alert.
To delete alert policies: 1 On the Alert Policies page, select the alerts that you want to delete and click Delete. A message is displayed prompting you to confirm the action. 2 Click Yes to proceed. Alert definitions You can view description of the alert logs generated for events that associated with the chassis, and devices and components in the chassis, on the Alerts Definition page.
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.
To export audit logs: 1 On the Audit Logs page, select the audit logs that you want to export. 2 Click Export, and select Export Selected. Else, you can click Export > Export All, to export all the audit logs. 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.
– Disabled • Job Type—To view jobs based on the type. The available options are: – Debug Logs – Settings Update – Software Rollback – Device Action – Restore – Device Config – Chassis Profile – Inventory – Update – MCM OffBoarding – Backup – Profile Update – Quick Deploy – MCM OnBoarding – MCM Group • Last Run Start Date and Last Run End Date—To view jobs based on the last run period. Selections made in the filters are applied at real time. To reset the filers click Clear All Filters.
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. Running jobs If a job is running from over 24 hours, stop the job after analyzing the job details. Rerun the job, if required. You can use theJobs page to run jobs immediately. To run jobs: On the Jobs page, select the jobs that you want to run and click Run Now.
16 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.
A Recommended slot configurations for IOMs The table below contains the recommended IOM slot configurations. Table 7.
Slot A1 Slot A2 Slot B1 Slot B2 25G PTM Empty 25G PTM Empty 10GBT PTM Empty 10GBT PTM Empty MX9116n MX9116n MX9116n Empty MX5108n MX5108n MX5108n Empty MX7116n MX7116n MX7116n Empty 25G PTM 25G PTM 25G PTM Empty 10GBT PTM 10GBT PTM 10GBT PTM Empty MX9116n MX9116n MX5108n MX5108n MX9116n MX9116n 25G PTM 25G PTM MX9116n MX9116n 10GBT PTM 10GBT PTM MX9116n MX7116n MX5108n MX5108n MX7116n MX9116n MX5108n MX5108n MX9116n MX7116n 25G PTM 25G PTM MX7116n MX9
LEGEND: *—Combining two types of Pass-Through Modules (PTMs) is supported.
