Use this Knowledge Script to check the availability of any computers or other devices that reply to ICMP Echo requests. (The ICMP Echo request is commonly used by the ping command on UNIX and Windows computers.) With this Knowledge Script, you can check the up/down status of your managed UNIX computers, Windows computers, and other equipment, such as TCP/IP-based printers.
You can specify computers to ping in two ways: by providing comma-separated lists or by naming files containing comma-separated lists. If a computer does not respond to a ping within the response time threshold, the script raises an event.
There are separate lists for UNIX and Windows computers. This separation allows the script to push raised events to computers listed in your TreeView: to do this, the script needs to know whether an event is destined for a UNIX or Windows computer. When an event is pushed to a computer listed in your TreeView, its icon blinks.
This script can raise an event for a computer that is not listed in your TreeView. When this happens, a server group named AppManager Proxy Events is automatically created in the Master TreeView. From this group, you can view, acknowledge, close, and delete all events on the computer. To discover resources and run monitoring jobs on the computer, you must delete the computer from the AppManager Proxy Events server group, then manually add the computer to the TreeView. If necessary, stop any proxy jobs that are monitoring the remote computer so you can add it to the TreeView.
UNIX computer icon
The default interval for this script is Every two hours.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
List of UNIX machines to check (by hostname or IP address) |
Enter a list of UNIX computer names, separated by commas, that you want to test communication with. The default is localhost. |
|
List of Windows machines to check (by hostname or IP address) |
Enter a list of Windows computer names, separated by commas, that you want to test communication with. The default is blank. |
|
Optional file listing UNIX hosts to ping |
Type the full path to the file containing a list of the UNIX computers you want to check. The file should contain the hostname or IP address for each computer in one or more lines. Each line can have multiple computer names, separated by commas. For example, the contents of a file could be: NYC01,NYC02 SALES01,10.15.221.5, SFO01 LABMACH, QATEST The default is blank. |
|
Optional file listing Windows hosts to ping |
Type the full path to the file containing a list of the Windows computers you want to check. The file should contain the hostname or IP address for each computer in one or more lines. Each line can have multiple computer names, separated by commas. For example, the contents of a file could be: NYC01,NYC02 SALES01,10.15.221.5, SFO01 LABMACH, QATEST The default is blank. |
|
Collect data for response time? (y/n) |
Set to y to collect data for charts and reports. If set to y, the script returns the time it took the server to respond to the ping command. The default is n. |
|
Collect data for machine up/down? (y/n) |
Set to y to collect data for charts and reports. If set to y, the script returns:
The default is n. |
|
Event if response time exceeds the threshold? (y/n) |
Set to y to raise an event if the response time from the computer whose connection you are testing exceeds the threshold you set. The default is y. |
|
Event if the machine is not responding? (y/n) |
Set to y to raise an event if the computer whose connection you are testing fails to respond to the Ping test. The default is y. |
|
Maximum response time (ms) threshold |
Enter a threshold for the maximum response time in milliseconds for the reply to take. The default is 500 milliseconds. |
|
Event severity level when response time is exceeded |
Set the event severity level, from 1 to 40, to indicate the importance of the event reported when the response time threshold is crossed. The default severity is 15. |
|
Event severity level when machine is unreachable |
Set the event severity level, from 1 to 40, to indicate the importance of the event reported when AppManager cannot communicate with the computer. The default severity is 5. |
|
Number of times to ping target machine per iteration |
Enter the number of times that you want to ping the target computer for each iteration. The default is 1. |
|
Event severity for internal failure |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which this job experienced an internal error. The default is 5. |
|
Enable debugging? (y/n) |
Set to y to enable debugging. The default is n. |