Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 4.2.x
Implementing the Carrier Grade IPv6
Downloads: This chapterpdf (PDF - 832.0KB) The complete bookPDF (PDF - 1.15MB) | Feedback

Table of Contents

Implementing the Carrier Grade IPv6 on Cisco IOS XR Software

Contents

Prerequisites for Implementing the CGv6

CGv6 Overview and Benefits

CGv6 Overview

Benefits of CGv6

IPv4 Address Shortage

NAT44 or CGN Overview

Network Address and Port Mapping

DS-Lite Overview

Scalability and Performance of DS Lite

Information About Implementing CGv6

Implementing NAT with ICMP

ICMP Query Session Timeout

Implementing NAT 44 over ISM

Implementing NAT 64 over ISM

Double NAT 444

Policy Functions

Application Level Gateway

TCP Maximum Segment Size Adjustment

Static Port Forwarding

External Logging

Netflow v9 Support

Syslog Support

Bulk Port Allocation

Cisco Integrated Service Module (ISM)

Solution Components

Configuring CGv6 on Cisco IOS XR Software

Installing Carrier Grade IPv6 (CGv6) on ISM

Hardware

Software

FPGA UPGRADE

Accessing CPU consoles on ISM Card

Installing CGv6 Application on an ISM Running CDS-TV/CDS-IS for Cisco IOS XR Software Release 4.2.0

Installing CGv6 Application on an ISM Running CDS-TV/CDS-IS for Cisco IOS XR Software Release 4.2.1

Getting Started with the Carrier Grade IPv6

Configuring the Service Role

Configuring the Service Instance and Location for the Carrier Grade IPv6

Configuring the Service Virtual Interfaces

Configuring the Service Type Keyword Definition

Configuring an Inside and Outside Address Pool Map

Configuring the Policy Functions for NAT44

Configuring the Port Limit Per Subscriber

Configuring the Timeout Value for the Protocol

Configuring the TCP Adjustment Value for the Maximum Segment Size

Configuring the Refresh Direction for the Network Address Translation

Configuring Static Port Forwarding

Configuring the Dynamic Port Ranges

Configuring External Logging for the Network Address Translation Table Entries

Configuring the Server Address and Port for Netflow Logging

Configuring the Path Maximum Transmission Unit for Netflow Logging

Configuring the Refresh Rate for Netflow Logging

Configuring the Timeout for Netflow Logging

Configuring Bulk Port Allocation

Configuring Syslog

Configuring DS Lite Feature on ISM Line Card

Configuring a DS Lite Instance

Configuring an Address Pool Map for a DS-Lite Instance

Configuring Bulk Port Allocation for a DS Lite Instance

Configuring Syslog for a DS Lite Instance

Configuring IPv6 Tunnel Endpoint Address for a DS-Lite Instance

Configuring the Path Maximum Transmission Unit for a DS-Lite Instance

Configuring the Port Limit Per Subscriber for a DS-Lite Instance

Configuring the Timeout Value for the Protocol for a DS-Lite Instance

Configuring the TCP Adjustment Value for the Maximum Segment Size for a DS-Lite Instance

Configuring the External Logging for a DS-Lite Instance

Configuration Examples for Implementing the CGv6

Configuring a Different Inside VRF Map to a Different Outside VRF for NAT44: Example

NAT44 Configuration: Example

Bulk Port Allocation and Syslog Configuration: Example

DS Lite Configuration: Example

IPv6 ServiceApp and Static Route Configuration

IPv4 ServiceApp and Static Route Configuration

DS Lite Configuration

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Implementing the Carrier Grade IPv6 on Cisco IOS XR Software

This module describes how to implement the Carrier Grade IPv6 (CGv6) on Cisco IOS XR software.

Contents

The following table lists changes made to the document.

Table 1 Feature History for Implementing CGv6 on ASR 9000

Release
Modification

R4.2.0

Initial release of this document.

CGv6 applications such as CGN or NAT44 are supported.

R4.2.1

The following features were introduced:

  • DS-Lite.
  • Syslog and Bulk Port Allocation for NAT44 and DS-Lite.

Prerequisites for Implementing the CGv6

The following prerequisites are required to implement CGv6:

  • You must be running Cisco IOS XR software Release 4.2.0 or above.
  • You must have installed the CGv6 service package, asr9k-services-p.pie ( to be used with RSP2) or asr9k-services-px.pie (to be used with RSP3).
  • You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command.

NoteAll the error conditions result in a syslog message. On observation of Heartbeat failure messages, contact Cisco Technical Support withshow tech-support services cgn information.



NoteIf you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


CGv6 Overview and Benefits

To implement the CGv6, you should understand the following concepts:

CGv6 Overview

Internet Protocol version 4 (IPv4) has reached exhaustion at the international level (IANA). But service providers 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 increasing rate. The Cisco Carrier Grade IPv6 Solution (CGv6) is designed to help address these challenges. With Cisco CGv6, you can:

  • Preserve investments in IPv4 infrastructure, assets, and delivery models.
  • 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 efficiencies that IPv6 can deliver.

Cisco CGv6 extends the already wide array of IPv6 platforms, solutions, and services. Cisco CGv6 helps you build 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 therefore different CGv6 solutions or applications are implemented on this platform (specifically on ISM service card). In Cisco IOS XR Release 4.2.0, CGN or NAT44 application is delivered as the first application. In Cisco IOS XR Release 4.2.1, the DS-Lite feature is added. Additional CGv6 applications will be delivered in future releases.

Benefits of CGv6

CGv6 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 Shortage

A fixed-size resource such as the 32-bit public IPv4 address space will run out in a few years. Therefore, the IPv4 address shortage presents a significant and major challenge to all service providers who depend on large blocks 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 that need to access the public IPv4 Internet.

NAT44 or CGN Overview

Carrier Grade Network Address Translation (CGN) is a large scale NAT that is capable of providing private IPv4 to public IPv4 address translation in the order of millions of translations 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 provider subscribers and content providers to implement a seamless transition to IPv6. CGN employs network address and 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 private IP subscribers assuming each subscriber requires 100 ports. For example, each TCP connection needs one port number.

