Configuring and Monitoring Microsoft Applications

Transcription

1 Configuring and Monitoring Microsoft Applications eg Enterprise v5.6

2 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 2013 eg Innovations, Inc. All rights reserved.

3 Table of Contents CONFIGURING AND MONITORING AN ACTIVE DIRECTORY SERVER Administering the eg Manager to monitor an Active Directory Server Monitoring the Active Directory Server... 5 CONFIGURING AND MONITORING EXTERNAL ACTIVE DIRECTORY (AD) SERVERS Administering the eg Manager to Work with an External AD Server Monitoring the External AD Server... 7 CONFIGURING AND MONITORING THE ACTIVE DIRECTORY (AD) CLUSTER SERVICE Administering the eg Manager to Work with an AD Cluster Service Monitoring the AD Cluster Service... 9 CONFIGURING AND MONITORING WINDOWS DOMAIN CONTROLLERS Administering the eg Manager to work with a Windows Domain Controller Monitoring the Windows Domain Controller CONFIGURING AND MONITORING THE WINDOWS INTERNET NAME SERVICE (WINS) Administering the eg Manager to work with a WINS Server Monitoring the WINS Server CONFIGURING AND MONITORING TERMINAL SERVER Administering the eg Manager to work with Terminal servers Monitoring the Terminal Server CONFIGURING AND MONITORING BIZTALK SERVER Administering the eg Manager to work with a BizTalk Server Monitoring the BizTalk Server CONFIGURING AND MONITORING BIZTALK SERVER Administering the eg Manager to work with a BizTalk server Monitoring the BizTalk server CONFIGURING AND MONITORING DHCP SERVERS Administering the eg Manager to work with a DHCP Server Monitoring the DHCP Server CONFIGURING AND MONITORING MICROSOFT PROXY SERVERS Administering the eg Manager to work with a Microsoft Proxy Server Monitoring the Microsoft Proxy Server CONFIGURING AND MONITORING MS PRINT SERVERS Administering the eg Manager to work with an MS Print Server Monitoring the MS Print Server CONFIGURING AND MONITORING MS FILE SERVERS Administering the eg Manager to Monitor an MS File Server Monitoring the MS File Server... 38

4 CONFIGURING AND MONITORING ISA PROXY SERVERS Administering the eg Manager to Work with the ISA Proxy Server Monitoring the ISA Proxy Server CONFIGURING AND MONITORING MICROSOFT RADIUS SERVERS Administering the eg Manager to Work with the Microsoft Radius Server Monitoring the Microsoft Radius Server CONFIGURING AND MONITORING THE MICROSOFT REMOTE AUTHENTICATION SERVICE (RAS) Administering the eg Manager to Work with the MS RAS Server Monitoring the Microsoft RAS Server CONFIGURING AND MONITORING WINDOWS CLUSTER Monitoring the Windows Cluster Server CONFIGURING AND MONITORING MICROSOFT FAST SEARCH SERVER Administering the eg Manager to monitor a Microsoft Fast Search Server Monitoring the Microsoft Fast Search Server CONCLUSION... 60

5 Table of Figures Figure 1.1: Viewing the list of unmanaged Active Directory servers... 2 Figure 1.2: Managing an Active Directory server... 2 Figure 1.3:List of unconfigured tests for an Active Directory server... 3 Figure 1.4: Configuring the ADServer test... 3 Figure 1.5: List of tests that are yet to be configured for the Active Directory server... 4 Figure 1.6: Configuring the Active Directory Checks test... 4 Figure 1.7: Configuring the Global Catalog Search test... 5 Figure 2.1: Adding an External AD server... 6 Figure 2.2: The list of unconfigured tests for an External AD server... 7 Figure 3.1: Adding an AD Cluster... 9 Figure 3.2: A segment containing the cluster service and the AD servers... 9 Figure 4.1: Selecting the Windows Domain Controller to manage Figure 4.2: Managing the Windows Domain Controller Figure 4.3: List of unconfigured tests for an Domain Controller server Figure 4.4: Configuring the Window Authentication test Figure 5.1: Selecting the WINS server to manage Figure 5.2: Managing the WINS server Figure 5.3: List of unconfigured tests for an WindowsProcesses test Figure 5.4: Configuring the Windows Processes test Figure 6.1: Selecting the Terminal server to manage Figure 6.2: Managing the Terminal server Figure 6.3: Unconfigured tests of the Terminal server Figure 6.4: Configuring the TerminalAuthentication test Figure 7.1:Adding a new BizTalk component Figure 8.1:Adding a new BizTalk server2010 component Figure 9.1: Viewing the list of unmanaged DHCP servers Figure 9.2: Managing a DHCP server Figure 10.1: Viewing the list of unmanaged Microsoft Proxy servers Figure 10.2: Managing an Micosoft Proxy server Figure 11.1: Viewing the list of unmanaged MS Print servers Figure 11.2: Managing an MS Print server Figure 12.1: Viewing the list of unmanaged MS File servers Figure 12.2: Managing an MS File server Figure 13.1: Viewing the list of unmanaged ISA Proxy servers Figure 13.2: Managing an ISA Proxy serverlist of unconfigured test for the ISA Proxy server Figure 13.3:List of unconfigured test for the ISA Proxy server Figure 13.4: Configuring of the Windows Processes test Figure 14.1: Adding a Microsoft Radius server Figure 15.1: Adding a Microsoft RAS server Figure 16.1: Selecting the config layer of the IIS Web server Figure 16.2: Selecting the Windows Cluster from the Disassociated Layers Figure 16.3: Associating the Windows Cluster to the top layer of the IIS Webserver Figure 16.4: Viewing the Cluster related tests in the Agents-Tests Configuration page Figure 17.1: Adding the Microsoft Fast Search Server Figure 17.2: List of unconfigured tests to be configured for the Microsoft Fast Search Server Figure 17.3: Configuring the Log Monitor test Figure 17.4: Configuring the Windows services test... 57

