Service Response Monitor › Test Management › Create Tests › Active Directory Tests

Active Directory Tests

The Active Directory test monitors the amount of time required to connect to the Active Directory service on a Windows system, perform a standard user name/password authentication, and then perform a user-defined query.

Options and Arguments

Active Directory tests require the following specific options and arguments:

• Active Directory Server – The name of the Active Directory server that you are testing.

  Note: As of Service Availability r2.1 IPv6 addresses can be used, but they must be embedded in brackets, for example [0aff::230:6eff:fe4b:51db]:8080. Here 0aff::230:6eff:fe4b:51db represents the IPv6 address and 8080 represents the port number.

• Active Directory Domain – The domain in which the Active Directory server is located.
• User Name – A valid user name for the Active Directory server.
• Password – A password for the user name specified above. SRM stores the password in encrypded format.
• Query – The query to perform, using the LDAP query language.
• Filter – (Optional) A term on which to filter the results of your query.

You specify these options and arguments when you create or modify tests.

Examples

This section includes examples for monitoring the amount of time to connect to local and remote Active Directory servers.

Example 1: Testing a Local Active Directory Server

Use this example to create a test that monitors the amount of time to connect to the local Active Directory server named ADTest, authenticate the user name adUser and the encoded password, and then query for the term Registered Users on the mylab.com site.

To create a new test in a policy

1. Click + (New) on the Test Monitors toolbar.

   The New test pane appears.

2. From the Test Type list, select Active Directory.
3. In the Description field, specify ad_local.
4. In the Test Name field, specify Local Active Directory Test.
5. In the Test Interval field, specify 30.
6. In the Test Timeout field, specify 10.
7. In the Samples Per Interval field, specify 1.
8. In the Statistics Window field, specify 120.
9. In the Active Directory Server field, specify ADTEST.
10. In the Active Directory Domain field, specify mylab.com.
11. In the User Name field, specify ADUser.
12. In the Password field, specify ADPass.
13. In the Query field, specify cn=Registered,cn=Users,dc=mylab,dc=com.
14. In the Filter field, specify cn=*.
15. Accept defaults for all other fields.
16. Click Save Test.

When you commit the changes, SRM adds an entry similar to the following to the svcrsp.cf file:

{ 
index=23 
type=adir
desc="ad_local" 
dest="ADTEST" 
username="ADUser" 
encoded=yes 
password="bXVyaWM=" 
args="domain=mylab.com&query=cn=Registered,cn=Users,dc=mylab,dc=com&filter=cn=*" 
interval=30 
samples=1 
timeout=10 
window=120 
tos=0 
limit=0 
status=active 
name="Local Active Directory Test"
class=""
context=""
flags="1"
loglevel=1
}

Example 2: Testing a Remote Active Directory Server

Use this example to create a test that monitors the amount of time to connect to the remote Active Directory server at 10.0.0.234, authenticate the user name RemoteUser and the encoded password, and then query for the term Guest Users on the testlab.com site.

To create a new test in a policy

1. Click + (New) on the Test Monitors toolbar.

   The New test pane appears.

2. From the Test Type list, select Active Directory.
3. In the Description field, specify ad_remote.
4. In the Test Name field, specify Remote Active Directory Test.
5. In the Test Interval field, specify 30.
6. In the Test Timeout field, specify 10.
7. In the Samples Per Interval field, specify 1.
8. In the Statistics Window field, specify 120.
9. In the Active Directory Server field, specify 10.0.0.234.
10. In the Active Directory Domain field, specify Test.com.
11. In the User Name field, specify RemoteUser.
12. In the Password field, specify ADPass.
13. In the Query field, specify cn=Guest,cn=Users,dc=testlab,dc=com.
14. In the Filter field, specify cn=*.
15. Click Save Test.

When you commit the changes, SRM adds an entry similar to the following to the svcrsp.cf file:

{ 
index=24 
type=adir
desc="ad_remote" 
dest="10.0.0.234" 
username="RemoteUser" 
encoded=yes 
password="bXVyaWMe" 
args="domain=test.com&query=cn=Guest,cn=Users,dc=testlab,dc=com&filter=cn=*" 
interval=30 
samples=1 
timeout=10 
window=120 
tos=0 
status=active 
name="Remote Active Directory Test"
class=""
context=""
flags="1"
loglevel=2
}

For information about errors you may encounter when running Active Directory tests, see Active Directory Test Error Codes.