Menu
Reply
  • 18
  • 0
  • 3
jimbob
On our wavelength
350 Views
Message 1 of 5
Flag for a moderator

Daily brief disconnects (Area 31)

Hi all,

I'm having difficulties with daily disconnects on my VM Broadband service. I run the SH in Modem mode and on a wired network. Quite often either get "request timed out" when pinging an external web address or SH gets green flashing arrow lights for a few minutes then reconnects. 

Can someone help interpret these BQM graphs and can VM check my account their end please?

BQM Graphs past week (14/10 - 20/10/19)

BQM Graph from today (20/10/19):VM_BQM01.jpg

Thanks,

Jimbob
--------------------
Content and advice from my experience as a Network Tech. Use at own risk.
0 Kudos
Reply
  • 6.42K
  • 493
  • 1.07K
Tudor
Hero
346 Views
Message 2 of 5
Flag for a moderator

Re: Daily brief disconnects (Area 31)

Please post your up/downstream stats and network log. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos
Reply
  • 18
  • 0
  • 3
jimbob
On our wavelength
320 Views
Message 3 of 5
Flag for a moderator

Re: Daily brief disconnects (Area 31)

Forum doesn't like table in post for some reason, says message too big. Just plain text follows...

Cable Modem Status    
Item Status Comments
Acquired Downstream Channel (Hz) 443000000 Locked
Ranged Upstream Channel (Hz) 39400000 Locked
Provisioning State Online  
 
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 443000000 -2.5 40 256 qam 5
2 451000000 -2.4 40 256 qam 6
3 459000000 -2.2 40 256 qam 7
4 467000000 -2.2 40 256 qam 8
5 475000000 -2.5 40 256 qam 9
6 483000000 -2.2 40 256 qam 10
7 491000000 -2 40 256 qam 11
8 499000000 -1.9 40 256 qam 12
9 507000000 -2.2 40 256 qam 13
10 515000000 -2.2 40 256 qam 14
11 523000000 -2.2 38 256 qam 15
12 531000000 -1.7 40 256 qam 16
13 539000000 -1.7 40 256 qam 17
14 547000000 -1.7 40 256 qam 18
15 555000000 -2 40 256 qam 19
16 563000000 -1.4 40 256 qam 20
17 571000000 -1.5 40 256 qam 21
18 579000000 -1.5 40 256 qam 22
19 587000000 -2 40 256 qam 23
20 595000000 -1.5 40 256 qam 24
21 635000000 -1.5 38 256 qam 25
22 643000000 -0.7 40 256 qam 26
23 651000000 -1 40 256 qam 27
24 659000000 -0.7 40 256 qam 28
 
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 64 98
2 Locked 40.3 45 56
3 Locked 40.3 58 62
4 Locked 40.3 60 60
5 Locked 40.3 70 61
6 Locked 40.9 81 59
7 Locked 40.9 107 62
8 Locked 40.9 116 59
9 Locked 40.3 123 61
10 Locked 40.3 124 70
11 Locked 38.9 116 67
12 Locked 40.3 158 57
13 Locked 40.9 128 56
14 Locked 40.3 159 70
15 Locked 40.3 153 49
16 Locked 40.3 187 50
17 Locked 40.9 173 43
18 Locked 40.3 180 50
19 Locked 40.3 165 50
20 Locked 40.3 154 85
21 Locked 38.9 143 81
22 Locked 40.3 180 44
23 Locked 40.9 169 48
24 Locked 40.9 160 47
 
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 4.471 5120 16 qam 26
2 25800000 4.275 5120 16 qam 28
3 32600000 4.4 5120 16 qam 27
4 46200000 4.375 5120 16 qam 25
 
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
 
General Configuration
Network access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode Docsis30
Config file V0d8310cb0396200.cm
 
Primary Downstream Service Flow
SFID 21744
Max Traffic Rate 80500000
Max Traffic Burst 10000
Min Traffic Rate 0
 
Primary Upstream Service Flow
SFID 21743
Max Traffic Rate 5250020
Max Traffic Burst 16320
Min Traffic Rate 0
Max Concatenated Burst 16320
Scheduling Type BestEffort
 
Network Log    
Time Priority Description
20/10/2019 09:12:5 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:12:5 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:12:5 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:20 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:20 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:27 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:27 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:31 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:31 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:56 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 09:13:56 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 15:35:17 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 15:37:57 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 16:02:8 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 16:02:8 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 16:03:21 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 16:03:21 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 16:13:55 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
20/10/2019 16:13:55 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 0:01:36 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
 
Noticed "Timing Synchronization fialure"  and "No ranging response" received in the logs. 
 
I don't know how to interpret the numbers in the Upstream and Downstream section.

I have a PDF version available which is easier to read the tables, let me know if you want it.
 
Thanks,

Jimbob
--------------------
Content and advice from my experience as a Network Tech. Use at own risk.
0 Kudos
Reply
  • 18
  • 0
  • 3
jimbob
On our wavelength
252 Views
Message 4 of 5
Flag for a moderator

Re: Daily brief disconnects (Area 31)

Interesting that the act of powering off my modem, connecting my laptop directly to modem (instead of router), powering up my modem and waiting for it to fully sync has created a stable connection. Could the act of having a different MAC address register on VMs network cause me to connect to a different piece of equipment their end? (My laptop as a DHCP client getting the 86.. address instead of my routers WAN port getting the address) 

I powered the modem down, reconnected my router, and powered modem up and my setup is stable today. I will keep an eye on BQM graphs and pings.

$RIA7Z1V.jpg

Jimbob
--------------------
Content and advice from my experience as a Network Tech. Use at own risk.
0 Kudos
Reply
  • 11.48K
  • 256
  • 1.57K
horseman
Alessandro Volta
209 Views
Message 5 of 5
Flag for a moderator

Re: Daily brief disconnects (Area 31)


@jimbob wrote:.... [snipped]...Could the act of having a different MAC address register on VMs network cause me to connect to a different piece of equipment their end? ......... I will keep an eye on BQM graphs and pings.

Not unless any (PHY)cable resegmentation has occurred(eg typically for  severe utilisation issues) otherwise it's more likely a "virtual mac domain/different line card" change.....?

Remember  that  TBB BQM (ICMP echo)  plot with Hub3.x (certainly  up  to V10 hardware v613  software, (- I can't dislose any changes above  those versions)  may well be susceptable to "resource issues" with specific "peering transit AP" in .RouterMode so any "redwall/block symptom" is likely to be misleading.  Best to also use/cross check with alternative "f8lure@mouslike.com" ICMP or  even better: "SamKnows UDP trace".....   (assuming you have been retained on the SK Panel).

In any event(until ForumTeam respond): you might consider noting any  V.I.P response[*]  once  they have engaged as their "credibility rating" is worth far more than most(but not all contributors)?   😉

Nota Bene:    [*] As a fossilised dinosaur of Nynex/C&W/NTL/VM with UseNet  BB . in late 90's until 2009 when CA(Community Ambassadors) evolved into SuperUsers in 2010/2011 and now VIP(Very Insightful Persons) in 3/4Q 2019 then be aware that at  least 4 of us ex CA/SU's have resigned or been "REVOKED" and at least one of us 😛 awarded VIP ?(Very  Intolerant Poster) back in end May2019 for not "suffering fools gladly"  😞 

Regards Tony
"Life is a Binary Inspired Turing Computed Hologram"(don't PM or @Mention me - in case ignoring you offends)
DEFROCKED