Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x First Published: 2016-07-01 Last Modified: 2014-10-01 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
362
Embed
Cisco ASR 9000 Series Aggregation Services Router CGv6 … · FPGAUPGRADE 31 AccessingCPUconsolesonISMCard 33 InstallingCGv6ApplicationonISMRunningforCiscoIOSXRSoftwareRelease 4.2.0
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Cisco ASR 9000 Series Aggregation Services Router CGv6Configuration Guide, Release 5.2.xFirst Published: 2016-07-01
Last Modified: 2014-10-01
Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1721R)
Configuration Examples for Implementing the Carrier Grade NAT 314
Configuring a Different Inside VRF Map to a Different Outside VRF: Example 314
Configuring a Different Inside VRF Map to a Same Outside VRF: Example 315
NAT44 Configuration: Example 315
Bulk Port Allocation and Syslog Configuration: Example 317
PPTP ALG Configuration: Example 318
NAT44 Instance 318
DBL Configuration: Example 318
NAT44 Instance 318
DS Lite Configuration: Example 318
IPv6 ServiceApp and Static Route Configuration 318
IPv4 ServiceApp and Static Route Configuration 318
DS Lite Configuration 319
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.xxii
Contents
DBL Configuration: Example 319
DS-Lite Instance 319
Configuring TCP Sequence-Check: Example 319
Configuring Address and Port-Dependent Filtering: Example 319
NAT0 Mode Configuration: Example 320
Configuration of Multiple NetFlow Servers: Example 320
Configuration of Multiple Syslog Servers: Servers 320
C H A P T E R 5 External Logging 323
Bulk Port Allocation 323
Restrictions for Bulk Port Allocation 323
Session logging 324
Syslog Logging 324
Restrictions for Syslog 324
Syslog Message Format 324
Header 325
Structured Data 326
MSG 326
Netflow v9 Support 328
NetFlow Record Format 328
Reliable Log Transfer 343
Reliable Log Transfer Configuration: Examples 344
Frequently Asked Questions (FAQs) 345
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x xiii
Contents
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.xxiv
Contents
Preface
The Preface contains these sections:
• Changes to This Document, page xv
• Obtaining Documentation and Submitting a Service Request, page xv
Changes to This DocumentThis table lists the technical changes made to this document since it was first released.
Table 1: Changes to This Document
Change SummaryDateRevision
Initial release of this document.July 2014OL-32683-01
Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a servicerequest, and gathering additional information, see What's New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What'sNew in Cisco Product Documentation RSS feed. RSS feeds are a free service.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x xv
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.xxvi
PrefaceObtaining Documentation and Submitting a Service Request
C H A P T E R 1New and Changed Carrier Grade NAT Feature
This table summarizes the new and changed information for theCisco ASR 9000 Series Aggregation ServicesRouter CGv6 Configuration Guide, and tells you where the features are documented.
• New and Changed Carrier Grade IPv6 Features, page 1
New and Changed Carrier Grade IPv6 FeaturesWhere DocumentedIntroduced/Changed in
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x2
New and Changed Carrier Grade NAT FeatureNew and Changed Carrier Grade IPv6 Features
Where DocumentedIntroduced/Changed inRelease
DescriptionFeature
Carrier Grade IPv6without Service Modulesm-carrier-grade-IPv6-without-service-modules.ditamap
Release 5.3.2This feature wasintroduced.
MAP E without VSMCard
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 3
New and Changed Carrier Grade NAT FeatureNew and Changed Carrier Grade IPv6 Features
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x4
New and Changed Carrier Grade NAT FeatureNew and Changed Carrier Grade IPv6 Features
C H A P T E R 2Introduction
This module provides an overview of the Carrier Grade IPv6 (CGv6) on Cisco IOS XR software.
The following table lists changes made to the document.
Table 2: Feature History for Implementing CGv6 on ASR 9000 Router
ModificationRelease
Initial release of this document. CGv6 applicationssuch as CGN or NAT44 are supported.
Release 4.2.0
These features were introduced:
• DS-Lite.
• Syslog and Bulk Port Allocation for NAT44and DS-Lite.
Release 4.2.1
Support for multiple ISM line cards.Release 4.2.3
These features were introduced:
• Stateful NAT64
• Mapping ofAddress and Port-TranslationMode
• High Availability
• Destination-Based Logging
Release 4.3.0
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 5
These features were introduced:
• IPv6 Rapid Deployment
• Mapping of Address and Port-EncapsulationMode
• Point-to-Point Tunneling Protocol-ApplicationLevel Gateway on NAT44
• Real-Time Streaming Proocol-ApplicationLevel Gateway on Stateful NAT64
Release 4.3.1
Support for Virtualized Services Module (VSM) hasbeen introduced in this release.
Release 5.1.1
These features were introduced:
• NAT0 Mode
• Static Destination NAT
• Multiple NetFlow/Syslog Servers
• Additional CGN Counters
Release 5.2.0
• CGv6 Overview and Benefits, page 6
• Prerequisites for Implementing the CGv6, page 7
• Implementation of NAT, page 8
• Double NAT 444, page 9
• Address Family Translation, page 9
• Jumbo Frame Support, page 9
CGv6 Overview and BenefitsTo implement the CGv6, you should understand the following concepts.
CGv6 OverviewInternet Protocol version 4 (IPv4) has reached exhaustion at the international level (IANA). But serviceproviders must maintain and continue to accelerate growth. Billions of new devices such as mobile phones,portable multimedia devices, sensors, and controllers are demanding Internet connectivity at an increasingrate. The Cisco Carrier Grade IPv6 Solution (CGv6) is designed to help address these challenges. With CiscoCGv6, you can:
• Preserve investments in IPv4 infrastructure, assets, and delivery models.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x6
IntroductionCGv6 Overview and Benefits
• Prepare for the smooth, incremental transition to IPv6 services that are interoperable with IPv4.
• Prosper through accelerated subscriber, device, and service growth that are enabled by the efficienciesthat IPv6 can deliver.
Cisco CGv6 extends the already wide array of IPv6 platforms, solutions, and services. Cisco CGv6 helps youbuild a bridge to the future of the Internet with IPv6.
Cisco ASR 9000 Series Aggregation Services Router is part of the Cisco CGv6 solution portfolio and thereforedifferent CGv6 solutions or applications are implemented on this platform (specifically on ISM service card).Carrier Grade Network Address Translation (CGN) is a large scale NAT that is capable of providing privateIPv4 to public IPv4 address translation in the order of millions of translations to support a large number ofsubscribers, and at least 10 Gbps full-duplex bandwidth throughput.
Benefits of CGv6CGv6 offers these benefits.
• Enables service providers to execute orderly transitions to IPv6 through mixed IPv4 and IPv6 networks.
• Provides address family translation but not limited to just translation within one address family.
• Delivers a comprehensive solution suite for IP address management and IPv6 transition.
IPv4 Address ShortageA fixed-size resource such as the 32-bit public IPv4 address space will run out in a few years. Therefore, theIPv4 address shortage presents a significant and major challenge to all service providers who depend on largeblocks of public or private IPv4 addresses for provisioning and managing their customers.
Service providers cannot easily allocate sufficient public IPv4 address space to support new customers thatneed to access the public IPv4 Internet.
Prerequisites for Implementing the CGv6The following prerequisites are required to implement CGv6.
• You must be running Cisco IOS XR software Release 4.2.0 and above.
• You must have installed the CGv6 service package, asr9k-services-p.pie (to be used with RSP2) orasr9k-services-px.pie (to be used with RSP3).
• Youmust be in a user group associated with a task group that includes the proper task IDs. The commandreference guides include the task IDs required for each command.
All the error conditions result in a syslog message. On observation of Heartbeat failure messages, contactCisco Technical Support with show tech-support services cgn information.
Note
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 7
IntroductionBenefits of CGv6
If you suspect user group assignment is preventing you from using a command, contact your AAAadministrator for assistance.
Note
Implementation of NATThis section explains various implementations of NAT. The implementation of NAT over ISM and VSM areexplained in the following chapters.
Implementing NAT with ICMPThis section explains how the Network Address Translation (NAT) devices work in conjunction with InternetControl Message Protocol (ICMP).
The implementations of NAT varies in terms of how they handle different traffic.
ICMP Query Session TimeoutRFC 5508 provides ICMP Query Session timeouts. A mapping timeout is maintained by NATs for ICMPqueries that traverse them. The ICMP Query Session timeout is the period during which a mapping will stayactive without packets traversing the NATs. The timeouts can be set as either Maximum Round Trip Time(MaximumRTT) or Maximum Segment Lifetime (MSL). For the purpose of constraining the maximumRTT,the Maximum Segment Lifetime (MSL) is considered a guideline to set packet lifetime.
If the ICMP NAT session timeout is set to a very large duration (240 seconds) it can tie up precious NATresources such as Query mappings and NAT Sessions for the whole duration. Also, if the timeout is set tovery low it can result in premature freeing of NAT resources and applications failing to complete gracefully.The ICMP Query session timeout needs to be a balance between the two extremes. A 60-second timeout is abalance between the two extremes.
Implementing NAT with TCPThis section explains the various NAT behaviors that are applicable to TCP connection initiation. The detailedNAT with TCP functionality is defined in RFC 5382.
Address and Port Mapping BehaviorA NAT translates packets for each TCP connection using the mapping. A mapping is dynamically allocatedfor connections initiated from the internal side, and potentially reused for certain connections later.
Internally Initiated ConnectionsA TCP connection is initiated by internal endpoints through a NAT by sending SYN packet. All the externalIP address and port used for translation for that connection are defined in the mapping.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x8
IntroductionImplementation of NAT
Generally for the client-server applications where an internal client initiates the connection to an externalserver, to translate the outbound SYN, the resulting inbound SYN-ACK response mapping is used, thesubsequent outbound ACK, and other packets for the connection.
The 3-way handshake corresponds to method of connection initiation.
Externally Initiated ConnectionsFor the first connection that is initiated by an internal endpoint NAT allocates the mapping. For some situations,the NAT policy may allow reusing of this mapping for connection initiated from the external side to theinternal endpoint.
Double NAT 444The Double NAT 444 solution offers the fastest and simplest way to address the IPv4 depletion problemwithout requiring an upgrade to IPv6 anywhere in the network. Service providers can continue offering newIPv4 customers access to the public IPv4 Internet by using private IPv4 address blocks, if the service provideris large enough; However, they need to have an overlapping RFC 1918 address space, which forces the serviceprovider to partition their network management systems and creates complexity with access control lists(ACL).
Double NAT 444 uses the edge NAT and CGN to hold the translation state for each session. For example,both NATs must hold 100 entries in their respective translation tables if all the hosts in the residence of asubscriber have 100 connections to hosts on the Internet). There is no easy way for a private IPv4 host tocommunicate with the CGN to learn its public IP address and port information or to configure a static incomingport forwarding.
Address Family TranslationThe IPv6-only to IPv4-only protocol is referred to as address family translation (AFT). The AFT translatesthe IP address from one address family into another address family. For example, IPv6 to IPv4 translation iscalled NAT 64 or IPv4 to IPv6 translation is called NAT 46.
Jumbo Frame SupportJumbo frames are frames that are larger than the standard Ethernet frame size, which is 1518 bytes. Thedefinition of frame size is vendor-dependent, and are not part of the IEEE standard.
The Integrated Services Module (ISM) and Virtualized Services Module (VSM) both support Jumbo Frames.
To enable Jumbo Frame support, configure the Maximum Transmission Unit (MTU) value of both the ingressand egress interfaces. The default MTU value is 1512 bytes and the maximum value is 9216 bytes.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 9
IntroductionDouble NAT 444
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x10
IntroductionJumbo Frame Support
C H A P T E R 3Carrier Grade IPv6 over Integrated ServicesModule (ISM)
This module describes how to implement the Carrier Grade IPv6 (CGv6) over Integrated Services Module( ISM).
• Cisco Integrated Service Module, page 11
• Implementing NAT 44 over ISM, page 13
• Implementing NAT 64 over ISM, page 16
• CGv6 Applications, page 21
• Policy Functions, page 27
• External Logging, page 30
• Configuring CGv6 on Cisco IOS XR Software, page 31
• Configuring MAP-E, page 109
• Configuring MAP-T, page 125
• Configuring High Availability, page 163
• Configuration Examples for Implementing the Carrier Grade NAT, page 165
Cisco Integrated Service ModuleCisco Integrated Service Module (ISM) is a physical line interface module (PLIM) that provides a highlyscalable modular services delivery platform for delivering multiple types of services. ISM is designed todeliver flexible and highly scalable service integration that allows operational efficiency, service flexibility,and faster time to market. The module offers the architectural advantages of integration with the routingsystem.
Solution ComponentsThese are the solution components of the Cisco Integrated Service Module (ISM).
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 11
• ASR 9000 with IOS XR
◦High-capacity, carrier-class SP platform with Cisco IOS XR Software
◦Leverages XR infrastructure to divert packets to ISM
◦Uniform, integrated configuration and management
• Integrated Service Module
◦Flexible Linux-based development & test environment
◦Supports required CGv6
◦First IPv6 Transition Strategy
• Integrated Service Module
◦Hardware
◦CGv6 function residing on ISM
◦Intel x86 with 12 CPU cores
◦Software
◦IOS-XR on LC, Linux on Intel CPUs
◦Integrated configuration and management through Cisco IOS XR Software
• Service Virtual Interface (SVI)
◦Two types of Service Virtual Interfaces are used in ISM
◦ServiceInfra SVI
◦ServiceApp SVI
There can be only one ServiceInfra SVI per ISM Slot. This is used for the management plane and is requiredto bring up ISM. This is of local significance within the chassis.
Access lists are not supported on service virtual interfaces.Note
ServiceApp SVI is used to forward the data traffic to the Application. Scale of ISM 244 ServiceApp perchassis is validated. These interfaces can be advertised in IGP/EGP.
Support for Multiple ISM Line CardsCisco IOS XR Software Release 4.2.3 and onwards supports a maximum of six ISM line cards in each CiscoASR 9000 Series Aggregation Services Router chassis. For applications such as NAT44 and DS-Lite, theconfiguration can be independently applied to each ISM line card.
For NAT-44, a maximum of ten million sessions are supported by each ISM line card.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x12
Carrier Grade IPv6 over Integrated Services Module (ISM)Support for Multiple ISM Line Cards
For DS-Lite, a maximum of twenty million sessions are supported by each ISM line card.
No additional configuration is required to support multiple ISM line cards.Note
CGN as Default Application on ISMISM supports CGN as the default application.
Configuring CGN as Default Application on ISMTo configure CGN as the default application, perform these steps.
SUMMARY STEPS
1. Install CGN services.pie.2. Configure the CGN role using hw-module service cgn location <node_id> command.3. Load the CGN Linux image as the default image instead of CDS-IS.4. Reload ISM.
DETAILED STEPS
Step 1 Install CGN services.pie.Step 2 Configure the CGN role using hw-module service cgn location <node_id> command.Step 3 Load the CGN Linux image as the default image instead of CDS-IS.Step 4 Reload ISM.
Implementing NAT 44 over ISMThese sections provide the information about implementation of NAT.
The following figure illustrates the implementation of NAT 44 over ISM
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 13
Carrier Grade IPv6 over Integrated Services Module (ISM)CGN as Default Application on ISM
The components of this illustration are as follows:
• Private IP4 subscribers: It denotes a private network.
• Interface/VLAN: It denotes a designated interface or VLAN which is associated with the VRF.
• Inside VRF: It denotes the VRF that handles packets coming from the subscriber network. It is knownas inside VRF as it forwards packets from the private network.
• App SVI: It denotes an application interface that forwards the data packet to and from the ISM. The datapacket may be sent from another line card through a backplane. Because the ISM card does not have aphysical interface, the APP SVI acts as a logical entry into it.
The inside VRF is bound to an App SVI. There are 2 App SVIs required; one for the inside VRF andthe other one for the outside VRF. Each App SVI pair will be associated with a unique "inside VRF"and a unique public IP address pool. The VRF consists of a static route for forwarding packets to AppSVI1.
• Outside VRF: It denotes the VRF that handles packets going out to the public network. It is known asoutside VRF as it forwards packets from the public network.
• Public IPV4: It denotes a public network.
The following figure illustrates the path of the data packet from a private network to a public network in aNAT implementation.
The packet goes through the following steps when it travels from the private network to the public network:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x14
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 44 over ISM
1 In the network shown in this figure, the packet travels from the host A (having the IP address 10.222.5.55)in the private network to host B (having the IP address 5.5.5.2) in the public network. The private addresshas to be mapped to the public address by NAT44 that is implemented in ISM.
2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 0. While usingNAT44, it is mandatory that the packet enters through VRF.
3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the inside VRFeither through static routing or ACL-based forwarding (ABL). After the inside VRF determines that thepacket needs address translation, it is forwarded to the App SVI that is bound to the VRF.
4 The packet is forwarded by AppSVI1 through a default static route (ivrf1). The destination address andthe port get translated because of the CGN configuration applied on ISM.
5 The ISM applies NAT44 to the packet and a translation entry is created. The CGN determines the destinationaddress from the FIB Look Up. It pushes the packet to the egress port.
6 The packet is then forwarded to the egress port on the interface through App SVI2. An inside VRF ismapped to an outside VRF. The outside VRF is associated with this interface. The packet is forwarded byApp SVI2 through the default static route (ovrf1). Then the packet is sent to the public network.
7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to thedestination through a different static route and a different egress port.
The following figure illustrates the path of the packet coming from the public network to the private network.
The packet goes through the following steps when it travels from the public network to the private network:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 15
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 44 over ISM
1 In the network shown in this figure, the packet travels from the host A (having the IP address 10.222.5.55)in the public network to host B (having the IP address 5.5.5.2) in the private network. The public addresshas to be mapped to the private address by NAT44 that is implemented in ISM.
2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 0.
3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the outside VRFeither through static routing or ACL-based forwarding (ABL).
4 The packet is forwarded by App SVI2 through a default static route. The destination address and the portare mapped to the translated address.
5 The ISM applies NAT44 to the packet. The CGN determines the destination address from the FIB LookUp. It pushes the packet to the egress port.
6 The packet is then forwarded to the egress port on the interface through App SVI2. Then the packet is sentto the private network through the inside VRF.
7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to thedestination through a different static route and a different egress port.
Implementing NAT 64 over ISMThis section explains how NAT64 is implemented over ISM. The figure illustrates the implementation ofNAT64 over ISM.
The components of this implementation are as follows:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x16
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 64 over ISM
• Private IP6 subscribers – It denotes a private network.
• Interface/VLAN- It denotes a designated interface or VLAN which is associated with the VRF.
• Inside VRF – It denotes the VRF that handles packets coming from the subscriber network. It is knownas inside VRF as it forwards packets from the private network.
• App SVI- It denotes an application interface that forwards the data packet to and from the ISM. Thedata packet may be sent from another line card through a backplane. Because the ISM card does nothave a physical interface, the APP SVI acts as a logical entry into it.
The inside VRF is bound to an App SVI. There are 2 App SVIs required; one for the inside VRF andthe other one for the outside VRF. Each App SVI pair will be associated with a unique "inside VRF"and a unique public IP address pool. The VRF consists of a static route for forwarding packets to AppSVI1.
• Outside VRF- It denotes the VRF that handles packets going out to the public network. It is known asoutside VRF as it forwards packets from the public network.
• Public IPV4- It denotes a public network.
The following figure illustrates the path of the data packet from a private network to a public network in aNAT64 implementation.
The packet goes through the following steps when it travels from the private network to the public network:
1 In the network shown in this figure, the packet travels from the host A (having the IP address3001:DB8:E0E:E03::/40) in the private network to host B (having the IP address 11.11.11.2) in the publicnetwork. The private address has to be mapped to the public address by NAT64 that is implemented inISM.
2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 3.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 17
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 64 over ISM
3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the inside VRFeither through static routing or ACL-based forwarding (ABL). Based on this routing decision, the packetthat needs address translation is determined and is forwarded to the App SVI that is bound to the VRF.
4 The packet is forwarded by AppSVI1 through a default static route. The destination address and the portget translated because of the CGN configuration applied on ISM.
5 The ISM applies NAT64 to the packet and a translation entry is created. The CGN determines the destinationaddress from the FIB Look Up. It pushes the packet to the egress port.
6 The packet is then forwarded to the egress port on the interface through App SVI2. The packet is forwardedby App SVI2 through the default static route. Then the packet is sent to the public network.
7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to thedestination through a different static route and a different egress port.
The following figure illustrates the path of the packet coming from the public network to the private network.
The packet goes through the following steps when it travels from the public network to the private network:
1 In the network shown in this figure, the packet travels from the host A (having the IP address 11.11.11.2)in the public network to host B (having the IP address 3001:DB8:E0E:E03::) in the private network. Thepublic address has to be mapped to the private address by NAT64 that is implemented in ISM.
2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 3.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x18
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 64 over ISM
3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the outside VRFeither through static routing or ACL-based forwarding (ABL). Based on this routing decision, the packetis forwarded to the App SVI that is bound to the VRF.
4 The packet is forwarded by App SVI2 through a default static route. The destination address and the portare mapped to the translated address.
5 The ISM applies NAT64 to the packet. The CGN determines the destination address from the FIB LookUp. It pushes the packet to the egress port.
6 The packet is then forwarded to the egress port on the interface through App SVI2. Then the packet is sentto the private network through the inside VRF.
7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to thedestination through a different static route and a different egress port.
Table 3: Supported Interfaces and Forwarding Features on CGv6
5.3.x5.2.x5.1.x4.3.x
Egress Interfaces
YesYesYesYesPhysical Interface
YesYesYesYesVLANSubinterface
YesYesYesYesBundle Interface
YesYesYesYesBundle Subinterface
NoNoNoNoBVI Interface
YesYesYesNoBNGIP-Subinterface/PPPoE
NoNoNoNoEthernetAttachmentCircuit orPseudowire
NoNoNoNoGRE Tunnel
L3 Unicast Forwarding Features
YesYesYesYesBasic IPv4 IGPForwarding
YesYesYesYesBGP Traffic
YesYesYesYesForwarding in VRF
YesYesYesYesRecursive Routes
NoNoNoNouRPF
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 19
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 64 over ISM
5.3.x5.2.x5.1.x4.3.x
NoNoNoNoBGP-PA
MPLS and Fast Reroute (FRR) Support
Note: The ISM card does not generate label for packets. It only processes unlabeled packets.
YesYesYesNoMPLS-TE Paths
YesYesYesYesBasic Labeled Path
YesYesYesNoMPLS-TE Tunnel
NoNoNoNoMPLS-TP Tunnel
YesYesYesNoTE-FRR
NoNoNoNoIP-FRR
NoNoNoNoLDP-FRR orLFA-FRR
Multicast
NoNoNoNoIP Multicast
NoNoNoNoMVPN
NoNoNoNoLabel SwitchedMulticast
ServiceApp Interfaces
YesYesYesYesABF to ServiceAppInterface
NoNoNoNoABF fromServiceAppInterface
NoNoNoNoACLon ServiceAppInterface
NoNoNoNoQoS on ServiceAppInterface
NoNoNoNoLawful Intercept(LI) on Service AppInterface
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x20
Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 64 over ISM
Note • The table refers to packet handling after CGv6 processing (from ingress to egress).
• The CGv6 application processes only L3 unicast traffic. Other traffic types such as L2 and L3multicast are not supported.
• The forwarding features that are supported are only those where traffic is injected from the CGv6application as an IPv4 or IPv6 packet.
CGv6 ApplicationsThese applications are deployed on the ISM line card.
Network Address Translation (NAT44)Network Address Translation (NAT44) or Carrier Grade Network Address Translation (CGN) is a large scaleNAT that is capable of providing private IPv4 to public IPv4 address translation in the order of millions oftranslations to support a large number of subscribers, and at least 10 Gbps full-duplex bandwidth throughput.
CGN is a workable solution to the IPv4 address completion problem, and offers a way for service providersubscribers and content providers to implement a seamless transition to IPv6. CGN employs network addressand port translation (NAPT) methods to aggregate many private IP addresses into fewer public IPv4 addresses.For example, a single public IPv4 address with a pool of 32 K port numbers supports 320 individual privateIP subscribers assuming each subscriber requires 100 ports. For example, each TCP connection needs oneport number.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 21
Carrier Grade IPv6 over Integrated Services Module (ISM)CGv6 Applications
A Network Address Translation (NAT) box is positioned between private and public IP networks that areaddressed with non-global private addresses and a public IP addresses respectively. A NAT performs the taskof mapping one or many private (or internal) IP addresses into one public IP address by employing bothnetwork address and port translation (NAPT) techniques. The mappings, otherwise referred to as bindings,are typically created when a private IPv4 host located behind the NAT initiates a connection (for example,TCP SYN) with a public IPv4 host. The NAT intercepts the packet to perform these functions:
• Rewrites the private IP host source address and port values with its own IP source address and portvalues
• Stores the private-to-public binding information in a table and sends the packet. When the public IP hostreturns a packet, it is addressed to the NAT. The stored binding information is used to replace the IPdestination address and port values with the private IP host address and port values.
Traditionally, NAT boxes are deployed in the residential home gateway (HGW) to translate multiple privateIP addresses. The NAT boxes are configured on multiple devices inside the home to a single public IP address,which are configured and provisioned on the HGW by the service provider. In enterprise scenarios, you canuse the NAT functions combined with the firewall to offer security protection for corporate resources andallow for provider-independent IPv4 addresses. NATs have made it easier for private IP home networks toflourish independently from service provider IP address provisioning. Enterprises can permanently employprivate IP addressing for Intranet connectivity while relying on a few NAT boxes, and public IPv4 addressesfor external public Internet connectivity. NAT boxes in conjunction with classic methods such as ClasslessInter-Domain Routing (CIDR) have slowed public IPv4 address consumption.
Network Address and Port MappingNetwork address and port mapping can be reused to map new sessions to external endpoints after establishinga first mapping between an internal address and port to an external address. These NAT mapping definitionsare defined from RFC 4787:
• Endpoint-independent mapping—Reuses the port mapping for subsequent packets that are sent fromthe same internal IP address and port to any external IP address and port.
• Address-dependent mapping—Reuses the port mapping for subsequent packets that are sent from thesame internal IP address and port to the same external IP address, regardless of the external port.
CGN on ISM implements Endpoint-Independent Mapping.Note
Translation FilteringRFC 4787 provides translation filtering behaviors for NATs. These options are used by NAT to filter packetsoriginating from specific external endpoints:
• Endpoint-independent filtering—Filters out only packets that are not destined to the internal addressand port regardless of the external IP address and port source.
• Address-dependent filtering—Filters out packets that are not destined to the internal address. Inaddition, NAT filters out packets that are destined for the internal endpoint.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x22
• Address and port-dependent filtering—Filters out packets that are not destined to the internal address.In addition, NAT filets out packets that are destined for the internal endpoint if the packets were notsent previously.
Dual Stack LiteThe Dual Stack Lite (DS-Lite) feature enables legacy IPv4 hosts and server communication over both IPv4and IPv6 networks. Also, IPv4 hosts may need to access IPv4 internet over an IPv6 access network. The IPv4hosts will have private addresses which need to have network address translation (NAT) completed beforereaching the IPv4 internet. The Dual Stack Lite application has these components:
• Basic Bridging BroadBand Element (B4): This is a Customer Premises Equipment (CPE) router thatis attached to the end hosts. The IPv4 packets entering B4 are encapsulated using a IPv6 tunnel and sentto the Address Family Transition Router (AFTR).
• Address Family Transition Router(AFTR): This is the router that terminates the tunnel from the B4.It decapsulates the tunneled IPv4 packet, translates the network address and routes to the IPv4 network.In the reverse direction, IPv4 packets coming from the internet are reverse network address translatedand the resultant IPv4 packets are sent the B4 using a IPv6 tunnel.
The Dual Stack Lite feature helps in these functions:
1 Tunnelling IPv4 packets from CE devices over IPv6 tunnels to the CGSE blade.
2 Decapsulating the IPv4 packet and sending the decapsulated content to the IPv4 internet after completingnetwork address translation.
3 In the reverse direction completing reverse-network address translation and then tunnelling them overIPv6 tunnels to the CPE device.
IPv6 traffic from the CPE device is natively forwarded.
VSM scale numbers supported in Dual Stack Lite
Dual Stack Lite supports the following VSM scale number:
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
80 MillionsDS-Lite Sessions
Scalability and Performance of DS Lite• Supports a total of 60 million translations.
• Number of unique users behind B4 router, basically IPv6 and IPv4 Source tuple, can scale to 1 million.
• There is no real limit to the number of B4 routers and their associated tunnels connecting to the AFTR,except the session limit, which is 20 million B4 routers (assuming each router has only one session). Inreality, a maximum of 1 million B4 routers can connect to an AFTR at any given time.
• The performance of DS-Lite traffic, combined IPv4 and IPv6, is 39 Gbps.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 23
Carrier Grade IPv6 over Integrated Services Module (ISM)Dual Stack Lite
Stateful NAT64The Stateful NAT64 (Network Address Translation 64) feature provides a translationmechanism that translatesIPv6 packets into IPv4 packets and vice versa. NAT64 allows IPv6-only clients to contact IPv4 servers usingunicast UDP, TCP, or ICMP. The public IPv4 address can be shared with several IPv6-only clients. NAT64supports communication between:
• IPv6 Network and Public IPv4 Internet
• Public IPv6 Internet and IPv4 Network
NAT64 is implemented on the Cisco CRS router CGSE platform. CGSE (Carrier Grade Service Engine) hasfour octeons and supports 20 Gbps full duplex traffic. It works on Linux operating system and traffic intoCGSE is forwarded using serviceApp interfaces. SVIs (Service Virtual Interfaces) are configured to enabletraffic to flow in and out of CGSE .
Each NAT64 instance configured is associated with two serviceApps for the following purposes:
• One serviceApp is used to carry traffic from IPv6 side
• Another serviceApp is used to carry traffic from IPv4 side of the NAT64.
NAT64 instance parameters are configured using the CGNCLI. The NAT64 application in the octeons updatesits NAT64 instance and serviceApp databases, which are used to perform the translation between IPv6 andIPv4 and vice versa.
Active CGN instance configuration is replicated in the standby CGN instance through the XR control plane.Translations that are established on the Active CGN instance are exported to the Standby CGN instance asthe failure of the Active CGN affects the service until translations are re-established through normal packetflow. Service interruption is moderate for the given fault detection time and translation learning rate in termsof seconds or tens of seconds for a large translation database.
Prefix FormatA set of bits at the start of an IPv6 address is called the format prefix. Prefix length is a decimal value thatspecifies the number of the left-most contiguous bits of an address.
When packets flow from the IPv6 to the IPv4 direction, the IPv4 host address is derived from the destinationIP address of the IPv6 packet that uses the prefix length.When packets flow from the IPv4 to the IPv6 direction,the IPv6 host address is constructed using the stateful prefix.
According to the IETF address format, a u-bit (bit 70) defined in the IPv6 architecture should be set to zero.The reserved octet, also called u-octet, is reserved for compatibility with the host identifier format defined inthe IPv6 addressing architecture. When constructing an IPv6 packet, the translator has to make sure that theu-bits are not tampered, and are set to the value suggested by RFC 2373. The suffix will be set to all zeros bythe translator. IETF recommends that the 8 bits of the u-octet (bit range 64-71) be set to zero.
Well Known Prefix (WKP)
Well Known Prefix (WKP) 64:FF9B::/96 is supported for Stateful NAT64. During stateful translation, if nostateful prefix is configured (either on the interface or globally), the WKP prefix is used to translate the IPv4host addresses.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x24
Carrier Grade IPv6 over Integrated Services Module (ISM)Stateful NAT64
Stateful IPv4-to-IPv6 Packet FlowThe packet flow of IPv4-initiated packets for Stateful NAT64:
• The destination address is routed to a NAT Virtual Interface (NVI). A virtual interface is created whenStateful NAT64 is configured. For Stateful NAT64 translation to work, all packets must get routed tothe NVI. When you configure an address pool, a route is automatically added to all IPv4 addresses inthe pool. This route automatically points to the NVI.
• The IPv4-initiated packet hits static or dynamic binding. Dynamic address bindings are created by theStateful NAT64 translator when you configure dynamic Stateful NAT64. A binding is dynamicallycreated between an IPv6 and an IPv4 address pool. Dynamic binding is triggered by the IPv6-to-IPv4traffic and the address is dynamically allocated. Based on your configuration, you can have static ordynamic binding.
• The IPv4-initiated packet is protocol-translated and the destination IP address of the packet is set to IPv6based on static or dynamic binding. The Stateful NAT64 translator translates the source IP address toIPv6 by using the Stateful NAT64 prefix (if a stateful prefix is configured) or the Well Known Prefix(WKP) (if a stateful prefix is not configured).
• A session is created based on the translation information.
All subsequent IPv4-initiated packets are translated based on the previously created session.
Stateful IPv6-initiated packet flow:• The first IPv6 packet is routed to the NAT Virtual Interface (NVI) based on the automatic routing setupthat is configured for the stateful prefix. Stateful NAT64 performs a series of lookups to determinewhether the IPv6 packet matches any of the configured mappings based on an access control list (ACL)lookup. Based on the mapping, an IPv4 address (and port) is associated with the IPv6 destination address.The IPv6 packet is translated and the IPv4 packet is formed by using these methods:
◦Extracting the destination IPv4 address by stripping the prefix from the IPv6 address. The sourceaddress is replaced by the allocated IPv4 address (and port).
◦Translating the rest of the fields from IPv6-to-IPv4 to form a valid IPv4 packet.
• Creating a new NAT64 translation in the session database and in the bind database. The pool and portdatabases are updated depending on the configuration. The return traffic and the subsequent traffic ofthe IPv6 packet flow will use this session database entry for translation.
Static port forwarding is not supported over StatefulNAT64 on ISM.Note
IP Packet FilteringStateful NAT64 filters IPv6 and IPv4 packets. All IPv6 packets that are transmitted into the stateful translatorare filtered because statefully translated IPv6 packets consume resources in the translator. These packetsconsume processor resources for packet processing, memory resources (always session memory) for static
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 25
Carrier Grade IPv6 over Integrated Services Module (ISM)Stateful NAT64
configuration, IPv4 address resources for dynamic configuration, and IPv4 address and port resources for PortAddress Translation (PAT).
Stateful NAT64 utilizes configured access control lists (ACLs) and prefix lists to filter IPv6-initiated trafficflows that are allowed to create the NAT64 state. Filtering of IPv6 packets is done in the IPv6-to-IPv4 directionbecause dynamic allocation of mapping between an IPv6 host and an IPv4 address can be done only in thisdirection.
Stateful NAT64 supports endpoint-dependent filtering for the IPv4-to-IPv6 packet flowwith PAT configuration.In a Stateful NAT64 PAT configuration, the packet flow originates from the IPv6 realm and creates the stateinformation in NAT64 state tables. Packets from the IPv4 side that do not have a previously created state aredropped. Endpoint-independent filtering is supported with static NAT and non-PAT configurations.
Mapping of Address and Port-Translation ModeMapping of Address and Port-Translation Mode (MAP-T) is a CGN solution that enables IPv4-only clientsto communicate with IPv6-only resources using address and packet translation. MAP-T is also referred to asDual IVI (dIVI) or Stateless NAT46. This enables a service provider to offer IPv4 services to IPv6 enabled(customer) sites to which it provides customer premise equipment (CPE). This approach utilizes stateless IPv4to IPv6 translation (that is NAT64) to transit IPv6-enabled network infrastructure. The provider access networkcan now be on IPv6, while customers use IPv6 and IPv4 services simultaneously. MAP-T keeps the statefulNAT44 on CPE, as usual, to handle IPv4 address exhaustion, in addition to stateless NAT64 on CPE andBorder Router.
MAP-T is attractive to those SPs who have deployed, or are planning to deploy IPv6 end-to-end services, andwant to manage IPv4 address exhaustion with utmost predictability.
MAP-T is a preferred alternate to DS-Lite in a sevice provider network when there is no tunneling needed.
MAP-T is offered in stateless mode only.Note
IPv6 Rapid DeploymentIPv6 Rapid Deployment (6RD) is a mechanism that allows service providers to provide a unicast IPv6 serviceto customers over their IPv4 network.
6RD Definitions• 6RD CE /RG/CPE: The 6rd "Customer Edge" router that sits between an IPv6-enabled site and anIPv4-enabled SP network. In the context of residential broadband deployment, this is referred to as theResidential Gateway (RG) or Customer Premises Equipment (CPE) or Internet Gateway Device (IGD).This router has a 6rd tunnel interface acting as an endpoint for the IPv6 in IPv4 encapsulation andforwarding, with at least one 6rd CE LAN side interface and 6rd CE WAN side interface, respectively.
• 6RDBorder Relay (BR): A 6rd-enabled Border Relay router located at the service provider’s premises.The 6rd BR router has at least one IPv4 interface, a 6rd tunnel interface for multi-point tunneling, andat least one IPv6 interface that is reachable through the IPv6 Internet or IPv6-enabled portion of the SPnetwork. A router running IOS can also be a 6RD BR.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x26
Carrier Grade IPv6 over Integrated Services Module (ISM)Mapping of Address and Port-Translation Mode
• 6RD Delegated Prefix: The IPv6 prefix determined by the 6rd CE device for use by hosts within thecustomer site.
• 6RD Prefix (SP Prefix) : An IPv6 prefix selected by the service provider for use by a 6rd domain. Thereis exactly one 6rd prefix for a given 6rd domain.
• CE LAN side : The functionality of a 6rd CE that serves the Local Area Network (LAN) orcustomer-facing side of the CE. The CE LAN side interface is fully IPv6 enabled.
• CEWAN side : The functionality of a 6rd CE that serves the Wide Area Network (WAN) or ServiceProvider- facing side of the CE. The CE WAN side is IPv4 only.
• BR IPv4 address : The IPv4 address of the 6rd Border Relay for a given 6rd domain. This IPv4 addressis used by the CE to send packets to a BR in order to reach IPv6 destinations outside of the 6rd domain.
• CE IPv4 address : The IPv4 address given to the CE as part of normal IPv4 Internet access (configuredthrough DHCP, PPP, or otherwise). This address may be global or private within the 6rd domain. Thisaddress is used by a 6rd CE to create the 6rd delegated prefix, as well as to send and receiveIPv4-encapsulated IPv6 packets.
Mapping of Address and Port-Encapsulation ModeMapping of Address and Port-EncapsulationMode (MAP-E) is a CGN solution that allows a service providerto enable IPv4 services at IPv6 (customer) sites to which it provides Customer Premise Equipment (CPE).This approach utilizes stateless IPv4-in-IPv6 encapsulation to transit IPv6-enabled network infrastructure.The encapsulation must be supported by the CPE and MAP-E Gateway/Border Relay, which removes theIPv6 encapsulation from IPv4 packets while forwarding them to the Internet. The provider access networkcan now be on IPv6, while customers see IPv6 and IPv4 service simultaneously.
MAP-E also helps manage IPv4 address exhaustion by keeping the stateful NAT44 on CPE. MAP-E is notsupported on any of the VRF interfaces, that is, either IPv4 or IPv6, whereas Map-T is supported with VRFinterfaces along with an SMU.
Policy Functions
Application Level GatewayTheApplication Level Gateway (ALG) deals with the applications that are embedded in the IP address payload.Active File Transfer Protocol (FTP), Point-to-Point Tunneling Protocol (PPTP), and Real Time StreamingProtocol (RTSP) are supported.
FTP-ALGCGN supports both passive and active FTP. FTP clients are supported with inside (private) address and serverswith outside (public) addresses. Passive FTP is provided by the basic NAT function. Active FTP is used withthe ALG.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 27
Carrier Grade IPv6 over Integrated Services Module (ISM)Mapping of Address and Port-Encapsulation Mode
RTSP-ALGCGN supports the Real Time Streaming Protocol (RTSP), an application-level protocol for control over thedelivery of data with real-time properties. RTSP provides an extensible framework to enable controlled,on-demand delivery of real-time data, such as audio and video. Sources of data can include both live datafeeds and stored clips.
PPTP-ALGPPTP is a network protocol that enables secure transfer of data from a remote client to a private enterpriseserver by creating a Virtual Private Network (VPN). It is used to provide IP security at the network layer.PPTP uses a control channel over TCP and a GRE tunnel operating to encapsulate PPP packets.
PPTP-ALG is a CGN solution that allows traffic from all clients through a single PPTP tunnel.
A PPTP tunnel is instantiated on the TCP port. This TCP connection is then used to initiate and manage asecond GRE tunnel to the same peer.
PPTP uses an access controller and network server to establish a connection.
PPTP Access Controller (PAC)
A device attached to one or more PSTN or ISDN lines capable of PPP operation and handling the PPTPprotocol. It terminates the PPTP tunnel and provides VPN connectivity to a remote client.
PPTP Network Server (PNS)
A device which provides the interface between the Point-to-Point Protocol (encapsulated in the PPTP protocol)and a LAN or WAN. The PNS uses the PPTP protocol to support tunneling between a PPTP PAC and thePNS. It requests to establish a VPN connectivity using PPTP tunnel.
Control Connection
A control connection is established between a PAC and a PNS for TCP.
Tunnel
A tunnel carries GRE encapsulated PPP datagrams between a PAC and a PNS
Active FTP, PPTP ALG, and RTSP ALG are supported on NAT44 applications. Active FTP and RTSPALG are supported on DS-Lite applications.
Note
TCP Maximum Segment Size AdjustmentWhen a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.
Static Port ForwardingStatic port forwarding helps in associating a private IP address and port with a statically allocated public IPand port. After you have configured static port forwarding, this association remains intact and does not get
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x28
Carrier Grade IPv6 over Integrated Services Module (ISM)TCP Maximum Segment Size Adjustment
removed due to timeouts until the CGSE is rebooted. In case of redundant CGSE cards, it remains intact untilboth of the CGSEs are reloaded together or the router is reloaded. There are remote chances that after a reboot,this association might change. This feature helps in cases where server applications running on the privatenetwork needs access from public internet.
High AvailabilityHigh Availability (HA) or 1:1 redundancy enables network-wide protection by providing fast recovery fromfaults that may occur in any part of the network. With Cisco High Availability on the module, the networkhardware and software work together and enable rapid recovery from disruption, to ensure fault transparencyto users and network applications. It provides continuous access to applications, data, and content anywhere,anytime by addressing potential causes of downtime with functionality, design, and best practices.
HA supports:
• 1:1 active or standby redundancy infrastructure for the services running on the module
◦Intra-chassis redundancy
◦Cold standby redundancy
• Replication of CGN-related configuration into a standby card
Before upgrading or downgrading the CGv6 OVA package on the Active VSM card inHA mode, perform a graceful shift of the traffic from Active VSM to Standby VSM.This will ensure that the CGN-related configuration is replicated into a standby card.For more information refer Upgrading CGv6 OVA Package, on page 182.
Note
• Failure detection
◦Data path - Channel through which CGV6 application data packets traverse
◦CPU health monitoring
◦Control path
◦Crashed processes
The following commands are supported for failure detection:
By default, failure detection for data path is not triggered unless the above command isconfigured.
Note
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 29
Carrier Grade IPv6 over Integrated Services Module (ISM)High Availability
The service-cgv6-ha location location-name datapath-test disable configurationdisables the heartbeat packets (health check packets) flowing in VSM. By default, thesepackets are flowing. You can disable these packets when required.
Note
• Failure reporting and recovery
◦If redundant module is configured, then switch-over the stand by module to active and reload theactive module.
◦If redundant module is not configured, then reload the module. This comes up again as an activemodule.
Redundancy Switchover Using CLI
You can trigger the switchover the failover by running the following the commands to an active slot and viceversa. :
Use the following command to switchover the failover to a preferred active slot.RP/0/RP0/CPU0:router(config)# service redundancy failover service-type all preferred-active<preferred-active slot>Use the following command to revert the failover to a preferred active slot.RP/0/RP0/CPU0:router(config)# service redundancy revert service-type all preferred-active<preferred-active slot>
External LoggingExternal logging configures the export and logging of the NAT table entries, private bindings that are associatedwith a particular global IP port address, and to use Netflow to export the NAT table entries.
Netflow v9 SupportThe NAT44 and DS Lite features support Netflow for logging of the translation records. Logging of thetranslation records can be mandated by for Lawful Intercept. The Netflow uses binary format and hencerequires software to parse and present the translation records.
Syslog SupportThe NAT44, Stateful NAT64, and DS Lite features support Netflow for logging of the translation records.Logging of the translation records can be mandated by for Lawful Intercept. The Netflow uses binary formatand hence requires software to parse and present the translation records.
In Cisco IOS XR Software Release 4.2.1 and later, the DS Lite and NAT44 features support Syslog as analternative to Netflow. Syslog uses ASCII format and hence can be read by users. However, the log datavolume is higher in Syslog than Netflow.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x30
Carrier Grade IPv6 over Integrated Services Module (ISM)External Logging
Bulk Port AllocationThe creation and deletion of NAT sessions need to be logged and these create huge amount of data. Theseare stored on Syslog collector which is supported over UDP. In order to reduce the volume of data generatedby the NAT device, bulk port allocation can be enabled. When bulk port allocation is enabled and when asubscriber creates the first session, a number of contiguous outside ports are pre-allocated. A bulk allocationmessage is logged indicating this allocation. Subsequent session creations will use one of the pre-allocatedport and hence does not require logging.
Session-logging and bulk port allocation are mutually exclusive.Note
Destination-Based LoggingDestination-Based Logging (DBL) includes destination IPv4 address and port number in the Netflow createand delete records used by NAT44, Stateful NAT64, and DS-Lite applications. It is also known asSession-Logging.
Session-Logging and Bulk Port Allocation are mutually exclusive.Note
Configuring CGv6 on Cisco IOS XR SoftwareThese configuration tasks are required to implement CGv6 on Cisco IOS XR software.
Installing Carrier Grade IPv6 on ISMThis section provides instructions on installing CGv6 on the ISM line card, removing CGv6 on the ISM linecard, and reinstalling the CDS TV application support.
Hardware
ISM hardware in chassis
Software
• asr9k-mini-p.vm or asr9k-mini-px.vm
• asr9k-services-p.pie or asr9k-services-px.pie
• asr9k-fpd-p.pie or asr9k-fpd-px.pie
FPGA UPGRADEThe installation is similar to an FPGA upgrade on any other ASR 9000 cards.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 31
Carrier Grade IPv6 over Integrated Services Module (ISM)Bulk Port Allocation
SUMMARY STEPS
1. Load the fpd pie.2. Run the show hw-module fpd location <> command in admin mode.3. Upgrade the identified FPGAs using the relevant commands:4. If one or more FPGAs were upgraded, reload the ISM card after all the upgrade operation completes
successfully.5. After the ISM card comes up, check for the FPGA version. This can be done using the following command
from the admin mode.
DETAILED STEPS
Step 1 Load the fpd pie.Step 2 Run the show hw-module fpd location <> command in admin mode.
Existing Field Programmable Devices================================================HW Current SW Upg/
Location Card Type Version Type Subtype Inst Version Dng?============ ======================== ======= ==== ======= ==== =========== ==== =====--------------------------------------------------------------------------------------0/1/CPU0 A9K-ISM-100 1.0 lc fpga1 0 0.29 No
--------------------------------------------------------------------------------------If one or more FPD needs an upgrade (can be identified from the Upg/Dng column in the output) then this can beaccomplished using the following steps.
Step 3 Upgrade the identified FPGAs using the relevant commands:upgrade hw-module fpd fpga1 location <>upgrade hw-module fpd cbc location <>upgrade hw-module fpd cpld1 location <>upgrade hw-module fpd fpga7 location <>upgrade hw-module fpd cpld3 location <>upgrade hw-module fpd fpga2 location <>To upgrade all FPGA using a single command, type:upgrade hw-module fpd all location <>
Step 4 If one or more FPGAs were upgraded, reload the ISM card after all the upgrade operation completes successfully.hw-module location <> reload
Step 5 After the ISM card comes up, check for the FPGA version. This can be done using the following command from theadmin mode.show hw-module fpd location <>
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x32
Carrier Grade IPv6 over Integrated Services Module (ISM)Installing Carrier Grade IPv6 on ISM
Accessing CPU consoles on ISM CardThis output shows ISM card in slot1:RP/0/RSP0/CPU0 #show platform0/RSP0/CPU0 A9K-RSP-4G(Active) IOS XR RUN PWR,NSHUT,MON0/1/CPU0 A9K-ISM-100(LCP) IOS XR RUN PWR,NSHUT,MON0/1/CPU1 A9K-ISM-100(SE) SEOS-READYTo access LC CPU console:RP/0/RSP0/CPU0#run attach 0/1/CPU0#To return to RSP console:#exitTo access X86 CPU console:RP/0/RSP0/CPU0:CRANE#run attachCon 0/0/cpu1 115200attachCon: Starting console session to node 0/0/cpu1attachCon: To quit console session type 'detach'Current Baud 115200Setting Baud to 115200
localhost.localdomain login: rootPassword: rootroot[root@localhost ~]#To return to RSP console:[root@localhost]# detach
Installing CGv6 Application on ISM Running for Cisco IOS XR Software Release 4.2.0If the card is in CDS-IS mode, then it must be converted to CDS-TV before installing CGv6. For installationinstructions, see the Cisco ASR 9000 Series Aggregation Services Router ISM Line Card Installation Guide.
With kernel.rpm, the "kernel.rpm" or "kernel-4.2.0.rpm" file is referred and with "ism_infra.tgz", the"ism_infra.tgz" or "ism_infra-4.2.0.tgz" file is referred.
Note
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 33
Carrier Grade IPv6 over Integrated Services Module (ISM)Installing Carrier Grade IPv6 on ISM
SUMMARY STEPS
1. Manually remove the non-CGv6 (CDS TV) configuration.2. Install the Cisco IOS XR Software Release 4.2.0 image on the ASR 9000 router.3. To handle version incompatibility between APIs of Cisco IOSXR and Linux software, run these commands
as soon as the ISM LCP is in IOS XR RUN state.4. Extract the ism_infra.tgz and kernel.rpm image from the tar file (available in the Download Software page
in Cisco.com) and copy the content to the disk on the RSP console.5. Copy kernel.rpm and ism_infra.tgz to X86 location.6. Install the images on X86:7. Run the following Cisco IOS XR Software Release 4.2.0 commands in admin mode, on RSP to install the
Services PIE:8. Run the following Cisco IOS XR Software Release 4.2.0 commands on the RSP to set the service role as
cgn.9. Revert the changes made in Step 310. Reload the ISM line card.11. Wait for the card to return to SEOS-READY and proceed with ServiceInfra interface configuration.
DETAILED STEPS
Step 1 Manually remove the non-CGv6 (CDS TV) configuration.Step 2 Install the Cisco IOS XR Software Release 4.2.0 image on the ASR 9000 router.Step 3 To handle version incompatibility between APIs of Cisco IOS XR and Linux software, run these commands as soon as
the ISM LCP is in IOS XR RUN state.RP/0/RSP0/CPU0#proc mandatory OFF fib_mgr location <ism_node_location>RP/0/RSP0/CPU0#proc SHUTDOWN fib_mgr location <ism_node_location>RP/0/RP0/CPU0:#adminRP/0/RSP0/CPU0(admin)#debug sim reload-disable location<ism_node_location>
Any delay may result in card reload due to APImismatch.
Caution
Step 4 Extract the ism_infra.tgz and kernel.rpm image from the tar file (available in the Download Software page in Cisco.com)and copy the content to the disk on the RSP console.RP/0/RSP0/CPU0#copy tftp://<tftp_addr><image_location>/ism_infra.tgz disk0:/RP/0/RSP0/CPU0#copy tftp://<tftp_addr><image_location>/kernel.rpm disk0:/
Step 5 Copy kernel.rpm and ism_infra.tgz to X86 location.
1 Log into X86 CPU console and start the se_mbox_server process:[root@localhost]# se_mbox_server -d
2 Log into ISM LC CPU and upload the images to X86:#avsm_se_upload /disk0:/kernel.rpm#avsm_se_upload /disk0:/ism_infra.tgz
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x34
Carrier Grade IPv6 over Integrated Services Module (ISM)Installing Carrier Grade IPv6 on ISM
3 After successful upload, the images should be available under /tmp directory in the X86 CPU.
Step 6 Install the images on X86:[root@localhost /] cd /tmp[root@localhost tmp]# rpm -i --force kernel.rpm[root@localhost tmp]# avsm_install ism_infra.tgz
Step 7 Run the following Cisco IOS XR Software Release 4.2.0 commands in admin mode, on RSP to install the Services PIE:RP/0/RSP0/CPU0#admin(admin)#install add tftp://<tftp_addr>/<image_location>/asr9k-services-p.pie synchronous activate. . . . . . . . . . .(admin)#exit
Step 8 Run the following Cisco IOS XR Software Release 4.2.0 commands on the RSP to set the service role as cgn.RP/0/RSP0/CPU0#config(config)#hw-module service cgn location <ism_node_location>(config)#commit(config)#exit
Step 9 Revert the changes made in Step 3RP/0/RSP0/CPU0#proc mandatory ON fib_mgr location <ism_node_location>RP/0/RSP0/CPU0#proc START fib_mgr location <ism_node_location>RP/0/RP0/CPU0:#adminRP/0/RSP0/CPU0:(admin)#no debug sim reload-disable location <ism_node_location>
Step 10 Reload the ISM line card.RP/0/RSP0/CPU0#hw-module location <ism_node_location> reload
Step 11 Wait for the card to return to SEOS-READY and proceed with ServiceInfra interface configuration.
Installing CGv6 Application on ISM for Cisco IOS XR Software Release 4.2.1 and laterThe CGv6 application can be installed on an ISM line card directly without changing fromCDS-IS to CDS-TVand then CGv6.
SUMMARY STEPS
1. Manually remove the non-CGv6 configuration, if any.2. Install the Cisco IOS XR Software image (asr9k-mini-p/px.vm/pie) for the specific release on the router.3. To handle version incompatibility between APIs of Cisco IOS XR and Linux software, run the following
commands in admin mode. Enter into maintenance mode by using the following command.4. To install the Services PIE on RSP, run the commands in admin mode:5. To set the service role as cgn on RSP, run the following commands.6. To install Linux Install-Kit from RSP, run the commands in admin mode.7. Wait for around 12-14 minutes for the card to come at SEOS-READY. Proceed with ServiceInfra interface
configuration.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 35
Carrier Grade IPv6 over Integrated Services Module (ISM)Installing Carrier Grade IPv6 on ISM
DETAILED STEPS
Step 1 Manually remove the non-CGv6 configuration, if any.Step 2 Install the Cisco IOS XR Software image (asr9k-mini-p/px.vm/pie) for the specific release on the router.Step 3 To handle version incompatibility between APIs of Cisco IOS XR and Linux software, run the following commands in
admin mode. Enter into maintenance mode by using the following command.RP/0/RP0/CPU0:# adminRP/0/RSP0/CPU0(admin)# debug sim reload-disable location<ism_node_location>The card must be in the following state:RP/0/RSP0/CPU0# show platform
Node Type State Config State___________________________________________________________________________0/5/CPU0 A9K-ISM-100(LCP) IOS XR RUN PWR,NSHUT,MON0/5/CPU1 A9K-ISM-100(SE) RECOVERY MODESometimes, the card goes into IN-RESET state due to multiple resets or if you miss to execute the step for a long time.
Reload the card using the following command to get out of the state:RP/0/RSP0/CPU0(admin)# hw-module location <ism_node_location> reload
The command must be executed in adminmode.
Note
Step 4 To install the Services PIE on RSP, run the commands in admin mode:RP/0/RSP0/CPU0#admin(admin)#install add tftp://<tftp_addr>/<image_location>/asr9k-services-p.pie synchronous activate. . . . . . . . . . .(admin)#exit
Step 5 To set the service role as cgn on RSP, run the following commands.RP/0/RSP0/CPU0#config(config)#hw-module service cgn location <ism_node_location>(config)#commit(config)#exit
Step 6 To install Linux Install-Kit from RSP, run the commands in admin mode.RP/0/RSP0/CPU0#adminRP/0/RSP0/CPU0(admin)# download install-image <install_kit_name_and_location> from<rsp_where_kit_present> to <ism_node_location>
You can download the Install-Kit from the File Exchage Serverhttps://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=IOS-XR
Note
Step 7 Wait for around 12-14 minutes for the card to come at SEOS-READY. Proceed with ServiceInfra interface configuration.
Configuring the Service Role for the Carrier Grade IPv6Perform this task to configure the service role on the specified location to start the CGv6 service.
Removal of service role is strictly not recommended while the card is active. This puts the card intoFAILED state, which is service impacting.
Note
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x36
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Service Role for the Carrier Grade IPv6
SUMMARY STEPS
1. configure2. hw-module service cgn location node-id3. endor commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures a CGv6 service role (cgn) on location 0/1/CPU0.hw-module service cgn location node-id
Example:RP/0/RP0/CPU0:router(config)#hw-module service cgn location0/1/CPU0
•When you issue the end command, the system prompts you to commitchanges:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returns therouter to EXEC mode.
◦Entering no exits the configuration session and returns the routerto EXEC mode without committing the configuration changes.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configuration changes.
• Use the commit command to save the configuration changes to therunning configuration file and remain within the configuration session.
Configuring the Service Instance and Location for the Carrier Grade NATPerform this task to configure the service instance and location for the CGN application.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 37
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Service Instance and Location for the Carrier Grade NAT
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-location preferred-active node-id [preferred-standby node-id]4. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application and entersCGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the active and standby locations for the CGN application.service-location preferred-active node-id[preferred-standby node-id]
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x38
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Service Instance and Location for the Carrier Grade NAT
PurposeCommand or Action
• Use the commit command to save the configuration changes tothe running configuration file and remain within the configurationsession.
Configuring the Infrastructure Service Virtual Interface for the Carrier GradeIPv6
Perform this task to configure the infrastructure service virtual interface (SVI) to forward the control traffic.
Access lists are not supported on service virtual interfaces.Note
The subnet mask length must be at least 30 (denoted as /30).
Do not remove or modify service infra interface configuration when the card is in Active state. Theconfiguration is service affecting and the line card must be reloaded for the changes to take effect.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes tothe running configuration file and remain within the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 43
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
Configuring an Inside and Outside Address Pool Map (NAT44)
Perform this task to configure an inside and outside address pool map with the following scenarios:
• The designated address pool is used for CNAT.
• One inside VRF is mapped to only one outside VRF.
• Multiple non-overlapping address pools can be used in a specified outside VRF mapped to differentinside VRF.
• Max Outside public pool per CGSE/CGN instance is 64 K or 65536 addresses. That is, if a /16 addresspool is mapped, then we cannot map any other pool to that particular CGSE.
• Multiple inside vrf cannot be mapped to same outside address pool.
•While Mapping Outside Pool Minimum value for prefix is 16 and maximum value is 26.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. map [outside-vrf outside-vrf-name] address-pool address/prefix6. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application andenters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition for CGN NAT44application.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXEC mode without committing the configurationchanges.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 49
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes tothe running configuration file and remain within the configurationsession.
Configuring the RTSP ALG for NAT44 Instance
Perform this task to configure the ALG for the rtsp for the specified NAT44 instance. RTSP packets areusually destined to port 554. But this is not always true because RTSP port value is configurable.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. alg rtsp [server-port] value5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application and entersCGN configuration mode.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXEC mode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes tothe running configuration file and remain within the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x52
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
TCP Maximum Segment Size Adjustment
When a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.
Static Port Forwarding
Static port forwarding helps in associating a private IP address and port with a statically allocated public IPand port. After you have configured static port forwarding, this association remains intact and does not getremoved due to timeouts until the CGSE is rebooted. In case of redundant CGSE cards, it remains intact untilboth of the CGSEs are reloaded together or the router is reloaded. There are remote chances that after a reboot,this association might change. This feature helps in cases where server applications running on the privatenetwork needs access from public internet.
Configuring Dynamic Port Range
Perform this task to configure a dynamic port range.
•When you issue the end command, thesystem prompts you to commitchanges:
Uncommitted changes found,commit them before exiting(yes/no/cancel)?[cancel]:
◦Entering yes saves configurationchanges to the runningconfiguration file, exits theconfiguration session, andreturns the router to EXECmode.
◦Entering no exits theconfiguration session and returnsthe router to EXEC modewithout committing theconfiguration changes.
◦Entering cancel leaves the routerin the current configurationsession without exiting orcommitting the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain withinthe configuration session.
Configuring External Logging for the NAT Table Entries
Perform the following to configure external logging for NAT table entries.
Netflow LoggingPerform the following tasks to configure Netflow Logging for NAT table entries.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x54
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
Configuring the Server Address and Port for Netflow LoggingPerform this task to configure the server address and port to log network address translation (NAT) tableentries for Netflow logging.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. address address port number8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Path Maximum Transmission Unit for Netflow LoggingPerform this task to configure the path maximum transmission unit (MTU) for the netflowv9-basedexternal-logging facility for the inside VRF.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x56
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. path-mtu value8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Refresh Rate for Netflow LoggingPerform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed orresent to the Netflow-v9 logging server.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x58
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. refresh-rate value8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Timeout for Netflow LoggingPerform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to besent to the Netflow-v9 logging server.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x60
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. timeoutvalue8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Syslog LoggingPerform the following tasks to configure Syslog Logging for NAT table entries.
Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x62
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definitionfor the DS-Lite application.
◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.
◦Entering no exits the configuration session andreturns the router to EXECmode without committingthe configuration changes.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committingthe configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file and remain withinthe configuration session.
Destination-Based Logging for NAT44Perform these tasks to configure destination-based logging for NAT table entries.
Configuring the Session-Logging for Netflow LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 69
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflow6. server7. session-logging8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forCGv6 NAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns therouter to EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Session-Logging for Syslog LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 71
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging syslog6. server7. session-logging8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forCGv6 NAT44 application.
instance. For TCP and UDP, you can configure theinitial and active session timeout values. For ICMP,there are no such options. This configuration isapplicable to all the IPv4 addresses that belong to aparticular service instance. This example configuresthe initial session timeout value as 90 for the TCPsession.
Configures the adjustment MSS value as 1100.msssize
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.
Configuring the RTSP ALG for DS-Lite Instance
Perform this task to configure the ALG for the rtsp for the specified DS-Lite instance. RTSP packets areusually destined to port 554. But this is not always true because RTSP port value is configurable.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. alg rtsp [server-port] value5. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x84
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application and entersCGN configuration mode.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXEC mode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes to therunning configuration file and remain within the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 85
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
TCP Maximum Segment Size Adjustment
When a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.
Configuring an Address Pool Map
Perform this task to configure an address pool map.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. map address-pool address/prefix5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forCGv6 DS-Lite application.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
orRP/0/RP0/CPU0:router(config-cgn-ds-lite)#commit
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x88
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
Configuring External Logging for DS-Lite Entries
Perform the following to configure external logging for DS-Lite entries.
Netflow LoggingPerform the following tasks to configure Netflow Logging for NAT table entries.
Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definitionfor the DS-Lite application.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
orRP/0/RP0/CPU0:router(config-cgn-ds-lite)#commit
[cancel]:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 91
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.
Configuring the Refresh Rate for Netflow LoggingPerform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed orresent to the Netflow-v9 logging server.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging netflowv95. server6. refresh-rate value7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x92
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
Configures the service type keyword definition for CGv6DS-Lite application..
◦Entering yes saves configuration changes tothe running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXECmode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in thecurrent configuration session without exitingor committing the configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file andremain within the configuration session.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 93
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
Configuring the Timeout for Netflow LoggingPerform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to besent to the Netflow-v9 logging server.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging netflowv95. server6. timeoutvalue7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forDS-Lite application.
◦Entering yes saves configuration changes tothe running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXECmode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in thecurrent configuration session without exitingor committing the configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file andremain within the configuration session.
Syslog LoggingPerform the following tasks to configure Syslog Logging for NAT table entries.
Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 95
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definitionfor the DS-Lite application.
•When you issue the end command, thesystem prompts you to commit changes:
Uncommitted changes found, committhem before exiting (yes/no/cancel)?
[cancel]:
◦Entering yes saves configurationchanges to the running configurationfile, exits the configuration session,and returns the router to EXECmode.
◦Entering no exits the configurationsession and returns the router to
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x98
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
EXEC mode without committingthe configuration changes.
◦Entering cancel leaves the router inthe current configuration sessionwithout exiting or committing theconfiguration changes.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Path Maximum Transmission Unit for Syslog LoggingPerform this task to configure the pathmaximum transmission unit (MTU) for the syslog-based external-loggingfacility.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. path-mtuvalue7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for theCGv6 application and enters CGv6 configurationmode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 99
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
Configures the service type keyword definitionfor the DS-Lite application.
•When you issue the end command, the systemprompts you to commit changes:
Uncommitted changes found, commit them beforeexiting (yes/no/cancel)?
[cancel]:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 101
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Destination-Based Logging for DS-LitePerform these tasks to configure destination-based logging for DS-Lite entries.
Configuring the Session-Logging for Netflow LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging netflow95. server6. session-logging7. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x102
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 forthe CGv6 application and enters CGv6configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyworddefinition for the DS-Lite application.
•When you issue the end command,the system prompts you to commitchanges:
Uncommitted changes found,commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes savesconfiguration changes to therunning configuration file,exits the configurationsession, and returns the routerto EXEC mode.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 103
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
◦Entering no exits theconfiguration session andreturns the router to EXECmodewithout committing theconfiguration changes.
◦Entering cancel leaves therouter in the currentconfiguration session withoutexiting or committing theconfiguration changes.
• Use the commit command to savethe configuration changes to therunning configuration file andremain within the configurationsession.
Configuring the Session-Logging for Syslog LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. session-logging7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x104
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
Configures the instance named cgn1 forthe CGv6 application and enters CGv6configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyworddefinition for the DS-Lite application.
•When you issue the end command,the system prompts you to commitchanges:
Uncommitted changes found,commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes savesconfiguration changes to therunning configuration file,exits the configurationsession, and returns the routerto EXEC mode.
◦Entering no exits theconfiguration session andreturns the router to EXECmodewithout committing theconfiguration changes.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 105
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
PurposeCommand or Action
◦Entering cancel leaves therouter in the currentconfiguration session withoutexiting or committing theconfiguration changes.
• Use the commit command to savethe configuration changes to therunning configuration file andremain within the configurationsession.
Configuring Stateful NAT64 on ISMPerform these tasks to configure Stateful NAT64 on ISM.
Configuring the Application Service Virtual Interface
This section lists the guidelines for selecting service application interfaces for 6RD
• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.
• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.
• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.
Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.
Warning
Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.
Caution
Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x106
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM
◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.
◦Entering no exits the configuration session andreturns the router to EXECmodewithout committingthe configuration changes.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committingthe configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file and remainwithinthe configuration session.
Configuring the Policy Functions
Perform these tasks to configure the policy functions.
Configuring MAP-EPerform these tasks to configure MAP-E.
Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for MAP-E.
• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.
• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.
• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 109
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring MAP-E
Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.
Warning
Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.
Caution
Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
orRP/0/RP0/CPU0:router(config-cgn-map_e)#commit
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remain within theconfiguration session.
Configuring MAP-TPerform these tasks to configure MAP-T.
MAP-T is supported only on Cisco ASR 9000 Series 400G and 200GModular Line Cards and Cisco ASR9000 Series 4-Port and 8-Port 100 Gigabit Ethernet Line Cards.
Note
Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for MAP-T.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 125
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring MAP-T
• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.
• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.
• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.
Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.
Warning
Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.
Caution
Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
•When you issue the end command, the system promptsyou to commit changes:
Uncommitted changes found, commit them beforeexiting (yes/no/cancel)?[cancel]:
◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 143
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Address Family
PurposeCommand or Action
◦Entering no exits the configuration session andreturns the router to EXEC mode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in the currentconfiguration session without exiting orcommitting the configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file and remainwithin the configuration session.
Configuring 6RD on ISMPerform these tasks to configure 6RD on ISM.
Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for 6RD
• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.
• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.
• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.
Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.
Warning
Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.
Caution
Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x144
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring 6RD on ISM
•When you issue the end command, the system prompts you to commitchanges:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
orRP/0/RP0/CPU0:router(config-if)#commit
◦Entering yes saves configuration changes to the running configurationfile, exits the configuration session, and returns the router to EXECmode.
◦Entering no exits the configuration session and returns the router toEXEC mode without committing the configuration changes.
◦Entering cancel leaves the router in the current configuration sessionwithout exiting or committing the configuration changes.
• Use the commit command to save the configuration changes to the runningconfiguration file and remain within the configuration session.
By default, failure detection for data path is not triggered unless theabove commands are configured.
Note
To disable failure detection, use the no form of the command: no service-cgv6-halocation node-iddatapath-test
Configuration Examples for Implementing the Carrier GradeNAT
This section provides the following configuration examples for CGN:
Configuring a Different Inside VRF Map to a Different Outside VRF: ExampleThis example shows how to configure a different inside VRF map to a different outside VRF and differentoutside address pools:service cgn cgn1inside-vrf insidevrf1map outside-vrf outsidevrf1 address-pool 100.1.1.0/24!!
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 165
Carrier Grade IPv6 over Integrated Services Module (ISM)Configuration Examples for Implementing the Carrier Grade NAT
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 175
Carrier Grade IPv6 over Integrated Services Module (ISM)PPTP ALG Configuration: Example
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x176
Carrier Grade IPv6 over Integrated Services Module (ISM)PPTP ALG Configuration: Example
C H A P T E R 4Carrier Grade IPv6 over Virtualized ServicesModule (VSM)
This module describes how to implement the Carrier Grade IPv6 (CGv6) over Virtualized Services Module( VSM).
• Virtualized Services Module, page 178
• Installing CGv6 on VSM , page 179
• Uninstalling CGv6 on VSM, page 181
• Upgrading CGv6 OVA Package, page 182
• VSM scale numbers, page 184
• NAT44 over VSM, page 185
• Implementing NAT44 or NAT64 over VSM, page 191
• Traffic Flow Mirroring, page 261
• High Availability, page 273
• Services Redundancy Configuration (Active/Standby): Example, page 277
• Mapping of Address and Port-Encapsulation Mode, page 277
• Configuring MAP-E, page 277
• MAP-E on VSM Configuration: Example, page 294
• Mapping of Address and Port-Translation Mode, page 294
• Configuring MAP-T, page 295
• MAP-T Configuration on VSM: Example, page 313
• Configuration Examples for Implementing the Carrier Grade NAT, page 314
• DS Lite Configuration: Example, page 318
• DBL Configuration: Example, page 319
• Configuring TCP Sequence-Check: Example, page 319
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 177
• Configuring Address and Port-Dependent Filtering: Example, page 319
• NAT0 Mode Configuration: Example, page 320
• Configuration of Multiple NetFlow Servers: Example, page 320
• Configuration of Multiple Syslog Servers: Servers, page 320
Virtualized Services ModuleVirtualized Services Module (VSM) is the next generation service card on the Cisco ASR 9000 SeriesAggregation Services Router. The software infrastructure on this card provides a virtual environment and theservices run as virtual machines (VM) in this environment. The VMs simulate individual physical computingenvironments over a common hardware. The available hardware resources, like processor, memory, hard disk,and so on, are virtualized and allocated to individual virtual machines by the hypervisor.
VSM Components
VSM is capable of hosting multiple VMs. It consists of the following components:
• IOS XR VM: This VM is used for managing the routing functions.
• System Admin VM: This VM is used for the system administration
• Application VM: CGv6 is the application VM running on VSM. In the current release, only one CGv6VM can run at a given time.
• Linux Host and Hypervisor: The routing functions and the system administration functions are run onseparate virtual machines (VMs) over a Linux host operating system. The CGv6 VM, along with theother VMs, runs on the top of the KVM hypervisor.
Features and Considerations
Some of the features and considerations of VSM are:
• The CGv6 application has to run in a VM environment.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x178
Carrier Grade IPv6 over Virtualized Services Module (VSM)Virtualized Services Module
• The IOS XR Service Enablement CLIs are needed to create, delete, access, and operate on CGv6 VM.
• The VSM card can co-exist with other LCs including ISM.
• Each NP has 6 NP ports and can send traffic to 24 CGv6 Application processes.
• For each VSM card, a ServiceInfra interface needs to be configured.
• Traffic diversion may be done based on a static route or ACL-based forwarding (ABF).
• In the current release, VSM does not support multiple CGv6 VMs on the same card.
Installing CGv6 on VSMThe process of installing CGv6 on VSM involves the following:
If you are performing an upgrade or a downgrade, the CGv6 VM needs to be deactivated first, uninstalled,installed, and then activated.
Note
PrerequisitesEnsure that you have installed the following images:
• asr9k-mini-px.vm (Base IOS-XR image)
• asr9k-services-infra.pie (VSM Services Infra package)
• asr9k-services-px.pie (CGv6 Services package)
• asr9k-fpd-px.pie (FPGA Image IOS XR package)
• asr9k-vsm-cgv6-<version>.ova (Linux Open Virtual Alliance or OVA package)
Installing CGv6 OVA PackageThe CGv6 Virtual Machine (VM) is provided as an OVA package. Open Virtualization Appliance (OVA) isa single file distribution of the file package. The CGv6 OVA package consists of the following files:
• OVA Profile Descriptor file
• Package version file
• Linux Image file
The process of installation of CGv6 OVA package consists of the following steps:
1 Copy the OVA file from the remote location to the RP disk.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 179
Carrier Grade IPv6 over Virtualized Services Module (VSM)Installing CGv6 on VSM
Once the CGv6 OVA package is copied to RP's disk, you can install it on multiple VSMs on the samechasis.
Note
2 Install CGv6 VM on a specific VSM card.RP/0/RSP0/CPU0:router# virtual-service install name <service/VM name> package <OVA packagename> node <VSM_location>
The service or VM name can contain only alphanumeric characters (A to Z, a to z, or 0 to 9), or anunderscore (_). All other special characters are not allowed. The installation process might take about 7-8minutes.
Note
3 Check the progress of the installation process by using the show virtual-service list command. Once theinstallation is complete, the status is changed to Installed.RP/0/RSP0/CPU0:router# show virtual-service listVirtual Service List:
Name Status Package Name Nodecgn1 Installing asr9k-vsm-cgv6.ova 0/1/CPU0
RP/0/RSP0/CPU0:NAT#sh virtual-service listVirtual Service List:
Name Status Package Name Nodecgn1 Installed asr9k-vsm-cgv6.ova 0/1/CPU0
Activating CGv6 VMThe steps to activate the CGv6 VM are as follows:
1 Configure the CGv6 VM and the 12 Gigabit Ethernet (GE) interfaces in the global configuration mode.RP/0/RSP0/CPU0:router(config)# virtual-service cgn123RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/0RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/1RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/2RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/3RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/4RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/5RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/6RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/7RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/8RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/9RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/10RP/0/RSP0/CPU0:router(config-virt-service)# vnic interface tenGigE 0/2/1/11RP/0/RSP0/CPU0:router(config-virt-service)# commit
2 Activate the CGv6 VM.RP/0/RSP0/CPU0:router(config-virt-service)# activateRP/0/RSP0/CPU0:router(config-virt-service)#commit
3 Check the progress of the activation process by using the show virtual-service list command. Once theVM is activated, the status changes to Activated.RP/0/RSP0/CPU0:router# show virtual-service listVirtual Service List:
Name Status Package Namecgn1 Activated asr9k-vsm-cgv6.ova
Once the VM is activated, it takes about 5 minutes for the CGv6 applications to come up.Note
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x180
Carrier Grade IPv6 over Virtualized Services Module (VSM)Activating CGv6 VM
5 Before you configure NAT44, ensure that the 12 Gigabit Ethernet (GE) interfaces are up. If they are inthe shutdown mode, then change their mode by using the no shut command.
In IOS-XR, by default, any interface that is not configured is shut down when the associated line card isreloaded. To prevent this behavior on the VSM TenGigE interface (port), add a minor configuration (suchas, description) on the interface.
When a virtual service is in Activating state and being recovered from a failure event like VSM card reloador server disconnect, and if another failure happens like the VSM card reload or server disconnect, thenthe virtual-service activation will not be attempted. In such conditions, virtual service is moved intoActivation Failed state and needs to be recovered manually with the following sequence of operations:RP/0/RSP0/CPU0:router# configure terminalRP/0/RSP0/CPU0:router(config)# virtual-service cgn123RP/0/RSP0/CPU0:router(config-virt-service)# no activateRP/0/RSP0/CPU0:router(config-virt-service)# commitRP/0/RSP0/CPU0:router(config-virt-service)# activateRP/0/RSP0/CPU0:router(config-virt-service)# commit
Note
Uninstalling CGv6 on VSMThe process of uninstalling CGv6 VSM involves the following processes:
• Deactivating CGv6 VM
• Uninstalling CGv6 OVA Package
• Disabling the Service Enablement Feature
Deactivating CGv6 VM
To de-activate the CGv6 VM, perform the following in the global configuration mode:RP/0/RP0/CPU0:router(config)#virtual-service cgn123
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 181
Carrier Grade IPv6 over Virtualized Services Module (VSM)Uninstalling CGv6 on VSM
RP/0/RP0/CPU0:router(config-virt-service)#commitTo remove the CGv6 instance, perform the following in the global configuration mode:RP/0/RP0/CPU0:router(config)#no virtual-service cgn123RP/0/RP0/CPU0:router(config)#commit
Uninstalling CGv6 OVA Package
To uninstall the CGv6 OVA package, run the following commands in the EXEC mode:RP/0/RSP0/CPU0:router# virtual-service uninstall name cgn123
Disabling the Service Enablement Feature
To disable the service enablement feature, run the following commands in the global configuration mode.RP/0/RP0/CPU0:router(config)#no virtual-service enableRP/0/RP0/CPU0:router(config)#commit
Upgrading CGv6 OVA PackageThe CGv6 Virtual Machine (VM) is provided as an OVA package. Open Virtualization Appliance (OVA) isa single file distribution of the file package. The CGv6 OVA package consists of the following files:
• OVA Profile Descriptor file
• Package version file
• Linux Image file
The process of upgrading the CGv6 OVA package consists of the following steps:
1 Saving the virtual service configuration
2 Deactivating CGv6 VM
3 Uninstalling CGv6 OVA Package
4 Upgrading Cisco IOS XR
5 Installing CGv6 on VSM
6 Restoring the virtual service configuration
Before upgrading or downgrading the CGv6 OVA package on the Active VSM card in HA (highavailability) mode, perform a graceful shift of the traffic from Active VSM to Standby VSM. This willensure that the CGN-related configuration is replicated into a standby card. To perform graceful shift ofthe traffic, run the service redundancy failover service-type all preferred-active
<active-VSM-slot> command in EXEC mode.
Note
Saving the Virtual Service Configuration
Before you start upgrading the CGv6 OVA package, save the virtual service configuration and related data.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x182
Carrier Grade IPv6 over Virtualized Services Module (VSM)Upgrading CGv6 OVA Package
To see the virtual service configuration, perform the following in the global configuration mode:RP/0/RP0/CPU0:router(config)# show run virtual-service
Deactivating CGv6 VM
To de-activate the CGv6 VM, perform the following in the global configuration mode:RP/0/RP0/CPU0:router(config)#virtual-service cgn123
RP/0/RP0/CPU0:router(config-virt-service)#commitTo remove the CGv6 instance, perform the following in the global configuration mode:RP/0/RP0/CPU0:router(config)#no virtual-service cgn123RP/0/RP0/CPU0:router(config)#commit
Uninstalling CGv6 OVA Package
To uninstall the CGv6 OVA package, run the following commands in the EXEC mode:RP/0/RSP0/CPU0:router# virtual-service uninstall name cgn123
Upgrading Cisco IOS XR
Upgrade Cisco IOS XR. For details refer the Upgrading and Managing Cisco IOS XR software chapter inCisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide
Installing the CGv6 OVA Package
The process of installing the CGv6 OVA package consists of the following steps:
1 Copy the OVA file from the remote location to the RP disk.
Once the CGv6 OVA package is copied to RP's disk, you can install it on multiple VSMs on the samechasis.
Note
2 Install CGv6 VM on a specific VSM card.RP/0/RSP0/CPU0:router#virtual-service install name <service/VM name> package <OVA packagename> node <VSM_location>
The installation process might take about 7-8 minutes.Note
3 Check the progress of the installation process by using the show virtual-service list command. Once theinstallation is complete, the status is changed to Installed.RP/0/RSP0/CPU0:router#sh virtual-service listVirtual Service List:
Name Status Package Name Nodecgn1 Installing asr9k-vsm-cgv6.ova 0/1/CPU0
RP/0/RSP0/CPU0:NAT#sh virtual-service listVirtual Service List:
Name Status Package Name Nodecgn1 Installed asr9k-vsm-cgv6.ova 0/1/CPU0
Restoring the Virtual Service Configuration
Restore the virtual service configuration.
CGv6 VM is activated automatically after the virtual service configuration is restored.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 183
Carrier Grade IPv6 over Virtualized Services Module (VSM)Upgrading CGv6 OVA Package
Check the progress of the activation process by using the show virtual-service list command. Once the VMis activated, the status changes to Activated.RP/0/RSP0/CPU0:router# show virtual-service listVirtual Service List:
Name Status Package Namecgn1 Activated asr9k-vsm-cgv6.ova
Once the VM is activated, it takes about 5 minutes for the CGv6 applications to come up.Note
VSM scale numbersASR9K supports the following VSM scale numbers:
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
81Number of CGN or CGv6Instances
81Number of Service InfraInterfaces
512Number of Service Appinterfaces
81Number of NAT44 instances
80 MillionsNumber of StatefulTranslation
80 MillionNumber of NAT session
4 MillionNumber of NAT users
6000Number of Static PortForwarding Entries
65536 or 16Number of Public IPv4addresses
128 (inside) + 128 (outside)Number of VRF per NAT44instance
32k per npBNG
8000VRF
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x184
Carrier Grade IPv6 over Virtualized Services Module (VSM)VSM scale numbers
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
15 Groups per NodeGDOI
(There are 15 Groups perNode. Two nodes for S2SVPN.)
80 MillionDS-Lite Sessions
80 MillionNAT64 Sessions
6RD
(ASR 9000 EnhancedEthernet Line Card is inlinewith 6RDwith an expectationrate of 90 percent.)
Number of VSM cards per chassis can be adjusted based on the type of chassis and traffic assessment.Note
NAT44 over VSMThe following are the features that are supported by NAT44 over VSM:
• TCP Sequence Check
• Address and Port-Dependent Filtering
• NAT0 or NAT Bypass Mode
• Static Destination Address Translation
• Multiple NetFlow and Syslog Servers for CGN Logging
VSM scale numbers supported in NAT 44
NAT 44 supports the following VSM scale numbers:
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
81Number of CGN or CGv6Instances
81Number of Service InfraInterfaces
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 185
Carrier Grade IPv6 over Virtualized Services Module (VSM)NAT44 over VSM
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
512Number of Service Appinterfaces
81Number of NAT44 instances
80 x Number of InstalledVSM cards based on type ofchassis. Max 8 number ofVSM cards supported perchassis.
80 MillionsNumber of StatefulTranslation
80 x Number of InstalledVSM cards based on type ofchassis. Max 8 number ofVSM cards supported perchassis.
80 MillionNumber of NAT session
4 xNumber of Installed VSMcards based on type ofchassis. Max 8 number ofVSM cards supported perchassis.
4 MillionNumber of NAT users
6000 x Number of InstalledVSM cards based on type ofchassis. Max 8 number ofVSM cards supported perchassis.
6000Number of Static PortForwarding Entries
65536 or 16Number of Public IPv4addresses
128 (inside) + 128 (outside)Number of VRF per NAT44instance
VSM Scale numbers supported in NAT 64
NAT 64 supports the following VSM scale number:
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
80 MillionsNAT64 Sessions
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x186
Carrier Grade IPv6 over Virtualized Services Module (VSM)NAT44 over VSM
TCP Sequence CheckIn order to overcome security threats to less secure networks, Cisco Virtualized Services Module (VSM)performs TCP sequence check.
A sequence number is a 32-bit number that is included in a packet in a TCP session. The sequence numbersof the incoming packets are stored in the translation or session entry. If a packet's sequence number does notmatch the expected sequence number, then the packet is dropped . In this way, the networks can be securedfrom spoofed packets.
You can perform these TCP sequence checks by using the sequence-check command. An optional keyword,diff-window, has been provided for a user to define and configure the accepted expected range of sequencenumbers. But it is recommended that the user does not specify this range and instead allows the router tocompute the range for each TCP session based on the client-server negotiation.
Two counters are configured for the TCP sequence checks:
• Out-to-In packets counter: This counter keeps a count of the packets whose sequence numbers did notmatch the expected range. But yet these packets are translated and forwarded because TCP sequencecheck has not been configured.
• Dropped packets counter: This counter keeps a count of the packets that were dropped because of theTCP sequence check.
The counters are displayed by using the show cgn nat44 counters command.
Address and Port-Dependent FilteringCurrently, CGN on VSM implements the following by default:
• Endpoint-Independent Mapping: This mapping process reuses the port mapping for subsequent packetsthat are sent from the same internal IP address and port to any external IP address and port.
• Endpoint-Independent Filtering: This filtering process filters out only packets that are not destined tothe internal address and port regardless of the external IP address and port source.
In such a configuration, by knowing the translated IP address and the port of a private host, any malicioushost in a public network can initiate packet floods to that private host. In order to prevent such attacks, theaddress and port-dependent filtering feature has to be enabled by using the filter-policy command. The usercan disable the filtering based on port by using the ignore-port keyword with this command.
Two counters are configured for the address and port-dependent filtering:
• Total number of sessions created due to Out2In packets: This counter keeps a count of the sessions thatwere created by the packets coming from outside.
• Number of Out2In drops due to end point filtering: This counter keeps a count of the packets that weredropped because of the endpoint filtering.
The counters are displayed by using the show cgn nat44 counters command.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 187
Carrier Grade IPv6 over Virtualized Services Module (VSM)TCP Sequence Check
NAT0 or NAT Bypass ModeFor some subscribers, a service provider may want to provide public addresses directly. Hence the NetworkAddress Translation (NAT) is not required for these IP addresses. But at the same time, services like endpointdependent filtering and TCP sequence check are required so that the subscribers do not receive any unwantedtraffic from the Internet. In such cases, NAT0 or NAT Bypass mode is supported per inside-VRF.
The NAT0 mode along with the TCP sequence check and endpoint dependent filtering offers protection tothe subscribers from Outside-to-Inside DoS attacks.
In this mode, when a subscriber sends a packet, an entry is made in the database. When the packet comesfrom the Outside-to-Inside direction, the entry is checked. But no translation occurs. The packet is allowedonly if the entry exists.
NAT0 mode can be enabled by using the nat-mode no-nat command.
Considerations
Some of the considerations regarding the NAT0 mode are as follows:
• Static port forwarding is applicable in this mode.
• Bulk port allocation is not applicable in this mode.
• There is no need for the public address pool to be configured as the translation does not happen.
• If you have not initiated any traffic, then you will not receive any packet. Hence bandwidth can be savedand controlled by the public IP user.
Static Destination Address TranslationIn static destination address translation, the VSM translates the destination IP address along with the sourceIP address. When a packet goes through NAT44, the source IP address translation happens. If the staticdestination address translation is enabled, then the destination IP address translation also takes place. For thesource address translation, the IP address is taken from the public address pool. For the destination addresstranslation, the user needs to provide a 1:1 mapping of the addresses in a .csv file.
To configure static destination address translation, use the static-mapping -file direction command. To deletethe existing configuration use the no static-mapping-file direction command. If you want to modify theexisting configuration, you can edit the existing .csv file and upload it back to the disk.
About the Static Mapping Configuration File
As mentioned before, the static mapping configuration file is in .csv format. The 1:1 mapping of the privateaddresses and the public addresses for the static destination address translation is provided in the .csv file. Ifthis file becomes corrupt, then the destination address will not get translated. This file must be stored on thelocal disk.
The 1:1 mapping of the addresses must be in the following format in the .csv file:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x188
Carrier Grade IPv6 over Virtualized Services Module (VSM)NAT0 or NAT Bypass Mode
13.1.1.5, 12.1.1.5
The IP address, 13.1.1.0, is known as the premap IP address and the IP address, 12.1.1.0, as the postmapIP address
Note
Considerations
Some of the considerations regarding the static destination address translation are as follows:
• The static destination address translation feature currently supports static destination NAT in theInside-to-Outside direction and static source NAT in the Outside-to-Inside direction.
• Currently, the static destination address translation supports NAT44 only.
• The maximum value of entries for static mapping of addresses per VSM is 50K.
High Availability Support for the Route Switch Processor (RSP) Switchover
To ensure high availability during the RSP switchover, the user should manually copy the static mappingconfiguration file on both active RSP as well as the standby RSP.
VSM High Availability Support
The high availability of VSM is supported by default.
CGN and BNG Interoperability through NAT44 over VSMBNG interoperates with Carrier Grade NAT (CGN). To address the impending threat from IPv4 address spacedepletion, it is recommended that the remaining or available IPv4 addresses be shared among larger numbersof customers. This is done by using CGN, which primarily pulls the address allocation to a more centralizedNAT in the service provider network. NAT44 is a technology that uses CGN and helps manage depletionissues of the IPv4 address space. BNG supports the ability to perform NAT44 translation on IPoE andPPPoE-based BNG subscriber sessions.
For BNG and CGN interoperability, configure the BNG interface and the application service virtualinterface (SVI) on the same VRF instance.
Note
Multiple NetFlow and Syslog Servers for CGN LoggingCisco IOS XR supports High Availability for NAT44 through multiple NetFlow or Syslog servers. Startingfrom Release 5.2.0, you can configure up to 8 additional NetFlow or Syslog Servers for a single inside VRFinstance.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 189
Carrier Grade IPv6 over Virtualized Services Module (VSM)CGN and BNG Interoperability through NAT44 over VSM
In an inside VRF with multiple servers configured, the NetFlow logging policy will be enabled on allservers if it is enabled for one or more servers inside the VRF.
Note
In an inside VRFwith multiple servers configured, the Syslog logging policy will be enabled on all serversif it is enabled for one or more servers inside the VRF.
Note
Dual Stack LiteThe Dual Stack Lite (DS-Lite) feature enables legacy IPv4 hosts and server communication over both IPv4and IPv6 networks. Also, IPv4 hosts may need to access IPv4 internet over an IPv6 access network. The IPv4hosts will have private addresses which need to have network address translation (NAT) completed beforereaching the IPv4 internet. The Dual Stack Lite application has these components:
• Basic Bridging BroadBand Element (B4): This is a Customer Premises Equipment (CPE) router thatis attached to the end hosts. The IPv4 packets entering B4 are encapsulated using a IPv6 tunnel and sentto the Address Family Transition Router (AFTR).
• Address Family Transition Router(AFTR): This is the router that terminates the tunnel from the B4.It decapsulates the tunneled IPv4 packet, translates the network address and routes to the IPv4 network.In the reverse direction, IPv4 packets coming from the internet are reverse network address translatedand the resultant IPv4 packets are sent the B4 using a IPv6 tunnel.
The Dual Stack Lite feature helps in these functions:
1 Tunnelling IPv4 packets from CE devices over IPv6 tunnels to the CGSE blade.
2 Decapsulating the IPv4 packet and sending the decapsulated content to the IPv4 internet after completingnetwork address translation.
3 In the reverse direction completing reverse-network address translation and then tunnelling them overIPv6 tunnels to the CPE device.
IPv6 traffic from the CPE device is natively forwarded.
VSM scale numbers supported in Dual Stack Lite
Dual Stack Lite supports the following VSM scale number:
Value per ASR9K Chassiswith VSM
Value per VSMParameter Name
80 MillionsDS-Lite Sessions
Scalability and Performance of DS Lite• Supports a total of 60 million translations.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x190
Carrier Grade IPv6 over Virtualized Services Module (VSM)Dual Stack Lite
• Number of unique users behind B4 router, basically IPv6 and IPv4 Source tuple, can scale to 1 million.
• There is no real limit to the number of B4 routers and their associated tunnels connecting to the AFTR,except the session limit, which is 20 million B4 routers (assuming each router has only one session). Inreality, a maximum of 1 million B4 routers can connect to an AFTR at any given time.
• The performance of DS-Lite traffic, combined IPv4 and IPv6, is 39 Gbps.
Implementing NAT44 or NAT64 over VSMThis section explains the implementation of NAT44 or NAT64 on VSM.
Configuring NAT44 over VSMPerform the following tasks to configure NAT44 on VSM:
1 Configuring a NAT44 Instance, on page 42
2 Configuring the Application Service Virtual Interface (NAT44), on page 41
3 Configuring an Inside and Outside Address Pool Map (NAT44), on page 44
Configuring a NAT44 InstancePerform this task to configure a NAT44 instance.
The system does not support deleting VRF on live traffic in the following scenarios:Note
• If you are in the global configuration mode.
• If you are within the CGN instance.
• If you are in the static route table.
SUMMARY STEPS
1. configure2. service cgn nat44instance-name3. service-location preferred-active VSM location4. service-type nat44 nat15. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 191
Carrier Grade IPv6 over Virtualized Services Module (VSM)Implementing NAT44 or NAT64 over VSM
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6 NAT44 applicationand enters CGv6 configuration mode.
service cgn nat44instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the NAT preferred active VSM location.service-location preferred-activeVSM location
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes tothe running configuration file and remain within the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x192
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring NAT44 over VSM
Configuring the Application Service Virtual Interface (NAT44)Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
SUMMARY STEPS
1. configure2. interface ServiceApp value3. service cgn instance-name service-type nat444. vrf vrf-name5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the application SVI as 1 and enters interface configurationmode.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 193
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring NAT44 over VSM
PurposeCommand or Action
◦Entering no exits the configuration session and returns therouter to EXEC mode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes to therunning configuration file and remain within the configurationsession.
Configuring an Inside and Outside Address Pool Map (NAT44)Perform this task to configure an inside and outside address pool map with the following scenarios:
• The designated address pool is used for CNAT.
• One inside VRF is mapped to only one outside VRF.
• Multiple non-overlapping address pools can be used in a specified outside VRF mapped to differentinside VRF.
• Max Outside public pool per CGSE/CGN instance is 64 K or 65536 addresses. That is, if a /16 addresspool is mapped, then we cannot map any other pool to that particular CGSE.
• Multiple inside vrf cannot be mapped to same outside address pool.
•While Mapping Outside Pool Minimum value for prefix is 16 and maximum value is 26.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. map [outside-vrf outside-vrf-name] address-pool address/prefix6. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x194
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring NAT44 over VSM
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application andenters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition for CGN NAT44application.
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returnsthe router to EXEC mode without committing theconfiguration changes.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 195
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring NAT44 over VSM
PurposeCommand or Action
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changesto the running configuration file and remain within theconfiguration session.
Configuring DS-LitePerform these tasks to configure DS-Lite.
Configuring the Application Service Virtual InterfacePerform this task to configure the application service virtual interface (SVI) to forward data traffic.
SUMMARY STEPS
1. configure2. interface ServiceApp value3. service cgn instance-name service-type ds-lite4. vrf vrf-name5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the application SVI as 1 and enters interface configurationmode.
instance. For TCP and UDP, you can configure theinitial and active session timeout values. For ICMP,there are no such options. This configuration isapplicable to all the IPv4 addresses that belong to aparticular service instance. This example configuresthe initial session timeout value as 90 for the TCPsession.
Configures the adjustment MSS value as 1100.msssize
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remain within the configurationsession.
Configuring the Timeout Value for ICMP, TCP and UDP SessionsPerform this task to configure the timeout value for ICMP, TCP or UDP sessions for a Dual Stack Lite (DSLite) instance:
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. protocol tcp session {active | initial} timeout value or protocol {icmp | udp} timeout value5. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x204
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6 applicationand enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition for CGv6DS-Lite application.
•When you issue the end command, the system prompts you tocommit changes:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x206
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.
Configuring the RTSP ALG for DS-Lite InstancePerform this task to configure the ALG for the rtsp for the specified DS-Lite instance. RTSP packets areusually destined to port 554. But this is not always true because RTSP port value is configurable.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. alg rtsp [server-port] value5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 207
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Configures the instance named cgn1 for the CGN application and entersCGN configuration mode.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXEC mode without committing the configurationchanges.
◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.
• Use the commit command to save the configuration changes to therunning configuration file and remain within the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x208
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
TCP Maximum Segment Size AdjustmentWhen a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.
Configuring an Address Pool MapPerform this task to configure an address pool map.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. map address-pool address/prefix5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forCGv6 DS-Lite application.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
orRP/0/RP0/CPU0:router(config-cgn-ds-lite)#commit
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 211
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Configuring External Logging for DS-Lite EntriesPerform the following to configure external logging for DS-Lite entries.
Netflow Logging
Perform the following tasks to configure Netflow Logging for NAT table entries.
Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definitionfor the DS-Lite application.
•When you issue the end command, the system prompts you tocommit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
orRP/0/RP0/CPU0:router(config-cgn-ds-lite)#commit
[cancel]:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x214
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.
Configuring the Refresh Rate for Netflow LoggingPerform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed orresent to the Netflow-v9 logging server.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging netflowv95. server6. refresh-rate value7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 215
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Configures the service type keyword definition for CGv6DS-Lite application..
◦Entering yes saves configuration changes tothe running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXECmode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in thecurrent configuration session without exitingor committing the configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file andremain within the configuration session.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x216
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Configuring the Timeout for Netflow LoggingPerform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to besent to the Netflow-v9 logging server.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging netflowv95. server6. timeoutvalue7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forDS-Lite application.
◦Entering yes saves configuration changes tothe running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXECmode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in thecurrent configuration session without exitingor committing the configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file andremain within the configuration session.
Syslog Logging
Perform the following tasks to configure Syslog Logging for NAT table entries.
Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x218
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definitionfor the DS-Lite application.
•When you issue the end command, thesystem prompts you to commit changes:
Uncommitted changes found, committhem before exiting (yes/no/cancel)?
[cancel]:
◦Entering yes saves configurationchanges to the running configurationfile, exits the configuration session,and returns the router to EXECmode.
◦Entering no exits the configurationsession and returns the router to
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 221
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
EXEC mode without committingthe configuration changes.
◦Entering cancel leaves the router inthe current configuration sessionwithout exiting or committing theconfiguration changes.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Path Maximum Transmission Unit for Syslog LoggingPerform this task to configure the pathmaximum transmission unit (MTU) for the syslog-based external-loggingfacility.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. path-mtuvalue7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for theCGv6 application and enters CGv6 configurationmode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x222
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Configures the service type keyword definitionfor the DS-Lite application.
•When you issue the end command, the systemprompts you to commit changes:
Uncommitted changes found, commit them beforeexiting (yes/no/cancel)?
[cancel]:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x224
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Destination-Based Logging for DS-Lite
Perform these tasks to configure destination-based logging for DS-Lite entries.
Configuring the Session-Logging for Netflow LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging netflow95. server6. session-logging7. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 225
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 forthe CGv6 application and enters CGv6configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyworddefinition for the DS-Lite application.
•When you issue the end command,the system prompts you to commitchanges:
Uncommitted changes found,commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes savesconfiguration changes to therunning configuration file,exits the configurationsession, and returns the routerto EXEC mode.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x226
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
◦Entering no exits theconfiguration session andreturns the router to EXECmodewithout committing theconfiguration changes.
◦Entering cancel leaves therouter in the currentconfiguration session withoutexiting or committing theconfiguration changes.
• Use the commit command to savethe configuration changes to therunning configuration file andremain within the configurationsession.
Configuring the Session-Logging for Syslog LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. session-logging7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 227
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring DS-Lite
PurposeCommand or Action
Configures the instance named cgn1 forthe CGv6 application and enters CGv6configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyworddefinition for the DS-Lite application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns therouter to EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Timeout Value for ICMP, TCP and UDP SessionsPerform this task to configure the timeout value for ICMP, TCP or UDP sessions for a Dual Stack Lite (DSLite) instance:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x230
Carrier Grade IPv6 over Virtualized Services Module (VSM)Policy Functions
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. protocol tcp session {active | initial} timeout value or protocol {icmp | udp} timeout value5. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6 applicationand enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition for CGv6DS-Lite application.
•When you issue the end command, the system promptsyou to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 231
Carrier Grade IPv6 over Virtualized Services Module (VSM)Policy Functions
PurposeCommand or Action
◦Entering no exits the configuration session andreturns the router to EXEC mode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in the currentconfiguration sessionwithout exiting or committingthe configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file and remainwithin the configuration session.
FTP-ALGCGN supports both passive and active FTP. FTP clients are supported with inside (private) address and serverswith outside (public) addresses. Passive FTP is provided by the basic NAT function. Active FTP is used withthe ALG.
RTSP-ALGCGN supports the Real Time Streaming Protocol (RTSP), an application-level protocol for control over thedelivery of data with real-time properties. RTSP provides an extensible framework to enable controlled,on-demand delivery of real-time data, such as audio and video. Sources of data can include both live datafeeds and stored clips.
PPTP-ALGPPTP is a network protocol that enables secure transfer of data from a remote client to a private enterpriseserver by creating a Virtual Private Network (VPN). It is used to provide IP security at the network layer.PPTP uses a control channel over TCP and a GRE tunnel operating to encapsulate PPP packets.
PPTP-ALG is a CGN solution that allows traffic from all clients through a single PPTP tunnel.
A PPTP tunnel is instantiated on the TCP port. This TCP connection is then used to initiate and manage asecond GRE tunnel to the same peer.
PPTP uses an access controller and network server to establish a connection.
PPTP Access Controller (PAC)
A device attached to one or more PSTN or ISDN lines capable of PPP operation and handling the PPTPprotocol. It terminates the PPTP tunnel and provides VPN connectivity to a remote client.
PPTP Network Server (PNS)
A device which provides the interface between the Point-to-Point Protocol (encapsulated in the PPTP protocol)and a LAN or WAN. The PNS uses the PPTP protocol to support tunneling between a PPTP PAC and thePNS. It requests to establish a VPN connectivity using PPTP tunnel.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x232
Carrier Grade IPv6 over Virtualized Services Module (VSM)Policy Functions
Control Connection
A control connection is established between a PAC and a PNS for TCP.
Tunnel
A tunnel carries GRE encapsulated PPP datagrams between a PAC and a PNS
Active FTP, PPTP ALG, and RTSP ALG are supported on NAT44 applications. Active FTP and RTSPALG are supported on DS-Lite applications.
Note
TCP Maximum Segment Size AdjustmentWhen a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.
Static Port ForwardingStatic port forwarding helps in associating a private IP address and port with a statically allocated public IPand port. After you have configured static port forwarding, this association remains intact and does not getremoved due to timeouts until the CGSE is rebooted. In case of redundant CGSE cards, it remains intact untilboth of the CGSEs are reloaded together or the router is reloaded. There are remote chances that after a reboot,this association might change. This feature helps in cases where server applications running on the privatenetwork needs access from public internet.
Configuring Dynamic Port RangePerform this task to configure a dynamic port range.
Enables the address and port-dependent filtering. The optionalignore-port keyword is used to disable the port-dependent filtering.
filter-policy ignore-port
Example:
Step 5
To enable address and port-dependent filteringRP/0/RP0/CPU0:router(config-cgn-invrf)#filter-policyTo enable address and port-dependent filtering whenthe port is not checked:RP/0/RP0/CPU0:router(config-cgn-invrf)#filter-policy ignore-port
◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.
◦Entering no exits the configuration session andreturns the router to EXEC mode withoutcommitting the configuration changes.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committingthe configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file and remainwithin the configuration session.
Configuring the Static Destination Address TranslationPerform the following steps to configure static destination address translation:
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. map [outside-vrf outside-vrf-name] address-pool address/prefix6. static-mapping-file direction i2o-dst path of the .csv file7. end or commit
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 241
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring the Static Destination Address Translation
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application andenters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition for CGN NAT44application.
Configures static destination address translation using the staticmapping configuration file (.csv). In this example, the file is storedin disk0: location.
static-mapping-file direction i2o-dst path of the .csvfile
Example:RP/0/RP0/CPU0:router(config-cgn-invrf-afi)#static-mapping-file direction i2o-dst/disk0:/30K.CSV
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring External Logging for the NAT Table EntriesPerform the following to configure external logging for NAT table entries.
Configuring the Server Address and Port for Netflow LoggingPerform this task to configure the server address and port to log network address translation (NAT) tableentries for Netflow logging.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. address address port number8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x248
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring External Logging for the NAT Table Entries
PurposeCommand or Action
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 249
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring External Logging for the NAT Table Entries
PurposeCommand or Action
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Path Maximum Transmission Unit for Netflow LoggingPerform this task to configure the path maximum transmission unit (MTU) for the netflowv9-basedexternal-logging facility for the inside VRF.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. path-mtu value8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x250
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring External Logging for the NAT Table Entries
PurposeCommand or Action
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 251
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring External Logging for the NAT Table Entries
PurposeCommand or Action
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Configuring the Refresh Rate for Netflow LoggingPerform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed orresent to the Netflow-v9 logging server.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. refresh-rate value8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 253
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring External Logging for the NAT Table Entries
PurposeCommand or Action
Configuring the Timeout for Netflow LoggingPerform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to besent to the Netflow-v9 logging server.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. timeoutvalue8. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definition forNAT44 application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 255
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring External Logging for the NAT Table Entries
Syslog LoggingPerform the following tasks to configure Syslog Logging for NAT table entries.
Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGv6application and enters CGv6 configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Configures the service type keyword definitionfor the DS-Lite application.
◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.
◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.
◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.
• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.
Traffic Flow MirroringTraffic flow mirroring is a solution which enables you to monitor the incoming and outgoing traffic on theVSMmodule (of ASR9K) running a CGN instance. This solution helps you to debug and analyze packets forissues pertaining to NAT-ing (NAT44). The traffic is filtered based on a set of particular parameters, whichcan be set by the user. The packets, collected, are encapsulated in a GRE envelope and sent to a pre-configured
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 261
Carrier Grade IPv6 over Virtualized Services Module (VSM)Traffic Flow Mirroring
collector like a UNIX system, laptop, etc. This envelope contains a field, which provides information aboutthe type of packet whether the packets are In2Out packet, Out2In packet, pre-NAT, post-NAT, or dropped,analyzing this field information, the issues pertaining to NAT can be debugged.
Salient Features:
• Any packets dropped will be mirrored.
• The packets are filtered based on destination address; and refined further based on port number, protocol,and IP addresses of the subscriber devices that are mirrored.
• Mirroring of up to 16 VRFs is supported when the destination address filter is configured. There is nolimit on the number of VRFs supported when the mirroring is enabled for only the dropped packets.
Figure 1: Traffic Flow Mirroring Topology
If the packets are filtered based on the destination IP address, then destination IP address is a mandatory fieldfor the solution whereas a few of the fields like protocol used, destination port, private source prefix, etc. areoptional.
Mirroring occurs only for packets that are intercepted after the feature is turned on.Note
Mirrored Packet Data Interpretation
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x262
Carrier Grade IPv6 over Virtualized Services Module (VSM)Traffic Flow Mirroring
The packets received at the collector have the original packet as the payload encapsulated in a GRE header.A typical GRE header is as shown in the following figure.
Figure 2: GRE Header
The KEY field in the GRE header contains the value. The following table lists the values and the descriptionassociated with those values.
Table 4: List of KEY field values and their descriptions:
DescriptionValue
In to Out direction, pre-nat packet1
Out to In direction, pre-nat packet2
In to Out direction, post-nat packet3
Out to In direction, post-nat packet4
Dropped In to Out TCP, PPTP control message packet.5
Dropped In to Out TCP Fragment packet. (Received non-first fragment.)6
Dropped In to Out TCP packet. (Failed to create new NAT entry.)7
Dropped In to Out TCP packet due to no session entry.8
Dropped In to Out TCP packet. (Source port is zero)9
Dropped In to Out TCP packet. (None sync drop)10
Dropped In to Out TCP packet (Session creation fail)11
Dropped In to Out TCP packet with TTL <= 1. (No ICMP generateddue to throttling)
12
Dropped packet as ICMP is sent for first fragment only.13
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 263
Carrier Grade IPv6 over Virtualized Services Module (VSM)Traffic Flow Mirroring
Dropped packet due to Invalid ICMP error code.14
Dropped In to Out due ICMP error packet with TTL <= 1.15
Dropped In to Out ICMP packet due to no NAT entry.16
Dropped Out to In ICMP packet (ipv4 packet too large for the tunnel)17
Dropped Out to In ICMP packet due to no NAT entry.18
Dropped In to Out ICMP packet due to no session.19
Dropped In to Out ICMP packet with TTL <= 1. (No ICMP generateddue to throttling)
20
Dropped In to Out ICMP query packet due to no NAT entry.21
Dropped Out to In ICMP query. (No NAT entry)22
Dropped Out to In ICMP query packet due to end point filtering. (EDFis enabled).
23
Dropped Out to In ICMP query packet, could not generate ICMP packetdue to throttling.
24
Dropped Out to In ICMP packet due to no session.25
Dropped Out to In ICMP packet due to no NAT entry.26
Dropped port control protocol (PCP) packet, as it couldn't be handled.27
Dropped In to Out PPTP packet (PPTP not configured)28
Dropped In to Out PPTP packet with TTL <= 1 (No ICMP generateddue to throttling)
29
Dropped Out to In PPTP packet (PPTP not configured)30
Dropped Out to In PPTP fragment packet (No NAT entry)31
Dropped Out to In PPTP packet (No NAT entry)32
Dropped Out to In PPTP packet with TTL <= 1. (No ICMP generateddue to throttling.)
33
Dropped In to Out UDP packet (Has no available ports)34
Dropped In to Out UDP packet (UDP port value of 0).35
Dropped In to Out UDP packet (No configuration available).36
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x264
Carrier Grade IPv6 over Virtualized Services Module (VSM)Traffic Flow Mirroring
Dropped In to Out UDP packet (No ICMP message generated).37
Dropped In to Out UDP packet (Create session failed).38
Dropped In to Out UDP packet (VRF not in run state)39
Dropped In to Out UDP packet (Port limit exceeded)40
Dropped In to Out UDP packet with TTL <= 1. (No ICMP generateddue to throttling.)
41
Dropped In to Out UDP packet (No direct port available).42
Dropped Out to In UDP packet (No NAT entry).43
Dropped Out to In UDP packet due to end point filtering. (EDF isenabled)
44
Dropped Out to In UDP packet (No NAT entry).45
Dropped Out to In UDP packet (Create session DB failed or Sessionlimit exceeded.)
46
Dropped Out to In UDP packet as it is too large for tunneling.ICMP not generated due tothrottling.
Note47
Dropped Out to In UDP packet (Create session failed.)48
Dropped Out to In UDP fragment packet (No NAT entry).49
Not used50
Dropped Out to In Error fragment packet.51
Dropped Out to In unsupported protocol Fragment packet.52
Dropped Out to In TCP packet (PPTP control message dropped.)53
Dropped Out to In TCP packet (No NAT entry)54
Dropped Out to In TCP packet (First fragment packet drop)55
Dropped Out to In TCP due to end point filtering. (EDF is enabled.)56
Dropped Out to In UDP packet as it is too large for tunneling.ICMP not generated due tothrottling.
Note57
Dropped Out to In TCP packet. (Create session failed.)58
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 265
Carrier Grade IPv6 over Virtualized Services Module (VSM)Traffic Flow Mirroring
Dropped Out to in TCP fragment packet (No NAT entry)59
Dropped Out to in TCP packet (SYN or RST flags not set for TCPsession to be established.)
60
Dropped Out to in TCP packet (Sequence mismatch)61
Dropped Out to In TCP packet with TTL <= 1. (No ICMP generateddue to throttling.)
62
Limitations and AssumptionsThe following are a few of the assumptions and limitations of the traffic flow mirroring solution:
• At any given point in time, only one traffic flow mirroring per inside-vrf is allowed.
• If the collector IP address is not configured, the traffic packet mirroring is blocked. In case the collectorIP address is not reachable, the mirrored packets are dropped.
• If the protocol is not provided, both TCP and UDP packets are mirrored.
• If the port number is not mentioned, the traffic flowing through all the destination ports are mirrored.
• If a private source IP address is not configured, the mirroring is performed for all subscribers of theVRF, that is listed. This can reduce the performance of VSM and also lead to choking the collector. Itis advisable to configure as many parameters as possible to filter and mirror only the required packets.
• Performance figures of VSM are not guaranteed when traffic mirroring is on.
• Traffic flow mirroring solution assumes that the collector is reachable to the router in the default VRF.The router does not attempts to ping or get acknowledgments to ascertain if the collector is receivingthe packets.
Configuring Mirroring Using Destination Address Filter and Collector IPAddress
Perform this task to configure mirroring the traffic packets using a destination address filter and collector IPaddress.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x266
Carrier Grade IPv6 over Virtualized Services Module (VSM)Limitations and Assumptions
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-location preferred-active node-id4. service-type nat44 nat1 instance5. inside-vrf vrf-name6. mirror-packets7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application andenters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Specifies the global command applied per CGN instance. It initiatesthe particular instance of the CGN application on the active andstandby locations.
•When you issue the end command, the system prompts youto commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
RP/0/RP0/CPU0:router(config-cgn-invrf)#commit
[cancel]:
◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.
◦Entering no exits the configuration session and returnsthe router to EXEC mode without committing theconfiguration changes.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.
• Use the commit command to save the configuration changesto the running configuration file and remain within theconfiguration session.
The following example shows how to filter and configure data packets to be mirrored onto a collector withthe destination IP address and the collector IP address provided.
service cgn cgn1service-location preferred-active 0/1/CPU0service-type nat44 nat1inside-vrf BLR_BTMmirror-packetsdestination-ipv4-address 201.22.3.45!collector-ipv4-address 187.2.3.55!!!!
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x268
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring Mirroring Using Destination Address Filter and Collector IP Address
Configuring Mirroring Using Destination Address, Port Number, Protocol Type,Source-Prefix Filters, and Collector IP Address
Perform this task to configure mirroring the traffic packets using a destination address, port number, protocoltype, source-prefix filter and collector IP address.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-location preferred-active node-id4. service-type nat44 nat1 instance5. inside-vrf vrf-name6. mirror-packets7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN applicationand enters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgn cgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Specifies the global command applied per CGN instance. Itinitiates the particular instance of the CGN application on theactive and standby locations.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 269
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring Mirroring Using Destination Address, Port Number, Protocol Type, Source-Prefix Filters, and Collector
IP Address
PurposeCommand or Action
Configures the traffic packets to be mirrored onto the provideddestination collector IP address.
•When you issue the end command, the system promptsyou to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.
◦Entering no exits the configuration session andreturns the router to EXECmode without committingthe configuration changes.
◦Entering cancel leaves the router in the currentconfiguration session without exiting or committingthe configuration changes.
• Use the commit command to save the configurationchanges to the running configuration file and remain withinthe configuration session.
The following example shows how to filter and configure packets to be mirrored onto a collector with thedestination details like the IP address, protocol type, port number, source-prefix filter, and the collector IPaddress.
service cgn cgn1service-location preferred-active 0/1/CPU0service-type nat44 nat1inside-vrf BLR_BTM3mirror-packets
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x270
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring Mirroring Using Destination Address, Port Number, Protocol Type, Source-Prefix Filters, and CollectorIP Address
Configuring Mirroring for Dropped Packets Using Collector IP AddressPerform this task to configure mirroring the dropped traffic packets using collector IP address.
SUMMARY STEPS
1. configure2. service cgn instance-name3. service-location preferred-active node-id4. service-type nat44 nat1 instance5. inside-vrf vrf-name6. mirror-packets7. end or commit
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the instance named cgn1 for the CGN application andenters CGN configuration mode.
service cgn instance-name
Example:RP/0/RP0/CPU0:router(config)# service cgncgn1RP/0/RP0/CPU0:router(config-cgn)#
Step 2
Specifies the global command applied per CGN instance. It initiatesthe particular instance of the CGN application on the active andstandby locations.
High AvailabilityHigh Availability (HA) or 1:1 redundancy enables network-wide protection by providing fast recovery fromfaults that may occur in any part of the network. With Cisco High Availability on the module, the networkhardware and software work together and enable rapid recovery from disruption, to ensure fault transparencyto users and network applications. It provides continuous access to applications, data, and content anywhere,anytime by addressing potential causes of downtime with functionality, design, and best practices.
HA supports:
• 1:1 active or standby redundancy infrastructure for the services running on the module
◦Intra-chassis redundancy
◦Cold standby redundancy
• Replication of CGN-related configuration into a standby card
Before upgrading or downgrading the CGv6 OVA package on the Active VSM card inHA mode, perform a graceful shift of the traffic from Active VSM to Standby VSM.This will ensure that the CGN-related configuration is replicated into a standby card.For more information refer Upgrading CGv6 OVA Package, on page 182.
Note
• Failure detection
◦Data path - Channel through which CGV6 application data packets traverse
◦CPU health monitoring
◦Control path
◦Crashed processes
The following commands are supported for failure detection:
By default, failure detection for data path is not triggered unless the above command isconfigured.
Note
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 273
Carrier Grade IPv6 over Virtualized Services Module (VSM)High Availability
The service-cgv6-ha location location-name datapath-test disable configurationdisables the heartbeat packets (health check packets) flowing in VSM. By default, thesepackets are flowing. You can disable these packets when required.
Note
• Failure reporting and recovery
◦If redundant module is configured, then switch-over the stand by module to active and reload theactive module.
◦If redundant module is not configured, then reload the module. This comes up again as an activemodule.
Redundancy Switchover Using CLI
You can trigger the switchover the failover by running the following the commands to an active slot and viceversa. :
Use the following command to switchover the failover to a preferred active slot.RP/0/RP0/CPU0:router(config)# service redundancy failover service-type all preferred-active<preferred-active slot>Use the following command to revert the failover to a preferred active slot.RP/0/RP0/CPU0:router(config)# service redundancy revert service-type all preferred-active<preferred-active slot>
Configuring High AvailabilityISM and VSM supports high availability or 1:1 redundancy on different CGv6 applications.
Perform these tasks to configure HA.
Configuring Active or Standby ModulePerform this task to configure active or standby module.
SUMMARY STEPS
1. configure2. service cgn <instance name>3. service-location preferred-active node-id[preferred-standby node-id]4. end or commit5. reload
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x274
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuring High Availability
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure
Example:RP/0/RP0/CPU0:router# configure
Step 1
Configures the infrastructure service virtual interface (SVI) for boththe module locations.
Mapping of Address and Port-Encapsulation ModeMapping of Address and Port-EncapsulationMode (MAP-E) is a CGN solution that allows a service providerto enable IPv4 services at IPv6 (customer) sites to which it provides Customer Premise Equipment (CPE).This approach utilizes stateless IPv4-in-IPv6 encapsulation to transit IPv6-enabled network infrastructure.The encapsulation must be supported by the CPE and MAP-E Gateway/Border Relay, which removes theIPv6 encapsulation from IPv4 packets while forwarding them to the Internet. The provider access networkcan now be on IPv6, while customers see IPv6 and IPv4 service simultaneously.
MAP-E also helps manage IPv4 address exhaustion by keeping the stateful NAT44 on CPE. MAP-E is notsupported on any of the VRF interfaces, that is, either IPv4 or IPv6, whereas Map-T is supported with VRFinterfaces along with an SMU.
Configuring MAP-EPerform these tasks to configure MAP-E.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 277
Carrier Grade IPv6 over Virtualized Services Module (VSM)Services Redundancy Configuration (Active/Standby): Example
Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for MAP-E.
• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.
• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.
• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.
Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.
Warning
Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.
Caution
Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
Mapping of Address and Port-Translation ModeMapping of Address and Port-Translation Mode (MAP-T) is a CGN solution that enables IPv4-only clientsto communicate with IPv6-only resources using address and packet translation. MAP-T is also referred to asDual IVI (dIVI) or Stateless NAT46. This enables a service provider to offer IPv4 services to IPv6 enabled(customer) sites to which it provides customer premise equipment (CPE). This approach utilizes stateless IPv4to IPv6 translation (that is NAT64) to transit IPv6-enabled network infrastructure. The provider access networkcan now be on IPv6, while customers use IPv6 and IPv4 services simultaneously. MAP-T keeps the statefulNAT44 on CPE, as usual, to handle IPv4 address exhaustion, in addition to stateless NAT64 on CPE andBorder Router.
MAP-T is attractive to those SPs who have deployed, or are planning to deploy IPv6 end-to-end services, andwant to manage IPv4 address exhaustion with utmost predictability.
MAP-T is a preferred alternate to DS-Lite in a sevice provider network when there is no tunneling needed.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x294
Carrier Grade IPv6 over Virtualized Services Module (VSM)MAP-E on VSM Configuration: Example
MAP-T is offered in stateless mode only.Note
Configuring MAP-TPerform these tasks to configure MAP-T.
MAP-T is supported only on Cisco ASR 9000 Series 400G and 200GModular Line Cards and Cisco ASR9000 Series 4-Port and 8-Port 100 Gigabit Ethernet Line Cards.
Note
Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for MAP-T.
• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.
• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.
• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.
Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.
Warning
Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.
Caution
Perform this task to configure the application service virtual interface (SVI) to forward data traffic.
Configuring TCP Sequence-Check: ExampleThis example shows how to configure sequence check for TCP sessions.configureservice cgn cgn1service-type nat44 nat1inside-vrf vrf1firewall protocol tcpsequence-check
Configuring Address and Port-Dependent Filtering: ExampleThis example shows how to configure address and port-dependent filtering.configureservice cgn cgn1
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 319
Carrier Grade IPv6 over Virtualized Services Module (VSM)DS Lite Configuration
NAT0 Mode Configuration: ExampleThis example shows how to configure the NAT0 mode:service cgn cgn1service-location preferred-active 0/2/CPU0service-type nat44 nat1inside-vrf Inside_1map outside-vrf ovrf outsideServiceApp ServiceApp2 address-pool 0.0.0.0/0nat-mode no-nat
Configuration of Multiple NetFlow Servers: Exampleservice cgn cgn1service-location preferred-active 0/1/CPU0service-type nat44 nat1inside-vrf ivrfmap outside-vrf ovrf outsideServiceApp ServiceApp2 address-pool 100.1.1.0/24external-logging netflow version 9serveraddress 111.1.1.1 port 6000path-mtu 1200refresh-rate 600timeout 1000session-logging!address 111.1.1.1 port 9000path-mtu 1100refresh-rate 500timeout 1000session-logging!address 122.1.1.1 port 9000path-mtu 1200refresh-rate 500timeout 1100session-logging!!!
Configuration of Multiple Syslog Servers: Serversservice cgn cgn1service-location preferred-active 0/1/CPU0service-type nat44 nat1inside-vrf ivrfmap outside-vrf ovrf outsideServiceApp ServiceApp2 address-pool 100.1.1.0/24external-logging syslogserveraddress 211.1.1.1 port 6000path-mtu 1200session-logging!address 211.1.1.1 port 9000path-mtu 1200session-logging!
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x320
Carrier Grade IPv6 over Virtualized Services Module (VSM)NAT0 Mode Configuration: Example
address 212.1.1.1 port 6000path-mtu 1200session-logging!!!
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 321
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuration of Multiple Syslog Servers: Servers
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x322
Carrier Grade IPv6 over Virtualized Services Module (VSM)Configuration of Multiple Syslog Servers: Servers
C H A P T E R 5External Logging
External logging configures the export and logging of the NAT table entries, private bindings that areassociated with a particular global IP port address, and to use Netflow to export the NAT table entries.
• Bulk Port Allocation, page 323
• Session logging, page 324
• Syslog Logging, page 324
• Reliable Log Transfer, page 343
• Frequently Asked Questions (FAQs), page 345
Bulk Port AllocationThe creation and deletion of NAT sessions lead to creation of logs. If logs of all such translations are stored,then a huge volume of data is created. This data is stored on a NetFlow or a Syslog collector. To reduce thevolume of this data, a block of ports is allocated. If bulk port allocation is enabled, as soon as a subscribercreates the first session, a number of contiguous external ports are allocated. To indicate this allocation, abulk allocation message is created in the log.
The bulk allocation message is created only during the first session. Rest of the sessions use one of theallocated ports. Hence no logs are created for them.
Note
A bulk delete message is created in the log when the subscriber deletes all the sessions that are using theallocated ports.
Another pool of ports is allocated only if the number of simultaneous sessions is more than N where N is thesize of the bulkk allocation. The size of the pool can be configured from the CLI.
Restrictions for Bulk Port AllocationThe restrictions for bulk port allocation are as follows:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 323
• The value for the size of bulk allocation can be 16, 32, 64, 128, 256, 512, 1024, 2048 and 4096. Foroptimum results, it is recommended that you set this size to half of the port limit.
• If the size of bulk allocation is changed, then all the current dynamic transactions will be deleted. Henceit is advisable to change the bulk port allocation size (only if necessary) during a maintenance window.
• The port numbers below the value of dynamic-port-range start value (which is 1024 by default), are notallocated in bulk.
• The algorithm that is used to allocate a public address to a user remains the same.
•When bulk allocation is enabled, session logging is not available.
•When bulk allocation is enabled, the translation record will not contain information about L4 protocol.
• Bulk port allocation features is not supported in NAT64 stateful application.
Session loggingIn general, NAT translation entries contain information about private source IP, port and translated public IPand port. However, there could be cases when the destination IP address (public IP address) and port mayalso be needed. In such cases, session logging has to be enabled so that Netflow or Syslog translation recordsinclude these values as well.
Syslog LoggingPerform the following tasks to configure Syslog Logging for NAT table entries.
Restrictions for SyslogThe restrictions for syslog are as follows:
• Syslog is supported over UDP only.
• Syslog is supported in ASCII format only.
• You cannot log onto multiple collectors or relay agents.
• All the messages comply to RFC 3954 except for the timestamp format. Timestamp is represented in asimpler way as explained later in this section.
• Syslog shall be supported for DS-Lite and NAT444 as of now. Support for NAT64 is not yet available.
Syslog Message FormatIn general, the syslog message is made up of header, structured data, and msg fields. However, in the CGv6applications, the structured data is not used.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x324
External LoggingSession logging
HeaderThe header fields shall be as per the RFC 5424. Fields shall be separated by ' ' (white space) as per the RFC.
The header consists of the following fields:
DescriptionField
• The priority value represents both the facilityand severity.
• Ensure that the severity code is set toInformational for all the messages at value 6.
Priority
• This field denotes the version of thespecification of the syslog protocol.
• In CGv6 application, the version value is set to1.
Version
• This field is needed to trace the port usage.
• The format is <year> <mon> <day><hh:mm:ss>.
• Ensure that the syslog collector converts thetime to local time whenever needed.
The timestamp is always reported inGMT/UTC irrespective of the timezone configured on the device.
Note
Timestamp
• This field is used to identify the device that sentthe syslog message.
•While configuring the syslog server, ensure thatthe host name does not exceed 31 characters.
• The default value for the host name is '-'.
Hostname
These fields are not included. In ASCII format, '-' isincluded for these fields.
App name and PROC ID
• This field identifies the type of the syslogmessage.
• In the ASCII format, the values for NAT44 andDS Lite messages are NAT44 and DS LITErespectively.
MSG ID
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 325
External LoggingSyslog Message Format
Structured DataIt is not used.
MSGThis field consists of the information about the NAT44 or DS Lite events. In a single UDP packet, there couldbe one or moreMSG fields each enclosed in [] brackets. TheMSG field has many sub fields as it has a commonstructure across different records (for both NAT44 and DS Lite). Note, that, depending on the event, some ofthe fields may not be applicable. For example, fields such as 'Original Source IPv6' address are not applicablefor all NAT44 events. In such cases, the inapplicable fields will be replaced by '-'.
The descriptions of the fields in this format are as follows:DescriptionField
Select any one of the values for EventName from thefollowing based on the event:
• UserbasedA: User-based port assignment
• SessionbasedA: Session-based port assignment
• SessionbasedAD: Session-based port assignmentwith destination information
Note: SessionbasedAD is used only if sessionlogging is enabled. Also, session-logging andbulk port allocation are mutually exclusive.
• UserbasedW: User-based port withdrawal
• SessionbasedW: Session-based port withdrawal
• SessionbasedWD: Session-based portwithdrawal with destination information
• Portblockrunout: Ports exhausted
EventName
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x326
External LoggingSyslog Message Format
DescriptionField
Specifies the identifier for the transport layer protocol.Select any one of the values for L4 from thefollowing:
• 1 for ICMP
• 6 for TCP
• 17 for UDP
• 47 for GRE
L4
Specify the private IPv4 address.Original Source IP
The Inside vrf is essential to identify the subscriber.Even though multiple subscribers connected to therouter might have the same source IP, they might beplaced in different VRFs. Hence the VRF name andthe original source IP together helps to identify asubscriber. Ensure that the VRF name is not morethan 32 characters in length.
Inside VRF Name
Specifies the IPv6 source address of the tunnel in caseof DS Lite.
Original Source IPv6
Specifies the public IPv4 address post translation.Translated Source IP
Specifies the source port number before translation.This is not applicable for the UserbasedA andUserbasedW events.
Original Port
Specifies the first source port after translation.Translated First Source Port
Specifies the last source port after translation. Thisis applicable only for the UserbasedA andUserbasedW events.
Translated Last Source Port
Specifies the destination IP recorded in the syslogsfor the SessionbasedAD and SessionbasedWDevents.
Destination IP
Specifies the destination port recorded in the syslogsfor the SessionbasedAD and SessionbasedWDevents.
Destination Port
Let us look at an example for NAT444 user-based UDP port translation mapping:[UserbasedA - 10.0.0.1 Broadband - 100.1.1.1 - 2048 3071 - -]
The description for this example is as follows:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 327
External LoggingSyslog Message Format
DescriptionValue
Event NameUserbasedA
Original Source IP10.0.0.1
Inside VRF nameBroadband
Translated Source IP100.1.1.1
Translated First Source Port2048
Translated Last Source Port3071
The number of MSG fields in an UDP packet are determined by the following factors:Note
• The space available in the UDP packet depends on MTU.
• The translation events pertaining to MSG records in a given packet must have happened within asecond (starting from the time at which the first event of that packet happened).
Netflow v9 SupportThe NAT64 stateful, NAT44, and DS Lite features support Netflow for logging of the translation records..The Netflow uses binary format and hence requires software to parse and present the translation records.However, for the same reason, Netflow requires lesser space than Syslog to preserve the logs.
Considerations
The considerations for NetFlow are as follows:
• NetFlow V9 is supported over UDP.
• You cannot log onto multiple collectors or relay agents.
• All the messages comply to RFC 3954.
NetFlow Record FormatAs NetFlowV9 is based on templates, the record format contains a packet header and templates or data recordsbased on templates.
Header
All the fields of the header follow the format prescribed in RFC 3954. The source ID field is composed ofthe IPv4 address of ServiceInfra interface (of the card) and specific CPU-core that is generating the record.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x328
External LoggingNetflow v9 Support
The collector device can use the combination of the sourceIPv4Address field plus the Source ID field toassociate an incoming NetFlow export packet with a unique instance of NetFlow on a particular device.
Templates for NAT44
The templates are defined and used for logging various NAT64 stateful, NAT44 and DS Lite events as follows.The templates may change in future software releases. Hence it is advised that the Netflow collector softwareis designed to understand the templates as distributed by the router and accordingly parse the records.
Options Templates
The translation entries consist of VRF IDs which might be incomprehensible to a user. To simplify this process,the CGv6 applications send the options templates along with the data templates.
Options template is a special type of data record that indicates the format of option data related to the processof NetFlow. The options data consist of the mapping between VRF Ids and VRF names. By parsing and usingthis data, the NetFlow collectors can modify the translation entries by adding VRF names instead of VRFIDs.
The value for the Template ID of options template is 1 where as the value of the Template ID for data templateis 0. For more information on Options template, see RFC3954.
Events
The events and the corresponding template details are described in the following table:
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 329
Reliable Log TransferThe VSM Line Cards support CGN application with NAT 44 feature. NAT 44 feature performs IPv4 NAToperations. The CGN applications based on server configuration generates NetFlow and Syslog records that
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 343
External LoggingReliable Log Transfer
contain critical NAT information. If an external NetFlow server is configured for storage and retrieval of NATinformation, the information is transferred to the server using UDP connection.
The CGN application VM running on VSM also supports transfer of records to external NetFlow serversusing TCP. This provides reliable log transfer. Use the protocol command to define the protocol to be usedfor the transfer.
Limitations
• Netflow and syslog records may be lost during any reload of VSM or restart of IOS XR VM or process.
• A maximum of two NetFlow or Syslog servers are supported.
• Server IP address along with the port number defines one server.
• Same TCP server can be configured on any number of VRFs and is considered as one TCP server.
• Loss of TCP connection may result in loss of NetFlow records.
• Bulk port allocation needs to be enabled with a minimum allocation value of 256 to prevent loss of NAT44 records, when Syslog and Netflow records are sent using TCP protocol.
Reliable Log Transfer Configuration: ExamplesConfigure NetFlow records' transport using TCP protocol when the TCP server is in the default globalVRF instance:service cgn cgn1service-location preferred-active 0/3/CPU0service-type nat44 nat1inside-vrf insidevrf1map outside-vrf outsidevrf1 outsideServiceApp ServiceApp2 address-pool 100.1.1.0/24external-logging netflow version 9serveraddress 45.1.1.1 port 65535protocol tcp
Configure NetFlow records' transport using TCP protocol when the TCP server is in an non-defaultVRF instance:service cgn cgn1service-location preferred-active 0/3/CPU0service-type nat44 nat1inside-vrf insidevrf1map outside-vrf outsidevrf1 outsideServiceApp ServiceApp2 address-pool 100.1.1.0/24external-logging netflow version 9serveraddress 55.1.1.1 port 4500protocol tcp vrf netflow-srv-vrf
Configure Syslog records' transport using TCP protocol when the TCP server is in the default globalVRF instance:service cgn cgn1service-location preferred-active 0/3/CPU0service-type nat44 nat1inside-vrf insidevrf1
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x344
External LoggingReliable Log Transfer Configuration: Examples
Configure Syslog records' transport using TCP protocol when the TCP server is in an non-default VRFinstance:service cgn cgn1service-location preferred-active 0/3/CPU0service-type nat44 nat1inside-vrf insidevrf1map outside-vrf outsidevrf1 outsideServiceApp ServiceApp2 address-pool 100.1.1.0/24external-logging syslogserveraddress 55.1.1.1 port 4500protocol tcp vrf syslog-srv-vrf
Frequently Asked Questions (FAQs)This section provides answers to the following frequently asked questions on external logging.
Q: How to trace a subscriber by using the NAT logs?
A: In order to trace a subscriber, you should know the public source IP address (post NAT source address),post NAT source port, protocol, and the time of usage. With these parameters, the steps to trace a subscriberare as follows:
1 Search for the create event that has the matching public IP address, post NAT Source IP address(postNATSourceIPv4Address) and protocol, egress VRF ID/Name and the time of the usage. Ensure thatthe time of the create-event is the same or earlier than the time of usage reported. You may not find theprotocol entry or the exact post NAT source port in the logs if bulk allocation is enabled. In such cases,find the create-event whose Post NAT Port Block Start and Post NAT Port Block End values includethe post NAT source port. The Pre NAT source IP address along with the corresponding ingress VRFID/Name will identify the subscriber.
2 The corresponding delete record may be found optionally to confirm that the subscriber was using thespecified public IP and port during the time of the reported usage.
Q: The Netflow records provide VRF IDs for ingress and egress VRFs. How will I know the VRF names?
A: The following are the two ways to find the VRF name from the VRF ID.
1 Use the command show rsi vrf-id <vrf-id> on the Router console to find VRF-ID to VRF-NAMEassociations.
2 The CGv6 applications periodically send out option templates containing the VRF-ID to VRF-NAMEmapping. The Netflow collector software presents the information with VRF-Names rather than VRF IDs.
Q: Does the time format in Syslog or Netflow account for Day light saving?
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 345
External LoggingFrequently Asked Questions (FAQs)
A: The Syslog and Netflow formats report time corresponding to GMT/UTC. The Netflow header containsthe time in seconds that elapsed since EPOCH whereas the Syslog header contains time in human readableformats. In both cases, the day light saving is not accounted. The Netflow/Syslog collectors have to make thatadjustments if needed.
Q: Since the Netflow and Syslog use UDP, how can we know if a packet containing translation record waslost?
A: The Netflow header contains a field called Sequence Number. This number is indicates the count of thepacket coming from each Source ID. The Netflow collector traces the Seqence Number pertaining to eachunique Source ID. The sequence numbers should be increased by one for each packet sent out by the Source.If the collector ever receives two successive packets with the same Source ID, but with a Sequence numberdifference of more than 1, it indicate a packet loss. However, currently, no such mechanism exists for Syslog.
Q: What is the use of session-logging?
A: Session logging includes destination IP and port number as well. Though this information is not directlyuseful in tracing the subscriber, in some cases, this information may be useful or may be mandated by thelegal authorities. There are cases where, legal authorities may not have the post NAT source 'port', howevermay know the destination IP address (and optionally destination port, such as IP address and port of an e-mailserver). In the absence of post NAT source port information, a list of subscribers who used the specified publicIP during that time may have to be pruned further based on the destination IP and port information.
Q: How does the bulk port allocation reduce data volume of translation logs?
A: With bulk port allocation, subscribers are allocated a range of contiguous ports on a public IP. Quite often,a subscriber will need more ports than just one. Especially AJAX based web pages and other web applicationssimultaneously open several ports. In such cases, pre-allocated ports are used and only one log entry is madethat specifies the range of ports allocated to the user. Hence, bulk port allocation significantly reduces logdata volume and hence the demand on storage space needed for the translation logs.
Q: What else can be done to reduce log data volume?
A: Predefined NAT is an option that can be used to eliminate the logging altogether. The Predefined NATtranslates private IP address to public IP address and a certain port range by using an algorithm. Hence thereis no need to keep track of NAT entries.
Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x346