6 C o n f i g u r i n g a n d M o n i t o r i n g a n A c t i v e D i r e c t o r y S e r v e r Configuring and Monitoring an Active Directory Server The eg Enterprise suite provides extensive monitoring support to the Active Directory (AD) server operating on Windows 2000, 2003, and The specialized monitoring model that the eg Enterprise offers periodically executes a number of tests on the AD server to extract a wide gamut of metrics indicating the availability, responsiveness, and overall health of the AD server and its underlying operating system. Using this model, Active Directory servers can be monitored in an agent-based or an agentless manner. This section discusses how to administer and monitor an Active Directory server. 1.1 Administering the eg Manager to monitor an Active Directory Server An Active Directory server is an integral part of a Windows 2000 server installation. 1. If an Active Directory server is automatically discovered by the eg Manager, it can be managed by the COMPONENTS - MANAGE/UNMANAGE page that appears when the Infrastructure -> Components -> Manage/Unmanage menu sequence is used. The screens below will guide you through this process. If an Active Directory server is not discovered automatically, then the ADD/MODIFY COMPONENTS page can be used to manually add an Active Directory server for monitoring. In such a case, the manual management procedure can be dispensed with, as the eg Enterprise system automatically manages added components. For more details on managing components, refer to Configuring and Monitoring Mail Servers document. 1

7 C o n f i g u r i n g a n d M o n i t o r i n g a n A c t i v e D i r e c t o r y S e r v e r Figure 1.1: Viewing the list of unmanaged Active Directory servers Figure 1.2: Managing an Active Directory server 2

8 C o n f i g u r i n g a n d M o n i t o r i n g a n A c t i v e D i r e c t o r y S e r v e r 2. Try to signout of the eg administrative interface. Figure 1.3 will appear prompting you to configure a list of tests. Figure 1.3:List of unconfigured tests for an Active Directory server 3. The Active Directory Server test monitors the availability and response time from clients of an Active Directory server. To configure this test, click on the test name in Figure 1.3. Figure 1.4 then appears. 4. Specify the following in Figure 1.4: Figure 1.4: Configuring the ADServer test TEST PERIOD - How often should the test be executed HOST - The IP address of the machine where the Active Directory is installed. PORT The port number through which the Active Directory communicates. The default port number is 389. DOMAIN - The default value of the DOMAIN parameter will be none. In Windows 2003 environments however, the ADServerTest will function effectively only if a "fully qualified domain name" is provided in the DOMAIN text box. USER - Provide the name of a domain user in the USER text box. This can be none for Windows 2000 environments. PASSWORD - Provide the password for the domain user specified above, in the PASSWORD text box. This can be none for Windows 2000 environments. CONFIRM PASSWORD Confirm the PASSWORD by retyping it here. CONNECTTIMEOUT - By default, this is set to 30 seconds. This implies that by default, the test will wait for 30 seconds to establish a connecton with the target Active Directory server. If a connection is established within the default 30 second period, then the test will report that the server is available; if the test is unable to connect to the server within the default period, then it will report that the server is unavailable. If it generally takes a longer time for clients to connect to the AD server in your environment, then, you may want to change the CONNECTTIMEOUT period so that, the test does not time out before the connection is established, and consequently present an "untrue" picture of the availability of the server. 3

9 C o n f i g u r i n g a n d M o n i t o r i n g a n A c t i v e D i r e c t o r y S e r v e r ISPASSIVE If the value chosen is Yes, then the Oracle server under consideration is a passive server in an Oracle cluster. No alerts will be generated if the server is not running. Measures will be reported as Not applicable by the agent if the server is not up. 5. Click the Update button in Figure 1.4, and try to signout of the eg administrative interface. A list of unconfigured tests will appear as shown in Figure 1.5. Figure 1.5: List of tests that are yet to be configured for the Active Directory server 6. Click on the Active Directory Checks test in Figure 1.5 to configure it. 7. Specify the following in Figure 1.6. Figure 1.6: Configuring the Active Directory Checks test TEST PERIOD - How often should the test be executed HOST - The IP address of the machine where the Active Directory is installed. PORT The port number through which the Active Directory communicates. The default port number is 389. DOMAINNAME, USERNAME, PASSWORD, and CONFIRM PASSWORD: In order to execute the DCDIAG command, the eg agent has to be configured with a domain administrator's privileges. Therefore, specify the domain name and login credentials of the domain administrator in the DOMAINNAME, USERNAME and PASSWORD text boxes. Confirm the PASSWORD you provide by retyping it in the CONFIRM PASSWORD text box. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eg Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eg agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: o o The eg manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0. 4

10 C o n f i g u r i n g a n d M o n i t o r i n g a n A c t i v e D i r e c t o r y S e r v e r 8. Now, when you click on the Update button in Figure 1.6 and signout of the eg administrative interface, you will once again be prompted to configure the Global Catalog Search test. Figure 1.7: Configuring the Global Catalog Search test 9. Specify the following in Figure 1.7 to configure the Global Catalog Search test. TEST PERIOD - How often should the test be executed HOST - The IP address of the machine where the Active Directory is installed. PORT The port number through which the Active Directory communicates. The default port number is 389. USERNAME - Specify the name of the user who has to be searched in the global catalog. USERDNSDOMAIN - Specify the name of the DNS to which the specified user who has to be searched in the global catalog belongs. 10. Click on the Update button in Figure 1.7 and signout of the eg administrative interface. 1.2 Monitoring the Active Directory Server 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 to view the layer model, tests and measurements of the Active Directory Server. 5

