Introduction
This document answers questions related to CGv6 Features supported on VSM card across different IOS-XR Releases. This document tries to list all the CGv6 on VSM related features in one place in a consolidated manner to help CGv6 on VSM customers. It does not intend to replace official IOS-XR release notes. For official release note document, please select "Release Notes for Cisco ASR 9000 Series Aggregation Services Routers for Cisco IOS-XR Software Release X.Y.Z" link for appropriate IOS-XR release.
Supported CGv6 features on VSM
A. Following table captures different CGv6 features supported on VSM and also indicates from which IOS-XR release they are supported.
| Feature Group | Feature Description | Supported on VSM from IOS-XR Release | Additional Comments |
|---|
| Generic (Common to All Applications) | Multiple CGv6 Applications on same VSM card | 5.1.1 | At present only 1 Application (NAT44) is supported, but the Architecture supports multiple CGv6 Applications (will be added in future release). |
| NAT44 | Generic / Base support | 5.1.1 | |
| | Active FTP ALG | 5.1.1 | Configurable per NAT44 instance. |
| | RTSP ALG | 5.1.1 | Configurable per NAT44 instance. |
| | PPTP ALG | 5.1.1 | Configurable per NAT44 instance. |
| | Port limit | 5.1.1 | Configurable per NAT44 instance. |
| | Netflow version 9 (NFv9) logging | 5.1.1 | Configurable per inside-VRF. |
| | Syslog logging | 5.1.1 | Configurable per inside-VRF. |
| | Bulk Port Allocation (BPA) | 5.1.1 | Configurable per inside-VRF. |
| | Destination Based Logging (DBL) | 5.1.1 | Configurable per inside-VRF. |
| | NFv9 logging with BPA | 5.1.1 | Configurable per inside-VRF. |
| | NFv9 logging with DBL | 5.1.1 | Configurable per inside-VRF |
| | Syslog loggging with BPA | 5.1.1 | Configurable per inside-VRF |
| | Syslog logging with DBL | 5.1.1 | Configurable per inside-VRF |
| | One-to-One mapping | 5.1.1 | Configurable per inside-VRF. One Public IP address is associated with maximum of one Private IP address. Multiple Private IP addresses are not mapped to single Public IP address, if this option is enabled. |
| | OutsideServiceApp mapping for inside-VRF | 5.1.1 | Configurable per inside-VRF. It is a MUST when you have multiple Outside ServiceApp interfaces inside same / single Outside VRF. |
| | Static Port Forwarding | 5.1.1 | Configurable per inside-VRF. User can specify a particular Inside/Private IP address, IP protocol and Port number which will be statically mapped to a Public IP address and Port, selected by the CGv6 Application. Usually, port number is preserved, unless there is a conflict (Port number is already in use). |
| | Endpoint Dependent Filtering (EDF) | 5.1.1 | Configurable per inside-VRF. Endpoint Independent Filtering (EIF) is also supported (default behaviour) along with this. |
| | TCP Sequence Check | 5.1.1 | Configurable per inside-VRF. |
.
A. Following table captures different supported scale numbers related to CGv6 features on VSM.
| Parameter Name | Parameter Value per VSM | Parameter Value per ASR9K Chassis | Additional Comments |
|---|
| Number of CGN/CGv6 Instances | 1 | 2 (5.1.1) | - Under one CGN/CGv6 instance, multiple CGv6 Applications (like, NAT44, DS-Lite, NAT64) are supported. Only NAT44 is supported now. Others will be supported in future.
- In future, we will support more number of CGv6 instances per ASR9K chassis
|
| Number of ServiceInfra Interfaces | 1 | 2 (5.1.1) | - ServiceInfra interface is used to send Management / Control traffic related to CGv6. Hence, only 1 ServiceInfra interface per VSM card is needed.
- In future, we will support more number of ServiceInfra interfaces per ASR9K chassis
|
| Number of ServiceApp interfaces | 256 | 256 (5.1.1) | - For running a CGv6 Application instance (like, NAT44, DS-Lite, etc.), you need a pair of ServiceApp interfaces. Hence, you can run at the most 128 CGv6 Application instances (of different types) per ASR9K.
|
| Number of NAT44 instances | 1 | 2 (5.1.1) | - Within 1 NAT44 instance, multiple Inside VRFs are possible. Several parameters can be configured on per Inside VRF.
- In future, we will support more number of NAT44 instances per ASR9K chassis
|
| Number of Stateful NAT Translations | 60 Millions | 120 Millions (5.1.1) | - NAT DB is shared across NAT44, Stateful NAT64 and DS-Lite Applications.
- In future, we will support more number NAT translations per ASR9K chassis
|
| Number of NAT Sessions | 60 Millions | 120 Millions (5.1.1) | - NAT Session DB is shared across NAT44, Stateful NAT64 and DS-Lite Applications.
- In future, we will support more number of NAT sessions per ASR9K chassis
|
| Number of NAT Users | 1 Million | 2 Millions (5.1.1) | - NAT User DB is shared across NAT44, Stateful NAT64 and DS-Lite Applications.
- In future, we will support more number of NAT users per ASR9K chassis
|
| Number of Static Port Forwarding Entries | 6,000 | 12,000 (5.1.1) | - In future, we will support more number of Static Port Forwarding entries per ASR9K chassis
|
| Number of Public IPv4 addresses | 65536 or /16 | | |
| Number of VRFs | 128 (Inside) + 128 (Outside) | > 128 (Inside) + > 128 (Outside ), as per ASR9K VRF scale | - As we support maximum of 256 ServiceApp interfaces per VSM card, at the most, we need to have 128 Inside and 128 Outside VRF. - You can have less number of Outside VRFs as well. - Please note that ASR9K supports higher number of VRFs in the chassis. This is only with respect to CGv6 Application on VSM. |
| Number of IPv4 Prefixes | Same as supported by any Typhoon-based LC. | | Related to forwarding. |
| Number of IPv6 Prefixes | Same as supported by any Typhoon-based LC. | | Related to forwarding. |
| Number of MPLS labels | Same as supported by any Typhoon-based LC. | | Related to forwarding. |
A. Please contact your Cisco Account Team or ASR9K Product Marketing team (whichever you have access to).
A. Please contact your Cisco Account Team or ASR9K Product Marketing team (whichever you have access to).
Note:
