Question On The Loadsharing With The MAPset Table For Different SSN Values

Asset ID:	1-71-2201801.1
Update Date:	2016-11-15
Keywords:

Solution Type Technical Instruction Sure

Solution 2201801.1 : Question On The Loadsharing With The MAPset Table For Different SSN Values

Applies to:

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

Goal

question : When the MSU come to (PC s-2856, SSN=7) , will the MSU be loadshared to (PC s-2856, SSN=8) or to (PC s-2856, SSN=146) ?
What is the meaning of RC=10 for (s-2856, SSN=7), (s-2856, SSN=8) and (s-2856, SSN=146)?

MAPSET ID=8
PCN       Mate PCN   SSN RC MULT SRM MRC GRP NAME SSO
s-02856              7   10 COM NO *Y -------- OFF
          s-02856    8   10 COM NO *Y -------- OFF
          s-02856    146 10 COM NO *Y -------- OFF
          s-02857    129 20 COM NO *Y -------- OFF

Solution

After GTT translation, if the translated PC/SSN is (s-2856 / 7), then Eagle will check the Mapset table.
In your case, you configured a Mapset with the same PC but with different SSN values.
It means Eagle will perform a loadsharing between the 3 x SSN : 7, 8, 146.
Eagle will route the messages to the DPC s-02856 but will use the corresponding SSN value to build the outgoing MSU.

This is a very particular case where different subsystems will process MSU normally addressed to the SSN=7.

if the Class1Seq parameter is set to ON, then the Class1 messages won't be loadshared, they will always be routed to the primary node : s-2856 ssn 7.

Another example of a "classic" configuration for instance :

  MAPSET ID=10
  PCN      Mate PCN SSN RC MULT SRM MRC GRP NAME SSO
  s-01060            6   10 DOM NO NO -------- OFF
           s-01087   6   20 DOM NO NO -------- OFF

  MAPSET ID=11
  PCN        Mate PCN SSN RC MULT SRM MRC GRP NAME SSO
  s-01060             10 10 DOM NO NO -------- OFF
             s-01087 10 20 DOM NO NO -------- OFF

Attachments

This solution has no attachment