forumarchive,nothingtosee,
Menu
Reply
wusong
  • 14
  • 1
  • 0
On our wavelength
140 Views
Message 1 of 7
Flag for a moderator

Gig1 drop connection

Hi, I just upgraded to Gig1 a few weeks ago, but I keep dropping the connection, a few times every day. I need to reboot the router at least once a day. I had similar problems with Hub 4 in the past, was hoping it would be resolved after the upgrade. Any advice?

Hub 4: Modem only

Google Nest Wifi set up.

Any help is appreciated.

Regards

Song

 

 

 

 

Tags (2)
0 Kudos
Reply
carl_pearce
  • 4.73K
  • 402
  • 706
Superstar
135 Views
Message 2 of 7
Flag for a moderator

Re: Gig1 drop connection


@wusong wrote:

Hi, I just upgraded to Gig1 a few weeks ago, but I keep dropping the connection, a few times every day. I need to reboot the router at least once a day. I had similar problems with Hub 4 in the past, was hoping it would be resolved after the upgrade. Any advice?

Hub 4: Modem only

Google Nest Wifi set up.

Any help is appreciated.

Regards

Song

 

 

 

 


As per Gary's request in your previous post in November we'll require the HUB stats to help.

Create a BQM and post the live link.

Could you access your router using http://192.168.0.1/ or http://192.168.100.1 for modem mode. Log in, select the 'Advanced settings / Tools / Network status' option and paste your 'Downstream', 'Upstream', and 'Network Log' tabs? Please copy/paste this data as text, split between multiple posts (Sometimes you have to click 'Post' twice due to an error message).

0 Kudos
Reply
wusong
  • 14
  • 1
  • 0
On our wavelength
121 Views
Message 3 of 7
Flag for a moderator

Re: Gig1 drop connection

Thanks for the reply. It seems BQM is not working on the google nest wifi as it blocks the ping.

See the router status below:

    3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

304027500007.440.4QAM25630
11387500006.340.4QAM2561
21467500006.640.4QAM2562
31547500006.940.4QAM2563
41627500006.840.4QAM2564
51707500006.640.4QAM2565
61787500006.440.4QAM2566
71867500006.540.9QAM2567
81947500006.840.4QAM2568
9202750000740.9QAM2569
102107500007.240.9QAM25610
112187500007.140.4QAM25611
122267500007.240.9QAM25612
132347500007.240.4QAM25613
142427500007.640.4QAM25614
152507500007.740.4QAM25615
162587500007.740.9QAM25616
172667500007.440.9QAM25617
182747500007.340.4QAM25618
192827500007.740.9QAM25619
202907500008.240.9QAM25620
212987500008.640.4QAM25621
223067500008.640.9QAM25622
233147500007.940.4QAM25623
243227500007.540.4QAM25624
253307500007.440.9QAM25625
263707500008.640.9QAM25626
273787500008.540.9QAM25627
28386750000840.4QAM25628
293947500007.540.4QAM25629
314107500007.640.4QAM25631



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

30Locked40.36628700
1Locked40.3662871865722986
2Locked40.36628716622000
3Locked40.36628739842516
4Locked40.3662871349762321
5Locked40.36628715751951
6Locked40.366287308603500
7Locked40.946209118960
8Locked40.36628700
9Locked40.94620900
10Locked40.94620900
11Locked40.36628760
12Locked40.94620900
13Locked40.36628700
14Locked40.36628700
15Locked40.36628700
16Locked40.94620900
17Locked40.94620900
18Locked40.36628700
19Locked40.94620900
20Locked40.94620900
21Locked40.36628700
22Locked40.94620900
23Locked40.36628700
24Locked40.36628700
25Locked40.94620900
26Locked40.94620900
27Locked40.94620900
28Locked40.36628700
29Locked40.36628700
31Locked40.36628760



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM4096759


0 Kudos
Reply
wusong
  • 14
  • 1
  • 0
On our wavelength
116 Views
Message 4 of 7
Flag for a moderator

Re: Gig1 drop connection

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159Locked4110.8194578300

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13940000042.85120 KSym/sec64QAM4
24620000041.85120 KSym/sec64QAM3
35370000041.85120 KSym/sec64QAM2
46030000041.85120 KSym/sec64QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

 

 

Network Log

Time Priority Description

Sun 24/01/2021 09:49:463No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 09:49:493Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 09:49:493Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 09:50:183No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 09:50:505MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 12:58:536CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 17:12:525Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 17:13:046CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 17:23:305Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 17:23:546CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 17:54:023No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 18:25:505Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 18:26:126CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 23:34:525Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 23:35:166CM-STATUS message sent. Event Type Code: 5; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 11:15:125Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 11:15:346CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:27:503No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:27:516CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:27:523No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:063SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:096CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:103No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:336CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:383No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:556CM-STATUS message sent. Event Type Code: 5; Chan ID: 27; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:563No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:28:593SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:023No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:026CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:023No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:116CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:153No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:236CM-STATUS message sent. Event Type Code: 5; Chan ID: 27; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:29:243No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:30:383Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:30:383Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:31:023Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 13:34:415MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 14:23:046CM-STATUS message sent. Event Type Code: 5; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 26/01/2021 14:47:063No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 26/01/2021 14:47:136CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 26/01/2021 14:47:133No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
carl_pearce
  • 4.73K
  • 402
  • 706
Superstar
103 Views
Message 5 of 7
Flag for a moderator
Helpful Answer

Re: Gig1 drop connection

With the cluster of downstream channels having a large number of errors recorded:

3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

30Locked40.36628700
1Locked40.3662871865722986
2Locked40.36628716622000
3Locked40.36628739842516
4Locked40.3662871349762321
5Locked40.36628715751951
6Locked40.366287308603500
7Locked40.946209118960

 

and your DOCSIS 3.1 channel power level being very high:

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159Locked4110.8194578300

 

and, although in spec, your downstream channels being high power (-6 to +10 is in spec, 0dB optimal), I would suggest an engineer is required to investigate further.

0 Kudos
Reply
wusong
  • 14
  • 1
  • 0
On our wavelength
100 Views
Message 6 of 7
Flag for a moderator
Helpful Answer

Re: Gig1 drop connection

Many thanks for the reply.

Shall I call them or it will be escalated through the forum?

VM engineer in the forum did resolve some of the problems for me in the past?

Thanks again.

Song

 

 

0 Kudos
Reply
carl_pearce
  • 4.73K
  • 402
  • 706
Superstar
94 Views
Message 7 of 7
Flag for a moderator

Re: Gig1 drop connection


@wusong wrote:

Many thanks for the reply.

Shall I call them or it will be escalated through the forum?

VM engineer in the forum did resolve some of the problems for me in the past?

Thanks again.

Song

 

 


It can take 5 - 10 days for a reply on here.

You can wait or contact VM, up to you.

0 Kudos
Reply