How to Troubleshoot Server Discovery Connectivity Issues in Dell OpenManage Enterprise (OME)
Summary: Dell OpenManage Enterprise (OME) uses a multi-step process to discover and onboard servers through iDRAC. The discovery process begins with a basic network reachability check (ICMP ping) followed by protocol-level communication (Redfish or WS-Man). If any step in this chain fails, the discovery will not succeed. ...
Instructions
Symptoms
- Discovery job status shows Failed in OME
- Servers cannot be added through iDRAC discovery
- Discovery job completes with zero devices onboarded
- Error messages referencing ICMP ping failures or connection timeouts in OME logs
How OME Discovery Works
Understanding the discovery flow helps identify where the failure is occurring:
Step 1: ICMP Ping → OME pings the target iDRAC IP to verify basic reachability
Step 2: Protocol Handshake → OME connects via Redfish (port 443) or WS-Man to authenticate
Step 3: Data Collection → OME retrieves server inventory and configuration
Step 4: Onboarding → Server is added to the OME console
Important: By default, if Step 1 (ICMP Ping) fails, OME will not proceed to any subsequent steps. This is the most common point of failure. However, the ICMP ping requirement can be adjusted. See Step 2 below for details.
Step-by-Step Troubleshooting
Step 1: Verify iDRAC Accessibility
Before troubleshooting OME, confirm that the iDRAC is online and accessible.
- From a workstation on your network, open a browser and navigate to
- Verify that the iDRAC login page loads successfully
-
Step 1: Verify iDRAC Accessibility
Before troubleshooting OME, confirm that the iDRAC is online and accessible.
- From a workstation on your network, open a browser and navigate to
- Verify that the iDRAC login page loads successfully
- Open a command prompt or terminal and run:
ping <iDRAC_IP>
- If the iDRAC web interface loads and ping is successful from your workstation, the iDRAC is online and the issue is specific to connectivity between OME and iDRAC
Step 2: Use the OME Built-In Troubleshooting Tool
OME includes a built-in diagnostic tool that allows you to test connectivity directly from the appliance.
- Log in to the OME web console
- Navigate to Monitor → Troubleshoot
- Ping Test:
- Enter the target iDRAC IP address
- Click Run to execute the ping test
- If the ping fails, this confirms a network-level connectivity issue between OME and the iDRAC
- Protocol Test:
- Select Redfish as the protocol
- Enter the target iDRAC IP address and credentials
- Click Run to test protocol connectivity
- If the ping succeeds but the protocol test fails, the issue is at the protocol or authentication level
Step 2a: Alternative — Disable ICMP Ping Requirement for Discovery
If ICMP ping is intentionally disabled or blocked in your environment by design, OME discovery can still work without it. The ICMP ping setting can be adjusted within OME:
- Log in to the OME web console
- Navigate to Application Settings → Discovery Settings
- Locate the ICMP Ping setting
- Disable the ICMP Ping option
- Save the changes and retry the discovery job
Important Note: Disabling the ICMP ping setting only removes the ICMP reachability check as a prerequisite for discovery. It does not resolve underlying network connectivity issues. If the network path between OME and iDRAC is broken due to subnet mismatch, routing issues, firewall rules blocking port 443, or other network-level problems, discovery will still fail at the protocol handshake stage even with ICMP ping disabled.
Recommended Validation:
Before disabling the ICMP ping setting and retrying discovery, use the Protocol Test under Monitor → Troubleshoot to verify that Redfish connectivity to the iDRAC is working. If the protocol test fails, there is a network issue that must be resolved first regardless of the ICMP ping setting.
When to use this option:
- Your network team has confirmed that ICMP is intentionally blocked by policy across the environment
- You have verified through the Protocol Test in OME that Redfish connectivity to the iDRAC is successful
- All other network requirements (routing, port 443, no proxy interference) are confirmed to be in place
Step 3: Verify Network Configuration
If the ping test from OME fails and the protocol test also fails, the issue is at the network level. Verify the following:
A. Subnet and VLAN Configuration
- If OME and iDRAC are on the same subnet, they should be able to communicate directly. Verify there are no VLAN isolation policies or port security rules blocking traffic.
- If OME and iDRAC are on different subnets, proper routing must exist between the two subnets. Verify that:
- The OME appliance has a correct default gateway configured
- The iDRAC has a correct default gateway configured
- Routers or Layer 3 switches between the subnets are configured to route traffic between them
B. IP Address Conflicts
- Ensure no other device on the network shares the same IP address as the iDRAC or the OME appliance
- An IP conflict can cause intermittent or complete connectivity loss
Step 4: Review Firewall and ACL Rules
If OME and iDRAC are on different subnets or if firewalls exist between them, the following traffic must be permitted:
Key Points:
- ICMP must be allowed unless intentionally disabled. OME uses ICMP ping as the first step of discovery by default. If ICMP is blocked, discovery will fail immediately unless the ICMP ping setting has been disabled under Application Settings → Discovery Settings.
- Port 443 must be open. This is the primary port used for Redfish and WS-Man communication between OME and iDRAC. This is required regardless of the ICMP ping setting.
- Check for any Access Control Lists (ACLs) on switches or routers that may be filtering traffic between the OME and iDRAC subnets.
Step 5: Check for Proxy or Traffic Inspection Devices
- If your network uses a web proxy, SSL inspection appliance, or traffic filtering device, it may intercept or block communication between OME and iDRAC.
- OME requires direct connectivity to iDRAC. Proxy configurations can disrupt the Redfish/WS-Man protocol handshake.
- If a proxy exists, configure an exception or bypass rule for traffic between the OME appliance and the iDRAC management network.
Step 6: Verify Discovery Job Configuration in OME
If network connectivity is confirmed (ping and/or protocol tests pass), verify the discovery job settings:
- Navigate to Monitor → Discovery
- Click Create to set up a new discovery job
- Verify the following settings:
Common Configuration Mistakes:
- Incorrect iDRAC IP address or IP range entered
- Wrong or expired iDRAC credentials
- iDRAC user account lacking sufficient privileges
Common Root Causes
Additional Resources
- OME User Guide: Refer to the Network Prerequisites and Supported Protocols and Ports sections for a complete list of requirements.
- OME Troubleshoot Tool: Available under Monitor → Troubleshoot within the OME web console
- OME Discovery Settings: Available under Application Settings → Discovery Settings to configure ICMP ping behavior
- Dell Support: If the issue persists after completing all troubleshooting steps, contact Dell Technical Support with the following information:
- OME application bundle logs - OpenManage Enterprise: How to Collect Debug logs
- TSR (Technical Support Report) from the affected iDRAC - PowerEdge: Export a SupportAssist Collection Using iDRAC UI or racadm cmd
- OME appliance IP and subnet details
- iDRAC IP and subnet details
- Network topology summary between OME and iDRAC