Tue Jun 26 20:53:48 2012 Critical (3) DHCP FAILED - Requested Info not supported.;;;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 26 20:53:25 2012 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;;;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 26 20:40:46 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:40:07 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:39:38 2012 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:39:18 2012 Critical (3) No Ranging Response received - T3 time-out;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:39:10 2012 Warning (5) Lost MDD Timeout;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:39:10 2012 Warning (5) MDD message timeout;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:38:58 2012 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:38:36 2012 Critical (3) No Ranging Response received - T3 time-out;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:38:04 2012 Warning (5) Lost MDD Timeout;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:38:04 2012 Warning (5) MDD message timeout;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:37:57 2012 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:37:35 2012 Critical (3) No Ranging Response received - T3 time-out;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 20:27:40 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 26 20:27:07 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;;;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 26 20:26:51 2012 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;;;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 26 18:40:54 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 26 17:32:16 2012 Critical (3) Ranging Request Retries exhausted;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 17:31:21 2012 Critical (3) Ranging Request Retries exhausted;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 17:07:02 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 17:06:58 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 15:35:31 2012 Critical (3) DHCP FAILED - Requested Info not supported.;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 08:18:54 2012 Critical (3) DHCP FAILED - Requested Info not supported.;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 07:12:32 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 07:12:27 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 07:12:19 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;;;CM-QOS=1.0;CM-VER=3.0;
Tue Jun 26 06:45:22 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;;;CM-QOS=1.0;CM-VER=3.0;
Mon Jun 25 23:31:35 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;;CM-QOS=1.0;CM-VER=3.0;
Mon Jun 25 23:31:13 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;;;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;;;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;;;CM-QOS=1.0;CM-VER=3.0;
---------- Post added at 22:23 ---------- Previous post was at 22:18 ----------
Quote:
Originally Posted by General Maximus
firstly it looks like you have had a 5th channel added hence the fake reporting of the 43.9 downstream, a reboot should fix it. Buuuuuuuuut, the problem, you have got is your upstream power, an engineer needs to come out and look at it, it is too high.
|
Thanks for the replies chaps!
Had three engineer visits and beem on the phone at least 14 times, each time repeating the same script. No, its not wireless. No, the operating system isn;t relevant, etc etc.
Managed to speak to somebody today and he "says" that the call has been escalated to the next level, whatever that means. Oh, and they're not allowed to call me and I have no idea when they "might" have fixed anything but I have to "see how it goes" for the next four days and call back after next Sunday if it is still going wrong!!!!
---------- Post added at 22:26 ---------- Previous post was at 22:23 ----------
Quote:
Originally Posted by General Maximus
firstly it looks like you have had a 5th channel added hence the fake reporting of the 43.9 downstream...
|
Am I only supposed to have 4 channels?
Sometimes I only see one.
Sometimes there is no upstream channel