HP Integrity Superdome 2 HP Integrity Superdome 2 Onboard Administrator User G - Page 179

Testing the directory login solution, Troubleshooting LDAP on Onboard Administrator, DOMAIN\Test Admin

Page 179 highlights

Testing the directory login solution 1. Log out of the current Onboard Administrator session, and then close all browser windows. 2. Browse to the Onboard Administrator, and then log in using one of the following options: • Test Admin • [email protected] • DOMAIN\Test Admin 3. Enter the corresponding password used for the user account. If you cannot log in with full Administrative privileges, see "Troubleshooting" (page 163). NOTE: You cannot login using your user name. For example, if your Account name is Jeff Allen and your account is jallen, you cannot login as jallen because this format is not now supported by LDAP. 4. Log off or sign out of Onboard Administrator, and then attempt to log in as Test Operator using one of the following options: • Test Operator • [email protected] • DOMAIN\Test Operator Enter the password used for the account. If this process succeeds, then the account has no access to any server blades, but full access to interconnect bays. Troubleshooting LDAP on Onboard Administrator To be sure that SSL is working on the Domain Controllers in your domain, open a browser and then navigate to https://:636 (substitute your Domain Controller for ). You can substitute in place of , which goes to DNS to verify which Domain Controller is now answering requests for the domain. Test multiple Domain Controllers to be sure that all of them have been issued a certificate. If SSL Testing the directory login solution 179

  • 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

Testing the directory login solution
1.
Log out of the current Onboard Administrator session, and then close all browser windows.
2.
Browse to the Onboard Administrator, and then log in using one of the following options:
Test Admin
DOMAIN\Test Admin
3.
Enter the corresponding password used for the user account. If you cannot log in with full
Administrative privileges, see
“Troubleshooting” (page 163)
.
NOTE:
You cannot login using your user name. For example, if your Account name is Jeff
Allen and your account is jallen, you cannot login as jallen because this format is not now
supported by LDAP.
4.
Log off or sign out of Onboard Administrator, and then attempt to log in as Test Operator
using one of the following options:
Test Operator
DOMAIN\Test Operator
Enter the password used for the account. If this process succeeds, then the account has no access
to any server blades, but full access to interconnect bays.
Troubleshooting LDAP on Onboard Administrator
To be sure that SSL is working on the Domain Controllers in your domain, open a browser and
then navigate to https://
<domain_controller>:
636 (substitute your Domain Controller for
<
domain_controller
>). You can substitute <
domain
> in place of <
domain controller
>,
which goes to DNS to verify which Domain Controller is now answering requests for the domain.
Test multiple Domain Controllers to be sure that all of them have been issued a certificate. If SSL
Testing the directory login solution
179