A Network Address Translation (NAT) box is positioned between private and public IP networks that are addressed with non-global private addresses and a public IP addresses respectively. A NAT performs the task of mapping one or many private (or internal) IP addresses into one public IP address by employing both network 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 port values
  • Stores the private-to-public binding information in a table and sends the packet. When the public IP host returns a packet, it is addressed to the NAT. The stored binding information is used to replace the IP destination 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 private IP 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 can use the NAT functions combined with the firewall to offer security protection for corporate resources and allow for provider-independent IPv4 addresses. NATs have made it easier for private IP home networks to flourish independently from service provider IP address provisioning. Enterprises can permanently employ private IP addressing for Intranet connectivity while relying on a few NAT boxes, and public IPv4 addresses for external public Internet connectivity. NAT boxes in conjunction with classic methods such as Classless Inter-Domain Routing (CIDR) have slowed public IPv4 address consumption.

Network Address and Port Mapping

Network address and port mapping can be reused to map new sessions to external endpoints after establishing a first mapping between an internal address and port to an external address. These NAT mapping definitions are defined from RFC 4787:

  • Endpoint-independent mapping —Reuses the port mapping for subsequent packets that are sent from the 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 the same internal IP address and port to the same external IP address, regardless of the external port.

NoteCGN on ISM implements Endpoint-independent Mapping.


Translation Filtering

RFC 4787 provides translation filtering behaviors for NATs. These options are used by NAT to filter packets originating from specific external endpoints:

  • Endpoint-independent filtering —Filters out only packets that are not destined to the internal address and port regardless of the external IP address and port source.
  • Address-dependent filtering —Filters out packets that are not destined to the internal address. In addition, NAT filters out packets that are destined for the internal endpoint.
  • 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 not sent previously.

NoteCGN on ISM implements Endpoint-independent Filtering.


DS-Lite Overview

The Dual Stack Lite (DS-Lite) feature enables legacy IPv4 hosts and server communication over both IPv4 and IPv6 networks. Also, IPv4 hosts may need to access IPv4 internet over an IPv6 access network. The IPv4 hosts will have private addresses which need to have network address translation (NAT) completed before reaching the IPv4 internet.

The Dual Stack Lite application has these two components:

  • Basic Bridging BroadBand Element (B4): This is a Customer Premises Equipment (CPE) router that is attached to the end hosts. The IPv4 packets entering B4 are encapsulated using a IPv6 tunnel and sent to 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 translated and the resultant IPv4 packets are sent the B4 using a IPv6 tunnel.

The Dual Stack Lite feature helps in these functions:

  • Tunnelling IPv4 packets from CE devices over IPv6 tunnels to the ISM blade.
  • Decapsulating the IPv4 packet and sending the decapsulated content to the IPv4 internet after completing network address translation.
  • In the reverse direction completing reverse-network address translation and then tunnelling them over IPv6 tunnels to the CPE device.

IPv6 traffic from the CPE device is natively forwarded.


NoteThe number of DS-Lite instances supported on the Integrated Service Module (ISM) line card is 64.


Scalability and Performance of DS Lite

The DS-Lite feature pulls translation entries from the same pool as the NAT44.

  • Supports a total of 20 million sessions.
  • 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). In reality, 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 10 Gbps.

Information About Implementing CGv6

These sections provide the information about implementation of NAT using ICMP and TCP:

Implementing NAT with ICMP

This section explains how the Network Address Translation (NAT) devices work in conjunction with Internet Control Message Protocol (ICMP).

The implementations of NAT varies in terms of how they handle different traffic.

ICMP Query Session Timeout

RFC 5508 provides ICMP Query Session timeouts. A mapping timeout is maintained by NATs for ICMP queries that traverse them. The ICMP Query Session timeout is the period during which a mapping will stay active without packets traversing the NATs. The timeouts can be set as either Maximum Round Trip Time (Maximum RTT) or Maximum Segment Lifetime (MSL). For the purpose of constraining the maximum RTT, 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 NAT resources such as Query mappings and NAT Sessions for the whole duration. Also, if the timeout is set to very 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 a balance between the two extremes.

Implementing NAT 44 over ISM

The following figure illustrates the implementation of NAT 44 over 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 known as 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 data packet may be sent from another line card through a backplane. Because the ISM card does not have 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 and the 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 App SVI1.

  • Outside VRF: It denotes the VRF that handles packets going out to the public network. It is known as outside 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 a NAT implementation.

 

The packet goes through the following steps when it travels from the private network to the public network:


Step 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 address has to be mapped to the public address by NAT44 that is implemented in ISM.

Step 2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 0. While using NAT44, it is mandatory that the packet enters through VRF.

Step 3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the inside VRF either through static routing or ACL-based forwarding (ABL). After the inside VRF determines that the packet needs address translation, it is forwarded to the App SVI that is bound to the VRF.

Step 4 The packet is forwarded by AppSVI1 through a default static route (ivrf1). The destination address and the port get translated because of the CGN configuration applied on ISM.

Step 5 The ISM applies NAT44 to the packet and a translation entry is created. The CGN determines the destination address from the FIB Look Up. It pushes the packet to the egress port.

Step 6 The packet is then forwarded to the egress port on the interface through App SVI2. An inside VRF is mapped to an outside VRF. The outside VRF is associated with this interface. The packet is forwarded by App SVI2 through the default static route (ovrf1). Then the packet is sent to the public network.

Step 7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to the destination 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:


Step 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 address has to be mapped to the private address by NAT44 that is implemented in ISM.

Step 2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 0.

Step 3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the outside VRF either through static routing or ACL-based forwarding (ABL).

Step 4 The packet is forwarded by App SVI2 through a default static route. The destination address and the port are mapped to the translated address.

Step 5 The ISM applies NAT44 to the packet. The CGN determines the destination address from the FIB Look Up. It pushes the packet to the egress port.

Step 6 The packet is then forwarded to the egress port on the interface through App SVI2. Then the packet is sent to the private network through the inside VRF.

Step 7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to the destination through a different static route and a different egress port.

Implementing NAT 64 over ISM

This section explains how NAT64 is implemented over ISM. The figure illustrates the implementation of NAT64 over ISM.

 

The components of this implementation are as follows:

  • 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 known as 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 data packet may be sent from another line card through a backplane. Because the ISM card does not have 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 and the 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 App SVI1.

  • Outside VRF- It denotes the VRF that handles packets going out to the public network. It is known as outside 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 a NAT64 implementation.

 

