Kitz Forum
Broadband Related => ADSL Issues => Topic started by: konrado5 on July 19, 2018, 04:08:42 PM
-
I've noticed my synchronization establishment process is two-time.
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.994 Training
Last Retrain Reason: 8000
Last initialization procedure status: 0
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.992 Started
Last Retrain Reason: 8000
Last initialization procedure status: 0
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.922 Channel Analysis
Last Retrain Reason: 8000
Last initialization procedure status: 0
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.992 Message Exchange
Last Retrain Reason: 8000
Last initialization procedure status: 0
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.994 Training
Last Retrain Reason: 8000
Last initialization procedure status: 3
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.992 Started
Last Retrain Reason: 8000
Last initialization procedure status: 3
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: G.922 Channel Analysis
Last Retrain Reason: 8000
Last initialization procedure status: 3
# adslctl info --show
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 8000
Last initialization procedure status: 0
Max: Upstream rate = 1213 Kbps, Downstream rate = 21108 Kbps
Bearer: 0, Upstream rate = 1213 Kbps, Downstream rate = 20931 Kbps
I've also type adslctl info --linediag after first synchronization.
# adslctl info --linediag
adslctl: ADSL driver and PHY status
Status: G.994 Training
Last Retrain Reason: 8000
Last initialization procedure status: 3
Down Up
SNRM(dB): 3.2 6.0
LATN(dB): 23.0 15.1
SATN(dB): 25.3 14.6
TxPwr(dBm): 19.1 12.0
ATTNDR(Kbps): 21272 1221
After second syncrhonzation process power output is merely 18.6 dBm.
Have somebody noticed something like this? What is cause?
-
In the past, I have performed a similar experiment to that which you have shown and have also recorded evidence of two-attempt synchronisation process. It is a normal event for my circuit and I have never bothered to understand the reason why.
Perhaps a study of the relevant ITU-T G-Series Recommendations (https://www.itu.int/itu-t/recommendations/index.aspx?ser=G) may reveal the answer?
-
Retrain reason is 8000 (G992 failure).
http://forum.kitz.co.uk/index.php/topic,12504.0.html