TAILF-ALARM-MIB: View SNMP OID List / Download MIB
VENDOR: TAIL-F SYSTEMS AB
Home | MIB: TAILF-ALARM-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
tfAlarmMIB | 1.3.6.1.4.1.24961.2.103 |
Alarm MIB for Tail-f Systems. This MIB represents alarms as states, where a row in the alarm table corresponds to a device, an object within the device and an unique alarm type. If the severity of an alarm or a the clear state is changed this is an update to an existing alarm entry and not a new. When the resource reports a clear on the alarm the alarm entry still exists until administrative processes purges the alarm list. These procedures are out of the scope for this module. |
||
tfAlarmObjects | 1.3.6.1.4.1.24961.2.103.1 | |||
tfAlarms | 1.3.6.1.4.1.24961.2.103.1.1 | |||
tfAlarmNumber | 1.3.6.1.4.1.24961.2.103.1.1.1 | unsigned32 | read-only |
This object shows the total number of of entries in the tfAlarmTable. |
tfAlarmLastChanged | 1.3.6.1.4.1.24961.2.103.1.1.2 | dateandtime | read-only |
A timestamp when the active alarm table was last changed. The value can be used by a manager to initiate an alarm resynchronization procedure. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long. |
tfAlarmTable | 1.3.6.1.4.1.24961.2.103.1.1.5 | no-access |
This table list all alarms in the system. Entries are created when a resource has a new alarm state. If the same resource has several active alarms, with different Alarm Types, this will be represented as separate rows. Rows disappear based on administrative procedures outside the scope of this module. Note that this means that cleared alarms exist in the table. Rows can be changed when an alarm changes severity, additional text or clearance state. |
|
1.3.6.1.4.1.24961.2.103.1.1.5.1 | no-access |
One entry in the table holds one alarm for a given resource. Entries are created by the system when a resource has a new alarm state. Entries are deleted by alarm pruning actions. An alarm that is cleared by a resource is still kept in the alarm list until pruned by a user. Alarm severity and additional text can later be changed in a row. |
||
tfAlarmIndex | 1.3.6.1.4.1.24961.2.103.1.1.5.1.1 | tfalarmindex | no-access |
A unique value, greater than zero, for each alarm. The value for each alarm must remain constant at least from one re-initialization of the entity to the next re-initialization. |
tfAlarmType | 1.3.6.1.4.1.24961.2.103.1.1.5.1.2 | snmpadminstring | read-only |
This provides an identification of the alarm type. Together with tfAlarmSpecificProblem, this is a unique identification of the alarm. Different managed object types and instances can share alarm types, but if the same managed object reports the same alarm type, it is to be considered as the same alarm state. The alarm type is a simplification of the different X.733 and 3GPP alarm IRP alarm correlation mechanisms based on EventType, ProbableCause, SpecificProblem and NotificationId. |
tfAlarmDevice | 1.3.6.1.4.1.24961.2.103.1.1.5.1.3 | snmpadminstring | read-only |
The name of the managed device. May also be the system itself for self-management alarms. Note that this object is not fine-grained enough to pinpoint the alarming resource. The alarm object within the device is the exact alarming resource. |
tfAlarmObject | 1.3.6.1.4.1.24961.2.103.1.1.5.1.4 | tfyangresource | read-only |
Name of alarm object within a device based on YANG naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator. |
tfAlarmObjectOID | 1.3.6.1.4.1.24961.2.103.1.1.5.1.5 | object identifier | read-only |
Name of alarm object based on SNMP naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator. |
tfAlarmObjectStr | 1.3.6.1.4.1.24961.2.103.1.1.5.1.6 | tfutf8string | read-only |
Name of alarm object based on any other naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator. |
tfAlarmSpecificProblem | 1.3.6.1.4.1.24961.2.103.1.1.5.1.7 | tfutf8string | read-only |
This object is used when the 'tfAlarmType' object cannot uniquely identify the alarm type. Normally, this is not the case, and this leaf is the empty string. |
tfAlarmEventType | 1.3.6.1.4.1.24961.2.103.1.1.5.1.8 | ianaitueventtype | read-only |
The event type as defined in X.733/X.736. |
tfAlarmProbableCause | 1.3.6.1.4.1.24961.2.103.1.1.5.1.9 | tfprobablecause | read-only |
The probable cause as defined in X.733/X.736. |
tfAlarmOrigTime | 1.3.6.1.4.1.24961.2.103.1.1.5.1.10 | dateandtime | read-only |
Time for alarm raise |
tfAlarmTime | 1.3.6.1.4.1.24961.2.103.1.1.5.1.11 | dateandtime | read-only |
A time stamp of the alarm state change event. Note that this variable represents the last change of the alarm state, like changed severity or additional text. If the alarm has not changed state this variable represents the alarm raise time and will be the same as tfAlarmOrigTime. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long. |
tfAlarmSeverity | 1.3.6.1.4.1.24961.2.103.1.1.5.1.12 | ituperceivedseverity | read-only |
The severity of the alarm as defined by X.733. Note that this may not be the original severity since the alarm may have changed severity. For cleared alarms, this is the last severity that is not equal to cleared. |
tfAlarmCleared | 1.3.6.1.4.1.24961.2.103.1.1.5.1.13 | truthvalue | read-only |
Indicates if the alarm is cleared or not. |
tfAlarmText | 1.3.6.1.4.1.24961.2.103.1.1.5.1.14 | tfutf8string | read-only |
A user friendly text describing the alarm. Intended for human consumption. |
tfAlarmOperatorState | 1.3.6.1.4.1.24961.2.103.1.1.5.1.15 | tfalarmoperatorstate | read-only |
The operator state of the alarm. |
tfAlarmOperatorNote | 1.3.6.1.4.1.24961.2.103.1.1.5.1.16 | tfutf8string | read-only |
Operator note for the alarm. |
tfAlarmNotifications | 1.3.6.1.4.1.24961.2.103.2 | |||
tfAlarmNotifsPrefix | 1.3.6.1.4.1.24961.2.103.2.0 | |||
tfAlarmIndeterminate | 1.3.6.1.4.1.24961.2.103.2.0.1 |
Indeterminate alarms are sent when errors occur for which the severity level cannot be determined. |
||
tfAlarmWarning | 1.3.6.1.4.1.24961.2.103.2.0.2 |
Warning alarms are sent for potential problems that haven't yet caused any significant effects. |
||
tfAlarmMinor | 1.3.6.1.4.1.24961.2.103.2.0.3 |
Minor alarms are sent for non-service affecting problems, and indicate that corrective action should be taken to prevent a more serious fault. |
||
tfAlarmMajor | 1.3.6.1.4.1.24961.2.103.2.0.4 |
Major alarms are sent for service affecting problems that require urgent corrective action. |
||
tfAlarmCritical | 1.3.6.1.4.1.24961.2.103.2.0.5 |
Critical alarms are sent for service affecting problems that require immediate corrective action. |
||
tfAlarmClear | 1.3.6.1.4.1.24961.2.103.2.0.6 |
A clear alarm indicates that a previously reported alarm is now cleared by the underlying resource. |
||
tfAlarmConformance | 1.3.6.1.4.1.24961.2.103.10 | |||
tfAlarmCompliances | 1.3.6.1.4.1.24961.2.103.10.1 | |||
tfAlarmCompliance | 1.3.6.1.4.1.24961.2.103.10.1.1 |
Compliance information for this MIB module |
||
tfAlarmGroups | 1.3.6.1.4.1.24961.2.103.10.2 | |||
tfAlarmNotifs | 1.3.6.1.4.1.24961.2.103.10.2.1 |
The alarm notifications that can be sent from the system. |
||
tfAlarmObjs | 1.3.6.1.4.1.24961.2.103.10.2.2 |
The alarm objects. |