cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

Are my Virgin Modem Stats okay? (Recently had many T3 time outs and some T4)

Naylor2006
On our wavelength

Hi I was hoping the knowledge on here could help me out because I have tried to speak to technical support on the phone and the less said the better about that.

My Hub 3.0 is in modem mode and I use my own router and wifi mesh, however I can confirm that neither router or wifi at at fault here, something the phone folks dont get πŸ˜•

Over the last few weeks my connection has progressively been dropping, logs show T3 time outs and T4 errors, alot of the time the connection just comes back but sometimes the router crashes and I cannot access it via its IP 192.168.100.1, I have to reboot it.

On some of the occasions I am seeing 1000's of Pre RS errors even more Post RS errors, I understand that these mean and Pre can be ok as they are solved but Post means dropped packets and bad news. All of this can be related to noise or power etc. Also it seems to me that these errors come in bursts, like that can stay on the same numbers for ages then suddenly ramp up.

Yesterday around 7pm (02/08/23) I disconnected everything inside and reseated it all and since then the connection has been steady apart from one drop around 5am this morning. I dont know if thats a big deal and can be expected from time to time but below are my stats, I was hoping someone would be kind enough to let me know if they are all in spec.

Thank you

9 REPLIES 9

Naylor2006
On our wavelength
Cable Modem Status 
ItemStatusComments 
Acquired Downstream Channel (Hz)331000000Locked 
Ranged Upstream Channel (Hz)36600000Locked 
Provisioning StateOnline  

Downstream bonded channels     
ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
13310000006.340256 qam25
22350000005.340256 qam13
3243000000540256 qam14
42510000004.640256 qam15
52590000004.840256 qam16
62670000005.338256 qam17
72750000005.540256 qam18
82830000005.940256 qam19
9291000000640256 qam20
10299000000640256 qam21
113070000006.140256 qam22
123150000006.340256 qam23
13323000000640256 qam24
143390000006.440256 qam26
153470000006.340256 qam27
16355000000640256 qam28
17363000000640256 qam29
183710000005.640256 qam30
19379000000540256 qam31
203870000004.640256 qam32
213950000004.540256 qam34
224030000004.640256 qam35
234110000004.940256 qam36
244190000004.440256 qam37

Downstream bonded channels    
ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
1Locked40.9390
2Locked40.380
3Locked40.9150
4Locked40.9170
5Locked40.9170
6Locked38.9120
7Locked40.3160
8Locked40.9110
9Locked40.350
10Locked40.3350
11Locked40.9310
12Locked40.3350
13Locked40.9370
14Locked40.3470
15Locked40.9410
16Locked40.3410
17Locked40.9390
18Locked40.9400
19Locked40.3500
20Locked40.9210
21Locked40.3240
22Locked40.9220
23Locked40.9100
24Locked40.3170

Upstream bonded channels     
ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
13660000035.8512064 qam3
23010000035.5512064 qam4
34310000036512064 qam2
44960000036.8512064 qam1
52360006835.3512064 qam9
      
      
Upstream bonded channels     
ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0010
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0000

General Configuration 
Network accessAllowed
Maximum Number of CPEs1
Baseline PrivacyEnabled
DOCSIS ModeDocsis30
Config filecmreg-vmdg505-bbt062-b.cm
  
  
Primary Downstream Service Flow 
SFID22980
Max Traffic Rate402500089
Max Traffic Burst42600
Min Traffic Rate0
  
  
Primary Upstream Service Flow 
SFID22979
Max Traffic Rate38500089
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

Here's an example of some of the errors pre-reseating everything: (No T4 errors are there to see sorry)

Network Log  
TimePriorityDescription
02/08/2023 13:49:01criticalNo Ranging Response received - T3 time-out;CM-MAC
02/08/2023 02:55:28Warning!RCS Partial Service;CM-MAC
01/08/2023 23:19:49criticalNo Ranging Response received - T3 time-out;CM-MAC
01/08/2023 23:01:58Warning!RCS Partial Service;CM-MAC
01/08/2023 22:46:14criticalNo Ranging Response received - T3 time-out;CM-MAC
01/08/2023 22:23:32Warning!RCS Partial Service;CM-MAC
01/08/2023 20:10:21criticalNo Ranging Response received - T3 time-out;CM-MAC
01/08/2023 18:52:33Warning!RCS Partial Service;CM-MAC
01/08/2023 18:52:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC
01/08/2023 18:52:30Warning!RCS Partial Service;CM-MAC
01/08/2023 18:52:30criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC
01/08/2023 18:36:54Warning!RCS Partial Service;CM-MAC
01/08/2023 18:36:54criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC
01/08/2023 18:33:40Warning!RCS Partial Service;CM-MAC
01/08/2023 17:04:47criticalNo Ranging Response received - T3 time-out;CM-MAC
01/08/2023 17:04:47criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC
01/08/2023 17:04:47criticalRanging Request Retries exhausted;CM-MAC
01/08/2023 17:04:09criticalNo Ranging Response received - T3 time-out;CM-MAC

 

Adduxi
Very Insightful Person
Very Insightful Person

Stats look fine, but far too many T3's being reported.  Looks like noise on the circuit?

Setup a BQM and post the results after 24Hours running.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

Naylor2006
On our wavelength

b6d1745da98c2844a7485ff40516fd0fa665d68f-03-08-2023.png

Actually I had one running already, attached is the last 24 hours, btw right now as you can see my connection is under heavy load, I am working and downloading alot of content.

The red line at around 3PM yesterday was my testing a new cable and that just signifies where I took it down. The really big red line in the evening around 8PM is where I shut everything off and reseated everything, since that time I have not manually reset anything, the red around 5am this morning was a drop, I was working at this time and noticed it.

The logs on the router though have not shown any T3's for a while now, none since the reseating although one is logged in the upstream table for channel 1 it is not logged in the network log.

Hi Naylor2006,

Thank you for reaching out to us in our community and welcome back, thank you for the update around what you have done to try to improve things, as there does look to be an improvement since we advise keeping an eye on it over the weekend and post the new results then.

Regards

Paul.