Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Help needed, Packet Loss, high latency to router

djgeurn
On our wavelength

on ‎05-01-2023 20:54

Hi!

Can someone help? I have 1Gb connection and generally get good speeds but I do get random packet loss, seems to be always when on a work zoom/webex etc. Have tried a reboot and factory restet but nothing seems to fix it. On my scan using the app I do see incredibly high latency (15k +) and Jitter (1000ms) to the hub, this is not to the device, just to the hub. Speeds seem to be fin Av around 500Mbps. I also notice poor performance on streaming sometimes even with wired connections. Will attach BQM graphs and network status reports below:-

Time Priority Description

Thu 01/01/1970 00:01:253No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:02:323Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=00:01:xxxxxxCM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:02:323No Ranging Response received - T3 time-out;CM-MAC=axxxxxxxx;CMTS-MAC=00:01:xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:02:544Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=axxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:04:223Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:04:223No Ranging Response received - T3 time-out;CM-MAC=xxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:04:513Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=axxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:04:513No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 28/12/2022 16:20:335MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 29/12/2022 00:06:263No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 31/12/2022 05:43:354DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 31/12/2022 10:28:473No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 01/01/2023 16:40:556US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=xxxxxxxxxxCMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 02/01/2023 00:22:453No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 03/01/2023 08:07:044DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 03/01/2023 13:08:453No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 03/01/2023 15:11:576US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 03/01/2023 16:13:203No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 04/01/2023 11:08:486US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:02:433DHCP FAILED - Discover sent, no offer received;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:03:083Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:03:093No Ranging Response received - T3 time-out;CM-MAC=axxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:03:304Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:05:003Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:05:003No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:05:323Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:05:323No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:06:043Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:06:043No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 04/01/2023 12:19:135MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 04/01/2023 16:05:053No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:23:193SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:23:235Lost MDD Timeout;CM-MAC=xxxxxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:23:236CM-STATUS message sent. Event Type Code: 21; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:23:245Lost MDD Timeout;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:23:473No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:24:026CM-STATUS message sent. Event Type Code: 23; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:24:063No Ranging Response received - T3 time-out;CM-MAC=xxxxxxx;CMTS-MAC=00:01:xxxxx;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:24:116CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxx;CMTS-MAC=00:01:x;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 10:24:296US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=xxxxxxxx;CMTS-MAC=0xxxx:da;CM-QOS=1.1;CM-VER=3.1;
Thu 05/01/2023 13:47:053No Ranging Response received - T3 time-out;CM-MAC=axxxxxxxx;CMTS-MAC=xxxxxx;CM-QOS=1.1;CM-VER=3.1;
 
0 Kudos
23 REPLIES 23

legacy1
Alessandro Volta
In response to Tudor

on ‎09-01-2023 19:41

A side from the low upstream modulation Your live BQM shows mostly ok.

Are you connected by wifi?
---------------------------------------------------------------

BQM, Test for outgoing ports and SSL/L2TP VPN test

0 Kudos

djgeurn
On our wavelength
In response to Tudor

on ‎09-01-2023 20:09

hey mate, thanks for taking a look, showing as 64QAM now. here is the latest stats but still getting these spikes in packet loss and latency

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14960000037.2705995120 KSym/sec64QAM1
22360000036.0205995120 KSym/sec64QAM9
34310000036.7705995120 KSym/sec64QAM2
43660000036.5205995120 KSym/sec64QAM3
53010000036.2705995120 KSym/sec64QAM4


3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_STDMA0070
2US_TYPE_STDMA0060
3US_TYPE_STDMA00120
4US_TYPE_STDMA0070
5US_TYPE_STDMA0050


3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
1010.433.02KQAM8


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
10OFDMA20853.470

Network Log

