Configuring and Monitoring DNS and LDAP Servers eG Enterprise v5.6

Restricted Rights Legend The information contained in this document is confidential and subject to change without notice. No part of this document may be reproduced or disclosed to others without the prior permission of eG Innovations, Inc. eG Innovations, Inc. makes no warranty of any kind with regard to the software and documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Trademarks Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Copyright © 2012 eG Innovations, Inc. All rights reserved.

Table of Contents CONFIGURING AND MONITORING DNS SERVERS ......................................................................................................................1 1.1

ADMINISTERING THE EG MANAGER TO MONITOR A DNS SERVER ................................................................................................1

CONFIGURING AND MONITORING WINDOWS DNS SERVER ..................................................................................................4 2.1 2.2

ADMINISTERING THE EG MANAGER TO WORK WITH A WINDOWS DNS SERVER ..........................................................................4 MONITORING THE WINDOWS DNS SERVER ....................................................................................................................................6 2.2.1 Troubleshooting .................................................................................................................................................................6

CONFIGURING AND MONITORING EXTERNAL DNS SERVERS...............................................................................................7 3.1 3.2

ADMINISTERING THE EG MANAGER TO WORK WITH AN EXTERNAL DNS SERVER ......................................................................7 MONITORING THE EXTERNAL DNS SERVER ...................................................................................................................................8

CONFIGURING AND MONITORING AN LDAP SERVER...............................................................................................................9 4.1 4.2

ADMINISTERING THE EG MANAGER TO MONITOR AN LDAP SERVER ...........................................................................................9 MONITORING THE LDAP SERVER .................................................................................................................................................10 4.2.1 Troubleshooting ...............................................................................................................................................................10

CONFIGURING AND MONITORING NETSCAPE DIRECTORY SERVERS .............................................................................11 5.1 5.2

ADMINISTERING THE EG MANAGER TO WORK WITH A NETSCAPE DIRECTORY SERVER .............................................................11 MONITORING THE NETSCAPE DIRECTORY SERVER ......................................................................................................................13

CONFIGURING AND MONITORING SUNONE DIRECTORY SERVER....................................................................................14 6.1 6.2

ADMINISTERING THE EG MANAGER TO WORK WITH A SUNONE DIRECTORY SERVER ...............................................................14 MONITORING THE SUNONE DIRECTORY SERVER ........................................................................................................................16

CONCLUSION..........................................................................................................................................................................................17

Table of Figures Figure 1.1: Viewing unmanaged DNS servers .............................................................................................................................................2 Figure 1.2: Managing DNS servers ..............................................................................................................................................................2 Figure 1.3: Configuring the test parameters of a DNS server ......................................................................................................................3 Figure 2.1: Selecting the Windows DNS server to be managed ..................................................................................................................5 Figure 2.2: Managing the Windows DNS server..........................................................................................................................................5 Figure 3.1: Adding an External DNS server.................................................................................................................................................8 Figure 4.1: Viewing the list of unmanaged LDAP servers ........................................................................................................................10 Figure 5.1: Selecting the Netscape Directory server to be managed..........................................................................................................12 Figure 5.2: Managing the Netscape Directory server.................................................................................................................................12 Figure 6.1: Adding a new SunONE Directory Server ................................................................................................................................14 Figure 6.2: The list of unconfigured tests for the SunONE Directory Server............................................................................................15 Figure 6.3: Configuring the SunONE Entry Cache test .............................................................................................................................15

Configuring

and

Monitoring

DNS

Servers

Chapter

1

Configuring and Monitoring DNS Servers This chapter focuses on the configuring and monitoring procedure associated with DNS servers.

1.1 1.

Administering the eG Manager to monitor a DNS Server

DNS servers use UDP port 53 for this operation. The eG manager is capable of autodiscovering DNS servers. Auto-discovered DNS servers are set as unmanaged by default. Use the COMPONENTS - MANAGE/UNMANAGE options in Figure 1.1 and Figure 1.2 to determine which DNS servers should be monitored. If the DNS server to be monitored is not autodiscovered, use the ADD/MODIFY COMPONENTS option to manually add the server.

1

Configuring

and

Monitoring

DNS

Servers

Figure 1.1: Viewing unmanaged DNS servers

Figure 1.2: Managing DNS servers 2.

When you attempt to sign out of the eG administrative interface, you will be prompted to

2

Configuring

and

Monitoring

DNS

Servers

configure the Processes test for the DNS server. Click on Processes test to configure it. The following screen will then appear:

Figure 1.3: Configuring the test parameters of a DNS server 3.

Based on the name of the DNS server’s process, configure the PROCESS parameter (see Figure 1.3) for the Processes test. For Unix systems, the DNS process is typically “named”.

For more details on configuring the PROCESS parameter, please refer to the Configuring and Monitoring Web Servers document. 4.

Once the Processes test is configured, start an internal agent on the system that hosts the DNS server. Also, ensure that the external agent is running so as to monitor the DNS server from an external perspective.

5.

