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

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

<channel>
<title>Topic &#x27;Technical Discussion of Upstream Channel Bonding&#x27; in forum &#x27;Comcast HSI&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Technical-Discussion-of-Upstream-Channel-Bonding-27143840</link>
<description></description>
<language>en</language>
<pubDate>Sat, 25 May 2013 19:24:46 EDT</pubDate>
<lastBuildDate>Sat, 25 May 2013 19:24:46 EDT</lastBuildDate>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27152285</link>
<description><![CDATA[EnasYorl posted : <div class="bquote"><said>said by <a href="/profile/1814025" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1814025');">JPnATL</a>:</said><p>Its hard to argue about something that obviously nobody is familiar with. Their is one thing that is fact not opinion and that is 16Qam is more tolerant to noise than 32 and then 64,128 and so forth.<br> </p></div>This is true and the TDMA carrier listed is the 16QAM the other two are DOCSIS2.0/3.0 most likely 32 or 64QAM  The issue I referred to is on the US0 ATDMA carrier.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27152285</guid>
<pubDate>Wed, 16 May 2012 20:07:26 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149913</link>
<description><![CDATA[JPnATL posted : Its hard to argue about something that obviously nobody is familiar with. Their is one thing that is fact not opinion and that is 16Qam is more tolerant to noise than 32 and then 64,128 and so forth.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149913</guid>
<pubDate>Wed, 16 May 2012 02:52:10 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149476</link>
<description><![CDATA[EnasYorl posted : <div class="bquote"><said>said by <a href="/profile/1368956" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1368956');">gar187er</a>:</said><p>doesnt matter what you think....higher engineers and telecom people are doing it with success.....i work it, troubleshoot it, and make it work....its happening.....<br><br>you have them on 1 channel.....that is not a ton of noise...so please back it up.....<br><br> i would assume the 16qam is lower in the spectrum those showing more noise due to typical 5-18 garbage.....if you work in the field you know what i mean....<br> </p></div><pre class="brush: text">Pre-EQ Good                        : 559242     12225      12225     &#012;Pre-EQ Scaled                      : 2064       0          0         &#012;Pre-EQ Impulse                     : 8          2          0         &#012;Pre-EQ Direct Loads                : 19         0          0         &#012;Good Codewords rx                  : 374766003  4728886    2382610   &#012;Corrected Codewords rx             : 20311862   4280       129       &#012;Uncorrectable Codewords rx         : 361755     1744       679       &#012;Phy Operating Mode                 : atdma*     atdma*     tdma*&#012; &#012;</pre><!--end code block--><br>Simple math 0.1% of the codewords are being dropped on US0<br>5.4% of all traffic is being corrected from errors.<br><br>That is a large amount compared to US1 and US2<br><br>Not to mention that just 2% packet loss can cause robotic issues or gaming issues on UDP sessions.<br><br>Yes it's not an issue for TCP sessions.<br><br>33db SNR is not horrible but that looks like some noise in band.<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149476</guid>
<pubDate>Tue, 15 May 2012 22:51:21 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149113</link>
<description><![CDATA[gar187er posted : doesnt matter what you think....higher engineers and telecom people are doing it with success.....i work it, troubleshoot it, and make it work....its happening.....<br><br>you have them on 1 channel.....that is not a ton of noise...so please back it up.....<br><br> i would assume the 16qam is lower in the spectrum those showing more noise due to typical 5-18 garbage.....if you work in the field you know what i mean....<br><small>--<br><b>I'm better than you!</b></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149113</guid>
<pubDate>Tue, 15 May 2012 20:37:23 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149008</link>
<description><![CDATA[EnasYorl posted : US0 fighting a ton of noise there. Ton's of Corrected and Uncorrectables<br><br><pre class="brush: text">Pre-EQ Good                        : 559242     12225      12225     &#012;Pre-EQ Scaled                      : 2064       0          0         &#012;Pre-EQ Impulse                     : 8          2          0         &#012;Pre-EQ Direct Loads                : 19         0          0         &#012;Good Codewords rx                  : 374766003  4728886    2382610   &#012;Corrected Codewords rx             : 20311862   4280       129       &#012;Uncorrectable Codewords rx         : 361755     1744       679       &#012;Phy Operating Mode                 : atdma*     atdma*     tdma*&#012; &#012; &#012;</pre><!--end code block--><br>Thanks for sharing.<br><br>Reading for the geeks &raquo;<A HREF="https://www.nanog.org/meetings/nanog46/presentations/Sunday/Byju_Intro_DOCSIS_N46.pdf" >www.nanog.org/meetings/nanog46/p&middot;&middot;&middot;_N46.pdf</A><br><br>And just because you can do something  doesn't mean you should.<br><br>This hits on some of my thoughts. &raquo;<A HREF="http://www.google.com/url?sa=t&rct=j&q=throughput%20rates%20of%20qam%20&source=web&cd=4&ved=0CGYQFjAD&url=http%3A%2F%2Fpiedmontscte.org%2Fresources%2FDOCSIS_Throughput.doc&ei=8vKyT5DTCcOuiAK3mv3yAw&usg=AFQjCNES9BAzB3k2cyUTka2sabAJmIKOvw" >www.google.com/url?sa=t&rct=j&q=&middot;&middot;&middot;AJmIKOvw</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27149008</guid>
<pubDate>Tue, 15 May 2012 19:52:34 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27148314</link>
<description><![CDATA[netcool posted : <div class="bquote"><said>said by <a href="/profile/528031" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=528031');">EnasYorl</a>:</said><p>Now looking at this data from my two upsteams what modulation is Really in use  QPSK or 64 QAM?  is the Modem accurate with it's data or is it false? <br> </p></div>The modem is only using QPSK to transmit station maintenance data. All other data coming from the modem is using 64QAM. So technically it's using both.<br><br>See this for additional info on configuring modulation profiles:<br><br>&raquo;<A HREF="http://www.cisco.com/en/US/tech/tk86/tk319/technologies_tech_note09186a00800a74b0.shtml" >www.cisco.com/en/US/tech/tk86/tk&middot;&middot;&middot;b0.shtml</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27148314</guid>
<pubDate>Tue, 15 May 2012 16:07:55 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27148268</link>
<description><![CDATA[netcool posted : How about an example from a live uBR10012?<br><br><pre class="brush: text">ten01.sacramento.ca#sh cab modem aaaa.bbbb.cccc ver&#012; &#012;MAC Address                        : aaaa.bbbb.cccc&#012;IP Address                         : 96.xxx.xxx.xxx  &#012;IPv6 Address                       : ---                                    &#012;Dual IP                            : N&#012;Prim Sid                           : 255&#012;Host Interface                     : C5/0/0/UB&#012;MD-DS-SG / MD-US-SG                : 1 / 23&#012;MD-CM-SG                           : 0x117&#012;Primary Wideband Channel ID        : 259 (Wi5/0/0:2)&#012;Primary Downstream                 : Mo5/0/0:7 (RfId : 247)&#012;Wideband Capable                   : Y&#012;RCP Index                          : 3&#012;RCP ID                             : 00 10 00 00 04&#012;Multi-Transmit Channel Mode        : Y&#012;Upstream Channel                   : US0        US1        US2       &#012;Ranging Status                     : sta        sta        sta       &#012;Upstream SNR (dB)                  : 33.1       31.76      35.18     &#012;Received Power (dBmV)              : -0.50      0.50       0.00      &#012;Reported Transmit Power (dBmV)     : 44.50      45.00      45.00     &#012;Peak Transmit Power (dBmV)         : 51.00      51.00      52.00     &#012;Minimum Transmit Power (dBmV)      : 24.00      24.00      21.00     &#012;Timing Offset             (97.6 ns): 6589       6587       6590      &#012;Initial Timing Offset              : 6589       6333       6333      &#012;Rng Timing Adj Moving Avg(0.381 ns): 0          255        255       &#012;Rng Timing Adj Lt Moving Avg       : 0          249        243       &#012;Rng Timing Adj Minimum             : -256       0          0         &#012;Rng Timing Adj Maximum             : 256        65024      65792     &#012;Pre-EQ Good                        : 559242     12225      12225     &#012;Pre-EQ Scaled                      : 2064       0          0         &#012;Pre-EQ Impulse                     : 8          2          0         &#012;Pre-EQ Direct Loads                : 19         0          0         &#012;Good Codewords rx                  : 374766003  4728886    2382610   &#012;Corrected Codewords rx             : 20311862   4280       129       &#012;Uncorrectable Codewords rx         : 361755     1744       679       &#012;Phy Operating Mode                 : atdma*     atdma*     tdma*     &#012;sysDescr                           : ARRIS DOCSIS 3.0 Touchstone WideBand Cable Modem &lt;&lt;HW_REV: 3; VENDOR: Arris Interactive, L.L.C.; BOOTR: 1.2.1.25; SW_REV: 7.1.103; MODEL: WBM760A&gt;&gt;&#012; &#012;</pre><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27148268</guid>
<pubDate>Tue, 15 May 2012 15:55:31 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147358</link>
<description><![CDATA[NetFixer posted : <div class="bquote"><said>said by <a href="/profile/528031" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=528031');">EnasYorl</a>:</said><p>It is very unlikely that the 16QAM channel (Upstream4) is being bonded.  Your modem is just detecting it. One would bond similar Channel Types as they have same modulation scheme and bandwidth.<br><br>&raquo;<A HREF="http://www.cisco.com/en/US/tech/tk86/tk168/technologies_white_paper09186a0080231fc3.shtml" >www.cisco.com/en/US/tech/tk86/tk&middot;&middot;&middot;c3.shtml</A><br> </p></div>It may be "unlikely" in your opinion, but it is indeed done.<br><br>[att=1]<br><small>--<br><A HREF="http://nature-pics.com">We can never have enough of nature.</a><br>We need to witness our own limits transgressed, and some life pasturing freely where we never wander.</small><div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#FFFFFF nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/27147358?c=2002776&ret=L2ZvcnVtL3IyNzE0Mzg0MC54bWw%3D"><IMG class="apic" BORDER=0 TITLE="32272 bytes" WIDTH=600 HEIGHT=727 SRC="/r0/download/2002776.thumb600~35503a55dbcfa65957cdaab43155936b/SMCD3G_CableModemStats.png/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147358</guid>
<pubDate>Tue, 15 May 2012 11:37:31 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147259</link>
<description><![CDATA[EnasYorl posted : A interesting read as well<br>Webview<br>&raquo;<A HREF="https://docs.google.com/viewer?a=v&q=cache:9hFwQ54dNosJ:www.piedmontscte.org/resources/SCTE-Rock-Hill-SC-Planning-for-DOCSIS-30-US.ppt+bonding+D3+modem+with+16+QAM+and+64+QAM&hl=en&gl=us&pid=bl&srcid=ADGEESg27YA58k_PgXf7_Y6CRBrt_TklQSmI234UZ5hnMaEsipDNwwNlN9-Kx3DUNNtdJEvzqfkbGThZfn43AXBB9iSn23PKqyxNT4o5HxiEiVjShw18GlzUGwAYx1JYdO3kXWm6swGi&sig=AHIEtbTtyW5_vVWRcC2lI3B61pRAbDv4_Q" >docs.google.com/viewer?a=v&q=cac&middot;&middot;&middot;RAbDv4_Q</A><br><br>PPT link &raquo;<A HREF="http://www.google.com/url?sa=t&rct=j&q=bonding%20d3%20modem%20with%2016%20qam%20and%2064%20qam&source=web&cd=9&ved=0CHcQFjAI&url=http%3A%2F%2Fwww.piedmontscte.org%2Fresources%2FSCTE-Rock-Hill-SC-Planning-for-DOCSIS-30-US.ppt&ei=X22yT4KODaGRiAKDysWNAg&usg=AFQjCNHlFfmSCBXN4AKsf3ua9rfxHV8Z2A" >www.google.com/url?sa=t&rct=j&q=&middot;&middot;&middot;fxHV8Z2A</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147259</guid>
<pubDate>Tue, 15 May 2012 11:02:28 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147186</link>
<description><![CDATA[EnasYorl posted : Your LED's are BLUE or Green on US indicator?<br><br>But my point before was a TDMA carrier wouldn't be bonded based on the info I posted.  If you are bonding a channel that is meant for 1.1 DOCSIS modems and 3.0 modems seems like a poor design choice the   Return spectrum maybe has too much noise to support multiple 64QAM channels .   If both your LED's are blue DS and US, i will admit i'm blown away.<br><br>For those whom like to read more on settings in CMTS.<br><br><pre class="brush: text"> &#012;cable modulation-profile&#012; &#012;To define a modulation profile for use on the router, use the cable modulation-profile command in global configuration mode. To remove the entire modulation profile or to reset a default profile to its default values, use the no form of this command.&#012; &#012;DOCSIS 1.0 and 1.1 Mixed Mode:&#012; &#012;cable modulation-profile profile {mix | qam-16 | qpsk | robust-mix}&#012; &#012;no cable modulation-profile profile {iuc | mix | qam-16 | qpsk | robust-mix}&#012; &#012;cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len&#012; &#012;DOCSIS 1.x/2.0 Mixed Mode:&#012; &#012;cable modulation-profile profile {mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-mid | robust-mix-qam}&#012; &#012;no cable modulation-profile profile {iuc | mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-mid | robust-mix-qam}&#012; &#012;cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len&#012; &#012;DOCSIS 2.0 A-TDMA Mode:&#012; &#012;cable modulation-profile profile {mix-high | mix-low | mix-mid | mix-qam | qam-8 | qam-16 | qam-32 | qam-64 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}&#012; &#012;no cable modulation-profile profile {iuc | mix-high | mix-low | mix-mid | mix-qam | qam-8 | qam-16 | qam-32 | qam-64 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}&#012; &#012;cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len&#012; &#012;Cisco IOS Release 12.2(33)SCC and Later&#012; &#012;DOCSIS 2.0 A-TDMA Mode and DOCSIS 2.0 S-CDMA Mode:&#012; &#012;cable modulation-profile profile {mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}&#012; &#012;no cable modulation-profile profile {iuc | mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}&#012; &#012;cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len&#012; &#012;Syntax Description&#012; &#012;profile&#012; &#012;Specifies the modulation profile number. The valid values for the profile number depend on the cable interface being used and the upstream's mode of operation.&#012; &#012;See Table 1 for a list of valid ranges based on cable interface and modulation type.&#012; &#012;In Cisco IOS Release 12.2(15)CX and later releases, you can create a maximum of 10 profiles for each mode of operation, for a total of 30 profiles. In earlier software releases, you can create a maximum of 8 profiles only for DOCSIS 1.0 and DOCSIS 1.1 mode.&#012; &#012;mix&#012; &#012;(DOCSIS 1.0 and DOCSIS 1.1 mode only) Creates a default QPSK/16-QAM mix modulation profile where short and long grant bursts are sent using 16-QAM, while request, initial ranging, and station maintenance bursts are sent using QPSK). The burst parameters are set to their default values for each burst type.&#012; &#012;mix-high&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 modes only) Creates a default QPSK/64-QAM modulation profile.&#012; &#012;mix-low&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 modes only) Creates a default QPSK/16-QAM modulation profile.&#012; &#012;mix-mid&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default QPSK/32-QAM modulation profile.&#012; &#012;mix-qam&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default 16-QAM/64-QAM modulation profile.&#012; &#012;qam-8&#012; &#012;(DOCSIS 2.0 A-TDMA mode only) Creates a default 8-QAM modulation profile.&#012; &#012;This modulation profile is available in hidden and internal mode only from Cisco IOS Release 12.2(33)SCC onwards.&#012; &#012;qam-16&#012; &#012;Creates a default 16-QAM modulation profile.&#012; &#012;qam-32&#012; &#012;(DOCSIS 2.0 A-TDMA mode only) Creates a default 32-QAM modulation profile.&#012; &#012;This modulation profile is available in hidden and internal mode only from Cisco IOS Release 12.2(33)SCC onwards.&#012; &#012;qam-64&#012; &#012;(DOCSIS 2.0 A-TDMA mode only) Creates a default 64-QAM modulation profile.&#012; &#012;This modulation profile is available in hidden and internal mode only from Cisco IOS Release 12.2(33)SCC onwards.&#012; &#012;qpsk&#012; &#012;Creates a default QPSK modulation profile.&#012; &#012;robust-mix&#012; &#012;(DOCSIS 1.0 and DOCSIS 1.1 mode only) Creates a default QPSK/16-QAM modulation profile with a longer preamble that is more robust and more able to deal with noise on the upstream better than the mix profile.&#012; &#012;robust-mix-high&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default QPSK/64-QAM mixed modulation profile with a longer preamble that is more robust and more able to deal with noise on the upstream better than the mix-high profile.&#012; &#012;robust-mix-low&#012; &#012;(DOCSIS 2.0 A-TDMA mode only) Creates a default QPSK/16-QAM modulation profile with a longer preamble that is more robust and better able to deal with noise on the upstream than the mix-low profile.&#012; &#012;robust-mix-mid&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default QPSK/32-QAM modulation profile with a longer preamble that is more robust and better able to deal with noise on the upstream than the mix-mid profile.&#012; &#012;robust-mix-qam&#012; &#012;(DOCSIS 1.x/2.0 mixed mode only) Creates a default 16-QAM/64-QAM mixed modulation profile with a longer preamble that is more robust and better able to deal with noise on the upstream than the mix-qam profile.&#012; &#012;iuc&#012; &#012;Interval usage code. Valid entries depend on the mode of operation:&#012; &#012;&amp;#149;If the upstream is configured for DOCSIS 1.0 and DOCSIS 1.1 modulation profiles, the valid values are initial, long, request, reqdata, short, or station.&#012; &#012;&amp;#149;If the upstream is configured for DOCSIS 1.x and DOCSIS 2.0 mixed modulation profiles, the valid values are a-long, a-short, a-ugs, initial, long, request, reqdata, short, or station.&#012; &#012;&amp;#149;If the upstream is configured for DOCSIS 2.0 A-TDMA modulation profiles, the valid values are a-long, a-short, a-ugs, initial, long, request, reqdata, short, or station.&#012; &#012;The reqdata burst type is included as a placeholder for scripts that might reference it, but the DOCSIS MAC scheduler on the Cisco CMTS does not use this type of burst.&#012; &#012;When you are using the initial and station bursts for DOCSIS 2.0 A-TDMA mode, qam-8, qam-32, and qam-64 modulation profiles are available in hidden mode only.&#012; &#012;preamble&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and a-short options) Specifies the preamble format. Valid values are qpsk0 and qpsk1.&#012; &#012;rs-interleave-depth&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and a-short options) Specifies the RS interleave depth. The valid range is from 0 to 114.&#012; &#012;rs-interleave-block&#012; &#012;(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and a-short options) Specifies the RS interleave block size. The valid range is from 18 to 2048.&#012; &#012;fec-tbytes&#012; &#012;The number of bytes that can be corrected per FEC code word. For DOCSIS 1.0 and DOCSIS 1.1 mode, valid values are from 0 to 10 (decimal), where 0 means no FEC. For DOCSIS 2.0 A-TDMA mode, the valid values are from 0 to 16 (decimal), where 0 means no FEC.&#012; &#012;fec-len&#012; &#012;FEC code-word length. Valid values are from 16 to 253.&#012; &#012;burst-len&#012; &#012;Maximum burst length in minislots. Valid values are from 0 to 255, where 0 means no limit.&#012; &#012;guard-t&#012; &#012;Guard time in symbols. The time between successive bursts, with a range from 22 to 255. (In Cisco IOS Release 12.2(15)BC2 and earlier releases, the minimum guard time was 0 symbols, but we do not recommend using a guard time smaller than 22 symbols.)&#012; &#012;mod&#012; &#012;Modulation. Valid entries are 16qam and qpsk for DOCSIS 1.0 and DOCSIS 1.1 upstreams. Valid entries are 8qam, 16qam, 32qam, 64qam, and qpsk for DOCSIS 2.0 upstreams.&#012; &#012;The qam-8, qam-32, and qam-64 modulation profiles are available in hidden and internal modes only from Cisco IOS Release 12.2(33)SCC onwards.&#012; &#012;scrambler&#012; &#012;Enable or disable scrambler. Valid entries are scrambler and no-scrambler.&#012; &#012;seed&#012; &#012;(Required if scrambler option used) Scrambler seed in hexadecimal format. Valid values are from 0x0 to 0x7FFF.&#012; &#012;diff&#012; &#012;Enable or disable differential encoding. Valid entries are diff and no-diff.&#012; &#012;In DOCSIS 2.0 mode, differential encoding cannot be enabled for the 8-QAM, 32-QAM, and 64-QAM modulations.&#012; &#012;The qam-8, qam-32, and qam-64 modulation profiles are available in hidden and internal modes only from Cisco IOS Release 12.2(33)SCC onwards.&#012; &#012;pre-len&#012; &#012;Preamble length in bits. Valid values are from 2 to 256.&#012; &#012;last-cw&#012; &#012;Handling of FEC for last code word. Valid entries are fixed for fixed code-word length and shortened for shortened last code word.&#012; &#012;uw-len&#012; &#012;Upstream unique word length. Enter uw8 for 8-bit unique code words or uw16 for 16-bit unique code words.&#012; &#012;Command Default&#012; &#012;Modulation profile 1 is defined as a qpsk Time Division Multiple Access (TDMA) profile.&#012; &#012;In Cisco IOS Release 12.2(15)CX, Release 12.2(15)BC2 and later releases, additional modulation profiles are defined as the default mixed TDMA/A-TDMA profile and the default Advanced TDMA (A-TDMA) profile. See Table 1 for a list of valid ranges based on cable interface and modulation type.&#012; &#012;Command Modes&#012; &#012;Global configuration (config)&#012; &#012;Command History&#012; &#012;</pre><!--end code block-->http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_06_cable_m.html]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147186</guid>
<pubDate>Tue, 15 May 2012 10:42:08 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147177</link>
<description><![CDATA[gar187er posted : up bonding does indeed make use of the 16qam.....equalization on that same 16qam is not always turned on, so nodes with noise behind  it will still have issues that the modem cannot overcome.<br><small>--<br><b>I'm better than you!</b></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147177</guid>
<pubDate>Tue, 15 May 2012 10:38:03 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147048</link>
<description><![CDATA[anon posted : My modem in Aurora Colorado has shown 64qam and 16qam bonded for a loooong time now, maybe over a year<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#FFFFFF nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/27147048?c=2002760&ret=L2ZvcnVtL3IyNzE0Mzg0MC54bWw%3D"><IMG class="apic" BORDER=0 TITLE="77379 bytes" WIDTH=600 HEIGHT=477 SRC="/r0/download/2002760.thumb600~51f955ba223927161749a09bba8b85ed/cm.png/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27147048</guid>
<pubDate>Tue, 15 May 2012 10:01:44 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27146634</link>
<description><![CDATA[EnasYorl posted : <div class="bquote"><said>said by <a href="/profile/1594001" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1594001');">netcool</a>:</said><p><div class="bquote"><said>said by <a href="/profile/528031" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=528031');">EnasYorl</a>:</said><p>So in short maybe it can be done in a lab (I've yet to see anyone show it done), but I would bet money that no one bonds those different modulation schemes in the real world deployment.<br> </p></div>You would lose that bet. <br><br>Look through this thread, many many people have bonded channels using different modulation profiles. <br><br>I myself have two channels bonded, one TDMA and one ATDMA. It also helps that I can login to the CMTS to verify as well ;)<br> </p></div>So in GW, CO you are saying your bonding 1.1 and 2.0 upstreams?<br><br>  Care to show your modem?<br><br><pre class="brush: text">DownstreamBonding Channel Value&#012;Channel ID101 102 103 104 &#012;Frequency567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz &#012;Signal to Noise Ratio35 dB 35 dB 35 dB 35 dB &#012;Downstream ModulationQAM256 QAM256 QAM256 QAM256 &#012;Power Level&#012;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&#012;-3 dBmV  -3 dBmV  -4 dBmV  -4 dBmV  &#012;UpstreamBonding Channel Value&#012;Channel ID4 3 &#012;Frequency22800000 Hz 32400000 Hz &#012;Ranging Service ID7409 7409 &#012;Symbol Rate5.120 Msym/sec 5.120 Msym/sec &#012;Power Level49 dBmV 49 dBmV &#012;Upstream Modulation&#91;3&#93; QPSK&#012;&#91;3&#93; 64QAM&#012; &#91;3&#93; QPSK&#012;&#91;3&#93; 64QAM&#012; &#012;Ranging StatusSuccess Success &#012;Signal Stats (Codewords)Bonding Channel Value&#012;Channel ID101 102 103 104 &#012;Total Unerrored Codewords197599661448 25800590019 25800424592 25800201713 &#012;Total Correctable Codewords2663474 3045577 3211190 3432391 &#012;Total Uncorrectable Codewords2718 2495 2439 1619 &#012; &#012;</pre><!--end code block--><br>Now looking at this data from my two upsteams what modulation is Really in use  QPSK or 64 QAM?  is the Modem accurate with it's data or is it false?  I can tell you for a long time I had both carriers present but they were not bonded until recently as my modem is one of the few that will indicate true bonding.<br><br>Upstream	Bonding Channel Value<br>Channel ID	4 	3 <br>Frequency	22800000 Hz 	32400000 Hz <br>Ranging Service ID	7409 	7409 <br>Symbol Rate	5.120 Msym/sec 	5.120 Msym/sec <br>Power Level	49 dBmV 	49 dBmV <br>Upstream Modulation	[3] QPSK<br>[3] 64QAM<br> 	[3] QPSK<br>[3] 64QAM<br><br>I will throw in the CMTS command info as well<br><pre class="brush: text">cable upstream docsis-mode&#012; &#012;To configure an upstream to use DOCSIS 1.x, DOCSIS 2.0 or DOCSIS 3.0 modulation profiles, use the cable upstream docsis-mode command in cable interface configuration mode. To reset the upstream to its default configuration, use the no form of this command.&#012; &#012;cable upstream n docsis-mode {atdma | scdma | scdma-d3 | tdma | tdma-atdma}&#012; &#012;no cable upstream n docsis-mode {atdma | scdma | scdma-d3 | tdma | tdma-atdma}&#012; &#012;Syntax Description&#012; &#012;n&#012; &#012;Specifies the upstream port. Valid values start with 0 for the first upstream port on the cable interface line card.&#012; &#012;atdma&#012; &#012;Configures the upstream only for DOCSIS 2.0 Advanced Time Division Multiple Access (A-TDMA) modulation profiles.&#012; &#012;scdma&#012; &#012;Configures the upstream for DOCSIS 2.0 Synchronous Code Division Multiple Access (S-CDMA) modulation profiles only.&#012; &#012;scdma-d3&#012; &#012;Configures the upstream for DOCSIS 3.0 S-CDMA modulation profiles. The scdma-d3 option uses channel type 4SR mode.&#012; &#012;tdma&#012; &#012;Configures the upstream only for DOCSIS 1.0/DOCSIS 1.1 Time Division Multiple Access (TDMA) modulation profiles (default).&#012; &#012;tdma-atdma&#012; &#012;Configures the upstream for both A-TDMA and TDMA operations (mixed mode). If you are using abbreviations at the command line, you must specify at least the tdma to select the mixed mode. If you choose a shorter abbreviation, you select TDMA-only mode.&#012; &#012;Command Default&#012; &#012;All upstreams are configured TDMA-only mode (DOCSIS 1.0/DOCSIS 1.1).&#012; &#012;Command Modes&#012; &#012;Interface configuration (config-if)&#012; &#012;Command History&#012; &#012;Release&#012;Modification&#012;12.2(15)CX&#012; &#012;This command was introduced to support DOCSIS 2.0 A-TDMA and mixed modulation profiles on the Cisco uBR-MC16U/X and Cisco uBR-MC28U/X cable interface line card on the Cisco uBR7246VXR router.&#012; &#012;12.2(15)BC2&#012; &#012;Support was added for the Cisco uBR-MC5X20S/U cable interface line cards on the Cisco uBR10012 router.&#012; &#012;12.3BC&#012; &#012;This command was integrated into Cisco IOS Release 12.3BC.&#012; &#012;12.2(33)SCA&#012; &#012;This command was integrated into Cisco IOS Release 12.2(33)SCA.&#012; &#012;12.2(33)SCC&#012; &#012;This command was modified with the addition of scdma and scdma-d3 keyword options and support was added for the Cisco UBR-MC20X20V cable interface line card on the Cisco uBR10012 router.&#012; &#012;Usage Guidelines&#012; &#012;The DOCSIS 2.0 specification builds on the existing TDMA to support advanced modulation profiles that increase potential upstream bandwidth. The A-TDMA profiles support higher QAM rates of up to 64-QAM and wider channel widths of up to 6.4 MHz (5.12 Msymbols).&#012; &#012;NoteThe advanced hardware-based spectrum management features for the Cisco uBR-MC16S/U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC5X20S/U cards are supported only in the DOCSIS 1.0/1.1 TDMA-only mode. They cannot be used in the mixed or A-TDMA-only modes.&#012;The DOCSIS 2.0 specification allows an upstream to be configured in one of the following three modes:&#012; &#012;&amp;#149;A-TDMA only mode&amp;#151;Upstreams only support cable modems that register using A-TDMA modulation profiles. The CMTS does not allow DOCSIS 1.0 and DOCSIS 1.1 cable modems to register and come online on these upstreams. The Cisco uBR-MC5X20S/U, Cisco uBR-MC16U/X, and Cisco uBR-MC28U/X cards also support 6,400,000 Hz (5,120,000 symbols/sec) when operating in DOCSIS 2.0 (A-TDMA-only) mode.&#012; &#012;Changing the DOCSIS mode to A-TDMA only mode automatically changes the symbol rate to 5.12 megasymbols per second and the channel width to 6.4 MHz. It also automatically disables the dynamic upstream modulation.&#012; &#012;In addition, the following are required to support the DOCSIS 2.0 A-TDMA features:&#012; &#012;&amp;#150;Cable modems must be DOCSIS 2.0 compliant.&#012; &#012;&amp;#150;The DOCSIS configuration file for the cable modem must either omit the DOCSIS 2.0 Enable field (TLV 39), or it must set TLV 39 to 1 (enable). If you set TLV 39 to 0 (disable), a DOCSIS 2.0 CM uses the TDMA mode.&#012; &#012;&amp;#150;The upstream must be configured for either A-TDMA-only or mixed TDMA/A-TDMA mode.&#012; &#012;&amp;#149;TDMA-only mode&amp;#151;Upstreams only support cable modems that register using TDMA modulation profiles. DOCSIS 2.0 cable modems can register on these upstreams only by using a DOCSIS 1.0/DOCSIS 1.1 modulation profile (which typically would happen only when a DOCSIS 2.0 cable modem cannot find an A-TDMA channel in its DOCSIS domain).&#012; &#012;Changing the DOCSIS mode to TDMA-only mode automatically changes the symbol rate to 1.28 megasymbols per second and the channel width to 3.2 MHz. It also automatically disables the dynamic upstream modulation.&#012; &#012;&amp;#149;Mixed mode&amp;#151;Upstreams support both DOCSIS 1.0/DOCSIS 1.1 cable modems using TDMA modulation profiles and DOCSIS 2.0 cable modems using A-TDMA modulation profiles. (The maximum channel width in mixed mode is 3.2 MHz.)&#012; &#012;Changing the DOCSIS mode to mixed mode also automatically changes the symbol rate to 1.28 megasymbols per second and the channel width to 3.2 MHz. Dynamic upstream modulation is also automatically disabled.&#012; &#012;NoteMixed mode upstreams do not support the 6.4 MHz channel width.&#012;The DOCSIS 3.0 specification allows an upstream to be configured in one of the following modes:&#012; &#012;&amp;#149;SCDMA-d3 mode&amp;#151;Upstreams only support cable modems that register using DOCSIS 3.0 S-CDMA modulation profiles.&#012; &#012;&amp;#149;SCDMA mode&amp;#151;Upstreams only support cable modems that register using DOCSIS 2.0 S-CDMA modulation profiles.&#012; &#012;NoteThe DOCSIS 3.0 option scdma-d3 (4SR) is available only when the CMTS is configured to operate in the global modulation profile format and is not available in the default mode. This option is available only for the Cisco UBR-MC20X20V cable interface line card, and not for other legacy line cards.&#012;Refer to the cable upstream channel-width command for valid values of supported channel widths and DOCSIS modes for cable interfaces.&#012; &#012;</pre><!--end code block-->http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_10_cable_u_to_cable_w.html#wp1090928<br><br>Based on the vendor information I don't believe you've proven your point.<br><br>Especially when scdma-d3 is what is needed to bond.<br><br>  <br>Configures the upstream for DOCSIS 3.0 S-CDMA modulation profiles. The scdma-d3 option uses channel type 4SR mode.<br>  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27146634</guid>
<pubDate>Tue, 15 May 2012 04:25:21 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27146466</link>
<description><![CDATA[netcool posted : <div class="bquote"><said>said by <a href="/profile/528031" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=528031');">EnasYorl</a>:</said><p>So in short maybe it can be done in a lab (I've yet to see anyone show it done), but I would bet money that no one bonds those different modulation schemes in the real world deployment.<br> </p></div>You would lose that bet. <br><br>Look through this thread, many many people have bonded channels using different modulation profiles. <br><br>I myself have two channels bonded, one TDMA and one ATDMA. It also helps that I can login to the CMTS to verify as well ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27146466</guid>
<pubDate>Tue, 15 May 2012 00:17:17 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27146313</link>
<description><![CDATA[EnasYorl posted : Well there are many reasons to not bond different types of carrier.<br><br>excerpts from my link.<br><br><pre class="brush: text">Preambles and Constellations&#012; &#012;Another key point is that ATDMA preambles are always Quadrature Phase-Shift Keying (QPSK) 0 or 1, where 0 denotes a low-power preamble and 1 denotes a high-power preamble. Original 1.x CMs use a preamble that is the same as the data, whether it is QPSK or 16-QAM. Because the preamble was a consistent pattern between two symbol landings, it was essentially bi-phase shift keying (BPSK). Figure 4 shows the new ATDMA preamble constellations.&#012; &#012;Figure 4 â&amp;#128;&amp;#147; ATDMA Preamble Constellations&#012; &#012;</pre><!--end code block--><br>And<br><br><pre class="brush: text">All commands and command outputs are as seen on a uBR10k running Cisco IOS Software Release 12.2(15)BC2a. While in the cable interface configuration, the US port can be assigned a docsis-mode as shown in this example:&#012; &#012;ubr10k(config-if)# cable upstream 0 docsis-mode ?&#012; &#012;  atdma       DOCSIS 2.0 ATDMA-only channel&#012;  tdma        DOCSIS 1.x-only channel&#012;  tdma-atdma  DOCSIS 1.x and DOCSIS 2.0 mixed channel&#012;If ATDMA mode is selected, 1.x CMs should not even range on this US, and this information is displayed:&#012; &#012;ubr10k(config-if)# cable upstream 0 docsis-mode atdma&#012; &#012;%Docsis mode set to ATDMA-only (1.x CMs will go offline)&#012;%Modulation profile set to 221&#012;These channel widths are available:&#012; &#012;ubr10k(config-if)# cable upstream 0 channel-width ?&#012; &#012;  1600000     Channel width 1600 kHz, symbol rate 1280 ksym/s&#012;  200000      Channel width 200 kHz, symbol rate 160 ksym/s&#012;  3200000     Channel width 3200 kHz, symbol rate 2560 ksym/s&#012;  400000      Channel width 400 kHz, symbol rate 320 ksym/s&#012;  6400000     Channel width 6400 kHz, symbol rate 5120 ksym/s&#012;  800000      Channel width 800 kHz, symbol rate 640 ksym/s&#012;If a 6.4 MHz channel width is selected, the minislot changes automatically to 1 tick, and this information is displayed:&#012; &#012;ubr10k(config-if)# cable upstream 0 channel-width 6400000&#012; &#012;%With this channel width, the minislot size is now changed to 1 tick&#012;Verify the interface settings with the show controller command:&#012; &#012;ubr10k# show controller cable6/0/0 upstream 0&#012; &#012;Cable6/0/0 Upstream 0 is up&#012;Frequency 16 MHz, Channel Width 6.400 MHz, 64-QAM Symbol Rate 5.120 Msps&#012;This upstream is mapped to phy port 0&#012;Spectrum Group is overridden&#012;SNR - Unknown - no modems online.&#012;Nominal Input Power Level 0 dBmV, Tx Timing Offset 0&#012;Ranging Backoff auto (Start 0, End 3)&#012;Ranging Insertion Interval auto (60 ms)&#012;Tx Backoff Start 3, Tx Backoff End 5&#012;Modulation Profile Group 221&#012;Concatenation is enabled&#012;Fragmentation is enabled&#012;part_id=0x0952, rev_id=0x00, rev2_id=0x00&#012;nb_agc_thr=0x0000, nb_agc_nom=0x0000&#012;Range Load Reg Size=0x58&#012;Request Load Reg Size=0x0E&#012;Minislot Size in number of Ticks is = 1&#012;Minislot Size in Symbols = 32&#012;Bandwidth Requests = 0x0&#012;Piggyback Requests = 0x0&#012;Invalid BW Requests= 0x0&#012;Minislots Requested= 0x0&#012;Minislots Granted  = 0x0&#012;Minislot Size in Bytes = 24&#012;Map Advance (Dynamic) : 2180 usecs&#012;UCD Count = 313435&#012;ATDMA mode enabled&#012; &#012;</pre><!--end code block--><br>Also there level differences when using different modulation schemes.<br><br>This article talks more about the modulation power of bonding channels. &raquo;<A HREF="http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/ubr_uscb.html#wp1181735" >www.cisco.com/en/US/docs/ios/cab&middot;&middot;&middot;p1181735</A><br><br><pre class="brush: text">Dynamic Range Window and Transmit Power Levels for Upstream Channel Bonding&#012; &#012;The dynamic range window functionality is based on the CableLabs DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification and DOCSIS 3.0 Specification. This requires a DOCSIS 3.0 CM to have upstream transmit channel power level within a 12 dB range for all channels in its transmit channel set (TCS).&#012; &#012;DOCSIS 1.x or 2.0 CMs operating with a single upstream channel, in non-MTC mode, have a higher maximum transmit power level than DOCSIS 3.0 CMs operating in the MTC mode with two or more upstream channels. That is, the maximum transmit power level per channel is reduced in the MTC mode.&#012; &#012;When the upstream attenuation exceeds the maximum transmit power level, a DOCSIS 3.0 CM attempting to register in the MTC mode may fail to come online, or register in partial mode. The CM fails to register when the transmit power level of all upstream channels in its TCS exceeds the maximum transmit power level. If the CM has some upstream channels that are within the maximum transmit power level, the CM may come online in partial mode. However, the upstream channels that exceed the maximum transmit power level are marked as down and cannot be used for upstream traffic.&#012; &#012;To verify the transmit power levels on a CM, use the show cable modem command with the verbose keyword. This command displays the following transmit power values for each assigned upstream channel:&#012; &#012;â&amp;#128;¢Reported Transmit Powerâ&amp;#128;&amp;#148;This is the reported transmit power level by the CM for each upstream channel.&#012; &#012;â&amp;#128;¢Minimum Transmit Powerâ&amp;#128;&amp;#148;This is the minimum transmit power level that the CM in the MTC mode could transmit at for the upstream channel.&#012; &#012;â&amp;#128;¢Peak Transmit Powerâ&amp;#128;&amp;#148;This is the maximum transmit power level that the CM in the MTC mode could transmit at for the upstream channel.&#012; &#012;To support upstream channel bonding, the minimum transmit power must be less than or equal to the reported transmit power, and the reported transmit power must be less than or equal to the peak transmit power. The peak transmit power and minimum transmit power levels are derived from the CM TCS assignment and each individual upstream channel configuration.&#012; &#012;If the minimum transmit power is higher than the reported transmit power, or the reported transmit power is higher than the peak transmit power, the CM may not come online or may register in partial mode.&#012; &#012;You can troubleshoot this transmit power problem in the following two ways:&#012; &#012;â&amp;#128;¢Insert an additional amplifier to reduce the upstream attenuation so that the upstream transmit power falls within the allowed transmit power range (12 dB).&#012; &#012;â&amp;#128;¢Disable the MTC mode. To switch the CM from the MTC mode to non-MTC mode, disable the bonded-bit (bit-0) in type, length, value (TLV) 43.9.3 using the CM configuration file.&#012; &#012; &#012;</pre><!--end code block--><br>So in short maybe it can be done in a lab (I've yet to see anyone show it done), but I would bet money that no one bonds those different modulation schemes in the real world deployment.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27146313</guid>
<pubDate>Mon, 14 May 2012 22:47:45 EDT</pubDate>
</item>

<item>
<title>Re: Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27144084</link>
<description><![CDATA[EG posted : <div class="bquote"><said>said by <a href="/profile/528031" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=528031');">EnasYorl</a>:</said><p>It is very unlikely that the 16QAM channel (Upstream4) is being bonded.  Your modem is just detecting it. One would bond similar Channel Types as they have same modulation scheme and bandwidth.<br><br>&raquo;<A HREF="http://www.cisco.com/en/US/tech/tk86/tk168/technologies_white_paper09186a0080231fc3.shtml" >www.cisco.com/en/US/tech/tk86/tk&middot;&middot;&middot;c3.shtml</A><br> </p></div>Please point out something specific in that article. My understanding has been that dissimilar channels can indeed be bonded.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Technical-Discussion-of-Upstream-Channel-Bonding-27144084</guid>
<pubDate>Mon, 14 May 2012 10:22:18 EDT</pubDate>
</item>

<item>
<title>Technical Discussion of Upstream Channel Bonding</title>
<link>http://www.dslreports.com/forum/Technical-Discussion-of-Upstream-Channel-Bonding-27143840</link>
<description><![CDATA[EnasYorl posted : <small> Split from <a href=/forum/remark,26047253>this topic</a>.<br>The original post in this topic is a reply to<a href=/forum/remark,27143312> this post</a>. ~sorto' </small><br><br>It is very unlikely that the 16QAM channel (Upstream4) is being bonded.  Your modem is just detecting it. One would bond similar Channel Types as they have same modulation scheme and bandwidth.<br><br>&raquo;<A HREF="http://www.cisco.com/en/US/tech/tk86/tk168/technologies_white_paper09186a0080231fc3.shtml" >www.cisco.com/en/US/tech/tk86/tk&middot;&middot;&middot;c3.shtml</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Technical-Discussion-of-Upstream-Channel-Bonding-27143840</guid>
<pubDate>Mon, 14 May 2012 08:54:06 EDT</pubDate>
</item>

</channel>
</rss>
