User`s manual

MediaPack
SIP User's Manual 380 Document #: LTRT-65408
F.1.4 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-11: 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-12: 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
Table F-13: acHTTPDownloadResult Log Trap
Trap:
acHTTPDownloadResult
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.28
Default Severity:
Indeterminate
Event Type:
processingErrorAlarm (3) for failures and other (0) for success.
Probable Cause:
other (0)
Status Changes:
Condition:
Successful HTTP download.
Trap text:
HTTP Download successful
Condition:
Failed download.
Trap text:
HTTP download failed, a network error occurred.
Note:
There are other possible textual messages describing NFS failures or success,
FTP failure or success.