Users Guide

Table Of Contents
NOTE: Do not use 169.254.0.3 and 169.254.0.4 IP addresses. These IP addresses are reserved for the USB NIC port on the
front panel when an A/A cable is used.
NOTE: iDRAC may not be accessible from the host server using LOM-Passthrough when NIC teaming is enabled. Then,
iDRAC can be accessed from the host server OS using the iDRAC USB NIC or through the external network, via the iDRAC
dedicated NIC.
Supported cards for OS to iDRAC Pass-through
The following table provides a list of cards that support the OS to iDRAC Pass-through feature using LOM.
Table 15. OS to iDRAC Pass-through using LOM supported cards
Category Manufacturer Type
NDC Broadcom
5720 QP rNDC 1G BASE-T
Intel
x520/i350 QP rNDC 1G BASE-T
In-built LOM cards also support the OS to iDRAC pass-through feature.
Supported operating systems for USB NIC
The operating systems supported for USB NIC are:
Server 2012 R2 Foundation Edition
Server 2012 R2 Essentials Edition
Server 2012 R2 Standard Edition
Server 2012 R2 Datacenter Edition
Server 2012 for Embedded Systems (Base and R2 w/ SP1)
Server 2016 Essentials Edition
Server 2016 Standard Edition
Server 2016 Datacenter Edition
RHEL 7.3
RHEL 6.9
SLES 12 SP2
ESXi 6.0 U3
vSphere 2016
XenServer 7.1
For Linux operating systems, configure the USB NIC as DHCP on the host operating system before enabling USB NIC.
For vSphere, you must install the VIB file before enabling USB NIC.
NOTE:
To configure USB NIC as DHCP in Linux operating system or XenServer, refer to the operating system or hypervisor
documentation.
Installing VIB file
For vSphere operating systems, before enabling the USB NIC, you must install the VIB file.
To install the VIB file:
1. Using Win-SCP, copy the VIB file to /tmp/ folder of the ESX-i host operating system.
2. Go to the ESXi prompt and run the following command:
esxcli software vib install -v /tmp/ iDRAC_USB_NIC-1.0.0-799733X03.vib --no-sig-check
The output is:
Message: The update completed successfully, but the system needs to be rebooted for
the changes to be effective.
Configuring iDRAC
103