Menu
Reply
  • 37
  • 1
  • 8
mbulliva
On our wavelength
244 Views
Message 1 of 5
Flag for a moderator

Errors in Hub 3.0 Network Log

I am getting errors in the network log and I experience disconnections.  Does this mean the router is trying to upgrade from firmware 610 to 613 and failing or is it something else?

Network Log

Time Priority Description

11/06/2019 11:16:55criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2019 11:20:48Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2019 11:20:48Warning!MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2019 11:21:3criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2019 11:29:1criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2019 11:29:1critical16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2019 11:29:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/06/2019 11:27:26criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/06/2019 11:28:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/06/2019 23:22:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2019 04:10:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2019 04:38:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2019 11:08:50Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2019 13:57:0Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2019 19:32:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/06/2019 10:11:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/06/2019 10:17:28criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/06/2019 10:18:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2019 01:03:17Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2019 01:08:40criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
  • 37
  • 1
  • 8
mbulliva
On our wavelength
243 Views
Message 2 of 5
Flag for a moderator

Re: Errors in Hub 3.0 Network Log

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1299000000-138256 qam21
2203000000-1.740256 qam9
3211000000-1.738256 qam10
4219000000-1.940256 qam11
5227000000-1.938256 qam12
6235000000-238256 qam13
7243000000-2.240256 qam14
8251000000-2.238256 qam15
9259000000-2.440256 qam16
10267000000-2.238256 qam17
11275000000-238256 qam18
12283000000-1.740256 qam19
13291000000-1.440256 qam20
14307000000-1.240256 qam22
15315000000-3.437256 qam23
16323000000-638256 qam24
17443000000-2.540256 qam25
18451000000-2.740256 qam26
19459000000-340256 qam27
20467000000-2.938256 qam28
21475000000-2.740256 qam29
22483000000-2.740256 qam30
23491000000-2.740256 qam31
24499000000-2.540256 qam32



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.91013
2Locked40.390
3Locked38.990
4Locked40.350
5Locked38.9110
6Locked38.970
7Locked40.380
8Locked38.970
9Locked40.330
10Locked38.970
11Locked38.990
12Locked40.380
13Locked40.370
14Locked40.3190
15Locked37.3110
16Locked38.9250
17Locked40.300
18Locked40.390
19Locked40.380
20Locked38.970
21Locked40.370
22Locked40.330
23Locked40.3180
24Locked40.310

 

Upstream bonded channels

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

1326000005.1512064 qam3
2462000005.1512064 qam1
3258000385.1512064 qam4
4394000005.1512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
  • 5.67K
  • 437
  • 944
Tudor
Hero
226 Views
Message 3 of 5
Flag for a moderator

Re: Errors in Hub 3.0 Network Log

Upstream power levels are too high, all other stats are fine. You need technician to visit to rectify. Call customer services and report the problem. The logs do not indicate a router firmware upgrade. 


There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal
  • 37
  • 1
  • 8
mbulliva
On our wavelength
75 Views
Message 4 of 5
Flag for a moderator

Re: Errors in Hub 3.0 Network Log

I rang up 150 and after checking, I was told the power levels are within acceptable limites, however, my Hub 3 resets several times a day still and the power levels remain the same.

Upstream bonded channels 

ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
1258000005.1512064 qam4
2462000005.1512064 qam1
3326000005.1512064 qam3
4394000005.1512064 qam2
0 Kudos
Reply
  • 11.58K
  • 1.06K
  • 2.49K
griffin
Alessandro Volta
57 Views
Message 5 of 5
Flag for a moderator

Re: Errors in Hub 3.0 Network Log

Your upstream power levels are still at max transmit and need VM to take a closer look.

The logs are showing occasional dropouts of VM's connection, but not several times a day, so you may have a wireless dropout problem as well.
Do wired devices dropout at the same time, or does the Hub's lights change behaviour.

Due to the poor service you have received from the call centre, I would wait for a Forum Team member to pick up the thread and arrange for a closer inspection of your connection, or you could try ringing again and hope you get a better agent.

0 Kudos
Reply