The packet goes through the following steps when it travels from the private network to the public network:


Step 1 In the network shown in this figure, the packet travels from the host A (having the IP address 3001:DB8:E0E:E03::/40) in the private network to host B (having the IP address 11.11.11.2) in the public network. The private address has to be mapped to the public address by NAT64 that is implemented in ISM.

Step 2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 3.

Step 3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the inside VRF either through static routing or ACL-based forwarding (ABL). Based on this routing decision, the packet that needs address translation is determined and is forwarded to the App SVI that is bound to the VRF.

Step 4 The packet is forwarded by AppSVI1 through a default static route. The destination address and the port get translated because of the CGN configuration applied on ISM.

Step 5 The ISM applies NAT64 to the packet and a translation entry is created. The CGN determines the destination address from the FIB Look Up. It pushes the packet to the egress port.

Step 6 The packet is then forwarded to the egress port on the interface through App SVI2. The packet is forwarded by App SVI2 through the default static route. Then the packet is sent to the public network.

Step 7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to the destination 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:


Step 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. The public address has to be mapped to the private address by NAT64 that is implemented in ISM.

Step 2 The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 3.

Step 3 Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the outside VRF either through static routing or ACL-based forwarding (ABL). Based on this routing decision, the packet is forwarded to the App SVI that is bound to the VRF.

Step 4 The packet is forwarded by App SVI2 through a default static route. The destination address and the port are mapped to the translated address.

Step 5 The ISM applies NAT64 to the packet. The CGN determines the destination address from the FIB Look Up. It pushes the packet to the egress port.

Step 6 The packet is then forwarded to the egress port on the interface through App SVI2. Then the packet is sent to the private network through the inside VRF.

Step 7 The packets that do not need the address translation can bypass the App SVI and can be forwarded to the destination through a different static route and a different egress port.

Double NAT 444

The Double NAT 444 solution offers the fastest and simplest way to address the IPv4 depletion problem without requiring an upgrade to IPv6 anywhere in the network. Service providers can continue offering new IPv4 customers access to the public IPv4 Internet by using private IPv4 address blocks, if the service provider is large enough; However, they need to have an overlapping RFC 1918 address space, which forces the service provider to partition their network management systems and creates complexity with access control lists (ACL).

Double NAT 444 uses the edge NAT and CGv6 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 a subscriber have 100 connections to hosts on the Internet). There is no easy way for a private IPv4 host to communicate with the CGv6 to learn its public IP address and port information or to configure a static incoming port forwarding.

Application Level Gateway

The application level gateway (ALG) deals with the applications that are embedded in the IP address payload.

CGv6 supports both passive and active FTP. FTP clients are supported with inside (private) address and servers with outside (public) addresses. Passive FTP is provided by the basic NAT function. Active FTP is used with the ALG.

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 maximum segment 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 configures a fixed, private (internal) IP address and port that are associated with a particular subscriber while CGv6 allocates a free public IP address and port. Therefore, the inside IP address and port are associated to a free outside IP address and port.

External Logging

External logging configures the export and logging of the NAT table entries, private bindings that are associated with a particular global IP port address, and to use Netflow to export the NAT table entries.

Netflow v9 Support

The NAT44 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 format and hence requires software to parse and present the translation records.

Syslog Support

In Cisco IOS XR Software Release 4.2.1 and later, the DS Lite and NAT44 features support Syslog as an alternative to Netflow. Syslog uses ASCII format and hence can be read by users. However, the log data volume is higher in Syslog than Netflow.

Attributes of Syslog Collector

  • Syslog is supported in ASCII format only.
  • Logging to multiple syslog collectors (or relay agents) is not supported.
  • Syslog is supported for DS-Lite and NAT444 in the Cisco IOS XR Software Release 4.2.1.

Bulk Port Allocation

The creation and deletion of NAT sessions need to be logged and these create huge amount of data. These are stored on Syslog collector which is supported over UDP. In order to reduce the volume of data generated by the NAT device, bulk port allocation can be enabled. When bulk port allocation is enabled and when a subscriber creates the first session, a number of contiguous outside ports are pre-allocated. A bulk allocation message is logged indicating this allocation. Subsequent session creations will use one of the pre-allocated port and hence does not require logging.

Cisco Integrated Service Module (ISM)

Solution Components

These are the solution components of the Cisco Integrated Service Module (ISM).

  • 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 required to bring up ISM. This is of local significance within the chassis.

ServiceApp SVI is used to forward the data traffic to the Application. Scale of ISM 244 ServiceApp per chassis is validated. These interfaces can be advertised in IGP/EGP.

Configuring CGv6 on Cisco IOS XR Software

The following configuration tasks are required to implement CGv6 on Cisco IOS XR software:

Installing Carrier Grade IPv6 (CGv6) on ISM

This section provides instructions on installing CGv6 on the ISM line card, removing CGv6 on the ISM line card, 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 UPGRADE

The installation is similar to an FPGA upgrade on any other ASR 9000 cards.


Step 1 Load the fpd pie.

Step 2 Run the show hw-module fpd location <> command in admin mode.

 
 
RP/0/RP0/CPU0:#admin
RP/0/RSP1/CPU0:LHOTSE#show hw-module fpd location 0/1/CPU0
===================================== ================================================
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
1.0 lc cbc 0 18.04 Yes
1.0 lc cpld1 0 0.01 No
1.0 lc fpga7 0 0.17 No
1.0 lc cpld3 0 0.16 No
1.0 lc fpga2 0 0.01 Yes
--------------------------------------------------------------------------------------
 

If one or more FPD needs an upgrade (can be identified from the Upg/Dng column in the output) then this can be accomplished 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 the admin mode.

show hw-module fpd location <>
 


 

Accessing CPU consoles on ISM Card

The following output shows ISM card in slot1:

RP/0/RSP0/CPU0 #show platform
0/RSP0/CPU0 A9K-RSP-4G(Active) IOS XR RUN PWR,NSHUT,MON
0/1/CPU0 A9K-ISM-100(LCP) IOS XR RUN PWR,NSHUT,MON
0/1/CPU1 A9K-ISM-100(SE) SEOS-READY

To access LC CPU console:

RP/0/RSP0/CPU0#run attach 0/1/CPU0
#

To return to RSP console:

#exit

To access X86 CPU console:

RP/0/RSP0/CPU0:CRANE#run attachCon 0/0/cpu1 115200
attachCon: Starting console session to node 0/0/cpu1
attachCon: To quit console session type 'detach'
Current Baud 115200
Setting Baud to 115200
 
localhost.localdomain login: root
Password: rootroot
[root@localhost ~]#
 

To return to RSP console:

[root@localhost]# detach

Installing CGv6 Application on an ISM Running CDS-TV/CDS-IS for Cisco IOS XR Software Release 4.2.0

If the card is in CDS-IS mode, then it must be converted to CDS-TV before installing CGv6. For installation instructions, see the Cisco ASR 9000 Series Aggregation Services Router ISM Line Card Installation Guide in the following location :

http://www.cisco.com/en/US/partner/docs/routers/asr9000/hardware/ism_line_card/installation/guide/ismig.html


NoteWith 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.



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 IOS XR and Linux software, run the following commands as soon as the ISM LCP is in IOS XR RUN state. Delay may result in card reload due to API mismatch.

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:#admin
RP/0/RSP0/CPU0(admin)#debug sim reload-disable location<ism_node_location>
 

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.

a. Log into X86 CPU console and start the se_mbox_server process:

[root@localhost]# se_mbox_server -d

b. Log into ISM LC CPU and upload the images to X86:

#avsm_se_upload /disk0:/kernel.rpm
#avsm_se_upload /disk0:/ism_infra.tgz
 

c. 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 3

RP/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:#admin
RP/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 an ISM Running CDS-TV/CDS-IS for Cisco IOS XR Software Release 4.2.1

From Cisco IOS XR Software Release 4.2.1 onwards, the CGv6 application can be installed on an ISM line card directly without changing from CDS-IS to CDS-TV and then CGv6.


Step 1 Manually remove the non-CGv6 configuration, if any.

Step 2 Install the Cisco IOS XR Software Release 4.2.1 image(asr9k-mini-p/px.vm/pie) on the 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:#admin
RP/0/RSP0/CPU0(admin)#debug sim reload-disable location<ism_node_location>

Caution Any delay may result in card reload due to API mismatch.

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 images on RSP, run the commands in admin mode.

RP/0/RSP0/CPU0#admin
RP/0/RSP0/CPU0(admin)# download install-image <kit_location> from <rsp_where_kit_present> to <ism_node_location>
 

Step 7 Wait for around 12-14 minutes for the card to come at SEOS-READY. Proceed with ServiceInfra interface configuration.

Step 8 Revert the changes made in Step 3

RP/0/RP0/CPU0:#admin
RP/0/RSP0/CPU0:(admin)#no debug sim reload-disable location <ism_node_location>


 

Getting Started with the Carrier Grade IPv6

Perform these tasks to get started with the CGv6 configuration tasks.

Configuring the Service Role

Perform this task to configure the service role on the specified location to start the CGv6 service.


NoteRemoval of service role is strictly not recommended while the card is active. This puts the card into FAILED state, which is service impacting.


SUMMARY STEPS

1. configure

2. hw-module service cgn location node-id

3. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

hw-module service cgn location node-id

 

RP/0/RP0/CPU0:router(config)# hw-module service cgn location 0/1/CPU0

Configures a CGv6 service role (cgn) on location 0/1/CPU0.

Step 3

end

or

commit

 

RP/0/RP0/CPU0:router(config)# end

or

RP/0/RP0/CPU0:router(config)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Service Instance and Location for the Carrier Grade IPv6

Perform this task to configure the service instance and location for the CGv6 application.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-location preferred-active node-id

4. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-location preferred-active node-id

 

RP/0/RP0/CPU0:router(config-cgn)# service-location preferred-active 0/1/CPU0

Configures the active locations for the CGv6 application.

Note preferred-standby option is not supported.

Step 4

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn)# end

or

RP/0/RP0/CPU0:router(config-cgn)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Infrastructure Service Virtual Interface

Perform this task to configure the infrastructure service virtual interface (SVI) to forward the control traffic. The subnet mask length must be at least 30 (denoted as /30).


NoteDo not remove or modify service infra interface configuration when the card is in Active state. The configuration is service affecting and the line card must be reloaded for the changes to take effect.


SUMMARY STEPS

1. configure

2. interface ServiceInfra value

3. service-location node-id

4. ipv4 address address/mask

5. end
or
commit

6. reload

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

interface ServiceInfra value

 

RP/0/RP0/CPU0:router(config)# interface ServiceInfra 1

RP/0/RP0/CPU0:router(config-if)#

Configures the infrastructure service virtual interface (SVI) as 1 and enters CGv6 configuration mode.

Note Only one service infrastructure SVI can be configured for a CGv6 instance.

Step 3

service-location node-id

 

RP/0/RP0/CPU0:router(config-if)# service-location 0/1/CPU0

Configures the location of the CGv6 service for the infrastructure SVI.

Step 4

ipv4 address address/mask

 

RP/0/RP0/CPU0:router(config-if)# ipv4 address 1.1.1.1/30

Sets the primary IPv4 address for an interface.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-if)# end

or

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 6

reload

 

RP/0/RP0/CPU0:Router#hw-mod location 0/3/cpu0 reload

 

Once the configuration is complete, the card must be reloaded for changes to take effect.

WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y

Configuring the Application Service Virtual Interface

The following section lists guidelines for selecting serviceapp interfaces for NAT44:

  • Pair ServiceApp<n> with ServiceApp<n+1> , where <n> is an odd integer. This is to ensure that the ServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 or ServiceApp3 with ServiceApp4
  • Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an odd integer. However, maintaining a track of these associations can be error prone. For example, ServiceApp1 with ServiceApp6 , ServiceApp1 with ServiceApp10 , ServiceApp3 with 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 such ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Inside traffic for the ServiceApp pair is halved.
  • Do not pair ServiceApp<n> with ServiceApp<n+1> , where <n> is an even integer. When used, Outside-to-Inside traffic is dropped becasue traffic flows in the wrong dispatcher and core.
  • Do not pair ServiceApp<n> with ServiceApp<n+1> , where <n> is an integer. When used, Outside-to-Inside traffic is dropped becasue traffic flows in the wrong dispatcher and core.

