Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[valleysboy]

Hi All,

I just received the following resync alert from mydslwebstats:

"Hi valleysboy

This is to let you know that a resync/restart occurred on your line at 15-08-2015 16:58 local time (+/- 1 minute).

Reason: 0 Loss of Service

Current Downstream Sync Rate is now 49000kbps
Current Upstream Sync Rate is now 16422kbps"

Trouble is there is no evidence of a resync at this end - HG612 shows uptime at 58 days (and counting) and dslstats event log shows nothing:

"15 Aug 2015 14:21:50   Recording started

15 Aug 2015 14:21:57   IP address is now 86.184.105.240
15 Aug 2015 17:48:10   IP address is now 86.184.105.240 "

Am I missing something here - how else can I confirm a resync has occurred?

(I'm not sure it really matters, but I have been waiting a long time for DLM to relent on my banding so I am interested).

Cheers,

Val

[GigabitEthernet]

Is the time since last resync at 58 days?

[valleysboy]

Hi Alecr

I'm not sure where I find that out?

dslstats shows:

"Stats recorded 15 Aug 2015 18:58:53

DSLAM/MSAN type:           BDCM:0xa459 / v0xa459
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    
Resyncs:                   0 (since 15 Aug 2015 14:21:50)"

whereas MDWS shows a resync at    15-08-2015 16:58

So I'm not sure why the discrepancy?

Val

[GigabitEthernet]

If you telnet into the HG612, enter sh and then enter xdslcmd info --stats, it'll show up if you scroll all the way down.

It will say, Since Link time = x.

[tbailey2]

This is to let you know that a resync/restart occurred on your line at 15-08-2015 16:58 local time (+/- 1 minute).
Reason: 0 Loss of Service

Current Downstream Sync Rate is now 49000kbps
Current Upstream Sync Rate is now 16422kbps"

You lost an upload somewhere en-route that caused the AS value (the number of secs the line has been up) to drop to zero (which is very unusual) for one minute then rise again to its previous value (look at your SNRM graph as that shows missing uploads). This is exactly what happens when there is a resync, hence the alert. 

If you look at the Upload time graph you'll see it - on reflection, and for whatever reason, the missing point should join to the previous one if it not actually uploaded so must be some sort of glitch as I've never seen this before. I'd have to look at the database table to maybe get some idea if I can find the time, you can ignore it though.

[valleysboy]

Thanks both

Found the "link since" time:

Since Link time = 49 days 17 hours 2 min 47 sec

which, interestingly, doesn't correspond to the router, dslstats or mdws figures who all report 58 days 

Anyways I'm happy to stop worrying about it, so thanks for the help!

Now if I can get DLM to relent and release my downstream banding (stuck on 49000, rock solid, since the beginning of time) I'd be a happy bunny!

Thanks again,

Val

[burakkucat]

Since Link time = 49 days 17 hours 2 min 47 sec

I wonder how many seconds the above represents? 

Could that be the limit of the size of the data that can be held by the variable?

(((((49 x 24) + 17) x 60) + 2) x 60) + 47 = 4294967 

Hmm . . . 2³² = 4294967295 

b*cat is confused. 

[roseway]

Don't be confused. What you say is quite right. 49 days 17 hours 2 min 47 sec is 2^32 milliseconds. This came to light a while back when Stuart (Broadstairs) noticed that his modem was stuck at this value. DSLstats now checks for this situation, and switches over to using the AS (available seconds) figure to determine uptime.

So in this case the "Since Link time=..." value is wrong. MDWS seems to have reported a phantom resync as Tony explained, and DSLstats and HG612_Modem_Stats are reporting correct values.

[burakkucat]

Ah, milliseconds and not seconds.

Thank you. 

[tbailey2]

@valleysboy

Just had a look in the database stats table (currently with 33 million+ records) and I can see that you uploaded a modem stats file at 16:58 with a lot of the data that should be there containing zeros. While the SNRM, Sync etc was there, one of the zeroed records was the Uptime seconds count which caused the notification (also the Uptime count in Hours that is also recorded was zero).

Why? Who knows 

[valleysboy]

Thanks for the investigation work all.

So the Link Since bucket is full - makes sense as the modem stats are still showing exactly the same time. Perhaps Huawei didn't think their equipment could stay up that long 

@Tony - thanks for taking the time to look at my uploads, I guess we'll never know why it happened, just one of life's little mysteries!

Cheers,

Val