1226 - SCCP did not route - DPC congested

This message indicates that SCCP did not route a message because the destination point code (DPC) was congested. The message was discarded.

Note:

With Weighted GTT load sharing, the available PC in the Weighted group may also drop below the configured threshold. This condition can also create this alarm.

Example

montrealstp 13-12-04 00:25:16 EST  EAGLE 44.0.2-64.34.16 
6041.1226    CARD 2307     INFO    SCCP did not route - DPC congested
             TRANSLATED PC=   001-187-016    TRANSLATED SS=149
             CDPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=010  NP=--  NAI=---  ADDR=164758001620
                    PC=--------------    SSN=149
             CGPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=010  NP=--  NAI=---  ADDR=164758001020
                    PC=--------------    SSN=006
             LSN=hlrfetoro3  GTTSETIDX=(18)  
             Report Date:13-12-04  Time:00:24:32

Legend

ADDR

Address

CDPA

Called party address

CGPA

Calling party address

DPC

Destination point code

GTI

Global title indicator

MSG TYPE

Message type (for example, connection request, connection confirm, connection refused)

NAI

Nature of address indicator

NI

Network indicator value

NP

Numbering plan

OPC

Origination point code

PC

Point code

PCI

Protocol control information

RI

Routing indicator

SIO

Service information octet

SSN

Subsystem number

SSNI

Subsystem number indicator

TT

Translation type

TRANSLATED PC

Translated point code

TRANSLATED SS

Translated subsystem

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

Recovery

This indicates an SCCP message was discarded due to congestion at a distant node. Maintenance personnel should monitor the network and verify the nodes congestion status changes to zero (no congestion).

Note:

A transfer controlled (TFC) should have been received on the link to indicate congestion to this node. When the congestion status changes, the congestion status indicator in the flow control messages will indicate what message type priorities can be transmitted to the distant node. If the condition persists, follow normal company procedures in dealing with congestion at distant nodes.

Note:

Local outbound link congestion can also create this UIM when an SCCP entity set (MRNSET) is assigned to an intermediate GT translation and when no uncongested route to any of the entities in the entity set are available.