One ServiceApp pair can be used as inside and the other as outside.

Perform the following tasks to configure the application service virtual interface (SVI) to forward data traffic.

SUMMARY STEPS

1. configure

2. interface ServiceApp value

3. service cgn instance-name service-type nat44

4. vrf vrf-name

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

interface ServiceApp value

 

RP/0/RP0/CPU0:router(config)# interface ServiceApp 1

RP/0/RP0/CPU0:router(config-if)#

Configures the application SVI as 1 and enters interface configuration mode.

Step 3

service cgn instance-name service-type nat44

 

RP/0/RP0/CPU0:router(config-if)# service cgn cgn1

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 4

vrf vrf-name

 

RP/0/RP0/CPU0:router(config-if)# vrf insidevrf1

Configures the VPN routing and forwarding (VRF) for the

Service Application interface

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-if)# end

or

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Service Type Keyword Definition

Perform this task to configure the service type key definition.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 instance-name

or

4. service-type ds-lite instance-name

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn nat44 instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 NAT44 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn)# end

or

RP/0/RP0/CPU0:router(config-cgn)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring an Inside and Outside Address Pool Map

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 different inside VRF.
  • Max Outside public pool per ISM/CGv6 instance is 64 K or 65536 addresses. That is, if a /16 address pool is mapped, then we cannot map any other pool to that particular ISM.
  • 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 30.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. map [ outside-vrf outside-vrf-name ] address-pool address/prefix

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures an inside VRF named insidevrf1 and enters CGv6 inside VRF configuration mode.

Step 5

map [ outside-vrf outside-vrf-name ] address-pool address/prefix

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# map outside-vrf outside vrf1 address-pool 10.10.0.0/16

or

RP/0/RP0/CPU0:router(config-cgn-invrf)# map

address-pool 100.1.0.0/16

 

Configures an inside VRF to an outside VRF and address pool mapping.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-invrf-afi)# end

or

RP/0/RP0/CPU0:router(config-cgn-invrf-afi)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Port Limit Per Subscriber

Perform this task to configure the port limit per subscriber for the system that includes TCP, UDP, and ICMP.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. portlimit value

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

portlimit value

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# portlimit 10

Limits the number of entries per address for each subscriber of the system

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn)# end

or

RP/0/RP0/CPU0:router(config-cgn)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout Value for the ICMP Protocol

Perform this task to configure the timeout value for the ICMP type for the CGv6 instance.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. protocol icmp

5. timeout seconds

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

protocol icmp

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# protocol icmp

RP/0/RP0/CPU0:router(config-cgn-proto)#

Configures the ICMP protocol session. The example shows how to configure the ICMP protocol for the CGv6 instance named cgn1.

Step 5

timeout seconds

 

RP/0/RP0/CPU0:router(config-cgn-proto)# timeout 908

Configures the timeout value as 908 for the ICMP session for the CGv6 instance named cgn1.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout Value for the TCP Session

Perform this task to configure the timeout value for either the active or initial sessions for TCP.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. protocol tcp

5. session { active | initial } timeout seconds

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

protocol tcp

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# protocol tcp

RP/0/RP0/CPU0:router(config-cgn-proto)#

Configures the TCP protocol session. The example shows how to configure the TCP protocol for the CGv6 instance named cgn1.

Step 5

session { active | initial } timeout seconds

 

RP/0/RP0/CPU0:router(config-cgn-proto)# session initial timeout 90

Configures the timeout value as 90 for the TCP session. The example shows how to configure the initial session timeout.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout Value for the UDP Session

Perform this task to configure the timeout value for either the active or initial sessions for UDP.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. protocol udp

5. session { active | initial } timeout seconds

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

protocol udp

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# protocol udp

RP/0/RP0/CPU0:router(config-cgn-proto)#

Configures the UDP protocol sessions. The example shows how to configure the TCP protocol for the CGv6 instance named cgn1.

Step 5

session { active | initial } timeout seconds

 

RP/0/RP0/CPU0:router(config-cgn-proto)# session active timeout 90

Configures the timeout value as 90 for the UDP session. The example shows how to configure the active session timeout.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the TCP Adjustment Value for the Maximum Segment Size

Perform this task to configure the adjustment value for the maximum segment size (MSS) for the VRF. You can configure the TCP MSS adjustment value on each VRF.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. protocol tcp

6. mss size

7. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-location preferred-active 0/1/CPU0

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

protocol tcp

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# protocol tcp

RP/0/RP0/CPU0:router(config-cgn-invrf-proto)#

Configures the TCP protocol session and enters CGv6 inside VRF AFI protocol configuration mode.

Step 6

mss size

 

RP/0/RP0/CPU0:router(config-cgn-invrf-afi-proto)# mss 1100

Configures the adjustment MSS value as 1100 for the inside VRF.

Step 7

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-invrf-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-invrf-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Refresh Direction for the Network Address Translation

Perform this task to configure the NAT mapping refresh direction as outbound for TCP and UDP traffic.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. refresh-direction Outbound

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

refresh-direction Outbound

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# protocol tcp

RP/0/RP0/CPU0:router(config-cgn-proto)#refresh-direction Outbound

 

Configures the NAT mapping refresh direction as outbound for the CGv6 instance named cgn1.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn)# end

or

RP/0/RP0/CPU0:router(config-cgn)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring Static Port Forwarding

Perform this task to configure static port forwarding for reserved or nonreserved port numbers.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. protocol tcp

6. static-forward inside

7. address address port number

8. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

protocol tcp

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# protocol tcp

RP/0/RP0/CPU0:router(config-cgn-invrf-proto)#

Configures the TCP protocol session and enters CGv6 inside VRF AFI protocol configuration mode.

Step 6

static-forward inside

 

RP/0/RP0/CPU0:router(config-cgn-invrf-proto)# static-forward inside

RP/0/RP0/CPU0:router(config-cgn-ivrf-sport-inside)#

Configures the CGv6 static port forwarding entries on reserved or nonreserved ports and enters CGv6 inside static port inside configuration mode.

Step 7

address address port number

 

RP/0/RP0/CPU0:router(config-cgn-ivrf-sport-inside)# address 1.2.3.4 port 90

