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

In-band Support for iDRAC SNMP Alerts

Page 256 highlights

On all iSM supported ESXi operating systems, the iSM v2.3 supports a Common Management Programming Interface (CMPI) method provider to perform the iDRAC reset remotely by using the WinRM remote commands. winrm i iDRACHardReset 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 NOTE: VMware ESXi operating system does not prompt for confirmation before resetting the iDRAC. NOTE: Due to limitations on the VMware ESXi operating system, iDRAC connectivity is not restored completely after the reset. Ensure that you manually reset iDRAC. For more information, see the "Remote iDRAC Hard Reset" in this document. Error Handling Table 46. Error Handling Result 0 1 2 3 4 Description Success Unsupported BIOS version for iDRAC reset Unsupported platform Access denied iDRAC reset failed In-band Support for iDRAC SNMP Alerts By using iDRAC Service Module v2.3, you can receive SNMP alerts from the host operating system, which is similar to the alerts that are generated by iDRAC. You can also monitor the iDRAC SNMP alerts without configuring the iDRAC and manage the server remotely by configuring the SNMP traps and destination on the host OS. In iDRAC Service Module v2.3 or later, this feature converts all the Lifecycle logs replicated in the OS logs into SNMP traps. NOTE: This feature is active only if the Lifecycle Logs replication feature is enabled. NOTE: On Linux operating systems, this feature requires a master or OS SNMP enabled with SNMP multiplexing (SMUX) protocol. By default, this feature is disabled. Though the In-band SNMP alerting mechanism can coexist along with iDRAC SNMP alerting mechanism, the recorded logs may have redundant SNMP alerts from both the sources. It is recommended to either use the in-band or out-of-band option, instead of using both. Command usage This section provides the command usages for Windows, Linux, and ESXi operating systems. • Windows operating system • Using the local Windows Management Instrumentation (WMI): winrm i EnableInBandSNMPTraps wmi/root/cimv2/dcim/DCIM_iSMService?InstanceID="iSMExportedFunctions" @{state="[0/1]"} • Using the remote WMI interface: winrm i EnableInBandSNMPTraps wmi/root/cimv2/dcim/DCIM_iSMService? InstanceID="iSMExportedFunctions" @{state="[0/1]"} -u: -p: -r:http:///wsman encoding:utf-8 -skipCACheck -skipCNCheck -a:Basic - • Linux operating system On all iSM supported Linux operating system, iSM provides an executable command. You can run this command by logging into the operating system by using SSH or equivalent. 256 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

On all iSM supported ESXi operating systems, the iSM v2.3 supports a Common Management Programming Interface (CMPI) method
provider to perform the iDRAC reset remotely by using the WinRM remote commands.
DCIM_iSMService?__cimnamespace=root/cimv2/dcim+InstanceID=
iSMExportedFunctions -u:<root-username> -p:<passwd> -r:https://<Host-IP>:443/wsman -
a:basic -encoding:utf-8 -skipCNCheck -skipCACheck -skipRevocationcheck
NOTE:
VMware ESXi operating system does not prompt for confirmation before resetting the iDRAC.
NOTE:
Due to limitations on the VMware ESXi operating system, iDRAC connectivity is not restored completely after
the reset. Ensure that you manually reset iDRAC. For more information, see the “Remote iDRAC Hard Reset” in this
document.
Error Handling
Table 46. Error Handling
Result
Description
0
Success
1
Unsupported BIOS version for iDRAC reset
2
Unsupported platform
3
Access denied
4
iDRAC reset failed
In-band Support for iDRAC SNMP Alerts
By using iDRAC Service Module v2.3, you can receive SNMP alerts from the host operating system, which is similar to the alerts that are
generated by iDRAC.
You can also monitor the iDRAC SNMP alerts without configuring the iDRAC and manage the server remotely by configuring the SNMP
traps and destination on the host OS. In iDRAC Service Module v2.3 or later, this feature converts all the Lifecycle logs replicated in the
OS logs into SNMP traps.
NOTE:
This feature is active only if the Lifecycle Logs replication feature is enabled.
NOTE:
On Linux operating systems, this feature requires a master or OS SNMP enabled with SNMP multiplexing
(SMUX) protocol.
By default, this feature is disabled. Though the In-band SNMP alerting mechanism can coexist along with iDRAC SNMP alerting
mechanism, the recorded logs may have redundant SNMP alerts from both the sources. It is recommended to either use the in-band or
out-of-band option, instead of using both.
Command usage
This section provides the command usages for Windows, Linux, and ESXi operating systems.
Windows operating system
Using the local Windows Management Instrumentation (WMI):
winrm i EnableInBandSNMPTraps
wmi/root/cimv2/dcim/DCIM_iSMService?InstanceID="iSMExportedFunctions" @{state="[0/1]"}
Using the remote WMI interface:
winrm i EnableInBandSNMPTraps wmi/root/cimv2/dcim/DCIM_iSMService?
InstanceID="iSMExportedFunctions" @{state="[0/1]"}
-u:<admin-username> -p:<admin-passwd> -r:http://<remote-hostname OR IP>/wsman
-a:Basic -
encoding:utf-8 -skipCACheck –skipCNCheck
Linux operating system
On all iSM supported Linux operating system, iSM provides an executable command. You can run this command by logging into the
operating system by using SSH or equivalent.
256
Using iDRAC Service Module