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 servers, supported by IT360 are;

Procedure to Create Server Monitor:

To create any of the above server monitors, [other then IBM AS400 / iSeries], follow the below steps:

  1. Go to 'Admin-> Servers & Applications', and click on 'New Monitor' link.

  2. Choose 'Server' from the 'Add Monitor of type' dropdown.

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

  4. Enter the SubNetMask of the network.

  5. Enter the Polling Interval time in minutes.

  6. 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.

Server Types:

Windows 2000, 2003, XP, NT, Vista, 7, 2008:

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

    2. If SNMP, provide the port, at which it is running (default is 161) and SNMP Community String (default is 'public'). This requires no Username and Password information.

    3. If WMI, provide Username and Password information of the server.

Note: You have the option to monitor Windows Event Logs. Kindly refer Windows Event Log Rules, under Admin Operations section.

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

    1. 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.

    2. If Telnet, provide the port number (default is 23), and Username and Password information of the server.

    3. If SSH, provide the port number (default is 22), and Username and Password information of the server. You also have an option to give Public Key Authentication (User name and Public Key).

      Note: To indentify the Public/Private key, go to command prompt from the Server, which you want to monitor, type 'cd.SSH/' then from the list, and open the files '<id_dsa.pub>/<id_rsa.pub> [Public]' or '<id_dsa>/<id_rsa>[Private]', to get the keys.

    4. If SNMP, provide the port, at which it is running (default is 161) and SNMP Community String (default is 'public'). This requires no Username and Password information. For Telnet/SSH mode of monitoring, specify the command prompt value, which is the last character in your command prompt. Default value is $ and possible values are >, #, etc.

Note: 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. Choose the grouping, to which you want to associate the Servers Monitor, from the combo box;

  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 Monitor 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

IBM AS400 / iSeries:

  1. Go to 'Admin-> Servers & Applications', and click on 'New Monitor' link.

  2. Select AS400/iSeries.

  3. Enter the Host Name / IP Address of AS400/iSeries server.

  4. Provide Subnet Mask and set Polling interval for the monitor.

  5. Enter Username and Password for authentication.

  6. Choose the grouping, to which you want to associate the Servers Monitor, from the combo box;

  7. Click Add Monitor(s). This discovers the AS400/iSeries from the network and starts monitoring them.

See also: Performance Metrics for AS400 / iSeries

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 Monitor 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.

Mode of Monitoring - SSH/Telnet vs SNMP:

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

Please check this link for more details.

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

Top


Copyright © 2013, ZOHO Corp. All Rights Reserved.