Menu
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
271 Views
Message 1 of 18
Flag for a moderator

Another "Hub4 Problems" Post

All,

I'm on the M350 package, but was offered a HUB4 to improve things in my area.  Since upgrading I've had frequent issues with the connection - all wired network so nothing WiFi related.

I'll be sat here working and my voice call will drop, or I'll notice the ring light starting to flash on the hub before it mostly sorts itself out in a couple of mins.  The uptime is never particularly high either, and it seems to be rebooting a couple of times a week - temperature doesn't seem high at all.

When things permanently drop then whilst the channels are connected the external I.P. lease seems in the past, and it's not picking up a new I.P.

My stats are as below, and whilst there are errors in some of the low number 3.0 channels I've no idea whether that is "unusual"

3.0 Downstream channels

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

51710000004.90000237.355988QAM2565
11390000005.59999837.355988QAM2561
21470000005.09999837.636276QAM2562
31550000005.50000037.636276QAM2563
41630000005.00000037.636276QAM2564
61790000005.00000037.636276QAM2566
71870000004.59999837.355988QAM2567
81950000004.80000337.636276QAM2568
92030000004.50000037.636276QAM2569
102110000004.90000238.605377QAM25610
112190000004.19999737.636276QAM25611
122270000004.40000237.636276QAM25612
132350000004.00000037.636276QAM25613
142430000003.40000237.355988QAM25614
152510000003.79999937.636276QAM25615
162590000003.59999837.636276QAM25616
172670000004.09999837.636276QAM25617
182750000004.09999837.636276QAM25618
192830000003.70000137.636276QAM25619
202910000003.50000037.636276QAM25620
212990000003.40000237.636276QAM25621
223070000003.70000138.605377QAM25622
233150000004.19999738.605377QAM25623
243230000005.19999738.605377QAM25624
253310000005.19999737.636276QAM25625
263390000005.69999738.605377QAM25626
273470000006.00000038.605377QAM25627
283550000005.59999838.983261QAM25628
293630000005.50000038.605377QAM25629
303710000005.30000338.605377QAM25630
313790000005.30000338.983261QAM25631

 

 

3.0 Downstream channelsChannel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
5Locked000
1Locked288046685168319434
2Locked29165293793152964
3Locked1076615604327510
4Locked291535652990
6Locked2906728000
7Locked2685303600
8Locked2552601100
9Locked2538903300
10Locked2520856600
11Locked2347086500
12Locked2337962000
13Locked2510178800
14Locked2502995600
15Locked2342431100
16Locked694580000
17Locked779868600
18Locked780840400
19Locked686853300
20Locked680694100
21Locked757197800
22Locked742287500
23Locked650589700
24Locked835308900
25Locked886723100
26Locked891717200
27Locked841001100
28Locked805919500
29Locked889151300
30Locked874859800
31Locked110996071700



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM2048759


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked 5.1408561500

 

Any idea whether the above needs Virgin to do anything?  Cables are tight/reseated, device reset and restarted many times & there's not a lot I can do myself.

 

0 Kudos
Reply
Highlighted
  • 11.83K
  • 925
  • 1.52K
Alessandro Volta
266 Views
Message 2 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

Upstream & Network Log ?

***********************************************************************************************************************************

Mike Robinson
Semi-Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.

My Broadband Ping - Mike Robbo
0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
264 Views
Message 3 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
259 Views
Message 4 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

3.0 Upstream channels

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

13260000045.0205995120 KSym/sec64QAM5
23940000045.2705995120 KSym/sec64QAM4
34620000045.2705995120 KSym/sec64QAM3
45370000045.5205995120 KSym/sec64QAM2



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

 

0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
256 Views
Message 5 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

Network Log

Time Priority Description

