1359 - SCCP Looping Detected

When a SCCP Looping condition is found, the mode of operation of the loopset will be notify or discard (based on provisioning). The mode of operation either only notifies the user (via this UIM), or notifies the user (via this UIM) and discards the MSU. The data shown in the output will be from the original MSU, before any GTT modifications were applied to it.

A hop counter violation message is also sent by EAGLE to the UDTS. The message indicates either ANSI or ITU Networks based on the provisioned GTT Translation point code type.

Example

nbsa01 12-01-23 19:41:10 BRA  EAGLE5 41.1.1-62.67.1 
    0527.1359    CARD 3217    INFO    SCCP Looping Detected 
                SIO=83  OPC=  000-004-666      DPC=  000-006-500        
                SCCP MSG TYPE=09 
                CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=0 
                        TT=000  NP=01  NAI=004  ADDR=554197388383 
                        PC=--------------    SSN=008 
                CGPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=0 
                        TT=000  NP=01  NAI=004  ADDR=551181134001 
                        PC=--------------    SSN=008 
                LSN=ylrjo1  GTTSETIDX=(0)                                        
                Report Date:12-01-23  Time:19:41:00
 

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

Recovery

Analysis of measurements and messages is required to ensure messages are correctly being discarded.

Note:

Entering the wrong data in the SCCP Loop Table and/or incorrectly connecting a GTT translation with a particular SCCP Loop Table entry could result in unwanted traffic loss.

Refer to the Commands Manual for more information using ENT/CHG/DEL/RTRV-LOOPSET commands.

1. Remove invalid or unwanted entries from the SCCP Loop Tables.
2. Create a valid SCCP Loop Table entry for a GTT translation if the available tables are valid for other translations, but not the one in error.
3. Set the "notify only" mode until confidence is gained in the EAGLE SCCP Loop Tables, this is also the recommended setting for initial provisioning with a subsequent change.
4. Periodic auditing of UIMs to ensure that valid messages are not being discarded.