Oracle® Communications EAGLE Database Administration - GTT User's Guide Release 46.8 F11880-02 |
|
![]() Previous |
![]() Next |
The In-Sequence Delivery of Class 1 UDT Messages provides
for the sequencing for both UDT and XUDT Class 1 MSUs. All UDT/XUDT Class 1
messages are routed out of the EAGLE in the same order that they were received
by the EAGLE. To enable the sequencing of UDT/XUDT Class 1 messages, the
class1seq
parameter value of the
chg-sccpopts
command is set to
on
.
When the
class1seq
parameter value is
on
, load sharing of these messages is
performed in the dominant mode, overriding the load sharing configuration in
the MAP and MRN tables. Delivering the UDT/XUDT Class 1 ITU messages in
sequence is guaranteed only if the
randsls
parameter value of the
chg-stpopts
command is either
off
or
class0
. If you wish to guarantee
delivering these messages in sequence, the
class1seq=on
and the
randsls=all
parameters should not be used
together in the EAGLE. The value of the
randsls
parameter is shown in the
rtrv-stpopts
command.
When the
class1seq
parameter value is
off
, load sharing of the UDT/XUDT Class 1
messages is performed using the load sharing configuration in the MAP and MRN
tables. The delivery of the UDT/XUDT Class 1 messages in sequence is not
guaranteed.
Caution:
If therandsls
parameter value of thechg-stpopts
command isall
, thus activating the Random SLS feature forITU
Class 1SCCP messages, the UDT/XUDT Class 1 messages are not delivered in
sequence. To ensure that Class 1 UDT/XUDT messages are delivered in sequence,
therandsls
parameter value should be set to
eitheroff
orclass0
.
Caution:
However, if therandsls
parameter value of thechg-stpopts
command isall
, Class 1 UDT/XUDT messages are load shared across
equal cost destinations by the WeightedSCP Load Balancing and Intermediate
Global Title Load Sharing (IGTTLS) features. If therandsls
parameter value of thechg-stpopts
command is eitheroff
orclass0
, load
sharing for all Class 1SCCP messages is supported only in the dominant mode.
If the messages are not in the correct sequence when they arrive at the EAGLE, they are not delivered to the next node in the correct sequence. The EAGLE does not perform message re-sequencing for messages that are received out of sequence, because the EAGLE is a transit node. Message re-sequencing is the responsibility of the originating and destination nodes.
GT-routed Class 0 UDT/XUDT messages are not sequenced, therefore, the EAGLE does not guarantee routing these messages out of the EAGLE in the same order that they were received.