Time Priority Description
Thu Jan 1 00:01:25 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:02:32 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:02:32 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:02:54 19704Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:04:22 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:04:22 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:04:51 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:04:51 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Dec 28 16:20:33 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 29 00:06:26 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Dec 31 05:43:35 20224DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Dec 31 10:28:47 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 1 16:40:55 20236US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 2 00:22:45 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 3 08:07:04 20234DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 3 13:08:45 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 3 15:11:57 20236US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 3 16:13:20 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 4 11:08:48 20236US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:02:43 19703DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:03:08 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:03:09 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:03:30 19704Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:00 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:00 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:32 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:32 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:04 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:04 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 4 12:19:13 20235MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 4 16:05:05 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:23:19 20233SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:23:23 20235Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:23:23 20236CM-STATUS message sent. Event Type Code: 21; Chan ID: 49; 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 Jan 5 10:23:24 20235Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:23:47 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:24:02 20236CM-STATUS message sent. Event Type Code: 23; Chan ID: 49; 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 Jan 5 10:24:06 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:24:11 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 10:24:29 20236US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 5 13:47:05 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 7 10:13:03 20234DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 7 13:24:04 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

djgeurn
On our wavelength
In response to Tudor

on ‎09-01-2023 20:09

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
92027500003.29999940.946209QAM2569
11387500003.59999840.366287QAM2561
21467500003.59999840.946209QAM2562
31547500003.59999840.946209QAM2563
41627500003.50000040.366287QAM2564
51707500003.29999940.946209QAM2565
61787500003.20000140.366287QAM2566
71867500003.29999940.946209QAM2567
81947500003.40000240.946209QAM2568
102107500003.40000240.946209QAM25610
112187500003.29999940.366287QAM25611
122267500003.20000140.366287QAM25612
132347500003.20000140.946209QAM25613
142427500003.09999840.366287QAM25614
152507500003.09999840.366287QAM25615
162587500003.20000140.366287QAM25616
172667500003.40000240.366287QAM25617
182747500003.79999940.366287QAM25618
192827500003.29999940.366287QAM25619
202907500002.79999940.366287QAM25620
212987500002.50000040.366287QAM25621
223067500002.59999840.946209QAM25622
233147500002.59999840.366287QAM25623
243227500002.59999838.983261QAM25624
253307500002.00000038.983261QAM25625
263387500001.90000238.983261QAM25626
273467500001.70000138.983261QAM25627
283547500001.59999838.605377QAM25628
293627500001.50000038.983261QAM25629
303707500001.50000038.605377QAM25630
313787500001.40000238.983261QAM25631


3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
9Locked40.94620900
1Locked40.36628700
2Locked40.94620900
3Locked40.94620900
4Locked40.36628700
5Locked40.94620900
6Locked40.36628700
7Locked40.94620900
8Locked40.94620900
10Locked40.94620900
11Locked40.36628700
12Locked40.36628700
13Locked40.94620900
14Locked40.36628700
15Locked40.36628700
16Locked40.36628700
17Locked40.36628700
18Locked40.36628700
19Locked40.36628700
20Locked40.36628700
21Locked40.36628700
22Locked40.94620900
23Locked40.36628700
24Locked38.98326100
25Locked38.98326100
26Locked38.98326100
27Locked38.98326100
28Locked38.60537700
29Locked38.98326100
30Locked38.60537700
31Locked38.98326100


3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
49964K1880QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
49Locked402.63335676779109
0 Kudos

djgeurn
On our wavelength
In response to legacy1

on ‎09-01-2023 20:13

Hardwired in to the pod

It's so frustrating as speeds are awesome, just unreliable and always seems to be when streaming or on a zoom/webex. It's almost like the router can't handle it when there's too much traffic? Sorry if that sounds obvious but IMHO I should be able to stream quite a few connections without getting any loss, especially with these speeds and a lot of the network over ethernet. 

what's your thoughts on the Virgin Scan showing 15k latency and 1000 jitter to the hub? Seems to be ok hub to device but not sure if that's normal to the hub?

 

 

0 Kudos

djgeurn
On our wavelength

on ‎10-01-2023 11:59

Posting an update here as been having major issues this morning here is todays BQM graph showing significant packet loss and latency8285dfb2f7addcd2dae1836b7b385ecab7cef268-10-01-2023.png

0 Kudos

Beth_G
Forum Team
Forum Team
In response to djgeurn

on ‎12-01-2023 13:04

Hi djgeurn,

Thanks for posting the graph, sorry to hear the issues are continuing on.

