Users Guide
Table Of Contents
- Dell EMC OpenManage Enterprise-Modular Edition Version 1.20.10 for PowerEdge MX7000 Chassis User's Guide
- Overview
- Updating firmware for PowerEdge MX solution
- Updating MX7000 components using OME-Modular 1.20.10
- Upgrading ethernet switch using DUP
- Logging in to OME-Modular
- Logging in to OME–Modular as local, Active Directory, or LDAP user
- OME-Modular home page
- Viewing device health
- Setting up chassis
- Initial configuration
- Configuring chassis settings
- Managing chassis
- Chassis groups
- Controlling chassis power
- Backing up chassis
- Restoring chassis
- Exporting chassis profiles
- Managing chassis failover
- Troubleshooting in chassis
- Blinking LEDs
- Interfaces to access OME-Modular
- Viewing chassis hardware
- Viewing chassis alerts
- Viewing chassis hardware logs
- Configuring OME–Modular
- Viewing current configuration
- Configuring users and user settings
- Configuring login security settings
- Configuring alerts
- Managing compute sleds
- Managing storage
- Managing templates
- Managing identity pools
- Ethernet IO Modules
- MX Scalable Fabric architecture
- SmartFabric Services
- Managing networks
- Managing Fibre Channel IOMs
- Managing firmware
- Monitoring alerts and logs
- Monitoring audit logs
- Use case scenarios
- Troubleshooting
- Storage
- Firmware update is failing
- Storage assignment is failing
- SAS IOM status is downgraded
- SAS IOM health is downgraded
- Drives on compute sled are not visible
- Storage configuration cannot be applied to SAS IOMs
- Drives in OpenManage are not visible
- iDRAC and OpenManage drive information do not match
- The assignment mode of storage sled is unknown
- Unable to access OME-Modular using Chassis Direct
- Troubleshooting lead chassis failure
- Storage
- Recommended slot configurations for IOMs
- Upgrading networking switch using different DUP versions
- Upgrading networking switch using CLI
● Provided the Primary and Alternate DNS server addresses.
After you enter the domain name, OME-Modular searches the SRV records on the DNS servers to fetch the details of the
domain controllers in that domain.
If you know the IP address or FQDN of the domain controllers, you can use the Manual domain controller lookup type.
5. Enter the Bind DN and Bind Password.
NOTE: Anonymous bind is not supported for AD LDS.
6. Under Advanced Options, enter the Server Port, Base Distinguished Name to Search, Attribute of User Login,
Attribute of Group Membership, and Search Filter.
By default, LDAP port number of 636 is populated. To change, enter a port number.
Enter the User attributes that are configured in the LDAP system, already. It is recommended that the attributes are unique
within the selected BaseDN. Else, configure a search filter to ensure that the attributes are unique. If the combination of
attribute and search filter cannot identify the user DN uniquely, the login task fails.
The Attribute of Group Membership stores information about groups and members in the directory.
NOTE: Configure the user attributes in the LDAP system that is used to query before integrating on the directory
services.
NOTE: Enter the user attributes as cn or sAMAccountName for AD LDS configuration, and UID for LDAP
configuration.
7. Select the Network Timeout and Search Timeout durations.
The maximum timeout duration supported is 300 seconds.
8. Select the Certificate Validation checkbox if you want to validate the directory service certificate and select the
certificate for validation.
The certificate must be a Root CA Certificate encoded in Base64 format.
The Test Connection option is enabled.
9. Click Test Connection to check the LDAP connection.
10. Enter the bind user credentials of the domain you want to connect to.
NOTE:
While testing the connection, ensure that the Test username is the Attribute of User Login value entered
earlier.
11. Click Test Connection.
The Directory Service Information window, indicating a successful connection, is displayed.
12. Click Ok and Finish.
A job is created and run to add the requested directory on the Directory Services page.
Logging in to OME–Modular using the directory user credentials
To log in to OME–Modular using the directory user credentials:
From the OME–Modular login page, log in using the AD user credentials. Enter the domain name, if necessary.
Importing active directory and LDAP user groups
You can import Active Directory (AD) and LDAP groups and map them to the existing OME–Modular groups.
NOTE: Users without Administrator rights cannot enable or disable the Active Directory (AD) and LDAP users.
To import the groups:
1. On the Users list page, click Import Directory Group.
The Import Directory window is displayed.
2. From the Directory Source drop-down, select the source from which you want to import the AD or LDAP.
3. Under Available Groups, you can search for directory groups.
22
Logging in to OME-Modular










