PDA

View Full Version : Superhub Downstream Power OK?


Chuck
13-09-2011, 01:26
I have a 20mbs connection with a super hub and all is well on the broadband front. My TV however is very unresponsive! All I can find is maybe the downstream power might be too high? Is it?

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 323000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
Downstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power SNR Docsis/EuroDocsis locked
Locked QAM256 104 55616000 Kbits/sec 323000000 Hz 14.6 dBmV 41.2 dB Hybrid
Locked QAM256 101 55616000 Kbits/sec 299000000 Hz 15.5 dBmV 41.4 dB Hybrid
Locked QAM256 102 55616000 Kbits/sec 307000000 Hz 15.4 dBmV 41.2 dB Hybrid
Locked QAM256 103 55616000 Kbits/sec 315000000 Hz 15.3 dBmV 41.4 dB Hybrid
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Upstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power
Locked ATDMA 3 20480 Kbits/sec 35800000 Hz 45.4 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

Sephiroth
13-09-2011, 01:31
DS power is too high. You can also check the power on the TV in the Settings menu.

But if all is well on the broadband front, why would the TV fail? Maybe the TV box is stuffed (even from the high power).

Can we also see an event log from the SH and your Operational Config from the stats.

Chuck
13-09-2011, 01:37
Here is the log, not where the operational config is?!

Time Priority Description
Mon Sep 12 14:33:46 2011 Error (4) DHCP RENEW sent - Invalid DHCP v4 option;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Sun Sep 11 05:26:54 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Sun Sep 11 05:26:54 2011 Warning (5) Lost MDD Timeout;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Sun Sep 11 05:26:54 2011 Warning (5) MDD message timeout;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Sun Sep 11 05:26:51 2011 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Fri Aug 12 06:25:39 2011 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Sat Aug 06 15:17:29 2011 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Sat Aug 06 15:17:21 2011 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.0;CM-VER=3.0;
Mon Jun 20 17:26:56 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Thu Jun 16 18:59:59 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:09:b6:6b:38:01;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:09:b6:6b:38:01;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=a0:21:b7:11:d1:18;CMTS-MAC=00:30:b8:d0:b7:90;CM-QOS=1.0;CM-VER=3.0;

jb66
13-09-2011, 04:17
More likely you have an unresponsive model of box

thenry
13-09-2011, 04:19
you need to remove your MACs from the log you posted. and as Seph said there high, you need an attenuator.

Chuck
13-09-2011, 05:24
where is the edit button? has it gone because someone has replied?

Sephiroth
13-09-2011, 11:04
You only need to remove (in future) the CM MAC address. The CMTS is at the VM end and isn't at risk.

The event log is clean from a problematic point of view (you said BB was OK).

Have you checked the settings menu in the TV box?

qasdfdsaq
13-09-2011, 14:39
Even the CM MACs on DOCSIS 3 aren't that much of a risk, what with certificates and all.