<?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 on: DOCSIS 3.0 Tutorial &#8211; Downstream Channel Bonding</title>
	<atom:link href="http://volpefirm.com/blog/docsis-3-0/downstream-channel-bonding/feed/" rel="self" type="application/rss+xml" />
	<link>http://volpefirm.com/docsis-3-0/downstream-channel-bonding/</link>
	<description>A Technical Communications Company</description>
	<lastBuildDate>Wed, 16 May 2012 06:51:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-3-0/downstream-channel-bonding/#comment-262</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Mon, 27 Feb 2012 22:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=904#comment-262</guid>
		<description>Jeff,

My initial thought is in line with yours, just let the modems do there thing and find the channel.  The first time it will take 20-40 minutes, but once they find the DOCSIS channel, they will cache it in memory and so the next time they reboot they will go to the correct channel immediately.  If the modems are not doing this, talk to your modem vendor and tell them to fix their firmware.

You can talk to your Cisco support engineer and they are able to add custom code for modem steering in special cases like this.  The challenge is keeping the custom code in place as the IOS is upgraded.  You may loose the custom code when you upgrade and have to get it added back in.  So it is always best to deal with these scenarios directly.

Another option would be if you can get the modem to register on any of the primary capable DOCSIS channels and then steer it via OUI mapping in the CMTS or by downloading a config file during DHCP that tells the modem to move frequency.  Again, these become more cumbersome methods, but would reduce the 20-40 minute time.

