0316 - Route is Prohibited

The route to the DPC cannot carry traffic to the DPC. Following are the possible causes:

• Local SLK failures

• Non-adjacent DPC SLK failures

Example

RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0316    DPC 144-201-001     Route is prohibited
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221

Legend

ALLOWED SS

Allowed subsystem

BLOCKED SS

Blocked subsystem

LSN

Linkset name. The name must be unique.

PROHIBITED SS

Prohibited subsystem

UNBLOCKED SS

Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

1. Enter the rept-stat-rte command using the DPC specified from the output message to determine which linkset has a problem.
   If it specifies a non-adjacent linkset, contact the far-end to test and correct the problem.
2. If it appears to be a local signaling link failure enter the rept-stat-ls using the linkset name specified from the output of 1 to determine which link(s) could have a problem.
3. Verify the link status using the rept-stat-slk command.
   For example, enter:
   rept-stat-slk:loc=:port=b
   Example of the output:

   RLGHNCXA03W 00-09-27 17:00:36 EST  EAGLE 35.0.0
   SLK     LSN          CLLI         PST           SST        AST
   1203,B  nsp1         ls02clli     OOS-MT        Unavail     ----
     ALARM STATUS       =  No alarm
     UNAVAIL REASON     =  FL NA LI RI 
   Command Completed.

4. Check the UNAVAIL REASON field in the output of the rept-stat-slk command.
   Following is an explanation of the UNAVAIL REASON codes:
   FL – The signaling link has a fault.
   NA – The signaling link is not aligned.
   LI – The signaling link has been inhibited locallyRI – The signaling link has been inhibited remotely.
   LB – The signaling link has been blocked locally.
   RB – The signaling link has been blocked remotely.
   FC – The signaling link is unavailable because of false congestion.
   RD(xx.xxx) - The signaling link is unavailable because of a restart delay to prevent signaling link oscillation. The number in parentheses indicates the amount of time, in seconds, remaining in the restart delay period. The link is restarted automatically after this amount of time has elapsed.
5. If the UNAVAIL REASON indicates an alignment problem or fault, activate a loopback using the act-lpb command, or use a physical loopback.
   (For a V.35, you must use an appropriate physical V.35 loopback.) If the signaling link aligns, contact the far-end to correct the problem.
6. If the UNAVAIL REASON still indicates an alignment problem or fault, check the status of the card by entering the rept-stat-card command for the specified card.
7. If the rept-stat-card command indicates a problem with the card, reset the card by entering the init-card command with the specified card location.
   If the card still does not align, try first reseating the card, then replacing the card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
8. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
9. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
10. If the signaling is blocked or inhibited remotely, contact the far-end to place the link in-service.