Users Guide

• 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 version 3.4 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.
● The servers must be on the same domain 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 three records to your DNS server on the network for which the interface is configured on
the appliance. Ensure to replace all instances of <domain> with the appropriate DNS domain and the system hostname.
○ _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>
For example, see the following information by using nsupdate:
1) To create hostname record
>update add omehost.example.com 3600 A XX.XXX.X.XX
2) To add records for Server-initated 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.
2. By default, the Discovery-Approval policy, in the appliance, is set to Automatic and the servers that establish contact with
the console are automatically discovered. To change the settings, see Manage Console preferences on page 141.
3. Once the appliance is configured as mentioned in the previous steps, the servers can initiate contact with OpenManage
Enterprise by querying the DNS. The appliance verifies the servers after ensuring that the client certificate of the servers is
signed by the Dell CA.
NOTE:
If there are any changes in the server IP address or SSL certificate, the server reinitiates contact with
OpenManage Enterprise.
106 Discovering devices for monitoring or management