Administering the eG Manager to monitor the Microsoft SQL Cluster Server
- Log into the eG administrative interface.
eG Enterprise cannot automatically discover Microsoft SQL Cluster Server. You need to manually add the server using the COMPONENTS page (see Figure 1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically.
Specify the Host IP/Name and the Nick name for the Microsoft SQL Cluster Server in Figure 1. The default port number appears in the Port number text box. The Microsoft SQL Cluster Server can only be monitored in an agentless manner. Therefore, the Agentless flag would be set to Yes, by default. Then, select Windows or Linux from the OS list box. If you select Windows as the OS, then select Perfmon as the Mode. If you select Linux as the OS, then select SSH as the Mode. Finally, click the Add button to register the changes.
The eG Enterprise also enables you to configure and monitor the Microsoft SQL Cluster Server that is installed as a 'named instance' in your environment. In such a case, you have to enter the host name or IP address of the SQL instance, which you specified while installing the SQL instance, against the Host IP/Name text box in Figure 1. The IP address and host name of the SQL instance can be viewed in the Failover Cluster Manager console as shown in Figure 2.
In addition, name of the SQL instance (see Figure 2) has to be specified against the Instance name parameter while configuring the tests for monitoring the Microsoft SQL Cluster Server.
When you attempt to sign out, a list of unconfigured tests will appear as shown in Figure 3.
- Click on the SQL Cluster Connection test to configure it. To know how to configure this test, refer to SQL Cluster Connection Test.
- Once all the tests are configured, signout of the eG administrative interface.