I've had a look at this end and it appears that there is a known SNR outage in your area, which will be causing issues with your speeds and connection in general. It's estimated to be resolved by 18th January.

We are sorry for any inconvenience caused in the meantime, do let us know how things are after the given date.

Thank you,

Beth
0 Kudos

djgeurn
On our wavelength
In response to Beth_G

on ‎13-01-2023 21:28

Thanks Beth, out of interest, what's SNR?

0 Kudos

jem101
Superstar
In response to djgeurn

on ‎13-01-2023 21:51

Signal to Noise Ratio.

Now imagine you are talking to a friend in a quiet room, you are speaking at a normal level and your friend can hear you perfectly because there is little background noise and he or she can easily pick out what you are saying.

Now think about having the same conversation in the middle of a Led Zeppelin concert! You speak at the same level but it is drowned out by the background noise, your friend just can't pick up what you are saying against the backdrop.

The same (well similar) principle applies to signals sent down the cable to you, contrary to popular believe these aren't 'digital' but analogue radio frequency waveforms. Now if there is some source of interference which is injecting random 'noise' into the circuit, and if the value of this 'noise' is too high then the receiver (your hub), struggles to understand the 'signal' (what is actually valid data) against the background 'noise' value. To some extent the system can try to compensate by effectively 'SHOUTING' which is what you would need to do at said Led Zeppelin concert!

But there is a limit as to how much the system can shout and still be reliably 'heard' over the noise, and to work properly the 'signal' level has to be substantially higher than the 'noise' level - so the actual power levels aren't important, it's the ratio, ie how much higher is the signal compared to the base noise level? Technically this is expressed in decibels, that being the unit concerned here, rather than a 1:5 or 1:8 etc. If you look at the stats on the Hubs, in the downstream channels you will see the SNR expressed and really anything under 35 dB and you are probably looking at trouble!

So where does the noise come from? Well the most common cause will be a bad joint or damaged cable between yourself and the street cabinet, but that will affect only you; a faulty amplifier in the street cabinet will do it and affect everyone connected to that cabinet. In this case though, as VM have acknowledged and identified an issue, then it is more likely to be a faulty component way upstream in what is called a CMTS, and it's just a case of when they have the resources to fix it.

 

djgeurn
On our wavelength
In response to Beth_G

on ‎18-01-2023 17:15

Here's the latest info from the router

3.0 Upstream channels

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

14960000037.2705995120 KSym/sec16QAM1
22360000035.7705995120 KSym/sec16QAM9
34310000036.7705995120 KSym/sec16QAM2
43660000036.2705995120 KSym/sec16QAM3
53010000036.2705995120 KSym/sec16QAM4



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA00360
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
5US_TYPE_STDMA0000



3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
1010.433.02KQAM8


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
10OFDMA20853.400

 

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
51707500003.50000040.366287QAM2565
11387500003.79999940.946209QAM2561
21467500003.79999940.946209QAM2562
31547500003.79999940.946209QAM2563
41627500003.70000140.946209QAM2564
61787500003.40000240.946209QAM2566
71867500003.50000040.946209QAM2567
81947500003.50000040.946209QAM2568
92027500003.50000040.946209QAM2569
102107500003.50000040.366287QAM25610
112187500003.50000040.946209QAM25611
122267500003.40000240.946209QAM25612
132347500003.40000240.366287QAM25613
142427500003.29999940.366287QAM25614
152507500003.29999940.366287QAM25615
162587500003.40000240.946209QAM25616
172667500003.70000140.946209QAM25617
182747500004.00000040.366287QAM25618
192827500003.59999840.366287QAM25619
202907500003.09999840.946209QAM25620
212987500002.70000140.366287QAM25621
223067500002.79999940.366287QAM25622
233147500002.90000240.366287QAM25623
243227500002.90000238.983261QAM25624
253307500002.29999938.983261QAM25625
263387500002.29999940.366287QAM25626
273467500002.00000038.983261QAM25627
283547500001.90000238.605377QAM25628
293627500001.79999938.605377QAM25629
303707500001.70000138.983261QAM25630
313787500001.70000138.983261QAM25631



 
0 Kudos
Top