Go to primary content
Oracle® Communications EAGLE Database Administration - GTT User's Guide
Release 46.7
E97332-02
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Flexible Final GTT Load Sharing

Flexible Final GTT Load Sharing provides more routing diversity for GTT traffic requiring final global title translation (the routing indicator in the message is SSN) than the load sharing arrangements provided by the mated applications without the Flexible GTT Load Sharing feature enabled. For the EAGLE to perform Flexible Final GTT Load Sharing, the Flexible GTT Load Sharing feature must be enabled and turned on.

Final Load Sharing Feature Only

With the Flexible GTT Load Sharing feature not enabled, the EAGLE load shares post-GTT destination point codes and subsystems when final global title translation is being performed by using the mated application (MAP) table. The destination point codes and subsystems in the MAP table can appear in the MAP table only once. The MAP table contains groups of point codes with a maximum of 100 point codes and subsystems in each group. This arrangement allows only one set of relationships to be defined between a given point code and subsystem and any other point codes and subsystems in the MAP group. All global title addresses in the GTT table that translate to a point code and subsystem in the given MAP group will have the same set of load sharing rules applied.

For example, the following point codes, subsystems, and relative cost values are provisioned in the MAP table.

PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
005-005-005               251 10  SHR *Y  *Y  grp01    OFF
             006-001-001  254 10  SHR *Y  *Y  grp01    OFF
             006-001-002  254 10  SHR *Y  *Y  grp01    OFF
             006-001-003  254 10  SHR *Y  *Y  grp01    OFF
             006-001-004  254 10  SHR *Y  *Y  grp01    OFF
             006-001-005  254 10  SHR *Y  *Y  grp01    OFF
             006-001-006  254 10  SHR *Y  *Y  grp01    OFF
             006-001-007  254 10  SHR *Y  *Y  grp01    OFF

When the point code and subsystem in the final global title translation is translated to 005-005-005, subsystem 251, all traffic routed using the global title addresses in the final global title translations containing this point code and subsystem are load shared equally, no matter what the global title address is.

Addition of Flexible GTT Load Sharing Feature

When the Flexible GTT Load Sharing feature enabled and turned on, allowing Flexible Final GTT Load Sharing to be performed, the GTT load sharing arrangements are determined by:

  • The MAP set assigned to the final global title translation
  • The translated point code and subsystem
  • The global title address in the message assigned to the global title translation

When a global title address in a final global title translation is translated to a point code and subsystem, the MAP set assigned to the final global title translation containing the translated point code and subsystem determines how load sharing is applied to the traffic for this final global title translation.

A MAP set is a group of point codes and subsystems in the MAP table defining the GTT load sharing rules that are applied to a final global title translation. The method of load sharing is determined by the relative cost (RC) value assigned to each point code and subsystem in the MAP set. There are four types of load sharing that can be performed:
  • Solitary
  • Dominant
  • Load sharing
  • Combined dominant/load sharing

Solitary

A solitary MAP set contains only one point code and subsystem and no mate point codes and subsystems. Traffic can be routed only to this point code and subsystem.

The following shows sample output from the rtrv-map command for a solitary map set.
MAPSET ID=1      MRNSET ID=----  MRNPC=-----------
PCI            Mate PCI      SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
7-111-1                      255 10  SOL *N  *N  -------- OFF – --- ---

Dominant

All the point codes in a dominant MAP set have different relative cost values. The translated point code and subsystem in the message is the preferred point code and subsystem that the message is routed on. The relative cost value assigned to the preferred point code and subsystem does not have to be the lowest value in the MAP set. All traffic is routed to the preferred point code and subsystem if it is available. If the preferred point code and subsystem becomes unavailable, the traffic is routed the next alternate point code and subsystem that is available. When the preferred point code and subsystem becomes available again, the traffic is then routed back to the preferred point code and subsystem.

The following shows sample output from the rtrv-map command for a dominant map set.
MAPSET ID=30
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
254-007-221                  218 10  COM YES *Y  -------- OFF
               254-007-220   234 15  COM YES *Y  -------- OFF
               254-007-219   250 20  COM YES *Y  -------- OFF
               254-007-234    10 25  COM YES *Y  -------- OFF
               254-007-233    26 30  COM YES *Y  -------- OFF
               254-007-232    42 35  COM YES *Y  -------- OFF
               254-007-231    58 40  COM YES *Y  -------- OFF
               254-007-230    74 45  COM YES *Y  -------- OFF
