You are here

Problem Channel-Bonding MC20X20V

4 posts / 0 new
Last post
Problem Channel-Bonding MC20X20V
Plain text icon config.txt7.12 KB


           I have the following situation. CMTS cisco ubr10k configured with 8 downstream channels and 2 upstream channels in bonding. I want to increase 4 more downstream channels but due to space problems in the spectrum the frequencies will be very high and can not be part of the bonding for only 1.x and 2.0 docsis cables.

            I made config file attachments and some docsis 3.0 cables are registering as 2.0. only take 1 downstream and upstream channel. What could be wrong? Is there any way out of my case?

Thank you, Flavio.

The fiber node stanza needs

The fiber node stanza needs to include all interfaces that are connected to this node, so the 5/1/2 needs to be included there.

You could ban the DOCSIS 3.0 modems from using the 4 x high frequency channels by using attribute masks.
Eg apply a provisioned-mask of F to the interface integrated-cable 5/1/2:x, and put forbidden-mask of F in the D3.0 CM config files.

Next, since the D2.0 modems can now use the new high frequency channels, you could free up capacity on the low frequency channels for D3.0 modems by making 5/1/0 or 5/1/1 not be primary enabled. This means the D2.0 modems wont register there, and you have bonus of saving all the SYNC/MAP/UCD overhead. D3.0 modems can still use the non-primary channels as part of the bonding group.

Another option

You may also be able to ban the D3.0 modems from the high frequency channels with this command

cable service attribute ds-bonded downstream-type bonding-enabled enforce

I haven't tested it personally though

okay i tested the first

okay i tested the first method and it worked very well. I got a docsis 2.0 cable to register in the downstream that left no attribute masks. in the file I left CM Downstream Forbidden Attribute Mask: 8000000F. of 12 downstream frequencies I did the cable modem register in the downstream I wanted. first it registered in any downstream and soon after was offline and recorded in the correct downstream,

I'm going to test this second method, it's a lot easier.

Thank you, Flavio.