This article provides information on how to determine if an iDRAC shared physical NIC 1 is connected on remote Windows Server
In some scenarios where a server is located in a remote facility (cannot get a hands-on view of server), the customer has access to the console of the system via RDP or Webex, but needs to verify if the Shared iDRAC port has a network cable plugged into it. Network Connections may state that Local Area Connection (LAC) is plugged in, but due to NIC enumeration issues, LAC may not actually be Physical NIC 1 on the server. In this situation, iDRAC connectivity will fail.
The root problem is that a NIC cable is not plugged into Physical NIC 1, not allowing iDRAC connectivity to the server.
To resolve this:
This is valid for Windows Server 2003 and Windows Server 2008. The release of Windows Server 2012 should resolve the issue of NIC enumeration and Local Area Connection 1 being connected to Physical NIC1.
|Need more help?|
|Find additional PowerEdge and PowerVault articles|
Visit and ask for support in our Communities
Create an online support Request
Article ID: SLN266203
Last Date Modified: 10/11/2017 08:15 AM