In this example, the preferred point code and subsystem is 254-007-231, subsystem 58 (relative cost 40). If that point code and subsystem becomes unavailable, the traffic is routed down the list to the next available point code and subsystem (relative cost 45). If that point code and subsystem becomes unavailable, the traffic is routed to the top of the list to that primary point code and subsystem (relative cost 10), and so on.

Load shared

All the point codes and subsystems in a load shared MAP set have the same relative cost value. Traffic is shared equally between the point codes and subsystems in this type of MAP set.

The following shows sample output from the rtrv-map command for a load shared map set.
MAPSET ID=32
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
254-007-219                  250 10  SHR *Y  *Y  -------- OFF
               254-007-234    14 10  SHR *Y  *Y  -------- OFF
               254-007-233    26 10  SHR *Y  *Y  -------- OFF
               254-007-232    42 10  SHR *Y  *Y  -------- OFF
               254-007-231    58 10  SHR *Y  *Y  -------- OFF
               254-007-230    74 10  SHR *Y  *Y  -------- OFF
               254-007-229    90 10  SHR *Y  *Y  -------- OFF
               254-007-228   106 10  SHR *Y  *Y  -------- OFF
               254-007-227   122 10  SHR *Y  *Y  -------- OFF
               254-007-226   138 10  SHR *Y  *Y  -------- OFF
               254-007-225   154 10  SHR *Y  *Y  -------- OFF
               254-007-224   170 10  SHR *Y  *Y  -------- OFF
               254-007-223   186 10  SHR *Y  *Y  -------- OFF
               254-007-222   202 10  SHR *Y  *Y  -------- OFF
               254-007-221   218 10  SHR *Y  *Y  -------- OFF
               254-007-220   234 10  SHR *Y  *Y  -------- OFF

Combined dominant/load shared

A combined dominant/load shared MAP set is a combination of the dominant and load sharing MAP sets. At least two of the point codes and subsystems in this MAP set have the same relative cost values, and at least one other point code and subsystem has a different relative cost value. The traffic is shared equally between the point codes and subsystems with the same relative cost values. If these point codes and subsystems become unavailable, the traffic is routed to the next point codes and subsystems in the MAP set and shared equally between these point codes and subsystems.

The following shows sample output from the rtrv-map command for a combined dominant/load shared map set.
MAPSET ID=31
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
254-007-220                  234 10  COM YES *Y  -------- OFF
               254-007-219   250 10  COM YES *Y  -------- OFF
               254-007-234    10 10  COM YES *Y  -------- OFF
               254-007-233    26 10  COM YES *Y  -------- OFF
               254-007-228   106 10  COM YES *Y  -------- OFF
               254-007-227   122 10  COM YES *Y  -------- OFF
               254-007-226   138 10  COM YES *Y  -------- OFF
               254-007-225   154 10  COM YES *Y  -------- OFF
               254-007-232    42 20  COM YES *Y  -------- OFF
               254-007-231    58 20  COM YES *Y  -------- OFF
               254-007-230    74 20  COM YES *Y  -------- OFF
               254-007-229    90 20  COM YES *Y  -------- OFF
               254-007-224   170 20  COM YES *Y  -------- OFF
               254-007-223   186 20  COM YES *Y  -------- OFF
               254-007-222   202 20  COM YES *Y  -------- OFF
               254-007-221   218 30  COM YES *Y  -------- OFF
In this example, if the preferred point code is 254-007-231, subsystem 58 (relative cost 20), then the traffic is shared among the seven point codes/subsystems with a relative cost of 20. If those become unavailable, the traffic is sent to 254-007-221, subsystem 218, which has a relative cost of 30. Finally, if point code 254-007-221, subsystem 218 is unavailable, the traffic is shared among the point codes/subsystems with a relative cost of 10.

Point Code Assigned to Multiple MAP Sets

With the Flexible GTT Load Sharing feature enabled, the same point code and subsystem can be assigned to multiple MAP sets. The relative cost value of this point code and subsystem in each MAP set can be different.

