Manualshelf

Reference Guide

ManualsBrandsDell ManualsConverged InfrastructureEnterprise Solution Resources
891011121314151617
14 No Restrictions | iDRAC Access via Host Operating System
4.3
Failure to access iDRAC via Host OS due to a Firewall rule that is
configured by some other application to block the listen port
Symptoms
While trying to access iDRAC page through Host OS, it fails to connect to iDRAC page and throws the
error “The site can’t be reached.”
Reason
There are scenarios where there is other firewall rules from other applications that has blocked the
listen port that is configured for iDRAC Access via Host OS.
Recovery Action
The port has to be unblocked or a new port has to be configured for this feature to work. If firewall is
enabled after iDRAC Access via host OS configuration then re-configure the iDRAC Access via Host
OS with valid port. For more information on enabling iDRAC via Host OS, refer the Configuration using
Linux Command line section.
4.4
Failure to access iDRAC via Host OS due to a Firewall rule is
configured to block the IP
Symptoms
While trying to access iDRAC page through Host OS, it fails to connect to iDRAC page and displays the
error “The site can’t be reached.”
Reason
There are scenarios where there is other firewall rules from other applications or administrator that has
blocked the Source IP that is configured for accessing iDRAC via Host OS.
Recovery Action
The IP Address has to be unblocked for accessing the iDRAC from that Source IP.
4.5
Failure to access iDRAC via Host OS during iDRAC reset
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
When iDRAC reset is in progress, it fails to access the iDRAC via Host OS until it comes up.
4.6
Failure to access iDRAC via Host OS while iDRAC is unavailable
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
When the iDRAC Firmware update is in progress, accessing iDRAC via Host OS fails. Only after the iDRAC
comes up, the user is able to access the iDRAC.