Menu
Reply
Moriturus
  • 3
  • 0
  • 0
Joining in
113 Views
Message 1 of 6
Flag for a moderator

Router restarting after each 24h (00:00-00:30) - logs included

Hi. Im fresh user of Virgin Broadband and I can say that my "relation" with Virgin router are not so good. I think this small black box have some bad feelings to me 🙂

From start I have issues with stability of connection. Speed was (and still is) good, but router is more delicate then egg. Any movement with cable, router, connecting/disconnecting network cables - can put it into state.. hm.. something between restart and loading default settings. Throw a coin and you can find results. Also restart are looong (comparing to routers used by e.g.BT) Sometimes it taking up to 20min before router decide to start all services.
After first two weeks and putting some "DMZ zone" for any movement around router all issues was gone. Until last few days I found new issue. Router is restarting after midnight. Each day.

I try find solution in network but on each post fist respond is - put some logs. So I will start with them:


Cable Modem Status
ItemStatusComments
Acquired Downstream Channel (Hz)

203000000

Locked

Ranged Upstream Channel (Hz)

60300000

Locked

Provisioning State

Online

 

 

Downstream bonded channels     
ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
1203000000238256 qam9
2139000000-3.237256 qam1
3147000000-1.437256 qam2
4155000000-0.538256 qam3
5163000000-1.738256 qam4
6171000000-0.238256 qam5
71790000001.540256 qam6
8187000000-0.738256 qam7
9195000000-138256 qam8
102110000002.438256 qam10
11219000000-1.238256 qam11
12227000000-138256 qam12
132350000003.538256 qam13
142430000003.538256 qam14
15251000000-0.538256 qam15
16259000000-0.238256 qam16
172670000004.938256 qam17
182750000005.538256 qam18
192830000000.738256 qam19
20291000000038256 qam20
212990000004.338256 qam21
223070000005.438256 qam22
23315000000238256 qam23
243230000000.238256 qam24

 

Downstream bonded channels    
ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
1Locked38.950
2Locked37.6530
3Locked37.6100
4Locked38.940
5Locked38.9100
6Locked38.640
7Locked40.310
8Locked38.9120
9Locked38.9240
10Locked38.9190
11Locked38.6220
12Locked38.9110
13Locked38.960
14Locked38.920
15Locked38.6240
16Locked38.6190
17Locked38.6220
18Locked38.6130
19Locked38.6260
20Locked38.9200
21Locked38.690
22Locked38.610
23Locked38.6180
24Locked38.9320

 

Upstream bonded channels     
ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
16030000051512064 qam1
      
      
Upstream bonded channels     
ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0000

 

General Configuration 
Network access

Allowed

Maximum Number of CPEs

1

Baseline Privacy

Enabled

DOCSIS Mode

Docsis30

Config file

cmreg-vmdg505-bbt053-b.cm

  
  
Primary Downstream Service Flow 
SFID24942
Max Traffic Rate575000000
Max Traffic Burst42600
Min Traffic Rate0
  
  
Primary Upstream Service Flow 
SFID24941
Max Traffic Rate38520000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort

 

Network Log  
TimePriorityDescription
20/01/2021 00:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/01/2021 00:12Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/01/2021 00:12Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2021 00:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2021 00:38Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2021 00:38Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2021 00:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2021 00:17Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2021 00:17Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2021 01:04criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2021 00:49Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2021 00:49Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2021 00:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 00:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 00:33noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 00:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 00:32Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 00:32Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2021 00:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2021 00:15Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Also I think I need to add information that when I move to this house - Virgin decided that home have active connection and I dont need engineer visit. 
When I connecting router I found old box from Telewest Broadband company. Cable is cable and port is port so self-installation was possible. Then all fun with router started. 

Can anyone from community can read that information and put some light on this case? I dont want to call to Virgin Help if there is something trivial on my network what I can fix by e.g. replacing cable or power extension or increase "DMZ zone" 😛

0 Kudos
Reply
Moriturus
  • 3
  • 0
  • 0
Joining in
101 Views
Message 2 of 6
Flag for a moderator

Re: Router restarting after each 24h (00:00-00:30) - logs included

Also I create BQM as I see its very popular here 

 

My Broadband Ping

0 Kudos
Reply
carl_pearce
  • 4.73K
  • 402
  • 706
Superstar
96 Views
Message 3 of 6
Flag for a moderator
Helpful Answer

Re: Router restarting after each 24h (00:00-00:30) - logs included

Your downstream power levels are all over the place. They should be pretty consistent.

You also only have one upstream channel when you should have at least two (four in most areas).

0 Kudos
Reply
gary_dexter
  • 28.88K
  • 1.76K
  • 3.78K
Alessandro Volta
92 Views
Message 4 of 6
Flag for a moderator
Helpful Answer

Re: Router restarting after each 24h (00:00-00:30) - logs included

And you’ll need an engineer to rectify 


*****
If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!!
I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences.
Office 365, Dynamics CRM and Cloud Computing Jedi
0 Kudos
Reply
Moriturus
  • 3
  • 0
  • 0
Joining in
78 Views
Message 5 of 6
Flag for a moderator

Re: Router restarting after each 24h (00:00-00:30) - logs included

Thank you for respond. 
Now is question - do with that info (logs from router) I can report fault or I need get ready with my wallet for some bill for engineer visit?

0 Kudos
Reply
carl_pearce
  • 4.73K
  • 402
  • 706
Superstar
75 Views
Message 6 of 6
Flag for a moderator

Re: Router restarting after each 24h (00:00-00:30) - logs included


@Moriturus wrote:

Thank you for respond. 
Now is question - do with that info (logs from router) I can report fault or I need get ready with my wallet for some bill for engineer visit?


There will be no charge for a call-out.

It's a problem with VM's infrastructure.

0 Kudos
Reply