 Feedback
|
Table Of Contents
Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.3
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.3
Determining Your Software Version
New Features in Cisco IOS XR Software Release 3.9.3
New Software Features Supported on all Platforms
Cisco CRS-1 Series Router Specific Software Features
IPv4/IPv6 Stateless Translator (XLAT)
NAT64 Stateless Sample Configuration
address (CGN NetflowV9 logging)
hw-module service cgn location (CGN)
show cgn nat44 inside-translation
show cgn nat44 outside-translation
show cgn nat44 pool-utilization
show cgn tunnel v6rd statistics
New Hardware Features for the Cisco CRS-1 Series Router
New Features in Cisco IOS XR Software Release 3.9.2
New Software Features Supported on all Platforms
Cisco CRS-1 Router Specific Software Features
Heartbeat Loss Debug Enhancement
New Hardware Features for the Cisco CRS-1 Router
ACL-Chaining (Multi-ACL) Commands
hw-module qos input police granularity
show hw-module qos input police granularity
hw-module qos output police granularity
show hw-module qos output police granularity
hw-module qos output shape granularity
show hw-module qos output shape granularity
8 port 10GE XFP Support Commands
Minimum Flash Disk Requirements When Upgrading to Release 3.9.3
Resolved Release 3.9.3 Cisco IOS XR PSIRT-Related Caveats
Open Release 3.9.3 Cisco IOS XR Caveats
Open Release 3.9.3 Caveats Specific to the Cisco CRS-1 Router
Upgrading Cisco IOS XR Software
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.3
April 15, 2013
Cisco IOS XR Software Release 3.9.3
Text Part Number OL-24252-01
These release notes describe the features provided in the Cisco IOS XR Software Release 3.9.3 for the Cisco CRS-1 Router and are updated as needed.
Note
For information on the Cisco CRS-1 Router running Cisco IOS XR Software Release 3.9.3, see the "Important Notes" section.
You can find the most current Cisco IOS XR software documentation at
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
These electronic documents may contain updates and modifications. For more information on obtaining Cisco documentation, see the "Obtaining Documentation and Submitting a Service Request".
For a list of software caveats that apply to Cisco IOS XR Software Release 3.9.3, see the "Caveats" section. The caveats are updated for every release and are described at www.cisco.com.
We recommend that you view the field notices for this release located at the following URL to see if your software or hardware platforms are affected:
http://www.cisco.com/public/support/tac/fn_index.html
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.3
Cisco IOS XR Software Release 3.9.3 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB or 4 GB before upgrading to Cisco IOS XR Software Release 3.9.3. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.3" section.
Contents
These release notes contain the following sections:
•
•
•
•
•
Introduction
Cisco IOS XR software is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.
Cisco IOS XR software running on the Cisco CRS-1 Router provides the following features and benefits:
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
For more information about new features provided on the Cisco CRS-1 Router for Cisco IOS XR Software Release 3.9.3, see the "New Features in Cisco IOS XR Software Release 3.9.3" section in this document.
System Requirements
This section describes the system requirements for Cisco IOS XR Software Release 3.9.3 supported on the Cisco CRS-1 Router. The system requirements include the following information:
To determine the software versions or levels of your current system, see the "Determining Your Software Version" section.
Feature Set Table
Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.9.3 features.
Table 1 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 3.9.3 supported on the Cisco CRS-1 Router.
Table 1 Cisco CRS-1 Supported Feature Sets
(Cisco IOS XR Software Release 3.9.3 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.9.3
Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.vm-3.9.3
Contains the required core packages including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.9.3
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.9.3
MPLS-TE,4 LDP,5 MPLS Forwarding, MPLS OAM,6 LMP,7 OUNI,8 RSVP,9 and Layer-2 VPN and Layer-3 VPN.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.9.3
Multicast Routing Protocols (PIM, MSDP,10 IGMP,11 Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB,12 MURIB13 , MFWD14 ), and BIDIR-PIM.15
Cisco IOS XR Security Package
hfr-k9sec-p.pie-3.9.3
Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI19 (Software based IPSec support—maximum of 500 tunnels)
Cisco IOS XR FPD Package
hfr-fpd.pie-3.9.3
Firmware for Fixed PLIM20 and SPA21 modules as well as ROMMON22 images for Cisco CRS-1 chassis.
Cisco IOS XR Diagnostic Package
hfr-diags.pie-3.9.3
Diagnostic utilities for Cisco IOS XR routers.
Cisco IOS XR Documentation Package
hfr-doc.pie-3.9.3
.man pages for Cisco IOS XR software on the Cisco CRS-1 chassis.
Cisco IOS XR Carrier Grade NAT Package
hfr-cgn-p.pie-3.9.3
Support for Carrier Grade NAT on Cisco CRS-1 routers.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 Extensible Markup Language
4 MPLS Traffic Engineering
5 Label Distribution Protocol
6 Operations, Administration, and Maintenance
7 Link Manager Protocol
8 Optical User Network Interface
9 Resource Reservation Protocol
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Multicast Routing Information Base
13 Multicast-Unicast RIB
14 Multicast forwarding
15 Bidirectional Protocol Independent Multicast
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Public-key infrastructure
20 Physical layer interface module
21 Shared port adapters
22 ROM monitor
Table 2 lists the Cisco CRS-1 Router TAR files.
Memory Requirements
Caution
The minimum memory requirements for a Cisco CRS-1 running Cisco IOS XR Software Release 3.9.3 consist of the following:
•
•
•
Note
Hardware Supported
All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 3 lists the supported hardware components on the Cisco CRS-1 and the minimum required software versions. For more information, see the "Other Firmware Support" section.
Software Compatibility
Cisco IOS XR Software Release 3.9.3 is compatible with the following Cisco CRS-1 systems:
•
•
•
•
Other Firmware Support
The Cisco CRS-1 supports the following firmware code:
•
http://www.cisco.com/en/US/products/ps5763/products_installation_and_configuration_guides_list.html•
•
RP/0/RP0/CPU0:FQ-PE1(admin)#show fpd packageMon Sep 27 08:32:32.106 PDT=============================== ================================================Field Programmable Device Package================================================SW Min Req Min ReqCard Type FPD Description Type Subtype Version SW Ver HW Vers==================== ========================== ==== ======= =========== ======== =======1OC768-ITU/C OPTICS FIRMWARE 110B10 lc fpga2 110.10 0.0 0.0------------------------------------------------------------------------------------------1OC768-DWDM-L OPTICS FIRMWARE 110B10 lc fpga2 110.10 0.0 0.0------------------------------------------------------------------------------------------1OC768-DPSK/C OPTICS FIRMWARE 110B14 lc fpga2 110.14 0.0 0.0------------------------------------------------------------------------------------------1OC768-DPSK/C-O OPTICS FIRMWARE 110B14 lc fpga2 110.14 0.0 0.0------------------------------------------------------------------------------------------1OC768-DPSK/C-E OPTICS FIRMWARE 110B14 lc fpga2 110.14 0.0 0.0------------------------------------------------------------------------------------------CRS-CGSE-PLIM FPGA mCPU0 0.559 lc fpga2 0.559 0.0 0.0FPGA sCPU0 0.559 lc fpga3 0.559 0.0 0.0FPGA mCPU1 0.559 lc fpga4 0.559 0.0 0.0FPGA sCPU1 0.559 lc fpga5 0.559 0.0 0.0FPGA PLIM_SVC 0.41014 lc fpga1 0.41014 0.0 0.0------------------------------------------------------------------------------------------CRS1-SIP-800 JACKET FPGA swv6.0 lc fpga1 6.00 5.0 0.0FPGA swv6.0 hwv80 lc fpga1 6.00 5.0 0.80------------------------------------------------------------------------------------------8-10GBE FPGA swvA.0 lc fpga1 10.00 0.0 0.0------------------------------------------------------------------------------------------OC48-POS-16-ED FPGA PLIM_OC48 9.0 lc fpga1 9.00 0.0 0.0------------------------------------------------------------------------------------------4-10GBE FPGA sw_4p_v15.0 lc fpga1 15.00 0.0 0.0------------------------------------------------------------------------------------------8-10GBE FPGA sw_8p_v15.0 lc fpga1 15.00 0.0 0.0------------------------------------------------------------------------------------------4-10GE SQUIRREL FPGA 10.0 lc fpga1 10.00 0.0 0.0------------------------------------------------------------------------------------------42-1GE FPGA swv6.0 lc fpga1 6.00 0.0 0.0FPGA swv6.0 hwv0.80 lc fpga1 6.00 0.0 0.80------------------------------------------------------------------------------------------20-1GE-FLEX FPGA swv6.0 lc fpga1 6.00 0.0 0.0FPGA swv6.0 hwv0.80 lc fpga1 6.00 0.0 0.80------------------------------------------------------------------------------------------2-10GE-WL-FLEX FPGA swv6.0 lc fpga1 6.00 0.0 0.0FPGA swv6.0 hwv0.80 lc fpga1 6.00 0.0 0.80------------------------------------------------------------------------------------------Route Processor ROMMONA swv1.54 asmp lc rommonA 1.54 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------SC ROMMONA swv1.54 asmp lc rommonA 1.54 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------RP ROMMONA swv1.54 asmp lc rommonA 1.54 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------Shelf Controller GE ROMMONA swv1.54 asmp lc rommonA 1.54 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------RP ROMMONA swv1.54 asmp lc rommonA 1.54 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------Shelf Controller GE2 ROMMONA swv1.54 asmp lc rommonA 1.54 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------DRP ROMMONA swv1.54 asmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------DRP_B ROMMONA swv1.54 asmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------S1S2S3 ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------S1S3 ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------S2 ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------Fabric HS123 ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------Fabric HS123 Star ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------Fabric HS13 Star ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------Fabric QQS123 ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------LED ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------40G-MSC ROMMONA swv1.54 asmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------MSC_B ROMMONA swv1.54 asmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.52 0.0 0.0ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------FP40 ROMMONA swv1.54 asmp lc rommonA 1.53 0.0 0.0ROMMONA swv1.54 dsmp lc rommonA 1.53 0.0 0.0ROMMONA swv1.54 sp lc rommonA 1.53 0.0 0.0ROMMONB swv1.54 asmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 dsmp lc rommon 1.54 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------PSAL ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------PSAL ROMMONA swv1.54 sp lc rommonA 1.54 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------FAN ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------FC Fan Controller ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------LED ROMMONA swv1.54 sp lc rommonA 1.52 0.0 0.0ROMMONB swv1.54 sp lc rommon 1.54 0.0 0.0------------------------------------------------------------------------------------------SPA-4XT3/E3 SPA E3 Subrate FPGA spa fpga2 1.04 0.0 0.0SPA T3 Subrate FPGA spa fpga3 1.04 0.0 0.0SPA I/O FPGA spa fpga1 1.00 0.0 0.0SPA ROMMON spa rommon 2.12 0.0 0.0------------------------------------------------------------------------------------------SPA-2XT3/E3 SPA E3 Subrate FPGA spa fpga2 1.04 0.0 0.0SPA T3 Subrate FPGA spa fpga3 1.04 0.0 0.0SPA I/O FPGA spa fpga1 1.00 0.0 0.0SPA ROMMON spa rommon 2.12 0.0 0.0------------------------------------------------------------------------------------------SPA-OC192POS SPA FPGA swv1.3 spa fpga1 1.03 0.0 0.0------------------------------------------------------------------------------------------SPA-8XOC12-POS SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.5------------------------------------------------------------------------------------------SPA-4XOC3-POS SPA FPGA swv3.4 spa fpga1 3.04 0.0 0.0------------------------------------------------------------------------------------------SPA-OC192POS-XFP SPA FPGA swv1.2 spa fpga1 1.02 0.0 0.0------------------------------------------------------------------------------------------SPA-8X1GE SPA FPGA swv1.8 spa fpga1 1.08 0.0 0.0------------------------------------------------------------------------------------------SPA-2XOC48POS/RPR SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.0------------------------------------------------------------------------------------------SPA-4XOC48POS/RPR SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.0------------------------------------------------------------------------------------------SPA-10X1GE-V2 SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-8X1GE-V2 SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-5X1GE-V2 SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-1X10GE-L-V2 SPA FPGA swv1.11 spa fpga1 1.11 0.0 0.0------------------------------------------------------------------------------------------SPA-1X10GE-WL-V2 SPA FPGA swv1.11 spa fpga1 1.11 0.0 0.0------------------------------------------------------------------------------------------SPA-1XOC3-ATM-V2 SPA FPGA swv1.2 spa fpga1 1.03 0.0 0.0------------------------------------------------------------------------------------------SPA-2XOC3-ATM-V2 SPA FPGA swv1.2 spa fpga1 1.03 0.0 0.0------------------------------------------------------------------------------------------SPA-3XOC3-ATM-V2 SPA FPGA swv1.2 spa fpga1 1.03 0.0 0.0------------------------------------------------------------------------------------------SPA-1XOC12-ATM-V2 SPA FPGA swv1.2 spa fpga1 1.03 0.0 0.0------------------------------------------------------------------------------------------Determining Your Software Version
To determine the version of Cisco IOS XR software running on your router, log into the router and enter the show version command:
Step 1
Step 2
RP/0/RP0/CPU0:FQ-PE1#show versionSun Sep 26 09:02:52.591 PDTCisco IOS XR Software, Version 3.9.2[00]Copyright (c) 2010 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.54(20091016:214209) [CRS-1 ROMMON],FQ-PE1 uptime is 1 day, 15 hours, 23 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.9.2/mbihfr-rp.vm"cisco CRS-16/S (7455) processor with 4194304K bytes of memory.7455 processor at 800Mhz, Revision 3.42 Management Ethernet75 GigabitEthernet36 SONET/SDH35 Packet over SONET/SDH1 Asynchronous Transfer Mode8 TenGigE4 T34 Serial network interface(s)1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.2053440k bytes of disk0: (Sector size 512 bytes).Boot device on node 0/5/CPU0 is mem:Package active on node 0/5/CPU0:hfr-fpd, V 3.9.2[00], Cisco Systems, at disk0:hfr-fpd-3.9.2Built on Fri Sep 24 04:12:43 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-diags, V 3.9.2[00], Cisco Systems, at disk0:hfr-diags-3.9.2Built on Fri Sep 24 04:12:27 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-mcast, V 3.9.2[00], Cisco Systems, at disk0:hfr-mcast-3.9.2Built on Fri Sep 24 06:49:25 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-mpls, V 3.9.2[00], Cisco Systems, at disk0:hfr-mpls-3.9.2Built on Fri Sep 24 06:49:10 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-lc, V 3.9.2[00], Cisco Systems, at disk0:hfr-lc-3.9.2Built on Fri Sep 24 03:58:19 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-fwdg, V 3.9.2[00], Cisco Systems, at disk0:hfr-fwdg-3.9.2Built on Fri Sep 24 03:57:06 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-admin, V 3.9.2[00], Cisco Systems, at disk0:hfr-admin-3.9.2Built on Fri Sep 24 03:56:20 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-base, V 3.9.2[00], Cisco Systems, at disk0:hfr-base-3.9.2Built on Fri Sep 24 03:59:33 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0hfr-os-mbi, V 3.9.2[00], Cisco Systems, at disk0:hfr-os-mbi-3.9.2Built on Fri Sep 24 03:51:00 PDT 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
New Features in Cisco IOS XR Software Release 3.9.3
New Software Features Supported on all Platforms
There are no new platform software features in Cisco IOS XR Software Release 3.9.3.
Cisco CRS-1 Series Router Specific Software Features
Figure 1 Upgrade Chart
3.6.3
3.9.3
3.8.2
3.9.3
3.8.4
3.9.3
3.9.0
3.9.3
3.9.1
3.9.31
3.9.2
3.9.32
1 When upgrading from release 3.9.1 to 3.9.3 the cgn configuration will be lost and will have to be reconfigured with service-type changes
2 When upgrading from release 3.9.2 to 3.9.3 the cgn configuration will be lost and will have to be reconfigured with service-type changes
Note
IPv4/IPv6 Stateless Translator (XLAT)
IPv4/IPv6 Stateless Translator (XLAT), running on the CRS-1 Carrier Grade Services Engine (CGSE), enables an IPv4-only endpoint situated in an IPv4-only network to communicate with an IPv6-only end-point situated in an IPv6-only network. This like-to-unlike address family connectivity paradigm provides backwards compatibility between IPv6 and IPv4.
A Stateless XLAT (SL-XLAT) does not create or maintain any per-session or per-flow data structures. Rather it is an algorithmic operation performed on the IP packet headers that results in the translation of an IPv4 packet to an IPv6 packet and vice-versa.
An SL-XLAT:
•
•
•
Hardware
The CRS-1 SL-XLAT solution is composed of two primary hardware components.
•
•
The CGSE PLIM itself is a multi-CPU processor bank composed of four Cavium Octeon CPU complexes with each supporting 16 x cores for a total of 64 x cores. Each Octeon complex has its own DRAM (2GB-8Gb) memory complex. The bandwidth available between the CGSE and the CRS-1 forwarding engine is 20Gb. The CGSE PLIM does not support any external I/O but rather interfaces to the CRS-1 routing space by means of a Services Virtual Interface (SVI). The SVI is a virtual interface connecting the SL-XLAT application to one or more VPN Routing and Forwarding (VRFs) spaces running on the CRS-1 router.
The CGSE does not run IOS-XR but instead a version of MonteVista Linux while the CRS-1 MSC forwarding engine it is bound to runs IOS-XR. The CGSE PLIM and SL-XLAT application will be managed and configured under IOS-XR. Packets arriving at a CRS-1 router that require SL-XLAT processing are diverted internally (across the switch fabric) to a SVI. Packets that do not require SL-XLAT processing are forwarded to the ingress linecard-switch fabric-egress linecard business as usual.
Software
The CRS-1 SL-XLAT is based on several important software components:
•
•
•
The post-DNS64 request/response packet flow:
1.
Note
2.
3.
4.
5.
Cisco Carrier-Grade Service Engine (CGSE)
Solution Components:
•
–
–
–
•
–
–
–
–
•
–
CGN (NAT44, 6rd, Stateless NAT64..) function resides on CGSE PLIM
Quad Octeon multiprocessor architecture, 64 CPU cores
Standard interface to MSC, 10 Gbps full-duplex nominal
–
IOS-XR on MSC, Linux on Octeon CPUs
Integrated configuration & management via IOS XR
•
–
ServiceInfra SVI
ServiceApp SVI
–
–
Configuring the CGSE
Prerequisites:
•
–
–
•
–
–
–
Bring Up the CGSE Board
•
RP/0/RP0/CPU0:#adminRP/0/RP0/CPU0:(admin)#show hw-module fpd location 0/2/cpu0===================================== ==========================================Existing Field Programmable Devices==========================================HW Current SW Upg/Location Card Type Version Type Subtype Inst Version Dng?============ ======================== ======= ==== ======= ==== =========== ====--------------------------------------------------------------------------------0/1/CPU0 CRS-CGSE-PLIM 0.88 lc fpga2 0 0.559 Nolc fpga3 0 0.559 Nolc fpga4 0 0.559 Nolc fpga5 0 0.559 Nolc fpga1 0 0.41014 Nolc rommonA 0 1.52 Nolc rommon 0 1.52 Yes
Note
Note
•
•
LC/0/3/CPU0:Sep 28 23:36:36.815 : plim_services[241]: plim_services_init[2063] Uknown role Retrying.., Role = -7205769247857836031LC/0/3/CPU0:Sep 28 23:37:59.341 : plim_services[241]: service_download_thread[3873] App img download max-retries exhausted, 'plim_services' detected the 'warning' condition 'Operation not okay'LC/0/3/CPU0:Sep 28 23:37:59.342 : plim_services[241]: plim_services_tile_failed[752] TILE0 failedRP/0/RP1/CPU0:Sep 28 23:38:18.494 : invmgr[240]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/0, state: FAILED•
RP/0/RP0/CPU0:router#show platformSun Dec 20 07:15:38.893 UTCNode Type PLIM State Config State-----------------------------------------------------------------------------0/0/CPU0 MSC Services Plim IOS XR RUN PWR,NSHUT,MON0/0/0 MSC(SPA) CGSE-TILE OK PWR,NSHUT,MON0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 8X1GE OK PWR,NSHUT,MON•
router(config)interface ServiceInfra1ipv4 address 3.1.1.2 255.255.255.252service-location 0/0/CPU0logging events link-statuscommitrouter(config)hw-module service cgn location 0/0/CPU0commit
Note
•
You need to reload the card. It takes ~15min
router#hw-module location 0/0/CPU0 reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)] yXLAT Configuration
•
•
•
•
•
•
•
•
XLAT ServiceApp Configuration
1.
–
–
–
conf tint ServiceApp4service cgn cgn1 service-type nat64 statelessipv4 add 2.0.0.1/24commitexitrouter staticaddress-family ipv4 unicast136.136.136.0/24 ServiceApp4 2.0.0.2commitexitend2.
–
–
–
conf tint serviceApp6service cgn cgn1service-type nat64 statelessipv6 address 2001:db8:fe00::1/40commitexitrouter staticaddress-family ipv6 unicast2001:db8:ff00::/40 ServiceApp6 2001:db8:fe00::2commitexitendXLAT Instance Configuration
•
–
•
–
•
–
•
–
•
–
–
•
–
–
TTL based - Chose address based on hop count of the pkt
Hash based - Hash IPv6 Source Address and use it for selection
Random - Randomly select an IPv4 address
•
–
–
•
–
–
•
–
–
–
conf tservice cgn cgn1service-type nat64 stateless xlat1ipv6-prefix 2001:db8:ff00::/40ubit-reservedaddress-family ipv4interface ServiceApp4tcp mss 1200tos 64address-family ipv6interface ServiceApp6tcp mss 1200traffic-class 32df-overridetraceroute translationaddress-pool 202.1.1.0/24algorithm HashShow Commands
•
show interface g0/2/0/5 accountingGigabitEthernet0/2/0/5Protocol Pkts In Chars In Pkts Out Chars OutIPV4_UNICAST 2072532 196637302 1777587 1388008448ARP 2 120 4 168show interface g0/2/0/6 accountingGigabitEthernet0/2/0/6Protocol Pkts In Chars In Pkts Out Chars OutIPV6_UNICAST 1777665 1423566488 2072607 254672848IPV6_MULTICAST 3 254 0 0ARP 0 0 2 84IPV6_ND 80 6464 125 10040•
show int ServiceApp4 accServiceApp4Protocol Pkts In Chars In Pkts Out Chars OutIPV4_UNICAST 1782667 1377627406 2079198 201248986show int ServiceApp6 accServiceApp6Protocol Pkts In Chars In Pkts Out Chars OutIPV6_UNICAST 2079198 242832922 1782667 1427542082•
show cgn nat64 stateless xlat1 statistics summaryStateless Nat64 IPv6 to IPv4 counters:_TCP Input Count: 64 TCP NonTranslatable Drop Count: 128 TCP Invalid NextHdr Drop Count: 192 TCP NoDb Drop Count: 256 TCP Output Count: 320......Stateless Nat64 IPv4 to IPv6 counters:_TCP Input Count: 384 TCP No Db Drop Count: 448 TCP Output Count: 512......Clear Command
•
clear cgn nat64 stateless xlat1 statistics
Line Card Upgrade
•
Step 1
Step 2
hw-module location 0/2/CPU0 uboot-modeWARNING: This will bring the requested node's PLIM to uboot mode.Do you wish to continue?[confirm(y/n)]yStep 3
RP/0/RP0/CPU0:#LC/0/2/CPU0:Sep 29 02:38:40.418 : plim_services[239]: tile_fsm_uboot_doorbell_handler[3222] Plim moved to uboot-mode and ready for UBOOT upgradeStep 4
upgrade hw-module fpd fpga1_location <>Step 5
upgrade hw-module fpd fpga2 location <>upgrade hw-module fpd fpga3 location <>upgrade hw-module fpd fpga4_location <>upgrade hw-module fpd fpga5_location <>Step 6
hw-module location <> reloadStep 7
show hw-module fpd location <>NAT44 Sample Configuration
The following is a NAT44 Sample Configuration
:
IPv4: 40.22.22.22/16!interface Loopback40description IPv4 Host for NAT44ipv4 address 40.22.22.22 255.255.0.0!interface Loopback41description IPv4 Host for NAT44ipv4 address 41.22.22.22 255.255.0.0!interface GigabitEthernet0/3/0/0.1description Connected to P2_CRS-8 GE 0/6/5/0.1ipv4 address 10.222.5.22 255.255.255.0dot1q vlan 1!router staticaddress-family ipv4 unicast180.1.0.0/16 10.222.5.2181.1.0.0/16 10.222.5.2!!Hardware Configuration for CSGE:!vrf InsideCustomer1address-family ipv4 unicast!!vrf OutsideCustomer1address-family ipv4 unicast!!hw-module service cgn location 0/3/CPU0!service-plim-ha location 0/3/CPU0 datapath-testservice-plim-ha location 0/3/CPU0 core-to-core-testservice-plim-ha location 0/3/CPU0 pci-testservice-plim-ha location 0/3/CPU0 coredump-extraction!!interface GigabitEthernet0/6/5/0.1vrf InsideCustomer1ipv4 address 10.222.5.2 255.255.255.0dot1q vlan 1!interface GigabitEthernet0/6/5/1.1vrf OutsideCustomer1ipv4 address 10.12.13.2 255.255.255.0dot1q vlan 1!interface ServiceApp1vrf InsideCustomer1ipv4 address 1.1.1.1 255.255.255.252service cgn cgn1 service-type nat44!interface ServiceApp2vrf OutsideCustomer1ipv4 address 2.1.1.1 255.255.255.252service cgn cgn1 service-type nat44!interface ServiceInfra1ipv4 address 75.75.75.75 255.255.255.0service-location 0/3/CPU0!!router static!vrf InsideCustomer1address-family ipv4 unicast0.0.0.0/0 ServiceApp140.22.0.0/16 10.222.5.2241.22.0.0/16 10.222.5.22181.1.0.0/16 vrf OutsideCustomer1 GigabitEthernet0/6/5/1.1 10.12.13.1!!vrf OutsideCustomer1address-family ipv4 unicast40.22.0.0/16 vrf InsideCustomer1 GigabitEthernet0/6/5/0.1 10.222.5.2241.22.0.0/16 vrf InsideCustomer1 GigabitEthernet0/6/5/0.1 10.222.5.22100.0.0.0/24 ServiceApp2180.1.0.0/16 10.12.13.1181.1.0.0/16 10.12.13.1!!!CGSE Configuration:service cgn cgn1service-location preferred-active 0/3/CPU0service-type nat44 nat44portlimit 200alg ActiveFTPinside-vrf InsideCustomer1map outside-vrf OutsideCustomer1 address-pool 100.0.0.0/24protocol tcpstatic-forward insideaddress 41.22.22.22 port 80!!protocol icmpstatic-forward insideaddress 41.22.22.22 port 80!!external-logging netflow version 9serveraddress 172.29.52.68 port 2055refresh-rate 600timeout 100 !!!!!IPv4: 180.1.1.1/16!interface Loopback180description IPv4 Host for NAT44ipv4 address 180.1.1.1 255.255.0.0!interface Loopback181description IPv4 Host for NAT44ipv4 address 181.1.1.1 255.255.0.0!interface GigabitEthernet0/6/5/1.1ipv4 address 10.12.13.1 255.255.255.0dot1q vlan 1!router staticaddress-family ipv4 unicast40.22.0.0/16 10.12.13.241.22.0.0/16 10.12.13.2100.0.0.0/24 10.12.13.2 !!NAT64 Stateless Sample Configuration
The following is a NAT64 Stateless Sample Configuration:
IPv6 Configuration:interface Loopback210description IPv6 Host for NAT64 XLATipv6 address 2001:db8:1c0:2:2100::/64ipv6 enable!interface GigabitEthernet0/3/0/0.20description Connected to P2_CRS-8 GE 0/6/5/0.20ipv6 address 2010::22/64ipv6 enabledot1q vlan 20!router static!address-family ipv6 unicast2001:db8:100::/40 2010::2!!CGSE Hardware Configuration:hw-module service cgn location 0/3/CPU0!service-plim-ha location 0/3/CPU0 datapath-testservice-plim-ha location 0/3/CPU0 core-to-core-testservice-plim-ha location 0/3/CPU0 pci-testservice-plim-ha location 0/3/CPU0 coredump-extraction!interface GigabitEthernet0/6/5/0.20description Connected to PE22_C12406 GE 0/3/0/0.20ipv6 address 2010::2/64ipv6 enabledot1q vlan 20!interface GigabitEthernet0/6/5/1.20description Connected to P1_CRS-8 GE 0/6/5/1.20ipv4 address 10.97.97.2 255.255.255.0dot1q vlan 20!interface ServiceApp4ipv4 address 7.1.1.1 255.255.255.252service cgn cgn1 service-type nat64 stateless!interface ServiceApp6ipv6 address 2011::1/64service cgn cgn1 service-type nat64 stateless!interface ServiceInfra1ipv4 address 75.75.75.75 255.255.255.0service-location 0/3/CPU0!router staticaddress-family ipv4 unicast192.0.2.0/24 ServiceApp4198.51.100.0/24 10.97.97.1!address-family ipv6 unicast2001:db8:100::/40 ServiceApp62001:db8:1c0:2::/64 2010::22!!CGSE Configuration:service cgn cgn1service-location preferred-active 0/3/CPU0!service-type nat64 stateless xlatipv6-prefix 2001:db8:100::/40address-family ipv4tos 64interface ServiceApp4tcp mss 1200!address-family ipv6interface ServiceApp6traffic-class 32tcp mss 1200df-override!traceroute translationaddress-pool 202.1.1.0/24algorithm Hash!!IPv4 Hardware Configuration:interface Loopback251description IPv4 Host for NAT64 XLATipv4 address 198.51.100.2 255.255.255.0!interface GigabitEthernet0/6/5/1.20description Connected to P2_CRS-8 GE 0/6/5/1.20ipv4 address 10.97.97.1 255.255.255.0dot1q vlan 20!router staticaddress-family ipv4 unicast192.0.2.0/24 10.97.97.2 !!6RD (IPv6 Rapid Deployment)
Introduction - 6rd
•
•
•
6RD Definitions : -
•
•
•
•
•
•
•
•
Cisco Carrier-Grade Service Engine (CGSE)
Solution Components:
•
–
–
–
•
–
–
–
–
•
–
CGN (NAT44, 6rd, Stateless NAT64..) function resides on CGSE PLIM
Quad Octeon multiprocessor architecture, 64 CPU cores
Standard interface to MSC, 10 Gbps full-duplex nominal
–
IOS-XR on MSC, Linux on Octeon CPUs
Integrated configuration & management via IOS XR
•
–
ServiceInfra SVI
ServiceApp SVI
–
–
Configuring the CGSE
Bring Up the CGSE Board
•
RP/0/RP0/CPU0:#adminRP/0/RP0/CPU0:(admin)#show hw-module fpd location all===================================== ==========================================Existing Field Programmable Devices==========================================HW Current SW Upg/Location Card Type Version Type Subtype Inst Version Dng?============ ======================== ======= ==== ======= ==== =========== ====--------------------------------------------------------------------------------0/1/CPU0 CRS-CGSE-PLIM 0.88 lc fpga2 0 0.559 Nolc fpga3 0 0.559 Nolc fpga4 0 0.559 Nolc fpga5 0 0.559 Nolc fpga1 0 0.41014 Nolc rommonA 0 1.52 Nolc rommon 0 1.52 Yes•
•
•
LC/0/3/CPU0:Sep 28 23:36:36.815 : plim_services[241]: plim_services_init[2063] Uknown role Retrying.., Role = -7205769247857836031LC/0/3/CPU0:Sep 28 23:37:59.341 : plim_services[241]: service_download_thread[3873] App img download max-retries exhausted, 'plim_services' detected the 'warning' condition 'Operation not okay'LC/0/3/CPU0:Sep 28 23:37:59.342 : plim_services[241]: plim_services_tile_failed[752] TILE0 failedRP/0/RP1/CPU0:Sep 28 23:38:18.494 : invmgr[240]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/0, state: FAILED•
RP/0/RP0/CPU0:router#show platformSun Dec 20 07:15:38.893 UTCNode Type PLIM State Config State-----------------------------------------------------------------------------0/0/CPU0 MSC Services Plim IOS XR RUN PWR,NSHUT,MON0/0/0 MSC(SPA) CGSE-TILE OK PWR,NSHUT,MON0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 8X1GE OK PWR,NSHUT,MONrouter(config)interface ServiceInfra1ipv4 address 3.1.1.2 255.255.255.252service-location 0/0/CPU0logging events link-statuscommit•
router(config)hw-module service cgn location 0/0/CPU0commit•
router#hw-module location 0/0/CPU0 reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)] y•
CGSE Health Monitoring
•
•
router(config)#RP/0/RP0/CPU0:(config)#service-plim-ha location R/S/CPU0 datapath-testRP/0/RP0/CPU0:(config)#service-plim-ha location R/S/CPU0 core-to-core-testRP/0/RP0/CPU0:(config)#service-plim-ha location R/S/CPU0 pci-testRP/0/RP0/CPU0:(config)#service-plim-ha location R/S/CPU0 coredump-extractionRP/0/RP0/CPU0:(config)#commit•
RP/0/RP0/CPU0:#show controllers services ha-stats service-cpu 0 location 0/0/cpu0==========================================================High Availability Statistics for MASTER OCTEON 0==========================================================TEST NAME ATTEMPTED PASSED=============================================Datapath test 2327 2327PCI Heartbeat test 1296 1296Core 0 heartbeat 0 0Core 1 heartbeat 2327 2327Core 2 heartbeat 2327 2327..................... .................. ..................... ..............--------------------------------------------------------------------------------6rd Configuration
Step 1
Step 2
•
router(config)#service cgn demoservice-location preferred-active 0/0/CPU0•
router(config)#interface ServiceApp4ipv4 address 1.1.1.1 255.255.255.252service cgn demoservice-type tunnel v6rdlogging events link-status•
router(config)#interface ServiceApp6ipv4 address 5000::1/126service cgn demo service-type tunnel v6rdlogging events link-status•
•
•
router(config)#service cgn demoservice-type tunnel v6rd 6rd1bripv6-prefix 2001:B000::/28source-address 100.1.1.1unicast address 2001:B006:4010:1010::1!address-family ipv4interface ServiceApp4!address-family ipv6interface ServiceApp6
Note
Step 3
•
router(config)#router staticaddress-family ipv4 unicast100.1.1.1/32 1.1.1.2 (Serviceapp4 NextHop)•
Router#show route ipv6S 2001:b000::/28 is directly connected,00:13:44, ServiceApp6S 2001:b006:4010:1010::/60 is directly connected,00:19:24, Null0S 2001:b006:4010:1010::/128 is directly connected,00:13:44, ServiceApp6S 2001:b006:4010:1010::1/128 is directly connected,00:13:44, ServiceApp6C 5000::/64 is directly connected,00:13:44, ServiceApp6L 5000::1/128 is directly connected,00:13:44, ServiceApp6C 2001:db8::/64 is directly connected,01:23:55, GigE0/1/1/4L 2001:db8::2/128 is directly connected,01:23:55, GigE0/1/1/4Step 4
•
•
RP/0/RP1/CPU0:#show cgn tunnel v6rd 6rd1 statisticsThu Oct 21 07:02:54.972 UTCTunnel 6rd configuration=========================Tunnel 6rd name: 6rd1IPv6 Prefix/Length: 2001:db8::/32Source address: 9.1.1.1BR Unicast address: 2001:db8:901:101::1IPv4 Prefix length: 0IPv4 Suffix length: 0TOS: 0, TTL: 255, Path MTU: 1280Tunnel 6rd statistics======================IPv4 to IPv6=============Incoming packet count : 0 (Total No. of Protocol pkts 41non Protocol 41)Incoming tunneled packets count : 0 (Total No. of Protocol pkts 41non Protocol 41)Decapsulated packets : 0ICMP translation count : 0 (ICMPv4 TO ICMPv6 translated count)Insufficient IPv4 payload drop count : 0 (Payload should carry IPv6 header)Security check failure drops : 0No DB entry drop count : 0 (6rd config is incomplete/missing)Unsupported protocol drop count : 0 (IPv4 protocol type is not 41 (IPv6))Invalid IPv6 source prefix drop count : 0 (IPv6 Source from RG doesn't have 6rdprefix)IPv6 to IPv4=============Incoming packet count : 0Encapsulated packets count : 0No DB drop count : 0 (6rd config is not complete/missing)Unsupported protocol drop count : 0 (Non ICMP pkts destined to IPv6 BRanycast/unicast address)IPv4 ICMP==========Incoming packets count : 0Reply packets count : 0Throttled packet count : 0 (ICMP throttling in CGSE 64 PKTS/secNontranslatable drops : 0 (ICMPv4 error pkt (ipv4->TL) at least72 bytes)Unsupported icmp type drop count : 0 (As perhttp://tools.ieft.org/html/draft-ieft-behave-v6v4-xlate-22 )IPv6 ICMP==========Incoming packets count : 0Reply packets count : 0Packet Too Big generated packets count : 0Packet Too Big not generated packets count : 0NA generated packets count : 0TTL expiry generated packets count : 0Unsupported icmp type drop count : 0 (As per http://tools.ieft.org/html/draft-ieft-behave-v6v4-xlate-22)Throttled packet count : 0 (ICMP throttling in CSGE 64pkts/core)IPv4 to IPv6 Fragments=======================Incoming fragments count : 0 (No. of IPv4 Fragments Came in)Reassembled packet count : 0 (No. of Pkts Reassembled fromFragments )Reassembled fragments count : 0 (No. of Fragments Reassembled)ICMP incoming fragments count : 0 (No. of ICMP Fragments Came in)Total fragment drop count : 0Fragments dropped due to timeout : 0 (Fragment dropped due toreassembly timeout)Reassembly throttled drop count : 0 (Fragments throttled)Duplicate fragments drop count : 0Reassembly disabled drop count : 0 (Number of fragments droppedwhile re-assembly is disabled.)No DB entry fragments drop count : 0 (6rd Config is incomplete/missing)Fragments dropped due to security check failure : 0Insufficient IPv4 payload fragment drop count : 0 (1st Fragment should have IPv6header)Unsupported protocol fragment drops : 0 (IPv4 protocol type is not 41(IPv6) & non ICMP)Invalid IPv6 prefix fragment drop count : 0 (IPv6 Source from RG doesn't have6rd prefix)=====================================================================IPv6 to IPv4 Fragments=======================Incoming ICMP fragment count : 0==================================================================================================================================================================Step 5
•
RP/0/RP0/CPU0:BR1#clear cgn tunnel v6rd 6rd1 statisticsClear all 6rd Counters "show cgn tunnel v6rd 6rd1 statistics"Ping to BR Anycast Address
•
/etc/init.d/service_wan_ipv6 # ping 2001:B006:4010:1010::Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 2001:B006:4010:1010::, timeout is 2 seconds:PING 2001:B006:4010:1010::(2001:B006:4010:1010::)56 data bytes64 bytes from 2001:B006:4010:1010::1 : seq=1 ttl=62 time=1.122 ms64 bytes from 2001:B006:4010:1010::1 : seq=2 ttl=62 time=0.914 ms--- 2001:B006:4010:1010:: ping statistics ---5 packets transmitted, 5 packets received, 0% packet loss
Note
RP/0/RP0/CPU0:BR1#show cgn tunnel v6rd 6rd1 statisticsIPv6 to IPv4=============Incoming packet count : 5IPv6 ICMP==========Incoming packets count : 5Reply packets count : 5Enable Additional 6rd Features
•
–
–
Note
•
–
–
service cgn demoservice-type tunnel v6rd 6rd1tos 160ttl 100commit•
–
service cgn demoservice-type tunnel v6rd 6rd1path-mtu 1480commit•
•
service cgn demoservice-type tunnel v6rd 6rd1reassembly-enablecommitRP/0/RP0/CPU0:BR1#show cgn tunnel v6rd 6rd1 statisticsIncoming fragments count : 2Reassembled packet count : 1Reassembled fragments count : 2ICMP incoming fragments count : 0Total fragment drop count : 0Fragments dropped due to timeout : 0Duplicate fragments drop count : 0No DB entry fragments drop count : 0Fragments dropped due to security check failure : 0Insufficient IPv4 payload fragment drop count : 0Unsupported protocol fragment drops : 0Invalid IPv6 prefix fragment drop count : 0Incoming ICMP fragment count : 0•
–
RP/0/RP0/CPU0:BR1#configRP/0/RP0/CPU0:BR1(config)#service cgn cgn1RP/0/RP0/CPU0:BR1(config-cgn)#protocol icmp rate-limit ?<0-65472> ICMP rate limit per second, should be multiple of 64commit•
–
–
service cgn demoservice-type tunnel v6rd 6rd1reset-df-bitcommit•
–
–
–
•
•
•
–
–
Line Card Upgrade
•
Step 1
Step 2
hw-module location 0/2/CPU0 uboot-modeWARNING: This will bring the requested node's PLIM to uboot mode.Do you wish to continue?[confirm(y/n)]yStep 3
RP/0/RP0/CPU0:#LC/0/2/CPU0:Sep 29 02:38:40.418 : plim_services[239]: tile_fsm_uboot_doorbell_handler[3222] Plim moved to uboot-mode and ready for UBOOT upgradeStep 4
upgrade hw-module fpd fpga1_location <>Step 5
upgrade hw-module fpd fpga2 location <>upgrade hw-module fpd fpga3 location <>upgrade hw-module fpd fpga4_location <>upgrade hw-module fpd fpga5_location <>Step 6
hw-module location <> reloadStep 7
show hw-module fpd location <>XLAT and 6rd Commands
address (CGN NetflowV9 logging)
Use the address command to enable the IPv4 address for the Netflow v9 external logging server for logging the entries in the Network Address Translation (NAT) table. To disable the Netflow server configuration, use the no form of this command.
address <A.B.C.D> port <1-65535>
no address <A.B.C.D> port <1-65535>
Syntax Description
address
Address of the server to be used for logging
<A.B.C.D>
Address of the server
port
Port to be used for logging
<1-65535>
Port number. Range is from 1 to 65535.
Command Default
NetflowV9 logging is disabled.
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This NAT44 specific command will configure the ipv4 address and portno for the netflowv9 external logging facility. The address corresponds to the IPv4 address of the NetflowV9 logging server port, which corresponds to the UDP port number in which the NetflowV9 logging server listens for the Netflow logs.
Note
Task ID
Examples
The following example shows how to configure the IPv4 address and port number 45 for NetFlow logging of the NAT table entries:
RP/0/RP1/CPU0:#configMon Oct 11 08:04:49.446 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#external-logging netflow version 9RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#server address 192.0.2.1 port 650RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#showMon Oct 11 08:15:44.325 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1external-logging netflow version 9serveraddress 192.0.2.1 port 650Related Commands
address (CGN static-forward)
Use the address command to enable the inside IPv4 address and port number for static forwarding. Use the no form of this command to disable the inside IPv4 address and port number for static forwarding.
address <A.B.C.D> port <1-65535>
no address <A.B.C.D> port <1-65535>
Syntax Description
address
Address of the server to be used for logging
<A.B.C.D>
Address of the server
port
Port to be used for logging
<1-65535>
Port number. Range is from 1 to 65535.
Command Default
No default behavior or values.
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This NAT44 command will configure the static port forwarding for an inside-ipv4 address and inside-portno combination. With this configuration, packets received on inside with the configured inside-ipv4 address and inside-portno will be forwarded using displayed outside-ipv4address and outside-portno.
CGN can dynamically allocate one free public IP address and port number from the configured outside address pool for an inside address and port.
Task ID
Examples
The following example shows how to configure the inside IPv4 address and port for static forwarding.
RP/0/RP1/CPU0:#configMon Oct 11 09:07:27.535 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#protocol tcpRP/0/RP1/CPU0:(config-cgn-invrf-proto)#static-forward inside address 198.51.100.1 port 800RP/0/RP1/CPU0:(config-cgn-invrf-proto)#showMon Oct 11 09:13:09.185 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1protocol tcpstatic-forward insideaddress 198.51.100.1 port 800Related Commands
address-family ipv4 (CGN)
To enter the IPv4 address family configuration mode while configuring the Carrier Group NAT (CGN), use the address-family ipv4 command in an appropriate configuration mode. To disable support for an address family, use the no form of this command.
address-family ipv4 {interface ServiceApp <1-2000> | tcp mss <28-1500> | tos <0-255>}
no address-family ipv4
Syntax Description
Command Default
No default behavior or values.
Command Modes
CGN-NAT64
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Syntax and Usage Guidelines.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This command will configure the ipv4 address family for NAT64 stateless XLAT.
Task ID
Examples
The following example shows the tcp mss for the ipv4 address family.
RP/0/RP1/CPU0:#configWed Sep 29 11:30:52.452 UTCRP/0/RP1/CPU0:(config)#sevice cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlatRP/0/RP1/CPU0:(config-cgn-nat64-stateless)#address-family ipv4RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#tcp mss 200RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#showWed Sep 29 11:34:30.508 UTCservice cgn cgn1service-type nat64 stateless xlataddress-family ipv4tcp mss 200Related Commands
address-family ipv6 (CGN)
Use the address-family ipv6 command to enter the IPv6 address family configuration mode. Use the no form of this command to disable support for an address family.
address-family ipv6 {interface ServiceApp <1-2000>} { df-override } { protocol { icmp | reset-mtu }} { tcp mss <28-1500>} { traffic-class <0-255>}
no address-family ipv6
Syntax Description
Defaults
No default behavior or values.
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This command will configure the ipv6 address family for NAT64 stateless XLAT.
Task ID
Examples
The following example shows the traffic-class setting for the ipv6 address family.
RP/0/RP1/CPU0:#configWed Sep 29 12:24:55.726 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#address-family ipv6RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#traffic-class 25RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#showWed Sep 29 12:26:56.117 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv6traffic-class 25Related Commands
alg ActiveFTP (CGN)
Use the alg ActiveFTP command to enable support for an Active FTP Application-Level Gateway (ALG) for the Active FTP. Use the no form of this command to disable ALG support for the Active FTP.
alg ActiveFTP
no alg ActiveFTP
Syntax Description
Command Default
By default, ActiveFTP ALG is disabled.
Command Modes
CGN-NAT44
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per cgn instance.
Task ID
Examples
The following example shows how to configure ALG for the active FTP connection for the CGN instance:
RP/0/RP0/CPU0:#configFri Sep 17 20:43:30.876 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP0/CPU0:(config-cgn-nat44)#alg ActiveFTPRP/0/RP0/CPU0:(config-cgn-nat44)#showSat Sep 18 00:17:54.986 UTCservice cgn cgn1service-type nat44 nat1alg ActiveFTPRelated Commands
alg rtsp
Use the alg rtsp command to enable support for the Application-Level Gateway (ALG) Real Time Streaming Protocol (rtsp) . Use the no form of this command to disable alg rtsp support.
alg rtsp
no alg rtsp
Syntax Description
Command Default
By default, the alg rtsp is disabled.
Command Modes
CGN-NAT44
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The application needs to be told to lookout for RTSP packets. The alg rtsp configuration command will allow enabling of RTSP scan.
Task ID
Examples
The following example shows how to configure the alg rtsp for the CGN instance:
RP/0/RP0/CPU0:#configThu Nov 11 07:27:46.511 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP0/CPU0:(config-cgn-nat44)#alg rtspRP/0/RP0/CPU0:(config-cgn-nat44)#showThu Nov 11 07:31:10.482 UTCservice cgn cgn1service-type nat44 nat1alg rtspRelated Commands
br (6rd)
The br command enters the Border Relay configuration mode. To disable this feature, use the no form of this command.
br { ipv4 | ipv6-prefix | source-address | unicast }
no br
Syntax Description
br
Border Relay related configurations
ipv4
IPv4 related configurations
ipv6-prefix
IPv6 prefix
source-address
Source address for tunnel
unicast
Unicast
Defaults
No default behavior or values.
Command Modes
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows the br configuration level commands how to configure the unicast address:
RP/0/RP1/CPU0:#configWed Sep 29 10:47:39.255 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#brRP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#unicast address 2010:db8:ff00::RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showWed Sep 29 10:29:48.215 UTCservice cgn cgn1service-type tunnel v6rd 6rd1brunicast address 2010:db8:ff00::Related Commands
df-override (CGN)
Use the df-override command to SET the DF (Don't Fragment) bit to 0. The no form of this command restores the default behavior.
df-override
no df-override
Syntax Description
Defaults
The df-override bit is set to 1
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Use the df-override command to set the DF bit to 0 when translating IPv6 to IPv4 packets provided the original IPv6 packet size is less than 1280 bytes and there is no Fragment header.
Task ID
Examples
The following example shows how to configure the df-override for the NAT64 stateless configuration:
RP/0/RP1/CPU0:#configThu Sep 16 10:31:38.053 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#ipv6-prefix 2010:db8:ff00::/40RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#address-family ipv6RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#df-overrideRP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#showThu Sep 16 10:32:40.146 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv6df-overrideRelated Commands
external-logging (CGN)
Use the external-logging command to enable the external-logging facility. Use the no form of this command to disable external-logging.
external-logging [ netflow version 9 ]
no external-logging netflow version 9
Syntax Description
netflow
Use netflow-v9 for logging.
version
Version of the Netflow protocol
9
Version 9
server
Specify the logging server information
Command Default
By default, external-logging is disabled.
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Syntax and Usage Guidelines.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The external-logging command enters CGN inside VRF external logging configuration mode.
You can use NetFlow to export NAT table entries.
The external-logging facility supports only netflow version 9.
Task ID
Examples
The following example shows how to enter the configuration mode for the netflowv9 external-logging facility:
RP/0/RP1/CPU0:#configTue Oct 12 08:46:33.996 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#external-logging netflow version 9RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#serverRP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#address 10.10.0.0 port 50RP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#showTue Oct 12 08:49:29.162 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1external-logging netflow version 9serveraddress 10.10.0.0 port 50Related Commands
hw-module service cgn location (CGN)
use the hw-module service cgn location command in global configuration mode to enable a CGN service role on a specified location. The no form of this command disables the CGN service role at the specified location.
hw-module service cgn location node-id
no hw-module service cgn location node-id
Syntax Description
Command Default
No default behavior or values.
Command Modes
CONFIG
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
The Syntax description updated.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
If no is used, the CGN service will be stopped at this particular location.
Task ID
Examples
The following example shows how to configure the CGN service for location 0/2/CPU0:
RP/0/RP1/CPU0:#configTue Oct 12 10:18:39.576 UTCRP/0/RP1/CPU0:(config)#hw-module service cgn location 0/1/CPU0RP/0/RP1/CPU0:(config)#showTue Oct 12 10:19:41.200 UTCBuilding configuration...!! IOS XR Configuration 3.9.3.01Ihw-module service cgn location 0/1/CPU0endRelated Commands
inside-vrf (CGN)
Use the inside-vrf command to enter inside VRF configuration mode. The no form of this command disables the inside vrf configuration.
inside-vrf vrf-name
no inside-vrf vrf-name
Syntax Description
Command Default
No default behavior or values.
Command Modes
CONFIG-CGN
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The inside-vrf command enters CGN inside VRF configuration mode.
Task ID
Examples
The following example shows the inside-vrf tcp mss protocol:
RP/0/RP1/CPU0:#configWed Sep 29 12:39:02.022 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#protocol tcp mss 28RP/0/RP1/CPU0:(config-cgn-invrf)#showWed Sep 29 12:41:39.847 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1protocol tcpmss 28Related Commands
interface ServiceApp (CGN)
Use the interface ServiceApp command to enable the SVI interface. The no form of this command disables a particular service application interface.
interface ServiceApp <1-2000>
no interface ServiceApp <1-2000>
Syntax Description
interface
ServiceApp interface to be used
ServiceApp
SEAPP SVI Interface
<1-2000>
Number of service application interfaces to be configured. Range is from 1 to 2000.
Command Default
No default behavior or values.
Command Modes
CONFIG-CGN
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated examples.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The name of the serviceapp interfaces will be serviceapp n where n can be any number between 1 to 2000.
Note
Task ID
Examples
The following example shows how to configure a nat64 stateless service application interface:
RP/0/RP0/CPU0:#configFri Sep 17 20:30:18.612 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#ipv6-prefix 2010:db8:ff00::/40RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#address-family ipv6RP/0/RP0/CPU0:(config-cgn-nat64-stless-afi)#interface ServiceApp 461RP/0/RP0/CPU0:(config-cgn-nat64-stless-afi)#showFri Sep 17 20:32:20.917 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv6interface ServiceApp461The following example shows how to configure 6rd service application interface:
RP/0/RP1/CPU0:#configMon Oct 4 12:14:09.677 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#address-family ipv6RP/0/RP1/CPU0:(config-cgn-6rd-afi)#interface ServiceApp 46RP/0/RP1/CPU0:(config-cgn-6rd-afi)#showMon Oct 4 12:09:07.174 UTCservice cgn cgn1service-type tunnel v6rd 6rd1address-family ipv6interface ServiceApp46Related Commands
Enables the infrastructure SVI interface.
Enables an instance for the CGN application.
Enables the particular instance of the CGN application on the active and standby locations.
interface ServiceInfra (CGN)
Use the interface ServiceInfra command in global configuration mode to enable the infrastructure SVI interface. The no form of this command disables a particular service infrastructure interface.
interface ServiceInfra <1-2000>
no interface ServiceInfra <1-2000>
Syntax Description
ServiceInfra
SEINFRA SVI Interface
<1-2000>
Number of service infrastructure interfaces to be configured. Range is from 1 to 2000.
Command Default
There is no default behavior.
Note
Command Modes
CONFIG-IF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Only one serviceinfra interface can be configured per Roddick PLIM card.
Note
Task ID
Examples
The following example shows how to configure the service infrastructure interface:
RP/0/RP1/CPU0:#configTue Oct 12 11:39:15.999 UTCRP/0/RP1/CPU0:(config)#interface ServiceInfra 1RP/0/RP1/CPU0:(config-if)#ipv4 address 3.1.1.2 255.255.255.252RP/0/RP1/CPU0:(config-if)#service-location 0/1/CPU0RP/0/RP1/CPU0:(config-if)#logging events link-statusRP/0/RP1/CPU0:(config-if)#showTue Oct 12 11:41:51.751 UTCinterface ServiceInfra1ipv4 address 3.1.1.2 255.255.255.252service-location 0/1/CPU0logging events link-statusRelated Commands
Enables the application SVI interface.
Enables an instance for the CGN application.
Enables the particular instance of the CGN application on the active and standby locations.
ipv4 prefix (6rd)
Use the ipv4 prefix command to assign a value for the ipv4 prefix of the tunnel. When the no form of this command is specified, the ipv4 prefix is not used.
ipv4 prefix length <0-31>
no ipv4 prefix length <0-31>
Syntax Description
Defaults
Zero will be the ipv4 prefix length when no ipv4 prefix is assigned
Command Modes
CGN-TUNNEL
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This command will assign a value for the common ipv4 prefix length to be used as part of both ends of the tunnel.
This is an optional br tunnel configuration parameter. If this parameter is added or modified, the unicast address also should also be modified.
Note
Note
Task ID
Examples
The following example shows how to configure the ipv4 prefix:
RP/0/RP1/CPU0:#configWed Oct 13 06:32:09.370 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#brRP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#ipv4 prefix length 16RP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#showWed Oct 13 06:33:57.046 UTCservice cgn cgn1service-type tunnel v6rd 6rd1bripv4 prefix length 16Related Commands
ipv4 suffix (6rd)
Use the ipv4 suffix command to assign a value for the ipv4 tunnel suffix. When the no form of this command is specified, the ipv4 suffix is not used.
ipv4 suffix length <0-31>
no ipv4 suffix length <0-31>
Syntax Description
Defaults
Zero will be the ipv4 suffix length when no ipv4 suffix is assigned
Command Modes
CGN-TUNNEL
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This command will assign a value for the common ipv4 suffix length to be used as part of both ends of the tunnel.
This is an optional br tunnel configuration parameter. If this parameter is added or modified, the unicast address also should also be modified.
Note
Note
Task ID
Examples
The following example shows how to configure the ipv4 suffix:
RP/0/RP1/CPU0:#configWed Oct 13 07:00:35.747 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#brRP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#ipv4 suffix length 15RP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#showWed Oct 13 07:02:29.064 UTCservice cgn cgn1service-type tunnel v6rd 6rd1bripv4 suffix length 15Related Commands
ipv6-prefix (6rd)
For a given 6rd domain there is exactly one 6rd prefix. The ipv6-prefix command is used to convert the ipv4 address into ipv6 address for use by the 6rd domain.
For NAT64 Stateless, the ipv6-prefix command is used for converting the ipv4 addresses into ipv6 addresses and ipv4 addresses into ipv6 addresses.
When the no form of this command is used there is no ipv6 prefix assigned for the application.
ipv6-prefix X:X::X/length <IPV6 subnet mask>
no ipv6-prefix X:X::X/length> <IPV6 subnet mask>
Syntax Description
ipv6-prefix
IPv6 prefix to be used to translate IPv4 address to IPv6 address
X:X::X/length
IPv6 address and prefix
IPV6 subnet mask
IPv6 address and prefix
Defaults
There is no default behavior.
Command Modes
TUNNEL-6RD
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The ipv6-prefix command is used in the NAT64 stateless and Border Relay (br) tunnel configurations.
The ipv6-prefix command will be used to generate a delegated ipv6 prefix for the Border Relay, br, related configurations. This is a mandatory br tunnel parameter. All mandatory parameters should be added or deleted at the same time.
Note
Note
Note
The ipv6-prefix command will configure the ipv6 prefix to be used for converting the ipv4 addresses into ipv6 addresses and ipv4 addresses into ipv6 addresses.
The same ipv6-prefix can be used for multiple nat64 stateless instances under multiple CGNs for load balancing.
Note
Task ID
Examples
The following example shows how to enter the ipv6-prefix for the NAT64 stateless CGN instance:
RP/0/RP1/CPU0:#configWed Oct 6 10:18:21.502 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#ipv6-prefix 2010:db8:ff00::/40RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#showWed Oct 6 10:19:55.758 UTCservice cgn cgn1service-type nat64 stateless xlat1ipv6-prefix 2010:db8:ff00::/40The following example shows how to enter the ipv6-prefix for the 6RD CGN instance:
RP/0/RP1/CPU0:#configWed Oct 6 10:30:55.107 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#brRP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#ipv6-prefix 2010:db8:ff00::/40RP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#showWed Oct 6 10:34:01.932 UTCservice cgn cgn1service-type tunnel v6rd 6rd1bripv6-prefix 2010:db8:ff00::/40Related Commands
map (CGN)
Use the map command to map an outside VRF and address pool to an inside VRF and address pool. Use the no form of this command to remove the outside VRF and address pool mapping for the specified inside VRF.
map [outside-vrf outside-vrf-name] [address-pool < A.B.C.D/prefix IP>< subnet mask>]
no map [outside-vrf outside-vrf-name] address-pool address/prefix
Syntax Description
Command Default
No default behavior or values.
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per inside vrf per cgn instance.
The map command maps the inside VRF to an outside VRF and assigns an outside address pool for the mapping.
There will be only one NAT44 instance per cgn instance.
An inside-VRF can be present in one and only one CGN instance.
One inside VRF can be mapped to only one outside VRF.
There can be multiple non-overlapping address-pools in a particular outside VRF.
The address pools being used on a CRS box for the outside VRF's should never overlap with each other.
An outside-VRF can be present in multiple CGN instances with different address pools.
If the outside VRF name is not specified, the default VRF is enabled.
Task ID
Examples
The following example shows how to configure the outside VRF and to assign the outside address pool for the mapping:
RP/0/RP1/CPU0:#configWed Oct 13 08:09:12.904 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#map outside-vrf outsidevrf1 address-pool 10.0.0.1 255.255.255.0RP/0/RP1/CPU0:(config-cgn-invrf)#showWed Oct 13 08:26:09.904 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1map outside-vrf outsidevrf1 address-pool 10.0.0.1/24Related Commands
mss (CGN)
Use the mss command to configure the inside-vrf TCP MSS (Maximum Segment Size). The no form of this command disables overriding the TCP MSS value in packets.
mss <28-1500>
no mss
Syntax Description
Command Default
If not configured, the default value for tcp mss is 1460 bytes
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per inside vrf per cgn instance.
The MSS value, which is configured by the mss command, overrides the MSS value that is set in the received TCP packets. The range for MSS value is from 28 to 1500.
The mss command adjusts the MSS value of the TCP SYN packets going through.
Task ID
Examples
The following example shows how to configure TCP MSS value as 1100 for the CGN instance:
RP/0/RP1/CPU0:#configWed Oct 13 10:34:44.212 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#protocol tcpRP/0/RP1/CPU0:(config-cgn-invrf-proto)#mss 1400RP/0/RP1/CPU0:(config-cgn-invrf-proto)#showWed Oct 13 10:36:23.896 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1protocol tcpmss 1400Related Commands
path-mtu (CGN)
Use the path-mtu command to configure the path Maximum Transmission Unit (MTU) for the netflowv9-based external-logging facility. Use the no form of this command to revert back to the default of 1500.
path-mtu <100-9200>
no path-mtu <100-9200>
Syntax Description
Command Default
The default path-mtu value is set to 1500.
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This NAT44 specific command will configure the value of the path-mtu for the netflowv9 based external logging facility for an inside vrf of cgn instance.
This command restricts the maximum size of the Netflow-v9 logging packet
The path-mtu value ranges from 100 to 9200.
The netflowv9-based external-logging facility can be used to export the NAT table entries.
Note
Task ID
Examples
The following example shows how to configure the path-mtu with the value of 2900 for the netflowv9-based external-logging facility:
RP/0/RP1/CPU0:#configWed Oct 13 11:07:53.464 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#external-logging netflow version 9RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#serverRP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#address 192.0.2.1 port 650RP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#path-mtu 1500RP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#showWed Oct 13 11:12:20.391 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1external-logging netflow version 9serveraddress 192.0.2.1 port 650path-mtu 1500Related Commands
path-mtu (6rd)
The path-mtu command will configure the 6rd ipv4 tunnel MTU (Maximum Transmission Unit) size in bytes. When the no form of this command is specified the MTU value will be set to its default value.
path-mtu <1280-9216>
no path-mtu
Syntax Description
Defaults
The default value is 1280.
Command Modes
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This command will configure the path MTU size in bytes for the ipv4 tunnel. If any packet comes with more than this path MTU, ICMP error will be sent back to the source.
Task ID
Examples
The following example shows how to configure the path-mtu with the value of 1280:
RP/0/RP1/CPU0:#configThu Sep 23 11:37:15.491 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#path-mtu 1500RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showThu Sep 23 11:39:17.737 UTCservice cgn cgn1service-type tunnel v6rd 6rd1path-mtu 1500Related Commands
portlimit (CGN)
Use the portlimit command to limit the number of entries per source address. Use the no form of this command to revert back to the default value of 100.
portlimit <1-65535>
no portlimit <1-65535>
Syntax Description
portlimit
Limit the number of entries per address
<1-65535>
Value for the port limit. Range is from 1 to 65535.
Command Default
The default value is 100 when the port limit is not configured.
Command Modes
CGN-NAT44
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per cgn instance.
The portlimit command configures the port limit per subscriber for the system, including TCP, UDP, and ICMP. In addition, the portlimit command restricts the number of ports that is used by an IPv4 address; for example, it limits the number of CNAT entries per IPv4 address in the CNAT table.
Task ID
Examples
This example shows how the port-limit needs can increased from the default value of 100 to a higher value of 500:
RP/0/RP1/CPU0:#configWed Oct 13 11:58:15.265 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#portlimit 850RP/0/RP1/CPU0:(config-cgn-nat44)#showWed Oct 13 12:00:22.279 UTCservice cgn cgn1service-type nat44 nat1portlimit 850Related Commands
protocol (CGN-INVRF)
Use the protocol command to enter the ICMP, TCP, and UDP inside-vrf protocol configuration mode. The no form of this command removes all the features that are enabled under the protocol configuration.
protocol {icmp | tcp | udp} {mss <28-1500>} {static-forward inside address <A.B.C.D> port <1-65535>}
no protocol {icmp | tcp | udp}
Syntax Description
Command Default
No default behavior or values.
Command Modes
CONFIG-CGN
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Syntax and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows the ICMP protocol with static forwarding:
RP/0/RP1/CPU0:#configWed Oct 13 12:38:16.452 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#protocol icmpRP/0/RP1/CPU0:(config-cgn-invrf-icmp)#static-forward inside address 192.0.2.1 port 650RP/0/RP1/CPU0:(config-cgn-invrf-icmp)#showWed Oct 13 12:42:05.211 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1protocol icmpstatic-forward insideaddress 192.0.2.1 port 650#Related Commands
protocol (CGN-NAT44)
Use the protocol command to enter the ICMP, TCP, and UDP protocol configuration mode. The no form of this command remove all the features that are enabled under the protocol configuration mode.
protocol {icmp | tcp | udp} [{session} <active | initial>] {timeout <1-65535>}
no protocol {icmp | tcp | udp}
Syntax Description
Command Default
No default behavior or values.
Command Modes
CGN-NAT44
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The protocol command enters the appropriate CGN AFI configuration mode.
Task ID
Examples
The following example shows how to configure the ICMP protocol for a CGN instance:
RP/0/RP1/CPU0:#configTue Sep 14 13:50:00.056 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#protocol icmp timeout 120RP/0/RP1/CPU0:(config-cgn-nat44)#showTue Sep 14 13:51:43.970 UTCservice cgn cgn1service-type nat44 nat1protocol icmptimeout 120The following example shows how to configure the UDP protocol for a CGN instance:
RP/0/RP1/CPU0:#configTue Sep 14 13:45:51.136 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#protocol udp session initial timeout 120RP/0/RP1/CPU0:(config-cgn-nat44)#protocol udp session active timeout 180RP/0/RP1/CPU0:(config-cgn-nat44)#showTue Sep 14 13:47:41.918 UTCservice cgn cgn1service-type nat44 nat1protocol udpsession initial timeout 120session active timeout 180The following example shows how to configure the UDP protocol for a CGN instance:
RP/0/RP1/CPU0:#configThu Oct 14 07:05:20.608 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#protocol tcp session active timeout 180RP/0/RP1/CPU0:(config-cgn-nat44)#showThu Oct 14 07:06:46.470 UTCservice cgn cgn1service-type nat44 nat1protocol tcpsession active timeout 180Related Commands
protocol icmp reset-mtu (CGN)
The protocol icmp reset-mtu command will reset the received packet size to 1280 when the received ipv4 ICMP packet size is less than 1280 bytes. When the no form of this command is specified, the received icmp packet size will be copied when translating ipv4 to ipv6.
protocol icmp reset-mtu
no protocol icmp reset-mtu
Syntax Description
protocol
Select a protocol
icmp
ICMP protocol
reset-mtu
Reset maximum transmission unit when packet is too big
Defaults
Received packet size will be copied when translating ipv4 to ipv6 for icmp packets.
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
When the icmp reset-mtu protocol is enabled, the ICMP packet size will be reset to 1280 when translating from ipv4 to ipv6 if the ICMP packet size is less than 1280 bytes.
Task ID
Examples
The following example shows how to configure the icmp reset-mtu protocol for a CGN instance:
RP/0/RP1/CPU0:#configThu Sep 16 11:27:57.172 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#ipv6-prefix 2010:db8:ff00::/40RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#address-family ipv6RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#protocol icmpRP/0/RP1/CPU0:ChunniBab(config-cgn-nat64-stless-icmp)#reset-mtuRP/0/RP1/CPU0:ChunniBab(config-cgn-nat64-stless-icmp)#showThu Sep 16 11:29:22.731 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv6protocol icmpreset-mtuRelated Commands
reassembly-enable (6rd)
Use the reassembly-enable command to reassemble fragmented packets. When the no form of this command is specified, packet fragments will not be reassembled.
reassembly-enable
no reassembly-enable
Syntax Description
Defaults
By default, reassembly is not allowed.
Command Modes
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows how to apply the reassembly-enable for a 6rd tunnel:
RP/0/RP1/CPU0:#configThu Sep 23 12:48:36.222 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#reassembly-enableRP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showThu Sep 23 12:49:35.929 UTCservice cgn cgn1service-type tunnel v6rd 6rd1reassembly-enableRelated Commands
refresh-direction (CGN)
Use the refresh-direction command to configure the Network Address Translation (NAT) mapping refresh direction. Use the no form of this command to revert back to bi-directional.
refresh-direction Outbound
no refresh-direction Outbound
Syntax Description
refresh-direction
NAT refresh direction to be used
Outbound
Configures only the refresh direction for outbound.
Command Default
The default is bidirectional when the NAT refresh-direction is not configured,
Command Modes
CONFIG-CGN
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per cgn instance.
Translation entries that do not have traffic flowing for specific time period are timed out and deleted to prevent unnecessary usage of system resources. Any traffic for a particular translation entry refreshes the entry and prevents it getting timed out. Usually, the refresh is based on packets coming from both inside and outside. This is referred to as bi-directional refresh mechanism. However, bi-directional refresh can lead to denial of service (DoS) attacks because someone from the outside can periodically refresh the entries even though there is no inside traffic.
When NAT refresh direction is configured as Outbound, the translation entries are refreshed only by traffic flowing from inside to outside and prevents DoS attacks.
Task ID
Examples
The following example shows how to configure the mapping refresh direction for outbound:
RP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#refresh-direction outboundRP/0/RP1/CPU0:(config-cgn-nat44)#showWed Sep 15 07:49:07.201 UTCservice cgn cgn1service-type nat44 nat1refresh-direction OutboundRelated Commands
refresh-rate (CGN)
Use the refresh-rate command to resend the log template to the netflowv9 server. Use the no form of this command to revert back to the default value of 500 packets.
refresh-rate <1-600>
no refresh-rate <1-600>
Syntax Description
Command Default
Default refresh-rate value is 500
Command Modes
EXTLOG-SERVER
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The netflowv9 based logging requires that a logging template be sent to the server periodically. The refresh-rate value implies that after sending these many packets to the server, the template will be resent. The timeout value implies that after these many minutes has elapsed since the template was last sent, the template will be resent to the logging server. The refresh-rate and timeout values are mutually exclusive, i.e. whichever expires first, will be taken into consideration for re sending the template.
Note
Task ID
Examples
The following example shows how to configure the refresh rate value of 60 for NetFlow logging for the NAT table entries:
RP/0/RP1/CPU0:#configureTue Oct 5 09:50:22.184 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#external-logging netflow version 9RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#serverRP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#refresh-rate 60RP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#showTue Oct 5 09:52:46.293 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1external-logging netflow version 9serverrefresh-rate 60Related Commands
reset-df-bit (6rd)
Use the reset-df-bit command to enable anycast mode functionality. When the no form of this command is specified the anycast mode functionality is disabled.
reset-df-bit
no reset-df-bit
Syntax Description
Defaults
Anycast mode is disabled.
Command Modes
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows how to configure the reset-df-bit:
RP/0/RP1/CPU0:#configWed Sep 29 06:59:27.886 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#reset-df-bitRP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showWed Sep 29 07:00:55.596 UTCservice cgn cgn1service-type tunnel v6rd 6rd1reset-df-bitRelated Commands
server (CGN)
Use the server command to enable the netflow external logging server IPv4 address and port for the netflowv9-based external-logging facility. Use the no form of this command to disable the IPv4 address and port for the netflow logging server. External logging of NAT Entries gets disabled.
server address <A.B.C.D> port <1-65535>
no server
Syntax Description
server
Specify the logging server information
address
Address of the server to be used for logging
<A.B.C.D>
IP address of the server
port
Port to be used for logging
<1-65535>
Port number
Command Default
Netflowv9 server for external-logging is disabled.
Command Modes
CGN-INVRF
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The NAT44 server command will configure the ipv4 address and portno for the server to be used for netflowv9 based external logging facility for an inside vrf of a cgn instance.
Note
Task ID
Examples
The following example shows how to configure the logging information for the IPv4 address and server:
RP/0/RP1/CPU0:#configTue Oct 12 08:46:33.996 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#external-logging netflow version 9RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#serverRP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#address 10.10.0.0 port 50RP/0/RP1/CPU0:Chun(config-cgn-invrf-af-extlog-server)#showTue Oct 12 08:49:29.162 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1external-logging netflow version 9serveraddress 10.10.0.0 port 50Related Commands
service cgn (CGN)
To enable an instance for the CGN application, use the service cgn command in global configuration mode. To disable the instance of the CGN application, use the no form of this command.
service cgn instance-name
no service cgn instance-name
Syntax Description
Command Default
No default behavior or values.
Command Modes
CONFIG
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The service cgn command enters CGN configuration mode.
Task ID
Examples
The following example shows how to configure the instance named cgn1 for the CGN application:
RP/0/RP1/CPU0:#configThu Oct 14 09:04:54.767 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#showThu Oct 14 09:05:22.500 UTCservice cgn cgn1Related Commands
Enables an instance for the CGN application.
Creates a NAT44 instance for the CGN application
Creates a NAT64 instance for the CGN application
Creates a v6rd tunnel application.
service-location (CGN)
Use the service-location command in CGN configuration mode to enable the particular instance of the CGN application on the active and standby locations. Use the no form of this command to disable the instance to run at the location of the CGN application.
service-location preferred-active node-id [preferred-standby node-id]
no service-location preferred-active node-id [preferred-standby node-id]
Syntax Description
Command Default
No default behavior or values.
Command Modes
config-cgn
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows how to specify active and standby locations for the CGN application:
RP/0/RP1/CPU0:#configWed Sep 29 13:41:36.358 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-location preferred-active 0/1/CPU0 preferred-standby 0/3/CPU0RP/0/RP1/CPU0:(config-cgn)#showWed Sep 29 13:45:19.086 UTCservice cgn cgn1service-location preferred-active 0/1/CPU0 preferred-standby 0/3/CPU0Related Commands
Enables a CGN service role on a specified location.
Enables the application SVI interface.
Enables the infrastructure SVI interface.
Enables an instance for the CGN application.
service-type nat44 (CGN)
Use the service-type nat44 command to create a NAT44 instance for the CGN application. The no form of this command will delete this instance of the nat44 application.
service-type nat44 instance [ alg | inside-vrf | portlimit | protocol | refresh-direction]
no service-type nat44 instance
Syntax Description
Defaults
There can only be 1 service-type NAT44 configuration per Roddick line card/chassis.
Command Modes
CONFIG-CGN
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The NAT44 instance name should be unique across all the CGN NAT44 and NAT64 stateless instance names.
Task ID
Examples
The following example shows how to configure the nat44 instance named nat44 for the CGN application:
RP/0/RP0/CPU0:#configFri Sep 17 20:43:30.876 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP0/CPU0:(config-cgn-nat44)#showFri Sep 17 20:44:10.344 UTCservice cgn cgn1service-type nat44 nat1Related Commands
service-type nat64 (CGN)
Use the service-type nat64 command to create a nat64 stateless application. The no form of this command will delete the nat64 stateless application.
service-type nat64 stateless instance [address-family | traceroute | ipv6-prefix | ubit-reserved ]
no service-type nat64 stateless instance
Syntax Description
Defaults
There can only be 64 Service-type NAT64 configurations per Roddick line card or chassis.
Command Modes
CONFIG-CGN
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The NAT64 stateless instance name(s) should be unique across all the CGN NAT44 and NAT64 stateless instance names.
There can only be 64 service-type NAT64 configurations per Roddick line card or chassis spanning over different cards.
Task ID
Examples
The following example shows how to configure the nat64 stateless instance named xlat1for the CGN application:
RP/0/RP1/CPU0:#configWed Sep 15 08:02:39.358 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#showWed Sep 15 08:15:41.097 UTCservice cgn cgn1service-type nat64 stateless xlat1Related Commands
service-type tunnel (CGN)
Use the service-type tunnel command to create a v6rd tunnel application. The no form of this command will delete this instance of the v6rd tunnel application.
service-type tunnel v6rd instance {address-family | br | path-mtu | reassembly-enable | reset-df-bit | tos | ttl }
no service-type tunnel v6rd instance
Syntax Description
Defaults
64 service-type v6rd tunnel configurations per Roddick line card or chassis.
Command Modes
CONFIG-CGN
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The 6rd instance name should be unique across all the instance names like CGN instance name, NAT44 instance and NAT64 stateless instance names.
There can only be 64 Service-type v6rd tunnel configurations per Roddick line card or chassis spanning over different cards.
Task ID
Examples
The following example shows how to configure the tunnel instance named nat64 for the CGN application:
RP/0/RP1/CPU0:#configThu Oct 14 12:46:34.188 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showThu Oct 14 12:47:11.521 UTCservice cgn cgn1service-type tunnel v6rd 6rd1Related Commands
session (CGN)
Use the session command to configure the timeout values for both active and initial sessions for TCP or UDP. The no form of this command reverts back to the default value for the TCP or UDP session time outs.
session {active | initial} timeout seconds
no session {active | initial} timeout seconds
Syntax Description
Command Default
If the value for the UDP initial session timeout is not configured, the default value for the UDP initial session timeout is 30.
If the value for the UDP active session timeout is not configured, the default value for the UDP active session timeout is 120.
If the value for the TCP initial session timeout is not configured, the default value for the TCP initial session timeout is 120.
If the value for the TCP active session timeout is not configured, the default value for the TCP active session timeout is 1800 (30 minutes).
Command Modes
AFI-PROTO
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Usage Guidelines and Examples.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
We recommend that you configure the timeout values for the protocol sessions carefully. For example, the values for the protocol and NAT functions must be configured properly.
If the no form of this command is specified, the following guidelines apply:
•
•
•
•
Task ID
Examples
The following example shows how to configure the TCP initial and active timeout session values:
RP/0/RP1/CPU0:#configThu Oct 14 12:50:59.342 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#protocol tcpRP/0/RP1/CPU0:(config-cgn-proto)#session active timeout 90RP/0/RP1/CPU0:(config-cgn-proto)#session initial timeout 120RP/0/RP1/CPU0:(config-cgn-proto)#showThu Oct 14 12:54:56.576 UTCservice cgn cgn1service-type nat44 nat1protocol tcpsession initial timeout 120session active timeout 90The following example shows how to configure the UDP initial and active timeout values:
RP/0/RP1/CPU0:#configThu Oct 14 12:55:49.619 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#protocol udpRP/0/RP1/CPU0:(config-cgn-proto)#session active timeout 90RP/0/RP1/CPU0:(config-cgn-proto)#session initial timeout 120RP/0/RP1/CPU0:(config-cgn-proto)#showThu Oct 14 12:57:52.000 UTCservice cgn cgn1service-type nat44 nat1protocol udpsession initial timeout 120session active timeout 90Related Commands
source-address (6rd)
Use the source-address command to assign an ipv4 address as the tunnel source address. When the no form of this command is used then there is no source address assigned to the tunnel.
source-address < A.B.C.D>
no source-address < A.B.C.D>
Syntax Description
Defaults
There is no default behavior.
Command Modes
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Note
Note
Task ID
Examples
The following example shows how to configure the v6rd tunnel source-address:
RP/0/RP1/CPU0:#configWed Sep 22 10:24:47.552 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#brRP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#source-address 10.2.2.1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd-br)#showWed Sep 22 10:26:13.196 UTCservice cgn cgn1service-type tunnel v6rd 6rd1brsource-address 10.2.2.1Related Commands
static-forward inside (CGN)
Use the static-forward inside command to enable static port forwarding for an inside IPv4 address and inside port combination. The no form of this command disables static port forwarding.
static-forward inside address <A.B.C.D> port <1-65535>
no static-forward inside
Syntax Description
Command Default
No default behavior or values.
Command Modes
INVRF-AFI
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Syntax, Usage Guidelines and Example.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per inside vrf per cgn instance.
This command will configure the static port forwarding for an inside-ipv4 address and inside-portno combination. With this configuration, packets received on inside with the configured inside-ipv4 address and inside-portno will be forwarded using displayed outside-ipv4 address & outside-portno.
Task ID
Examples
The following example shows how to configure static forwarding for a port:
RP/0/RP1/CPU0:#configWed Oct 13 12:38:16.452 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#protocol icmpRP/0/RP1/CPU0:(config-cgn-invrf-icmp)#static-forward inside address 192.0.2.1 port 650RP/0/RP1/CPU0:(config-cgn-invrf-icmp)#showWed Oct 13 12:42:05.211 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1protocol icmpstatic-forward insideaddress 192.0.2.1 port 650Related Commands
tcp mss (CGN)
Use the tcp mss command to adjust the TCP maximum segment size (MSS) value for a ServiceApp interface. Use the no form of this command to disable a particular service application interface.
tcp mss <28-1500>
no tcp mss
Syntax Description
tcp
Protocol tcp
mss
Maximum segment size for TCP in bytes
<28-1500>
Maximum segment size to be used in bytes
Command Default
Default is disabled for the TCP maximum segment size (MSS) adjustment.
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
If this configuration does not exist, TCP determines the maximum segment size based on the settings specified by the application process, interface maximum transfer unit (MTU), or MTU received from Path MTU Discovery.
This is an NAT64 stateless translation command to be applied per instance of NAT64 stateless of a cgn instance. This command will enable rewriting of the TCP MSS value in the translated IPv4 packet (getting translated from IPv6 to IPv4), the incoming TCP MSS value is greater than the value configured by this command.
Task ID
Examples
The following example shows how to configure TCP MSS value as 1000 for a NAT64 stateless ServiceApp interface
RP/0/RP1/CPU0:#configThu Sep 16 06:55:47.821 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#interface ServiceApp 2RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#address-family ipv4RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#tcp mss 1000RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#showThu Sep 16 07:00:02.014 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv4interface ServiceApp2tcp mss 1000Related Commands
timeout (CGN)
Use the timeout command to configure the timeout in seconds for the ICMP, TCP and UDP sessions. The no form of this command reverts the timeout value back to the default.
timeout seconds
no timeout seconds
Syntax Description
Command Default
If icmp timeout is not configured, the default ICMP timeout value is 60 seconds.
If udp init-session timeout is not configured, the default udp init-session timeout value is 30 seconds.
If udp active-session timeout is not configured, the default udp active-session timeout value is 120 sec.
If tcp init-session timeout is not configured, the default tcp init timeout value is 120 seconds.
If tcp active-session timeout is not configured, the default tcp active-session timeout value is 30 minutes (1800 seconds).
Command Modes
CGN-NAT44
Command History
Release 3.9.1
This command was introduced.
Release 3.9.2
No modification.
Release 3.9.3
Updated Command Default and Usage Guidelines.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is a NAT44 service type specific command to be applied per cgn instance.
This command will configure the initial and active timeout value in seconds for TCP or UDP sessions for a cgn instance. For ICMP the user will only be able to configure the timeout value.
Note
For TCP and UDP, the per port active timeout session will be prioritized according to the following criteria, higher to lower precedence:
3.
4.
5.
6.
Enter up to 1000 timer entries (inclusive of port only, ip only or port/ip combo).
We recommend that you configure the timeout values for the protocol sessions carefully.
Task ID
Examples
The following example shows how to configure a destination address and port combination value as 600 for the tcp session:
RP/0/RP0/CPU0:Chammeli#configMon Nov 15 12:44:17.954 UTCRP/0/RP0/CPU0:Chammeli(config)#service cgn cgn1RP/0/RP0/CPU0:Chammeli(config-cgn)#service-type nat44 nat1RP/0/RP0/CPU0:Chammeli(config-cgn-nat44)#inside-vrf redRP/0/RP0/CPU0:Chammeli(config-cgn-invrf)#protocol tcpRP/0/RP0/CPU0:Chammeli(config-cgn-invrf-proto)#address 40.1.1.2 port 80 timeout 600RP/0/RP0/CPU0:Chammeli(config-cgn-invrf-proto)#showMon Nov 15 12:47:57.198 UTCservice cgn cgn1service-type nat44 nat1inside-vrf redprotocol tcpaddress 40.1.1.2port 80 timeout 600The following example shows how to configure a destination address value as 600 for the tcp session:RP/0/RP0/CPU0:Chammeli#configMon Nov 15 12:55:30.276 UTCRP/0/RP0/CPU0:Chammeli(config)#service cgn cgn1RP/0/RP0/CPU0:Chammeli(config-cgn)#service-type nat44 nat1RP/0/RP0/CPU0:Chammeli(config-cgn-nat44)#inside-vrf redRP/0/RP0/CPU0:Chammeli(config-cgn-invrf)#protocol tcpRP/0/RP0/CPU0:Chammeli(config-cgn-invrf-proto)#address 40.1.1.2 timeout 600RP/0/RP0/CPU0:Chammeli(config-cgn-invrf-proto)#showMon Nov 15 12:57:21.841 UTCservice cgn cgn1service-type nat44 nat1inside-vrf redprotocol tcpaddress 40.1.1.2timeout 600The following example shows how to configure a destination port value as 600 for the tcp session:RP/0/RP0/CPU0:Chammeli#configMon Nov 15 13:01:54.262 UTCRP/0/RP0/CPU0:Chammeli(config)#service cgn cgn1RP/0/RP0/CPU0:Chammeli(config-cgn)#service-type nat44 nat1RP/0/RP0/CPU0:Chammeli(config-cgn-nat44)#inside-vrf redRP/0/RP0/CPU0:Chammeli(config-cgn-invrf)#protocol tcpRP/0/RP0/CPU0:Chammeli(config-cgn-invrf-proto)#port 80 timeout 600RP/0/RP0/CPU0:Chammeli(config-cgn-invrf-proto)#showMon Nov 15 13:03:40.954 UTCservice cgn cgn1service-type nat44 nat1inside-vrf redprotocol tcpport 80 timeout 600Related Commands
timeout (CGN logging)
Use the timeout command to configure the frequency at which the netflow-v9 template is refreshed or resent to the netflow-v9 server. The no form of this command to reverts the timeout back to the default value of 30 minutes.
timeout <1-3600>
no timeout <1-3600>
Syntax Description
Command Default
The default timeout value is 30 minutes.
Command Modes
CGN-INVRF
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
The netflowv9 based logging requires that a logging template be sent to the server periodically. The timeout value implies that after these many minutes has elapsed since the template was last sent, the template will be resent to the logging server. The refresh-rate value implies that after sending these many packets to the server, the template will be resent. The timeout and refresh-rate values are mutually exclusive, i.e. whichever expires first, will be taken into consideration for re sending the template.
Note
Task ID
Examples
The following example shows how to configure the timeout value as 50 for the NetFlow logging information for the NAT table entries:
RP/0/RP1/CPU0:#configureTue Oct 5 09:03:35.007 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat44 nat1RP/0/RP1/CPU0:(config-cgn-nat44)#inside-vrf insidevrf1RP/0/RP1/CPU0:(config-cgn-invrf)#external-logging netflow version 9RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#server timeout 60RP/0/RP1/CPU0:(config-cgn-invrf-af-extlog)#showTue Oct 5 09:08:14.072 UTCservice cgn cgn1service-type nat44 nat1inside-vrf insidevrf1external-logging netflow version 9servertimeout 60Related Commands
tos (CGN)
The tos command configures the ipv4 tunnel type of service. The no form of this command disables the type of service.
tos <0-255>
no tos <0-255>
Syntax Description
Defaults
The default type of service is 0.
Command Modes
CGN-NAT64
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This command is used to configure the type of service (TOS) for the ipv4 tunnel.
Task ID
Examples
The following example shows how to configure the NAT64 ipv4 tunnel type of service:
RP/0/RP1/CPU0:#configWed Sep 15 11:02:43.611 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP1/CPU0:(config-cgn-nat64-stateless)#address-family ipv4RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#tos 255RP/0/RP1/CPU0:(config-cgn-nat64-stless-afi)#showWed Sep 15 11:04:14.938 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv4tos 255The following example shows how to configure the 6rd tunnel type of service:
RP/0/RP1/CPU0:#configWed Sep 29 07:27:34.087 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#tos 25RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showWed Sep 29 07:28:30.381 UTCservice cgn cgn1service-type tunnel v6rd 6rd1tos 25Related Commands
traceroute (CGN)
The traceroute configures a range of ipv4 addresses that are to be used for mapping when a non-translatable ipv6 address is received. When the no form of this command is specified, there will be no pool of IPv4 addresses for mapping the non-translatable IPv6 source addresses.
traceroute translation address-pool <A.B.C.D/prefix IP subnet mask> algorithm <Hash | Random | TTL >
no traceroute translation
Syntax Description
Defaults
Ipv4 address/prefix for traceroute-pool
•
•
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This traceroute command will configure a range of ipv4 addresses that are to be used for mapping when a non-translatable ipv6 address is received. One of the addresses from this block will be mapped to the ipv6 address.
The following ipv4 addresses will not be allowed to be configured through this command:
1. 127.0.0.12. addresses from 224.0.0.0 onwards3. All zero address4. Broadcast addressThe value for prefix can be any value from 1 to 32. There will be only one such map per instance of stateless ipv4 to ipv6 service-type.
When there is no pool of IPv4 addresses to translate the non-translatable IPv6 source address, packets coming with non-translatable IPv6 source addresses will be dropped.
Task ID
Examples
The following example shows how to configure the address-pool:
RP/0/RP0/CPU0:#configSat Sep 18 00:52:30.424 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#traceroute translation address-pool 121.1.2.0/24RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#showSat Sep 18 01:01:55.117 UTCservice cgn cgn1service-type nat64 stateless xlat1traceroute translationaddress-pool 121.1.2.0/24The following example shows how to configure the random algorithm:
RP/0/RP0/CPU0:#configSat Sep 18 01:31:24.788 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#traceroute translation algorithm RandomRP/0/RP0/CPU0:(config-cgn-nat64-stateless)#showSat Sep 18 01:32:53.793 UTCservice cgn cgn1service-type nat64 stateless xlat1traceroute translationalgorithm RandomThe following example shows how to configure the hash algorithm:
RP/0/RP0/CPU0:#configSat Sep 18 01:31:24.788 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#traceroute translation algorithm HashRP/0/RP0/CPU0:(config-cgn-nat64-stateless)#showSat Sep 18 01:32:53.793 UTCservice cgn cgn1service-type nat64 stateless xlat1traceroute translationalgorithm HashThe following example shows how to configure the TTL algorithm:
RP/0/RP0/CPU0:#configSat Sep 18 01:36:18.370 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#traceroute translation algorithm TTLRP/0/RP0/CPU0:(config-cgn-nat64-stateless)#showSat Sep 18 01:37:42.283 UTCservice cgn cgn1service-type nat64 stateless xlat1traceroute translationalgorithm TTLRelated Commands
traffic-class (CGN)
Use the traffic-class command to configure the traffic class value to be used when translating a packet from ipv4 to ipv6. When the no form of this command is specified, the traffic-class value will be copied from ipv4 packet.
traffic-class <0-255>
no traffic-class <0-255>
Syntax Description
traffic-class
Traffic class to be set when translating from IPv4 to IPv6
<0-255>
Traffic class to be set
Defaults
There is no default behavior.
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows how to configure the CGN-NAT64 traffic class value:
RP/0/RP0/CPU0:#configFri Sep 17 19:48:58.089 UTCRP/0/RP0/CPU0:(config)#service cgn cgn1RP/0/RP0/CPU0:(config-cgn)#service-type nat64 stateless xlat1RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#ipv6-prefix 2010:db8:ff00::/40RP/0/RP0/CPU0:(config-cgn-nat64-stateless)#address-family ipv6RP/0/RP0/CPU0:(config-cgn-nat64-stless-afi)#interface ServiceApp 461RP/0/RP0/CPU0:(config-cgn-nat64-stless-afi)#traffic-class 20RP/0/RP0/CPU0:(config-cgn-nat64-stless-afi)#showFri Sep 17 19:53:00.277 UTCservice cgn cgn1service-type nat64 stateless xlat1address-family ipv6interface ServiceApp461traffic-class 20Related Commands
ttl (6rd)
Use the ttl command to configure the ipv4 tunnel time to live. The no form of this command disables the time to live.
ttl <value>
no ttl <value>
Syntax Description
Defaults
There is no default behavior.
Command Modes
TUNNEL-6RD
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows how to configure the 6rd tunnel time to live, ttl, value:
RP/0/RP1/CPU0:#configWed Sep 29 07:43:18.178 UTCRP/0/RP1/CPU0:(config)#service cgn cgn1RP/0/RP1/CPU0:(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#ttl 25RP/0/RP1/CPU0:(config-cgn-tunnel-6rd)#showWed Sep 29 07:44:57.026 UTCservice cgn cgn1service-type tunnel v6rd 6rd1ttl 25!Related Commands
ubit-reserved (CGN)
When the ubit-reserved command is enabled bits 64-71 in the IPv6 addresses are reserved. If no form of this command is specified, then bits 64..71 in the IPv6 address will not be reserved and may be used to store the IPv4 address octets as part of translation.
ubit-reserved
no ubit-reserved
Syntax Description
Defaults
There is no default behavior
Command Modes
CGN-NAT64
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
This is an NAT64 stateless translation command to be applied per instance of NAT64 stateless of a CGN instance. When this configuration is enabled bits 64-71 in the IPv6 addresses are reserved for purposes including U-Bit. These won't be used for translation purposes.
If no is specified, then bits 64..71 in the IPv6 address will not be reserved and may be used to store the IPv4 address octets as part of translation.
Task ID
