<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for bradyvolpe.com</title>
	<atom:link href="http://bradyvolpe.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradyvolpe.com</link>
	<description></description>
	<lastBuildDate>Wed, 21 Jul 2010 23:42:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on DOCSIS and Cable Modems &#8211; How it works :: Station Maintenance by Brady</title>
		<link>http://bradyvolpe.com/docsis-101/docsis101_station-maintenance/comment-page-1/#comment-256</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Wed, 21 Jul 2010 23:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=245#comment-256</guid>
		<description>Hi Roger,

You have what sounds like a classic case of an upstream impairment that is time-dependent.  Do you by chance have any heavy equipment around you that fires up at 8:40pm?  If this is a new occurrence, see if there is a streetlight that turns on at this same time.  Something is likely coming on which is emitting a lot of ingress into the upstream.  It is preventing your RNG-REQ from reaching the CMTS, hence your T3 Timeouts.  In addition it is causing packet loss, which you are seeing as latency, because in a TCP/IP flow, the packets are just being retransmitted.  Of course I am presuming your are basing the latency off of HTTP page requests or gaming results.  If using VoIP or video conferencing, which is UDP-based, there is no packet re-transmission and so you would have noticeable packet loss and hence degraded service quality.

I think it is important you work with your cable operator and have them measure errored code words (measured on the CMTS) on your modem during the evening hours (8:40pm and after).  This will be the only way that they will actually see the problems you are experiencing.  If they test in the day time, everything will look just fine.  Ideally, you may be able to identify the source of ingress and point it out to the cable operator so that they can fix the leak in their plant.  This is often a difficult battle for the cable operator and everyone pays the price.

Good luck, let me know how it turns out.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Roger,</p>
<p>You have what sounds like a classic case of an upstream impairment that is time-dependent.  Do you by chance have any heavy equipment around you that fires up at 8:40pm?  If this is a new occurrence, see if there is a streetlight that turns on at this same time.  Something is likely coming on which is emitting a lot of ingress into the upstream.  It is preventing your RNG-REQ from reaching the CMTS, hence your T3 Timeouts.  In addition it is causing packet loss, which you are seeing as latency, because in a TCP/IP flow, the packets are just being retransmitted.  Of course I am presuming your are basing the latency off of HTTP page requests or gaming results.  If using VoIP or video conferencing, which is UDP-based, there is no packet re-transmission and so you would have noticeable packet loss and hence degraded service quality.</p>
<p>I think it is important you work with your cable operator and have them measure errored code words (measured on the CMTS) on your modem during the evening hours (8:40pm and after).  This will be the only way that they will actually see the problems you are experiencing.  If they test in the day time, everything will look just fine.  Ideally, you may be able to identify the source of ingress and point it out to the cable operator so that they can fix the leak in their plant.  This is often a difficult battle for the cable operator and everyone pays the price.</p>
<p>Good luck, let me know how it turns out.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DOCSIS and Cable Modems &#8211; How it works :: Station Maintenance by Roger Case</title>
		<link>http://bradyvolpe.com/docsis-101/docsis101_station-maintenance/comment-page-1/#comment-251</link>
		<dc:creator>Roger Case</dc:creator>
		<pubDate>Wed, 21 Jul 2010 04:21:53 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=245#comment-251</guid>
		<description>I have a interesting issue regarding the T3 timeouts on 2 different moto modems Ive tried.   Exactly at 840pm CST every night my connection and latency suffers until 4am or so (cant stay up everynight to get exact time) but connection then is perfect for the entire day.   Latency and speed are well within parameters, but at 840pm my modem displays No Ranging Response received - T3 time-out.     Why is that at 840 this is happening and no other time?    Its getting very frustrating and having to call my cable provider every evening about this.
HELP?
Thank you much</description>
		<content:encoded><![CDATA[<p>I have a interesting issue regarding the T3 timeouts on 2 different moto modems Ive tried.   Exactly at 840pm CST every night my connection and latency suffers until 4am or so (cant stay up everynight to get exact time) but connection then is perfect for the entire day.   Latency and speed are well within parameters, but at 840pm my modem displays No Ranging Response received &#8211; T3 time-out.     Why is that at 840 this is happening and no other time?    Its getting very frustrating and having to call my cable provider every evening about this.<br />
HELP?<br />
Thank you much</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial &#8211; M-CMTS Architecture by Digital Cable: Cable Modem, List of Cable Internet Providers, Cablecard, Docsis, Hybrid Fibre-Coaxial, Digital Cable, Com21 &#124; Uncategorized &#124; Information about VoIP phone service!</title>
		<link>http://bradyvolpe.com/docsis-3-0/docsis-3-0-tutorial-m-cmts-architecture/comment-page-1/#comment-199</link>
		<dc:creator>Digital Cable: Cable Modem, List of Cable Internet Providers, Cablecard, Docsis, Hybrid Fibre-Coaxial, Digital Cable, Com21 &#124; Uncategorized &#124; Information about VoIP phone service!</dc:creator>
		<pubDate>Wed, 14 Jul 2010 15:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=376#comment-199</guid>
		<description>[...] DOCSIS 3.0 Tutorial &#8211; M-CMTS Architecture &#124; bradyvolpe.com [...]</description>
		<content:encoded><![CDATA[<p>[...] DOCSIS 3.0 Tutorial &#8211; M-CMTS Architecture | bradyvolpe.com [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial &#8211; CMTS Architecture by Agnet</title>
		<link>http://bradyvolpe.com/docsis-3-0/docsis3_architecture/comment-page-1/#comment-182</link>
		<dc:creator>Agnet</dc:creator>
		<pubDate>Tue, 13 Jul 2010 02:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=360#comment-182</guid>
		<description>We like I-CMTS for new introdution.</description>
		<content:encoded><![CDATA[<p>We like I-CMTS for new introdution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial &#8211; M-CMTS Architecture by DOCSIS 3.0 Tutorial - The EQAM &#124; bradyvolpe.com</title>
		<link>http://bradyvolpe.com/docsis-3-0/docsis-3-0-tutorial-m-cmts-architecture/comment-page-1/#comment-131</link>
		<dc:creator>DOCSIS 3.0 Tutorial - The EQAM &#124; bradyvolpe.com</dc:creator>
		<pubDate>Fri, 02 Jul 2010 00:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=376#comment-131</guid>
		<description>[...] my article on DOCSIS 3.0 M-CMTS architecture, I talked about the distributed nature of the CMTS with an M-CMTS core (the CPU of the system), a [...]</description>
		<content:encoded><![CDATA[<p>[...] my article on DOCSIS 3.0 M-CMTS architecture, I talked about the distributed nature of the CMTS with an M-CMTS core (the CPU of the system), a [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
