Menu
Reply
  • 24
  • 0
  • 0
quietriot1983
Tuning in
8,058 Views
Message 1 of 22
Flag for a moderator

Hub 3 woes

Hi, 

Can't complain about my Virgin Media speeds, as I get 100Mbps+, and round about 60 during peak times.

HOWEVER. Every day (and I mean every day, I go through a 30minute-1hour period where my connection drops completely - the Hub reports 'Your unit is updating - please wait' but never does anything other than flash green Surely it can't need to update every day? If it does, why does it do it in the middle of the afternoon or evening?. A switch off and on sometimes cures it, but often the connection status says 'Registration failure'.

I have hard reset my Hub 3, but the issues persists. Annoying seeing as it's normally when you've just started streaming a film, or started an online gaming session.

Any advice greatly appreciated

0 Kudos
Reply

Helpful Answers
  • 14.38K
  • 640
  • 1.45K
Moderator
Moderator
9,129 Views
Message 13 of 22
Flag for a moderator
Helpful Answer

Re: Hub 3 woes

Hi Quietriot1983,

 

Based on the timestamps of the errors it's unlikely to be maintenance as this is usually carried out in the early hours of the morning. 

It would be worth getting a technician out to check everything over based on these error messages so I've just sent you a private message to arrange the best time for this.


The do's and don'ts. Keep the community welcoming for all. Follow the house rules



All Replies
  • 10.92K
  • 237
  • 2.01K
Superuser
Superuser
8,031 Views
Message 2 of 22
Flag for a moderator

Re: Hub 3 woes


quietriot1983 wrote:   ...the Hub reports 'Your unit is updating - please wait' but never does anything other than flash green Surely it can't need to update every day?
......Any advice greatly appreciated

Just another "misnomer" in the Hub3. You can check if it's a genuine Firmware update from the Network Log as the stanza's will include SW INIT, FAILURE, INVALID etc..

The Internet LED flashing indicates the Hub is trying to re-range (probably due to RF impairments on upstream). Post your full SHub stats RouterStatus > Downstream, Upstream (not BurstProfile) and the obligatory NetworkLog!

ForumTeam response 2-4 days.

Regards Tony
"Life is a Binary Inspired Turing Computed Hologram"(don't PM or @Mention me - in case ignoring you offends)
0 Kudos
Reply
  • 24
  • 0
  • 0
quietriot1983
Tuning in
7,986 Views
Message 3 of 22
Flag for a moderator

Re: Hub 3 woes

2016-03-13 17:26:44.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-13 17:27:56.00	68000100	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:38.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-17 14:27:10.00	68010100	DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-18 01:24:52.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-18 03:07:19.00	68010100	DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-18 15:47:31.00	68010400	DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:14:04.00	84000500	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:14:06.00	84020200	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:14:15.00	84000500	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:15:40.00	84000700	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:15:40.00	84000500	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:16:05.00	82000400	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;
2016-03-19 22:16:37.00	84020200	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:16:37.00	84020300	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-19 22:16:51.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:33.00	84020200	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:33.00	84020300	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:47.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:02:50.00	68000100	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 10.92K
  • 237
  • 2.01K
Superuser
Superuser
7,973 Views
Message 4 of 22
Flag for a moderator

Re: Hub 3 woes

You've got some serious (probably upstream) RF impairments and fwiw I've escalated to @ForumTeam. That may still a couple of days more to respond but you can ring 150/0345 454 1111 instead? (let us know the outcome if you do as ForumTeam will eventually follow up if you don't get a satisfactory solution). In meantime I would suggest a Factory Reset using the external recessed RESET button for >30secs until the lights flash and it reboots.(don't bother with software FR via advanced settings). Check all F connectors are at least finger tight on patch cables tween wall box and hub including any splitters you may have for Tivo/TV STB. You can also post the remaining Upstream/Downstream stats. Otherwise likely need a tech visit anyway but FR'ing your hub will allow him to replace it if he finds no obvious error. (May also be network upgrade work). good luck...
Regards Tony
"Life is a Binary Inspired Turing Computed Hologram"(don't PM or @Mention me - in case ignoring you offends)
0 Kudos
Reply
  • 24
  • 0
  • 0
quietriot1983
Tuning in
7,964 Views
Message 5 of 22
Flag for a moderator

Re: Hub 3 woes

Thanks Tony, all connections seem tight enough. And FR done, will monitor over next day or so.

As an aside, could the problem stem from the fact the NYNEX (!) box outside the house and the white box inside the house have been here since before I moved in 6 years ago?

0 Kudos
Reply
  • 10.92K
  • 237
  • 2.01K
Superuser
Superuser
7,959 Views
Message 6 of 22
Flag for a moderator

Re: Hub 3 woes

Had any major lightning storms or mains power brownouts/surges? Only likely item is the isolator(in interior wall box) which a competent tech will examine/replace if he doesn't find anything obvious and certainly  if it's still got the legacy analog Radio/FM/TV ports included.

Coax Cable itself is good (undisturbed) for 25-40 years or longer! Joint's, connections (and naive users DIY screw type F connectors) are usual sources other than co-lateral utility excavations etc......... and vandalised street cabinets,,,, Smiley Sad
I had to ask my area AFM to re-pull my cable last Nov only because some passing school kid had wedged his penknife down the pavement "T"!
Shame really that only 48v-68v AC/DC allowed on coax shielding for in inline actives/amp extenders.....

I would personally have made it 440V and cremated the little ba.stard ...  Smiley Tongue 

Regards Tony
"Life is a Binary Inspired Turing Computed Hologram"(don't PM or @Mention me - in case ignoring you offends)
0 Kudos
Reply
  • 13.02K
  • 372
  • 1.06K
Moderator
Moderator
7,932 Views
Message 7 of 22
Flag for a moderator

Re: Hub 3 woes

Hi quietriot1983,

 

Thanks for getting in touch and apologies for the connection troubles, looks like Tony has been a great source of advice already.

 

I've run a few checks on your service from this end and no obvious RF problems or other isolated issues are currently showing up against your Hub.

 

The loss of sync reported in your logs from around 22:15 on the 19/03 looks to have been cable wide and may have been related to some reseg work that 's been going on in the area for the past few days, looks like there's a little more to go today and tomorrow, however as it's not linked to your cable the impact, if any, should be minimal.

 

I'd suggest we monitor the connection over the next couple of days and should the loss of sync problems continue we'll arrange for an engineer to call and take a closer look.

 

Cheers

 

 

Ralph_R
Forum Moderator

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply
  • 24
  • 0
  • 0
quietriot1983
Tuning in
7,921 Views
Message 8 of 22
Flag for a moderator

Re: Hub 3 woes

Thanks Ralph, I haven't noticed it happening since saturday night, although it may have happened when I've not been there, is there anything specific in the logs I should look for to see if it has happened?

0 Kudos
Reply
  • 13.02K
  • 372
  • 1.06K
Moderator
Moderator
7,882 Views
Message 9 of 22
Flag for a moderator

Re: Hub 3 woes

Hi quietriot1983,

 

Sounds like good news, you'll see any dropped connection in the logs with perhaps an error mentioning a loss of sync or reconnection event with the time your IP address was leased.

 

If there are few entries in general then happy daysSmiley Happy

 

Speak soon.

 

 

Ralph_R
Forum Moderator

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply
  • 24
  • 0
  • 0
quietriot1983
Tuning in
7,837 Views
Message 10 of 22
Flag for a moderator

Re: Hub 3 woes

Same old, same old. Becoming a real pain now. Last night, streaming TV, sudden loss. "Your unit is updating" "DS Scanning" and a new one "Now configuring your new wifi settings" (I changed nothing!!) - an hour later I sacked it off and went to bed. Really annoying and just not good enough tbh. Not helped by the really clunky UI on the hub, it's nigh on unusable at times and only adds to the frustration factor of not receiving the service you're paying for.

Date And Time
Error Number
Event Description
2016-03-28 20:46:21.00
84000700
RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:46:21.00
84000500
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:46:47.00
82000400
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;
2016-03-28 20:47:21.00
84020200
Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:47:21.00
84020300
MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:47:34.00
82000200
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:50:29.00
84020200
Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:50:29.00
84020300
MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:50:42.00
82000200
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:53:28.00
84020200
Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:53:28.00
84020300
MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:53:42.00
82000200
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:58:06.00
84020200
Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:58:06.00
84020300
MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:58:20.00
82000200
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:59:24.00
68000100
DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:03:45.00
84020200
Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:03:45.00
84020300
MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:03:59.00
82000200
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:05:06.00
68000100
DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-
Date And Time Error Number Event Description
2016-03-28 20:58:06.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:58:20.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 20:59:24.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:03:45.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:03:45.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:03:59.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:05:06.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:08:10.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:08:10.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:08:23.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:33.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:33.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:47.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:02:51.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:05:31.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:05:31.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:05:45.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:06:50.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-03-28 21:19:19.00 69010200 SW Download INIT - Via Config file
2016-03-28 21:26:59.00 69011200 SW download Successful - Via Config file
0 Kudos
Reply