Menu
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
669 Views
Message 1 of 30
Flag for a moderator

Gig1 Upgrade - Massive Packet Loss

Hello,

My M350 connection has been upgraded to Gig1, I received the Hub 4 on Thursday and swapped out my older Superhub 3. Since that time my connection has been almost unusable at times, with so much packet loss that I can't even browse most websites due to the connections timing out (it took me several attempts to post this, for instance).

When a connection is established on sites like fast.com I can run through all of a speed test I do see the sort of speeds I would be expecting on the connection.

 

Broadband Quality Monitor 

My BQMMy BQM

 

 

Tested:

  • Reseating cables
  • Wired to hub in router mode
  • Wired to hub in modem mode
  • Restarting hub
  • Resetting hub to factory

 

Network Log

Time Priority Description

Sat 03/10/2020 02:22:433Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 02:22:433No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 02:29:243Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 02:29:243No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:00:203Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:00:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:09:393Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:09:393No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:10:393Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:10:393No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:12:193Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:12:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:14:583Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:14:583No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:17:383Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:17:383No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:21:583Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:21:583No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:28:373Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:28:373No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:49:553Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:49:553No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:52:353Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:52:353No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:09:533Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:09:533No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:11:333Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:11:333No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:35:313Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:35:313No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:36:503Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:36:513No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:43:303Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:43:303No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:45:103Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:45:103No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:54:093Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:54:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:56:493Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:56:493No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:59:283Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:59:293No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 05:11:273Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 05:11:273No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 05:14:073Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 05:14:073No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
659 Views
Message 2 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

Should also say that I can see the drops if I set up a constant ping going out to 8.8.8.8 or 1.1.1.1, then also the same with an incoming ping (from a server in a datacentre) to the Hub's WAN IP address.

There are periods where it appears stable for a time and then others where there are more pings with requests timing out than actually replying.

0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.94K
Alessandro Volta
649 Views
Message 3 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

Can you please

Type 192.168.0.1 (192.168.100.1 in Modem mode) into your browser URL bar and press enter. 

Hub 2 & 3 When the page appears DO NOT LOG IN but click ‘Check Router Status’.

Hub 4 When the page appears LOG IN then click ‘Check Router Status’.

Copy and paste the contents of the Downstream, Upstream and Network Log tabs onto here, if you get a yellow warning click the Post button again. Use one post for each tab if you wish. Please do not use screen grabs.

A Guru will be along soon to decipher the info.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
645 Views
Message 4 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

The Network Log was already posted above, but here are the Downstream and Upstream.

 

3.0 Downstream channels

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

304027500002.40000240.366287QAM25630
11387500005.90000240.946209QAM2561
21467500005.50000040.946209QAM2562
31547500005.59999840.366287QAM2563
41627500005.40000240.366287QAM2564
51707500004.90000240.946209QAM2565
61787500004.69999740.366287QAM2566
71867500004.69999740.946209QAM2567
81947500004.40000240.366287QAM2568
92027500004.09999840.366287QAM2569
102107500004.30000340.366287QAM25610
112187500004.09999840.946209QAM25611
122267500004.00000040.366287QAM25612
132347500003.70000140.366287QAM25613
142427500003.50000040.946209QAM25614
152507500003.70000140.366287QAM25615
162587500003.00000040.366287QAM25616
172667500003.40000240.366287QAM25617
182747500004.40000240.946209QAM25618
192827500004.69999740.946209QAM25619
202907500004.30000340.366287QAM25620
212987500003.09999840.366287QAM25621
223067500003.40000240.946209QAM25622
233147500003.50000040.366287QAM25623
243227500003.90000240.366287QAM25624
253307500004.30000340.366287QAM25625
263707500004.19999740.946209QAM25626
273787500003.50000040.366287QAM25627
283867500002.29999940.366287QAM25628
293947500001.79999938.983261QAM25629
314107500002.40000240.366287QAM25631



3.0 Downstream channels

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

30Locked000
1Locked86545000
2Locked84690000
3Locked15987324600
4Locked86314000
5Locked85152300
6Locked85168400
7Locked85802400
8Locked20252800
9Locked20655500
10Locked19968500
11Locked18665700
12Locked20437700
13Locked18310200
14Locked17819500
15Locked20429000
16Locked19983000
17Locked719694900
18Locked18765300
19Locked17218400
20Locked20127900
21Locked21040000
22Locked14246200
23Locked21518300
24Locked35264900
25Locked34239900
26Locked33650300
27Locked33050500
28Locked32407100
29Locked33645400
31Locked2766868500



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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked 3.678419

0

 

