Users Guide
Table Of Contents
- Dell EMC OpenManage Enterprise Version 3.6.1 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
- 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
- Global exclusion of ranges
- 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
- Manage devices and device groups
- Organize devices into groups
- Create a custom group (Static or Query)
- Create a Static device group
- Create a Query device group
- Edit a static group
- Edit a query group
- Rename a static or query group
- Delete a static or query device group
- Clone a static or query group
- Add devices to a new group
- Add devices to existing group
- Refresh health on group
- All Devices page - devices list
- All Devices page — device list actions
- Delete devices from OpenManage Enterprise
- Exclude devices from OpenManage Enterprise
- Run inventory on devices
- Update the device firmware and drivers by using baselines
- Refresh the device health of a device group
- Refresh health on devices
- Roll back an individual device's firmware version
- Export the single device inventory
- Performing more actions on chassis and servers
- Hardware information displayed for MX7000 chassis
- Export all or selected data
- View and configure individual devices
- Device Overview
- Device hardware information
- Run and download Diagnostic reports
- Extract and download SupportAssist reports
- Managing individual device hardware logs
- Run remote–RACADM and IPMI–commands on individual devices
- Start Management application iDRAC of a device
- Start the Virtual Console
- Refresh device inventory of a single device
- Organize devices into groups
- Managing device inventory
- 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
- Monitor and Manage device alerts
- Monitor audit logs
- Using jobs for device control
- Manage the device warranty
- Reports
- Managing MIB files
- Managing OpenManage Enterprise appliance settings
- Configure OpenManage Enterprise network settings
- Manage OpenManage Enterprise users
- Role and scope based access control in OpenManage Enterprise
- Add and edit OpenManage Enterprise local users
- Edit OpenManage Enterprise user properties
- Enable OpenManage Enterprise users
- Disable OpenManage Enterprise users
- Delete OpenManage Enterprise users
- Import AD and LDAP groups
- Transfer of ownership of Device Manager entities
- 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
uniquely identify a server on a network and also determine how the server communicates with a network resource using a
specific protocol. Using OpenManage Enterprise, you can automatically generate and assign virtual identity attributes to the I/O
interfaces of a server.
Servers deployed by using a device deployment template that contains virtual I/O identities are known as 'stateless.' Stateless
deployments enable you to create a server environment that is dynamic and flexible. For example, deploying a server with virtual
I/O identities in a boot-from-SAN environment enables you to quickly do the following:
● Replace a failing or failed server by moving the I/O identity of the server to another spare server.
● Deploy additional servers to increase the computing capability during high workload.
The OpenManage Enteprise > Configuration > Identity Poolspage allows you to create, edit, delete, or export virtual I/O
pools.
NOTE:
● To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based
operational access to the devices. Role and scope based access control in OpenManage Enterprise on page 15
● Scope based restrictions don't apply to identity pools, therefore, all identify pools can viewed and used by all user types.
However, once the identities are assigned by a device manager, then only those identities can be viewed and used by
that device manager.
Create Identity Pool - Pool Information
Identity pools are used for template-based deployment on servers to virtualize the network identity for the following:
● Ethernet
● iSCSI
● Fibre Channel over Ethernet (FCoE)
● Fibre Channel (FC)
You can create a maximum of 5000 identity pools in each of these categories.
The server deployment process fetches the next available identity from the pool and uses while providing a server from the
template description. You can then migrate the profile from one server to another without losing access to the network or
storage resources in your environment.
You can edit the number of entries in the pool. However, you cannot reduce the number of entries less than those assigned or
reserved. You can also delete the entries that are not assigned or reserved.
Identity pools
An identity pool is a collection of one or more virtual identity types that are required for network communication. An identity
pool can contain a combination of any of the following virtual identity types:
● Ethernet identities
The Identities which are defined by the Media Access Control (MAC) address. MAC addresses are required for Ethernet
(LAN) communications.
● iSCSI identities
The Identities which are defined by the iSCSI Qualified Name (IQN). IQN identities are required to support boot-from-SAN by
using the iSCSI protocol.
● Fibre Channel (FC) identities
The Identities which are defined by the World Wide Node Name (WWNN) and World Wide Port Name (WWPN). A WWNN
identity is assigned to a node (device) in an FC fabric and may be shared by some or all ports of a device. A WWPN identity
is assigned to each port in an FC fabric and is unique to each port. WWNN and WWPN identities are required to support
boot-from-SAN and for data access using FC and Fibre Channel over Ethernet (FCoE) protocols.
● Fibre Channel over Ethernet (FCoE) identities
Identities that provide a unique virtual identity for FCoE operations. These identities are defined by both MAC address and
the FC addresses (that is WWNN and WWPN). WWNN and WWPN identities are required to support boot-from-SAN and for
data access using FC and Fibre Channel over Ethernet (FCoE) protocols.
90
Manage device deployment templates