Wed 21/10/2020 19:08:453Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:09:153Received 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.1;
Wed 21/10/2020 19:10:053Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:10:343Received 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.1;
Wed 21/10/2020 19:11:253Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:11:543Received 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.1;
Wed 21/10/2020 19:12:443Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:13:143Received 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.1;
Wed 21/10/2020 19:14:043Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:14:343Received 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.1;
Wed 21/10/2020 19:15:243Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:15:543Received 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.1;
Wed 21/10/2020 19:18:185MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:18:223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:19:185Initializing 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.1;
Wed 21/10/2020 19:19:185TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:19:483Received 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.1;
Wed 21/10/2020 19:20:273Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:20:573Received 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.1;
Wed 21/10/2020 19:21:473Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:22:173Received 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.1;
Wed 21/10/2020 19:23:073Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:23:373Received 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.1;
Wed 21/10/2020 19:24:273Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:24:573Received 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.1;
Wed 21/10/2020 19:25:473Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:26:173Received 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.1;
Wed 21/10/2020 19:28:375MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:28:413No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:29:375Initializing 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.1;
Wed 21/10/2020 19:29:375TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:30:073Received 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.1;
Wed 21/10/2020 19:30:453Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:31:143Received 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.1;
Wed 21/10/2020 19:32:053Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:32:343Received 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.1;
Wed 21/10/2020 19:33:243Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:33:543Received 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.1;
Wed 21/10/2020 19:34:443Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:35:143Received 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.1;
Wed 21/10/2020 19:37:385MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:37:423No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:38:163No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:38:165TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:38:426Received REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 19:38:463Received 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.1;
Wed 21/10/2020 19:46:335MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 21/10/2020 20:36:265Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
255 Views
Message 6 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

Most of the log above are around when I reported fault and had to do a power cycle to get back online.

0 Kudos
Reply
Highlighted
  • 11.83K
  • 925
  • 1.52K
Alessandro Volta
224 Views
Message 7 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

Try a reboot to see if the Hub can renegotiate a better connection using this method ...

Switch the Hub off using the small switch on the rear of the Hub next to the power cord and pull the PSU plug from the wall socket.

Give it a good 10 minutes put the plug back in and switch the Hub back on.

Allow the Hub a few minutes to fully restart then try your connection again.

***********************************************************************************************************************************

Mike Robinson
Semi-Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.

My Broadband Ping - Mike Robbo
0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
214 Views
Message 8 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

Cheers Mike - I have power cycled a few times, but probably haven't left 10 mins before renegotiating.  I'll do this later this evening - there will be another family mutiny if the internet stops again just now 😩

0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
186 Views
Message 9 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

Followed the advice above and now (10 mins uptime) am getting

3.0 Downstream channels

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

51710000004.90000237.636276QAM2565
11390000005.50000037.355988QAM2561
21470000005.00000037.092701QAM2562
31550000005.50000037.355988QAM2563
41630000005.00000037.636276QAM2564
61790000005.00000037.636276QAM2566
71870000004.50000037.355988QAM2567
81950000004.80000337.636276QAM2568
92030000004.59999837.355988QAM2569
102110000004.80000338.605377QAM25610
112190000004.30000337.636276QAM25611
122270000004.40000237.636276QAM25612
132350000004.09999837.636276QAM25613
142430000003.50000037.636276QAM25614
152510000003.79999937.636276QAM25615
162590000003.70000137.636276QAM25616
172670000004.19999737.636276QAM25617
182750000004.19999737.636276QAM25618
192830000003.70000137.636276QAM25619
202910000003.50000037.636276QAM25620
212990000003.50000037.636276QAM25621
223070000003.90000238.605377QAM25622
233150000004.30000338.605377QAM25623
243230000005.19999738.605377QAM25624
253310000005.19999737.636276QAM25625
263390000005.80000338.605377QAM25626
273470000006.00000038.983261QAM25627
283550000005.69999738.983261QAM25628
293630000005.69999738.605377QAM25629
303710000005.30000338.605377QAM25630
313790000005.30000338.605377QAM25631



3.0 Downstream channels

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

5Locked04380
1Locked1302896637147
2Locked1234421625140
3Locked20349236421111
4Locked134151143563
6Locked1320880730
7Locked119878300
8Locked116922100
9Locked84895000
10Locked83258800
11Locked79761300
12Locked80757200
13Locked84613900
14Locked89998000
15Locked62373800
16Locked35171500
17Locked35871000
18Locked32513400
19Locked28675800
20Locked32597100
21Locked35659200
22Locked33402500
23Locked27241900
24Locked46057100
25Locked51990900
26Locked51763500
27Locked49515300
28Locked46778400
29Locked48917900
30Locked49084000
31Locked379331500



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM2048759


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked 5.228029190
0 Kudos
Reply
Highlighted
  • 19
  • 1
  • 1
On our wavelength
185 Views
Message 10 of 18
Flag for a moderator

Re: Another "Hub4 Problems" Post

3.0 Upstream channels

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

13260000045.0205995120 KSym/sec64QAM5
23940000044.7705995120 KSym/sec64QAM4
34620000044.7705995120 KSym/sec64QAM3
45370000045.2705995120 KSym/sec64QAM2



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

 

No new events currently in Network Log.

 

0 Kudos
Reply