Servers

Introduction

This section is common to all editions of IT360 - Professional Edition, Enterprise Edition (Probes only) and MSP Edition (Probes only).

Server level management is a concept, which involves a lot of manual intervention, human resources, and administrative tasks, to be performed. IT360 provides with a Server level monitoring functionality, to achieve such goals, and to ease the process of configuration management of hosts. 

The different type of server supported by IT360 are listed below. Their arrangement in Monitor List UI is as shown here.

  1. Windows 2000, 2003, XP, NT, Vista, 7, 2008

  2. Linux

  3. Sun Solaris

  4. IBM AIX

  5. HP Unix / Tru64 Unix

  6. FreeBSD

  7. Mac OS

  8. IBM AS400 / iSeries

  9. Novell

Procedure to Create Server Monitor

To create any of the above server monitors, follow the below steps:

  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click any of the monitors under Servers. Now, choose Servers from the Add Monitor of type dropdown.

  6. Enter a Display Name for the server.

  7. Enter the 'Host Name / IP Address'.

  8. Enter the SubNetMask of the network. (The subnet mask determines the maximum number of hosts on a subnetwork)

  9. Enter the Polling Interval time in minutes. (The time interval to monitor the different parameters configured for a Monitor)

  10. OS Type: Provide the monitor specific authentication information, i.e.choose the 'OS type' (FreeBSD, AIX, Linux, Novell, HP UX, AS400 / iSeries, Mac OS, Sun Solaris, Tru64 Unix, Windows 2000, 2003, XP, NT, Vista, 7, 2008). Based on the type of OS, the Mode of Monitoring information changes.

Types of OS

10. 1 Windows 2000, 2003, XP, NT, Vista, 7, 2008, 8, 2012:

    1. Follow the steps 1-9.

    2. Choose any of the above Windows OS Types.

    3. Select the Mode of Monitoring (SNMP or WMI).

    4. If you choose SNMP, do the following:
    1. Provide the Port number, at which it is running (default is 161)

    2. Choose between the SNMP Versions V1/V2 or V3. If you choose V1/V2, enter the SNMP Community String (default is 'public'). This requires no Username and Password information. If you choose V3, select the Security Level, enter a UserName and a Context Name. (Refer the below screenshot)

    1. If you choose WMI, do the following:

      1. Enable Event Log Monitoring, if required. (Kindly refer Windows Event Log Rules)

      2. Provide Username and Password information of the server.

10.2 Linux/ Sun Solaris/ IBM AIX/ HP Unix/ Tru64 Unix/ FreeBSD/ Mac OS/Novell:

    1. Follow the steps 1-9.

    2. Choose any of the above OS Types.

    3. Select the Mode of Monitoring (Telnet, SSH or SNMP). For IBM AIX, HP Unix, Tru64 Unix, only Telnet and SSH are supported. For Novell, only SNMP is supported.

    4. If you choose Telnet:

      1. Provide the Port number, at which it is running (default is 23)

      2. Provide Username and Password information of the server.

      3. Specify the Command Prompt value, which is the last character in your command prompt. Default value is $ and possible values are >, #, etc.
    1. If you choose SSH:

      1. Provide the Port number, at which it is running (default is 22)

      2. Provide Username and Password information of the server.

      3. Enable Public Key Authentication (supported for SSH2 only). Enter the Private Key value.

      4. Specify the Command Prompt value, which is the last character in your command prompt. Default value is $ and possible values are >, #, etc.

    Note:

    1. To identify the Public/Private key, go to command prompt, type cd .SSH/ then from the list, open the files <id_dsa.pub>/<id_rsa.pub> [Public] or <id_dsa>/<id_rsa>[Private] to get the keys If SNMP, provide the port at which it is running (default is 161) and SNMP Community String (default is 'public'). This requires no user name and password information.

    2. In the Server, which you are trying to monitor through SSH, the PasswordAuthentication variable should be set as 'yes' for the data collection, to happen. To ensure this, access the file '/etc/ssh/sshd_config' and verify the value of PasswordAuthentication variable. If it is set as 'no', modify it to 'yes', and restart the SSH Daemon, using the command '/etc/rc.d/sshd restart'.

    1. If you choose SNMP, do this.

10.3 IBM AS400 / iSeries:

    1. Follow the steps 1-9.

    2. Choose the OS Type as AS400/iSeries.

    3. Provide Username and Password information of the server.

  1. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the Servers Monitor, from the dropdown. If no Business Service is found, Create one by clicking the Create New Business Service link.

  2. Click Add Monitor(s). This discovers the Host or Server from the network and starts monitoring them.

If you have added Monitors and not associated them with a Business Service, you can do this manually anytime. For information on associating a Monitor with a Business Service, refer to Associating Monitors with Business Service topic. However, if you are configuring a MSP Probe, it is mandatory to associate the Monitor to the appropriate Customer / Site. There are situations, where the host gets automatically discovered with the Monitor running in the host. To disable the default option, disable it using Global Settings.

Top

    Mode of Monitoring - SSH/Telnet vs SNMP:

    We recommend Telnet or SSH mode of monitoring, because the following attributes are not available through SNMP;

    • Disk I/O Stats

    • Process Monitoring - CPU Utilization

    • Swap Memory Utilization

    System administrators generally prefer to check system resources, with commands, and will prefer to compare it with the SSH/telnet mode output, rather than running SNMP walk, to compare. Also, having the connection to the Linux boxes over SSH will make it easier for you to configure the same for script monitors or 'execute program' actions, if required.

See Also:

Monitor Information - Server | Create Other New Monitors



Copyright © 2014, ZOHO Corp. All Rights Reserved.