Use this Knowledge Script to monitor the up and down status of Distributed File System (DFS) roots, links, and replicas. You can set this script to automatically attempt to restart roots, links, and replicas when they are not running. This script raises an event when auto-start fails, succeeds, or when roots, links, or replicas are down but the Auto-start service? parameter is set to n.
DFS Namespace Service object
DFS Replication Service object
The default interval for this script is Every 5 minutes.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Event? |
Set to y to raise an event if auto-start fails, succeeds, or is disabled. The default is y. |
|
Collect data? |
Set to y to collect data for charts and reports. If enabled, data collection returns:
These values are used to report the percentage of time the service is up in any given period. The default is n. |
|
Restart the service(s) if stopped? |
Set to y to automatically restart the DFS service when it is down. The default is y. |
|
Event severity when restart fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the service is down and AppManager cannot restart it. The default is 5 (red event indicator). |
|
Event severity when restart succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the service was down and AppManager successfully restarted it. The default is 25 (blue event indicator). |
|
Event severity when restart is set to n |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the service is down and the Auto-start service? parameter has been disabled. The default is 18 (yellow event indicator). |
|
Severity for an unexpected KS error |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the DFSServiceDown job fails unexpectedly. The default is 35 (magenta event indicator). |