Configures the CGv6 static port forwarding entries for the inside VRF.

Step 8

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ivrf-sport-inside)# end

or

RP/0/RP0/CPU0:router(config-cgn-ivrf-sport-inside)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Dynamic Port Ranges

Perform this task to configure dynamic port ranges for TCP, UDP, and ICMP ports. The default value range of 0 to 1023 is preserved and not used for dynamic translations. Therefore, if the value of dynamic port range start is not configured explicitly, the dynamic port range value starts at 1024.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. dynamic port range start value

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

dynamic port range start value

 

RP/0/RP0/CPU0:router(config-cgn-nat44)# dynamic port range start 1024

Configures the value of dynamic port range start for a CGv6 NAT 44 instance. The value can range from 1 to 65535.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ivrf-sport-inside)# end

or

RP/0/RP0/CPU0:router(config-cgn-ivrf-sport-inside)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Server Address and Port for Netflow Logging

Perform this task to configure the server address and port to log network address translation (NAT) table entries for Netflow logging.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. external-logging netflowv9

6. server

7. address address port number

8. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 inside VRF address family external logging configuration mode.

Step 6

server

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 inside VRF address family external logging server configuration mode.

Step 7

address address port number

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# address 2.3.4.5 port 45

Configures the IPv4 address and port number 45 to log Netflow entries for the NAT table.

Step 8

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Path Maximum Transmission Unit for Netflow Logging

Perform this task to configure the path maximum transmission unit (MTU) for the netflowv9-based external-logging facility for the inside VRF.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. external-logging netflowv9

6. server

7. path-mtu value

8. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 inside VRF address family external logging configuration mode.

Step 6

server

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 inside VRF address family external logging server configuration mode.

Step 7

path-mtu value

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# path-mtu 2900

Configures the path MTU with the value of 2900 for the netflowv9-based external-logging facility.

Step 8

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Refresh Rate for Netflow Logging

Perform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed or resent to the Netflow-v9 logging server.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. external-logging netflowv9

6. server

7. refresh-rate value

8. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 inside VRF address family external logging configuration mode.

Step 6

server

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflow-v9 based external-logging facility and enters CGv6 inside VRF address family external logging server configuration mode.

Step 7

refresh-rate value

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# refresh-rate 50

Configures the refresh rate value of 50 to log Netflow-based external logging information for an inside VRF.

Step 8

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout for Netflow Logging

Perform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to be sent to the Netflow-v9 logging server.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-name

5. external-logging netflowv9

6. server

7. timeout value

8. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-invrf)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 inside VRF address family external logging configuration mode.

Step 6

server

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 inside VRF address family external logging server configuration mode.

Step 7

timeout value

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# timeout 50

Configures the timeout value of 50 for Netflow logging of NAT table entries for an inside VRF.

Step 8

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring Bulk Port Allocation

Perform this task to configure bulk port allocation to reduce Netflow or Syslog data volume:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 nat1

4. inside-vrf vrf-instance

5. bulk-port-alloc size number of ports

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

bulk-port-alloc size number of ports

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-)# bulk-port-alloc size 64

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf)

Allocate ports in bulk to reduce Netflow/Syslog data volume.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf)# end

or

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring Syslog

Perform this task to configure syslog data for a NAT44 instance:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type nat44 instance-name

4. inside-vrf instance name

5. external-logging syslog

6. server

7. address server ip address

8. port server port number

9. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type nat44 nat1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type nat44 nat1

Configures the service type keyword definition for CGv6 NAT44 application.

Step 4

inside-vrf vrf-name

 

RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1

RP/0/RP0/CPU0:router(config-cgn-invrf)#

Configures the inside VRF for the CGv6 instance named cgn1 and enters CGv6 inside VRF configuration mode.

Step 5

external-logging syslog

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf)# external-logging syslog

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-extlog

Configures the syslog data for the CGv6 instance named cgn1 and enters CGv6 DS-Lite.

Step 6

server

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#

Configures the server used to log syslog data.

Step 7

address server IP address

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-extlog-server)# address 100.2.1.1

Configures the server IP address.

Step 8

port server port number

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-extlog-server)# address 100.2.1.1 port 256

Configures the server port number.

Step 9

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-nat44-invrf-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring a DS Lite Instance

Perform this task to configure an instance of the DS-Lite application:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance name

4. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring an Address Pool Map for a DS-Lite Instance

Perform this task to configure an address pool map for a DS-Lite instance:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance name

4. map address-pool address/prefix

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

map address-pool address/prefix

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# map address-pool 10.10.0.0/16

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# map address-pool 100.1.0.0/16

Configures an address pool mapping.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring Bulk Port Allocation for a DS Lite Instance

Perform this task to configure bulk port allocation for a DS Lite instance to reduce Netflow or Syslog data volume:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite ds-lite1

4. bulk-port-alloc size number of ports

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

bulk-port-alloc size number of ports

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# bulk-port-alloc size 64

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Allocate ports in bulk to reduce Netflow/Syslog data volume.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring Syslog for a DS Lite Instance

Perform this task to configure syslog data for a DS Lite instance:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. external-logging syslog

5. server

6. address server ip address

7. port server port number

8. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

external-logging syslog

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# external-logging syslog

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog

Configures the syslog data for the CGv6 instance named cgn1 and enters CGv6 DS-Lite.

Step 5

server

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#

Configures the server used to log syslog data.

Step 6

address server IP address

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# address 100.2.1.1

Configures the server IP address.

Step 7

port server port number

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# address 100.2.1.1 port 256

Configures the server port number.

Step 8

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring IPv6 Tunnel Endpoint Address for a DS-Lite Instance

Perform this task to configure the IPv6 tunnel endpoint address for a DS-Lite instance:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance name

4. aftr-tunnel-endpoint-address X:X::X IPv6 address

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

aftr-tunnel-endpoint-address X:X::X IPv6 address

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# aftr-tunnel-endpoint-address 10:2::10

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures an IPv6 tunnel endpoint address.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Path Maximum Transmission Unit for a DS-Lite Instance

Perform this task to configure the path maximum transmission unit (MTU) for a DS-Lite instance:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance name

4. path-mtu value

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

