Cisco I-CMTS Design and Implementation for DOCSIS 3 migration | docsis.org

You are here

Cisco I-CMTS Design and Implementation for DOCSIS 3 migration

9 posts / 0 new
Last post
ragent
Cisco I-CMTS Design and Implementation for DOCSIS 3 migration

Hello, colleagues!
We're small ISP with uBR 10012 (12.2(33)SCD6) +PRE2 +8 20x20v cards running DOCSIS 2.0. We're going to migrate our cable users into 3.0
Will migration be possible with these limitations ?
1. we have only 5 frequencies to operate DS streams;
2. each 20x20v card running 5ds 20 us license.
We are going to bond all 5 available ds channels on each 20x20v card and put them in separate MAC domain.
Any suggestions would be highly appreciated!

mbowe
I wouldn't recommend this.

I wouldn't recommend this. The 5x20 licence isn't a good choice for this application.

Are you planning of creating just 1 mac domain per card, with 5 x primary DS in the mac domain? Beware that you can have a max of 8 US per mac domain, so you are going to strand a heap of your US.

Instead you could create 5 x mac domains, each having 1 x primary, and then add the remaining DS as non-primary.

Obviously you would be a lot better off with a full 20x20 licence, as that is the whole idea of D3, where you at least quadruple the DS density. The 20x20 is the D3 version of the previous generation 5x20 D2 card. You can buy 20x20 cards pretty cheap these days from ebay/brokers.

5x20 cards are more targeted for use in D2 deployment, or for D3 use when paired up with SPA-24XDS-SFP and edgeqam

ragent
Hi, mbowe!

Hi, mbowe!
I saw a lot of your valuable comments in this forum and highly appreciate your contribution!
Mostly yes, the plan is to create one MAC domain per card. We targeted to reach 100 Mb/s of speed per CM.
About licensing. I suppose it might be easier/cheaper to buy additional DS license rather than replace a line card? I mean we could add 15 DS license on each card and will have 20 DS 20 US per MC20X20V.

What's more - we're limited in frequencies, available to transmit the data. Actually we have only 5 channels.
Might it be reasonable to let's say bond what we have or we should rather discuss to get more channels available?

ragent
As you can see we rather

As you can see we rather limited both technically and technologically. The ultimate goal for our migration - give our customers rather higher speeds in current limits.

mbowe
4 or 5 DS frequencies is OK

4 or 5 DS frequencies is OK to achieve 100Mbps. But if you could shuffle the TV channels around to provide a block of 8 freqs for the CMTS that would be ideal.

With only 5 DS frequencies, I would look to split a fully licenced 20x20 card into 5 MAC domains, and send 4 unique DS channels to each mac domain.

With 8 DS frequencies I would look to split the 20x20 card into 4 MAC domains, but this time send 4 unique DS channels to each mac domain plus span the remaining 4 DS across the 4 mac domains, to provide support for 8 way bonding groups.

Although these proposals would depend on how many nodes and forward lasers you have. Ideally each mac domain would be connected to a distinct group of forward lasers / nodes.

Note, it may be cheaper to buy a whole 20x20 card than to upgrade your licences. These cards are becoming quite common now, as operators are upsizing to the 3G60.

ragent
mbowe thank you

