Menu
Reply
  • 8
  • 0
  • 0
Gyro85
Joining in
64 Views
Message 11 of 15
Flag for a moderator

Re: Problems with Hub 3.0

Hi,

I'm still experiencing issues daily and just had to reboot router again appears to have a considerable amount of critical and warnings continually being logged

Time Priority Description

2018-12-05 21:08:54.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:56.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:56.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:56.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:56.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:56.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:56.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:57.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:57.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:08:59.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:00.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:00.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:01.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:01.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:02.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:03.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:07.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:11.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:20.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-05 21:09:58.00criticalReceived 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
  • 8
  • 0
  • 0
Gyro85
Joining in
60 Views
Message 12 of 15
Flag for a moderator

Re: Problems with Hub 3.0

Downstream bonded channels

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

14430000001.438256 qam5
2651000000-0.738256 qam27
3643000000-0.438256 qam26
4635000000-0.538256 qam25
5595000000-1.238256 qam24
6587000000-1.538256 qam23
7579000000-1.538256 qam22
8571000000-0.538256 qam21
9563000000-0.238256 qam20
10555000000-0.538256 qam19
11547000000-0.538256 qam18
12539000000-0.238256 qam17
135310000000.438256 qam16
145150000000.438256 qam14
155070000000.238256 qam13
16491000000138256 qam11
174830000001.238256 qam10
18659000000-0.938256 qam28
195230000000.538256 qam15
204990000000.738256 qam12
214750000000.938256 qam9
224670000000.938256 qam8
234590000001.238256 qam7
244510000001.238256 qam6



Downstream bonded channels

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

1Locked38.650
2Locked38.940
3Locked38.960
4Locked38.680
5Locked38.6100
6Locked38.640
7Locked38.630
8Locked38.950
9Locked38.970
10Locked38.670
11Locked38.630
12Locked38.9120
13Locked38.680
14Locked38.630
15Locked38.640
16Locked38.970
17Locked38.670
18Locked38.9130
19Locked38.970
20Locked38.650
21Locked38.960
22Locked38.960
23Locked38.640
24Locked38.950

 

 

Upstream bonded channels

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

14580000047.3512016 qam1
25370000047.3512016 qam4
33580000047.5512016 qam2
42740000048512016 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
  • 21.6K
  • 612
  • 3.56K
Sephiroth
Alessandro Volta
56 Views
Message 13 of 15
Flag for a moderator

Re: Problems with Hub 3.0

Thing is, your stats were taken after the reset. Not much you can do about that because of the T4 Timeout which forces a reset, after which stats are fine till it glitches again.

The VM bods might be able to see something on the logs for the CMTS.

Seph - ( DEFROCKED - My advice is at your risk)

0 Kudos
Reply
  • 8
  • 0
  • 0
Gyro85
Joining in
31 Views
Message 14 of 15
Flag for a moderator

Re: Problems with Hub 3.0

Just been locked out again, managed to get on router before it collapsed

Time Priority Description
2018-12-06 19:34:52.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:34:52.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:35:03.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:35:03.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:35:20.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:35:20.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:36:03.00 critical Received 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;
2018-12-06 19:40:05.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:05.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:07.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:15.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:16.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:16.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:16.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:40:16.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:41:07.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:41:33.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:41:33.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:41:33.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-06 19:41:45.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 45800000 47.3 5120 16 qam 1
2 53700000 47.3 5120 16 qam 4
3 35800000 47.5 5120 16 qam 2
4 27400000 48 5120 16 qam 3


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 2 0
3 ATDMA 0 0 2 0
4 ATDMA 0 0 0 0

Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz)
Updating..
Locked
Ranged Upstream Channel (Hz)
45800000
Locked
Provisioning State
Online

Didnt show me any downstream information and just updating

Can a mod please action as getting reallyu frustrated through lack of service at key times

 

 

 

0 Kudos
Reply
  • 143
  • 2
  • 37
carnivalist
Superfast
27 Views
Message 15 of 15
Flag for a moderator

Re: Problems with Hub 3.0


Can a mod please action as getting reallyu frustrated through lack of service at key times

 

 

 


Join the club. I've been waiting months for a reliable service. Fortunately I was able to take advantage of a steal of an offer on a 40GB monthly MIFi deal from Three, so at least I've been able to use that when my Superhub turns back into Clark Kent. Unfortunately that deal isn't available any more and as far as I can see at the moment no other companies have cheap MiFi deals either. I don't know if Virgin Mobile allow tethering, as that would be a fallback. They didn't when I was a Virgin Mobile victim (I hesitate to use the word "customer") but that may have changed.

Given what appears to be the advent of chronic problems on their network, Virgin Media really should be following a competitor's lead and offering free MiFi to customers affected by broadband outages.

0 Kudos
Reply