To test the availability and response time for queries to the DNS server, the eG agent uses a Dns test. By default, this test requires no special configuration. A user can change the default configuration of the test to get it to perform additional tasks. For example, the TARGETS specification can be a comma separated list of host names / IP addresses that the DnsTest should attempt to resolve. Additionally, the RECURSIVE flag can be used to determine the type of queries to be issued to a DNS server. A DNS server supports two types of queries. For a non-recursive query, the DNS server attempts to respond to the request based on its local cache only. For a recursive query, a DNS server may use other DNS servers to respond to a request.

6.

To view the measurements collected during monitoring, log into the eG monitor interface to track the state of a DNS server.

3

Configuring

and

Monitoring

Windows

DNS

Server

Chapter

2

Configuring and Monitoring Windows DNS Server The eG Enterprise suite includes specialized models for DNS server executing in Windows environments. This section describes how to configure and manage Windows DNS servers.

2.1

Administering the eG Manager to work with a Windows DNS Server

To do the above, do the following: 1. Log into the eG administrative interface. 2.

If a Windows DNS server is already discovered, then directly proceed towards managing the same using the COMPONENTS -MANAGE/UNMANAGE page (Infrastructure -> Manage/Unmanage -> Servers ). However, if it is yet to be discovered, then run discovery (Infrastructure -> Discover -> Start) to get it discovered or add the server manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Add/Modify Servers). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENETS MANAGE/UNMANAGE page. Figure 2.1 and Figure 2.2 clearly illustrate the process of managing a Windows DNS server.

For more details on managing components, refer to the Configuring and Managing Web Servers document.

4

Configuring

and

Monitoring

Windows

DNS

Server

Figure 2.1: Selecting the Windows DNS server to be managed

Figure 2.2: Managing the Windows DNS server 3.

Next, sign out of the eG administrative interface.

5

Configuring

2.2

and

Monitoring

Windows

DNS

Server

Monitoring the Windows DNS Server

To monitor the Windows DNS server, do the following: 1.

Login as a monitor / supermonitor user.

2.

Click on the Components option in the menu bar, and select the Servers option from the Components menu.

3.

From the Components page that appears next, click on the Windows DNS server for which you wish to view measurements.

2.2.1

Troubleshooting If the Network test is reporting measures, but many of the other tests are not reporting measures, check if the internal agent is executing on the host that the DNS server is executing on. If the Dns test is not reporting measures, there may be a firewall between the external agent and the DNS server that could be blocking requests from the external agent to the DNS server. If the Processes test is not reporting measures, check if the parameters of this test have been configured via the eG admin interface.

For more details on configuring the PROCESS parameter, please refer to Configuring and Managing Web Servers document.

6

Configuring

and

Monitoring

External

DNS

Servers

Chapter

3

Configuring and Monitoring External DNS Servers eG Enterprise offers the DNS server model (discussed previously), which not only checks how well the DNS server performs host name resolutions, but also indicates how healthy the DNS server host is by reporting a wide variety of operating system-level metrics. However, some administrators might just need to verify whether the DNS server is available or not, and if so, how quickly it can resolve a host name to an IP address or vice-versa. Such administrators therefore, might want to "exclude" the host-level performance data from the monitoring model. To cater to the needs of such administrators, eG Enterprise offers an External DNS server model. This model only executes the DnsTest, which emulates a user request to the DNS server to ascertain its availability and responsiveness. This section explains how to configure and monitor the External DNS server.

3.1

Administering the eG Manager to Work with an External DNS Server

To administer eG so that it monitors the External DNS server, do the following: 1. Login as an administrator to the eG administrative interface 2.

Next, add the External DNS server manually using the ADD/MODIFY COMPONENTS page (Infrastructure->Components ->Add/Modify) (see Figure 3.1). Components manually added will be automatically managed by the eG Enterprise system (see Figure 3.1).

7

Configuring

and

Monitoring

External

DNS

Servers

Figure 3.1: Adding an External DNS server 3.

Finally, sign out of the administrative interface.

3.2

Monitoring the External DNS Server

1.

Login as a monitor / supermonitor to the eG monitor user interface

2.

Click on the independent External DNS server to view its Layer model, tests and measurements of the External DNS server.

8

Configuring

and

Monitoring

an

LDAP

Server

Chapter

4

Configuring and Monitoring an LDAP Server 4.1

Administering the eG Manager to monitor an LDAP Server

To administer the eG Manager to monitor an LDAP server, do the following: 1. Login to the eG administrative interface. 2.

The eG manager is capable of auto discovering LDAP servers. Auto-discovered LDAP servers are set as unmanaged by default. Use the COMPONENTS - MANAGE/UNMANAGE options in Figure 4.1 to determine which LDAP servers should be monitored. If the LDAP server to be monitored is not auto-discovered, use the ADD/MODIFY COMPONENTS option to manually add the server. The eG Enterprise system manages the components so added, automatically.

9

Configuring

and

Monitoring

an

LDAP

Server

Figure 4.1: Viewing the list of unmanaged LDAP servers 3.

Finally, sign out of the administrative interface.

4.2

Monitoring the LDAP Server

To view the measurements collected during monitoring, do the following: 1.

Log into the eG monitor interface to track the state of an LDAP server.

2.

Click on the Components option in the menu bar, and select the Servers option from the Components menu.

3.

Then, select the monitored LDAP server from the Components page that appears to view the layer model, tests and measurements of the LDAP server.

4.2.1

Troubleshooting

While monitoring an LDAP server, if the measure Tcp_connection_availability is 100% and the Availability is 0, then it indicates a problem with the server configuration. Alternatively, the search string provided as a parameter to the Ldap test may not be supported by the corresponding LDAP server. In this case, configure the test based on the directory structure configured for the target LDAP server (i.e., change the "cn=monitor" value with an appropriate alternative).

10

Configuring

and

Monitoring

Netscape

Directory

Servers

Chapter

5

Configuring and Monitoring Netscape Directory Servers This chapter describes how to configure and monitor Netscape Directory servers.

5.1

Administering the eG Manager to work with a Netscape Directory server

To do the above, do the following: 1. Log into the eG administrative interface. 2.

If a Netscape Directory server is already discovered, then directly proceed towards managing the same using the COMPONENTS - MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage). However, if it is yet to be discovered, then run discovery (Infrastructure -> Components -> Discover) to get it discovered or add the server manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 5.1 and Figure 5.2 clearly illustrate the process of managing a Netscape Directory Server.

For more details on managing components, refer to Configuring and Managing Web Servers document.

11

Configuring

and

Monitoring

Netscape

Directory

Servers

Figure 5.1: Selecting the Netscape Directory server to be managed

Figure 5.2: Managing the Netscape Directory server 3.

Next, sign out of the eG administrative interface.

12

Configuring

5.2

and

Monitoring

Netscape

Directory

Servers

Monitoring the Netscape Directory Server

To monitor the Netscape Directory server, do the following: 1.

Login as a monitor / supermonitor user.

2.

Click on the Components option in the menu bar, and select the Servers option from the Components menu.

3.

From the Components page that appears next, click on the Netscape Directory Server for which you wish to view measurements.

13

Configuring

and

Monitoring

SunONE

Directory

Server

Chapter

6

Configuring and Monitoring SunONE Directory Server This chapter describes how to configure and monitor the SunONE Directory Server.

6.1

Administering the eG Manager to work with a SunONE Directory Server

To do the above, do the following: 1. Log into the eG administrative interface. 2. Next, add the SunONE Directory Server manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify) (see Figure 6.1). Remember that components manually added are managed automatically by the eG Enterprise system.

Figure 6.1: Adding a new SunONE Directory Server 3.

Now, try to signout of the administrative interface. You will be prompted to configure a list of tests as shown in Figure 6.2.

14

Configuring

and

Monitoring

SunONE

Directory

Server

Figure 6.2: The list of unconfigured tests for the SunONE Directory Server 4.

Clicking on the SunOne Entry Cache test will result in Figure 6.3. This test reports the measures pertaining to the entry caches of this server.

Figure 6.3: Configuring the SunONE Entry Cache test 5.

Configure the following parameters as shown in Figure 6.3. a.

TEST PERIOD - How often should the test be executed

b.

HOST – The host for which the test is to be configured

c.

PORT - The port on which the server is listening

d.

DISTINGUISHEDNAME – This parameter represents the server's Distinguished name. This value is to be specified when the server requires explicit authentication of requests. By default, this attribute is set to "none", implying that authentication is not required.

e.

PASSWORD - Specify the password to be used for authenticating the request. The password is to be specified whenever the DISTINGUISHEDNAME is not "none".

f.

CONFIRM PASSWORD – Confirm the password by retyping it here.

g.

DATABASENAME - Specify the name of the database that you wish to monitor here. To figure out the name of the database, do the following: o

In the command prompt, login to the SUNONE Directory Server with appropriate user permission.

o

Run the command, for e.g., ps -aef | grep slapd to find out the directory on which this server is installed.

o

In this case, your directory location will be /var/Sun/mps/slapd-sunt1000/. Now, go to that particular directory and run the command ./monitor.

o

Now you can figure out the database names from the backendmonitordn entries of that particular directory.

15

Configuring

and

Monitoring

SunONE

Directory

Server

6.

Then, click the Update button in Figure 6.3 to update this configuration.

7.

Finally, signout of the administrative interface.

6.2

Monitoring the SunONE Directory Server

To monitor the SunONE Directory Server, do the following: 1.

Login as a monitor / supermonitor user.

2.

Click on the Components option in the menu bar, and select the Servers option from the Components menu.

3.

From the Components page that appears next, click on the SunONE Directory Server for which you wish to view measurements.

16

Conclusion

Chapter

7

Conclusion This document has described in detail the steps for configuring and monitoring the DNS and LDAP servers. For details of how to administer and use the eG Enterprise suite of products, refer to the user manuals. We will be adding new measurement capabilities into the future versions of the eG Enterprise suite. If you can identify new capabilities that you would like us to incorporate in the eG Enterprise suite of products, please contact [email protected]. We look forward to your support and cooperation. Any feedback regarding this manual or any other aspects of the eG Enterprise suite can be forwarded to [email protected].

17