Reference Guide

13 No Restrictions | iDRAC Access via Host Operating System
4 Troubleshooting and Recovery
4.1 Failure to access iDRAC via Host OS due to Iptables holding the
lock in Linux OS
Symptoms
While trying to access iDRAC page via Host OS, it fails to connect to iDRAC page and throws the error
“The site can’t be reached.”
Reason
When executing, Iptables acquires an internal lock and if multiple iptables commands are run
simultaneously, one of the commands might fail as the other command had acquired the lock already.
The iDRAC Access via Host OS feature fails to configure when there is an iptables command running
which already have acquired the lock.
Recovery Action
By verifying if the SNAT and DNAT rules are configured with the given port, it can be confirmed if the
iDRAC Access via Host OS feature is configured properly or not.
[root@MyDevBox bin]# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- 10.10.0.0/16 anywhere tcp dpt:9999 to:169.254.0.1:443
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
SNAT tcp -- anywhere 169.254.0.1 tcp dpt:https to:169.254.0.2
If the DNAT and SNAT rules were not added, the other instances of iptables command needs to be
stopped and using CLI the feature needs to be reconfigured again.
4.2 Failure to access iDRAC via Host OS due to disabling of IP
Forwarding in Linux kernel
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
IP Forwarding is a concept to make Linux based machines to send data from one network to other. In
order to forward the connection request to iDRAC, the host OS should enable IP Forwarding in the
kernel.
If it is disabled iDRAC Access via Host OS feature fails.
Recovery Action
It can be enabled using the command
“echo 1 > /proc/sys/net/ipv4/ip_forward”