path-mtu value

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# path-mtu 2000

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the path MTU with the value of 2000 for the ds-lite instance.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Port Limit Per Subscriber for a DS-Lite Instance

Perform this task to configure the port limit per subscriber for the system that includes TCP, UDP, and ICMP.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. port-limit value

5. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

port-limit value

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# port-limit 65

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the port value that restricts the number of translations for the ds-lite instance.

Step 5

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout Value for the ICMP Protocol

Perform this task to configure the timeout value for the ICMP type for the DS-Lite instance.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. protocol icmp

5. timeout seconds

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

protocol icmp

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# protocol icmp

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)

Configures the ICMP protocol session.

Step 5

timeout seconds

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)

timeout 90

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)

Configures the timeout value for the ICMP session.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout Value for the TCP Session

Perform this task to configure the timeout value for either the active or initial sessions for TCP.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. protocol tcp

5. session { active | init } timeout seconds

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

protocol tcp

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# protocol tcp

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)

Configures the TCP protocol session.

Step 5

session { active | initial } timeout seconds

 

RP/0/RP0/CPU0:router(config-cgn-proto)# session initial timeout 90

Configures the timeout value for the TCP session. The example shows how to configure the initial session timeout.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout Value for the UDP Session

Perform this task to configure the timeout value for either the active or initial sessions for UDP.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. protocol udp

5. session { active | init } timeout seconds

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

protocol udp

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# protocol icmp

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)

Configures the UDP protocol session.

Step 5

session { active | initial } timeout seconds

 

RP/0/RP0/CPU0:router(config-cgn-proto)# session initial timeout 90

Configures the timeout value for the UDP session. The example shows how to configure the initial session timeout.

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the TCP Adjustment Value for the Maximum Segment Size for a DS-Lite Instance

Perform this task to configure the adjustment value for the maximum segment size (MSS) for the DS-Lite instance.

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. protocol tcp

5. mss size

6. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite ds-lite1

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

protocol tcp

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# protocol tcp

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)

Configures the TCP protocol session.

Step 5

mss size

 

RP/0/RP0/CPU0:router(config-cgn-proto)# mss 90

Configures maximum segment size value for TCP sessions for a ds-lite instance

Step 6

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-proto)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Server Address and Port for Netflow Logging

Perform this task to configure the server address and port to log DS-Lite table entries for Netflow logging:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. external-logging netflowv9

5. server

6. address address port number

7. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 external logging configuration mode.

Step 5

server

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 external logging server configuration mode.

Step 6

address address port number

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# address 10.3.20.130 port 45

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)

Configures the IPv4 address and port number to log Netflow entries for the DS-Lite instance.

Step 7

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Path Maximum Transmission Unit for Netflow Logging

Perform this task to configure the path maximum transmission unit (MTU) for the netflowv9-based external-logging facility for a DS-Lite instance:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. external-logging netflowv9

5. server

6. path-mtu value

7. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 external logging configuration mode.

Step 5

server

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 external logging server configuration mode.

Step 6

path-mtu value

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# path mtu 200

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)

Configures the path MTU with the value of 200 for the netflowv9-based external-logging facility.

Step 7

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Refresh Rate for Netflow Logging

Perform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed or resent to the Netflow-v9 logging server:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. external-logging netflowv9

5. server

6. refresh-rate value

7. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 external logging configuration mode.

Step 5

server

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 external logging server configuration mode.

Step 6

refresh-rate value

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# refresh-rate 200

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)

Configures the refresh rate value of 200 to log Netflow-based external logging information.

Step 7

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Timeout for Netflow Logging

Perform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to be sent to the Netflow-v9 logging server:

SUMMARY STEPS

1. configure

2. service cgn instance-name

3. service-type ds-lite instance-name

4. external-logging netflowv9

5. server

6. timeout value

7. end
or
commit

DETAILED STEPS

 

Command or Action
Purpose

Step 1

configure

 

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

service cgn instance-name

 

RP/0/RP0/CPU0:router(config)# service cgn cgn1

RP/0/RP0/CPU0:router(config-cgn)#

Configures the instance named cgn1 for the CGv6 application and enters CGv6 configuration mode.

Step 3

service-type ds-lite instance-name

 

RP/0/RP0/CPU0:router(config-cgn)# service-type ds-lite ds-lite1

RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Configures the service type keyword definition for CGv6 DS-Lite application.

Step 4

external-logging netflowv9

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite)# external-logging netflowv9

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)#

Configures the external-logging facility for the CGv6 instance named cgn1 and enters CGv6 external logging configuration mode.

Step 5

server

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog)# server

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#

Configures the logging server information for the IPv4 address and port for the server that is used for the netflowv9-based external-logging facility and enters CGv6 external logging server configuration mode.

Step 6

timeout value

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# timeout 200

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)

Configures the timeout value of 200 for Netflow logging of the DS-Lite instance.

Step 7

end

or

commit

 

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# end

or

RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)?
[cancel]:
 

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuration Examples for Implementing the CGv6

This section provides the following configuration examples for CGN:

Configuring a Different Inside VRF Map to a Different Outside VRF for NAT44: Example

This example shows how to configure a different inside VRF map to a different outside VRF and different outside address pools:

service cgn cgn1
inside-vrf insidevrf1
map outside-vrf outsidevrf1 address-pool 100.1.1.0/24
!
!
inside-vrf insidevrf2
map outside-vrf outsidevrf2 address-pool 100.1.2.0/24
!
service-location preferred-active 0/2/cpu0
!
interface ServiceApp 1
vrf insidevrf1
ipv4 address 210.1.1.1 255.255.255.0
service cgn cgn1
!
router static
vrf insidevrf1
0.0.0.0/0 serviceapp 1
!
!
interface ServiceApp 2
vrf outsidevrf1
ipv4 address 211.1.1.1 255.255.255.0
service cgn cgn1
service-type nat44 nat1
!
router static
vrf outsidevrf1
100.1.1.0/24 serviceapp 2
!
!
interface ServiceApp 3
vrf insidevrf2
ipv4 address 1.1.1.1 255.255.255.0
service cgn cgn1
service-type nat44 nat1
!
router static
vrf insidevrf2
0.0.0.0/0 serviceapp 3
!
!
interface ServiceApp 4
vrf outsidevrf2
ipv4 address 2.2.2.1 255.255.255.0
service cgn cgn1
service-type nat44 nat1
!
router static
vrf outsidevrf2
100.1.2.0/24 serviceapp 4
 