-Brady</description>
		<content:encoded><![CDATA[<p>Jeff,</p>
<p>My initial thought is in line with yours, just let the modems do there thing and find the channel.  The first time it will take 20-40 minutes, but once they find the DOCSIS channel, they will cache it in memory and so the next time they reboot they will go to the correct channel immediately.  If the modems are not doing this, talk to your modem vendor and tell them to fix their firmware.</p>
<p>You can talk to your Cisco support engineer and they are able to add custom code for modem steering in special cases like this.  The challenge is keeping the custom code in place as the IOS is upgraded.  You may loose the custom code when you upgrade and have to get it added back in.  So it is always best to deal with these scenarios directly.</p>
<p>Another option would be if you can get the modem to register on any of the primary capable DOCSIS channels and then steer it via OUI mapping in the CMTS or by downloading a config file during DHCP that tells the modem to move frequency.  Again, these become more cumbersome methods, but would reduce the 20-40 minute time.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Shields</title>
		<link>http://volpefirm.com/docsis-3-0/downstream-channel-bonding/#comment-261</link>
		<dc:creator>Jeff Shields</dc:creator>
		<pubDate>Mon, 20 Feb 2012 20:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=904#comment-261</guid>
		<description>Thanks for the great site and your time.


On this particular topic, here&#039;s our dilemma:

We have 3 DSs per DSG (4 or 8 channels w/ Cisco 5x20 line card in M-CMTS mode).  Therefore, we can&#039;t make every DS channel primary capable - not allowed.  We also &quot;enforce&quot; wideband modems to use one of the DSG channels for its primary channel.  This has created a problem with new wideband CM&#039;s DS selection process to the point where it can take up to an hour for modems to find a legit primary channel - average is 20 - 40 minutes or so.

My initial thought is to not enforce the process, but allow load balancing and D2 modems to use the modular channels (DSG channels) as needed.  The problem I foresee here is for the 8 channel setup where only 8 channels are allowed - therefore using the legacy channel for its primary DS really wouldn&#039;t be an option anyway. (NOTE: with 3G60 line cards, we don&#039;t have this problem as they are much more dense)

Do you have any suggestions on how to improve the DS selection process with this setup?

Thanks for any information provided.</description>
		<content:encoded><![CDATA[<p>Thanks for the great site and your time.</p>
<p>On this particular topic, here&#8217;s our dilemma:</p>
<p>We have 3 DSs per DSG (4 or 8 channels w/ Cisco 5&#215;20 line card in M-CMTS mode).  Therefore, we can&#8217;t make every DS channel primary capable &#8211; not allowed.  We also &#8220;enforce&#8221; wideband modems to use one of the DSG channels for its primary channel.  This has created a problem with new wideband CM&#8217;s DS selection process to the point where it can take up to an hour for modems to find a legit primary channel &#8211; average is 20 &#8211; 40 minutes or so.</p>
<p>My initial thought is to not enforce the process, but allow load balancing and D2 modems to use the modular channels (DSG channels) as needed.  The problem I foresee here is for the 8 channel setup where only 8 channels are allowed &#8211; therefore using the legacy channel for its primary DS really wouldn&#8217;t be an option anyway. (NOTE: with 3G60 line cards, we don&#8217;t have this problem as they are much more dense)</p>
<p>Do you have any suggestions on how to improve the DS selection process with this setup?</p>
<p>Thanks for any information provided.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-3-0/downstream-channel-bonding/#comment-260</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Fri, 08 Oct 2010 19:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=904#comment-260</guid>
		<description>Hi Tom,

There is nothing in the DOCSIS spec that talks about this.  But you raise a good point.  First, most modem manufacturers provide a search table that makes the cable modem search algorithm begin around 500 MHz.  Why?  Because many legacy Downstream plants start their DOCSIS channels above 500 MHz, so it reduces the time to find a DOCSIS channel and lock.  Starting at 100 MHz would increase the time.  So if you put a DOCSIS channel below 500 MHz, say around 400 MHz, this will take the longest time to register.  So in the case of load balancing, first time registration would be long if you take this route.  However, a cable modem does have memory.  Typically they will remember at least the last two channels they have locked on.  So once they found that 400 MHz channel and the possible upper channel for load balancing, you should be okay.  But if you have have more than two, all bets are off depending upon your cable modem vendor.

Remember that you can enter in known frequencies into the config file.  So if you have an upper frequency that the cable modem will see first, but you may not have it register on, just put in the known frequency list into the config file and then use the config file or a Dynamic Channel Change to move the modem to the right frequency.  This will save your modem a lot time in searching for the correct DOCSIS frequency.  Planning ahead is always better than letting the modem wonder around your network.

Regards,
-Brady</description>
		<content:encoded><![CDATA[<p>Hi Tom,</p>
<p>There is nothing in the DOCSIS spec that talks about this.  But you raise a good point.  First, most modem manufacturers provide a search table that makes the cable modem search algorithm begin around 500 MHz.  Why?  Because many legacy Downstream plants start their DOCSIS channels above 500 MHz, so it reduces the time to find a DOCSIS channel and lock.  Starting at 100 MHz would increase the time.  So if you put a DOCSIS channel below 500 MHz, say around 400 MHz, this will take the longest time to register.  So in the case of load balancing, first time registration would be long if you take this route.  However, a cable modem does have memory.  Typically they will remember at least the last two channels they have locked on.  So once they found that 400 MHz channel and the possible upper channel for load balancing, you should be okay.  But if you have have more than two, all bets are off depending upon your cable modem vendor.</p>
<p>Remember that you can enter in known frequencies into the config file.  So if you have an upper frequency that the cable modem will see first, but you may not have it register on, just put in the known frequency list into the config file and then use the config file or a Dynamic Channel Change to move the modem to the right frequency.  This will save your modem a lot time in searching for the correct DOCSIS frequency.  Planning ahead is always better than letting the modem wonder around your network.</p>
<p>Regards,<br />
-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Marshal</title>
		<link>http://volpefirm.com/docsis-3-0/downstream-channel-bonding/#comment-259</link>
		<dc:creator>Tom Marshal</dc:creator>
		<pubDate>Thu, 23 Sep 2010 22:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=904#comment-259</guid>
		<description>Does it make a difference where the bonded frequencies are placed in related to the narrow band forward frequency?  In other words is it better to have the narrow band frequency lower spectrum wise than say Edge QAM frequencies?   Just wondering if having Edge QAM frequencies lower may potentially increase a legacy modem&#039;s ranging time where load-balancing is present.</description>
		<content:encoded><![CDATA[<p>Does it make a difference where the bonded frequencies are placed in related to the narrow band forward frequency?  In other words is it better to have the narrow band frequency lower spectrum wise than say Edge QAM frequencies?   Just wondering if having Edge QAM frequencies lower may potentially increase a legacy modem&#8217;s ranging time where load-balancing is present.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

