Dell EMC OpenManage Enterprise-Modular Edition Version 1.00.01 for PowerEdge MX7000 Chassis User's Guide September 2019 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 - 2019 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...................................................................................................................... 7 Key features.......................................................................................................................................................................... 7 Supported platforms...........................................................................................................................................................
Viewing current configuration.................................................................................................................................. 27 Configuring users and user settings....................................................................................................................... 28 Configuring login security settings..........................................................................................................................32 Configuring alerts.............
Configuring IOM settings................................................................................................................................................ 52 Configuring networking settings............................................................................................................................. 52 Configuring root password........................................................................................................................................
Chapter 14: Monitoring alerts and logs........................................................................................ 74 Alert log................................................................................................................................................................................74 Filtering alert logs........................................................................................................................................................
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.
Platforms: ● ● ● ● ● ● ● ● ● ● ● ● PowerEdge MX7000 PowerEdge MX740c PowerEdge MX840c PowerEdge MX5016s PowerEdge MX5000s SAS Switch PowerEdge MX 25Gb Ethernet Pass-Through Module MX 10GBASE-T Ethernet Pass-Through Module Dell EMC MX9116n Fabric Switching Engine Dell EMC MX5108n Ethernet Switch Dell EMC MX7116n Fabric Expander Module Brocade MXG610s Fibre Channel Switching Module PowerEdge MX9002m Management module Supported web browsers OME–Modular is supported on the following web browsers: ● Google Chr
Table 1. List of other documents for reference (continued) Name of the document Brief introduction of the document Dell EMC PowerEdge MX5016s and MX5000s Installation and Service Manual This document provides information about installing and replacing components in the PowerEdge MX5016s storage sled and PowerEdge MX5000s SAS IOM. Accessing documents from Dell support site You can access the required documents in one of the following ways: ● Using the following links: ○ For OpenManage documents — www.
2 Updating the management module firmware You can update the management module firmware using the following methods: 1. Individual package method—Through OME–Modular web interface or RESTful API. 2. Catalog-based compliance method To update the firmware using the Individual package method: 1. Download the DUP from the Dell.com/support/drivers. 2. On the OME–Modular web interface, navigate Devices > Chassis and select the chassis for which you want to update the firmware. 3. Click Update Firmware.
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 1. 2. 3. log into OME–Modular as an Active Directory (AD) or LDAP user: Add directory service Import directory group 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.
NOTE: When you refresh inventory and power the chassis on after the chassis is AC power cycled, the inventory of the compute sled and IOM may be displayed after 3-5 minutes. NOTE: If chassis has not been powered on after the AC Power Cycle operation, the inventory status is displayed as "unknown". Viewing alerts The Alerts section displays the specific types of alerts such as Critical, Warning, and Unknown.
A list of all the devices at the bottom of the All Devices page. You can select a device to view its summary on the right side of the list. You can sort the list using Advanced Filters.
8. Select the Configure all devices to use following catalog check box, select the network share type and click Catalog to open the Add Firmware Catalog window. 9. Enter a name for the catalog, select the catalog source, and click Finish to save the changes and return to the Chassis Deployment Wizard. 10. Click Next to view the Proxy tab and configure the proxy settings. OME–Modular uses the proxy settings to access the Dell EMC website for the latest catalogs.
To configure the chassis network: 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. 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.
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. 3. Enter the Community String. 4.
Configuring Quick Deploy options The Quick Deploy feature enables you to configure the password to access the iDRAC user interface, IOMs, and IPv4 and IPv6 settings. These settings can be applied to existing compute sleds or IOM devices immediately. You can apply the quick deploy settings to compute sleds when they are inserted into the chassis, later. Quick deploy settings are validated when the job is run. If an invalid parameter is used, the quick deploy job fails.
● ● ● ● ● ● Health State Name Contains IP Address Contains Service Tag Contains Model Viewing chassis overview On the chassis Overview page, you can click View Slot Information to view the compute sled slot details. A graphical representation of the chassis is displayed on the left side. Information about the chassis is displayed below the graphical representation.
Chassis groups You can group many chassis to form a multi-chassis management (MCM) group. An MCM group can have one leader chassis and nine 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 can be of wired type. In the wired type, the chassis is daisy-chained or wired through a redundant port on the management module.
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.
The dashboard of a leader chassis displays a summary of the health information, recent activity, and recent alerts of the member chassis. You can select a member chassis to view its details. The current membership ID of the chassis is displayed on the left side. Adding member chassis to groups You can add members to the chassis groups from the Overview page of the lead chassis or from the member chassis. Adding member chassis from lead chassis To add a member chassis to the group from the lead chassis: 1.
● ● ● ● ● ● ● ● ● ● Setup configuration Power configuration Chassis network configuration Local access configuration Location configuration Slot configuration OME–Modular network settings Users settings Security settings Alert settings You can use the backed-up configuration in other chassis. To create a chassis backup: 1. On the chassis Overview page, click More Actions > Backup. The Backup Chassis window is displayed. 2.
2. Select the Share Type. 3. Enter the network share address and path. 4. If the Share Type is CIFS, enter the Domain, User Name, and Password to access the shared location. 5. Click Export. Managing chassis failover Failover is applicable in dual management module configuration and is the process of transferring the active role to the standby management module. Reboot the active management module and re-initialize the stand-by management module to assume the active role.
Table 2. Management module Interfaces (continued) Interface Description For a list of supported web browsers, see the Supported browsers section in the OME - Modular for PowerEdge MX7000 Chassis Release Notes available at www.dell.com/ openmanagemanuals. Remote RACADM command line interface Use this command line utility to manage OME–Modular and its components. You can use remote or firmware RACADM: ● Remote RACADM is a client utility that runs on a management station.
Table 2. Management module Interfaces (continued) Interface Description KVM You can have a maximum of one KVM session open at a time. Viewing chassis hardware On the OME–Modular home page, click Hardware to view details of the hardware components that are installed in the chassis. You can also view the chassis hardware details by clicking Devices > Chassis > View Details > Hardware.
Configuring OME–Modular The Application Settings menu on the home page enables you to configure various settings for OME–Modular. The settings include the following: ● ● ● ● Network Users Security Alerts 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.
3. Enter the proxy address and the port number. 4. If the proxy requires authentication, select Enable Proxy Authentication and enter the credentials. You can enable proxy authentication only if the Enable HTTP Proxy Settings option is selected. 5. Enter the proxy user credentials. Changing device naming and preference 1. Click Application Settings > Network > Device Name Preference. 2. Select the naming preference.
Enabling, disabling, and deleting users 1. Click Application Settings > Users. 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.
Table 3.
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: ● AD ● LDAP 3. Enter a name for the directory service in the Directory Name field. NOTE: The directory name can have a maximum of 255 characters. 4.
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. Configuring login IP range 1. Click Application Settings > Security > Login IP Range. 2. Select Enable IP Range. 3. Enter the IP range in the CIDR format. For IPv4, enter the IP address in the format—192.168.100.14/24.
Generating certificate signing request 1. Click Application Settings > Security > Certificates. 2. At the bottom-right of the page, click Generate Certificate Signing Request. 3. Enter the required details and click Generate. ● OME–Modular does not create an SSL certificate on time change or on every boot or time change and boot simultaneously.
When you configure the community string for SNMP V1, by default, the community string is appended with |common| FibreChannel11. 7. Select the Port Number and click Send to test the SNMP trap. Configuring sys log alerts You can configure up to four sys log destinations. To configure system log alerts, perform the following steps: 1. Click Application Settings > Alerts > Syslog Configuration. 2. Select the Enabled check box corresponding to the required server. 3.
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.
● Recent Activity—Displays the status of the jobs performed in the compute sled. ● Remote Console—Displays a graphical representation of the remote console is displayed on the right-side of the page. Below the remote console image, you can use the following links: ○ Launch iDRAC—Displays the iDRAC GUI. ○ Launch Virtual Console—Opens the virtual console. NOTE: The virtual console preview is unavailable for users with the "Viewer" User Role type.
NOTE: When a compute sled is inserted into a chassis, sometimes the message, "No device image found", is displayed. To resolve the issue refresh the inventory of the compute sled, manually. Configuring compute settings You can configure the following compute settings: ● Network ● Management Configuring compute network settings To configure the compute network settings: 1. Click Devices > Compute > View Details > Settings > Network. 2.
● Export logs displayed on the current page or export specific logs using Export. Viewing compute alerts You can view the list of alerts and warnings for compute sleds on the Alerts page. To view the compute alerts, click Devices > Compute > View Details > Alerts. You can sort the list of alerts based on the following advanced filters: ● ● ● ● ● ● ● Severity Acknowledge Start Date End Date Category Subcategory Message Select an alert to view the summary on the right side of the Alerts.
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.
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. 3. Click on Blink LED and click Turn Off. Editing storage sled assignments You can change the assignments of the device using Edit Assignments option. To edit assignments: ● On the storage Overview page, click Edit Assignments. The Hardware page is displayed. ● Select the hardware component, and change the assignment.
Assigning drives to a compute sled Using the Drive-Assigned mode, you can map the drives in a storage enclosure to a compute sled slot. If the compute sled fails, the drive remains assigned to the slot. If the sled is moved to another slot on the chassis, reassign the drives to the new slot. To configure RAID on the drives, use the iDRAC web interface, a server configuration profile, or an operating system deployment script, after the drive assignment is complete.
NOTE: The OME–Modular is inaccessible during the update process. Updating the firmware using DUP 1. Download the DUP from the Dell.com/support/drivers. 2. On the OME–Modular web interface, go to Devices > Storage. 3. Select the storage sled on which you want to update the firmware. 4. Click Update Firmware. 5. Select the Individual package option and click Browse to go to the location where you have downloaded the DUP. Wait for the comparison report, the supported components are displayed. 6.
● Passive ● Degraded A healthy system has one "Active" and one "Passive" SAS IOM. The chassis information comprises of the name of the chassis, slot name, and slot number. Information about the SAS IOM storage subsystems is also displayed on the right side of the Overview page. The storage subsystem information comprises the name of the subsystem and health status. Click View Details to view the alerts and alert details.
● Reset a chassis configuration in one step. ● Resolve a worst case mismatch where two switches are taken from two different chassis and inserted into a third chassis. In this scenario, it is unlikely that the two switches have a correct configuration. It is recommended that the Clear option is used to clear existing configuration and create a correct configuration.
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.
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.
Editing template networks To edit template network details: 1. On the Deploy page, select the template whose network details you want to modify and click Edit Network. The Edit Network window is displayed. 2. Modify the Identity Pool, and tagged and untagged VLANs. Cloning templates To create a copy of a template: On the Deploy page, select the template of which you want to create a copy, and click Clone. Exporting templates You can export the templates to a network share or a local drive on your system.
7 Managing identity pools Identity pools are used in template-based deployment of servers. They facilitate virtualization of network identities required for accessing systems using Ethernet, iSCSI, FCoE, or Fibre Channel (FC). You can enter the information required for managing the I/O identities. The identities, in turn, are managed by chassis management applications such as OME–Modular.
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. The Identity Pools page is displayed with the list of available identity pools and their key attributes. 2. Click Create. The Create Identity Pool wizard is displayed. 3. Enter a name and description for the identity pool and click Next.
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. Exporting identity pools You can export the identity pools in a .csv format to a network share or local drive on your system. To export identity pools: On the Identity Pools page, select the identity pools and click Export. Deleting identity pools You can delete identity pools that are not assigned or reserved.
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.
• • Viewing hardware details Configuring IOM settings Viewing hardware details You can view information for the following IOM hardware: ● FRU ● Device Management Info ● Installed Software ● Port Information NOTE: If the physical port is added as part of the port channel it is listed under the port channel group instead of the physical port. For Port Information, when you enable auto-negotiation, peer devices exchange capabilities such as speed and settle on mutually acceptable configuration.
7. In the DNS Server Settings section, enter the Preferred DNS Server, Alternate DNS Server 1, and Alternate DNS Server 2 addresses. For MXG610s IOMs, you can set the Preferred DNS and Alternate Server 1 and 2 addresses. However, the server address for Alternate DNS Server 2 is not applied though the response is successful as, MXG610s IOMs support only two server address for DNS settings. 8. In the Management VLAN section, select Enable VLAN and enter the VLAN ID.
Configuring Maximum Transmission Unit You can configure the Maximum Transmission Unit (MTU) for full-switch and fabric mode IOMs. The MTU can be configured for the Ethernet ports 1/1/1 to 1/1/16. 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. The default value is 1532 bytes, and the maximum is 9000 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.
Table 4. 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: 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 chassis that only contain FEMs, all four FEMs must connect to the same chassis with the FSEs. The fabric B FEMs cannot be connected to FSEs in a different chassis as the fabric A FSEs. Recommended connection order While any QSSFP28-DD port on the MX9116n can be used for any purpose, the table below describes the recommended port order for connecting chassis with FEM modules to the FSE. The table contains references IOMs in fabric A, but the same guidelines apply to IOMs in fabric B. Table 5.
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 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 interconnected only with other A1/A2 or B1/B2 switches respectively. Connecting switches that are placed in slots A1/A2 in one chassis with switches in slots B1/B2 in another chassis is not supported. ● Uplinks must be symmetrical.
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. Switch to switch cabling When operating in SmartFabric mode, each switch pair runs a Virtual Link Trunk (VLT) link between them. For the MX9116n, the port groups 11 and 12 are used. For the MX5108n, ports 9 and 10 are used.
NOTE: You cannot select the ports, and the connection topology is enforced by SmartFabric Services. NOTE: VLT is supported only on Ethernet and not on FCoE. Physically separate uplinks for LAN and FCoE traffic are required for MX5108n and MX9116n switches. Upstream network switch requirements It is recommended, but not required, that PowerEdge MX switches are connected to a pair of redundant upstream switches.
2. If the host OS is Windows, the LACP timer MUST be set to “slow” (also referred to as “normal”) For the list of supported operating systems, see Dell EMC PowerEdge MX7000 Enclosure Installation and Service Manual. NOTE: In the fabric mode, if an LACP team is created with four port and you want to delete two ports from the LACP team, you must delete the entire LACP team and create a new LACP team with two ports.
● 2xMX9116n Fabric Switching Engines in same chassis ● 2xMX9116n Fabric Switching Engines in different chassis Based on the design type selected, the options to select the chassis and the switches—A and B, are displayed. 5. Select the chassis and switches. The cabling image is displayed. 6. Click Next to view the summary of the fabric. You can print to print a hard copy of the fabric details or save the details as a PDF on your system.
4. Click Add Network. The Define Network window is displayed. 5. Enter Name, Description, VLAN ID and select the Network Type. For the network types, see the Online Help. Editing uplink To edit an existing uplink: 1. From the Devices drop-down, select Fabric. The Fabric page is displayed. 2. From the fabrics table, select the fabric and click View Details. The Fabric Details page is displayed. 3. From the Uplinks table, select the uplink and click Edit. The Edit uplink page is displayed. 4.
The Fabric page is displayed. 2. From the fabrics table, select the fabric that you want to delete. 3. Click Delete. A message is displayed prompting you to confirm the deletion. 4. Click Yes to proceed. After the fabric is deleted, the 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.
Table 6. Network traffic types - QoS settings (continued) Network Traffic Type Description QoS Setting Storage - FCoE Used for FCoE VLANs 3 Storage - Data Replication Used for VLANssupporting storage data replication such as for VMware VSAN 5 VM Migration Used for VLANs supporting vMotion and similar technologies 5 VMWare FT Logging Used for VLANs supporting VMware Fault Tolerance 5 Defining networks To configure a logical network: 1. Click Configuration > Networks.
Deleting network configurations To delete a network: On the Networks page, select the network and click Delete. If the network is associated with a fabric uplink, a warning message is displayed that deleting the network results in loss of connectivity.
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.
You can select a catalog to view the summary on the right-side. The summary comprises of the number of bundles in the catalog, date and time when the catalog was released, and name of the baselines associated with the catalog. You can perform the following tasks on the Catalog Management page: ● Add catalogs ● Edit catalogs ● Delete catalogs Viewing catalogs You can view the following catalog information on the Catalog Management page.
To update firmware: 1. On the Compliance Report page, select the device or component for which you want to update the firmware. The Update Firmware window is displayed. 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, then reconfigure the NTP servers.
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. To view the alerts page, from the menu bar, click Alerts. The Alerts page with the following tabs is displayed: ● Alert Log ● Alert Policies ● Alert Definition Topics: • • • Alert log Alert policies Alert definitions Alert log The Alerts Log page displays the list alert logs for events occurring in the chassis.
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 create an alert policy: 1. From the menu bar, click Alerts > Alert Policies > Create. The Create Alert Policy wizard is displayed. 2. Enter the name and description for the alert policy. 3. Select Enable Policy to activate the alert policy and click Next.
Editing alert policies You can edit alert policies. To edit alert policies: On the Alert Policies page, select the alerts that you want to edit and click Edit. A confirmation message is displayed. Disabling alert policies You can disable alert policies that are enabled. You can disable more than one alert policy at a time. To disable alert policies: On the Alert Policies page, select the alerts that you want to disable and click Disable. A confirmation message is displayed.
Selections that are made in the filters are applied at real time. 4. To reset the filters, click Clear All Filters.
15 Monitoring audit logs The audit log feature in OME–Modular enables you to monitor log entries related to: ● Log in attempts ● Appliance setup ● Chassis configuration change using RESTful API ● Change in alert filter configuration On the Audit Log page, you can perform the following tasks: ● Sort the audit logs using the Advanced Filter. ● Export all the audit logs in .csv format to a network share or local drive on your system.
Monitoring jobs You can view the status of and details of jobs that are initiated in the chassis and its subcomponents, on the Jobs page. The jobs include firmware update and inventory refresh for devices. To view the Jobs page, from the menu bar, click Monitor > Jobs. You can perform the following tasks on the Jobs page: ● ● ● ● ● ● ● Filter jobs using Advanced Filter View a summary of the job.
○ MCM 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. Viewing job details To view the details of a job: 1. On the Jobs page, select the job of which you want to view the details. A summary of the job is displayed on the right side of the Jobs page. 2. Click View Details. The Job Details page is displayed.
Deleting jobs To delete jobs: On the Jobs page, select the jobs that you want to delete and click Delete. A message is displayed prompting you to confirm the operation.
16 Troubleshooting This section describes the tasks for troubleshooting and resolving issues using the OME–Modular user interface.
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. Storage configuration cannot be applied to IOMs 1. 2. 3. 4.
A Recommended slot configurations for IOMs The table below contains the recommended IOM slot configurations. Table 7.
Table 8.
