| Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.6 E93318 Revision 1 |
|
 Previous |
 Next |
| Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.6 E93318 Revision 1 |
|
|
Previous |
Next |
This procedure is used to change the values of the level 3 timers using the chg-l3t command. The level 3 timers apply to both ANSI and ITU linksets, except as noted for the specific timer.
Note:
Only one level 3 timer set exists.The level 3 timers are defined as follows:
:t1 – Timer 1 – Delay to avoid message mis-sequencing on changeover. Values - 100-2000 milliseconds; system default value - 800 milliseconds.
:t2 – Timer 2 – Waiting for changeover acknowledgment. Values - 100-3000 milliseconds; system default value - 1400 milliseconds.
:t3 – Timer 3 – Time controlled diversion – delay to avoid mis-sequencing on changeback. Values - 100 - 2000 milliseconds; system default value - 800 milliseconds.
:t4 – Timer 4 – Waiting for changeback acknowledgment (1st attempt). Values - 100-2000 milliseconds; system default value - 800 milliseconds.
:t5 – Timer 5 – Waiting for changeback acknowledgment (2nd attempt). Values - 100-2000 milliseconds; system default value - 800 milliseconds.
:t6 – Timer 6 – Delay to avoid message mis-sequencing on controlled rerouting. Values - 100-2000 milliseconds; system default values - 800 milliseconds. If the 6-Way Loadsharing on Routesets feature is enabled and turned on, it is recommended that the value for this timer is set to 100 milliseconds. Enter the rtrv-ctrl-feat:partnum=893019801 command to verify the status of the 6-Way Loadsharing on Routesets feature.
:t7 – Timer 7 – Waiting for signaling data link connection acknowledgment. Values - 100-3000 milliseconds; system default value - 1000 milliseconds.
:t8 – Timer 8 – Transfer-prohibited (TFP) inhibited timer (transient solution). Values - 500-2000 milliseconds; system default value - 800 milliseconds.
:t10 – Timer 10 – Waiting to repeat signaling-route-set-test (SRST) message. Values - 20000-90000 milliseconds; system default value - 30000 milliseconds.
:t11 – Timer 11 – Transfer-restricted timer. Values - 1000-90000 milliseconds; system default - 30000 milliseconds.
:t12 – Timer 12 – Waiting for uninhibit acknowledgment. Values - 100-2000 milliseconds; system default value - 800 milliseconds.
:t13 – Timer 13 – Waiting for force uninhibit. Values - 100-2000 milliseconds; system default value - 800 milliseconds.
:t14 – Timer 14 – Waiting for inhibition acknowledgment. Values - 200-4000 milliseconds; system default value - 2000 milliseconds.
:t15 – Timer 15 – Waiting to repeat signaling route set congestion test (RSCT). Values - 200-4000 milliseconds; system default value - 3000 milliseconds.
:t16 – Timer 16 – Waiting for route set congestion (RSC) status update. Values - 200-3000 milliseconds; system default value - 1400 milliseconds.
:t17 – Timer 17 – Delay to avoid oscillation of initial alignment failure and link restart. Values - 500-2000 milliseconds; system default value - 800 milliseconds.
:t18 – Timer 18 – ANSI linksets – Repeat TFR once by response method. Values - 2000-20000 milliseconds; system default value - 10000 milliseconds.
:it18 – Timer 18 – ITU linksets – Timer within a signaling point whose MTP restarts to supervise the receipt of routing information and activation of the link and linkset. Values - 19000-50000 milliseconds; system default value - 50000 milliseconds.
:t19 – Timer 19 – ANSI linksets – Failed link craft referral timer. Values - 30000-600000 milliseconds; system default value - 480000 milliseconds.
:it19 – Timer 19 – ITU linksets – Supervision timer during MTP restart to avoid ping of TFP, TFR1, and TRA messages. Values - 67000-69000 milliseconds; system default value - 67000 milliseconds.
:t20 – Timer 20 – ANSI linksets – Waiting to repeat local inhibit test. The value of the t20 parameter overwrites the value of the it22 parameter. Values - 90000-120000 milliseconds; system default value - 90000 milliseconds.
:it20 – Timer 20 – ITU linksets – Overall MTP restart timer at the signaling point whose MTP restarts. Values - 59000-61000 milliseconds; system default value - 59000 milliseconds.
:it20 – Timer 20 – ITU linksets – Waiting to repeat local inhibit test (it22 parameter). Values - 59000-61000 milliseconds; system default value - 59000 milliseconds.
:t21 – Timer 21 – ANSI linksets – Waiting to repeat remote inhibit test. The value of the t21 parameter overwrites the value of the it23 parameter. Values - 90000-120000 milliseconds; system default value - 90000 milliseconds.
:it21 – Timer 21 – ITU linksets – Overall MTP restart timer at a signaling point adjacent to one whose MTP restarts. Values - 63000-65000 milliseconds; system default value - 63000 milliseconds.
:t22 – Timer 22 – ANSI linksets – the amount of time the restarting node waits for the signaling links to become available. This parameter is used when the MTP restart feature is turned on. Values - 10000-60000 milliseconds; system default value - 10000 milliseconds.
:it22 – Timer 22 – ITU linksets – Waiting to repeat local inhibit test. The value of the it22 parameter overwrites the value of the t20 parameter. Values - 180000-360000 milliseconds; system default value - 90000 milliseconds.
:t23 – Timer 23 – ANSI linksets – the amount of time the restarting node waits to receive the TRA message. This parameter is used when the MTP restart feature is turned on. Values - 9000-100000 milliseconds; system default value - 10000 milliseconds.
:it23 – Timer 23 – ITU linksets – Waiting to repeat remote inhibit test. The value of the it23 parameter overwrites the value of the t21 parameter. Values - 180000-360000 milliseconds; system default value - 90000 milliseconds.
:t24 – Timer 24 – ANSI linksets – the amount of time the restarting node waits to broadcast all TRA messages. This parameter is used when the MTP restart feature is turned on. Values - 9000-60000 milliseconds; system default value - 10000 milliseconds.
:t25 – Timer 25 – ANSI linksets – the amount of time the adjacent node waits for the TRA message. This parameter is used when the MTP restart feature is turned on. Values - 30000-35000 milliseconds; system default value - 30000 milliseconds.
:t26 – Timer 26 – ANSI linksets – the amount of time the restarting node waits to repeat the TRW message. This parameter is used when the MTP restart feature is turned on. Values - 12000-15000 milliseconds; system default value - 12000 milliseconds.
:t28 – Timer 28 – ANSI linksets – the amount of time the adjacent node waits for the TRW message. This parameter is used when the MTP restart feature is turned on. Values - 3000-35000 milliseconds; system default value - 3000 milliseconds.
:t29 – Timer 29 – ANSI linksets – this timer is started when a TRA message is sent in response to an unexpected TRA/TRW message or when the MTP restart process has completed. Any TRA/TRW messages received while the T29 timer is running are ignored. This parameter is used when the MTP restart feature is turned on. Values - 60000-65000 milliseconds; system default value - 60000 milliseconds.
:t30 – Timer 30 – ANSI linksets – the amount of time between sending TFPs/TFRs in response to an unexpected TRA/TRW message. This parameter is used when the MTP restart feature is turned on. Values - 30000-35000 milliseconds; system default values - 30000 milliseconds.
:t31 – Timer 31 – ANSI linksets – False link congestion detection timer. Values - 10000-120000 milliseconds; system default value - 60000 milliseconds.
:t32 –Timer 32 – Link oscillation timer - Procedure A. Values - 60000-120000 milliseconds; system default values - 60000 milliseconds.
It is possible that a problem on a signaling link can cause one signaling link in a linkset to go into congestion, even though the traffic on the linkset is not high enough to cause congestion. For example, if a link has a large number of retransmissions, the throughput of the signaling link could drop enough to cause congestion on that signaling link. To help prevent this from happening, the EAGLE starts the level 3 T31 timer whenever a signaling link goes into congestion. If the signaling link remains in the same congestion state until the level 3 T31 timer expires, the signaling link is removed from service. The signaling link becomes unaligned, then the alignment procedure is started.
The congestion level that starts the level 3 T31 timer can be set to either congestion level 1 or congestion level 2 using the chg-stpopts command with the mtpt31ctl parameter. This congestion level can be verified with the rtrv-stpopts command and is shown in the MTPT31CTL field. The level 3 T31 timer is started when the signaling link reaches this congestion level or a higher level. An increase in congestion level or abatement to a lower congestion level restarts the timer. When the congestion level goes below the congestion level configured in the chg-stpopts command, the level 3 T31 timer is stopped. If the level 3 T31 timer expires and the signaling link’s congestion level has not changed, the signaling link is restarted.
For example, if the level 3 T31 timer is set at 60 seconds and a signaling link goes into congestion level 1, the level 3 T31 timer is started. If, after 45 seconds, the signaling link’s congestion increases to level 2, the timer is restarted to 60 seconds. If the signaling link remains at congestion level 2 for 60 seconds, the signaling link is taken out of service and it becomes unaligned. Then the alignment procedure is started, and the EAGLE attempts to realign the signaling link. The level 3 T31 timer can only be assigned to ANSI SS7 linksets and signaling links.
The level 3 T32 timer helps to prevent a signaling link from oscillating in and out of service. When the EAGLE begins restoring an out of service signaling link, the EAGLE starts the level 3 T32 timer. If the signaling link fails again before the level 3 T32 expires, the EAGLE does not attempt to continue to bring the signaling link into service until the level 3 T32 timer expires. Once the level 3 T32 timer expires, the EAGLE attempts to restore the signaling link into service.
The level 3 T32 timer is only started after a signaling link fails, not when a signaling link is manually deactivated. When a signaling link is manually taken out of service using the dact-slk command, the level 3 T32 timer is stopped, if it is running. When the signaling link is brought back into service using the act-slk command, the level 3 T32 timer is not started. The level 3 T32 timer is not started when a new signaling link is first aligned.
The l3tset parameter specifies the level 3 timer set. For any level 3 timer parameters not specified with the chg-l3t command, the values for those parameters are not changed.
Figure 3-24 Changing Level 3 Timers
