Friday, September 18, 2020

CGN Deployment Advice

We're a small service provider that has been been native dual stack since early 2014. However, we are now approaching IPv4 address exhaustion (a /19 and a /20 today).

Though we're contemplating purchasing an additional /22 - /20 to kick the can a little further down the road, in the long term, CGN seems unavoidable.

As a result I would be appreciative to hear from other service providers, universities, etc that have already implemented CGN.

In particular what does it absolutely break, and can you provide any tips, tricks or configuration recommendations to make it less painful?

Presently I'm investigating configuring CGN directly on our CMTS (Cisco cBR-8 with SUP160s running IOS-XE). We would need to support about 10,000 subscribers, but as of this writing I am unsure if it's up to the task.

I haven't ruled out a dedicated CGN appliance if those have more horsepower or better features than letting our CMTS or an ASR do the job.

Once we ultimately deploy CGN we will still have native IPv6 and will offer a static IPv4 adddress to those that ABSOLUTELY need it.



No comments:

Post a Comment