11 C o n f i g u r i n g a n d M o n i t o r i n g E x t e r n a l A c t i v e D i r e c t o r y ( A D ) S e r v e r s Configuring and Monitoring External Active Directory (AD) Servers The Active Directory server model, discussed previously, performs in-depth internal monitoring of the health of an Active Directory server. However, sometimes, administrators might just want to receive an "external" perspective to the health of an Active Directory server - i.e., he/she might simply want to know whether an Active Directory server is available over the network, and if so, how quickly it responds to user requests. Such administrators can use the External AD model instead. This section explains how to configure and monitor the External AD server. 2.1 Administering the eg Manager to Work with an External AD Server To administer eg so that it monitors the External AD server, do the following: 1. Login as an administrator to the eg administrative interface 2. Next, add the external AD server manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify) (see Figure 2.1). Components manually added will be automatically managed by the eg Enterprise system (see Figure 2.1). Figure 2.1: Adding an External AD server 3. Next, try to sign out of the administrative interface. 4. Upon doing so, you will be prompted to configure the Active Directory Server test for the External 6

12 C o n f i g u r i n g a n d M o n i t o r i n g E x t e r n a l A c t i v e D i r e c t o r y ( A D ) S e r v e r s AD server (see Figure 2.2). Figure 2.2: The list of unconfigured tests for an External AD server 5. Click on the Active Directory Server test in Figure 2.1 and proceed to configure it using the same procedure discussed in Section 1.1 above. 6. Finally, sign out of the eg administrative interface. 2.2 Monitoring the External AD Server 1. Login as a monitor / supermonitor to the eg monitor user interface. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. Click on the External AD server to view its measurements, tests and layer model. 7

13 C o n f i g u r i n g a n d M o n i t o r i n g t h e A c t i v e D i r e c t o r y ( A D ) C l u s t e r S e r v i c e Configuring and Monitoring the Active Directory (AD) Cluster Service An active directory (AD) Cluster is a collection of physical AD servers that can act as a single logical server. Requests to a cluster are routed through a virtual cluster server that is assigned a cluster IP address and TCP port. Requests to this server can be handled by any of the individual nodes in the cluster at any given point in time, depending on which node is active at that time. Since clusters are deployed in environments where 24*7 availability and responsiveness are critical, it is imperative that the performance of the clusters is monitored all the time. 3.1 Administering the eg Manager to Work with an AD Cluster Service To monitor an Active Directory cluster, an eg external agent is deployed, which emulates a user login to the cluster to determine the availability of the cluster and the speed with which the cluster responds to the emulated request. The emulated requests are directed at the virtual cluster server. Therefore, you need to manage the virtual cluster server as an AD Cluster using the eg administrative interface. To do so, do the following: 1. Login as an administrator to the eg administrative interface 2. Next, add the virtual cluster server in your environment as the AD cluster service 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). 8

14 C o n f i g u r i n g a n d M o n i t o r i n g t h e A c t i v e D i r e c t o r y ( A D ) C l u s t e r S e r v i c e Figure 3.1: Adding an AD Cluster 3. Next, manage/manually add the individual Active Directory servers that form part of the cluster. Please refer to Configuring and Monitoring Database Servers for a more elaborate discussion on how to manage an Active Directory server. 4. Then, configure a new segment, where the AD cluster shares a USES relationship with all the individual AD servers in the cluster (see Figure 3.2). The cluster service is deemed healthy if the user requests are served by at least one of the servers in the cluster. Figure 3.2: A segment containing the cluster service and the AD servers 5. Ensure that an external agent monitors the AD Custer, and internal agents are deployed on the individual AD servers in the cluster to monitor their internal operations. 6. Finally, sign out of the administrative interface. 3.2 Monitoring the AD Cluster Service 1. Login as a monitor / supermonitor to the eg monitor user interface 2. Select the Segments option from the eg monitor menu, and click on the segment representing the cluster being monitored; then, click on the AD Cluster component in the segment to view its measurements, layer model and tests of the AD Cluster. 9

15 C o n f i g u r i n g a n d M o n i t o r i n g t h e A c t i v e D i r e c t o r y ( A D ) C l u s t e r S e r v i c e For an in-depth discussion on eg Enterprise's Cluster Monitoring capabilities and to understand the implications of cluster availability on service performance, refer to the Monitoring Clusters Using eg Enterprise chapter (Chapter 7) in the eg User Manual. 10

16 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s D o m a i n C o n t r o l l e r s Configuring and Monitoring Windows Domain Controllers In this chapter, we will discuss the procedures involved in configuring and monitoring a Windows Domain Controller. 4.1 Administering the eg Manager to work with a Windows Domain Controller To do the above, do the following: 1. Log into the eg administrative interface. 2. If a Windows Domain Controller is already discovered, then directly proceed towards managing it 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 controller 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 4.1 and Figure 4.2 clearly illustrate the process of managing a Windows Domain Controller. For more details on managing components, refer to Configuring and Managing Web Servers document. 11

17 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s D o m a i n C o n t r o l l e r s Figure 4.1: Selecting the Windows Domain Controller to manage Figure 4.2: Managing the Windows Domain Controller 5. Try to signout of the eg administrative interface. Figure 4.3 then appears prompting you to configure the Window Authentication test. 12

