AJA BRIDGE LIVE - SNMP Traps

BRIDGE LIVE Video I/O and Streaming Appliance v1.12 117 www.aja.com
Obtaining name of an object in a tree – outputs COMPRIMATO-
SYSTEMS-MIB:cmpto
snmptranslate .1.3.6.1.4.1.50087
Obtaining location of a certain object from MIB – outputs
.1.3.6.1.4.1.50087.1.1.3
snmptranslate –On COMPRIMATO-SYSTEMS-MIB:trcOutputStreamTable
SNMP Traps
BRIDGE LIVE uses standard SNMP traps. SNMP traps are used to send event
messages. An event has a start and an end which are conveyed by event
messages. Below is an example of events we use:
• user launched a pipeline
• user stopped a pipeline
• a pipeline crashed
• the device is receiving no input
• the device is producing no output
• some frames are being dropped by the transcoder
• invalid data on input
Each event has assigned a severity, which can be:
• info(0)
• warning(1)
• error(2)
• clear(3)
Events get cleared by a trap containing an event message with severity clear(3).
Event messages regarding the same event are linked together by the same
trcEventKey.
trcEvent structure:
• trcEventIndex
• trcEventKey
• trcEventObject
• trcEventObjectName
• trcEventSeverity
• trcEventText
• trcEventCreatedTime
The event message contains all necessary information about the event:
• eventObject – OID of the alarming object within the node having the alarm
• eventObjectName – human-friendly name of the alarming object
• severity – the severity of the event (CLEAR - add)
• text – an event text providing more information about the issue
• createTime – time when the event was raised/cleared
There are also two related tables – lastEventsTable and activeEventsTable.
lastEventsTable contains the 10 most recent event messages (one row for each
sent trap). activeEventsTable contains all raised events which have not been
cleared yet, alongside the four most recently cleared ones.
OIDs of relevant tables:
• lastEventsTable .1.3.6.1.4.1.50087.1.1.2.1