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

iDRAC access via Host OS Experimental Feature

Page 257 highlights

Beginning with iSM 2.4.0, you can configure Agent-x as the default protocol for in-band iDRAC SNMP alerts using the following command: ./Enable-iDRACSNMPTrap.sh 1/agentx -force If -force is not specified, ensure that the net-SNMP is configured and restart the snmpd service. • To enable this feature: Enable-iDRACSNMPTrap.sh 1 Enable-iDRACSNMPTrap.sh enable • To disable this feature: Enable-iDRACSNMPTrap.sh 0 Enable-iDRACSNMPTrap.sh disable NOTE: The --force option configures the Net-SNMP to forward the traps. However, you must configure the trap destination. • VMware ESXi operating system On all iSM supported ESXi operating systems, the iSM v2.3 supports a Common Management Programming Interface (CMPI) method provider to enable this feature remotely by using the WinRM remote commands. winrm i EnableInBandSNMPTraps http://schemas.dell.com/wbem/wscim/1/cim-schema/2/root/cimv2/ dcim/DCIM_iSMService? __cimnamespace=root/cimv2/dcim+InstanceID=iSMExportedFunctions -u: -p: r:https://:443/wsman -a:basic -encoding:utf-8 -skipCNCheck -skipCACheck skipRevocationcheck @{state="[0/1]"} NOTE: You must review and configure the VMware ESXi system-wide SNMP settings for traps. NOTE: For more details, refer to the In-BandSNMPAlerts technical white paper available at http:// en.community.dell.com/techcenter/extras/m/white_papers. iDRAC access via Host OS (Experimental Feature) By using this feature, you can configure and monitor the hardware parameters through iDRAC Web interface, WSMAN, and Redfish interfaces using the host IP address without configuring the iDRAC IP address. You can use the default iDRAC credentials if the iDRAC server is not configured or continue to use the same iDRAC credentials if the iDRAC server was configured earlier. iDRAC access via Windows Operating Systems You can perform this task by using the following methods: • Install the iDRAC access feature by using the webpack. • Configure using iSM PowerShell script Installation by using MSI You can install this feature by using the web-pack. This feature is disabled on a typical iSM installation. If enabled, the default listening port number is 1266. You can modify this port number within the range 1024 through 65535. iSM redirects the connection to the iDRAC. iSM then creates an inbound firewall rule, OS2iDRAC. The listening port number is added to the OS2iDRAC firewall rule in the host operating system, which allows incoming connections. The firewall rule is enabled automatically when this feature is enabled. Beginning with iSM 2.4.0, you can retrieve the current status and listening-port configuration by using the following PowerShell cmdlet: Enable-iDRACAccessHostRoute -status get The output of this command indicates whether this feature is enabled or disabled. If the feature is enabled, it displays the listening-port number. Using iDRAC Service Module 257

  • 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

Beginning with iSM 2.4.0, you can configure Agent-x as the default protocol for in-band iDRAC SNMP alerts using the following
command:
./Enable-iDRACSNMPTrap.sh 1/agentx –force
If
–force
is not specified, ensure that the net-SNMP is configured and restart the snmpd service.
To enable this feature:
Enable-iDRACSNMPTrap.sh 1
Enable-iDRACSNMPTrap.sh enable
To disable this feature:
Enable-iDRACSNMPTrap.sh 0
Enable-iDRACSNMPTrap.sh disable
NOTE:
The --force option configures the Net-SNMP to forward the traps. However, you must configure the trap
destination.
VMware ESXi operating system
On all iSM supported ESXi operating systems, the iSM v2.3 supports a Common Management Programming Interface (CMPI) method
provider to enable this feature remotely by using the WinRM remote commands.
dcim/DCIM_iSMService?
__cimnamespace=root/cimv2/dcim+InstanceID=iSMExportedFunctions -u:<user-name> -p:<passwd> -
r:https://<remote-host-name
ip-address>:443/wsman -a:basic -encoding:utf-8 -skipCNCheck -skipCACheck -
skipRevocationcheck @{state="[0/1]"}
NOTE:
You must review and configure the VMware ESXi system-wide SNMP settings for traps.
NOTE:
For more details, refer to the In-BandSNMPAlerts technical white paper available at http://
en.community.dell.com/techcenter/extras/m/white_papers.
iDRAC access via Host OS (Experimental Feature)
By using this feature, you can configure and monitor the hardware parameters through iDRAC Web interface, WSMAN, and Redfish
interfaces using the host IP address without configuring the iDRAC IP address. You can use the default iDRAC credentials if the iDRAC
server is not configured or continue to use the same iDRAC credentials if the iDRAC server was configured earlier.
iDRAC access via Windows Operating Systems
You can perform this task by using the following methods:
Install the iDRAC access feature by using the webpack.
Configure using iSM PowerShell script
Installation by using MSI
You can install this feature by using the web-pack. This feature is disabled on a typical iSM installation. If enabled, the default listening port
number is 1266. You can modify this port number within the range 1024 through 65535. iSM redirects the connection to the iDRAC. iSM
then creates an inbound firewall rule, OS2iDRAC. The listening port number is added to the OS2iDRAC firewall rule in the host operating
system, which allows incoming connections. The firewall rule is enabled automatically when this feature is enabled.
Beginning with iSM 2.4.0, you can retrieve the current status and listening-port configuration by using the following PowerShell cmdlet:
Enable-iDRACAccessHostRoute –status get
The output of this command indicates whether this feature is enabled or disabled. If the feature is enabled, it displays the listening-port
number.
Using iDRAC Service Module
257