ManageEngine® Applications Manager


Servers

<< Prev

Home

Next >>

Servers

 

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

 

The different type of servers that are supported by Applications Manager are:

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

  1. Click New Monitor. Choose Server.

  2. Enter the IP Address or hostname of the host.

  3. Enter the SubNetMask of the network.

  4. Enter the polling interval time in minutes.

  5. Provide the monitor specific authentication information: Choose the OS type (FreeBSD, AIX, AS400 / iSeries, Novell, Linux, HP UX, Sun OS, Windows 2000, 2003, 2008, 2012, XP, NT). Based on the type of OS, the 'Mode of Monitoring' information changes.

Windows 2000/2003/2008/2012/XP/NT/Vista:

  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 user name and password information.

  3. If WMI, provide user name 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.

This monitor type is not supported in the Cloud Starter Edition. Compare Editions.

 

Linux/Sun OS/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 user name and password information of the server.

  3. If SSH, provide the port number (default is 22) and user name and password information of the server. You have an option to give Public Key Authentication (User name and Private Key). You can also give a Passphrase if the private key is protected with one.

    Note: 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.

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

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 Monitor Group from the combo box to which you want to associate the Monitor (optional).

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

IBM AS400 / iSeries:

  1. 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 Monitor Group from the combo box with which you want to associate AS400/iSeries Monitor (optional).

  7. Click Add Monitor(s). This discovers 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 Monitor Group, you can do this manually anytime. For information on associating a Monitor with a Monitor Group, refer to Associating Monitor with Monitor Groups topic.

 

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.

 

It is important to note that if Applications Manager server is running in Windows machine, then it can monitor any type of host but if the server is running in Linux, then it can monitor Windows only if an SNMP agent is running in it. Also, any type of user can be used to log into Linux, whereas only Admin users can log into Windows.

 

Note: The important configuration details that are required while discovering host resource by Applications Manager are available in Appendix - Data Collection.

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.

Top

See Also

Monitor Information - Server | Create Other New Monitors

 

<< Prev

Home

Next >>

Script Monitors

Services