120M : Superhub 2 faulty?

[ianch99]

I am running a shub2 in modem mode and a few times now it has had an issue which required a power cycle to resolve. The symptoms are that at a particular point in time (all happening during the night so far), the modem goes into a brain dead state with massive packet loss and really low speeds (<5Mbps). When I checked the modem levels, etc. this morning (after it happened last night) and could see nothing out of the ordinary. Forgot to check the log though ..

Here's the ping chart covering the problem period:



and here's the same period for my neighbour who was unaffected (he is on a legacy 20Mb product w/ a media hub):



It seems that there is a network event at around 12:15 in the morning which sends my shub2 into a fit but the mediahub happily survives ..

If this keeps happening, should I request a replacement unit? If so, what evidence would VM need to support this?

[General Maximus]

yes the shub is faulty and yes you should get it replaced. It is a known issue with a minority of shubs where over a 24-48hr period they seem to get themselves worked up and have a spaz fit and the only way to implement a short term fix is reboot. (it isn't a network issue)

[Sephiroth]

If mon General is correct then whatever glitched on your SH2 made noise on the network that briefly glitched your neighbour's TBB.

To square the circle here, it would be useful to compare downstream channel frequencies. On the face of it, your neighbour is in the same frequency plan because of the TBB pattern to the right. But it's not unknown for 20 meg users to be on the legacy frequencies. Just a point of interest.

[General Maximus]

my bad, I was in a rush to get out and skimmed over the post and only caught the shub needed a reboot everyday and missed out the neighbour part