Liebert MONITORING OpenComms, Руководство пользователя

Страница: 22 / 56

Operation
16
[OIDALARMS]
1.3.6.1.2.1.33.1.6.3.1:upsAlarmBatteryBad{}
1.3.6.1.2.1.33.1.6.3.2:upsAlarmOnBattery{}
1.3.6.1.2.1.33.1.6.3.3:upsAlarmLowBattery{}
1.3.6.1.2.1.33.1.6.3.4:upsAlarmDepletedBattery{}
1.3.6.1.2.1.33.1.6.3.5:upsAlarmTempBad{}
1.3.6.1.2.1.33.1.6.3.6:upsAlarmInputBad{}
1.3.6.1.2.1.33.1.6.3.7:upsAlarmOutputBad{}
1.3.6.1.2.1.33.1.6.3.8:upsAlarmOutputOverload{}
1.3.6.1.2.1.33.1.6.3.9:upsAlarmOnByPass{}
1.3.6.1.2.1.33.1.6.3.10:upsAlarmBypassBad{}
1.3.6.1.2.1.33.1.6.3.11:upsAlarmOutputOffAsRequested{}
1.3.6.1.2.1.33.1.6.3.12:upsAlarmUpsOffAsRequested{}
1.3.6.1.2.1.33.1.6.3.13:upsAlarmChargerFailed{}
1.3.6.1.2.1.33.1.6.3.14:upsAlarmUpsOutputOff{}
1.3.6.1.2.1.33.1.6.3.15:upsAlarmUpsSystemOff{}
1.3.6.1.2.1.33.1.6.3.16:upsAlarmFanFailure{}
1.3.6.1.2.1.33.1.6.3.17:upsAlarmFuseFailure{}
1.3.6.1.2.1.33.1.6.3.18:upsAlarmGeneralFault{}
1.3.6.1.2.1.33.1.6.3.19:upsAlarmDiagnosticTestFailed{}
1.3.6.1.2.1.33.1.6.3.20:upsAlarmCommunicationsLost{}
1.3.6.1.2.1.33.1.6.3.21:upsAlarmAwaitingPower{}
1.3.6.1.2.1.33.1.6.3.22:upsAlarmShutdownPending{}
1.3.6.1.2.1.33.1.6.3.23:upsAlarmShutdownImminent{}
1.3.6.1.2.1.33.1.6.3.24:upsAlarmTestInProgress{}
To summarize, event traps generally are parsed by the NMS for any of
the information contained in the trap. A process should be put in place
by the NMS to recognize whether the event trap is a new condition or
a cleared condition by looking at the trap type. Likewise, the NMS
should be able to extract the second binding of the trap notification to
see the OID of the well-known alarm. This OID reference will allow
the NMS to extract the well-known name or description of the event.