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

Racadm

Page 291 highlights

• To remove port group: esxcfg-vmknic -d -p "iDRAC Network" • To remove vSwitch: esxcfg-vswitch -d vSwitchiDRACvusb NOTE: You can reinstall iDRAC Service Module on the VMware ESXi server as this is not a functional issue for the server. Where is the Replicated Lifecycle log available on the operating system? To view the replicated Lifecycle logs: Table 49. Lifecycle logs Operating System Microsoft Windows Location Event viewer > Windows Logs > System. All the iDRAC Service Module Lifecycle logs are replicated under the source name iDRAC Service Module. NOTE: In iSM version 2.1 and later, Lifecycle logs are replicated under the Lifecycle Controller Log source name. In iSM version 2.0 and earlier, the logs are replicated under iDRAC Service Module source name. NOTE: The location of the Lifecycle log can be configured using the iDRAC Service Module installer. You can configure the location while installing iDRAC Service Module or modifying the installer. Red Hat Enterprise Linux, SUSE Linux, CentOS, and Citrix XenServer VMware ESXi /var/log/messages /var/log/syslog.log What are the Linux-dependent packages or executables available for installation while completing the Linux installation? To see the list of Linux-dependent packages, see the Linux Dependencies section in the iDRAC Service Module User's Guide. RACADM After performing an iDRAC reset (using the racadm racreset command), if any command is issued, the following message is displayed. What does this indicate? ERROR: Unable to connect to RAC at specified IP address The message indicates that you must wait until the iDRAC completes the reset before issuing another command. When using RACADM commands and subcommands, some errors are not clear. You may see one or more of the following errors when using the RACADM commands: • Local RACADM error messages - Problems such as syntax, typographical errors, and incorrect names. • Remote RACADM error messages - Problems such as incorrect IP Address, incorrect user name, or incorrect password. During a ping test to iDRAC, if the network mode is switched between Dedicated and Shared modes, there is no ping response. Clear the ARP table on your system. Remote RACADM fails to connect to iDRAC from SUSE Linux Enterprise Server (SLES) 11 SP1. Make sure that the official openssl and libopenssl versions are installed. Run the following command to install the RPM packages: rpm -ivh --force < filename > where, filename is the openssl or libopenssl rpm package file. For example: rpm -ivh --force openssl-0.9.8h-30.22.21.1.x86_64.rpm rpm -ivh --force libopenssl0_9_8-0.9.8h-30.22.21.1.x86_64.rpm Frequently asked questions 291

  • 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

To remove port group:
esxcfg-vmknic -d -p "iDRAC Network"
To remove vSwitch:
esxcfg-vswitch -d vSwitchiDRACvusb
NOTE:
You can reinstall iDRAC Service Module on the VMware ESXi server as this is not a functional issue for the
server.
Where is the Replicated Lifecycle log available on the operating system?
To view the replicated Lifecycle logs:
Table 49. Lifecycle logs
Operating System
Location
Microsoft Windows
Event viewer
>
Windows Logs
>
System
. All the iDRAC Service
Module Lifecycle logs are replicated under the source name
iDRAC
Service Module
.
NOTE:
In iSM version 2.1 and later, Lifecycle logs are
replicated under the Lifecycle Controller Log source
name. In iSM version 2.0 and earlier, the logs are
replicated under iDRAC Service Module source name.
NOTE:
The location of the Lifecycle log can be
configured using the iDRAC Service Module installer.
You can configure the location while installing iDRAC
Service Module or modifying the installer.
Red Hat Enterprise Linux, SUSE Linux, CentOS, and Citrix
XenServer
/var/log/messages
VMware ESXi
/var/log/syslog.log
What are the Linux-dependent packages or executables available for installation while completing the Linux installation?
To see the list of Linux-dependent packages, see the
Linux Dependencies
section in the
iDRAC Service Module User's Guide
.
RACADM
After performing an iDRAC reset (using the racadm racreset command), if any command is issued, the following message is
displayed. What does this indicate?
ERROR: Unable to connect to RAC at specified IP address
The message indicates that you must wait until the iDRAC completes the reset before issuing another command.
When using RACADM commands and subcommands, some errors are not clear.
You may see one or more of the following errors when using the RACADM commands:
Local RACADM error messages — Problems such as syntax, typographical errors, and incorrect names.
Remote RACADM error messages — Problems such as incorrect IP Address, incorrect user name, or incorrect password.
During a ping test to iDRAC, if the network mode is switched between Dedicated and Shared modes, there is no ping
response.
Clear the ARP table on your system.
Remote RACADM fails to connect to iDRAC from SUSE Linux Enterprise Server (SLES) 11 SP1.
Make sure that the official openssl and libopenssl versions are installed. Run the following command to install the RPM packages:
rpm -ivh --force < filename >
where,
filename
is the openssl or libopenssl rpm package file.
For example:
rpm -ivh --force openssl-0.9.8h-30.22.21.1.x86_64.rpm
rpm -ivh --force libopenssl0_9_8-0.9.8h-30.22.21.1.x86_64.rpm
Frequently asked questions
291