<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Cox HSI forum - dslreports.com community</title>
<link>http://www.dslreports.com/forum/coxhsi</link>
<description>Cox HSI forum current topics</description>
<language>en</language>
<copyright>Copyright 2007, dslreports.com</copyright>
<pubDate>Sun, 22 Nov 2009 20:58:31 EDT</pubDate>
<lastBuildDate>Sun, 22 Nov 2009 20:58:31 EDT</lastBuildDate>

<image>
<title>dslreports.com</title>
<url>http://i.dslr.net/bbrdisc1.gif</url>
<link>http://www.dslreports.com</link>
<width>19</width>
<height>18</height>
<description>bbr disc</description>
</image>

<item>
<title>COX DNS issue?</title>
<link>http://www.dslreports.com/forum/remark,23374827</link>
<description><![CDATA[Just noticed a serious issue that makes my home networking totally useless.

Basically, the cox DNS server will return any unknown host name with a fixed IP address 72.215.225.9. You can open a CMD window and start ping some random host names and they always return the same ip address. 

This basically destroys my home networking because none of my local PC names can be resolved correctly.

Anyone saw the same issue?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23374827</guid>
<pubDate>2009-11-21 11:39:46</pubDate>
</item>

<item>
<title>[CA] San Diego-lower freq range + no bonding after modem swap</title>
<link>http://www.dslreports.com/forum/remark,23349931</link>
<description><![CDATA[Upgraded from SB5100 to SB6120.  SB5100 showed frequency of 891Mhz, SB6120 shows 591Mhz w/no channel bonding.  Anyone else in Santee/El Cajon experiencing this?  My understanding is that my node would show two bonded downstream channels.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23349931</guid>
<pubDate>2009-11-16 16:34:37</pubDate>
</item>

<item>
<title>[NV] Speed Upgrade</title>
<link>http://www.dslreports.com/forum/remark,22375154</link>
<description><![CDATA[Anyone hear about a speed upgrade this summer for Las Vegas? We're still @ 12 down while the people in Cali got 20 last year. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22375154</guid>
<pubDate>2009-05-12 01:08:53</pubDate>
</item>

<item>
<title>[NV] Cox HSI Las Vegas NOW w/Docsis 3</title>
<link>http://www.dslreports.com/forum/remark,23293555</link>
<description><![CDATA[Well came home tonight to see the blue light on my Motorola SB6120. Ran a speed test with Cox's internal testing site and I'm getting a reported 88Mbps available bandwidth and able to run the speed test at over 70Mbps.  :D]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23293555</guid>
<pubDate>2009-11-04 21:49:01</pubDate>
</item>

<item>
<title>[CA] What Causes Image Tiling w/&#x27;Blipping&#x27; Audio?</title>
<link>http://www.dslreports.com/forum/remark,23375794</link>
<description><![CDATA[Problem began only about a month ago, has become persistent and is very annoying:  intermittent picture tiling that occurs combined with "blips" in audio (so that 1 or 2 words are absent in broadcasts, content "advances" over or past brief moments while image tiling is evident).

Happens on the "upper tier" channels like movie channels (Showtime, etc.), news (FOX, specifically).  VERY ANNOYING.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23375794</guid>
<pubDate>2009-11-21 16:38:15</pubDate>
</item>

<item>
<title>[LA] Slow in Baton Rouge 70810</title>
<link>http://www.dslreports.com/forum/remark,21567818</link>
<description><![CDATA[Lately, my HSI has been very sluggish in the evenings. I just pinged the gateway (8:15 PM, 12/11/08), and I've copied the results below. It's not as bad during the day, and it improves late at night. I'm in Baton Rouge, zip code 70810.

Pinging 68.11.159.129 with 32 bytes of data:
Reply from 68.11.159.129: bytes=32 time=448ms TTL=254
Reply from 68.11.159.129: bytes=32 time=243ms TTL=254
Reply from 68.11.159.129: bytes=32 time=96ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=252ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=61ms TTL=254
Reply from 68.11.159.129: bytes=32 time=158ms TTL=254
Reply from 68.11.159.129: bytes=32 time=407ms TTL=254
Reply from 68.11.159.129: bytes=32 time=118ms TTL=254
Reply from 68.11.159.129: bytes=32 time=242ms TTL=254
Reply from 68.11.159.129: bytes=32 time=58ms TTL=254
Reply from 68.11.159.129: bytes=32 time=241ms TTL=254
Reply from 68.11.159.129: bytes=32 time=74ms TTL=254
Reply from 68.11.159.129: bytes=32 time=50ms TTL=254
Reply from 68.11.159.129: bytes=32 time=71ms TTL=254
Reply from 68.11.159.129: bytes=32 time=62ms TTL=254
Reply from 68.11.159.129: bytes=32 time=228ms TTL=254
Reply from 68.11.159.129: bytes=32 time=380ms TTL=254
Reply from 68.11.159.129: bytes=32 time=182ms TTL=254
Reply from 68.11.159.129: bytes=32 time=247ms TTL=254
Reply from 68.11.159.129: bytes=32 time=207ms TTL=254
Reply from 68.11.159.129: bytes=32 time=122ms TTL=254
Reply from 68.11.159.129: bytes=32 time=91ms TTL=254
Reply from 68.11.159.129: bytes=32 time=321ms TTL=254
Reply from 68.11.159.129: bytes=32 time=243ms TTL=254
Reply from 68.11.159.129: bytes=32 time=62ms TTL=254
Reply from 68.11.159.129: bytes=32 time=316ms TTL=254
Reply from 68.11.159.129: bytes=32 time=462ms TTL=254
Reply from 68.11.159.129: bytes=32 time=26ms TTL=254
Reply from 68.11.159.129: bytes=32 time=81ms TTL=254
Reply from 68.11.159.129: bytes=32 time=58ms TTL=254
Reply from 68.11.159.129: bytes=32 time=25ms TTL=254
Reply from 68.11.159.129: bytes=32 time=372ms TTL=254
Reply from 68.11.159.129: bytes=32 time=80ms TTL=254
Reply from 68.11.159.129: bytes=32 time=82ms TTL=254
Reply from 68.11.159.129: bytes=32 time=168ms TTL=254
Reply from 68.11.159.129: bytes=32 time=277ms TTL=254
Reply from 68.11.159.129: bytes=32 time=259ms TTL=254
Reply from 68.11.159.129: bytes=32 time=37ms TTL=254
Reply from 68.11.159.129: bytes=32 time=142ms TTL=254
Reply from 68.11.159.129: bytes=32 time=556ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=104ms TTL=254
Reply from 68.11.159.129: bytes=32 time=159ms TTL=254
Reply from 68.11.159.129: bytes=32 time=120ms TTL=254
Reply from 68.11.159.129: bytes=32 time=199ms TTL=254
Reply from 68.11.159.129: bytes=32 time=32ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=310ms TTL=254
Reply from 68.11.159.129: bytes=32 time=33ms TTL=254
Reply from 68.11.159.129: bytes=32 time=48ms TTL=254
Reply from 68.11.159.129: bytes=32 time=261ms TTL=254

Ping statistics for 68.11.159.129:
    Packets: Sent = 53, Received = 49, Lost = 4 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 556ms, Average = 181ms
Control-C]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21567818</guid>
<pubDate>2008-12-11 21:21:00</pubDate>
</item>

<item>
<title>Fiber Cut SE NOVA Springfield/Mt Vernon-repairs underway</title>
<link>http://www.dslreports.com/forum/remark,23372968</link>
<description><![CDATA[At about 5pm today a Cox Communications fiber was cut by another company doing other work in the southeastern Fairfax County area of Springfield and Mt.Vernon. A small number of homes in this area are currently experiencing an outage. Cox crews are on site to make repairs. More updates shortly.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23372968</guid>
<pubDate>2009-11-20 20:50:16</pubDate>
</item>

<item>
<title>[CA] Cox HSI dropping constantly, in a tech rut....help</title>
<link>http://www.dslreports.com/forum/remark,23336360</link>
<description><![CDATA[Hello,

Hopefully one of the keen Cox people can help a bit here. Thanks so much Cox gurus in advance.

I have the Premium plan, and when it works -- it works well for a very long time -- until something happens in the network.   I had one other issue 3 years ago -- and it took Cox 5 months to fix, it.    It took them this long to finally go across the street in a junction box where Taps are for all the houses immediately around me.   Apparently a cable was loose.   It was a bit maddening experience.

Well here I am again, and something in the Cox network has changed.   After 4 calls, 2 different visits I am no better off with any plan or methodology to do anything else.   Cox said my return signal is "not good" or is "failing" or "critical" .  However, my power levels appear to be good to them.  They sent out techs.  The first had no clue, and didnt really care to.  I showed him the numerous cable modem log errors of rebooting and SYNC troubles, and was promptly ignored while him looking at me in the face saying everything is fine.    

I had to call again to get another tech out, this one knew very little, and wasnt qualified to look into the phone box across the street (where my Tap issue was a couple years ago) to check connections in there.    He was very nice however, and clearly wanted to help -- but didnt know what to do.

I suggested leaving another cable modem, in absence of any suggestions from Cox, to see if that helps.    He had to call for approval, and got this.   

Cable modem is a Motorola SB5101.  The one I had before was the Ambit U10C018.   

The Motorola is certainly less verbose in the error logs, but when it loses connectivity it lasts sometimes much longer and reboots.  The Ambit had more errors logged, but when it looses connectivity, it lasts for seconds only and never seemed to reboot.       The first log I post below is an example of what is going on with the Motorola.  You can see it is rebooting itself (happens at least a couple times a day).       After this log I will post what the Ambit looked like when that was in the system:

Motorola Log:

009-11-12 11:51:18&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:23&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-12 11:50:37&#9;6-Notice&#9;M573.0&#9;Modem Is Shutting Down and Rebooting...
2009-11-12 11:50:37&#9;3-Critical&#9;R004.0&#9;Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-11-12 01:43:47&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:21&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:12&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-12 01:43:11&#9;6-Notice&#9;E111.0&#9;SW download Successful - Via NMS
2009-11-12 01:42:37&#9;6-Notice&#9;E101.0&#9;SW Download INIT - Via NMS
2009-11-11 22:57:51&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:28&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 22:57:04&#9;6-Notice&#9;M573.0&#9;Modem Is Shutting Down and Rebooting...
2009-11-11 22:57:04&#9;3-Critical&#9;R004.0&#9;Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-11-11 21:14:59&#9;4-Error&#9;D103.0&#9;DHCP RENEW sent - Invalid DHCP option
2009-11-11 09:16:22&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 09:16:20&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
2009-11-11 09:16:18&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 09:16:12&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
2009-11-11 09:15:14&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:22&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 08:44:51&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:20&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 08:24:35&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:55&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:44&#9;3-Critical&#9;R004.0&#9;Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:00:11&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 08:23:24&#9;6-Notice&#9;M573.0&#9;Modem Is Shutting Down and Rebooting...
2009-11-11 08:23:24&#9;3-Critical&#9;&Ocirc;7954.20&#9;Resetting the cable modem due to docsDevResetNow
2009-11-11 08:22:46&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:01:19&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:01:10&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:01:09&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:01:06&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:01:04&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:01:03&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:26&#9;3-Critical&#9;T002.0&#9;SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:26&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:24&#9;3-Critical&#9;T002.0&#9;SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:24&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:06&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:00:21&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Now below is the Ambit Logs from various prior days:

Wed Nov 11 05:55:26 2009&#9;Wed Nov 11 05:55:26 2009&#9;Critical (3)&#9;Started Unicast Maintenance Ranging - No Response received - ...
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Nov 10 17:19:00 2009&#9;Tue Nov 10 17:19:00 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:06:32 2009&#9;Tue Nov 10 17:06:32 2009&#9;Critical (3)&#9;Started Unicast Maintenance Ranging - No Response received - ...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to receive MAC S...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Information (7)&#9;Downstream pulse failed
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:01:23 2009&#9;Tue Nov 10 17:01:23 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Authorized
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Registration complete!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;We registered with a DOCSIS 1.1 config file!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Received a REG-RSP message from the CMTS...
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Sending a REG-REQ to the CMTS...
Tue Nov 10 16:56:52 2009&#9;Tue Nov 10 16:56:52 2009&#9;Information (7)&#9;CableModem SNMP configure complete

 

Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Nov 10 17:19:00 2009&#9;Tue Nov 10 17:19:00 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:06:32 2009&#9;Tue Nov 10 17:06:32 2009&#9;Critical (3)&#9;Started Unicast Maintenance Ranging - No Response received - ...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to receive MAC S...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Information (7)&#9;Downstream pulse failed
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:01:23 2009&#9;Tue Nov 10 17:01:23 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Authorized
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Registration complete!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;We registered with a DOCSIS 1.1 config file!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Received a REG-RSP message from the CMTS...
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Sending a REG-REQ to the CMTS...
Tue Nov 10 16:56:52 2009&#9;Tue Nov 10 16:56:52 2009&#9;Information (7)&#9;CableModem SNMP configure complete
Tue Nov 10 16:56:52 2009&#9;Tue Nov 10 16:56:52 2009&#9;Notice (6)&#9;TLV-11 - unrecognized OID]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23336360</guid>
<pubDate>2009-11-13 12:02:57</pubDate>
</item>

<item>
<title>[CT] Dropped connections, ongoing.</title>
<link>http://www.dslreports.com/forum/remark,23365595</link>
<description><![CDATA[Modem (SB5120) keep dropping the connection. Has been going on for over a week.

Had a tech out "Nothing wrong, it's all fine".

Sorry but having your connection drop out 30-40 times a day is not "all fine".

Power Level -3 dBmV   The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading  
 

Upstream  Value 
Channel ID 1 
Frequency 33600000 Hz  
Ranging Service ID 456 
Symbol Rate 2.560 Msym/s 
Power Level 43 dBmV  

Some log info from today when it was happening:

Software Version: SB5120-2.19.0.10-SCM01-NOSH

2009-11-19 14:07:53 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:53 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:51 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:51 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:45 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:45 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:42 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:42 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:40 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:40 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:30 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:29 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:27 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:27 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:26 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:26 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:24 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:24 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:13 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:13 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:07:09 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:07:09 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:06:36 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:06:36 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:05:49 5-Warning  TSM: TxError WatchDog - Restart Upstream 
2009-11-19 14:05:49 5-Warning  HAL: Overcoming Tx Error (reseting the US - DMA) 
2009-11-19 14:05:29 7-Information  SNMP: Working in SNMP V1/2c Only NmAccess mode 
2009-11-19 14:05:28 7-Information  INITIALIZATION COMPLETE - MODEM IS OPERATIONAL 
2009-11-19 14:05:28 7-Information B401.0 Authorized 
2009-11-19 14:05:27 6-Notice I401.0 TLV-11 - unrecognized OID 
2009-11-19 14:05:27 7-Information  SEC: Co-Signer CVC from configuration file was verified 
2009-11-19 14:05:27 7-Information  REGISTRATION COMPLETE - Waiting for Operational status 
2009-11-19 14:05:26 7-Information  REG: Capability type  incorrectly negotiated by CMTS 
2009-11-19 14:05:26 7-Information  Registration file - downloaded 
2009-11-19 14:05:24 7-Information  Trying to download Configuration file ... 
2009-11-19 14:05:24 7-Information  Time of day - retrieved 
2009-11-19 14:05:23 7-Information  DHCP - parameters acquired 
2009-11-19 14:05:23 7-Information  DHCP: ACK: Setting (*) CM TFTP Boot file: 150001_vm1.1_d.cfg 
2009-11-19 14:05:23 7-Information  DHCP: Setting CM IP address to: 10.3.218.208 
2009-11-19 14:05:23 7-Information  DHCP: Setting (*) CM Syslog Server address to: 10.254.254.254 
2009-11-19 14:05:23 7-Information  DHCP: Setting (*) CM Time Server address to: 172.19.65.16 
2009-11-19 14:05:23 7-Information  DHCP: Setting (*) CM Subnet mask to: 255.255.248.0 
2009-11-19 14:05:23 7-Information  DHCP: Setting (*) CM Gateway address to: 10.3.216.1 
2009-11-19 14:05:23 7-Information  DHCP: OFFER: Setting (*) CM TFTP Boot file: 150001_vm1.1_d.cfg 
2009-11-19 14:05:23 7-Information  DHCP select: Setting (*) CM TFTP Server address to: 172.19.65.16 
2009-11-19 14:05:23 7-Information  DHCP: Offered (*) CM IP address to: 10.3.218.208 

If any one has any ideas, I'd love to hear them. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23365595</guid>
<pubDate>2009-11-19 14:25:35</pubDate>
</item>

<item>
<title>[FL] Problems in Gainesville</title>
<link>http://www.dslreports.com/forum/remark,23356697</link>
<description><![CDATA[I moved into my own apartment in Gainesville at the start of the Fall semester in August. I purchased the premier package. I noticed few if any problems with the speed or consistency for two or three weeks, then some nights I began to get 2-3 mbits according to both speakeasy and speedtest.net. It seems to be inconsistent, but it is virtually always at night and virtually always drops down to the 2-3 range and not higher or lower. This is crippling as my roommates and I cannot even watch videos or anything and expect any kind of browsing or internet gameplay to work. These problems persist regardless of whether we are using our wireless router or whether connected directly to the modem.

&#149; make and model of cable modem

Scientific-atlanta WebSTAR DPC2100R2 

&#149; make a model of router

Netgear wrg614v9

&#149; cox speed tier

Premier

&#149; signal levels from 192.168.100.1 at several intervals during the day, especially as the slowness is occurring

These don't vary much and tend to be quite good, which is what really confuses me.

For example right now I'm getting 4.9 dBmV Receive and 43.0 dBmV transmit.

&#149; if they have splitters and if the cable modem has been plugged into a line directly from the wall (bypassing all splitters and surge protectors)

The modem is connected directly into the wall, if that is what you are asking. The technician who came out could find nothing wrong with the connections.

&#149; several speed tests to various locations close to where they reside (if applicable, &iuml;&iquest;&frac12;test.lvcm.com)

  
http://imgur.com/97dnT.png

They seem to agree regardless of server. Also of potential interest; a history:
http://imgur.com/iPALd.png

&#149; smokeping results or pingplotter output to various sites that they perceive packet loss to (if applicable)

My ping is generally just fine even during low bandwidth periods. I don't have any reason to believe it is packet loss.

&#149; has the user tweaked 

I followed the instructions and found no serious improvement. It does not seem to matter what computer is connected nor in what manner they are connected.

&#149; are you connected wired or wireless?

My roommates are wireless and I am wired ordinarily.

&#149; have you tested speeds bypassing router?

Many times.

&#149; are other services such as phone or tv affected?

I do not purchase these services from Cox.

I have been through the automated service multiple times and have been through multiple customer service representations. The technician who came out a week or two ago could not find anything wrong. At this point I am desperate. I should also mention that my upload is not really affected in any way and is consistently 2-3 mbs. 

I apologize if I have made any faux pas in posting this, but I am sort of at the end of my rope and was hoping I could get some potential explanation if not resolution. The best I could come up with is a lack of bandwidth for our area, but this seems unlikely as the representative stated that there have been no other complaints. 

Thank you for any help you might be able to give.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23356697</guid>
<pubDate>2009-11-17 21:34:12</pubDate>
</item>

</channel>
</rss>
