3Com TP-1610, Usermanualmanual

Page: 440 / 496

440
V6100 and V7122 User Guide
<text> value: %i - <Link number>
%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” }
Additional Info1 varbind CONGESTED
Condition: Link becomes un-congested (local AND remote).
Alarm status: Cleared
Corrective Action: Reduce SS7 traffic on that link.
This alarm is raised for any change in the remote or local congestion status.
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 104 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
Keep-alive is sent every 9/10 of the time defined in the parameter
NatBindingDefaultTimeout.