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

Logging in to iDRAC SSO using iDRAC web interface, Accessing iDRAC using remote RACADM

Page 32 highlights

Logging in to iDRAC SSO using iDRAC web interface Before logging in to iDRAC using Single Sign-On, make sure that: • You have logged in to your system using a valid Active Directory user account. • Single Sign-On option is enabled during Active Directory configuration. To log in to iDRAC using web interface: 1. Log in to your management station using a valid Active Directory account. 2. In a web browser, type https://[FQDN address] NOTE: If the default HTTPS port number (port 443) has been changed, type: https://[FQDN address]:[port number] where, [FQDN address] is the iDRAC FQDN (iDRACdnsname.domain. name) and [port number] is the HTTPS port number. NOTE: If you use IP address instead of FQDN, SSO fails. iDRAC logs you in with appropriate Microsoft Active Directory privileges, using your credentials that were cached in the operating system when you logged in using a valid Active Directory account. Logging in to iDRAC SSO using CMC web interface Using the SSO feature, you can launch iDRAC web interface from CMC web interface. A CMC user has the CMC user privileges when launching iDRAC from CMC. If the user account is present in CMC and not in iDRAC, the user can still launch iDRAC from CMC. If iDRAC network LAN is disabled (LAN Enabled = No), SSO is not available. If the server is removed from the chassis, iDRAC IP address is changed, or there is a problem in iDRAC network connection, the option to Launch iDRAC is grayed-out in the CMC web interface. For more information, see the Chassis Management Controller User's Guide available at dell.com/support/manuals. Accessing iDRAC using remote RACADM You can use remote RACADM to access iDRAC using RACADM utility. For more information, see the iDRAC RACADM Command Line Interface Reference Guide available at dell.com/idracmanuals. If the management station has not stored the iDRAC's SSL certificate in its default certificate storage, a warning message is displayed when you run the RACADM command. However, the command is executed successfully. NOTE: The iDRAC certificate is the certificate iDRAC sends to the RACADM client to establish the secure session. This certificate is either issued by a CA or self-signed. In either case, if the management station does not recognize the CA or signing authority, a warning is displayed. Related tasks Validating CA certificate to use remote RACADM on Linux Validating CA certificate to use remote RACADM on Linux Before running remote RACADM commands, validate the CA certificate that is used for secure communications. To validate the certificate for using remote RACADM: 1. Convert the certificate in DER format to PEM format (using openssl command-line tool): openssl x509 -inform pem -in [yourdownloadedderformatcert.crt] -outform pem -out [outcertfileinpemformat.pem] -text 2. Find the location of the default CA certificate bundle on the management station. For example, for RHEL5 64 bit, it is /etc/pki/tls/ cert.pem. 3. Append the PEM formatted CA certificate to the management station CA certificate. For example, use the cat command: cat testcacert.pem >> cert.pem 32 Logging in to iDRAC

  • 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

Logging in to iDRAC SSO using iDRAC web interface
Before logging in to iDRAC using Single Sign-On, make sure that:
You have logged in to your system using a valid Active Directory user account.
Single Sign-On option is enabled during Active Directory configuration.
To log in to iDRAC using web interface:
1.
Log in to your management station using a valid Active Directory account.
2.
In a web browser, type
https://[FQDN address]
NOTE:
If the default HTTPS port number (port 443) has been changed, type:
https://[FQDN address]:[port
number]
where,
[FQDN address]
is the iDRAC FQDN (iDRACdnsname.domain. name) and
[port number]
is the
HTTPS port number.
NOTE:
If you use IP address instead of FQDN, SSO fails.
iDRAC logs you in with appropriate Microsoft Active Directory privileges, using your credentials that were cached in the operating
system when you logged in using a valid Active Directory account.
Logging in to iDRAC SSO using CMC web interface
Using the SSO feature, you can launch iDRAC web interface from CMC web interface. A CMC user has the CMC user privileges when
launching iDRAC from CMC. If the user account is present in CMC and not in iDRAC, the user can still launch iDRAC from CMC.
If iDRAC network LAN is disabled (LAN Enabled = No), SSO is not available.
If the server is removed from the chassis, iDRAC IP address is changed, or there is a problem in iDRAC network connection, the option to
Launch iDRAC is grayed-out in the CMC web interface.
For more information, see the
Chassis Management Controller User’s Guide
available at
dell.com/support/manuals
.
Accessing iDRAC using remote RACADM
You can use remote RACADM to access iDRAC using RACADM utility.
For more information, see the
iDRAC RACADM Command Line Interface Reference Guide
available at
dell.com/idracmanuals
.
If the management station has not stored the iDRAC’s SSL certificate in its default certificate storage, a warning message is displayed
when you run the RACADM command. However, the command is executed successfully.
NOTE:
The iDRAC certificate is the certificate iDRAC sends to the RACADM client to establish the secure session. This
certificate is either issued by a CA or self-signed. In either case, if the management station does not recognize the CA
or signing authority, a warning is displayed.
Related tasks
Validating CA certificate to use remote RACADM on Linux
Validating CA certificate to use remote RACADM on Linux
Before running remote RACADM commands, validate the CA certificate that is used for secure communications.
To validate the certificate for using remote RACADM:
1.
Convert the certificate in DER format to PEM format (using openssl command-line tool):
openssl x509 -inform pem -in [yourdownloadedderformatcert.crt] –outform pem -out
[outcertfileinpemformat.pem] –text
2.
Find the location of the default CA certificate bundle on the management station. For example, for RHEL5 64 bit, it is
/etc/pki/tls/
cert.pem
.
3.
Append the PEM formatted CA certificate to the management station CA certificate.
For example, use the
cat command: cat testcacert.pem >> cert.pem
32
Logging in to iDRAC