[philipp]

As explained in another thread I'm the OPs brother and its my connection as well. Last night and this morning it came back which lasted longer than a resync. Heres a snip of the superhub log:

Mon Apr 16 08:13:02 2012 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 16 08:12:54 2012 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Mon Apr 16 08:12:47 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Mon Apr 16 08:09:02 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Mon Apr 16 08:08:17 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Mon Apr 16 08:07:27 2012 Critical (3) 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;
Mon Apr 16 07:58:17 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 16 07:18:32 2012 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Mon Apr 16 07:18:02 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:52:41 2012 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:52:36 2012 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:52:33 2012 Warning (5) Lost MDD Timeout;CM-MAC=;CMTS-MAC=CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:52:33 2012 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:52:17 2012 Warning (5) Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 15 23:52:17 2012 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 15 23:48:29 2012 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:48:02 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 15 23:47:43 2012 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 15 23:42:02 2012 Critical (3) No UCDs Received - Timeout;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:41:43 2012 Critical (3) No UCDs Received - Timeout;;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:41:25 2012 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:38:26 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:38:08 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 23:38:06 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 15 23:34:58 2012 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 15 08:59:38 2012 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 08:54:15 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 15 08:53:31 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;

Also I have noticed. Occasionally before the timeouts that 1 or more channels on the superhub becomes un-usable the snr drops to about 9 and power levels go to lower than -20 and QAM256 becomes unknown. It then goes back to where the other channels are or the superhub loses complete sync.

Is there anything there that may suggest if its the line coming in at the property or at the green box or beyond?

Are there any functions (hidden or otherwise) that will show the ranges of power levels and snr during the time its on? (If not there should be!)