Grass Valley iControl V.6.02 - Manual (Page 434)

iControl and SNMP
Example
424
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION "The service or transport stream that generated the alarm"
::= { traps 2 }
statusTrap NOTIFICATION-TYPE
OBJECTS { trapDevice, trapAlarm }
STATUS current
DESCRIPTION
"User traps sent after certain conditions"
::= { traps 0 3 }
Example
In this example, a user has attached GSM trap actions to an SCP probe freeze detection alarm.
The traps have been configured as follows:
• if an alarm goes from normal (green) to error (red), trap number 100 is sent
• if an alarm goes from error (red) to normal (green), trap number 200 is sent
In order for these traps to be successfully parsed by a third party SNMP manager, the following
custom MIB entries should be added to its GSM-MIB:
clear TRAP-TYPE
ENTERPRISE miranda
VARIABLES { trapDevice, trapAlarm }
DESCRIPTION
"A clear trap means that the alarm condition that existed has now been
cleared."
::= 100
error TRAP-TYPE
ENTERPRISE miranda
VARIABLES { trapDevice, trapAlarm }
DESCRIPTION
"A error trap means that a error alarm condition is present"
::= 200
END
When the SCP probe freeze detection alarm goes from an error state to a normal state, a trap is
sent to the specified trap target. Here’s the output of a trap catcher application.