0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
642 Views
Message 5 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

3.0 Upstream channels

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

13940000041.7705995120 KSym/sec32QAM6
22580000041.2705995120 KSym/sec32QAM8
33260000041.2705995120 KSym/sec32QAM7
44620000041.7705995120 KSym/sec32QAM5



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0030
2US_TYPE_STDMA0030
3US_TYPE_STDMA0030
4US_TYPE_STDMA0030
0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.94K
Alessandro Volta
638 Views
Message 6 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

All 4 of your Upstream Channels are running at 32QAM - they should be at 64QAM.

Try a 5 minute reboot to see if your Hub can renegotiate a better connection.

If not you will need an engineer visit to put things back into spec.

Try a reboot using this method ...

Switch the Hub off using the small switch on the rear of the Hub next to the power cord and pull the PSU plug from the wall socket.

Give it a good 5 minutes put the plug back in and switch the Hub back on.

Allow the Hub a few minutes to fully restart then check the logs again.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
620 Views
Message 7 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

I powered it down for half an hour to be safe, now I've powered back on. Looking in Upstream all channels were still 32QAM, although as I'm writing this post I refreshed it and they decided to drop to 8QAM so not sure what's going on there.

I'll give it a few hours, see if it stablises or some magic happens, then I'll update with the stats then.

 

Thanks for your help with this so far Mike, appreciate it.

0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
602 Views
Message 8 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

Unfortunately not much difference. The upstreams have settled back down to all 32QAM again. I'll attach the usual diagnostic info to this post again if anyone can take a look please?

 

bqm.png

Status.png

 

Configuration.png

 

Upstream.png

Network Log

Time Priority Description

Sat 03/10/2020 03:12:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:14:583Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:14:583No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:17:383Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:17:383No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:21:583Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:21:583No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:28:373Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:28:373No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:49:553Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:49:553No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:52:353Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 03:52:353No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:09:533Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:09:533No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:11:333Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:11:333No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:35:313Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:35:313No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:36:503Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:36:513No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:43:303Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:43:303No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:45:103Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:45:103No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:54:093Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:54:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:56:493Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:56:493No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 04:59:283Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
600 Views
Message 9 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

3.0 Downstream channels

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

304027500002.90000240.366287QAM25630
11387500006.30000340.366287QAM2561
21467500005.90000240.366287QAM2562
31547500006.00000040.366287QAM2563
41627500005.80000340.366287QAM2564
51707500005.19999740.366287QAM2565
61787500005.09999840.366287QAM2566
71867500005.19999740.946209QAM2567
81947500004.80000340.366287QAM2568
92027500004.50000040.366287QAM2569
102107500004.69999740.946209QAM25610
112187500004.50000040.946209QAM25611
122267500004.40000240.366287QAM25612
132347500004.19999740.366287QAM25613
142427500004.00000040.366287QAM25614
152507500004.09999840.366287QAM25615
162587500003.40000240.366287QAM25616
172667500003.79999940.946209QAM25617
182747500004.90000240.946209QAM25618
192827500005.09999840.946209QAM25619
202907500004.80000340.946209QAM25620
212987500003.50000040.366287QAM25621
223067500003.90000240.366287QAM25622
233147500004.00000040.366287QAM25623
243227500004.30000340.366287QAM25624
253307500004.80000340.946209QAM25625
263707500004.80000340.946209QAM25626
273787500003.79999940.366287QAM25627
283867500002.70000140.946209QAM25628
293947500002.20000140.366287QAM25629
314107500002.90000240.366287QAM25631



3.0 Downstream channels

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

30Locked000
1Locked19211315800
2Locked20679988100
3Locked19161411100
4Locked19147647200
5Locked19119010600
6Locked19170555400
7Locked19145600900
8Locked9095958900
9Locked9084546000
10Locked9112405300
11Locked8805190900
12Locked8983224000
13Locked8942439600
14Locked8923115500
15Locked8949120100
16Locked9673146000
17Locked9732789700
18Locked9673256800
19Locked9670373200
20Locked9729538700
21Locked9704241400
22Locked7665450100
23Locked9726058900
24Locked18135334600
25Locked18135377500
26Locked18160068400
27Locked19596765800
28Locked18121537700
29Locked18185035100
31Locked18732929700



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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked 4.024650550
0 Kudos
Reply
Xermin
  • 21
  • 0
  • 0
Joining in
550 Views
Message 10 of 30
Flag for a moderator

Re: Gig1 Upgrade - Massive Packet Loss

Does it usually take long to hear anything from Virgin on here?

0 Kudos
Reply