mbowe thank you for such a valuable comments!
Once more we have only 5 DS and 20 US license per MC20X20V card.
So for now config looks like this:
controller Integrated-Cable 5/0/0
rf-channel 0 cable downstream channel-id 1
rf-channel 0 frequency 834000000 annex A modulation 256qam interleave 12
rf-channel 0 rf-power 52.0
no rf-channel 0 rf-shutdown
rf-channel 1 cable downstream channel-id 2
rf-channel 1 frequency 842000000 annex A modulation 256qam interleave 12
rf-channel 1 rf-power 52.0
rf-channel 1 rf-shutdown
rf-channel 2 cable downstream channel-id 3
rf-channel 2 frequency 850000000 annex A modulation 256qam interleave 12
rf-channel 2 rf-power 52.0
rf-channel 2 rf-shutdown
rf-channel 3 cable downstream channel-id 4
rf-channel 3 frequency 858000000 annex A modulation 256qam interleave 12
rf-channel 3 rf-power 52.0
rf-channel 3 rf-shutdown
!
controller Integrated-Cable 5/0/1
rf-channel 0 cable downstream channel-id 5
rf-channel 0 frequency 842000000 annex A modulation 256qam interleave 12
rf-channel 0 rf-power 52.0
no rf-channel 0 rf-shutdown
rf-channel 1 cable downstream channel-id 6
rf-channel 1 frequency 850000000 annex A modulation 256qam interleave 12
rf-channel 1 rf-power 52.0
rf-channel 1 rf-shutdown
rf-channel 2 cable downstream channel-id 7
rf-channel 2 frequency 858000000 annex A modulation 256qam interleave 12
rf-channel 2 rf-power 52.0
rf-channel 2 rf-shutdown
rf-channel 3 cable downstream channel-id 8
rf-channel 3 frequency 866000000 annex A modulation 256qam interleave 12
rf-channel 3 rf-power 52.0
rf-channel 3 rf-shutdown
!
controller Integrated-Cable 5/0/2
rf-channel 0 cable downstream channel-id 9
rf-channel 0 frequency 850000000 annex A modulation 256qam interleave 12
rf-channel 0 rf-power 52.0
no rf-channel 0 rf-shutdown
rf-channel 1 cable downstream channel-id 10
rf-channel 1 frequency 858000000 annex A modulation 256qam interleave 12
rf-channel 1 rf-power 52.0
rf-channel 1 rf-shutdown
rf-channel 2 cable downstream channel-id 11
rf-channel 2 frequency 866000000 annex A modulation 256qam interleave 12
rf-channel 2 rf-power 52.0
rf-channel 2 rf-shutdown
rf-channel 3 cable downstream channel-id 12
rf-channel 3 frequency 874000000 annex A modulation 256qam interleave 12
rf-channel 3 rf-power 52.0
rf-channel 3 rf-shutdown
!
controller Integrated-Cable 5/0/3
rf-channel 0 cable downstream channel-id 13
rf-channel 0 frequency 858000000 annex A modulation 256qam interleave 12
rf-channel 0 rf-power 56.0
no rf-channel 0 rf-shutdown
rf-channel 1 cable downstream channel-id 14
rf-channel 1 frequency 866000000 annex A modulation 256qam interleave 12
rf-channel 1 rf-power 56.0
rf-channel 1 rf-shutdown
rf-channel 2 cable downstream channel-id 15
rf-channel 2 frequency 874000000 annex A modulation 256qam interleave 12
rf-channel 2 rf-power 56.0
rf-channel 2 rf-shutdown
rf-channel 3 cable downstream channel-id 16
rf-channel 3 frequency 882000000 annex A modulation 256qam interleave 12
rf-channel 3 rf-power 56.0
rf-channel 3 rf-shutdown
!
controller Integrated-Cable 5/0/4
rf-channel 0 cable downstream channel-id 17
rf-channel 0 frequency 866000000 annex A modulation 256qam interleave 12
rf-channel 0 rf-power 52.0
no rf-channel 0 rf-shutdown
rf-channel 1 cable downstream channel-id 18
rf-channel 1 frequency 874000000 annex A modulation 256qam interleave 12
rf-channel 1 rf-power 52.0
rf-channel 1 rf-shutdown
rf-channel 2 cable downstream channel-id 19
rf-channel 2 frequency 882000000 annex A modulation 256qam interleave 12
rf-channel 2 rf-power 52.0
rf-channel 2 rf-shutdown
rf-channel 3 cable downstream channel-id 20
rf-channel 3 frequency 890000000 annex A modulation 256qam interleave 12
rf-channel 3 rf-power 52.0
rf-channel 3 rf-shutdown
!
can we realise bonding with that?
Physically each card (e.g. 5/0, 5/1 etc) connected to separate laser

ragent
mbowe, we have only 5DS20US

mbowe, we have only 5DS20US licensed cards, and each card connected to its own forward laser

ragent
for you convenience I

for you convenience I uploaded running conf here: http://pastebin.com/LEVgfKZq
Could you please review it?
I doubt about mistekes in config, especially in 'cable fiber-node' section

ragent
dear colleagues, your

dear colleagues, your comments will be highly appreciated

Log in or register to post comments