Traffic Incorrectly Routed to the PC With the Higher RC of the MRNSET

(Doc ID 2319520.1)

Last updated on OCTOBER 27, 2017

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 3x.x and later
Information in this document applies to any platform.

Symptoms

In the STP configuration, there is one MRNSET for which the SCCP traffic is loadshared between DPCs 4-019-4, 4-019-5, 4-019-6 & 4-019-7 (RC=25).
Once those 4 DPCs become inaccessible, the traffic should be routed to backup DPC 4-020-1 (RC=50)

> rtrv-mrn:mrnset=5:pci=4-019-4

   eaglestp  17-09-27 07:34:20 GMT EAGLE5 45.0.1-64.70.35
    MRNSET PCI RC
    5 4-019-4 25
    4-019-5 25
    4-019-6 25
    4-019-7 25
    4-020-1 50


However, when one of the 4 x DPCs becomes inaccessible, for instance DPC 4-019-6, the incoming MSUs with GTA=923189244102 is routed to the backup DPC 4-020-1.
It was expected that Eagle will loadshare the MSUs to other DPC 4-019-4, 4-019-5 & 4-019-7.

 

> rtrv-gta:gttsn=e164intL0:gta=923189244102

  eaglestp 17-09-27 07:38:12 GMT EAGLE5 45.0.1-64.70.35
    GTTSN NETDOM SETTYPE NDGT
    e164intl0 itu CDGTA 3,4,5,6,7,8,9,10,11,12

    START GTA END GTA XLAT RI ITU PC
    923189244102 923189244102 dpc gt 4-019-6
    MRNSET=5 SSN=--- CCGT=no
    GTMODID=--------- TESTMODE=off
    OPTSN=--------- CGSELID=----- OPCSN=---------
    ACTSN=--------- PPMEASREQD= no


For which reason is the traffic routed to the DPC 4-020-1?

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms