User`s manual

Mediant 1000
H.323 User's Manual 418 Document #: LTRT-83401
F.1.5 Log Traps (Notifications)
This section details traps that are not alarms. These traps are sent with the severity varbind value of
‘indeterminate’. These traps don’t ‘clear’, they don’t appear in the alarm history or active tables. One
log trap that does send clear is acPerformanceMonitoringThresholdCrossing.
Table F-15: acKeepAlive Log Trap
Trap:
acKeepAlive
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.16
Default Severity:
Indeterminate
Event Type:
other (0)
Probable Cause:
other (0)
Trap Text:
Keep alive trap
Status Changes:
Condition:
The STUN client in is enabled and identified a NAT device or doesn’t locate the
STUN server.
The ini file contains the following line: ‘SendKeepAliveTrap=1’
Trap Status:
Trap is sent
Note:
Keep-alive is sent every 9/10 of the time defined in the parameter
NatBindingDefaultTimeout.
Table F-16: acPerformanceMonitoringThresholdCrossing Log Trap
Trap:
acPerformanceMonitoringThresholdCrossing
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.27
Default Severity:
Indeterminate
Event Type:
other (0)
Probable Cause:
other (0)
Trap Text:
"Performance: Threshold trap was set”, with source = name of performance
counter which caused the trap
Status Changes:
Condition:
A performance counter has crossed the high threshold
Trap Status:
Indeterminate
Condition:
A performance counter has crossed the low threshold
Trap status:
cleared