In the following example, the point code 002-002-002, subsystem 254, is assigned to three MAP sets.
MAPSET ID=1
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
002-002-002                  254 10  COM YES *Y  -------- OFF
               254-007-219   250 20  COM YES *Y  -------- OFF
               254-007-234    10 25  COM YES *Y  -------- OFF
               254-007-233    26 30  COM YES *Y  -------- OFF
               254-007-232    42 35  COM YES *Y  -------- OFF
               254-007-231    58 40  COM YES *Y  -------- OFF
               254-007-230    74 45  COM YES *Y  -------- OFF

MAPSET ID=2
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
254-007-219                  250 20  SHR *Y  *Y  -------- OFF
               254-007-234    14 20  SHR *Y  *Y  -------- OFF
               254-007-233    26 20  SHR *Y  *Y  -------- OFF
               254-007-232    42 20  SHR *Y  *Y  -------- OFF
               002-002-002   254 20  SHR *Y  *Y  -------- OFF
               254-007-230    74 20  SHR *Y  *Y  -------- OFF
               254-007-229    90 20  SHR *Y  *Y  -------- OFF
               254-007-228   106 20  SHR *Y  *Y  -------- OFF

MAPSET ID=3
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
004-004-004                  200 20  COM YES *Y  -------- OFF
               254-007-219   250 20  COM YES *Y  -------- OFF
               254-007-234    10 30  COM YES *Y  -------- OFF
               254-007-233    26 30  COM YES *Y  -------- OFF
               002-002-002   254 30  COM YES *Y  -------- OFF
               254-007-227   122 40  COM YES *Y  -------- OFF
               254-007-226   138 40  COM YES *Y  -------- OFF
In MAP set 1, point code 002-002-002, subsystem 254, is the primary (first) point code and subsystem in a dominant MAP set with a relative cost value of 10. In MAP set 2, point code 002-002-002, subsystem 254, is one of eight point codes and subsystems in a load shared MAP set, each with a relative cost value of 20. In MAP set 3, point code 002-002-002, subsystem 254, is assigned the relative cost value of 30 in a combined dominant/load shared MAP set whose primary point code and subsystem is 004-004-004, subsystem 200, with a relative cost value of 20.

MAP set 1 is assigned to a global title translation containing the global title address of 9195551212. When the point code and subsystem in this final global title translation is translated to 002-002-002, subsystem 254, this point code and subsystem handles all the traffic for this final global title translation until it becomes unavailable. When point code 002-002-002, subsystem 254 becomes unavailable, the next point code and subsystem (254-007-219, subsystem 250) in this dominant MAP set handles the traffic until this point code and subsystem become unavailable, or until point code 002-002-002, subsystem 254 becomes available again.

MAP set 2 is assigned to a global title translation containing the global title address of 8285551212. When the point code and subsystem in this final global title translation is translated to 002-002-002, subsystem 254, the traffic for this final global title translation is shared equally among all members of the MAP set.

MAP set 3 is assigned to a global title translation containing the global title address of 3365551212. When the point code and subsystem in this final global title translation is translated to 002-002-002, subsystem 254, the traffic for this final global title translation is shared equally among all members of the MAP set with the relative cost value of 30, including point code 002-002-002, subsystem 254. When all of these point codes and subsystems with a relative cost value of 30 become unavailable, the traffic is shared equally among all the point codes and subsystems with the relative cost value of 40. If those with a relative cost of 40 also become unavailable, the traffic is shared equally among all the point codes and subsystems with the relative cost of 20.

By allowing a point code and subsystem to be assigned to multiple MAP sets, and by assigning a MAP set to a specific global title address, different load sharing arrangements can be made based on the global title address of the global title translation and the translated point code and subsystem.

The same MAP set can be assigned to multiple global title translations.

For the EAGLE to perform Flexible Final GTT Load Sharing, the Flexible GTT Load Sharing feature must be enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. Perform the Activating the Flexible GTT Load Sharing Feature procedure to enable and turn on the Flexible GTT Load Sharing feature.

The Flexible GTT Load Sharing feature can also be turned off with the chg-ctrl-feat command. If the Flexible GTT Load Sharing feature is turned off, provisioning for Flexible Final GTT Load Sharing can be performed with the ent-map, dlt-map, chg-map, and rtrv-map commands. The EAGLE will not perform Flexible Final GTT Load Sharing on GTT traffic requiring final global title translation. Perform the Turning Off the Flexible GTT Load Sharing Feature procedure to turn off the Flexible GTT Load Sharing feature.