TORRE TIPO A+
6.2 Primera Etapa Trabajos Preliminares
Directory tests enable you to validate the configured directory settings. The directory test results are reset when directory settings are saved, or when the directory tests are started.
To validate the configured directory settings:
1. ClickTest Settingson the Security→Directorypage. TheDirectory Testspage opens.
This page displays the results of a series of simple tests designed to validate the current directory settings. Also, it includes a test log that shows test results and detected issues. After your directory settings are configured correctly, you do not need to rerun these tests. TheDirectory Testspage does not require you to log in as a directory user.
2. In theDirectory Test Controlssection, enter the DN and password of a directory administrator.
• Directory Administrator Distinguished Name—Searches the directory for iLO objects, roles, and search contexts. This user must have the right to read the directory.
• Directory Administrator Password—Authenticates the directory administrator.
HP recommends that you use the same credentials that you used when creating the iLO objects in the directory. These credentials are not stored by iLO; they are used to verify the iLO object and user search contexts.
3. In theDirectory Test Controlssection, enter a test user name and password.
• Test User Name—Tests login and access rights to iLO. This name does not need to be fully distinguished because user search contexts can be applied. This user must be associated with a role for this iLO.
• Test User Password—Authenticates the test user.
Typically, this account is used to access the iLO processor being tested. It can be the directory administrator account, but the tests cannot verify user authentication with a superuser account. These credentials are not stored by iLO.
4. ClickStart Test.
Several tests begin in the background, starting with a network ping of the directory user by establishing an SSL connection to the server and evaluating user privileges.
While the tests are running, the page refreshes periodically. You can stop the tests or manually refresh the page at any time.
Viewing directory test results
TheDirectory Test Resultssection shows the directory test status with the date and time of the last update.
• Overall Status—Summarizes the results of the tests.
Not Run—No tests were run.
◦
◦
Inconclusive—No results were reported.◦
Passed—No failures were reported.◦
Problem Detected—A problem was reported.◦
Failed—A specific subtest failed. Check the onscreen log to identify the problem.◦
Warning—One or more of the directory tests reported aWarningstatus.• Test—The name of each test.
For more information about the iLO directory tests, see“About the iLO directory tests” (page 78).
• Result—Reports status for a specific directory setting or an operation that uses one or more directory settings. These results are generated when a sequence of tests is run. The results stop when the tests run to completion, when a test failure prevents further progress, or when the tests are stopped. Test results follow:
◦
Passed—The test ran successfully. If more than one directory server was tested, all servers that ran this test were successful.◦
Not Run—The test was not run.◦
Failed—The test was unsuccessful on one or more directory servers. Directory support might not be available on those servers.◦
Warning—The test ran and reported a warning condition, for example, a certificate error. Check theNotescolumn for suggested actions to correct the warning condition.• Notes—Indicates the results of various phases of the directory tests. The data is updated with failure details and information that is not readily available, like the directory server certificate subject and which roles were evaluated successfully.
Using the directory test controls
TheDirectory Test Controlssection enables you to view the current state of the directory tests, adjust the test parameters, start and stop the tests, and refresh the page contents.
• In Progress—Indicates that directory tests are currently being performed in the background. ClickStop Testto cancel the current tests, or clickRefreshto update the contents of the page with the latest results. Using theStop Testbutton might not stop the tests immediately.
• Not Running—Indicates that directory tests are current, and that you can supply new parameters to run the tests again. Use theStart Testbutton to start the tests and use the current test control values. Directory tests cannot be started after they are already in progress.
• Stopping—Indicates that directory tests have not yet reached a point where they can stop. You cannot restart tests until the status changes toNot Running. Use theRefreshbutton to determine whether the tests are complete.
For information about the parameters you can enter, see“Running directory tests” (page 75).
About the iLO directory tests
Descriptions of the directory tests follow:
• Directory Server DNS Name—If the directory server is defined in FQDN format
(directory.company.com), iLO resolves the name from FQDN format to IP format, and queries the configured DNS server.
If the test is successful, iLO obtained an IP address for the configured directory server. If iLO cannot obtain an IP address for the directory server, this test and all subsequent tests fail. If the directory server is configured with an IP address, iLO skips this test.
If a failure occurs:
1. Verify that the DNS server configured in iLO is correct.
2. Verify that the directory server FQDN is correct.
3. As a troubleshooting tool, use an IP address instead of the FQDN.
4. If the problem persists, check the DNS server records and network routing.
• Ping Directory Server—iLO initiates a ping to the configured directory server.
The test is successful if iLO receives the ping response; it is unsuccessful if the directory server does not reply to iLO.
If the test fails, iLO will continue with the subsequent tests. If a failure occurs:
1. Check to see if a firewall is active on the directory server.
2. Check for network routing issues.
• Connect to Directory Server—iLO attempts to negotiate an LDAP connection with the directory server.
If the test is successful, iLO was able to initiate the connection.
If the test fails, iLO was not able to initiate an LDAP connection with the specified directory server. Subsequent tests will stop.
If a failure occurs:
1. Verify that the configured directory server is the correct host.
2. Verify that iLO has a clear communication path to the directory server through port 636 (consider any routers or firewalls between iLO and the directory server).
3. Verify that any local firewall on the directory server is enabled to allow communications through port 636.
• Connect using SSL—iLO initiates SSL handshake and negotiation and LDAP communications with the directory server through port 636.
If the test is successful, the SSL handshake and negotiation between iLO and the directory server were successful.
If a failure occurs, the directory server is not enabled for SSL negotiations.
If you are using Microsoft Active Directory, verify that Active Directory Certificate Services are installed.
• Bind to Directory Server—This test binds the connection with the user name specified in the test boxes. If no user is specified, iLO does an anonymous bind.
If the test is successful, the directory server accepted the binding. If a failure occurs:
1. Verify that the directory server allows anonymous binding.
3. If you verified that the user name is correct, try using other user-name formats; for example,
[email protected],DOMAIN\username,username (called Display Name in Active Directory), oruserlogin.
4. Verify that the specified user is allowed to log in and is enabled.
• Directory Administrator Login—IfDirectory Administrator Distinguished NameandDirectory Administrator Passwordwere specified, iLO uses these values to log in to the directory server as an administrator. These boxes are optional.
• User Authentication—iLO authenticates to the directory server with the specified user name and password.
If the test is successful, the supplied user credentials are correct. If the test fails, the user name and/or password is incorrect. If a failure occurs:
1. If you verified that the user name is correct, try using other user-name formats; for example,
[email protected],DOMAIN\username, username(called Display Name in Active Directory), oruserlogin.
2. Verify that the specified user is allowed to log in and is enabled.
3. Check to see if the specified user name is restricted by logon hours or IP-based logging.
• User Authorization—This test verifies that the specified user name is part of the specified directory group, and is part of the directory search context specified during directory services configuration.
If a failure occurs:
1. Verify that the specified user name is part of the specified directory group.
2. Check to see if the specified user name is restricted by logon hours or IP-based logging.
• Directory User Contexts—IfDirectory Administrator Distinguished Namewas specified, iLO tries to search the specified context.
If the test is successful, iLO found the context by using the administrator credentials to search for the container in the directory.
Contexts that begin with "@" can be tested only by user login. A failure indicates that the container could not be located.
• LOM Object Exists—This test searches for the iLO object in the directory server by using the
LOM Object Distinguished Nameconfigured on theSecurity→Directorypage.
NOTE: You can enter aLOM Object Distinguished Nameon theSecurity→Directorypage only whenUse HP Extended Schemais selected. This test is run even if LDAP Directory Authenticationis disabled.
If the test is successful, iLO found the object that represents itself. If a failure occurs:
1. Verify that the LDAP FQDN of the LOM object is correct.
2. Try to update the HP Extended Schema and snap-ins in the directory server by updating the HP Directories Support for ProLiant Management Processors software.