Users Guide

• 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
Discover servers automatically by using the server-
initiated discovery feature
OpenManage Enterprise allows automatic discovery of servers that have iDRAC firmware version 4.00.00.00 or later. The
appliance can be configured to allow these servers to automatically locate the console by querying the DNS and initiate their
discovery .
For a server-initiated discovery, the following prerequisites must be met:
● This feature is applicable only for servers with iDRAC firmware version 4.00.00.00 or later.
● The servers must be on the same domain or subdomain as OpenManage Enterprise.
● OpenManage Enterprise must be registered with the DNS to add the configuration information to the DNS by using TUI. It is
preferred that the DNS allows automatic updates from OpenManage Enterprise.
● Old records of the appliance console on the DNS, if any, should be cleaned up to avoid multiple announcements from the
servers.
The following steps are followed for an automatic discovery of servers in OpenManage Enterprise :
1. Add the configuration information of OpenManage Enterprise on the DNS using one of following methods:
● TUI—By using the TUI interface, enable the Configure Server Initiated Discovery option. For more information, see
Configure OpenManage Enterprise by using Text User Interface on page 24.
● Manually—Add the following four records to your DNS server on the network for which the interface is configured on
the appliance. Ensure that you replace all instances of <domain> or <subdomain.domain> with the appropriate DNS
domain and the system hostname.
○ <OME hostname>.<domain> 3600 A <OME IP address>
○ _dcimprovsrv._tcp.<domain> 3600 PTR ptr.dcimprovsrv._tcp.<domain>
○ ptr.dcimprovsrv._tcp.<domain> 3600 TXT URI=/api/DiscoveryConfigService/Actions/
DiscoveryConfigService.SignalNodePresence
○ ptr.dcimprovsrv._tcp.<domain> 3600 SRV 0 0 443 <hostname>.<domain>
To create the records with nsupdate in Linux, use the following commands:
○ To create hostname record
>update add omehost.example.com 3600 A XX.XX.XX.XX
○ To add records for server-initiated discovery
>update add _dcimprovsrv._tcp.example.com 3600 PTR ptr.dcimprovsrv._
tcp.example.com.
>update add ptr.dcimprovsrv._tcp.example.com 3600 TXT URI=/api/
DiscoveryConfigService/Actions/DiscoveryConfigService.SignalNodePresence
>update add ptr.dcimprovsrv._tcp.example.com 3600 SRV 0 0 443
omehost.example.com.
To create the records with dnscmd on a Windows DNS server, use the following commands:
○ To create hostname record
>dnscmd <DnsServer> /RecordAdd example.com omehost A XX.XX.XX.XX
Discovering devices for monitoring or management
105