Reference Guide

16 No Restrictions | iDRAC Access via Host Operating System
iptables -A OS2iDRAC -p tcp -d 169.254.0.1 --dport 443 -j ACCEPT
iptables -A OS2iDRAC -p tcp -i idrac -s 169.254.0.1 -j ACCEPT
(By Default, the iDRAC USBNIC IP is 169.254.0.1, iDRAC Secure Port is 443). The iDRAC USBNIC IP and
iDRAC Secure Port details can be obtained from the file /opt/dell/srvadmin/iSM/etc/ini/dcos2idrac.ini as
mentioned below.
connect_address=169.254.0.1
connect_port=443
4.9 iDRAC Access via Host OS feature can’t be enabled post
installation if it is not included manually during installation using
webpack
Symptoms
While trying to access iDRAC page via Host OS, it fails to connect to iDRAC page and displays the error
“The site can’t be reached.”
Reason
While installing iDRAC Service module using the setup.sh provided as part of the Linux webpack and if
the user does not select the "iDRAC Access Via Host OS" feature to install, it is observed that you cannot
enable the feature post installation.
Recovery Action
Modify the iDRAC Service Module by running setup.sh installer script, with the option to enable “iDRAC
Access via Host OS” feature as mentioned below.
./setup.sh -i -O --port=<listen-port-no>
Where:
–-port is a mandatory parameter. This port number is used to listen for connections/requests to iDRAC
on the Host OS, in order to forward all connections or requests to iDRAC.
Accepted port number range is 1024 to 65535. You must ensure that a unique port number is assigned.
This issue is not observed when the iDRAC Service Module is installed using the other alternative
methods such as iDRAC Service Module DUP, yum, and rpm packages. The feature can be configured
using the “Enable-iDRACAccessHostRoute” CLI.
4.10 Failure to access iDRAC via Host OS on Microsoft Windows
although the listen port and firewall are configured
Symptoms
While trying to access iDRAC page via Host OS, it fails to connect to iDRAC page and displays the error