30M : Superhub problems

[IvIaXiIvIuS]

Recently started having problem with the superhub dropping connection,i've done all the basic checks such as virus scan ect to make sure its not my machine thats at fault.
Times vary throughout the day but its mainly in the mornings its happening(not always logged on the superhub event log page)

power levels:
Downstream ChannelsLock StatusModulationChannel IDMax Raw Bit RateFrequencyPowerSNRDocsis/EuroDocsis lockedLockedQAM2567855616000 Kbits/sec299000000 Hz2.7 dBmV42.3 dBHybridLockedQAM2567955616000 Kbits/sec307000000 Hz2.3 dBmV41.9 dBHybridLockedQAM2568055616000 Kbits/sec315000000 Hz2.2 dBmV41.9 dBHybrid

Upstream ChannelsLock StatusModulationChannel IDMax Raw Bit RateFrequencyPowerLockedATDMA420480 Kbits/sec45800000 Hz52.2 dBmV


Thu Apr 21 14:23:02 2011 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Thu Apr 21 14:22:44 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Thu Apr 21 14:22:12 2011 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Thu Apr 21 14:20:07 2011 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0; Tue Apr 19 17:46:02 2011 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Tue Apr 19 17:45:56 2011 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Tue Apr 19 17:45:53 2011 Warning (5) Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Tue Apr 19 17:45:53 2011 Warning (5) MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Tue Apr 19 17:45:44 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0; Mon Apr 18 00:43:46 2011 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Sat Apr 16 22:15:01 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0; Sat Apr 16 04:31:44 2011 Warning (5) ToD request sent - No Response received;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 16 04:31:42 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Sat Apr 16 04:31:28 2011 Warning (5) ToD request sent - No Response received;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Fri Apr 15 05:54:56 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Fri Apr 15 02:54:09 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:12:da:28:38:01;CM-QOS=1.0;CM-VER=3.0; Fri Apr 15 02:53:43 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 13 12:18:03 2011 Critical (3) REG RSP not received;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 13 12:18:03 2011 Error (4) T6 Timeout and retries exceeded;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Tue Apr 12 13:45:21 2011 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0; Tue Apr 12 12:22:20 2011 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0; Tue Apr 12 12:22:20 2011 Critical (3) TFTP failed - Request sent - No Response;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0; Tue Apr 12 01:10:17 2011 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.1;CM-VER=3.0; Tue Feb 08 15:45:19 2011 Critical (3) Resetting the cable modem due to docsDevResetNow Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:23:5e:6f:c6:b6;CM-QOS=1.0;CM-VER=3.0;
thought i'd post on here before i spent hours on the phone being told its my machine

[Stephen]

Is it wired or wireless thats dropping?

If wireless what channel have you got the superhub on.

[IvIaXiIvIuS]

wired,sorry meant to add that in the previous post
running on 10/100 full duplex too(double checked)

[SimonZA]

I am having the exact same problem. I also notice it in the mornings, though I think it is just the fact that that is when we first notice it. I have noticed it now today, since I am at home. I have a complete network failure, i.e. I cannot even access the router admin page. I have to reboot the router. This affects 2 of my wired PCs, I am unsure if it affects wireless yet.

[Mick Fisher]

I had to dump my network and start again from scratch after introducing the superdud. It worked for a day or so then the wireless problems started, the dropped internet problems started, software firewalls went haywire, you name it, it happened. Complete melt down.

So IMO you might be able to save yourself some headscratching by starting again rather than trying to solve the LAN problems.

The superdud wireless is inherently weak and the auto setting doesn't seem to work. Manually optimising channels with the aid of an app like InSSider helps as does switching the 802.11 mode to 145mbps.

Heavy activity on the LAN can cause it to reboot, mine reboots itself up to 3 times a day completely spontaneously.

[Chrysalis]

I have a adsl gigabit router been used for my lan traffic as a switch.

If you guys still have the dir615 I suggest using that for lan traffic even tho its only 100mbit it at least wont keep rebooting.

[IvIaXiIvIuS]

Just got off the phone with Virgin,new superhub in the post.According to the guy on the phone its a common issue and they are getting through hubs hand over fist.

Thanks for the help,will probably post again in a few weeks when the new one gives up the ghost too

[Kymmy]

CM-MAC's removed from original post
Please avoid posting modem MACs in the future

[SimonZA]

Originally Posted by IvIaXiIvIuS

Just got off the phone with Virgin,new superhub in the post.According to the guy on the phone its a common issue and they are getting through hubs hand over fist.

Thanks for the help,will probably post again in a few weeks when the new one gives up the ghost too

Yep, I figured as much. I do see that they rolled out a new firmware, v26 last night that was supposed to fix some issues. Didnt help me!

On the phone to VM now.

[pip08456]

The only issue the new firmware (R26) resolves is the freezing downloads.

[IvIaXiIvIuS]

Back again,

After 3 Tech visits and 2 more hubs (on my 3rd) the symptoms keep persisting.
Phoned again this morning to be told yet again i'll need another Tech visit on wednesday,pointless if you ask me as the fault is at random times throughout the day.
Dunno if to just cancel the service now as its beyond a joke and only getting worse and still paying full price for a service i can only use for 5-10 mins before a 5 min reboot cycle of the Hub.Also don't know if this is relivant but i'm getting alot of T3 and T4 timouts now on the Hub log page:

Mon May 30 12:01:36 2011 Critical (3) DHCP FAILED - Requested Info not supported.;
Mon May 30 12:01:20 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon May 30 12:00:47 2011 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;Mon May 30 12:00:07 2011 Critical (3) No Ranging Response received - T3 time-out;
Mon May 30 02:20:04 2011 Critical (3) REG RSP not received;

[Mick Fisher]

My superhub random rebooting issue has hopefully sorted itself out, well somewhat.

The device managed 6 days+ before doing a spontaneous reboot. That was a couple of days ago. ATM it's uptime is 1:16:44:56.

Not great but better than rebooting 9 to 10 times a day and who knows how many time per night.

Anyway nothing has changed my end so it looks like a network problem. No amount of hub swaps or engineer visits will do any good IMO.