Chapter 4 Alarms
Alarm Name | Priority | Description | Cause/Recommended | |
Action | ||||
|
|
| ||
|
|
|
| |
FailADUCon | High | Connection to <uuid> | A connection to a remote | |
|
| closed; n dropped | server has failed. The UUID of | |
|
| watchers [reason] | the remote server is reported, | |
|
|
| as is the number of clients that | |
|
|
| were assigned to the server. | |
|
|
| The reason is often | |
|
|
| ADU.ServerFailed. | |
|
|
|
| |
LostADUEvents | High | n events lost due to | Event handling requests are | |
|
| network congestion or | timing out. n represents the | |
|
| error | approximate number of events | |
|
|
| that have been lost. | |
|
|
|
| |
NoMeInDS | Emergency | This ADU Server is not | The configuration of servers | |
|
| listed in the domain’s DS | and domains is incorrect. | |
|
| for this ADU Server. | Contact Technical Support (1- | |
|
|
| ||
|
|
|
| |
NoEventSink | High | A VESP_Request call | The server could not be | |
|
| failed to send a request | reached. History is being lost. | |
|
| to the server named by | If you are not using a server to | |
|
| the EventSink | archive terminated ADUs, set | |
|
| configuration parameter. | the database configuration | |
|
|
| parameter to 0 and restart the | |
|
|
| ADU Server. | |
|
|
| Check the vesp.imp and | |
|
|
| vespidl.pk installation files. If | |
|
|
| they do not list the server and | |
|
|
| interface, | |
|
|
| restart the ADU Server. | |
|
|
|
| |
Victims | High | Shutdown with n ADUs | This alarm should not be | |
|
| in existence; objects | generated. Contact Technical | |
|
| discarded | Support | |
|
|
|
| |
|
|
| (Sheet 2 of 2) | |
|
|
|
|