View Single Post
Old 25-12-2011, 18:52   #28
Superblade7
cf.geek
 
Superblade7's Avatar
 
Join Date: Mar 2011
Location: Sheffield
Services: Sky Q 2TB & Sky Q Mini (Signature with Cinema & Sports HD) with VM 500Mbps Broadband & Phone
Posts: 583
Superblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond reputeSuperblade7 has a reputation beyond repute
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
Superblade7 is offline   Reply With Quote