Menu
Reply
tbp
  • 15
  • 1
  • 0
On our wavelength
705 Views
Message 1 of 25
Flag for a moderator

Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

Hi all, looking for some advice with my Gig1 connection.

On first installation was getting:

800-1100Mbps non-peak time, 400-550Mbps peak time (within contract amounts-happy enough)

After 4 weeks I'm getting:

~300Mbps non-peak time, 40Mbps peak time (not good)

Nothing has physically changed within or around the property that I'm aware of.

These are way below my contract limits.

The averages from above were all taken with:

  • -A single Win10 machine with the supplied CAT6 cable connected to a gigabit Ethernet port (also tested with an alternate machine with a gigabit Ethernet port and alternate new CAT6 cable - same results)
  • -No Wifi devices connected or any devices downloading content whilst speeds measured
  • Speeds measured using speedtest.net and Google SpeedTest

Factory reset of router had no effect.

Any advice before i sit in a call queue for eternity, to be asked to switch my computer off and back on again?

Are there any typically good SNR values for the coax connection I should be seeing in the router status pages that may indicate a virgin network connection issue?

Tags (1)
0 Kudos
Reply
Anonymous
Not applicable
702 Views
Message 2 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

Could you post the router stats so we can review?

Upstream, Downstream, and Network Log should be fine.

0 Kudos
Reply
tbp
  • 15
  • 1
  • 0
On our wavelength
689 Views
Message 3 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

Sure, please see the stats below.

Note I carried out a manual router reboot shortly before taking these.

3.0 Downstream channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
122270000001.90000238.983261QAM25612
102110000002.00000038.983261QAM25610
112190000001.90000238.983261QAM25611
132350000001.79999938.983261QAM25613
142430000001.50000038.983261QAM25614
152510000000.09999838.605377QAM25615
16259000000-0.50000038.605377QAM25616
172670000001.40000238.605377QAM25617
182750000002.29999938.983261QAM25618
192830000002.50000038.983261QAM25619
202910000002.40000238.605377QAM25620
212990000002.29999938.983261QAM25621
223070000002.40000238.983261QAM25622
233150000002.79999938.983261QAM25623
243230000003.29999938.983261QAM25624
254110000002.00000040.366287QAM25625
264190000002.20000138.983261QAM25626
274270000002.29999938.983261QAM25627
284350000002.40000238.983261QAM25628
294430000002.59999840.366287QAM25629
304510000002.90000240.366287QAM25630
314590000002.70000140.366287QAM25631
324670000002.79999940.366287QAM25632
334750000002.79999940.366287QAM25633
344830000002.90000240.366287QAM25634
354910000003.09999838.983261QAM25635
364990000003.29999940.366287QAM25636
375070000003.50000040.946209QAM25637
385150000003.70000140.366287QAM25638
395230000003.90000240.366287QAM25639
405310000004.09999840.366287QAM25640


3.0 Downstream channelsChannel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
12Locked000
10Locked872344200
11Locked2077828500
13Locked799968100
14Locked866687700
15Locked776390800
16Locked858000900
17Locked873995700
18Locked830632900
19Locked872485500
20Locked395836800
21Locked840361900
22Locked854710900
23Locked768251500
24Locked2035235000
25Locked2177346600
26Locked2182458200
27Locked3372416900
28Locked1990209600
29Locked2208539500
30Locked2175272700
31Locked2053948700
32Locked1952151000
33Locked2255636900
34Locked2138054900
35Locked2107470900
36Locked3310631900
37Locked2191507800
38Locked2295754000
39Locked1929648100
40Locked2218188500


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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
41Locked 4.718436610
0 Kudos
Reply
tbp
  • 15
  • 1
  • 0
On our wavelength
688 Views
Message 4 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

3.0 Upstream channels

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

14620000042.5205995120 KSym/sec64QAM5
22580000042.5205995120 KSym/sec64QAM8
33940000042.2705995120 KSym/sec64QAM6
43260000042.5205995120 KSym/sec64QAM7



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0010
3US_TYPE_STDMA0010
4US_TYPE_STDMA0010

 

Network Log

Time Priority Description

Thu 23/07/2020 19:51:203Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 23/07/2020 19:51:203Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 23/07/2020 19:51:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 23/07/2020 19:57:265MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 24/07/2020 00:25:476CM-STATUS message sent. Event Type Code: 5; Chan ID: 10; 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 26/07/2020 19:16:173No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 28/07/2020 02:19:504DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/07/2020 06:15:114DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 31/07/2020 11:04:556CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 01/08/2020 17:55:154DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 02/08/2020 16:44:264DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 04/08/2020 18:17:446CM-STATUS message sent. Event Type Code: 5; Chan ID: 26; 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;
Wed 05/08/2020 08:28:343No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 06/08/2020 04:54:576CM-STATUS message sent. Event Type Code: 5; Chan ID: 35; 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;
Thu 06/08/2020 05:33:463No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 06/08/2020 05:37:236CM-STATUS message sent. Event Type Code: 5; Chan ID: 15; 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;
Thu 06/08/2020 20:46:444DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 07/08/2020 03:36:296CM-STATUS message sent. Event Type Code: 5; Chan ID: 15; 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;
Fri 07/08/2020 04:52:153SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 07/08/2020 04:52:296CM-STATUS message sent. Event Type Code: 5; Chan ID: 15; 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;
Fri 07/08/2020 06:43:213SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 07/08/2020 06:43:386CM-STATUS message sent. Event Type Code: 5; Chan ID: 15; 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;
Fri 07/08/2020 10:25:154DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 07/08/2020 20:40:516CM-STATUS message sent. Event Type Code: 5; Chan ID: 15; 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;
Fri 07/08/2020 22:21:274DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 08/08/2020 00:01:526CM-STATUS message sent. Event Type Code: 5; Chan ID: 15; 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;
Sat 08/08/2020 00:02:114DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 08/08/2020 00:03:494DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 08/08/2020 07:58:046CM-STATUS message sent. Event Type Code: 5; Chan ID: 39; 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 09/08/2020 07:20:503No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 09/08/2020 12:51:006CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; 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 09/08/2020 16:01:233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 09/08/2020 20:27:396CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; 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 10/08/2020 00:17:143No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Anonymous
Not applicable
685 Views
Message 5 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

The stats look ok, however as you stated you've rebooted which generally clears the 'Pre' and 'Post' RS errors.

Could you setup a BQM here, and leave it running overnight?

It can give us a better picture of your line quality, especially when the stats don't give up much info!

0 Kudos
Reply
tbp
  • 15
  • 1
  • 0
On our wavelength
679 Views
Message 6 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

BQM is setup will check back in tomorrow, thanks.
0 Kudos
Reply
tbp
  • 15
  • 1
  • 0
On our wavelength
600 Views
Message 7 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

BQM from overnight

BQMCapture2.png

0 Kudos
Reply
Anonymous
Not applicable
557 Views
Message 8 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time


@tbp wrote:

BQM from overnight

BQMCapture2.png


The BQM looks great currently, I'm jealous!.

Maybe there is an oversubscription in your area.

0 Kudos
Reply
tbp
  • 15
  • 1
  • 0
On our wavelength
553 Views
Message 9 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time

Likely, however is the call center going to undestand or acknowledge that, ever?

Any suggestions for next steps?

0 Kudos
Reply
Anonymous
Not applicable
550 Views
Message 10 of 25
Flag for a moderator

Re: Gig1 4 weeks in - Ethernet Downstream ~240Mbps non-peak time, 40Mbps peak time


@tbp wrote:

Likely, however is the call center going to undestand or acknowledge that, ever?

Any suggestions for next steps?


An oversubscription would normally be flagged as an issue in the area, to be resolved by a certain date.

Only VM will know this, however they do acknowledge when this occurs.

One of the VM staff should reply to your thread.

0 Kudos
Reply