Use this Knowledge Script to monitor services on remote computers. You can specify the computers to monitor either directly using the Machine list parameter, or in a file containing a list of computer names or addresses.
This script tries to communicate with each of the remote computers in the Machine list parameter. This script raises an event if a named service is down or a specified computer cannot be reached from the computer where this script is running.
This script displays event information even if the remote computer is in maintenance mode.
NOTE:The AppManager agent does not need to be installed on the remote computer you want to monitor, nor does the remote computer need to exist in the Navigation pane or the TreeView pane.
When configuring an action for the RemoteServiceDown script, configure the Location to run on the MS (management server) or on a Proxy (a particular managed client computer).
If you instead configure an action to run on the managed client (MC), when a remotely monitored computer is placed into maintenance mode or scheduled maintenance mode, AppManager ignores any event conditions detected on the remote computer but does not disable the action.
Windows 2003 Server or later
The default schedule for this script is Every 5 minutes.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Raise event? |
Set to y to raise an event if a specified service is down or if a specified computer cannot be reached from the computer where this script is running. The default is y. |
|
Collect data? |
Set to y to collect data for charts and reports. If enabled, data collection returns data for each named service, either:
The default is n. |
|
Collect data only on down? |
Set to y to collect data for charts and reports only when named services are down. If enabled, data collection returns a value of 0 when a service is down. Enable this parameter only if the Collect data? parameter is enabled. The default is n. |
|
Machine list |
Specify the names of the computers to be monitored. Separate multiple names with commas (,) and no spaces. For example: AppSrvr,Storm,CorpSrvr. |
|
File name for machine list |
Provide the full path to the file containing the list of computers to test. 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 and no spaces. For example: NYC01,NYC02 SALES01,10.15.221.5,SFO01 LABMACH,QATEST The job supports a maximum file size of 32KB. If the file size exceeds 32KB, the job stops and raises an error event message: Out of string space. |
|
Services |
Provide the names of the services to be monitored. Separate multiple names with commas (,) and no spaces. The default is the NetIQ AppManager Agent service: NetIQmc. |
|
Auto-start service? |
Set to y to automatically restart down services. The default is y. |
|
Event severity level for service down; auto-start failed |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a service is down and auto-start failed. The default is 5 (red event indicator). |
|
Event severity level for service down; auto-start succeeded |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a service is down and auto-start succeeded. The default is 25 (blue event indicator). |
|
Event severity level for service down; don’t auto-start |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a service is down and you have selected not to restart it. The default is 18 (yellow event indicator). |
|
Event severity level for service not found |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a selected service cannot be found. The default is 8 (red event indicator). |