0216 - REPT-LKF: remote congestion timeout

The remote node has been in congestion too long. The T6 timer has timed out.

Example

   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0216 ** SLK 1205,A nc00027  REPT-LKF:remote congestion timeout
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far end is not responding correctly.

1. Enter rept-stat-card:mode=full:loc=xxxx to determine if the signaling link is M2PA. If so, continue to 2. If not, skip to 3.
2. If this alarm is raised for IPSG M2PA signaling links, do the following:
   1. Enter the rept-stat-iptps and msucount –l commands to determine how much traffic is received and transmitted on the M2PA links.
   2. Enter the rtrv-ls command to determine the amount of rsvdslktps and maxslktps traffic that the M2PA signaling link can receive based on what is provisioned. (The rsvdslktps is the reserved-per-signaling-link TPS for IPSG linkset; this indicates the minimum guaranteed capacity for each link in the linkset. The maxslktps is the maximum-per-signaling-link TPS; this indicates the maximum traffic permitted when sufficient unused capacity is present on the host card.)
   3. Determine if the value exceeds the incoming traffic rate that the near end can accept. If the value is incorrect, enter the chg-ls command to increase or decrease the minimum and maximum TPS for the M2PA signaling link.

   Note:

   This step applies to only IPSG M2PA links and not to IPLIM M2PA links.
3. If the problem persists, follow local procedures to determine why the far end is not responding correctly.