18 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s D o m a i n C o n t r o l l e r s Figure 4.3: List of unconfigured tests for an Domain Controller server 6. To configure this test, click on the test name in Figure 4.3. then appears. 7. Specify the following in Figure 4.4. Figure 4.4: Configuring the Window Authentication test TEST PERIOD - How often should the test be executed HOST - The IP address of the machine where the Active Directory is installed. PORT The port number through which the Active Directory communicates. The default port number is 389. DOMAIN - The default value of the DOMAIN parameter will be none. In Windows 2003 environments however, the WindowAuthenticationTest will function effectively only if a "fully qualified domain name" is provided in the DOMAIN text box. USER - Provide the name of a domain user in the USER text box. This can be none for Windows 2000 environments. PASSWORD - Provide the password for the domain user specified above, in the PASSWORD text box. This can be none for Windows 2000 environments. CONFIRM PASSWORD Confirm the PASSWORD by retyping it here. 8. Click the Update button in Figure 4.4, and finally, exit the administrative interface. 4.2 Monitoring the Windows Domain Controller To monitor the Windows Domain Controller, 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, click on the Windows Domain Controller for which you wish to view 13

19 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s D o m a i n C o n t r o l l e r s measurements. 14

20 C o n f i g u r i n g a n d M o n i t o r i n g t h e W i n d o w s I n t e r n e t N a m e S e r v i c e ( W I N S ) Configuring and Monitoring the Windows Internet Name Service (WINS) This chapter illustrates the process of configuring and monitoring the Windows Internet Name Service or WINS. 5.1 Administering the eg Manager to work with a WINS Server To do the above, do the following: 1. Log into the eg administrative interface. 2. If a WINS server is already discovered, then directly proceed towards managing it using the COMPONENTS - MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage). However, if it is yet to be discovered, then run discovery (Infrstructure -> Components -> Discover) to get it discovered or add the WINS 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 WINS server. For more details on managing components, refer to Configuring and Managing Web Servers document. 15

21 C o n f i g u r i n g a n d M o n i t o r i n g t h e W i n d o w s I n t e r n e t N a m e S e r v i c e ( W I N S ) Figure 5.1: Selecting the WINS server to manage Figure 5.2: Managing the WINS server 3. Next, sign out of the eg administrative interface. Then Figure 5.3 appears prompting you to configure the Windows Processes test. 16

