Unable to ping an iDRAC from within an OS using the same LOM that is being shared

Unable to ping an iDRAC from within an OS using the same LOM that is being shared

This article provides information about pinging an iDRAC from within an Operating System when the iDRAC is being shared with the same LOM (LAN on Motherboard).

Users can configure a Dell EMC Poweredge iDRAC to operate on one or more of the LOM (LAN on Motherboard) ports. This is a common practice to limit the number of physical switch ports required in the network environment or provide physical redundancy to the iDRAC. When this network configuration is leveraged, an end-user may notice that the Host Operating System cannot ping or connect to its own iDRAC IP Address on the shared switch port.

This behavior is a Layer-2 networking limitation when both the Host Operating System and iDRAC are using the same VLAN (Virtual Local Area Network). When a broadcast packet is sent from the Host Operating System, the broadcast excludes the source switch port. In this scenario, the iDRAC will not receive the broadcast request.

In order to resolve this issue, Dell EMC Engineering recommends that Host Operating System and iDRAC exist on separate VLANs. In order to achieve this configuration, there are some considerations that need to be taken into account:

  • The leveraged LOM port will need to connect to a trunked switch port that is a member of both desired VLANs.
  • Refer to Network Adapter User Guides or Host Operating System documentation on how to tag VLAN IDs from within Host Operating System for the shared network adapter.
  • Enable VLAN ID Settings in the F2 System Setup>>iDRAC Settings>>Network Settings>>VLAN Settings.

Article ID: SLN167419

Last Date Modified: 09/07/2017 04:11 AM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.