Log Traps (Notifications) - 3Com V7122 User Manual

<text> value: %i - <Link number>
Additional Info1 varbind
Condition:
Alarm status: Cleared
Corrective Action:

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.
acKeepAlive Log Trap
Table 111
Trap:
OID:
Default Severity
Event Type:
Probable Cause:
Trap Text:
Status Changes:
Condition:
Trap status:
468
%s – If link has MTP3 layer, then this string equals:
(SP %i linkset %i slc %i)
Where:
%i - <SP number>
%i - <Link-Set number>
%i - <SLC number>
Otherwise there is NO additional text.
%s - <congestion state>: { "UNCONGESTED", "CONGESTED" }
CONGESTED
Link becomes un-congested (local AND remote).
Reduce SS7 traffic on that link.
This alarm is raised for any change in the remote or local congestion status.
acKeepAlive
1.3.6.1.4.1.5003.9.10.1.21.2.0.16
Indeterminate
other (0)
other (0)
Keep alive trap
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 is sent
Keep-alive is sent every 9/10 of the time defined in the parameter
NatBindingDefaultTimeout.
V7122 GatewayUser Guide