Users Guide
Table Of Contents
- Dell EMC OpenManage Enterprise Version 3.5 User's Guide
- Contents
- Tables
- About Dell EMC OpenManage Enterprise
- Security features in OpenManage Enterprise
- Install OpenManage Enterprise
- Installation prerequisites and minimum requirements
- Deploy OpenManage Enterprise on VMware vSphere
- Deploy OpenManage Enterprise on Hyper-V 2012 R2 and earlier host
- Deploy OpenManage Enterprise on Hyper-V 2016 host
- Deploy OpenManage Enterprise on Hyper-V 2019 host
- Deploy OpenManage Enterprise by using Kernel-based Virtual Machine
- Deploy OpenManage Enterprise programmatically
- Get started with OpenManage Enterprise
- Log in to OpenManage Enterprise
- Configure OpenManage Enterprise by using Text User Interface
- Configure OpenManage Enterprise
- Recommended scalability and performance settings for optimal usage of OpenManage Enterprise
- Supported protocols and ports in OpenManage Enterprise
- Use case links for the supported protocols and ports in OpenManage Enterprise
- OpenManage Enterprise Graphical User Interface overview
- OpenManage Enterprise Home portal
- Managing devices
- Organize devices into groups
- Create or delete a Static device group
- Create or edit a Query device group
- Adding or editing devices in a Static child group
- Rename child groups of Static or Query Dynamic groups
- Clone a Static or Query group
- Add devices to a new group
- Add devices to existing group
- Delete devices from OpenManage Enterprise
- Exclude devices from OpenManage Enterprise
- Update the device firmware and drivers by using baselines
- Roll back an individual device's firmware version
- Refresh the device inventory
- Refresh the device status
- Export the single device inventory
- Devices list
- Performing more actions on chassis and servers
- Hardware information displayed for MX7000 chassis
- Export all or selected data
- Viewing and configuring devices
- Start Management application iDRAC of a device
- Start the Virtual Console
- Organize devices into groups
- Manage the device firmware and drivers
- Manage device deployment templates
- Create a deployment template from a reference device
- Create a deployment template by importing a template file
- View a deployment template information
- Edit a server deployment template
- Edit a chassis deployment template
- Edit IOA deployment template
- Edit network properties of a deployment template
- Deploy device deployment templates
- Deploy IOA deployment templates
- Clone deployment templates
- Auto deployment of configuration on yet-to-be-discovered servers or chassis
- Create auto deployment targets
- Delete auto deployment targets
- Export auto deployment target details to different formats
- Overview of stateless deployment
- Define networks
- Edit or delete a configured network
- Export VLAN definitions
- Import network definitions
- Manage Profiles
- Managing the device configuration compliance
- Monitoring device alerts
- Manage audit logs
- Using jobs for device control
- Discovering devices for monitoring or management
- Discover servers automatically by using the server-initiated discovery feature
- Create a device discovery job
- Protocol support matrix for discovering devices
- View device discovery job details
- Edit a device discovery job
- Run a device discovery job
- Stop a device discovery job
- Specify multiple devices by importing data from the .csv file
- Globally excluding devices
- Specify discovery mode for creating a server discovery job
- Create customized device discovery job protocol for servers –Additional settings for discovery protocols
- Specify discovery mode for creating a chassis discovery job
- Create customized device discovery job protocol for Chassis – Additional settings for discovery protocols
- Specify discovery mode for creating a Dell storage discovery job
- Specify discovery mode for creating a network switch discovery job
- Create customized device discovery job protocol HTTPS storage devices –Additional settings for discovery protocols
- Create customized device discovery job protocol for SNMP devices
- Specify discovery mode for creating a MULTIPLE protocol discovery job
- Delete a device discovery job
- Managing device inventory
- Manage the device warranty
- Reports
- Managing MIB files
- Managing OpenManage Enterprise appliance settings
- Configure OpenManage Enterprise network settings
- Manage OpenManage Enterprise users
- Ending user sessions
- Directory services integration in OpenManage Enterprise
- OpenManage Enterprise login using OpenID Connect providers
- Add an OpenID Connect provider to OpenManage Enterprise
- Configure an OpenID Connect provider policy in PingFederate for role-based access to OpenManage Enterprise
- Configure an OpenID Connect provider policy in Keycloak for role-based access to OpenManage Enterprise
- Test the registration status of OpenManage Enterprise with the OpenID Connect provider
- Edit an OpenID Connect provider details in OpenManage Enterprise
- Enable OpenID Connect providers
- Delete OpenID Connect providers
- Disable OpenID Connect providers
- Security Certificates
- Set the login security properties
- Manage Console preferences
- Customize the alert display
- Configure SMTP, SNMP, and Syslog alerts
- Manage incoming alerts
- Manage warranty settings
- Check and update the version of the OpenManage Enterprise and the available plugins
- Execute remote commands and scripts
- OpenManage Mobile settings
- Enable or disable alert notifications for OpenManage Mobile
- Enable or disable OpenManage Mobile subscribers
- Delete an OpenManage Mobile subscriber
- View the alert notification service status
- Notification service status
- View information about OpenManage Mobile subscribers
- OpenManage Mobile subscriber information
- Troubleshooting OpenManage Mobile
- Other references and field descriptions
- Schedule Reference
- Firmware baseline field definitions
- Schedule job field definitions
- Alert categories after EEMI relocation
- Token substitution in remote scripts and alert policy
- Field service debug workflow
- Unblock the FSD capability
- Install or grant a signed FSD DAT.ini file
- Invoke FSD
- Disable FSD
- Catalog Management field definitions
- Firmware/driver compliance baseline reports— devices with 'Unknown' compliance status
- Generic naming convention for Dell EMC PowerEdge servers
Add a catalog to the local network
Catalog containing the firmware and drivers (64-bit Windows) can be downloaded using the Dell Repository Manager (DRM)
and saved on a network share.
1. On the Catalog Management page, click Add.
2. In the Add Update Catalog dialog box:
a. In the Name box, enter a catalog name.
b. For the Catalog Source, select the option Network Path.
The Share Type drop-down menu is displayed.
c. Select one of the following:
NOTE: Ensure to enable SMBv1 in the SMB Settings before you begin any firmware tasks which need
communication with any chassis or the PowerEdge YX2X and YX3X servers that have iDRAC version 2.50.50.50
and earlier. See Manage Console preferences on page 143 and Generic naming convention for Dell EMC PowerEdge
servers on page 162 for more information.
● NFS
i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the
network.
ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path:
nfsshare\catalog.xml
● CIFS
i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the
network.
ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path:
Firmware\m630sa\catalog.xml
iii. In the Domain box, enter the domain name of the device.
iv. In the User Name box, enter the user name of the device where the catalog is stored.
v. In the Password box, enter the password of the device to access the share. Type the username and password of
the shared folder where the catalog.xml file is stored.
● HTTP
i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the
network.
ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: compute/
catalog.xml.
● HTTPS
i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the
network.
ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: compute/
catalog.xml.
iii. In the User Name box, enter the user name of the device where the catalog is stored.
iv. In the Password box, enter the password of the device where the catalog is stored.
v. Select the Certificate Check check box.
The authenticity of the device where the catalog file is stored is validated and a Security Certificate is generated
and displayed in the Certificate Information dialog box.
d. After you have entered the Share Address and the Catalog File Path, the Test now link is displayed. To validate
a connection to the catalog click Test now. If the connection to the catalog is established, a Connection Successful
message is displayed. If connection to the share address or the catalog file path is not established, Connection to path
failed error message is displayed. This is an optional step.
e. In the Update Catalog box, select either Manually or Automatically.
If the Update Catalog is selected as Automatically, select either Daily or Weekly as the update frequency and enter
time in the 12-hour format.
3. Click Finish. The Finish button appears only after you have entered all the fields in the dialog box.
A new firmware catalog is created and listed in the Catalog table on the Catalog Management page.
4. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance.
Manage the device firmware and drivers
53