Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2319520.1
Update Date:2017-10-27
Keywords:

Solution Type  Problem Resolution Sure

Solution  2319520.1 :   Traffic Incorrectly Routed to the PC With the Higher RC of the MRNSET  


Related Items
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-15821677501>

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

This is due to the fact that the incoming messages are Class1 messages
The loadsharing is ignored in such a case and therefore the MRNSET is used in DOMINANT mode instead of LOADSHARED mode.

Check with the command "rtrv-sccpopts" the value of the parameter "Class1seq"
 

Solution

It is important to maintain the sequencing of the Class1 messages, so you must keep this parameter set to ON.
Now if you want to loadshare the Class1 messages, the only solution is to use the controlled feature named "Transaction Based GTT LS" (TBGTTLS).
Please contact your sales representative to discuss about this option and see how it could be applied according to your traffic.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback