Systemwalker Service Quality Coordinator User's Guide

3.1.2 Settings for Monitored Servers

The following explains the settings required so that performance information can be collected from the monitored server.

If the server to be monitored is a Windows server

1. Create a user so that connections can be made remotely.

   Do not specify "User must change password at next logon" for the user.

2. Add a user to the groups necessary for connecting remotely and collecting information ("TelnetClients" group and "Performance Monitor Users" group).

   Follow these steps to make the settings.

   1. Create a "TelnetClients" local group.

      1. Open Computer Management.

      2. In the console tree, expand Local Users and Groups and click Groups.

      3. If the "TelnetClients" group already exists in the list, skip the next step and go on to "b. Add user to the "TelnetClients" group".

      4. Right-click on Groups, and click New Group.

      5. In the New Group dialog, enter "TelnetClients". Add descriptions as required.

      6. If the user has already been created, click Add and enter the user name in the Select Users, Computers, or Groups dialog.

      7. Click Create.

   2. Add user to the "TelnetClients" group.

      1. Open Computer Management.

      2. In the console tree, expand Local Users and Groups and click Groups.

      3. Double-click the "TelnetClients" local group.

      4. Click Add.

      5. Follow the instructions in the Select Users, Computers, or Groups dialog to add the user to the "TelnetClients" group and click OK.

   3. Add user to the "Performance Monitor Users" group.

      1. Open Computer Management.

      2. In the console tree, expand Local Users and Groups and click Groups.

      3. Double-click the "Performance Monitor Users" group.

      4. Click Add.

      5. Follow the instructions in the Select Users, Computers, or Groups dialog to add the user to the "Performance Monitor Users" group and click OK.

   Note

   • From a security point of view, it is not recommended to use a user belonging to the Administrators group.

   • To open Computer Management, from the Windows Start menu, click Control Panel and double-click Administrative Tools >> Computer Management.

   • When entering the group name, be sure to spell "TelnetClients" as shown.

   • Users cannot login after creating a "TelnetClients" group until the "Telnet Server" service is stopped and then started again.

3. Make settings to have the "Telnet" service start automatically.

   Windows Server® 2003

   Make settings to have the "Telnet" service start automatically.

   Note

   The "Telnet" service is set to not start automatically by default.

   1. Open Computer Management.

   2. In the console tree, click Services.

   3. Double-click the "Telnet" service.

   4. Make the startup type Automatic, change the service status to Start, and click OK.

   Windows Server® 2008

   Enable the "Telnet Server" function and set the "Telnet" service to start automatically.

   Note

   The "Telnet Server" function is disabled by default.

   The "Telnet" service is also set to not start automatically by default.

   The following describes how to enable the "Telnet Server" function and set the "Telnet" service to start automatically.

   1. Start the Windows Server Manager.

   2. Select Features in the tree on the left and click Add Features in the window on the right.

   3. Select Telnet Server and click Next.

   4. Click the Install button.

      
      

   When installation is finished, start Windows Services, and follow the steps below to have the Telnet service start automatically.

   1. Open Computer Management.

   2. In the console tree, click Services.

   3. Double-click the "Telnet" service.

   4. Make the startup type Automatic, change the service status to Start, and click OK.

      
      

4. Change the maximum number of sessions that can be connected simultaneously with the "Telnet" service.

   The default maximum number of sessions that can be connected simultaneously with the "Telnet" service is "2".
   Set the maximum number of sessions with consideration for the number of sessions required shown in "Number of connection sessions".

   Use the Windows "tlntadmn" command to change the maximum number of sessions that can be connected simultaneously.

   tlntadmn config maxconn=<maximum number of connection sessions>

   Note

   When running the command under Windows Server® 2008, run as the administrator. To do so, from the Start menu, select All Programs, Accessories, then right-click Command Prompt and select Run as administrator. Now run the commands described below in the command prompt that appears.

   tlntadmn config maxconn=<maximum number of connection sessions>

5. Logon to the computer with the new user.

   Note

   The user profile of the connecting user is necessary for connecting remotely and collecting information. For this reason, logon to the Windows computer as the connecting user.

6. Connect to the set server with telnet and confirm that you can log in with the created user.

   
   

If the server to be monitored is a UNIX server

When communicating by telnet

1. Create a user so that connections can be made remotely. Set a user home directory at this time.

   For instance, when using the useradd or usermod command, set the home directory of the user with the -d option, for example. If a home directory does not exist, create one. Set a directory with user write access privileges for the home directory.

   Note

   A user registered in the adm group is required to run the sar command if the monitored server is an AIX server.
   If the user for connecting remotely is not a root user, register the user in the adm group.

2. Make settings to have the telnet daemon start automatically.

   Refer to the telnet manual for information about how to start and set the daemon.

3. Connect to the set server with telnet and confirm that you can log in with the created user. Also confirm that the current directory when you login is the home directory created for the user.

   
   

When communicating by ssh

1. Create a user so that connections can be made remotely. Set a user home directory at this time.

   For instance, when using the useradd or usermod command, set the home directory of the user with the -d option, for example. If a home directory does not exist, create one. Set a directory with user write access privileges for the home directory.

   Note

   A user registered in the adm group is required to run the sar command if the monitored server is an AIX server.
   If the user for connecting remotely is not a root user, register the user in the adm group.

2. Make settings to have the ssh daemon start automatically.

   Install SSH (or OpenSSH) if it has not been installed yet.
   Refer to the ssh manual for information about how to install and start the daemon.

3. Connect to the set server with ssh and confirm that you can log in with the created user. Also confirm that the current directory when you login is the home directory created for the user.