Dell PowerEdge R830 Integrated Remote Access Controller 8 Version 2.70.70.70 U - Page 258

Using iDRAC Service Module from iDRAC web interface

Page 258 highlights

NOTE: Ensure that the Microsoft IP Helper Services is running on your system for this feature to function. To access the iDRAC Web interface, use the format https:// or OS-IP>:443/login.html in the browser, where: • - Complete host name of the server on which iSM is installed and configured for iDRAC access via OS feature. You can use the OS IP address if the host name is not present. • 443 - Default iDRAC port number. This is called the Connect Port number to which all the incoming connections on listen port number are redirected. You can modify the port number through iDRAC Web interface, WSMAN, and RACADM interfaces. Configuration by using iSM PowerShell cmdlet If this feature is disabled while installing iSM, you can enable the feature by using the following Windows PowerShell command provided by iSM: Enable-iDRACAccessHostRoute If the feature is already configured, you can disable or modify it by using the PowerShell command and the corresponding options. The available options are as follows: • Status - This parameter is mandatory. The values are not case sensitive and the value can be true, false, or get. • Port - This is the listening port number. If you do not provide a port number, the default port number (1266) is used. If the Status parameter value is FALSE, then you can ignore rest of the parameters. You must enter a new port number that is not already configured for this feature. The new port number settings overwrite the existing OS2iDRAC in-bound firewall rule and you can use the new port number to connect to iDRAC. The value range is from 1024 to 65535. • IPRange - This parameter is optional and it provides a range of IP addresses that are allowed to connect to iDRAC through the host operating system. The IP address range format is in Classless Inter-Domain Routing (CIDR) format, which is a combination of IP address and subnet mask. For example, 10.94.111.21/24. Access to iDRAC is restricted for IP addresses that are not within the range. NOTE: This feature supports only IPv4 addresses. iDRAC access via Linux Operating Systems You can install this feature by using the setup.sh file that is available with the Web pack. This feature is disabled on a default or typical iSM installation. To get the status of this feature, use the following command: Enable-iDRACAccessHostRoute get-status To install, enable, and configure this feature, use the following command: ./Enable-iDRACAccessHostRoute [ ] Coexistence of OpenManage Server Administrator and iDRAC Service Module In a system, both OpenManage Server Administrator and the iDRAC Service Module can co-exist and continue to function correctly and independently. If you have enabled the monitoring features during the iDRAC Service Module installation, then after the installation is complete if the iDRAC Service Module detects the presence of OpenManage Server Administrator, it disables the set of monitoring features that overlap. If OpenManage Server Administrator is running, the iDRAC Service Module disables the overlapping monitoring features after logging to the OS and iDRAC. When you re-enable these monitoring features through the iDRAC interfaces later, the same checks are performed and the features are enabled depending on whether OpenManage Server Administrator is running or not. Using iDRAC Service Module from iDRAC web interface To use the iDRAC Service Module from the iDRAC web interface: 1. Go to Overview > Server > Service Module. 258 Using iDRAC Service Module

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

NOTE:
Ensure that the Microsoft IP Helper Services is running on your system for this feature to function.
To access the iDRAC Web interface, use the format
https://<host-name>
or
OS-IP>:443/login.html
in the browser, where:
<host-name>
— Complete host name of the server on which iSM is installed and configured for iDRAC access via OS feature. You
can use the OS IP address if the host name is not present.
443
— Default iDRAC port number. This is called the Connect Port number to which all the incoming connections on listen port
number are redirected. You can modify the port number through iDRAC Web interface, WSMAN, and RACADM interfaces.
Configuration by using iSM PowerShell cmdlet
If this feature is disabled while installing iSM, you can enable the feature by using the following Windows PowerShell command provided by
iSM:
Enable-iDRACAccessHostRoute
If the feature is already configured, you can disable or modify it by using the PowerShell command and the corresponding options. The
available options are as follows:
Status
— This parameter is mandatory. The values are not case sensitive and the value can be
true
,
false
, or
get
.
Port
— This is the listening port number. If you do not provide a port number, the default port number (1266) is used. If the
Status
parameter value is FALSE, then you can ignore rest of the parameters. You must enter a new port number that is not already
configured for this feature. The new port number settings overwrite the existing OS2iDRAC in-bound firewall rule and you can use the
new port number to connect to iDRAC. The value range is from 1024 to 65535.
IPRange
— This parameter is optional and it provides a range of IP addresses that are allowed to connect to iDRAC through the host
operating system. The IP address range format is in Classless Inter-Domain Routing (CIDR) format, which is a combination of IP
address and subnet mask. For example, 10.94.111.21/24. Access to iDRAC is restricted for IP addresses that are not within the range.
NOTE:
This feature supports only IPv4 addresses.
iDRAC access via Linux Operating Systems
You can install this feature by using the
setup.sh
file that is available with the Web pack. This feature is disabled on a default or typical
iSM installation. To get the status of this feature, use the following command:
Enable-iDRACAccessHostRoute get-status
To install, enable, and configure this feature, use the following command:
./Enable-iDRACAccessHostRoute <Enable-Flag> [ <source-port> <source-IP-range/source-ip-range-
mask>]
Coexistence of OpenManage Server Administrator and
iDRAC Service Module
In a system, both OpenManage Server Administrator and the iDRAC Service Module can co-exist and continue to function correctly and
independently.
If you have enabled the monitoring features during the iDRAC Service Module installation, then after the installation is complete if the
iDRAC Service Module detects the presence of OpenManage Server Administrator, it disables the set of monitoring features that overlap.
If OpenManage Server Administrator is running, the iDRAC Service Module disables the overlapping monitoring features after logging to
the OS and iDRAC.
When you re-enable these monitoring features through the iDRAC interfaces later, the same checks are performed and the features are
enabled depending on whether OpenManage Server Administrator is running or not.
Using iDRAC Service Module from iDRAC web
interface
To use the iDRAC Service Module from the iDRAC web interface:
1.
Go to
Overview
>
Server
>
Service Module
.
258
Using iDRAC Service Module