Reference Guide

9 No Restrictions | iDRAC Access via Host Operating System
The available options are:
1. Status: The values are not case sensitive. This parameter is mandatory.
Values Range {TRUE, FALSE}
2. Port: This is the port number and is similar to what user is prompted for during iDRAC Service Module
installation. This parameter is mandatory, if the previous parameter “Status” is TRUE. If the Status value
is FALSE; then the rest of the parameters can be ignored. If the new port number entered is already
configured for this feature; then user is requested to enter a different port number. The existing
OS2iDRAC in-bound firewall rule is overwritten with this new port number settings. There-after user
have to connect to iDRAC using this new port number.
Values Range {1024 to 65535}
3. IPRange: This parameter is optional irrespective of the other two parameters. This depicts a range of
source IP addresses that are permitted to connect to iDRAC via the Host OS. The IP address range
format is CIDR format which is a combination of IP Address and Subnet Mask. Any other client outside
this specified range is not allowed to connect to iDRAC via Host OS.
Example: 10.10.10.10/24
This parameter, if specified is added to the Scope variant of the OS2iDRAC firewall rule.
NOTE: Ensure valid and reachable IP Range is specified. Else, iDRAC will not be accessible.
Sl. No.
OS2iDRAC configuration type
Example Command/Syntax
1.
Enable the feature
Enable-iDRACAccessHostRoute –status
true –port 1234
2.
Listen Port Modification
Enable-iDRACAccessHostRoute –status
true –port 2345
3.
Adding IP Range or allowed IPs
Enable-iDRACAccessHostRoute –status
true –port 2345 –iprange <10.10.10.3/24>
4.
Disabling the feature
Enable-iDRACAccessHostRoute –status
false
Any modification to the listen port number can modify the firewall rule “OS2iDRAC” and it can be disabled. This
must again be reviewed by the administrator and enabled as necessary.
NOTE: Disabling this feature removes the OS2iDRAC firewall rule from the list.
NOTE: Enabling or disabling this feature can create an audit log entry in the OS logs (Event Viewer.)
Like the PowerShell way of specifying IPRange values, iDRAC also supports Network Security to allow restricted
clients to connect to iDRAC. If the allowed IP Range is already configured in iDRAC before iSM installation; then
iSM shall configure the same on the Host OS as well for iDRAC Access via Host OS feature. Any subsequent
modification of IP Range in iDRAC shall not take effect. In other words, the IP range specified using the iDRAC
Service Module provided command line interfaces take precedences over the iDRAC IP Range Setting.