Dell EMC OpenManage Enterprise-Modular Edition Version 1.00.10 for PowerEdge MX7000 Chassis User's Guide February 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 New in this release..............................................................................................................................................................
Configuring OME–Modular............................................................................................................................................. 27 Viewing current configuration.................................................................................................................................. 27 Configuring users and user settings.......................................................................................................................
Viewing hardware details.................................................................................................................................................52 Configuring IOM settings................................................................................................................................................ 52 Configuring IOM network settings..........................................................................................................................
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.
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 (continued) Name of the document Brief introduction of the document OpenManage Enterprise Modular Release Notes This document provides the latest updates to the system or documentation or advanced technical reference material intended for experienced users or technicians.
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. 2. Catalog-based compliance method To update the firmware using the Individual package method: 1.
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 into 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.
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.
Viewing device health The Devices > All Devices page displays the health summary of the chassis, compute and storage sleds, and networking components. 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.
Enter details of the network share, where the chassis profile is located and click Import. 3. In the Time Configuration tab, select the Configure Time Settings to configure the time zone and timestamp of the configuration. 4. Select the Use NTP check box to configure the primary, secondary, or tertiary NTP addresses and click Next. NOTE: It is recommended that at least three valid NTP servers, which synchronize to a single time source, are used to ensure reliable synchronization.
● No Redundancy—The intent of the No Redundancy policy is to power on the maximum number of devices based on the available PSUs. In case of single or multiple PSU failures, the system is at risk of degraded performance and other significant power limiting events. The No Redundancy policy distributes power between all the PSUs, and the system limits the power on of devices added to the chassis to the sum of the capacity of all PSUs.
5. 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 change the VLAN settings, that is, move from a VLAN network to a non-VLAN network, or move from a non-VLAN network to a VLAN network, only if Register with DNS is cleared. By default, the IPv4 settings are enabled and the DNS registration is disabled with a default name. You can modify the name using any local interfaces such as OpenManage Mobile.
NOTE: The Timeout Limit option is available only if the Enable Inactivity Timeout is selected. 5. Select Enable Read Authentication to use your user credentials to read the inventory in a secure data center. 6. Select Enable Quick Sync Wi-Fi to use WiFi to communicate with the chassis. By default, the Enable Quick Sync Wi-Fi check box is selected. 7. Select Enable KVM Access to configure the quick sync setting using KVM. You can also use the RACADM or Redfish command to enable or disable KVM.
● Static ● DHCP 6. If the IPv6 Network Type is Static, select the IPv6 Prefix Length and enter the IPv6 Gateway. Managing chassis You can view the list of chassis and the chassis details on the Chassis page. The details are—health, power state, name, IP address, service tag, and model of the chassis. You can also select a chassis to view the graphical representation and summary of the chassis, on the right side of the Chassis page.
NOTE: The temperature statistics timestamp remains unchanged after a failover or management module reboot. ● Recent Alerts—Displays the number and details of the tasks that are performed in the chassis. Click View All to view the list of all alerts that are related to the compute sled on the Chassis > Alerts page. ● Recent Activity—Displays the status of the jobs that are performed in the compute sled. ● Server Subsystems—Displays a summary of information about the server sub systems.
Prerequisites for creating a wired group Following are the prerequisites to create a wired or daisy-chained chassis group: ● List of wired daisy-chained chassis—All the chassis must be on the private stack. You need not enter a password as the machine to machine authentication trust is used. ● Ensure that you have added member chassis to the group using the automatic or manual method.
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.
Controlling chassis power You can turn on and turn off the chassis power supply from the OME–Modular home page: To control the chassis power: 1. On the home page, click Power Control and select the required option. The available options are: ● Power Off (Non-graceful) ● Power Cycle System (Cold Boot) ● Power Off (Graceful) NOTE: After login, wait for 7 minutes, if the IP is unavailable, then check if: ○ The cable is connected.
Restoring chassis You can restore the configuration of a chassis using a back up file, if the backed-up configuration is of the same chassis. You must have the chassis administrator role with device configuration privilege to restore the chassis. To restore a chassis: 1. On the chassis Overview page, click More Actions > Restore. The Restore Chassis window is displayed. 2. Under Restore File Location, select the Share Type where the configuration backup file is located. 3.
NOTE: During a factory reset process, the synchronization takes about 3-5 minutes. During this period, the serial, KVM, and Quick Sync interfaces do not accept the factory password and the login attempt fails. ● Terminate Serial Connection—Use this option to end the existing serial sessions. Blinking LEDs You can use the Blink LED option on the OME–Modular home page to turn off or turn on the chassis LED.
Table 2. Management module Interfaces (continued) Interface Description management. It is a new interface that uses RESTful interface semantics to access data that is defined in model format to perform out-of-band systems management. It is suitable for a wide range of servers ranging from stand-alone servers to rack mount and bladed environments and for large-scale cloud environments.
You can also perform the following activities on the Alerts page. ● ● ● ● ● Acknowledge Unacknowledge Ignore Export Delete Viewing chassis hardware logs The logs of activities performed on the hardware components associated with the chassis are displayed on the OME–Modular Hardware Logs page. The log details that are displayed include severity, message ID, category, timestamp, and description. You can also view the chassis hardware logs by clicking Devices > Chassis > View Details > Hardware Logs.
4. Enter the port number for the web server. You can enter a port number in the 10-65535 range. The default port number is 443. when the web server https port settings from the lead chassis are applied to member chassis as part of the add or join member task, refresh the inventory for the lead chassis manually to see the correct https port for the member chassis, on the Hardware > Device Management Info page. Launch the member chassis from the lead chassis to see the port number.
3. Enter the Username. The default username is "root", and you cannot edit it. You cannot disable the default account or edit the role associated with the default account. The length of the username can be 1-16 characters long and contain white spaces and alphanumeric characters. The special characters - §, ", /, :, @, and ` are not supported. NOTE: For the OME–Modular serial interface, ensure that the length of the local or remote username does not exceed 35 characters.
Table 3.
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.
● 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 username 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 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.
○ Edit server profiles—You can edit the profile characteristics that are unique to the device or slot. If a profile is attached to a compute, the updated profile configuration is propagated to the compute. ○ Remove slot associations—You can detach the server profile from the slot. 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.
You can also perform the following tasks on the Hardware Logs page: ● Filter the logs using Advanced Filter—You can filter the logs based on severity, message ID, start date, end date, or category. ● Select logs and include comments for them using Add Comment. ● 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.
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.
● Active ● 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.
You can use the Clear option to: ● 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 templates You can only modify the name and description of the template from the Deploy and Template Details pages. 1. On the Deploy page, select the template that you want to modify and click Edit. Else, on the Template Details page, click Edit. The Edit Template window is displayed. 2. Make the required changes. 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.
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 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.
Topics: • • 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.
The IPv6 Address, Prefix Length, and Gateway options are enabled only if the Enable Autoconfiguration check box is cleared. NOTE: For tagged or untagged VLAN network, any IPv6 setting configured using OME - Modular may not have the default gateway. To get the default gateway, go to the respective OS10 CLI and enable Stateless Address Autoconfiguration (SLAAC) on the respective tagged or untagged VLAN. 7.
First apply "Hardware Default" and then select the required breakout. NOTE: Breakouts can be configured only for Fabric Mode IOMs. Configuring admin status You can switch the admin status for all ports, which is enabled by default. For the MX9116n FSE port groups 1/1/15 and 1/1/16, when you breakout the fiber channel ports, the admin status is disabled by default. Enable the status if required. To switch the admin status: Select the port and click Toggle Admin State.
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 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 Fabric Expander Modules (FEMs) to the FSE. The table contains references IOMs in fabric A, but the same guidelines apply to IOMs in fabric B.
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.
• 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 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.
In SmartFabric mode, ports 9 and 10 are automatically configured in a VLT at 40GbE speed. For port 10, use a cable or optic that supports 40GbE and not 100GbE. 2 x MX9116n Fabric Switching Engines in the same chassis Use this placement in environments with a single chassis. The switches must be placed in either slots A1/A2 or slots B1/B2. A SmartFabric cannot include a switch in Fab A and a switch in Fab B.
NOTE: You cannot select the ports, and the connection topology is enforced by SmartFabric Services. NOTE: VLT is supported only on Ethernet and not on FCoE. Physically separate uplinks for LAN and FCoE traffic are required for MX5108n and MX9116n switches. Upstream network switch requirements It is recommended, but not required, that PowerEdge MX switches are connected to a pair of redundant upstream switches.
2. If 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.
● 2xMX5108n Ethernet Switches in same chassis ● 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.
2. From the fabrics table, select the fabric and click View Details. The Fabric Details page is displayed. 3. From the Uplinks section, click Add Uplink. The Add Uplink window is displayed. 4. Click Add Network. The Define Network window is displayed. 5. Enter Name, Description, VLAN ID and select the Network Type. For the network types, see the Online Help. Editing uplink To edit an existing uplink: 1. From the Devices drop-down, select Fabric. The Fabric page is displayed. 2.
4. Click Delete. Click Yes to confirm the deletion. Deleting fabric To delete an existing fabric: 1. From the Devices drop-down, select Fabric. The Fabric page is displayed. 2. From the fabrics table, select the fabric that you want to delete. 3. Click Delete. A message is displayed prompting you to confirm the deletion. 4. Click Yes to proceed. After the fabric is deleted, the 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 5 Storage - Data Replication Used for VLANssupporting storage data replication such as for VMware VSAN 5 VM Migration Used for VLANs supporting vMotion and similar technologies 5 VMWare FT Logging Used for VLANs supporting VMware Fault Tolerance 5 Defining networks To configure a logical network: 1. Click Configuration > 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.
Updating firmware Before updating the firmware on a chassis, compute, or storage sleds, ensure that all IOMs and network fabrics are healthy. NOTE: The Update Firmware button may be disabled temporarily during inventory refresh when a Refresh Inventory job or Default Inventory job is run. 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.
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 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.
● 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.
○ 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. Viewing job details The Fabric Manager on-boarding is initiated when a Fabric Manager failover occurs in the IOM cluster. When a new Fabric Manager is discovered, OME - Modular initiates the on-boarding process to reestablish communication with the IOM cluster.
Enabling jobs You can enable jobs that are disabled. To enable jobs: On the Jobs page, select the disabled jobs that you want to enable and click Enable. A confirmation message is displayed and the state of the selected jobs changes to "Enabled". Disabling jobs You can disable jobs that are enabled. To disable jobs: On the Jobs page, select the enabled jobs that you want to disable and click Disable. A confirmation message is displayed and the state of the selected jobs changes to "Disabled".
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 SAS IOMs 1. 2. 3. 4.
A Recommended slot configurations for IOMs The table below contains the recommended IOM slot configurations. Table 7.
Table 8.
