![]() |
Re: Randomly Rebooting Superhub - Very Annoying
LOL Craigie's apology. Masque needs nothing explaining. He just needs to acknowledge facts presented by other people as regards the SH.
Anyway, the engineer wasn't far off the mark with his 5 channels observation. Your area is being prepared for 100 meg along with most others at different stages of preparation. In any case, in Modem Mode, the only resets you should see should occur because of something VM have done at the other end. Barring a duff SH, Modem Mode is rock steady IMO. Even Masque agrees! |
Re: Randomly Rebooting Superhub - Very Annoying
Seph, thanks again for the info. I've tried modem mode a couple of times and the SH has still rebooted after a day or two. If the engineer was right then all could settle down come January and all become well again. Fingers crossed!
Alternatively, my SH has decided to call it a day and the new SH may be the answer when it arrives! Guess I'll just wait and see. Craig, don't apologise on my account mate. Yours opinions are as valuable as others on here, regardless of whether or not they agree with you. Thanks again for all your comments, have a good Xmas! Superblade7 |
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
|
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
|
Re: Randomly Rebooting Superhub - Very Annoying
Search in the forum or Google on HUAWEI SUPERHUB. Although now Chrysalis has put some doubt on the Huawei device.
|
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
Who says the majority do not want a combined device, the very few posters on various forums or the 500,000+ customers all using the device satisfactorily. All modems are made to a price and have you heard of another company using Ambit as they were made for NTL/Virgin Media. Never had a single reboot but I expect with any product the will be faulty devices. I have used it both as a router and a modem and when i had my Edimax connected all devices preferred the Superhub connection, I am presently in Modem Mode as I was a tester for it. The device was I expect built for the masses rather than the few who want a fully customisable device which due to Modem Mode you can now use a state of the art router instead. As for my device being stable so are the majority or we would have many many calls about them. ---------- Post added at 22:48 ---------- Previous post was at 22:48 ---------- Quote:
|
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
i understand what your sayin, but you go about it the wrong way a lot of the time |
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
And Merry Christmas to you, of course. |
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
https://www.cableforum.co.uk/images/...2011/12/18.jpg |
Re: Randomly Rebooting Superhub - Very Annoying
Quote:
|
Re: Randomly Rebooting Superhub - Very Annoying
Seph,
Placed my SH in modem mode yesterday evening and by the time I got up this morning it had rebooted to default settings. Put it back in modem mode this morning and just arrived home and it has rebooted again. So 2 reboots in less than 24 hours both from modem mode, from the advice you've previously given, would you agree that it is actually my SH that has become faulty, nothing to do with the signal levels as you state that modem mode should be rock solid. If that is the case, then I am hopeful that the new SH that should arrive sometime next week may be the solution to my rebooting problem! Superblade7 |
Re: Randomly Rebooting Superhub - Very Annoying
You did right to test in modem mode. It's the baseline for all of this.
Can we see your power levels again please and the event log. Tell us also at what time you think the reset occurred so that it can be correlated with the event log. There would be only two reasons for a reset: 1) Commanded by the CMTS (the other end); 2) Faulty SH. The first reason is usually becauese your SH hasn't responded properly to thr keep-alives; or the CMTS doesn't think it has (in which case the event log should provide clues). |
Re: Randomly Rebooting Superhub - Very Annoying
Seph,
The reboots do usually coincide with the timings in the event log but as the reboots wipe the SH back to default settings, it only ever stores that last event. I generally have the same content on the event log following each reboot and today's reboots were sometime around 6:50am and presumably the next will have been about 15:43/15:44. This is the message that always seems to be on there following a reboot - Time Priority Description Sun Dec 25 15:44:05 2011 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 15:43:58 2011 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=XX:XX:XX:X:XX:XX;CMTS-MAC=XX:XX:XX:X:XX:XX;CM-QOS=1.0;CM-VER=3.0; The downstream power levels also seem to have settled down a little - Downstream Channels Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power SNR Docsis/EuroDocsis locked Locked QAM256 80 55616000 Kbits/sec 299000000 Hz 6.4 dBmV 43.8 dB Hybrid Locked QAM256 79 55616000 Kbits/sec 291000000 Hz 6.5 dBmV 43.3 dB Hybrid Locked QAM256 81 55616000 Kbits/sec 307000000 Hz 6.5 dBmV 43.3 dB Hybrid Locked QAM256 82 55616000 Kbits/sec 315000000 Hz 6.3 dBmV 43.3 dB Hybrid Locked QAM256 83 55616000 Kbits/sec 323000000 Hz 6.9 dBmV 43.9 dB Hybrid Hope that you can decipher the event log as it means nothing to me. Cheers again for your help Seph. Superblade7 |
Re: Randomly Rebooting Superhub - Very Annoying
The event log does not contain a DOCSDEV RESET message. So the reset to default isn't coming from the CMTS. The circuit reset messages are normal; during initialisation, while it searches for channels it's not in state of grace and errors are reported. If you have lots of T3 timeouts during normal operation, you might have a busty upstream, but that's not the case.
So now we await the new SH and hope the problem is resolved. It was worth looking for other causes if only toprepare you for dealing with VM again. I would add that on the VM forum, some people are reporting that the same thing happens with the replacement SH. In that case you'd need to get a Senior Engineer in to work with you to diagnose the situation. That can usually be arranged with UK Customer Services. But I'm surprised you don't have stability in modem mode. |
Re: Randomly Rebooting Superhub - Very Annoying
Seph,
Thanks again for your response, much appreciated. I think we've narrowed it down to a faulty Superhub then which will hopefully be easily resolved following a swap out when I get the replacement Superhub. I've just had another look on the VM forum and noticed this thread for someone who seems to be having a similar issue - http://community.virginmedia.com/t5/...ng/td-p/925613 On that, Ray M of the Forum Team states they are aware of the rebooting issue and have escalated it to Netgear. So if the new Superhub doesn't work, it's possible that there is some sort of firmware bug causing this to happen as it's been reported by a number of people on the VM forum now. Thanks again for you help and hopefully the new Superhub will bring an end to my issues. Cheers Superblade7 |
| All times are GMT. The time now is 01:14. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum