Menu
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
282 Views
Message 1 of 14
Flag for a moderator

Really stuck

Help needed please , this may or may not be a VM  problem but someone may be able to answer...
I have several Alexa's and connect them to several smart plugs (gosund)..I was prompted to get a new router as virgin media said I was overloading my hub 3 causing my WiFi to crash, when this happened obviously nothing worked until I rebooted or it reconnected then everything was OK...I bought a TP Link router and set my hub to modem mode and everything connected fine..However I am still getting dropouts so it was not the router as I am losing Internet connection on wired and WiFi connection  , proving it is  a modem or isp network fault however what I am finding now is that when the Internet reconnects Alexa will not reconnect to various random plugs saying it is not connected or unresponsive but the plug will work through the Gosund app manually...the only way to get it back on line is to reinstall it and let Alexa detect it . this a pain as I have to reset up my routines.. any advise would be appreciated thanks... especially how to stop these drop outs ..I am reluctant to contact support as I just can't understand them .

0 Kudos
Reply
legacy1
  • 16.64K
  • 723
  • 1.64K
Alessandro Volta
274 Views
Message 2 of 14
Flag for a moderator

Re: Really stuck

VM say your overloading the so they will support in router mode if you have less device connected and then you get a better router use modem mode and VM will not support you...really think VM should support modem mode better to find the problems then first blaming it on number of devices.

Go to 192.168.100.1 and ports hubs download and upstream info.

Setup a BQM with your router allowing ICMP
https://www.thinkbroadband.com/broadband/monitoring/quality

---------------------------------------------------------------
0 Kudos
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
249 Views
Message 3 of 14
Flag for a moderator

Re: Really stuck

Thanks for info, unfortunately I am not rally sure I understand what you mean lol

0 Kudos
Reply
Andrew-G
  • 7.55K
  • 1.28K
  • 3.37K
Very Insightful Person
Very Insightful Person
238 Views
Message 4 of 14
Flag for a moderator

Re: Really stuck

Connect to the hub by clicking on this link http://192.168.100.1/  That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.  Then we can check for any obvious problems with power, noise or error counts.

 

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
207 Views
Message 5 of 14
Flag for a moderator

Re: Really stuck

 
Password 
 



Network LogTime Priority Description
14/07/2021 01:16:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:16:35criticalREG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:16:35ErrorT6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:16:35criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:15:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:15:12criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:14:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:14:16criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:13:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:13:15criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:12:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:12:27criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:10:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:10:42criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:09:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:09:46criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:08:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:08:12criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:07:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 01:07:20criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
 
0 Kudos
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
206 Views
Message 6 of 14
Flag for a moderator

Re: Really stuck

I dont think they all have come through ok  I kept getting error messages..wiull try again  just in case

 

 

0 Kudos
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
196 Views
Message 7 of 14
Flag for a moderator

Re: Really stuck

 
 
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1259000000-0.738256 qam16
21390000001.740256 qam1
31470000001.540256 qam2
41550000000.740256 qam3
5163000000140256 qam4
6171000000140256 qam5
7179000000140256 qam6
8187000000140256 qam7
91950000000.740256 qam8
10203000000040256 qam9
11211000000-1.238256 qam10
12219000000038256 qam11
13227000000038256 qam12
14235000000-0.238256 qam13
15243000000-0.240256 qam14
16251000000-0.740256 qam15
17267000000-140256 qam17
18275000000-1.238256 qam18
19283000000-1.540256 qam19
20291000000-1.738256 qam20
21299000000-2.238256 qam21
22307000000-238256 qam22
23315000000-1.538256 qam23
24323000000-1.240256 qam24


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.6120
2Locked40.3210
3Locked40.9170
4Locked40.3200
5Locked40.9200
6Locked40.9260
7Locked40.3100
8Locked40.360
9Locked40.370
10Locked40.3220
11Locked38.9180
12Locked38.9110
13Locked38.980
14Locked38.970
15Locked40.3140
16Locked40.9240
17Locked40.3100
18Locked38.9110
19Locked40.390
20Locked38.9210
21Locked38.9180
22Locked38.9220
23Locked38.9260
24Locked40.3120
 
0 Kudos
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
195 Views
Message 8 of 14
Flag for a moderator

Re: Really stuck

 
 



 
  •  
 
 
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14620000044.8512064 qam1
22580000043.3512064 qam4
33260000044.8512064 qam3
43940000044.8512064 qam2


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0010
3ATDMA0000
4ATDMA0000
 
0 Kudos
Reply
ukmartian
  • 114
  • 1
  • 1
Dialled in
194 Views
Message 9 of 14
Flag for a moderator

Re: Really stuck

ok sorted it you should have them now

 

0 Kudos
Reply
lotharmat
  • 3.53K
  • 241
  • 649
Community elder
179 Views
Message 10 of 14
Flag for a moderator

Re: Really stuck

Power levels look OK! - The log tells a different story though! - Far too many T3 Timeouts!

I'd say VM need to do some investigating



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

0 Kudos
Reply