22 C o n f i g u r i n g a n d M o n i t o r i n g t h e W i n d o w s I n t e r n e t N a m e S e r v i c e ( W I N S ) Figure 5.3: List of unconfigured tests for an WindowsProcesses test 4. To configure this test, click on the test name in Figure 5.3, then Figure 5.4 appears. 5. Specify the following in Figure 5.4. Figure 5.4: Configuring the Windows Processes test TEST PERIOD - How often should the test be executed HOST - The host for which the test is to be configured PORT - The port to which the specified HOST listens PROCESS - In the PROCESS text box, enter a comma separated list of names:pattern pairs which identify the process(es) associated with the server being considered. processname is a string that will be used for display purposes only. processpattern is an expression of the form - *expr* or expr or *expr or expr* or *expr1*expr2*... or expr1*expr2, etc. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. For example, to monitor the Word and Powerpoint applications on a system, in the PROCESS text box, enter officeprocess:*winword*,*power*, where * denotes zero or more characters. WIDE - This parameter is valid on Solaris and Windows systems only. On Solaris environments, if the value of the WIDE parameter is true, the eg agent will use usr/ucb/ps instead of /usr/bin/ps to search for processes executing on the host. /usr/ucb/ps provides a long output (> 80 characters), whereas /usr/bin/ps only outputs the first 80 characters of the process path and its arguments. However, some Solaris systems are configured with tightened security, which prevents the usr/ucb/ps command to be executed by any and every user to the system - in other words, only pre-designated users will be allowed to execute this command. The sudo (superuser do) utility (see can be used to allow designated users to execute this command. If your system uses sudo to restrict access to the /usr/ucb/ps command, then specify the value of the "wide" parameter to be "sudo". This will ensure that not only does the agent use the /usr/ucb/ps command to monitor processes (like it would do if the "wide" parameter were set to be true), but it would also use sudo to execute this command. 17

23 C o n f i g u r i n g a n d M o n i t o r i n g t h e W i n d o w s I n t e r n e t N a m e S e r v i c e ( W I N S ) On Windows environments, by default, the eg agent uses perfmon to search for the processes that match the configured patterns. Accordingly, the WIDE parameter is set to false by default. Typically, a process definition in Windows includes the full path to the process, the process name, and process arguments (if any). Perfmon however scans the system only for process names that match the configured patterns in other words, the process path and arguments are ignored by perfmon. This implies that if multiple processes on a Windows host have the same name as specified against PROCESSPATTERN, then perfmon will only be able to report the overall resource usage across all these processes; it will not provide any pointers to the exact process that is eroding the host s resources. To understand this better, consider the following example. Typically, Windows represents any Java application executing on it as java.exe. Say, two Java applications are executing on a Windows host, but from different locations. If java.exe has been configured for monitoring, then by default, perfmon will report the availability and average resource usage of both the Java applications executing on the host. If say, one Java application goes down, then perfmon will not be able to indicate accurately which of the two Java applications is currently inaccessible. Therefore, to enable administrators to easily differentiate between processes with the same name, and to accurately determine which process is unavailable or resource-hungry, the eg agent should be configured to perform its process searches based on the process path and/or process arguments, and not just on the process name in other words, the eg agent should be configured not to use perfmon. To achieve this, first, set the WIDE parameter to true. This will instruct the eg agent to not use perfmon to search for the configured process patterns. Once this is done, then, you can proceed to configure a PROCESSPATTERN that includes the process arguments and/or the process path, in addition to the process name. For instance, if both the Remote Access Connection Manager service and the Terminal Services service on a Windows host, which share the same name svchost - are to be monitored as two different processes, then your PROCESSPATTERN specification should be as follows: Terminal:C:\WINDOWS\System32\svchost -k DcomLaunch,Remote:C:\WINDOWS\system32\svchost.exe -k netsvcs You can also use wildcard characters, wherever required. For instance, in the above case, your PROCESSPATTERN can also be: Terminal:*svchost -k DcomLaunch,Remote:*svchost.exe -k netsvcs Similarly, to distinctly monitor two processes having the same name, but operating from different locations, your specification can be: JavaC:c:\javaapp\java.exe,JavaD:d:\app\java.exe Before including process paths and/or arguments in your PROCESSPATTERN configuration, make sure that the WIDE parameter is set to true. If not, the test will not work. If your PROCESSPATTERN configuration includes a process path that refers to the Program Files directory, then make sure that you do not a include a ~ (tilde) while specifying this directory name. For instance, your PROCESSPATTERN specification should not be say, Adobe:C:\Progra~1\Adobe\AcroRd32.exe. 18

24 C o n f i g u r i n g a n d M o n i t o r i n g t h e W i n d o w s I n t e r n e t N a m e S e r v i c e ( W I N S ) DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eg Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eg agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: o o The eg manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be Click the Update button in Figure 5.4, and finally, exit the administrative interface. 5.2 Monitoring the WINS Server To monitor the WINS 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, click on the WINS server for which you wish to view measurements. 19

25 C o n f i g u r i n g a n d M o n i t o r i n g T e r m i n a l S e r v e r Configuring and Monitoring Terminal Server This chapter explains the process of configuring and monitoring Terminal servers. 6.1 Administering the eg Manager to work with Terminal servers To do the above, do the following: 1. Log into the eg administrative interface. 2. If a Terminal server is already discovered, then directly proceed towards managing it 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 Terminal 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 6.1 and Figure 6.2 clearly illustrate the process of managing a WINS server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 20

26 C o n f i g u r i n g a n d M o n i t o r i n g T e r m i n a l S e r v e r Figure 6.1: Selecting the Terminal server to manage Figure 6.2: Managing the Terminal server 3. Next, try to sign out of the eg administrative interface. Doing so will result in the LIST OF UNCONFIGURED TESTS listing the unconfigured tests of the Terminal server (see Figure 6.3). 21

27 C o n f i g u r i n g a n d M o n i t o r i n g T e r m i n a l S e r v e r Figure 6.3: Unconfigured tests of the Terminal server 4. Now, click on the TerminalAuthentication test in Figure 6.3 to configure it. From the AGENT TESTS - SPECIFIC CONFIGURATION page that follows, configure the test as shown in Figure 6.4. Figure 6.4: Configuring the TerminalAuthentication test 5. The TerminalAuthentication test emulates a user logging into a Windows domain or local host and reports whether the login succeeded and how long it took. Now, specify the following in Figure 6.4: TEST PERIOD How often should the test be executed HOST The host for which the test is to be configured PORT Refers to the port used by the Terminal server USERNAME - This test emulates a user logging into a Microsoft Windows domain or a local host. Therefore, specify the login name of the user here. PASSWORD - Enter the password that corresponds to the specified USERNAME. CONFIRM PASSWORD Confirm the password by retyping it here. DOMAIN - Specify the name of the domain to which the test will try to login. If the test is to login to a local host, specify 'none' here. Multiple user names, passwords, and domains can be specified, separated by a comma. REPORT BY DOMAIN - By default, this flag is set to Yes. This implies that by default, this test will report metrics for every domainname\username configured for this test. This way, administrators will be able to quickly determine which user logged in from which domain. If you want the detailed diagnosis to display the username alone, then set this flag to No. 6. Finally, click the Update button. 7. Now, sign out of the administrative interface. 22

28 C o n f i g u r i n g a n d M o n i t o r i n g T e r m i n a l S e r v e r 6.2 Monitoring the Terminal Server To monitor the Terminal 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 MicrosoftTerminal server for which you wish to view measurements. 23

29 C o n f i g u r i n g a n d M o n i t o r i n g B i z T a l k S e r v e r Configuring and Monitoring BizTalk Server 2000 This chapter discusses the procedures involved in configuring and monitoring a BizTalk server. 7.1 Administering the eg Manager to work with a BizTalk Server To do the above, do the following: 1. Log into the eg administrative interface. 2. The BizTalk server cannot be discovered by the eg Enterprise system. Therefore, proceed to add it using the ADD/MODIFY - COMPONENTS page that appears when the menu sequence, Infrastructure -> Components -> Add/Modify is followed. Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 7.1 clearly illustrates the process of adding a BizTalk server2000 component. For more details on managing components, refer to Configuration and Monitoring Web Servers document. 24

30 C o n f i g u r i n g a n d M o n i t o r i n g B i z T a l k S e r v e r Next, sign out of the eg administrative interface. Figure 7.1:Adding a new BizTalk component 7.2 Monitoring the BizTalk Server To monitor the BizTalk 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, click on the BizTalk server for which you wish to view measurements. 25

31 C o n f i g u r i n g a n d M o n i t o r i n g B i z T a l k s e r v e r Configuring and Monitoring BizTalk server2010 In this chapter, we will discuss the procedures involved in configuring and monitoring a BizTalk server Administering the eg Manager to work with a BizTalk server2010 To do the above, do the following: 1. Log into the eg administrative interface. 2. The BizTalk server2010 cannot be discovered by the eg Enterprise system. Therefore, proceed to add it using the ADD/MODIFY - COMPONENTS page that appears when the menu sequence, Infrastructure -> Components -> Add/Modify is followed. Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 8.1 clearly illustrates the process of adding a BizTalk server2010 component. For more details on managing components, refer to Configuration and Monitoring Web Servers document. 26

32 C o n f i g u r i n g a n d M o n i t o r i n g B i z T a l k s e r v e r Figure 8.1:Adding a new BizTalk server2010 component 3. Next, sign out of the eg administrative interface. 8.2 Monitoring the BizTalk server2010 To monitor the BizTalk server2010, 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, click on the BizTalk server2010 for which you wish to view the measurements. 27

33 C o n f i g u r i n g a n d M o n i t o r i n g D H C P S e r v e r s Configuring and Monitoring DHCP Servers In this chapter, we will discuss the procedures involved in configuring and monitoring a DHCP server. 9.1 Administering the eg Manager to work with a DHCP Server To do the above, do the following: 1. Log into the eg administrative interface. 2. If a DHCP server is already discovered, then directly proceed towards managing it 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 DHCP 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 9.1 and Figure 9.2 clearly illustrate the process of managing a DHCP server. To know more about how to configure this component, refer to the eg Installation Guide. For more details on managing components, refer to Configuration and Monitoring Web Servers document. 28

34 C o n f i g u r i n g a n d M o n i t o r i n g D H C P S e r v e r s Figure 9.1: Viewing the list of unmanaged DHCP servers Figure 9.2: Managing a DHCP server 3. Next, sign out of the eg administrative interface. 9.2 Monitoring the DHCP Server To monitor the DHCP server, do the following: 29

35 C o n f i g u r i n g a n d M o n i t o r i n g D H C P S e r v e r s 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, click on the DHCP server for which you wish to view measurements. 30

36 C o n f i g u r i n g a n d M o n i t o r i n g M i c r o s o f t P r o x y S e r v e r s Configuring and Monitoring Microsoft Proxy Servers This chapter delineates the process of configuring and monitoring MS Proxy servers Administering the eg Manager to work with a Microsoft Proxy Server To do the above, do the following: 1. Log into the eg administrative interface. 2. If a MS Proxy server is already discovered, then directly proceed towards managing it 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 MS Proxy 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 10.1 and Figure 10.2 clearly illustrate the process of managing an Microsoft Proxy server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 31

37 C o n f i g u r i n g a n d M o n i t o r i n g M i c r o s o f t P r o x y S e r v e r s Figure 10.1: Viewing the list of unmanaged Microsoft Proxy servers Figure 10.2: Managing an Micosoft Proxy server 3. Next, sign out of the eg administrative interface. 32

38 C o n f i g u r i n g a n d M o n i t o r i n g M i c r o s o f t P r o x y S e r v e r s 10.2 Monitoring the Microsoft Proxy Server To monitor the Microsoft Proxy 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, click on the Microsoft Proxy server for which you wish to view measurements. 33

39 C o n f i g u r i n g a n d M o n i t o r i n g M S P r i n t S e r v e r s Configuring and Monitoring MS Print Servers This chapter explains the process of configuring and monitoring MS Print servers Administering the eg Manager to work with an MS Print Server To do the above, do the following: 1. Log into the eg administrative interface. 2. If an MS Print server is already discovered, then directly proceed towards managing it 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 MS Print 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 11.1 and Figure 11.2 clearly illustrate the process of managing an MS Print server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 34

40 C o n f i g u r i n g a n d M o n i t o r i n g M S P r i n t S e r v e r s Figure 11.1: Viewing the list of unmanaged MS Print servers Figure 11.2: Managing an MS Print server 3. Next, sign out of the eg administrative interface Monitoring the MS Print Server To monitor the Microsoft Print server, do the following: 1. Login as a monitor / supermonitor user. 35

41 C o n f i g u r i n g a n d M o n i t o r i n g M S P r i n t S e r v e r s 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. From the Components page, click on the Microsoft Print server for which you wish to view measurements. 36

42 C o n f i g u r i n g a n d M o n i t o r i n g M S F i l e S e r v e r s Configuring and Monitoring MS File Servers This chapter explains the procedures involved in configuring and monitoring an MS File server Administering the eg Manager to Monitor an MS File Server To do the above, do the following: 1. Log into the eg administrative interface. 2. If an MS File server is already discovered, then directly proceed towards managing it 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 MS File 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 12.1 and Figure 12.2 clearly illustrate the process of managing an MS File server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 37

43 C o n f i g u r i n g a n d M o n i t o r i n g M S F i l e S e r v e r s Figure 12.1: Viewing the list of unmanaged MS File servers 3. Next, sign out of the eg administrative interface. Figure 12.2: Managing an MS File server 12.2 Monitoring the MS File Server To monitor the Microsoft File 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, click on the Microsoft File server for which you wish to view 38

44 C o n f i g u r i n g a n d M o n i t o r i n g M S F i l e S e r v e r s measurements. 39

45 C o n f i g u r i n g a n d M o n i t o r i n g I S A P r o x y S e r v e r s Configuring and Monitoring ISA Proxy Servers This chapter discusses the procedures involved in configuring and monitoring ISA Proxy servers Administering the eg Manager to Work with the ISA Proxy Server To do the above, do the following: 1. Log into the eg administrative interface. 2. If an ISA Proxy server is already discovered, then directly proceed towards managing it 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 ISA Proxy 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 13.1 and Figure 13.2 clearly illustrate the process of managing an ISA Proxy server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 40

46 C o n f i g u r i n g a n d M o n i t o r i n g I S A P r o x y S e r v e r s Figure 13.1: Viewing the list of unmanaged ISA Proxy servers Figure 13.2: Managing an ISA Proxy serverlist of unconfigured test for the ISA Proxy server 3. Next, sign out of the eg administrative interface. then Figure 13.3 appears prompting you to configure the ISA Proxy server test. Figure 13.3:List of unconfigured test for the ISA Proxy server 4. To configure this test, click on the test name in Figure 13.3, then Figure 13.4 appears. 41

47 C o n f i g u r i n g a n d M o n i t o r i n g I S A P r o x y S e r v e r s 5. Specify the following in Figure Figure 13.4: Configuring of the Windows Processes test TEST PERIOD - How often should the test be executed HOST - The host for which the test is to be configured PORT - The port to which the specified HOST listens PROCESS - In the PROCESS text box, enter a comma separated list of names:pattern pairs which identify the process(es) associated with the server being considered. processname is a string that will be used for display purposes only. processpattern is an expression of the form - *expr* or expr or *expr or expr* or *expr1*expr2*... or expr1*expr2, etc. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. For example, to monitor the Word and Powerpoint applications on a system, in the PROCESS text box, enter officeprocess:*winword*,*power*, where * denotes zero or more characters. WIDE - This parameter is valid on Solaris and Windows systems only. On Solaris environments, if the value of the WIDE parameter is true, the eg agent will use usr/ucb/ps instead of /usr/bin/ps to search for processes executing on the host. /usr/ucb/ps provides a long output (> 80 characters), whereas /usr/bin/ps only outputs the first 80 characters of the process path and its arguments. However, some Solaris systems are configured with tightened security, which prevents the usr/ucb/ps command to be executed by any and every user to the system - in other words, only pre-designated users will be allowed to execute this command. The sudo (superuser do) utility (see can be used to allow designated users to execute this command. If your system uses sudo to restrict access to the /usr/ucb/ps command, then specify the value of the "wide" parameter to be "sudo". This will ensure that not only does the agent use the /usr/ucb/ps command to monitor processes (like it would do if the "wide" parameter were set to be true), but it would also use sudo to execute this command. On Windows environments, by default, the eg agent uses perfmon to search for the processes that match the configured patterns. Accordingly, the WIDE parameter is set to false by default. Typically, a process definition in Windows includes the full path to the process, the process name, and process arguments (if any). Perfmon however scans the system only for process names that match the configured patterns in other words, the process path and arguments are ignored by perfmon. This implies that if multiple processes on a Windows host have the same name as specified against PROCESSPATTERN, then perfmon will only be able to report the overall resource usage across all these processes; it will not provide any pointers to the exact process that is eroding the host s resources. To understand this better, consider the following example. Typically, Windows represents any Java application executing on it as 42

48 C o n f i g u r i n g a n d M o n i t o r i n g I S A P r o x y S e r v e r s java.exe. Say, two Java applications are executing on a Windows host, but from different locations. If java.exe has been configured for monitoring, then by default, perfmon will report the availability and average resource usage of both the Java applications executing on the host. If say, one Java application goes down, then perfmon will not be able to indicate accurately which of the two Java applications is currently inaccessible. Therefore, to enable administrators to easily differentiate between processes with the same name, and to accurately determine which process is unavailable or resource-hungry, the eg agent should be configured to perform its process searches based on the process path and/or process arguments, and not just on the process name in other words, the eg agent should be configured not to use perfmon. To achieve this, first, set the WIDE parameter to true. This will instruct the eg agent to not use perfmon to search for the configured process patterns. Once this is done, then, you can proceed to configure a PROCESSPATTERN that includes the process arguments and/or the process path, in addition to the process name. For instance, if both the Remote Access Connection Manager service and the Terminal Services service on a Windows host, which share the same name svchost - are to be monitored as two different processes, then your PROCESSPATTERN specification should be as follows: Terminal:C:\WINDOWS\System32\svchost -k DcomLaunch,Remote:C:\WINDOWS\system32\svchost.exe -k netsvcs You can also use wildcard characters, wherever required. For instance, in the above case, your PROCESSPATTERN can also be: Terminal:*svchost -k DcomLaunch,Remote:*svchost.exe -k netsvcs Similarly, to distinctly monitor two processes having the same name, but operating from different locations, your specification can be: JavaC:c:\javaapp\java.exe,JavaD:d:\app\java.exe Before including process paths and/or arguments in your PROCESSPATTERN configuration, make sure that the WIDE parameter is set to true. If not, the test will not work. If your PROCESSPATTERN configuration includes a process path that refers to the Program Files directory, then make sure that you do not a include a ~ (tilde) while specifying this directory name. For instance, your PROCESSPATTERN specification should not be say, Adobe:C:\Progra~1\Adobe\AcroRd32.exe. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eg Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eg agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: o o The eg manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis 43

49 C o n f i g u r i n g a n d M o n i t o r i n g I S A P r o x y S e r v e r s measures should not be Click on the Update button and signout of the eg administrative interface Monitoring the ISA Proxy Server To monitor the ISA Proxy 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, click on the ISA Proxy server for which you wish to view measurements. 44

50 C o n f i g u r i n g a n d M o n i t o r i n g M i c r o s o f t R a d i u s S e r v e r s Configuring and Monitoring Microsoft Radius Servers Internet Authentication Service (IAS) in Microsoft Windows Server is the Microsoft implementation of a Remote Authentication Dial-In User Service (RADIUS) server and proxy. As a RADIUS server, IAS performs centralized connection authentication, authorization, and accounting for many types of network access, including wireless, authenticating switch, dial-up and virtual private network (VPN) remote access, and router-to-router connections. As a RADIUS proxy, IAS forwards authentication and accounting messages to other RADIUS servers. This chapter deals with the procedure for configuring and monitoring the IAS server Administering the eg Manager to Work with the Microsoft Radius Server To do the above, do the following: 1. Log into the eg administrative interface. 2. The IAS server cannot be discovered by the eg Enterprise system. Therefore, proceed to add it using the ADD/MODIFY COMPONENTS page that appears when the menu sequence, Infratructure -> Components -> Add/Modify is followed. Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 14.1 clearly illustrates the process of adding an Microsoft Radius server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 45

51 C o n f i g u r i n g a n d M o n i t o r i n g M i c r o s o f t R a d i u s S e r v e r s 3. Next, sign out of the eg administrative interface. Figure 14.1: Adding a Microsoft Radius server 14.2 Monitoring the Microsoft Radius Server To monitor the Microsoft Radius 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, click on the Micosoft Radius server for which you wish to view measurements. 46

52 C o n f i g u r i n g a n d M o n i t o r i n g t h e M i c r o s o f t R e m o t e A u t h e n t i c a t i o n S e r v i c e ( R A S ) Configuring and Monitoring the Microsoft Remote Authentication Service (RAS) Microsoft Remote Access Service (RAS) is a feature in the Windows Server family, including Windows Server 2003, Windows 2000 Server, and, NT4 Server. A Limited version of RAS is also included in Windows XP Professional. RAS allows remote dial-up clients to connect to a Local Area Network using analog phone lines or ISDN lines. A typical use would be by an ISP (Internet Service Provider) to allow users to dial in to their LAN, or by a corporate network administrator to allow their users to connect to the corporate LAN from remote sites. The remote clients connect to RAS using the TCP/IP protocol encapsulated in the Point-to- Point (PPP) protocol, which allows the remote client to access the LAN as if they were plugged directly into it. This chapter deals with the procedure for configuring and monitoring the RAS server Administering the eg Manager to Work with the MS RAS Server To do the above, do the following: 1. Log into the eg administrative interface. 2. The RAS server cannot be discovered by the eg Enterprise system. Therefore, proceed to add it using the ADD/MODIFY - COMPONENTS page that appears when the menu sequence, Infrastructure -> Components -> Add/Modify is followed. Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 15.1 clearly illustrates the process of adding an RAS server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. 47

53 C o n f i g u r i n g a n d M o n i t o r i n g t h e M i c r o s o f t R e m o t e A u t h e n t i c a t i o n S e r v i c e ( R A S ) 3. Next, sign out of the eg administrative interface. Figure 15.1: Adding a Microsoft RAS server 15.2 Monitoring the Microsoft RAS Server To monitor the Microsoft RAS 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, click on the Microsoft RAS server for which you wish to view measurements. 48

54 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s C l u s t e r Configuring and Monitoring Windows Cluster This chapter deals with the steps involved in configuring and monitoring Windows clusters. Unlike other component-types, eg Enterprise does not offer a specialized monitoring model for monitoring Windows clusters. If a Windows-based application (eg., IIS Web, MS SQL database, Citrix Presentation server, etc.) that is being monitored functions within a Windows cluster, then eg Enterprise provides administrators the option to monitor the health of the cluster service as well by including an additonal Windows Cluster layer to the layer model of the Windows-based application. For instance, if you are monitoring an IIS web server that is operating on a Windows host that is part of a cluster, and you wish to know how well the cluster service is performing, then you can proceed to associate the Windows Cluster layer to the layer model of the IIS web server. The steps for achieving this are detailed below. 1. Follow the menu sequence, IntegrationConsole -> Components to open the INTEGRATIONCONSOLE- COMPONENT page. Now choose the Config Layer button corresponding to IIS Web server from the PRE- DEFINED SERVERS (see Figure 16.1 ). Figure 16.1: Selecting the config layer of the IIS Web server 2. Now select the Windows Cluster from the DISASSOCIATED LAYERS as depicted in the Figure

55 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s C l u s t e r Figure 16.2: Selecting the Windows Cluster from the Disassociated Layers 3. Next, click on Associate to associate the Windows Cluster to as the top layer of IIS web server s monitoring model. Now, click on Update to register the changes. (see Figure 16.3). Figure 16.3: Associating the Windows Cluster to the top layer of the IIS Webserver 4. If you now navigate to the AGENTS-TESTS SPECIFIC CONFIGURATION page (using the menu sequence Agents -> Tests -> Configure -> Specific), and view the tests available for an IIS web server, you will find that as a result of associating the Windows Cluster layer to the IIS Web server, a few clusterrelated tests are visible along with the web server-specific tests. (see Figure 16.4). 50

56 C o n f i g u r i n g a n d M o n i t o r i n g W i n d o w s C l u s t e r Figure 16.4: Viewing the Cluster related tests in the Agents-Tests Configuration page 5. Since the cluster tests are configured by default, just sign out of the eg administrative interface by clicking on the Signout button at the right, top corner of the interface Monitoring the Windows Cluster Server To monitor the Windows Cluster 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. Yow will see the Windows Cluster as the first layer of the IIS Web server in the Components page. From the Components page, click on the Windows Cluster server for which you wish to view tests and measurements. 51