Menu
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
93 Views
Message 1 of 7
Flag for a moderator

Massive upstream-only packet loss this AM

 

Port	Frequency (Hz)	Modulation	Power (dBmV)	SNR (dB)	Channel
1	203000000	256QAM	12.700	40.946	9
2	139000000	256QAM	12.800	40.366	1
3	147000000	256QAM	12.700	40.366	2
4	155000000	256QAM	12.500	40.946	3
5	163000000	256QAM	12.500	40.946	4
6	171000000	256QAM	12.400	40.366	5
7	179000000	256QAM	12.600	40.366	6
8	187000000	256QAM	12.500	40.366	7
9	195000000	256QAM	12.800	40.366	8
10	211000000	256QAM	12.800	40.946	10
11	219000000	256QAM	12.800	40.946	11
12	227000000	256QAM	12.900	40.366	12
13	235000000	256QAM	12.700	40.946	13
14	243000000	256QAM	12.800	40.946	14
15	251000000	256QAM	12.500	40.366	15
16	259000000	256QAM	12.600	40.946	16
17	267000000	256QAM	12.600	40.366	17
18	275000000	256QAM	12.400	40.366	18
19	283000000	256QAM	12.400	40.366	19
20	291000000	256QAM	12.800	40.366	20
21	299000000	256QAM	13.000	40.366	21
22	307000000	256QAM	13.100	40.366	22
23	315000000	256QAM	12.900	40.366	23
24	323000000	256QAM	13.200	40.366	24

 

 

Upstream Overview

Port Frequency (Hz) BandWidth Modulation Power (dBmV) Channel

1394000006400000ATDMA36.7504
2462000006400000ATDMA34.7503
3537000006400000ATDMA35.2502
4603000006400000ATDMA34.7501

 

Docsis Logs
No. Time Type Priority Event
111/05/20 08:08:0682000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
211/05/20 08:08:0782000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
311/05/20 08:13:4682000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
411/05/20 08:13:4682000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
511/05/20 08:15:0682000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
611/05/20 08:15:0682000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
711/05/20 08:17:4682000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
811/05/20 08:17:4682000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
911/05/20 08:24:0582000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1011/05/20 08:24:0582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1111/05/20 08:24:2582000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1211/05/20 08:24:2582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1311/05/20 08:25:4582000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1411/05/20 08:25:4582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1511/05/20 08:27:0582000700criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1611/05/20 08:27:0582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
1701/01/70 00:02:1168000401warningToD request sent - No Response received;CM-MAC=x;CMTS-MAC=x:ea;CM-QOS=1.1;CM-VER=3.0;
1811/05/20 10:23:2590000000warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x;CMTS-MAC=x:ea;CM-QOS=1.1;CM-VER=3.0;
1911/05/20 10:23:5673040100noticeTLV-11 - unrecognized OID;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
2011/05/20 10:38:2582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;

 

Any ideas? Packet loss upstream (up to 100%) is for 10 seconds on 30 second intervals.

--- 8.8.4.4 ping statistics ---
93 packets transmitted, 39 received, +3 errors, 58.0645% packet loss, time 94380ms
rtt min/avg/max/mdev = 13.846/19.582/53.559/6.678 ms

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
92 Views
Message 2 of 7
Flag for a moderator

Re: Massive upstream-only packet loss this AM

Tried restarting router at 8:30am but being used in modem mode so not much internal network issue.
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
90 Views
Message 3 of 7
Flag for a moderator

Re: Massive upstream-only packet loss this AM

1 xxxx (172.22.16.1) 0.432 ms 0.415 ms 0.446 ms
2 192.168.1.1 (192.168.1.1) 2.580 ms 2.562 ms 4.208 ms
3 * * *
4 hari-core-2b-xe-11110-0.network.virginmedia.net (213.104.84.189) 24.860 ms * *
5 * * *
6 * * *
7 * cpc69435-hink4-2-0-cust104.8-2.cable.virginm.net (62.252.5.105) 34.981 ms 74.125.118.144 (74.125.118.144) 37.655 ms
8 * * *
9 dns.google (8.8.4.4) 31.070 ms 36.836 ms 35.103 ms

0 Kudos
Reply
Highlighted
  • 1.37K
  • 107
  • 197
Knows their stuff
83 Views
Message 4 of 7
Flag for a moderator

Re: Massive upstream-only packet loss this AM

Have you checked for known network faults ? 

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
81 Views
Message 5 of 7
Flag for a moderator

Re: Massive upstream-only packet loss this AM

None showing so far today

0 Kudos
Reply
Highlighted
  • 7.69K
  • 461
  • 486
Forum Team
Forum Team
38 Views
Message 6 of 7
Flag for a moderator

Re: Massive upstream-only packet loss this AM

Hi Bobbysteel, 

Really sorry for the issues you're having and the delay in getting back in touch, we have been busier than usual. 

Are you still having these issues this evening?

I've had a look and can certainly see some errors so I've booked a tech for you, this is the next available visit we have and you'll be able to find all of the details via your online account. 
 

If the visit doesn't suit then please re arrange online and you'll also need to ensure somebody over the age of 18 is in the property at the time. 

Keep us posted with how you get on. 

Emma_C - Forum Team
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
13 Views
Message 7 of 7
Flag for a moderator

Re: Massive upstream-only packet loss this AM

There was an area outage. It eventually got fixed but way beyond the business sla.

0 Kudos
Reply