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-71-1913724.1
Update Date:2018-04-03
Keywords:

Solution Type  Technical Instruction Sure

Solution  1913724.1 :   Eagle: Loadsharing of SCCP Class1 Messages is not Correct from Eagle STP  


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




In this Document
Goal
Solution


Created from <SR 3-9299303171>

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 45.0 and later
Tekelec

Goal

The Eagle is not loadsharing SCCP Class1 messages towards ABC1 and ABC2 nodes.
Eagle is sending messages to only ABC1 node.
 

Solution

Loadsharing of SCCP Class1 messages can only be achieved by enabling Transaction based GTT Loadsharing Feature (Partnum: 893017101) found in Oracle Communications Documentation for Tekelec Products
This feature was not enabled in Customers Eagle STP..

Confirmed that loadsharing of SCCP Class1 messages towards ABC1 and ABC2 was happening correctly after this feature was enabled and configured correctly.

Transaction-Based GTT Load Sharing
Transaction-Based GTT Load Sharing allows messages with the same transaction parameters (TCAP, SCCP, MTP, or ENHMTP parameters) to be routed to the same destination within an entity set. An entity set is a group of entities that are used to determine the proper destination of a post-GTT message. This group of entities can be one of the following:

• A mated application (MAP) group
• A mated relay node (MRN) group
• A mated application set (MAPSET), if the Flexible GTTLoad Sharing feature is enabled
• A mated relay node set (MRNSET), if the Flexible GTTLoad Sharing feature is enabled.

This feature applies to the following types of SCCP messages:

• UDT/UDTS class 0 messages
• UDT/UDTS class 1 messages
• XUDT/XUDTS class 0 messages
• XUDT/XUDTS class 1 messages.

UDT/UDTS and XUDT/XUDTS messages are loadshared using a key derived from these elements in the message.

• MTP parameters - the first 3 bytes of the incoming OPC and 1 byte of the SLS.
• SCCP parameters - the last 4 bytes of the global title address field of the called party address.
• TCAP parameter - the TCAP Transaction ID in the messages.
• Enhanced MTP parameter - a combination of the SLS and the incoming OPC values.

The parameters used for Transaction-Based GTT Load Sharing are selected using the chg-sccpopts command. These parameters are:

• :tgtt0 – enable or disable Transaction-Based GTTLoad Sharing for SCCP Class 0 UDT, UDTS, XUDT, or XUDTS messages.
• :tgtt1 – enable or disable Transaction-Based GTTLoad Sharing for SCCP Class 1 UDT, UDTS, XUDT, or XUDTS messages.
• :tgttudtkey – the Transaction Parameter for the incoming UDT or UDTS messages.
• :tgttxudtkey – the Transaction Parameter for the incoming XUDT or XUDTS messages.
 


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