<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for bradyvolpe.com</title>
	
	<link>http://bradyvolpe.com</link>
	<description>Explore</description>
	<lastBuildDate>Fri, 03 Feb 2012 15:03:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForBradyvolpecom" /><feedburner:info uri="commentsforbradyvolpecom" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Comment on Advanced Troubleshooting in a DOCSIS 3.0 Plant by Brady</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/n49VEirmGvI/</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Fri, 03 Feb 2012 15:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=1795#comment-22363</guid>
		<description>Hi Matthew,

Although I am leaving money on the table, I do not recommend, sell or promote specific equipment or vendors.  There is good equipment out there and bad equipment.  My company, &lt;a href="http://volpefirm.com" title="The Volpe Firm" target="_blank" rel="nofollow"&gt;The Volpe Firm&lt;/a&gt;, is frequently approached to either sell or recommend products to my clients for commission, but often I find myself troubleshooting with different vendor equipment and vendor devices, so it is important that I remain a neutral party.  In addition I don't want a bad recommendation to poorly reflect on my reputation.

My recommendation is that you first get datasheets from available equipment vendors you may be interested in.  Next, contact the sales reps/engineers and have them come in and demo the equipment so that you are familiar with how to use the equipment.  Ask for a demo unit for one week so that you can test it onsite and record its accuracy / precision against a reference you have available.  Do the same with the next vendor and the one after that.  By the time you have gone through this experiment with each vendor you should have a pretty good idea of the vendor's support, the equipment ease of use, its features, and side-by-side accuracy / precision with other equivalent equipment provided you are keeping good notes when you make your measurements.  You don't always get what you pay for and there is a difference from vendor to vendor.

I hope this helps.