NAT44 Configuration: Example

This example shows a NAT44 sample configuration:

interface Loopback40
description IPv4 Host for NAT44
ipv4 address 40.22.22.22 255.255.0.0
!
interface Loopback41
description IPv4 Host for NAT44
ipv4 address 41.22.22.22 255.255.0.0
!
interface GigabitEthernet0/3/0/0.1
description Connected to P2_ASR9000-8 GE 0/6/5/0.1
ipv4 address 10.222.5.22 255.255.255.0
encapsulation dot1q 1
!
router static
address-family ipv4 unicast
180.1.0.0/16 10.222.5.2
181.1.0.0/16 10.222.5.2
!
!

Hardware Configuration for ISM

!
vrf InsideCustomer1
address-family ipv4 unicast
!
!
vrf OutsideCustomer1
address-family ipv4 unicast
!
!
hw-module service cgn location 0/3/CPU0
!
!
interface GigabitEthernet0/6/5/0.1
vrf InsideCustomer1
ipv4 address 10.222.5.2 255.255.255.0
encapsulation dot1q 1
!
interface GigabitEthernet0/6/5/1.1
vrf OutsideCustomer1
ipv4 address 10.12.13.2 255.255.255.0
encapsulation dot1q 1
!
interface ServiceApp1
vrf InsideCustomer1
ipv4 address 1.1.1.1 255.255.255.252
service cgn cgn1 service-type nat44
!
interface ServiceApp2
vrf OutsideCustomer1
ipv4 address 2.1.1.1 255.255.255.252
service cgn cgn1 service-type nat44
!
interface ServiceInfra1
ipv4 address 75.75.75.75 255.255.255.0
service-location 0/3/CPU0
!
!
router static
!
vrf InsideCustomer1
address-family ipv4 unicast
0.0.0.0/0 ServiceApp1
40.22.0.0/16 10.222.5.22
41.22.0.0/16 10.222.5.22
181.1.0.0/16 vrf OutsideCustomer1 GigabitEthernet0/6/5/1.1 10.12.13.1
!
!
vrf OutsideCustomer1
address-family ipv4 unicast
40.22.0.0/16 vrf InsideCustomer1 GigabitEthernet0/6/5/0.1 10.222.5.22
41.22.0.0/16 vrf InsideCustomer1 GigabitEthernet0/6/5/0.1 10.222.5.22
100.0.0.0/24 ServiceApp2
180.1.0.0/16 10.12.13.1
181.1.0.0/16 10.12.13.1
!
!
!

ISM Configuration

service cgn cgn1
service-location preferred-active 0/3/CPU0
service-type nat44 nat44
portlimit 200
alg ActiveFTP
inside-vrf InsideCustomer1
map outside-vrf OutsideCustomer1 address-pool 100.0.0.0/24
protocol tcp
static-forward inside
address 41.22.22.22 port 80
!
!
protocol icmp
static-forward inside
address 41.22.22.22 port 80
!
!
external-logging netflow version 9
server
address 172.29.52.68 port 2055
refresh-rate 600
timeout 100 !
!
!
!
!
IPv4: 180.1.1.1/16
!
interface Loopback180
description IPv4 Host for NAT44
ipv4 address 180.1.1.1 255.255.0.0
!
interface Loopback181
description IPv4 Host for NAT44
ipv4 address 181.1.1.1 255.255.0.0
!
interface GigabitEthernet0/6/5/1.1
ipv4 address 10.12.13.1 255.255.255.0
encapsulation dot1q 1
!
router static
address-family ipv4 unicast
40.22.0.0/16 10.12.13.2
41.22.0.0/16 10.12.13.2
100.0.0.0/24 10.12.13.2 !
!

Bulk Port Allocation and Syslog Configuration: Example

service cgn cgn2
service-type nat44 natA
inside-vrf broadband
map address-pool 100.1.2.0/24
external-logging syslog
server
address 20.1.1.2 port 514
!
!
bulk-port-alloc size 64
!
!

DS Lite Configuration: Example

IPv6 ServiceApp and Static Route Configuration

conf
int serviceApp61
service cgn cgn1 service-type ds-lite
ipv6 address 2001:202::/32
commit
exit
 
router static
address-family ipv6 unicast
3001:db8:e0e:e01::/128 ServiceApp61 2001:202::2
commit
exit
end

IPv4 ServiceApp and Static Route Configuration

conf
int serviceApp41
service cgn cgn1 service-type ds-lite
ipv4 add 41.41.41.1/24
commit
exit
 
router static
address-family ipv4 unicast
52.52.52.0/24 ServiceApp41 41.1.1.2
commit
exit
end

DS Lite Configuration

service cgn cgn1
service-location preferred-active 0/2/CPU0 preferred-standby 0/4/CPU0
service-type ds-lite dsl1
portlimit 200
bulk-port-alloc size 128
map address-pool 52.52.52.0/24
aftr-tunnel-endpoint-address 3001:DB8:E0E:E01::
address-family ipv4
interface ServiceApp41
address-family ipv6
interface ServiceApp61
protocol tcp
session init timeout 300
session active timeout 400
mss 1200
external-logging netflow9
server
address 90.1.1.1 port 99
external-logging syslog
server
address 90.1.1.1 port 514

Additional References

For additional information related to Implementing the Carrier Grade IPv6, see the following references:

Related Documents

 

Related Topic
Document Title

Cisco IOS XR Carrier Grade IPv6 commands

Cisco IOS XR Carrier Grade IPv6 (CGv6) Command Reference for the Cisco CRS-1 Router.

Cisco CRS-1 router getting started material

Cisco IOS XR Getting Started Guide

Information about user groups and task IDs

Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide

Standards

 

Standards 1
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

1.Not all supported standards are listed.

MIBs

 

MIBs
MIBs Link

To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs

 

RFCs 2
Title

RFC 4787

Network Address Translation (NAT) Behavioral Requirements for Unicast UDP

RFC 5382

NAT Behavioral Requirements for TCP

RFC 5508

NAT Behavioral Requirements for ICMP

2.Not all supported RFCs are listed.

Technical Assistance

 

Description
Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport