Grass Valley iControl V.4.43 - Manual (Page 526)

iControl and SNMP
Developer Tip
516
Numerical OID
.1.3.6.1.4.1.3872.11.1.1.6.12.9.100075 (status OID)
This would return the following variable binding:
status.12.9.100075:‐‐>normal(10000)
Developer Tip
When developing code to interface with the iControl GSM agent, developers often ask how to
determine a specific device index. A programming approach would be to poll the alarm status
table using
SNMP GET‐NEXT , starting at the beginning of the table, and then to compare the
returned varBind value (using contains ) with the Densité or Imaging frame name. Once an
entry in the table is found that matches the frame name, the device index can be determined
from the OID.
GSM SNMP Traps
SNMP traps are GSM actions attached to GSM alarms. In order to configure a trap
(see
"Configuring iControl to Send Traps" , on page 505), the following information must be
specified:
• the alarm transition(s) that will trigger the trap
• a trap target destination IP
• a trap SNMP version
• a trap number
The trap number, which is chosen arbitrarily from a predefined range, can be assigned to
alarms that appear in the GSM browser, as well as to alarm transitions (e.g. from normal to
error). The same trap number can be re-used for more than one alarm or alarm transition.
Once a trap number as been configured, a new user defined MIB entry is added for the
trap.This is the form for the custom MIB entry for a v1 trap type:
User_defined_event TRAP‐TYPE
ENTERPRISE miranda
VARIABLES { trapDevice, trapAlarm }
DESCRIPTION
"User defined description"
::= user_defined_trap_number
This is the form for the custom MIB entry for a v2c trap type:
User_defined_event NOTIFICATION‐TYPE
OBJECTS { trapDevice, trapAlarm }
STATUS current
Note: Values 1 to 99999 are reserved for user-defined virtual alarms and for third
party SNMP devices. Values of 100000 and up are iControl alarms.