Regards,
-Brady</description>
		<content:encoded><![CDATA[<p>Hi Matthew,</p>
<p>Although I am leaving money on the table, I do not recommend, sell or promote specific equipment or vendors.  There is good equipment out there and bad equipment.  My company, <a href="http://volpefirm.com" title="The Volpe Firm" target="_blank" rel="nofollow">The Volpe Firm</a>, is frequently approached to either sell or recommend products to my clients for commission, but often I find myself troubleshooting with different vendor equipment and vendor devices, so it is important that I remain a neutral party.  In addition I don&#8217;t want a bad recommendation to poorly reflect on my reputation.</p>
<p>My recommendation is that you first get datasheets from available equipment vendors you may be interested in.  Next, contact the sales reps/engineers and have them come in and demo the equipment so that you are familiar with how to use the equipment.  Ask for a demo unit for one week so that you can test it onsite and record its accuracy / precision against a reference you have available.  Do the same with the next vendor and the one after that.  By the time you have gone through this experiment with each vendor you should have a pretty good idea of the vendor&#8217;s support, the equipment ease of use, its features, and side-by-side accuracy / precision with other equivalent equipment provided you are keeping good notes when you make your measurements.  You don&#8217;t always get what you pay for and there is a difference from vendor to vendor.</p>
<p>I hope this helps.</p>
<p>Regards,<br />
-Brady</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/n49VEirmGvI" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/troubleshooting-docsis/advanced-troubleshooting-in-a-docsis-3-0-plant/comment-page-1/#comment-22363</feedburner:origLink></item>
	<item>
		<title>Comment on Advanced Troubleshooting in a DOCSIS 3.0 Plant by Matthew Horwat</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/1JInvdEMRjc/</link>
		<dc:creator>Matthew Horwat</dc:creator>
		<pubDate>Fri, 03 Feb 2012 14:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=1795#comment-22362</guid>
		<description>I noticed in the last few slides, it noted the best slm to use is one that can allow you to see all the bonded upstream channels at once.  Do you have any recommendations for slm's that support said feature, or at least one that supports checking them channel by channel as it showed in the slide?</description>
		<content:encoded><![CDATA[<p>I noticed in the last few slides, it noted the best slm to use is one that can allow you to see all the bonded upstream channels at once.  Do you have any recommendations for slm&#8217;s that support said feature, or at least one that supports checking them channel by channel as it showed in the slide?</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/1JInvdEMRjc" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/troubleshooting-docsis/advanced-troubleshooting-in-a-docsis-3-0-plant/comment-page-1/#comment-22362</feedburner:origLink></item>
	<item>
		<title>Comment on DOCSIS 3.0 | Impaired Service by Brady</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/BYyPJ-goJmM/</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Thu, 26 Jan 2012 12:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=1741#comment-21857</guid>
		<description>Hi Isaac,

Until just recently I would have said "Yes", more bonded downstreams mean a more robust downstream.  But not so fast.  Unlike partial service in the upstream (read my article on &lt;a href="http://bradyvolpe.com/docsis-3-0/docsis-3-0-partial-service/" target="_blank" rel="nofollow"&gt;Partial Service&lt;/a&gt;), the CMTS has no way of knowing that downstream channel is down or impaired going to a subscriber's cable modem.  So the CMTS will continue to "stripe" data across all bonded channels.  So if you have four downstream bonded channels and one channel is down or impaired, then 25% of the data will be lost.

This was discussed during a recent SCTE Seminar I was giving in North Carolina where an operator experienced this very problem.  I am in the process of configuring a DOCSIS 3.0 CMTS in my lab where I can run some experiments to definitively prove the issue and provide a full article back to this site.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Isaac,</p>
<p>Until just recently I would have said &#8220;Yes&#8221;, more bonded downstreams mean a more robust downstream.  But not so fast.  Unlike partial service in the upstream (read my article on <a href="http://bradyvolpe.com/docsis-3-0/docsis-3-0-partial-service/" target="_blank" rel="nofollow">Partial Service</a>), the CMTS has no way of knowing that downstream channel is down or impaired going to a subscriber&#8217;s cable modem.  So the CMTS will continue to &#8220;stripe&#8221; data across all bonded channels.  So if you have four downstream bonded channels and one channel is down or impaired, then 25% of the data will be lost.</p>
<p>This was discussed during a recent SCTE Seminar I was giving in North Carolina where an operator experienced this very problem.  I am in the process of configuring a DOCSIS 3.0 CMTS in my lab where I can run some experiments to definitively prove the issue and provide a full article back to this site.</p>
<p>-Brady</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/BYyPJ-goJmM" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/docsis-3-0-impaired-service/comment-page-1/#comment-21857</feedburner:origLink></item>
	<item>
		<title>Comment on Hacking DOCSIS Cable Modems by Brady</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/esUyRgMyAW4/</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Thu, 26 Jan 2012 12:24:24 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=966#comment-21855</guid>
		<description>Great to hear ToRuDiNe.  Keep a careful lookout, however and don't become too lax on the security side.  You have put a first line of defense in place.  BPI+ and TFTP Enforce keep the lazy folks from getting online, but the hardcore hackers will find ways around it.  There are other more aggressive security precautions that can be implemented to eliminate even the most diligent hackers.

-Brady</description>
		<content:encoded><![CDATA[<p>Great to hear ToRuDiNe.  Keep a careful lookout, however and don&#8217;t become too lax on the security side.  You have put a first line of defense in place.  BPI+ and TFTP Enforce keep the lazy folks from getting online, but the hardcore hackers will find ways around it.  There are other more aggressive security precautions that can be implemented to eliminate even the most diligent hackers.</p>
<p>-Brady</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/esUyRgMyAW4" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/troubleshooting-docsis/hacking-docsis-cable-modems/comment-page-1/#comment-21855</feedburner:origLink></item>
	<item>
		<title>Comment on Hacking DOCSIS Cable Modems by ToRuDiNe</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/bsi7e8CmzGI/</link>
		<dc:creator>ToRuDiNe</dc:creator>
		<pubDate>Tue, 24 Jan 2012 14:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=966#comment-21790</guid>
		<description>Hey Brady!

This article has helped me secure my network in many ways. 

I am an engineer in charge of a small cable company in Patagonia Argentina. We started to offer internet service around 8 months ago - before that it was just cable - .

During the first two months we didn't have any kind of security but a shared secret, and we experienced some theft of service by a couple of -well identified- users.

Now we have mandatory BPI+ and tftp enforce, which has made theft of service disappear. 

Thanks for showing me where to look!</description>
		<content:encoded><![CDATA[<p>Hey Brady!</p>
<p>This article has helped me secure my network in many ways. </p>
<p>I am an engineer in charge of a small cable company in Patagonia Argentina. We started to offer internet service around 8 months ago &#8211; before that it was just cable &#8211; .</p>
<p>During the first two months we didn&#8217;t have any kind of security but a shared secret, and we experienced some theft of service by a couple of -well identified- users.</p>
<p>Now we have mandatory BPI+ and tftp enforce, which has made theft of service disappear. </p>
<p>Thanks for showing me where to look!</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/bsi7e8CmzGI" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/troubleshooting-docsis/hacking-docsis-cable-modems/comment-page-1/#comment-21790</feedburner:origLink></item>
</channel>
</rss><!-- Dynamic page generated in 1.345 seconds. --><!-- Cached page generated by WP-Super-Cache on 2012-02-03 11:54:41 --><!-- Compression = gzip -->

