1
Download Contents - Datatek Applications
Transcript
Monitoring the Network Table 5-1. Alarm Severities Alarm Severity Critical Definition the node is inoperative; likely causes are: Mark *C deleted during nightly cleanup only after a specified retention period has passed ** deleted during nightly cleanup only after a specified retention period has passed * deleted during nightly cleanup • loss of power to the node • failure of a critical module • more than one control computer is active Major a serious, service-degrading condition; likely causes are: • interface module failures, including a blown fuse • environmental extremes, like high temperature in the node cabinet Minor a secondary problem or transient condition that is not likely to affect overall node service, although many minor alarms may indicate a serious condition; likely causes are: Cleanup ‡ • parity errors • FIFO overflows Informational ‡ a system message (not a problem). These alarms are not forwarded to other entities; they are received and stored in the database with a status of cleared. deleted during nightly cleanup Most alarms can be cleared manually using the clear command (Link Down alarms are the exception), and some alarms are cleared automatically when the condition no longer exists. All cleared alarms are deleted during nightly cleanup. StarKeeper II NMS Core System Guide R10.0, Issue 1 5-3
