carrier grade ipv6 over integrated services module (ism)€¦ · carrier grade ipv6 over integrated...

Carrier Grade IPv6 over Integrated ServicesModule (ISM)

This module describes how to implement the Carrier Grade IPv6 (CGv6) over Integrated Services Module( ISM).

• Cisco Integrated Service Module, page 1

• Implementing NAT 44 over ISM, page 3

• Implementing NAT 64 over ISM, page 6

• CGv6 Applications, page 11

• Policy Functions, page 17

• External Logging, page 20

• Configuring CGv6 on Cisco IOS XR Software, page 21

• Configuring MAP-E, page 99

• Configuring MAP-T, page 115

• Configuring High Availability, page 153

• Configuration Examples for Implementing the Carrier Grade NAT, page 155

Cisco Integrated Service ModuleCisco Integrated Service Module (ISM) is a physical line interface module (PLIM) that provides a highlyscalable modular services delivery platform for delivering multiple types of services. ISM is designed todeliver flexible and highly scalable service integration that allows operational efficiency, service flexibility,and faster time to market. The module offers the architectural advantages of integration with the routingsystem.

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

Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x 1

• ASR 9000 with IOS XR

◦High-capacity, carrier-class SP platform with Cisco IOS XR Software

◦Leverages XR infrastructure to divert packets to ISM

◦Uniform, integrated configuration and management

• Integrated Service Module

◦Flexible Linux-based development & test environment

◦Supports required CGv6

◦First IPv6 Transition Strategy

• Integrated Service Module

◦Hardware

◦CGv6 function residing on ISM

◦Intel x86 with 12 CPU cores

◦Software

◦IOS-XR on LC, Linux on Intel CPUs

◦Integrated configuration and management through Cisco IOS XR Software

• Service Virtual Interface (SVI)

◦Two types of Service Virtual Interfaces are used in ISM

◦ServiceInfra SVI

◦ServiceApp SVI

There can be only one ServiceInfra SVI per ISM Slot. This is used for the management plane and is requiredto bring up ISM. This is of local significance within the chassis.

Access lists are not supported on service virtual interfaces.Note

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

Support for Multiple ISM Line CardsCisco IOS XR Software Release 4.2.3 and onwards supports a maximum of six ISM line cards in each CiscoASR 9000 Series Aggregation Services Router chassis. For applications such as NAT44 and DS-Lite, theconfiguration can be independently applied to each ISM line card.

For NAT-44, a maximum of ten million sessions are supported by each ISM line card.

Cisco ASR 9000 Series Aggregation Services Router CGv6 Configuration Guide, Release 5.2.x2

Carrier Grade IPv6 over Integrated Services Module (ISM)Support for Multiple ISM Line Cards

For DS-Lite, a maximum of twenty million sessions are supported by each ISM line card.

No additional configuration is required to support multiple ISM line cards.Note

CGN as Default Application on ISMISM supports CGN as the default application.

Configuring CGN as Default Application on ISMTo configure CGN as the default application, perform these steps.

SUMMARY STEPS

1. Install CGN services.pie.2. Configure the CGN role using hw-module service cgn location <node_id> command.3. Load the CGN Linux image as the default image instead of CDS-IS.4. Reload ISM.

DETAILED STEPS

Step 1 Install CGN services.pie.Step 2 Configure the CGN role using hw-module service cgn location <node_id> command.Step 3 Load the CGN Linux image as the default image instead of CDS-IS.Step 4 Reload ISM.

Implementing NAT 44 over ISMThese sections provide the information about implementation of NAT.

The following figure illustrates the implementation of NAT 44 over ISM


Carrier Grade IPv6 over Integrated Services Module (ISM)CGN as Default Application on ISM

The components of this illustration are as follows:

• Private IP4 subscribers: It denotes a private network.

• Interface/VLAN: It denotes a designated interface or VLAN which is associated with the VRF.

• Inside VRF: It denotes the VRF that handles packets coming from the subscriber network. It is knownas inside VRF as it forwards packets from the private network.

• App SVI: It denotes an application interface that forwards the data packet to and from the ISM. The datapacket may be sent from another line card through a backplane. Because the ISM card does not have aphysical interface, the APP SVI acts as a logical entry into it.

The inside VRF is bound to an App SVI. There are 2 App SVIs required; one for the inside VRF andthe other one for the outside VRF. Each App SVI pair will be associated with a unique "inside VRF"and a unique public IP address pool. The VRF consists of a static route for forwarding packets to AppSVI1.

• Outside VRF: It denotes the VRF that handles packets going out to the public network. It is known asoutside VRF as it forwards packets from the public network.

• Public IPV4: It denotes a public network.

The following figure illustrates the path of the data packet from a private network to a public network in aNAT implementation.

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


Carrier Grade IPv6 over Integrated Services Module (ISM)Implementing NAT 44 over ISM

1 In the network shown in this figure, the packet travels from the host A (having the IP address 10.222.5.55)in the private network to host B (having the IP address 5.5.5.2) in the public network. The private addresshas to be mapped to the public address by NAT44 that is implemented in ISM.

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

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

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

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

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

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

The following figure illustrates the path of the packet coming from the public network to the private network.

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



1 In the network shown in this figure, the packet travels from the host A (having the IP address 10.222.5.55)in the public network to host B (having the IP address 5.5.5.2) in the private network. The public addresshas to be mapped to the private address by NAT44 that is implemented in ISM.

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

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

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

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

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


Implementing NAT 64 over ISMThis section explains how NAT64 is implemented over ISM. The figure illustrates the implementation ofNAT64 over ISM.

The components of this implementation are as follows:



• Private IP6 subscribers – It denotes a private network.

• Interface/VLAN- It denotes a designated interface or VLAN which is associated with the VRF.

• Inside VRF – It denotes the VRF that handles packets coming from the subscriber network. It is knownas inside VRF as it forwards packets from the private network.

• App SVI- It denotes an application interface that forwards the data packet to and from the ISM. Thedata packet may be sent from another line card through a backplane. Because the ISM card does nothave a physical interface, the APP SVI acts as a logical entry into it.

The inside VRF is bound to an App SVI. There are 2 App SVIs required; one for the inside VRF andthe other one for the outside VRF. Each App SVI pair will be associated with a unique "inside VRF"and a unique public IP address pool. The VRF consists of a static route for forwarding packets to AppSVI1.

• Outside VRF- It denotes the VRF that handles packets going out to the public network. It is known asoutside VRF as it forwards packets from the public network.

• Public IPV4- It denotes a public network.

The following figure illustrates the path of the data packet from a private network to a public network in aNAT64 implementation.

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

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




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

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

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

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


The following figure illustrates the path of the packet coming from the public network to the private network.

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

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




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

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

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

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


Table 1: Supported Interfaces and Forwarding Features on CGv6

5.3.x5.2.x5.1.x4.3.x

Egress Interfaces

YesYesYesYesPhysical Interface

YesYesYesYesVLANSubinterface

YesYesYesYesBundle Interface

YesYesYesYesBundle Subinterface

NoNoNoNoBVI Interface

YesYesYesNoBNGIP-Subinterface/PPPoE

NoNoNoNoEthernetAttachmentCircuit orPseudowire

NoNoNoNoGRE Tunnel

L3 Unicast Forwarding Features

YesYesYesYesBasic IPv4 IGPForwarding

YesYesYesYesBGP Traffic

YesYesYesYesForwarding in VRF

YesYesYesYesRecursive Routes

NoNoNoNouRPF



5.3.x5.2.x5.1.x4.3.x

NoNoNoNoBGP-PA

MPLS and Fast Reroute (FRR) Support

Note: The ISM card does not generate label for packets. It only processes unlabeled packets.

YesYesYesNoMPLS-TE Paths

YesYesYesYesBasic Labeled Path

YesYesYesNoMPLS-TE Tunnel

NoNoNoNoMPLS-TP Tunnel

YesYesYesNoTE-FRR

NoNoNoNoIP-FRR

NoNoNoNoLDP-FRR orLFA-FRR

Multicast

NoNoNoNoIP Multicast

NoNoNoNoMVPN

NoNoNoNoLabel SwitchedMulticast

ServiceApp Interfaces

YesYesYesYesABF to ServiceAppInterface

NoNoNoNoABF fromServiceAppInterface

NoNoNoNoACLon ServiceAppInterface

NoNoNoNoQoS on ServiceAppInterface

NoNoNoNoLawful Intercept(LI) on Service AppInterface



5.3.x5.2.x5.1.x4.3.x

NoNoNoNoIPv4Enable/Disable(Per Interface)

NoNoNoNoMPLSEnable/Disable (PerInterface)

NoNoNoNoMTU Setting (PerInterface)

YesYesPartial

Per-interfaceper-protocolpacket/byte count issupported.

Partial

Per-interfaceper-protocolpacket/byte count issupported.

Statistics onServiceAppInterface

NoNoNoNoPer-Label/TunnelStatistics

Note • The table refers to packet handling after CGv6 processing (from ingress to egress).

• The CGv6 application processes only L3 unicast traffic. Other traffic types such as L2 and L3multicast are not supported.

• The forwarding features that are supported are only those where traffic is injected from the CGv6application as an IPv4 or IPv6 packet.

CGv6 ApplicationsThese applications are deployed on the ISM line card.

Network Address Translation (NAT44)Network Address Translation (NAT44) or Carrier Grade Network Address Translation (CGN) is a large scaleNAT that is capable of providing private IPv4 to public IPv4 address translation in the order of millions oftranslations to support a large number of subscribers, and at least 10 Gbps full-duplex bandwidth throughput.

CGN is a workable solution to the IPv4 address completion problem, and offers a way for service providersubscribers and content providers to implement a seamless transition to IPv6. CGN employs network addressand port translation (NAPT) methods to aggregate many private IP addresses into fewer public IPv4 addresses.For example, a single public IPv4 address with a pool of 32 K port numbers supports 320 individual privateIP subscribers assuming each subscriber requires 100 ports. For example, each TCP connection needs oneport number.


Carrier Grade IPv6 over Integrated Services Module (ISM)CGv6 Applications

A Network Address Translation (NAT) box is positioned between private and public IP networks that areaddressed with non-global private addresses and a public IP addresses respectively. A NAT performs the taskof mapping one or many private (or internal) IP addresses into one public IP address by employing bothnetwork address and port translation (NAPT) techniques. The mappings, otherwise referred to as bindings,are typically created when a private IPv4 host located behind the NAT initiates a connection (for example,TCP SYN) with a public IPv4 host. The NAT intercepts the packet to perform these functions:

• Rewrites the private IP host source address and port values with its own IP source address and portvalues

• Stores the private-to-public binding information in a table and sends the packet. When the public IP hostreturns a packet, it is addressed to the NAT. The stored binding information is used to replace the IPdestination address and port values with the private IP host address and port values.

Traditionally, NAT boxes are deployed in the residential home gateway (HGW) to translate multiple privateIP addresses. The NAT boxes are configured on multiple devices inside the home to a single public IP address,which are configured and provisioned on the HGW by the service provider. In enterprise scenarios, you canuse the NAT functions combined with the firewall to offer security protection for corporate resources andallow for provider-independent IPv4 addresses. NATs have made it easier for private IP home networks toflourish independently from service provider IP address provisioning. Enterprises can permanently employprivate IP addressing for Intranet connectivity while relying on a few NAT boxes, and public IPv4 addressesfor external public Internet connectivity. NAT boxes in conjunction with classic methods such as ClasslessInter-Domain Routing (CIDR) have slowed public IPv4 address consumption.

Network Address and Port MappingNetwork address and port mapping can be reused to map new sessions to external endpoints after establishinga first mapping between an internal address and port to an external address. These NAT mapping definitionsare defined from RFC 4787:

• Endpoint-independent mapping—Reuses the port mapping for subsequent packets that are sent fromthe same internal IP address and port to any external IP address and port.

• Address-dependent mapping—Reuses the port mapping for subsequent packets that are sent from thesame internal IP address and port to the same external IP address, regardless of the external port.

CGN on ISM implements Endpoint-Independent Mapping.Note

Translation FilteringRFC 4787 provides translation filtering behaviors for NATs. These options are used by NAT to filter packetsoriginating from specific external endpoints:

• Endpoint-independent filtering—Filters out only packets that are not destined to the internal addressand port regardless of the external IP address and port source.

• Address-dependent filtering—Filters out packets that are not destined to the internal address. Inaddition, NAT filters out packets that are destined for the internal endpoint.


Carrier Grade IPv6 over Integrated Services Module (ISM)Network Address Translation (NAT44)

• Address and port-dependent filtering—Filters out packets that are not destined to the internal address.In addition, NAT filets out packets that are destined for the internal endpoint if the packets were notsent previously.

Dual Stack LiteThe Dual Stack Lite (DS-Lite) feature enables legacy IPv4 hosts and server communication over both IPv4and IPv6 networks. Also, IPv4 hosts may need to access IPv4 internet over an IPv6 access network. The IPv4hosts will have private addresses which need to have network address translation (NAT) completed beforereaching the IPv4 internet. The Dual Stack Lite application has these components:

• Basic Bridging BroadBand Element (B4): This is a Customer Premises Equipment (CPE) router thatis attached to the end hosts. The IPv4 packets entering B4 are encapsulated using a IPv6 tunnel and sentto the Address Family Transition Router (AFTR).

• Address Family Transition Router(AFTR): This is the router that terminates the tunnel from the B4.It decapsulates the tunneled IPv4 packet, translates the network address and routes to the IPv4 network.In the reverse direction, IPv4 packets coming from the internet are reverse network address translatedand the resultant IPv4 packets are sent the B4 using a IPv6 tunnel.

The Dual Stack Lite feature helps in these functions:

1 Tunnelling IPv4 packets from CE devices over IPv6 tunnels to the CGSE blade.

2 Decapsulating the IPv4 packet and sending the decapsulated content to the IPv4 internet after completingnetwork address translation.

3 In the reverse direction completing reverse-network address translation and then tunnelling them overIPv6 tunnels to the CPE device.

IPv6 traffic from the CPE device is natively forwarded.

VSM scale numbers supported in Dual Stack Lite

Dual Stack Lite supports the following VSM scale number:

Value per ASR9K Chassiswith VSM

Value per VSMParameter Name

80 MillionsDS-Lite Sessions

Scalability and Performance of DS Lite• Supports a total of 60 million translations.

• Number of unique users behind B4 router, basically IPv6 and IPv4 Source tuple, can scale to 1 million.

• There is no real limit to the number of B4 routers and their associated tunnels connecting to the AFTR,except the session limit, which is 20 million B4 routers (assuming each router has only one session). Inreality, a maximum of 1 million B4 routers can connect to an AFTR at any given time.

• The performance of DS-Lite traffic, combined IPv4 and IPv6, is 39 Gbps.


Carrier Grade IPv6 over Integrated Services Module (ISM)Dual Stack Lite

Stateful NAT64The Stateful NAT64 (Network Address Translation 64) feature provides a translationmechanism that translatesIPv6 packets into IPv4 packets and vice versa. NAT64 allows IPv6-only clients to contact IPv4 servers usingunicast UDP, TCP, or ICMP. The public IPv4 address can be shared with several IPv6-only clients. NAT64supports communication between:

• IPv6 Network and Public IPv4 Internet

• Public IPv6 Internet and IPv4 Network

NAT64 is implemented on the Cisco CRS router CGSE platform. CGSE (Carrier Grade Service Engine) hasfour octeons and supports 20 Gbps full duplex traffic. It works on Linux operating system and traffic intoCGSE is forwarded using serviceApp interfaces. SVIs (Service Virtual Interfaces) are configured to enabletraffic to flow in and out of CGSE .

Each NAT64 instance configured is associated with two serviceApps for the following purposes:

• One serviceApp is used to carry traffic from IPv6 side

• Another serviceApp is used to carry traffic from IPv4 side of the NAT64.

NAT64 instance parameters are configured using the CGNCLI. The NAT64 application in the octeons updatesits NAT64 instance and serviceApp databases, which are used to perform the translation between IPv6 andIPv4 and vice versa.

Active CGN instance configuration is replicated in the standby CGN instance through the XR control plane.Translations that are established on the Active CGN instance are exported to the Standby CGN instance asthe failure of the Active CGN affects the service until translations are re-established through normal packetflow. Service interruption is moderate for the given fault detection time and translation learning rate in termsof seconds or tens of seconds for a large translation database.

Prefix FormatA set of bits at the start of an IPv6 address is called the format prefix. Prefix length is a decimal value thatspecifies the number of the left-most contiguous bits of an address.

When packets flow from the IPv6 to the IPv4 direction, the IPv4 host address is derived from the destinationIP address of the IPv6 packet that uses the prefix length.When packets flow from the IPv4 to the IPv6 direction,the IPv6 host address is constructed using the stateful prefix.

According to the IETF address format, a u-bit (bit 70) defined in the IPv6 architecture should be set to zero.The reserved octet, also called u-octet, is reserved for compatibility with the host identifier format defined inthe IPv6 addressing architecture. When constructing an IPv6 packet, the translator has to make sure that theu-bits are not tampered, and are set to the value suggested by RFC 2373. The suffix will be set to all zeros bythe translator. IETF recommends that the 8 bits of the u-octet (bit range 64-71) be set to zero.

Well Known Prefix (WKP)

Well Known Prefix (WKP) 64:FF9B::/96 is supported for Stateful NAT64. During stateful translation, if nostateful prefix is configured (either on the interface or globally), the WKP prefix is used to translate the IPv4host addresses.


Carrier Grade IPv6 over Integrated Services Module (ISM)Stateful NAT64

Stateful IPv4-to-IPv6 Packet FlowThe packet flow of IPv4-initiated packets for Stateful NAT64:

• The destination address is routed to a NAT Virtual Interface (NVI). A virtual interface is created whenStateful NAT64 is configured. For Stateful NAT64 translation to work, all packets must get routed tothe NVI. When you configure an address pool, a route is automatically added to all IPv4 addresses inthe pool. This route automatically points to the NVI.

• The IPv4-initiated packet hits static or dynamic binding. Dynamic address bindings are created by theStateful NAT64 translator when you configure dynamic Stateful NAT64. A binding is dynamicallycreated between an IPv6 and an IPv4 address pool. Dynamic binding is triggered by the IPv6-to-IPv4traffic and the address is dynamically allocated. Based on your configuration, you can have static ordynamic binding.

• The IPv4-initiated packet is protocol-translated and the destination IP address of the packet is set to IPv6based on static or dynamic binding. The Stateful NAT64 translator translates the source IP address toIPv6 by using the Stateful NAT64 prefix (if a stateful prefix is configured) or the Well Known Prefix(WKP) (if a stateful prefix is not configured).

• A session is created based on the translation information.

All subsequent IPv4-initiated packets are translated based on the previously created session.

Stateful IPv6-initiated packet flow:• The first IPv6 packet is routed to the NAT Virtual Interface (NVI) based on the automatic routing setupthat is configured for the stateful prefix. Stateful NAT64 performs a series of lookups to determinewhether the IPv6 packet matches any of the configured mappings based on an access control list (ACL)lookup. Based on the mapping, an IPv4 address (and port) is associated with the IPv6 destination address.The IPv6 packet is translated and the IPv4 packet is formed by using these methods:

◦Extracting the destination IPv4 address by stripping the prefix from the IPv6 address. The sourceaddress is replaced by the allocated IPv4 address (and port).

◦Translating the rest of the fields from IPv6-to-IPv4 to form a valid IPv4 packet.

• Creating a new NAT64 translation in the session database and in the bind database. The pool and portdatabases are updated depending on the configuration. The return traffic and the subsequent traffic ofthe IPv6 packet flow will use this session database entry for translation.

Static port forwarding is not supported over StatefulNAT64 on ISM.Note

IP Packet FilteringStateful NAT64 filters IPv6 and IPv4 packets. All IPv6 packets that are transmitted into the stateful translatorare filtered because statefully translated IPv6 packets consume resources in the translator. These packetsconsume processor resources for packet processing, memory resources (always session memory) for static


Carrier Grade IPv6 over Integrated Services Module (ISM)Stateful NAT64

configuration, IPv4 address resources for dynamic configuration, and IPv4 address and port resources for PortAddress Translation (PAT).

Stateful NAT64 utilizes configured access control lists (ACLs) and prefix lists to filter IPv6-initiated trafficflows that are allowed to create the NAT64 state. Filtering of IPv6 packets is done in the IPv6-to-IPv4 directionbecause dynamic allocation of mapping between an IPv6 host and an IPv4 address can be done only in thisdirection.

Stateful NAT64 supports endpoint-dependent filtering for the IPv4-to-IPv6 packet flowwith PAT configuration.In a Stateful NAT64 PAT configuration, the packet flow originates from the IPv6 realm and creates the stateinformation in NAT64 state tables. Packets from the IPv4 side that do not have a previously created state aredropped. Endpoint-independent filtering is supported with static NAT and non-PAT configurations.

Mapping of Address and Port-Translation ModeMapping of Address and Port-Translation Mode (MAP-T) is a CGN solution that enables IPv4-only clientsto communicate with IPv6-only resources using address and packet translation. MAP-T is also referred to asDual IVI (dIVI) or Stateless NAT46. This enables a service provider to offer IPv4 services to IPv6 enabled(customer) sites to which it provides customer premise equipment (CPE). This approach utilizes stateless IPv4to IPv6 translation (that is NAT64) to transit IPv6-enabled network infrastructure. The provider access networkcan now be on IPv6, while customers use IPv6 and IPv4 services simultaneously. MAP-T keeps the statefulNAT44 on CPE, as usual, to handle IPv4 address exhaustion, in addition to stateless NAT64 on CPE andBorder Router.

MAP-T is attractive to those SPs who have deployed, or are planning to deploy IPv6 end-to-end services, andwant to manage IPv4 address exhaustion with utmost predictability.

MAP-T is a preferred alternate to DS-Lite in a sevice provider network when there is no tunneling needed.

MAP-T is offered in stateless mode only.Note

IPv6 Rapid DeploymentIPv6 Rapid Deployment (6RD) is a mechanism that allows service providers to provide a unicast IPv6 serviceto customers over their IPv4 network.

6RD Definitions• 6RD CE /RG/CPE: The 6rd "Customer Edge" router that sits between an IPv6-enabled site and anIPv4-enabled SP network. In the context of residential broadband deployment, this is referred to as theResidential Gateway (RG) or Customer Premises Equipment (CPE) or Internet Gateway Device (IGD).This router has a 6rd tunnel interface acting as an endpoint for the IPv6 in IPv4 encapsulation andforwarding, with at least one 6rd CE LAN side interface and 6rd CE WAN side interface, respectively.

• 6RDBorder Relay (BR): A 6rd-enabled Border Relay router located at the service provider’s premises.The 6rd BR router has at least one IPv4 interface, a 6rd tunnel interface for multi-point tunneling, andat least one IPv6 interface that is reachable through the IPv6 Internet or IPv6-enabled portion of the SPnetwork. A router running IOS can also be a 6RD BR.


Carrier Grade IPv6 over Integrated Services Module (ISM)Mapping of Address and Port-Translation Mode

• 6RD Delegated Prefix: The IPv6 prefix determined by the 6rd CE device for use by hosts within thecustomer site.

• 6RD Prefix (SP Prefix) : An IPv6 prefix selected by the service provider for use by a 6rd domain. Thereis exactly one 6rd prefix for a given 6rd domain.

• CE LAN side : The functionality of a 6rd CE that serves the Local Area Network (LAN) orcustomer-facing side of the CE. The CE LAN side interface is fully IPv6 enabled.

• CEWAN side : The functionality of a 6rd CE that serves the Wide Area Network (WAN) or ServiceProvider- facing side of the CE. The CE WAN side is IPv4 only.

• BR IPv4 address : The IPv4 address of the 6rd Border Relay for a given 6rd domain. This IPv4 addressis used by the CE to send packets to a BR in order to reach IPv6 destinations outside of the 6rd domain.

• CE IPv4 address : The IPv4 address given to the CE as part of normal IPv4 Internet access (configuredthrough DHCP, PPP, or otherwise). This address may be global or private within the 6rd domain. Thisaddress is used by a 6rd CE to create the 6rd delegated prefix, as well as to send and receiveIPv4-encapsulated IPv6 packets.

Mapping of Address and Port-Encapsulation ModeMapping of Address and Port-EncapsulationMode (MAP-E) is a CGN solution that allows a service providerto enable IPv4 services at IPv6 (customer) sites to which it provides Customer Premise Equipment (CPE).This approach utilizes stateless IPv4-in-IPv6 encapsulation to transit IPv6-enabled network infrastructure.The encapsulation must be supported by the CPE and MAP-E Gateway/Border Relay, which removes theIPv6 encapsulation from IPv4 packets while forwarding them to the Internet. The provider access networkcan now be on IPv6, while customers see IPv6 and IPv4 service simultaneously.

MAP-E also helps manage IPv4 address exhaustion by keeping the stateful NAT44 on CPE. MAP-E is notsupported on any of the VRF interfaces, that is, either IPv4 or IPv6, whereas Map-T is supported with VRFinterfaces along with an SMU.

Policy Functions

Application Level GatewayTheApplication Level Gateway (ALG) deals with the applications that are embedded in the IP address payload.Active File Transfer Protocol (FTP), Point-to-Point Tunneling Protocol (PPTP), and Real Time StreamingProtocol (RTSP) are supported.

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


Carrier Grade IPv6 over Integrated Services Module (ISM)Mapping of Address and Port-Encapsulation Mode

RTSP-ALGCGN supports the Real Time Streaming Protocol (RTSP), an application-level protocol for control over thedelivery of data with real-time properties. RTSP provides an extensible framework to enable controlled,on-demand delivery of real-time data, such as audio and video. Sources of data can include both live datafeeds and stored clips.

PPTP-ALGPPTP is a network protocol that enables secure transfer of data from a remote client to a private enterpriseserver by creating a Virtual Private Network (VPN). It is used to provide IP security at the network layer.PPTP uses a control channel over TCP and a GRE tunnel operating to encapsulate PPP packets.

PPTP-ALG is a CGN solution that allows traffic from all clients through a single PPTP tunnel.

A PPTP tunnel is instantiated on the TCP port. This TCP connection is then used to initiate and manage asecond GRE tunnel to the same peer.

PPTP uses an access controller and network server to establish a connection.

PPTP Access Controller (PAC)

A device attached to one or more PSTN or ISDN lines capable of PPP operation and handling the PPTPprotocol. It terminates the PPTP tunnel and provides VPN connectivity to a remote client.

PPTP Network Server (PNS)

A device which provides the interface between the Point-to-Point Protocol (encapsulated in the PPTP protocol)and a LAN or WAN. The PNS uses the PPTP protocol to support tunneling between a PPTP PAC and thePNS. It requests to establish a VPN connectivity using PPTP tunnel.

Control Connection

A control connection is established between a PAC and a PNS for TCP.

Tunnel

A tunnel carries GRE encapsulated PPP datagrams between a PAC and a PNS

Active FTP, PPTP ALG, and RTSP ALG are supported on NAT44 applications. Active FTP and RTSPALG are supported on DS-Lite applications.

Note

TCP Maximum Segment Size AdjustmentWhen a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.

Static Port ForwardingStatic port forwarding helps in associating a private IP address and port with a statically allocated public IPand port. After you have configured static port forwarding, this association remains intact and does not get


Carrier Grade IPv6 over Integrated Services Module (ISM)TCP Maximum Segment Size Adjustment

removed due to timeouts until the CGSE is rebooted. In case of redundant CGSE cards, it remains intact untilboth of the CGSEs are reloaded together or the router is reloaded. There are remote chances that after a reboot,this association might change. This feature helps in cases where server applications running on the privatenetwork needs access from public internet.

High AvailabilityHigh Availability (HA) or 1:1 redundancy enables network-wide protection by providing fast recovery fromfaults that may occur in any part of the network. With Cisco High Availability on the module, the networkhardware and software work together and enable rapid recovery from disruption, to ensure fault transparencyto users and network applications. It provides continuous access to applications, data, and content anywhere,anytime by addressing potential causes of downtime with functionality, design, and best practices.

HA supports:

• 1:1 active or standby redundancy infrastructure for the services running on the module

◦Intra-chassis redundancy

◦Cold standby redundancy

• Replication of CGN-related configuration into a standby card

Before upgrading or downgrading the CGv6 OVA package on the Active VSM card inHA mode, perform a graceful shift of the traffic from Active VSM to Standby VSM.This will ensure that the CGN-related configuration is replicated into a standby card.For more information refer Upgrading CGv6 OVA Package.

Note

• Failure detection

◦Data path - Channel through which CGV6 application data packets traverse

◦CPU health monitoring

◦Control path

◦Crashed processes

The following commands are supported for failure detection:

◦Data PathRP/0/RP0/CPU0:router(config)# service-cgv6-ha location location-name datapath-testRP/0/RP0/CPU0:router(config)# service-cgv6-ha location location-name datapath-testdisable

By default, failure detection for data path is not triggered unless the above command isconfigured.

Note


Carrier Grade IPv6 over Integrated Services Module (ISM)High Availability

b_cgnat_cg52xasr9k_chapter_011.pdf#unique_18

The service-cgv6-ha location location-name datapath-test disable configurationdisables the heartbeat packets (health check packets) flowing in VSM. By default, thesepackets are flowing. You can disable these packets when required.

Note

• Failure reporting and recovery

◦If redundant module is configured, then switch-over the stand by module to active and reload theactive module.

◦If redundant module is not configured, then reload the module. This comes up again as an activemodule.

Redundancy Switchover Using CLI

You can trigger the switchover the failover by running the following the commands to an active slot and viceversa. :

Use the following command to switchover the failover to a preferred active slot.RP/0/RP0/CPU0:router(config)# service redundancy failover service-type all preferred-active<preferred-active slot>Use the following command to revert the failover to a preferred active slot.RP/0/RP0/CPU0:router(config)# service redundancy revert service-type all preferred-active<preferred-active slot>

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

Netflow v9 SupportThe NAT44 and DS Lite features support Netflow for logging of the translation records. Logging of thetranslation records can be mandated by for Lawful Intercept. The Netflow uses binary format and hencerequires software to parse and present the translation records.

Syslog SupportThe NAT44, Stateful NAT64, and DS Lite features support Netflow for logging of the translation records.Logging of the translation records can be mandated by for Lawful Intercept. The Netflow uses binary formatand hence requires software to parse and present the translation records.

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


Carrier Grade IPv6 over Integrated Services Module (ISM)External Logging

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

Session-logging and bulk port allocation are mutually exclusive.Note

Destination-Based LoggingDestination-Based Logging (DBL) includes destination IPv4 address and port number in the Netflow createand delete records used by NAT44, Stateful NAT64, and DS-Lite applications. It is also known asSession-Logging.

Session-Logging and Bulk Port Allocation are mutually exclusive.Note

Configuring CGv6 on Cisco IOS XR SoftwareThese configuration tasks are required to implement CGv6 on Cisco IOS XR software.

Installing Carrier Grade IPv6 on ISMThis section provides instructions on installing CGv6 on the ISM line card, removing CGv6 on the ISM linecard, and reinstalling the CDS TV application support.

Hardware

ISM hardware in chassis

Software

• asr9k-mini-p.vm or asr9k-mini-px.vm

• asr9k-services-p.pie or asr9k-services-px.pie

• asr9k-fpd-p.pie or asr9k-fpd-px.pie

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


Carrier Grade IPv6 over Integrated Services Module (ISM)Bulk Port Allocation

SUMMARY STEPS

1. Load the fpd pie.2. Run the show hw-module fpd location <> command in admin mode.3. Upgrade the identified FPGAs using the relevant commands:4. If one or more FPGAs were upgraded, reload the ISM card after all the upgrade operation completes

successfully.5. After the ISM card comes up, check for the FPGA version. This can be done using the following command

from the admin mode.

DETAILED STEPS

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

Example:RP/0/RP0/CPU0:#adminRP/0/RSP1/CPU0:LHOTSE#show hw-module fpd location 0/1/CPU0===================================== ================================================

Existing Field Programmable Devices================================================HW Current SW Upg/

Location Card Type Version Type Subtype Inst Version Dng?============ ======================== ======= ==== ======= ==== =========== ==== =====--------------------------------------------------------------------------------------0/1/CPU0 A9K-ISM-100 1.0 lc fpga1 0 0.29 No

1.0 lc cbc 0 18.04 Yes1.0 lc cpld1 0 0.01 No1.0 lc fpga7 0 0.17 No1.0 lc cpld3 0 0.16 No1.0 lc fpga2 0 0.01 Yes

--------------------------------------------------------------------------------------If one or more FPD needs an upgrade (can be identified from the Upg/Dng column in the output) then this can beaccomplished using the following steps.

Step 3 Upgrade the identified FPGAs using the relevant commands:upgrade hw-module fpd fpga1 location <>upgrade hw-module fpd cbc location <>upgrade hw-module fpd cpld1 location <>upgrade hw-module fpd fpga7 location <>upgrade hw-module fpd cpld3 location <>upgrade hw-module fpd fpga2 location <>To upgrade all FPGA using a single command, type:upgrade hw-module fpd all location <>

Step 4 If one or more FPGAs were upgraded, reload the ISM card after all the upgrade operation completes successfully.hw-module location <> reload

Step 5 After the ISM card comes up, check for the FPGA version. This can be done using the following command from theadmin mode.show hw-module fpd location <>


Carrier Grade IPv6 over Integrated Services Module (ISM)Installing Carrier Grade IPv6 on ISM

Accessing CPU consoles on ISM CardThis output shows ISM card in slot1:RP/0/RSP0/CPU0 #show platform0/RSP0/CPU0 A9K-RSP-4G(Active) IOS XR RUN PWR,NSHUT,MON0/1/CPU0 A9K-ISM-100(LCP) IOS XR RUN PWR,NSHUT,MON0/1/CPU1 A9K-ISM-100(SE) SEOS-READYTo access LC CPU console:RP/0/RSP0/CPU0#run attach 0/1/CPU0#To return to RSP console:#exitTo access X86 CPU console:RP/0/RSP0/CPU0:CRANE#run attachCon 0/0/cpu1 115200attachCon: Starting console session to node 0/0/cpu1attachCon: To quit console session type 'detach'Current Baud 115200Setting Baud to 115200

localhost.localdomain login: rootPassword: rootroot[root@localhost ~]#To return to RSP console:[root@localhost]# detach

Installing CGv6 Application on ISM Running for Cisco IOS XR Software Release 4.2.0If the card is in CDS-IS mode, then it must be converted to CDS-TV before installing CGv6. For installationinstructions, see the Cisco ASR 9000 Series Aggregation Services Router ISM Line Card Installation Guide.

With kernel.rpm, the "kernel.rpm" or "kernel-4.2.0.rpm" file is referred and with "ism_infra.tgz", the"ism_infra.tgz" or "ism_infra-4.2.0.tgz" file is referred.

Note



SUMMARY STEPS

1. Manually remove the non-CGv6 (CDS TV) configuration.2. Install the Cisco IOS XR Software Release 4.2.0 image on the ASR 9000 router.3. To handle version incompatibility between APIs of Cisco IOSXR and Linux software, run these commands

as soon as the ISM LCP is in IOS XR RUN state.4. Extract the ism_infra.tgz and kernel.rpm image from the tar file (available in the Download Software page

in Cisco.com) and copy the content to the disk on the RSP console.5. Copy kernel.rpm and ism_infra.tgz to X86 location.6. Install the images on X86:7. Run the following Cisco IOS XR Software Release 4.2.0 commands in admin mode, on RSP to install the

Services PIE:8. Run the following Cisco IOS XR Software Release 4.2.0 commands on the RSP to set the service role as

cgn.9. Revert the changes made in Step 310. Reload the ISM line card.11. Wait for the card to return to SEOS-READY and proceed with ServiceInfra interface configuration.

DETAILED STEPS

Step 1 Manually remove the non-CGv6 (CDS TV) configuration.Step 2 Install the Cisco IOS XR Software Release 4.2.0 image on the ASR 9000 router.Step 3 To handle version incompatibility between APIs of Cisco IOS XR and Linux software, run these commands as soon as

the ISM LCP is in IOS XR RUN state.RP/0/RSP0/CPU0#proc mandatory OFF fib_mgr location <ism_node_location>RP/0/RSP0/CPU0#proc SHUTDOWN fib_mgr location <ism_node_location>RP/0/RP0/CPU0:#adminRP/0/RSP0/CPU0(admin)#debug sim reload-disable location<ism_node_location>

Any delay may result in card reload due to APImismatch.

Caution

Step 4 Extract the ism_infra.tgz and kernel.rpm image from the tar file (available in the Download Software page in Cisco.com)and copy the content to the disk on the RSP console.RP/0/RSP0/CPU0#copy tftp://<tftp_addr><image_location>/ism_infra.tgz disk0:/RP/0/RSP0/CPU0#copy tftp://<tftp_addr><image_location>/kernel.rpm disk0:/

Step 5 Copy kernel.rpm and ism_infra.tgz to X86 location.

1 Log into X86 CPU console and start the se_mbox_server process:[root@localhost]# se_mbox_server -d

2 Log into ISM LC CPU and upload the images to X86:#avsm_se_upload /disk0:/kernel.rpm#avsm_se_upload /disk0:/ism_infra.tgz



3 After successful upload, the images should be available under /tmp directory in the X86 CPU.

Step 6 Install the images on X86:[root@localhost /] cd /tmp[root@localhost tmp]# rpm -i --force kernel.rpm[root@localhost tmp]# avsm_install ism_infra.tgz

Step 7 Run the following Cisco IOS XR Software Release 4.2.0 commands in admin mode, on RSP to install the Services PIE:RP/0/RSP0/CPU0#admin(admin)#install add tftp://<tftp_addr>/<image_location>/asr9k-services-p.pie synchronous activate. . . . . . . . . . .(admin)#exit

Step 8 Run the following Cisco IOS XR Software Release 4.2.0 commands on the RSP to set the service role as cgn.RP/0/RSP0/CPU0#config(config)#hw-module service cgn location <ism_node_location>(config)#commit(config)#exit

Step 9 Revert the changes made in Step 3RP/0/RSP0/CPU0#proc mandatory ON fib_mgr location <ism_node_location>RP/0/RSP0/CPU0#proc START fib_mgr location <ism_node_location>RP/0/RP0/CPU0:#adminRP/0/RSP0/CPU0:(admin)#no debug sim reload-disable location <ism_node_location>

Step 10 Reload the ISM line card.RP/0/RSP0/CPU0#hw-module location <ism_node_location> reload

Step 11 Wait for the card to return to SEOS-READY and proceed with ServiceInfra interface configuration.

Installing CGv6 Application on ISM for Cisco IOS XR Software Release 4.2.1 and laterThe CGv6 application can be installed on an ISM line card directly without changing fromCDS-IS to CDS-TVand then CGv6.

SUMMARY STEPS

1. Manually remove the non-CGv6 configuration, if any.2. Install the Cisco IOS XR Software image (asr9k-mini-p/px.vm/pie) for the specific release on the router.3. To handle version incompatibility between APIs of Cisco IOS XR and Linux software, run the following

commands in admin mode. Enter into maintenance mode by using the following command.4. To install the Services PIE on RSP, run the commands in admin mode:5. To set the service role as cgn on RSP, run the following commands.6. To install Linux Install-Kit from RSP, run the commands in admin mode.7. Wait for around 12-14 minutes for the card to come at SEOS-READY. Proceed with ServiceInfra interface

configuration.



DETAILED STEPS

Step 1 Manually remove the non-CGv6 configuration, if any.Step 2 Install the Cisco IOS XR Software image (asr9k-mini-p/px.vm/pie) for the specific release on the router.Step 3 To handle version incompatibility between APIs of Cisco IOS XR and Linux software, run the following commands in

admin mode. Enter into maintenance mode by using the following command.RP/0/RP0/CPU0:# adminRP/0/RSP0/CPU0(admin)# debug sim reload-disable location<ism_node_location>The card must be in the following state:RP/0/RSP0/CPU0# show platform

Node Type State Config State___________________________________________________________________________0/5/CPU0 A9K-ISM-100(LCP) IOS XR RUN PWR,NSHUT,MON0/5/CPU1 A9K-ISM-100(SE) RECOVERY MODESometimes, the card goes into IN-RESET state due to multiple resets or if you miss to execute the step for a long time.

Reload the card using the following command to get out of the state:RP/0/RSP0/CPU0(admin)# hw-module location <ism_node_location> reload

The command must be executed in adminmode.

Note

Step 4 To install the Services PIE on RSP, run the commands in admin mode:RP/0/RSP0/CPU0#admin(admin)#install add tftp://<tftp_addr>/<image_location>/asr9k-services-p.pie synchronous activate. . . . . . . . . . .(admin)#exit

Step 5 To set the service role as cgn on RSP, run the following commands.RP/0/RSP0/CPU0#config(config)#hw-module service cgn location <ism_node_location>(config)#commit(config)#exit

Step 6 To install Linux Install-Kit from RSP, run the commands in admin mode.RP/0/RSP0/CPU0#adminRP/0/RSP0/CPU0(admin)# download install-image <install_kit_name_and_location> from<rsp_where_kit_present> to <ism_node_location>

You can download the Install-Kit from the File Exchage Serverhttps://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=IOS-XR

Note

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

Configuring the Service Role for the Carrier Grade IPv6Perform this task to configure the service role on the specified location to start the CGv6 service.

Removal of service role is strictly not recommended while the card is active. This puts the card intoFAILED state, which is service impacting.

Note


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Service Role for the Carrier Grade IPv6

SUMMARY STEPS

1. configure2. hw-module service cgn location node-id3. endor commit

DETAILED STEPS

PurposeCommand or Action

Enters global configuration mode.configure

Example:RP/0/RP0/CPU0:router# configure

Step 1

Configures a CGv6 service role (cgn) on location 0/1/CPU0.hw-module service cgn location node-id

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

Step 2

Saves configuration changes.endor commitStep 3

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

•When you issue the end command, the system prompts you to commitchanges:

Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:

◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returns therouter to EXEC mode.

◦Entering no exits the configuration session and returns the routerto EXEC mode without committing the configuration changes.

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

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

Configuring the Service Instance and Location for the Carrier Grade NATPerform this task to configure the service instance and location for the CGN application.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Service Instance and Location for the Carrier Grade NAT

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-location preferred-active node-id [preferred-standby node-id]4. end or commit

DETAILED STEPS




Step 1

Configures the instance named cgn1 for the CGN application and entersCGN configuration mode.

service cgn instance-name

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

Step 2

Configures the active and standby locations for the CGN application.service-location preferred-active node-id[preferred-standby node-id]

Step 3

Example:RP/0/RP0/CPU0:router(config-cgn)#service-location preferred-active0/1/CPU0 preferred-standby 0/4/CPU0

Saves configuration changes.end or commit

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

Step 4

•When you issue the end command, the system prompts you tocommit changes:

Uncommitted changes found, commit them before exiting(yes/no/cancel)?

[cancel]:

◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, and returnsthe router to EXEC mode.

◦Entering no exits the configuration session and returns therouter to EXECmode without committing the configurationchanges.

◦Entering cancel leaves the router in the current configurationsession without exiting or committing the configurationchanges.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Service Instance and Location for the Carrier Grade NAT


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

Configuring the Infrastructure Service Virtual Interface for the Carrier GradeIPv6

Perform this task to configure the infrastructure service virtual interface (SVI) to forward the control traffic.

Access lists are not supported on service virtual interfaces.Note

The subnet mask length must be at least 30 (denoted as /30).

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

Note

SUMMARY STEPS

1. configure2. interface ServiceInfra value3. service-location node-id4. ipv4 address address/mask5. endor commit6. reload

DETAILED STEPS




Step 1

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

interface ServiceInfra value

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

Step 2

Only one service infrastructure SVI can be configured for aCGv6 instance.

Note


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Infrastructure Service Virtual Interface for the Carrier Grade IPv6


Configures the location of the CGv6 service for the infrastructure SVI.service-location node-id

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

Step 3

Sets the primary IPv4 address for an interface.ipv4 address address/mask

Example:RP/0/RP0/CPU0:router(config-if)# ipv4address 1.1.1.1/30

Step 4


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




◦Entering no exits the configuration session and returns therouter to EXEC mode without committing the configurationchanges.


• Use the commit command to save the configuration changes to therunning configuration file and remain within the configurationsession.

Once the configuration is complete, the cardmust be reloaded for changesto take effect.

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

reload

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

Step 6

Configuring Different CGv6 Applications on ISMThese CGv6 applications are configured on ISM.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different CGv6 Applications on ISM

Configuring NAT44 on ISMPerform these tasks to configure NAT44 on ISM.

Configuring the Application Service Virtual Interface (NAT44)

Perform this task to configure the application service virtual interface (SVI) to forward data traffic.

SUMMARY STEPS

1. configure2. interface ServiceApp value3. service cgn instance-name service-type nat444. vrf vrf-name5. end or commit

DETAILED STEPS




Step 1

Configures the application SVI as 1 and enters interface configurationmode.

interface ServiceApp value

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

Step 2


service cgn instance-name service-type nat44

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

Step 3

Configures the VPN routing and forwarding (VRF) for the ServiceApplication interface

vrf vrf-name

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

Step 4



Step 5



[cancel]:








Configuring a NAT44 Instance

Perform this task to configure a NAT44 instance.

The system does not support deleting VRF on live traffic in the following scenarios:Note

• If you are in the global configuration mode.

• If you are within the CGN instance.

• If you are in the static route table.

SUMMARY STEPS

1. configure2. service cgn nat44instance-name3. service-location preferred-active VSM location4. service-type nat44 nat15. end or commit



DETAILED STEPS




Step 1

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

service cgn nat44instance-name


Step 2

Configures the NAT preferred active VSM location.service-location preferred-activeVSM location

Example:RP/0/RP0/CPU0:router(config-cgn)#service-location preferred-active0/3/CPU0

Step 3

Configures the service type keyword definition for CGv6 NAT44application.

service-type nat44 nat1

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

Step 4

Saves configuration changes.end or commitStep 5




◦Entering yes saves configuration changes to the runningconfiguration file, exits the configuration session, andreturns the router to EXEC mode.






Configuring an Inside and Outside Address Pool Map (NAT44)

Perform this task to configure an inside and outside address pool map with the following scenarios:

• The designated address pool is used for CNAT.

• One inside VRF is mapped to only one outside VRF.

• Multiple non-overlapping address pools can be used in a specified outside VRF mapped to differentinside VRF.

• Max Outside public pool per CGSE/CGN instance is 64 K or 65536 addresses. That is, if a /16 addresspool is mapped, then we cannot map any other pool to that particular CGSE.

• Multiple inside vrf cannot be mapped to same outside address pool.

•While Mapping Outside Pool Minimum value for prefix is 16 and maximum value is 26.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. map [outside-vrf outside-vrf-name] address-pool address/prefix6. end or commit

DETAILED STEPS




Step 1

Configures the instance named cgn1 for the CGN application andenters CGN configuration mode.



Step 2

Configures the service type keyword definition for CGN NAT44application.



Step 3




Configures an inside VRF named insidevrf1 and enters CGN insideVRF configuration mode.

inside-vrf vrf-name

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

Step 4

Configures an inside VRF to an outside VRF and address poolmapping.

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

Example:RP/0/RP0/CPU0:router(config-cgn-invrf)# mapoutside-vrf outside vrf1 address-pool

Step 5

10.10.0.0/16orRP/0/RP0/CPU0:router(config-cgn-invrf)# mapaddress-pool 100.1.0.0/16


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

Step 6

•When you issue the end command, the system prompts youto commit changes:


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

[cancel]:


◦Entering no exits the configuration session and returnsthe router to EXEC mode without committing theconfiguration changes.

◦Entering cancel leaves the router in the currentconfiguration session without exiting or committing theconfiguration changes.

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

Policy Functions

Configuring Port Limit per Subscriber

Perform this task to restrict the number of ports used by an IPv6 address.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat64 stateful instance-name4. portlimit value5. end or commit

DETAILED STEPS




Step 1

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


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

Step 2

Configures the service type keyword definition forCGv6 Stateful NAT64 application.

service-type nat64 stateful instance-name

Example:RP/0/RP0/CPU0:router(config-cgn)# service-type nat64stateful nat64-instRP/0/RP0/CPU0:router(config-cgn-nat64-stateful)#

Step 3

Configures a value to restrict the number of ports usedby an IPv6 address.

portlimit value

Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)#portlimit66RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)# endorRP/0/RP0/CPU0:router(config-cgn-nat64-stateful)# commit

Step 5

•When you issue the end command, the systemprompts you to commit changes:

Uncommitted changes found, commit thembefore exiting (yes/no/cancel)?

[cancel]:

◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns therouter to EXEC mode.

◦Entering no exits the configuration sessionand returns the router to EXEC mode




without committing the configurationchanges.

◦Entering cancel leaves the router in thecurrent configuration session withoutexiting or committing the configurationchanges.

• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain within theconfiguration session.

Configuring the Timeout Value for ICMP, TCP and UDP Sessions

Perform this task to configure the timeout value for ICMP, TCP or UDP sessions for a Dual Stack Lite (DSLite) instance:

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. protocol tcp session {active | initial} timeout value or protocol {icmp | udp} timeout value5. end or commit

DETAILED STEPS




Step 1

Configures the instance named cgn1 for the CGv6 applicationand enters CGv6 configuration mode.



Step 2




Configures the service type keyword definition for CGv6DS-Lite application.

service-type ds-lite instance-name

Example:RP/0/RP0/CPU0:router(config-cgn)# service-typeds-lite ds-lite-instRP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Step 3

Configures the initial and active session timeout values forTCP.

protocol tcp session {active | initial} timeout value orprotocol {icmp | udp} timeout value

Step 4

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite)#protocoltcp session active timeout 90

Configures the timeout value in seconds for ICMP and UDP.

orprotocol icmp timeout 90RP/0/RP0/CPU0:router(config-cgn-ds-lite)


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

Step 5

•When you issue the end command, the system promptsyou to commit changes:


[cancel]:

◦Entering yes saves configuration changes to therunning configuration file, exits the configurationsession, and returns the router to EXEC mode.

◦Entering no exits the configuration session andreturns the router to EXEC mode withoutcommitting the configuration changes.

◦Entering cancel leaves the router in the currentconfiguration sessionwithout exiting or committingthe configuration changes.

• Use the commit command to save the configurationchanges to the running configuration file and remainwithin the configuration session.

Configuring the FTP ALG for NAT44 Instance

Perform this task to configure the FTP ALG for the specified NAT44 instance.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. alg activeFTP5. end or commit

DETAILED STEPS




Step 1



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

Step 2

Configures the service type keyword definition for NAT44 application.service-type nat44 nat1


Step 3

Configures the FTP ALG on the NAT44 instance.alg activeFTP

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)#alg activeFTP

Step 4



Step 5



[cancel]:








Configuring the RTSP ALG for NAT44 Instance

Perform this task to configure the ALG for the rtsp for the specified NAT44 instance. RTSP packets areusually destined to port 554. But this is not always true because RTSP port value is configurable.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. alg rtsp [server-port] value5. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for NAT44application.service-type nat44 nat1


Step 3




Configures the rtsp ALG on the NAT44 instance for server port 5000.The range is from 1 to 65535. The default port is 554.

alg rtsp [server-port] value

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)#alg rtsp server-port 5000

Step 4

The option of specifying a server port) is currently notsupported. Even if you configure some port, RTSPworks onlyon the default port (554).

Caution



Step 5



[cancel]:





Configuring the PPTP ALG for a NAT44 Instance

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. alg pptpAlg5. end or commit



DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for NAT44 or DS-Liteapplication.



Step 3

Configures the pptp ALG on the CGN instance.alg pptpAlg

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)#alg pptpAlg

Step 4



Step 5



[cancel]:







TCP Maximum Segment Size Adjustment

When a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.

Static Port Forwarding

Static port forwarding helps in associating a private IP address and port with a statically allocated public IPand port. After you have configured static port forwarding, this association remains intact and does not getremoved due to timeouts until the CGSE is rebooted. In case of redundant CGSE cards, it remains intact untilboth of the CGSEs are reloaded together or the router is reloaded. There are remote chances that after a reboot,this association might change. This feature helps in cases where server applications running on the privatenetwork needs access from public internet.

Configuring Dynamic Port Range

Perform this task to configure a dynamic port range.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat64 stateful instance-name4. dynamic-port-range start port-number5. endor commit

DETAILED STEPS




Step 1

Configures the instance for the CGv6application and enters CGv6 configurationmode.



Step 2

Configures the service type keyworddefinition for CGv6 Stateful NAT64application.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-type nat64 statefulnat64-instRP/0/RP0/CPU0:router(config-cgn-nat64-stateful)

Step 3




Configures the port range from 1 to 65535.dynamic-port-range start port-number

Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)#dynamic-port-rangestart 66RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)# endorRP/0/RP0/CPU0:router(config-cgn-nat64-stateful)# commit

•When you issue the end command, thesystem prompts you to commitchanges:

Uncommitted changes found,commit them before exiting(yes/no/cancel)?[cancel]:

◦Entering yes saves configurationchanges to the runningconfiguration file, exits theconfiguration session, andreturns the router to EXECmode.

◦Entering no exits theconfiguration session and returnsthe router to EXEC modewithout committing theconfiguration changes.

◦Entering cancel leaves the routerin the current configurationsession without exiting orcommitting the configurationchanges.

• Use the commit command to save theconfiguration changes to the runningconfiguration file and remain withinthe configuration session.

Configuring External Logging for the NAT Table Entries

Perform the following to configure external logging for NAT table entries.

Netflow LoggingPerform the following tasks to configure Netflow Logging for NAT table entries.



Configuring the Server Address and Port for Netflow LoggingPerform this task to configure the server address and port to log network address translation (NAT) tableentries for Netflow logging.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. address address port number8. end or commit

DETAILED STEPS




Step 1

Configures the instance named cgn1 for the CGNapplication and enters CGN configuration mode.



Step 2

Configures the service type keyword definition forNAT44 application.


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

Step 3

Configures the inside VRF for the CGN instancenamed cgn1 and enters CGN inside VRF configurationmode.

inside-vrf vrf-name

Example:RP/0/RP0/CPU0:router(config-cgn)# inside-vrf insidevrf1RP/0/RP0/CPU0:router(config-cgn-invrf)#

Step 4

Configures the external-logging facility for the CGNinstance named cgn1 and enters CGN inside VRFaddress family external logging configuration mode.

external-logging netflowv9

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

Step 5




Configures the logging server information for the IPv4address and port for the server that is used for the

server

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

Step 6

netflowv9-based external-logging facility and entersCGN inside VRF address family external loggingserver configuration mode.

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

address address port number

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

Step 7


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

Step 8


Uncommitted changes found, commit them beforeexiting (yes/no/cancel)?

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

[cancel]:

◦Entering yes saves configuration changesto the running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.

◦Entering no exits the configuration sessionand returns the router to EXEC modewithout committing the configurationchanges.



Configuring the Path Maximum Transmission Unit for Netflow LoggingPerform this task to configure the path maximum transmission unit (MTU) for the netflowv9-basedexternal-logging facility for the inside VRF.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. path-mtu value8. end or commit

DETAILED STEPS




Step 1




Step 2




Step 3


inside-vrf vrf-name


Step 4




Step 5


server


Step 6





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

path-mtu value

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

Step 7



Step 8




[cancel]:





Configuring the Refresh Rate for Netflow LoggingPerform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed orresent to the Netflow-v9 logging server.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. refresh-rate value8. end or commit

DETAILED STEPS




Step 1




Step 2




Step 3


inside-vrf vrf-name


Step 4




Step 5


server


Step 6





Configures the refresh rate value of 50 to logNetflow-based external logging information for aninside VRF.

refresh-rate value

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

Step 7



Step 8




[cancel]:





Configuring the Timeout for Netflow LoggingPerform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to besent to the Netflow-v9 logging server.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflowv96. server7. timeoutvalue8. end or commit

DETAILED STEPS




Step 1




Step 2




Step 3


inside-vrf vrf-name


Step 4




Step 5


server


Step 6





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

timeoutvalue

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

Step 7



Step 8




[cancel]:





Syslog LoggingPerform the following tasks to configure Syslog Logging for NAT table entries.

Configuring the Server Address and Port for Syslog LoggingPerform this task to configure the server address and port to log DS-Lite entries for Syslog logging.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. addressaddressportnumber7. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definitionfor the DS-Lite application.

service-type ds-lite instance_name

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

Step 3

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

external-logging syslog

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

Step 4

Configures the logging server information for theIPv4 address and port for the server that is used

server

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

Step 5

for the syslog-based external-logging facility andenters CGv6 external logging server configurationmode.

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

addressaddressportnumber

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlogserver)#address2.3.4.5 port 45

Step 6





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

Step 7

•When you issue the end command, thesystem prompts you to commit changes:


[cancel]:

◦Entering yes saves configurationchanges to the running configurationfile, exits the configuration session,and returns the router to EXECmode.

◦Entering no exits the configurationsession and returns the router toEXEC mode without committing theconfiguration changes.

◦Entering cancel leaves the router inthe current configuration sessionwithout exiting or committing theconfiguration changes.


Configuring the Host-Name for Syslog LoggingPerform this task to configure the host name to be filled in the Netflow header for the syslog logging.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging syslog6. server7. host-namename8. end or commit



DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition forCGv6 NAT44 application.



Step 3

Configures the inside VRF for the CGv6 instancenamed cgn1 and enters CGv6 insideVRF configurationmode.

inside-vrf vrf-name

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrfinsidevrf1RP/0/RP0/CPU0:router(config-cgn-invrf)#

Step 4

Configures the external-logging facility for the CGv6instance named cgn1 and enters CGv6 inside VRFaddress family external logging configuration mode.


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

Step 5


server


Step 6

syslog-based external-logging facility and enters CGv6inside VRF address family external logging serverconfiguration mode.

Configures the host name for the syslog-basedexternal-logging facility.

host-namename

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

Step 7



Step 8




[cancel]:








Configuring the Path Maximum Transmission Unit for Syslog Logging

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging syslog6. server7. path-mtuvalue8. end or commit

DETAILED STEPS




Step 1







Step 2




Step 3

Configures the inside VRF for the CGv6 instancenamed cgn1 and enters CGv6 insideVRF configurationmode.

inside-vrf vrf-name

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrfinsidevrf1RP/0/RP0/CPU0:router(config-cgn-invrf)#

Step 4

Configures the external-logging facility for the CGv6instance named cgn1 and enters CGv6 inside VRFaddress family external logging configuration mode.



Step 5


server


Step 6

syslog-based external-logging facility and enters CGv6inside VRF address family external logging serverconfiguration mode.

Configures the path MTU with the value of 200 forthe syslog-based external-logging facility.

path-mtuvalue

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

Step 7



Step 8




[cancel]:


◦Entering no exits the configuration sessionand returns the router to EXEC mode




without committing the configurationchanges.



Bulk Port Allocation

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. bulk-port-alloc size number of ports6. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for CGv6NAT44application.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typenat44 nat1

Step 3




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

inside-vrf vrf-name

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

Step 4

Allocate ports in bulk to reduce Netflow/Syslog data volume.bulk-port-alloc size number of ports

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

Step 5


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

Step 6



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

[cancel]:


◦Entering no exits the configuration session andreturns the router to EXECmode without committingthe configuration changes.

◦Entering cancel leaves the router in the currentconfiguration session without exiting or committingthe configuration changes.

• Use the commit command to save the configurationchanges to the running configuration file and remain withinthe configuration session.

Destination-Based Logging for NAT44Perform these tasks to configure destination-based logging for NAT table entries.

Configuring the Session-Logging for Netflow LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging netflow6. server7. session-logging8. end or commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the inside VRF for the CGv6 instancenamed cgn1 and enters CGv6 inside VRFconfiguration mode.

inside-vrf vrf-name

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrfinsidevrf1RP/0/RP0/CPU0:router(config-cgn-nat44-invrf)#

Step 4

Configures the external-logging facility for the NAT44instance.

external-logging netflow

Example:RP/0/RP0/CPU0:router(config-cgn-invrf)# external-loggingnetflow version 9RP/0/RP0/CPU0:router(config-cgn-invrf-af-extlog)#

Step 5

Configures the logging server information for the IPv4address and port for the server that is used for thenetflow-v9 based external-logging facility.

server


Step 6




Configures the session logging for a NAT44 instance.session-logging

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

Step 7



Step 8




[cancel]:





Configuring the Session-Logging for Syslog LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat44 nat14. inside-vrf vrf-name5. external-logging syslog6. server7. session-logging8. end or commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the inside VRF for the CGv6 instancenamed cgn1 and enters CGv6 inside VRFconfiguration mode.

inside-vrf vrf-name

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)# inside-vrfinsidevrf1RP/0/RP0/CPU0:router(config-cgn-nat44-invrf)#

Step 4

Configures the external-logging facility for the NAT44instance.



Step 5

Configures the logging server information for the IPv4address and port for the server that is used for thenetflow-v9 based external-logging facility.

server


Step 6




Configures the session logging for a NAT44 instance.session-logging

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

Step 7



Step 8




[cancel]:





Configuring DS-LitePerform these tasks to configure DS-Lite.

Configuring the Application Service Virtual Interface




SUMMARY STEPS

1. configure2. interface ServiceApp value3. service cgn instance-name service-type ds-lite4. vrf vrf-name5. end or commit

DETAILED STEPS




Step 1

Configures the application SVI as 1 and enters interface configurationmode.



Step 2


service cgn instance-name service-type ds-lite

Example:RP/0/RP0/CPU0:router(config-if)# servicecgn cgn1 service-type ds-lite

Step 3

Configures the VPN routing and forwarding (VRF) for the ServiceApplication interface

vrf vrf-name

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

Step 4



Step 5



[cancel]:








Configuring Dual Stack Lite Instance

Perform this task to configure dual stack lite application.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-location preferred-active node-id [preferred-standby node-id]4. service-type ds-lite instance5. portlimit value6. bulk-port-alloc size value7. map address-pool address8. aftr-tunnel-endpoint-address <address>9. address-family ipv410. interface ServiceApp4111. address-family ipv612. interface ServiceApp6113. protocol tcp14. session {initial | active} timeout seconds15. msssize16. external-logging netflow917. server18. address A.B.C.D port port-number19. external-logging syslog20. server21. address A.B.C.D port port-number22. end or commit



DETAILED STEPS




Step 1




Step 2

Specifies the global command applied per cgninstance. It initiates the particular instance of the cgnapplication on the active and standby locations.

service-location preferred-active node-id [preferred-standbynode-id]

Example:RP/0/RP0/CPU0:router(config-cgn)# service-locationpreferred-active 0/2/CPU0 preferred-standby 0/4/CPU0

Step 3

Configures the service type keyword definition forthe DS LITE application.

service-type ds-lite instance

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

Step 4

Configures the service type keyword definition forthe DS LITE application.

portlimit value

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

Step 5

Enables bulk port allocation and sets bulk size that isused to reduce logging data volume.

bulk-port-alloc size value

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

Step 6

Specifies the address pool for the DS LITE instance.map address-pool addressStep 7

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite)# mapaddress-pool 52.52.52.0/24

52.52.52.0/24 is the IPv4 public address poolassigned to the DS Lite instance.

Note

Specifies the IPv6 address of the tunnel end point.The IPv4 elements must address their IPV6 packetsto this address.

aftr-tunnel-endpoint-address <address>

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite)#aftr-tunnel-endpoint address 3001:DB8:EOE:E01::

Step 8

Enters the address family IPv4 configuration mode.address-family ipv4

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

Step 9




Specifies the ServiceApp on which IPv4 traffic entersand leaves.

interface ServiceApp41

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

Step 10

Enters the address family IPv6 configuration mode.address-family ipv6

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

Step 11

Specifies the ServiceApp on which IPv6 traffic entersand leaves.

interface ServiceApp61

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

Step 12

Configures the TCP protocol session.protocol tcp

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

Step 13

This command configures the timeout value inseconds for ICMP,TCP or UDP sessions for a service

session {initial | active} timeout seconds

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

Step 14

instance. For TCP and UDP, you can configure theinitial and active session timeout values. For ICMP,there are no such options. This configuration isapplicable to all the IPv4 addresses that belong to aparticular service instance. This example configuresthe initial session timeout value as 90 for the TCPsession.

Configures the adjustment MSS value as 1100.msssize

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

Step 15

Configures the external-logging facility for the DSLITE instance named dsl1 and enters the externallogging configuration mode.

external-logging netflow9

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

Step 16


server

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

Step 17

netflow-v9 based external-logging facility and entersexternal logging server configuration mode.




Configures the netflow server address and port numberto use for netflow version 9 based external loggingfacility for DS LITE instance.

address A.B.C.D port port-number

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#address 90.1.1.1 port 99

Step 18

Configures the external-logging facility for the DSLITE translation entries that can be logged in syslogservers to analyze and debug the information.


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

Step 19

Configures the logging server information for the IPv4address and port for the server that is used for thesyslog based external-logging facility.

server

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

Step 20

Configures the syslog server address and port numberto use for syslog based external logging facility forDS LITE instance.

address A.B.C.D port port-number

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlog-server)#address 90.1.1.1 port 514

Step 21


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

Step 22



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

[cancel]:


◦Entering no exits the configurationsession and returns the router to EXECmode without committing theconfiguration changes.






Configuring the Policy Functions

Perform these tasks to configure the policy functions.

Configuring IPv6 Tunnel Endpoint Address

Perform this task to configure the IPv6 tunnel endpoint address:

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance name4. aftr-tunnel-endpoint-address X:X::X IPv6 address5. end or commit

DETAILED STEPS




Step 1

Configures the instance named cgn1 for the CGv6 application andenters CGv6 configuration mode.



Step 2

Configures the service type keyword definition for CGv6 DS-Liteapplication.

service-type ds-lite instance name

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

Step 3

Configures an IPv6 tunnel endpoint address.aftr-tunnel-endpoint-address X:X::X IPv6address

Step 4

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





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

Step 5



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

[cancel]:





Configuring the Port Limit per Subscriber

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

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. portlimit value5. end or commit

DETAILED STEPS




Step 1







Step 2

Configures the service type keyword definition for CGv6 DS-Liteapplication.

service-type ds-lite ds-lite1


Step 3

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

portlimit value

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

Step 4



Step 5



[cancel]:


◦Entering no exits the configuration session and returns therouter to EXECmodewithout committing the configurationchanges.



Configuring the Timeout Value for ICMP, TCP and UDP Sessions

Perform this task to configure the timeout value for ICMP, TCP or UDP sessions for a Dual Stack Lite (DSLite) instance:



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. protocol tcp session {active | initial} timeout value or protocol {icmp | udp} timeout value5. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for CGv6DS-Lite application.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typeds-lite ds-lite-instRP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Step 3

Configures the initial and active session timeout values forTCP.

protocol tcp session {active | initial} timeout value orprotocol {icmp | udp} timeout value

Step 4

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite)#protocoltcp session active timeout 90

Configures the timeout value in seconds for ICMP and UDP.

orprotocol icmp timeout 90RP/0/RP0/CPU0:router(config-cgn-ds-lite)


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

Step 5



[cancel]:






◦Entering cancel leaves the router in the currentconfiguration sessionwithout exiting or committingthe configuration changes.


Configuring the FTP ALG for DS-Lite Instance

Perform this task to configure the FTP ALG for the specified DS-Lite instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. alg ftp5. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for NAT44 or DS-Liteapplication.


Example:

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

Step 3




Configures the FTP ALG on the DS-Lite instance.alg ftp

Example:

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

Step 4



Step 5



[cancel]:




• Use the commit command to save the configuration changes tothe running configuration file and remainwithin the configurationsession.

Configuring the RTSP ALG for DS-Lite Instance

Perform this task to configure the ALG for the rtsp for the specified DS-Lite instance. RTSP packets areusually destined to port 554. But this is not always true because RTSP port value is configurable.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. alg rtsp [server-port] value5. end or commit



DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for DS-Lite application.service-type ds-lite ds-lite1

Example:

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

Step 3

Configures the rtsp ALG on the DS-Lite instance for server port 5000.The range is from 1 to 65535. The default port is 554.

alg rtsp [server-port] value

Example:RP/0/RP0/CPU0:router(config-cgn-nat44)#alg rtsp server-port 5000

Step 4

The option of specifying a server port) is currently notsupported. Even if you configure some port, RTSPworks onlyon the default port (554).

Caution



Step 5



[cancel]:







TCP Maximum Segment Size Adjustment

When a host initiates a TCP session with a server, the host negotiates the IP segment size by using the maximumsegment size (MSS) option. The value of the MSS option is determined by the maximum transmission unit(MTU) that is configured on the host.

Configuring an Address Pool Map

Perform this task to configure an address pool map.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance-name4. map address-pool address/prefix5. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition forCGv6 DS-Lite application.


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

Step 3

Configures an address pool mapping.map address-pool address/prefix

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

Step 4

orRP/0/RP0/CPU0:router(config-cgn-ds-lite)# mapaddress-pool 100.1.0.0/16



Step 5







[cancel]:





Configuring the Path Maximum Transmission Unit

Before You Begin

DS-Lite

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. path-mtu value5. end or commit



DETAILED STEPS




Step 1




Step 2



Step 3

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

Configures the path MTU with the value of 2900 for the DS-Liteinstance.

path-mtu value

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

Step 4

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



Step 5




[cancel]:








Configuring External Logging for DS-Lite Entries

Perform the following to configure external logging for DS-Lite entries.

Netflow LoggingPerform the following tasks to configure Netflow Logging for NAT table entries.


SUMMARY STEPS


DETAILED STEPS




Step 1




Step 2




Step 3







Step 4


server


Step 5





Step 6



Step 7



[cancel]:





Configuring the Path Maximum Transmission Unit



Before You Begin

DS-Lite

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. path-mtu value5. end or commit

DETAILED STEPS




Step 1




Step 2



Step 3

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

Configures the path MTU with the value of 2900 for the DS-Liteinstance.

path-mtu value

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

Step 4

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



Step 5




[cancel]:








Configuring the Refresh Rate for Netflow LoggingPerform this task to configure the refresh rate at which the Netflow-v9 logging templates are refreshed orresent to the Netflow-v9 logging server.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging netflowv95. server6. refresh-rate value7. end or commit

DETAILED STEPS




Step 1




Step 2




Configures the service type keyword definition for CGv6DS-Lite application..


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typeds-lite ds-lite1RP/0/RP0/CPU0:router(config-cgn-ds-lite)#

Step 3

Configures the external-logging facility for the CGNinstance named cgn1 and enters CGN external loggingconfiguration mode.


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

Step 4

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


server


Step 5

netflow9-based external-logging facility and enters CGv6external logging server configuration mode..

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

refresh-rate value

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

Step 6


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

Step 7



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

[cancel]:

◦Entering yes saves configuration changes tothe running configuration file, exits theconfiguration session, and returns the routerto EXEC mode.

◦Entering no exits the configuration sessionand returns the router to EXECmode withoutcommitting the configuration changes.

◦Entering cancel leaves the router in thecurrent configuration session without exitingor committing the configuration changes.

• Use the commit command to save the configurationchanges to the running configuration file andremain within the configuration session.




Configuring the Timeout for Netflow LoggingPerform this task to configure the frequency in minutes at which the Netflow-V9 logging templates are to besent to the Netflow-v9 logging server.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging netflowv95. server6. timeoutvalue7. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition forDS-Lite application.



Step 3

Configures the external-logging facility for the CGv6instance named cgn1 and enters CGv6 external loggingconfiguration mode.


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

Step 4

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





server


Step 5

netflow9-based external-logging facility and enters CGv6external logging server configuration mode.

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

timeoutvalue

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

Step 6


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

Step 7



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

[cancel]:





Syslog LoggingPerform the following tasks to configure Syslog Logging for NAT table entries.




SUMMARY STEPS


DETAILED STEPS




Step 1




Step 2




Step 3




Step 4


server


Step 5





Step 6






Step 7



[cancel]:





Configuring the Host-Name for Syslog LoggingPerform this task to configure the host name to be filled in the Netflow header for the syslog logging.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite ds-lite14. external-logging syslog5. server6. host-namename7. end or commit



DETAILED STEPS




Step 1

Configures the instance named cgn1 for theCGv6 application and enters CGv6configuration mode.



Step 2




Step 3



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

Step 4

Configures the logging server information forthe IPv4 address and port for the server that is

server


Step 5

used for the syslog-based external-loggingfacility and enters CGv6 external logging serverconfiguration mode.

Configures the host name for the syslog-basedexternal-logging facility.

host-namename

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlogserver)#host-namehost1

Step 6



Step 7


Uncommitted changes found, committhem before exiting (yes/no/cancel)?

[cancel]:


◦Entering no exits the configurationsession and returns the router to




EXEC mode without committingthe configuration changes.



Configuring the Path Maximum Transmission Unit for Syslog LoggingPerform this task to configure the pathmaximum transmission unit (MTU) for the syslog-based external-loggingfacility.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. path-mtuvalue7. end or commit

DETAILED STEPS




Step 1

Configures the instance named cgn1 for theCGv6 application and enters CGv6 configurationmode.



Step 2







Step 3




Step 4

Configures the logging server information forthe IPv4 address and port for the server that is

server


Step 5

used for the syslog-based external-loggingfacility and enters CGv6 external logging serverconfiguration mode.

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

path-mtuvalue

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlogserver)#path-mtu200

Step 6



Step 7



[cancel]:


◦Entering no exits the configurationsession and returns the router toEXECmode without committing theconfiguration changes.






Bulk Port AllocationPerform this task to configure bulk port allocation to reduce Netflow or Syslog data volume.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. bulk-port-alloc size number of ports5. end or commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for theDS-Lite application.



Step 3

Allocate ports in bulk to reduce Netflow/Syslog datavolume.

bulk-port-alloc size number of ports

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

Step 4


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

Step 5



[cancel]:








Destination-Based Logging for DS-LitePerform these tasks to configure destination-based logging for DS-Lite entries.

Configuring the Session-Logging for Netflow LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging netflow95. server6. session-logging7. end or commit



DETAILED STEPS




Step 1

Configures the instance named cgn1 forthe CGv6 application and enters CGv6configuration mode.



Step 2

Configures the service type keyworddefinition for the DS-Lite application.



Step 3

Configures the external-logging facilityfor the DS-Lite instance.

external-logging netflow9

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

Step 4

Configures the logging serverinformation for the IPv4 address and port

server


Step 5

for the server that is used for thenetflow-v9 based external-loggingfacility.

Configures the session logging for aDS-Lite instance.

session-logging

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlogserver)#session-logging

Step 6



Step 7

•When you issue the end command,the system prompts you to commitchanges:

Uncommitted changes found,commit them before exiting(yes/no/cancel)?

[cancel]:

◦Entering yes savesconfiguration changes to therunning configuration file,exits the configurationsession, and returns the routerto EXEC mode.




◦Entering no exits theconfiguration session andreturns the router to EXECmodewithout committing theconfiguration changes.

◦Entering cancel leaves therouter in the currentconfiguration session withoutexiting or committing theconfiguration changes.

• Use the commit command to savethe configuration changes to therunning configuration file andremain within the configurationsession.

Configuring the Session-Logging for Syslog LoggingPerform this task to configure session-logging if destination IP and Port information needs to logged in theNetflow records.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type ds-lite instance_name4. external-logging syslog5. server6. session-logging7. end or commit

DETAILED STEPS




Step 1




Configures the instance named cgn1 forthe CGv6 application and enters CGv6configuration mode.



Step 2

Configures the service type keyworddefinition for the DS-Lite application.



Step 3

Configures the external-logging facilityfor the DS-Lite instance.



Step 4

Configures the logging serverinformation for the IPv4 address and port

server


Step 5

for the server that is used for thenetflow-v9 based external-loggingfacility.

Configures the session logging for aDS-Lite instance.

session-logging

Example:RP/0/RP0/CPU0:router(config-cgn-ds-lite-extlogserver)#session-logging

Step 6



Step 7

•When you issue the end command,the system prompts you to commitchanges:

Uncommitted changes found,commit them before exiting(yes/no/cancel)?

[cancel]:

◦Entering yes savesconfiguration changes to therunning configuration file,exits the configurationsession, and returns the routerto EXEC mode.

◦Entering no exits theconfiguration session andreturns the router to EXECmodewithout committing theconfiguration changes.




◦Entering cancel leaves therouter in the currentconfiguration session withoutexiting or committing theconfiguration changes.

• Use the commit command to savethe configuration changes to therunning configuration file andremain within the configurationsession.

Configuring Stateful NAT64 on ISMPerform these tasks to configure Stateful NAT64 on ISM.

Configuring the Application Service Virtual Interface

This section lists the guidelines for selecting service application interfaces for 6RD

• Pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an odd integer. This is to ensure that theServiceApp pairs works with a maximum throughput. For example, ServiceApp1 with ServiceApp2 orServiceApp3 with ServiceApp4.

• Pair ServiceApp<n> with ServiceApp<n+5> or ServiceApp<n+9>, and so on, where <n> is an oddinteger. For example, ServiceApp1 with ServiceApp6, ServiceApp1 with ServiceApp10, ServiceApp3with ServiceApp8, or ServiceApp3 with ServiceApp12.

• Pair ServiceApp<n>with ServiceApp<n+4>, where <n> is an integer (odd or even integer). For example,ServiceApp1 with ServiceApp5, or ServiceApp2 with ServiceApp6.

Although ServiceApp pairs work, the aggregate throughput for Inside-to-Outside and Outside-to-Insidetraffic for the ServiceApp pair is halved.

Warning

Do not pair ServiceApp<n> with ServiceApp<n+1>, where <n> is an even integer. When used,Outside-to-Inside traffic is dropped because traffic flows in the incorrect dispatcher and core.

Caution




SUMMARY STEPS

1. configure2. interface ServiceApp value3. service cgn instance-name4. service-type nat64 stateful instance-name5. endor commit

DETAILED STEPS




Step 1

Configures the application SVI to 1, and enters interface configurationmode.



Step 2

Configures the instance named cgn1 for the CGv6 application, andenters CGv6 configuration mode.


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

Step 3

Configures the service-type as stateful NAT64.service-type nat64 stateful instance-name

Example:RP/0/RP0/CPU0:router(config-if)# servicecgn cgn1 service-type nat64 statefulnat1

Step 4


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



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








Configuring a Stateful NAT64 Instance

Perform this task to configure a stateful NAT64 instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat64 stateful instance-name4. endor commit

DETAILED STEPS




Step 1

Configures the instance for the CGv6 application and entersCGv6 configuration mode.



Step 2

Configures the service type keyword definition for CGv6Stateful NAT64 application.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typenat64 stateful nat64-instRP/0/RP0/CPU0:router(config-cgn-nat64-stateful)

Step 3


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





Uncommitted changes found, commit them beforeexiting (yes/no/cancel)?[cancel]:

orRP/0/RP0/CPU0:router(config-cgn-nat64-stateful)#commit


◦Entering no exits the configuration session andreturns the router to EXECmodewithout committingthe configuration changes.


• Use the commit command to save the configurationchanges to the running configuration file and remainwithinthe configuration session.

Configuring the Policy Functions

Perform these tasks to configure the policy functions.

Configuring MAP-EPerform these tasks to configure MAP-E.

Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for MAP-E.





Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring MAP-E


Warning


Caution


SUMMARY STEPS

1. configure2. interface ServiceApp value3. service cgn instance -name service-type map-e4. endor commit

DETAILED STEPS




Step 1

Configures the application SVI to 1, and enters interfaceconfiguration mode.


Example:

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

Step 2

ServiceApp1ipv4 address 40.40.40.1 255.255.255.0service cgn cgn1 service-type map-e!

RP/0/RP0/CPU0:router(config)# interfaceServiceApp2ipv6 address 1001::101/32service cgn cgn1 service-type map-e!


service cgn instance -name service-type map-e

Example:RP/0/RP0/CPU0:router(config-if)# servicecgn cgn1 service-type map-e map1

Step 3


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



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


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Application Service Virtual Interface






Configuring a MAP-E InstancePerform this task to configure a MAP-E instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. endor commit

DETAILED STEPS




Step 1

Configures the instance for the CGv6 application and enters CGv6configuration mode.


Example:RP/0/RP0/CPU0:router(config)# servicecgn cgn1

Step 2

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


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring a MAP-E Instance


Configures the service type keyword definition for CGv6 MAP-Eapplication.

service-type map-e instance-name

Example:RP/0/RP0/CPU0:router(config-cgn)#service-type map-e m1RP/0/RP0/CPU0:router(config-cgn-map_e)#

Step 3


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



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





Configuring the Policy FunctionsPerform these tasks to configure the policy functions.

Configuring Address FamilyPerform these tasks to configure address family.

Configuring IPv4 Address FamilyPerform these tasks configure IPv4 address family for a MAP-E instance.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Policy Functions

Configuring IPv4 Interface

Perform this task to configure an IPv4 interface for a MAP-E instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. address-family ipv4 interface ServiceApp number5. endor commit

DETAILED STEPS




Step 1

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


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

Step 2

Defines the service type keyword definition for the CGv6MAP-E application.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typemap-e m1RP/0/RP0/CPU0:router(config-cgn-map_e)

Step 3

Configures the IPv4 interface to divert IPv4 map-e traffic.address-family ipv4 interface ServiceApp number

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#address-family ipv4 interface serviceApp 66RP/0/RP0/CPU0:router(config-cgn-map_e-afi)#

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-map_e-afi)# endorRP/0/RP0/CPU0:router(config-cgn-map_e-afi)#commit





Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Address Family



◦Entering cancel leaves the router in the currentconfiguration session without exiting orcommitting the configuration changes.


Configuring TCP Maximum Segment Size

Perform this task to configure the Maximum Segment Size (MSS) for TCP.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. address-family ipv4 tcp mss value5. endor commit

DETAILED STEPS




Step 1



Example:RP/0/RP0/CPU0:router(config)# service cgncgn1

Step 2





Defines the service type keyword definition for the CGv6 MAP-Eapplication.



Step 3

Configures the MSS to be used, in bytes. The range is from 28 to1500.

address-family ipv4 tcp mss value

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#address-family ipv4 tcp mss 300RP/0/RP0/CPU0:router(config-cgn-map_e-afi)#

Step 4


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



orRP/0/RP0/CPU0:router(config-cgn-map_e-afi)#commit





Configuring IPv6 Address FamilyPerform these tasks configure an IPv6 address family.


Perform this task to configure an IPv6 interface.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. address-family ipv6 interface ServiceApp number5. endor commit

DETAILED STEPS




Step 1




Step 2





Step 3

Configures the IPv6 interface to divert IPv6 map-e traffic.address-family ipv6 interface ServiceApp number

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#address-family ipv6 interface serviceApp 66RP/0/RP0/CPU0:router(config-cgn-map_e-afi)#

Step 4













Configuring TCP Maximum Segment Size

Perform this task to configure the Maximum Segment Size (MSS) to be used for TCP.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. address-family ipv6 tcp mss number5. endor commit

DETAILED STEPS




Step 1




Step 2





Step 3




Configures the MSS to be used, in bytes. The range is from 28 to1500.

address-family ipv6 tcp mss number

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#address-family ipv6 tcp mss 300RP/0/RP0/CPU0:router(config-cgn-map_e-afi)#

Step 4










Configuring AFTR Endpoint AddressPerform this task to configure the Address Family Transition Router (AFTR) endpoint address.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. aftr-endpoint-address IPv6 address5. endor commit


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring AFTR Endpoint Address

DETAILED STEPS




Step 1




Step 2





Step 3

Configures the AFTR endpoint address.aftr-endpoint-address IPv6 address

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#aftr-en dpoint-address 2001:db8::32RP/0/RP0/CPU0:router(config-cgn-map_e)#

Step 4


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



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






Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring AFTR Endpoint Address

Configuring Contiguous PortsPerform this task to configure the number of contiguous ports for a MAP-E instance

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. contiguous-ports number5. endor commit

DETAILED STEPS




Step 1




Step 2





Step 3

Configures the number of contiguous ports. The range is from 1 to65536.

The value is expressed in powers of2.

Note

contiguous-ports number

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#contiguous-ports 16RP/0/RP0/CPU0:router(config-cgn-map_e)#

Step 4







Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Contiguous Ports





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

Configuring CPE Domain ParametersPerform this task to configure Customer Premise Equipment (CPE) domain parameters.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. cpe-domain ipv4 prefix ipv4 address/prefix or cpe-domain ipv6 prefix ipv6 address/prefix5. endor commit

DETAILED STEPS




Step 1




Step 2


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring CPE Domain Parameters


Defines the service type keyword definition for the CGv6MAP-Eapplication.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typemap-e m1RP/0/RP0/CPU0:router(config-cgn-map_e)#

Step 3

Configures the IPv4 or IPv6 prefixes of the CPE domain.cpe-domain ipv4 prefix ipv4 address/prefix orcpe-domain ipv6 prefix ipv6 address/prefix

Step 4

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#cpe-domain ipv4 prefix 10.2.2.24/2RP/0/RP0/CPU0:router(config-cgn-map_e)#orRP/0/RP0/CPU0:router(config-cgn-map_e)#cpe-domain ipv6 prefix 2001:da8:a464::/48RP/0/RP0/CPU0:router(config-cgn-map_e)#


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






• Use the commit command to save the configurationchanges to the running configuration file and remain withinthe configuration session.

Configuring Path MTU of the TunnelPerform this task to configure the path Maximum Transmission Unit (MTU) of the tunnel.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Path MTU of the Tunnel

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. path-mtu value5. endor commit

DETAILED STEPS




Step 1




Step 2





Step 3

Configures the path MTU of the tunnel. The range is from 1280 to9216.

path-mtu value

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#path-mtu 1300RP/0/RP0/CPU0:router(config-cgn-map_e)#

Step 4







◦Entering no exits the configuration session and returns therouter to EXEC mode without committing theconfiguration changes.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Path MTU of the Tunnel




Configuring Port Sharing RatioPerform this task to configure the sharing ratio of the port.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-e instance-name4. sharing-ratio number5. endor commit

DETAILED STEPS




Step 1




Step 2





Step 3


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Port Sharing Ratio


Configures the port sharing ratio. The range is from 1 to 32768.The value is expressed in powers of2.

Notesharing-ratio number

Example:RP/0/RP0/CPU0:router(config-cgn-map_e)#sharing-ratio 64RP/0/RP0/CPU0:router(config-cgn-map_e)#

Step 4










Configuring MAP-TPerform these tasks to configure MAP-T.

MAP-T is supported only on Cisco ASR 9000 Series 400G and 200GModular Line Cards and Cisco ASR9000 Series 4-Port and 8-Port 100 Gigabit Ethernet Line Cards.

Note

Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for MAP-T.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring MAP-T





Warning


Caution


SUMMARY STEPS

1. configure2. interface ServiceApp value3. service cgn instance-name service-type map-t4. endor commit

DETAILED STEPS




Step 1




Step 2


service cgn instance-name service-typemap-t

Example:RP/0/RP0/CPU0:router(config-if)# servicecgn cgn1 service-type map-t map1

Step 3



Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Application Service Virtual Interface









Configuring a MAP-T InstancePerform this task to configure a MAP-T instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. end or commit

DETAILED STEPS




Step 1


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring a MAP-T Instance


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



Step 2

Configures the service type keyword definition for CGv6 MAP-Tapplication

service-type map-t instance-name

Example:RP/0/RP0/CPU0:router(config-cgn)#service-type map-t map-t-instRP/0/RP0/CPU0:router(config-cgn-mapt)#

Step 3


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

Step 4



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

[cancel]:






Configuring Address FamilyPerform these tasks to configure address family.


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring the Policy Functions

Configuring IPv4 Address FamilyPerform these tasks configure IPv4 address family for a MAP-T instance.

Configuring an IPv4 Interface

Perform this task to configure an IPv4 interface for a MAP-T instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. address-family ipv4 interface ServiceApp number5. endor commit

DETAILED STEPS




Step 1




Step 2

Configures the service type keyword definition for CGv6MAP-T application.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-type map-tmap-t-instRP/0/RP0/CPU0:router(config-cgn-mapt)#

Step 3

Configures the IPv4 interface to divert IPv4MAP-T traffic.address-family ipv4 interface ServiceApp number

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#address-familyipv4 interface serviceApp 66RP/0/RP0/CPU0:router(config-cgn-mapt-afi)

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-mapt-afi)# endorRP/0/RP0/CPU0:router(config-cgn-mapt-afi)# commit






◦Entering yes saves configuration changes to therunning configuration file, exits theconfiguration session, and returns the router toEXEC mode.




Configuring IPv4 TCP Maximum Segment Size (MSS)

Perform this task to configure the MSS for TCP in bytes.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. address-family ipv4 tcp mss value5. endor commit

DETAILED STEPS




Step 1




Step 2







Step 3

Configures the MSS for TCP in bytes.address-family ipv4 tcp mss value

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#address-familyipv4 tcp mss 66RP/0/RP0/CPU0:router(config-cgn-mapt-afi)

Step 4









Configuring IPv4 Type of Service (ToS)

Perform this task to configure the configured ToS value to be used when translating a packet from IPv6 toIPv4.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. address-family ipv4 tos value5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the TOS value.address-family ipv4 tos value

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#address-familyipv4 tos 66RP/0/RP0/CPU0:router(config-cgn-mapt-afi)

Step 4












Configuring IPv6 Address FamilyPerform these tasks configure an IPv6 address family.

Configuring IPv6 Do not Fragment (DF) Override

Perform this task to enable DF override configuration.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. address-family ipv6 df-override5. endor commit

DETAILED STEPS




Step 1




Step 2



Example:RP/0/RP0/CPU0:router(config-cgn)# service-type map-tmap-t-instRP/0/RP0/CPU0:router(config-cgn-mapt)

Step 3




Configures the DF-Override.address-family ipv6 df-override

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#address-familyipv6 df-overrideRP/0/RP0/CPU0:router(config-cgn-mapt-afi)

Step 4









Configuring an IPv6 Interface

Perform this task to configure an IPv6 interface for a stateful NAT64 instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat64 stateful instance-name4. address-family ipv6 interface ServiceApp number5. endor commit



DETAILED STEPS




Step 1

Configures the instance for the CGv6 applicationand enters CGv6 configuration mode.



Step 2

Configures the service type keyword definitionfor CGv6 Stateful NAT64 application.



Step 3

Configures the IPv6 interface to divert IPv6nat64 traffic.

address-family ipv6 interface ServiceApp number

Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)#address-familyipv4 interface ServiceApp 66RP/0/RP0/CPU0:router(config-cgn-nat64-stful-afi)

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stful-afi)# endorRP/0/RP0/CPU0:router(config-cgn-nat64-stful-afi)# commit


Uncommitted changes found, committhem before exiting (yes/no/cancel)?[cancel]:


◦Entering no exits the configurationsession and returns the router toEXECmode without committing theconfiguration changes.






Configuring IPv6 TCP Maximum Segment Size (MSS)

Perform this task to configure the MSS for TCP in bytes.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. address-family ipv6 tcp mss value5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the MSS for TCP in bytes.address-family ipv6 tcp mss value

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#address-familyipv6 tcp mss 66RP/0/RP0/CPU0:router(config-cgn-mapt-afi)

Step 4












Configuring IPv6 Traffic-Class

Perform this task to configure a traffic-class.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type nat64 stateful instance-name4. address-family ipv6 traffic-class value5. endor commit

DETAILED STEPS




Step 1

Configures the instance for the CGv6 applicationand enters CGv6 configuration mode.



Step 2




Configures the service type keyword definitionfor CGv6 Stateful NAT64 application.



Step 3

Configures the traffic class to be set.address-family ipv6 traffic-class value

Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stateful)#address-familyipv6 traffic-class 66RP/0/RP0/CPU0:router(config-cgn-nat64-stful-afi)

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-nat64-stful-afi)# endorRP/0/RP0/CPU0:router(config-cgn-nat64-stful-afi)# commit


Uncommitted changes found, committhem before exiting (yes/no/cancel)?[cancel]:


◦Entering no exits the configurationsession and returns the router toEXECmodewithout committing theconfiguration changes.



Configuring Contiguous Ports

Perform this task to configure contiguous ports.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. contiguous-ports number5. endor commit

DETAILED STEPS




Step 1

Configures the instance for the CGv6 application andenters CGv6 configuration mode.



Step 2




Step 3

Configures the number of ports and the value is expressedin powers of 2. The range is from 1 to 65536.

contiguous-ports number

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#contiguous-ports14RP/0/RP0/CPU0:router(config-cgn-mapt)

Step 4


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


Uncommitted changes found, commit thembefore exiting (yes/no/cancel)?[cancel]:








Configuring Customer Premise Equipment Domain Parameters

Perform this task to configure Customer Premise Equipment (CPE) domain parameters.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. cpe-domain ipv4 prefix ipv4 address/prefix or cpe-domain ipv6 prefix ipv6 address/prefix5. endor commit

DETAILED STEPS




Step 1




Step 2



Example:RP/0/RP0/CPU0:router(config-cgn)# service-typemap-t map-t-instRP/0/RP0/CPU0:router(config-cgn-mapt)

Step 3

Configures the cpe domain parameters.cpe-domain ipv4 prefix ipv4 address/prefix orcpe-domain ipv6 prefix ipv6 address/prefix

Step 4




Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#acpe-domainipv4 prefix 10.2.2.24/2RP/0/RP0/CPU0:router(config-cgn-mapt)orRP/0/RP0/CPU0:router(config-cgn-mapt)#acpe-domainipv6 prefix 10:2::2/24RP/0/RP0/CPU0:router(config-cgn-mapt)









Configuring External Domain Parameters

Perform this task to configure external domain parameters.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. external-domain ipv6 prefix ipv6 address/prefix5. endor commit



DETAILED STEPS




Step 1

Configures the instance for the CGv6 application andenters CGv6 configuration mode.



Step 2




Step 3

Configures the external domain parameters.external-domain ipv6 prefix ipv6 address/prefix

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#external-domainipv6 prefix 10:2::2/24RP/0/RP0/CPU0:router(config-cgn-mapt)

Step 4




Uncommitted changes found, commit thembefore exiting (yes/no/cancel)?[cancel]:


◦Entering no exits the configuration sessionand returns the router to EXEC mode withoutcommitting the configuration changes.





Configuring Port Sharing Ratio

Perform this task to configure port sharing ratio.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type map-t instance-name4. sharing-ratio number5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the port sharing ratio and the value is expressedin powers of 2. The range is from 1 to 32768.

sharing-ratio number

Example:RP/0/RP0/CPU0:router(config-cgn-mapt)#sharing-ratio14RP/0/RP0/CPU0:router(config-cgn-mapt)

Step 4












Configuring 6RD on ISMPerform these tasks to configure 6RD on ISM.

Configuring the Application Service Virtual InterfaceThis section lists the guidelines for selecting service application interfaces for 6RD





Warning


Caution



Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring 6RD on ISM

SUMMARY STEPS

1. configure2. interface ServiceApp value3. service cgn instance-name4. service-type tunnel v6rd instance-name5. endor commit

DETAILED STEPS




Step 1




Step 2

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


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

Step 3

Configures the service-type as tunnel v6rd, and the instance nameas 6rd1.

service-type tunnel v6rd instance-name

Example:RP/0/RP0/CPU0:router(config-cgn)# service-typetunnel v6rd 6rd1RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)

Step 4


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



orRP/0/RP0/CPU0:router(config-cgn-tunnel-v6rd)#commit








Configuring a 6RD Instance

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. endor commit

DETAILED STEPS




Step 1




Step 2

Configures the service-type as tunnel v6rd, and the instance nameas 6rd1.


Example:RP/0/RP0/CPU0:router(config-cgn)# service-typetunnel v6rd 6rd1RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)

Step 3


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






orRP/0/RP0/CPU0:router(config-cgn-tunnel-v6rd)#commit






Configuring Address Family

Perform these tasks to configure address family for a 6RD instance.

Configuring IPv4 Address Family

Perform this task to configure IPv4 address family for a 6RD instance.


Perform this task to configure an IPv4 interface for a 6RD instance.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. address-family ipv4 interface ServiceApp number5. endor commit

DETAILED STEPS




Step 1




Step 2

Defines the service type keyword definition for CGv6 6RDapplication.


Example:RP/0/RP0/CPU0:router(config-cgn)#service-type tunnel v6rd 6rd1RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)

Step 3

Configures the IPv4 interface to divert IPv4 6RD traffic. The rangeis from 1 to 2000.


Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#address-family ipv4 interface serviceApp 66RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#

Step 4


Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#end



orRP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#commit








Configuring IPv6 Address Family

Perform this task to configure an IPv6 address family for a 6RD instance.


Perform this task to configure an IPv6 interface for a 6RD instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. address-family ipv6 interface ServiceApp number5. endor commit

DETAILED STEPS




Step 1




Step 2







Step 3

Configures the IPv6 interface to divert IPv4 6RD traffic. The rangeis from 1 to 2000.


Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#address-family ipv6 interface serviceApp 66

Step 4

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










Configuring Border Relay

Perform these tasks to configure a border relay router for a 6RD instance.

Configuring IPv4 InterfacePerform this task to configure an IPv4 interface for a border relay router.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. br ipv4 prefix | suffix length value5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the IPv4 interface for a border relay router. The IPv4prefix or suffix length is used to derive delegated IPv6 prefix.

br ipv4 prefix | suffix length value

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#br ipv4 prefix length 20

Step 4

The prefix or suffix value range is from 0 to 31.














Configuring IPv6 PrefixPerform this task to configure IPv6 address and prefix for a border relay router.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. br ipv6 prefixaddress5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the IPv6 address and prefix for a border relay router.br ipv6 prefixaddress

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#br ipv6-prefix 2001:db8::/32

Step 4














Configuring Source AddressPerform this task to configure IPv4 source address for a tunnel.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. br source-addressaddress5. endor commit

DETAILED STEPS




Step 1







Step 2




Step 3

Configures the IPv4 source address for a tunnel.br source-addressaddress

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#br source-address 22.23.24.26

Step 4











Configuring Unicast AddressPerform this task to configure IPv6 unicast address.



SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. br unicast addressaddress5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Configures the IPv6 address that is unicast from the IPv6 network.br unicast addressaddress

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#br unicast address 3001:db8:1617:181a::1

Step 4














Configuring Maximum Transmission Unit

Perform this task to configure the Maximum Transmission Unit (MTU) of the tunnel for a 6RD instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. path-mtu value5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3




Configures the path mtu of the tunnel. The range is from 1280 to9216.

path-mtu value

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#path-mtu 1282

Step 4











Configuring Reassembly-Enable

Perform this task to assemble the fragmented packets for a 6RD instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. reassembly-enable5. endor commit



DETAILED STEPS




Step 1




Step 2




Step 3

Assembles the fragmented packets after forwarding is complete.reassembly-enable

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#reassembly-enable

Step 4













Configuring Reset-df-bit

Perform this task to reset the df bit and enable the anycast feature for a 6RD instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. reset-df-bit5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3

Resets the df bit and enables the anycast feature.reset-df-bit

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#reset-df-bit

Step 4














Configuring Type of Service

Perform this task to configure the Type of Service (ToS) to be used for the IPv4 tunnel for a 6RD instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. tos value5. endor commit

DETAILED STEPS




Step 1




Step 2




Step 3




Configures the type of service to be used for the IPv4 tunnel. Therange is from 0 to 255.

tos value

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#tos 66RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#

Step 4










Configuring Time to Live

Perform this task to configure Time to Live (TTL) value to be used for the IPv4 tunnel for a 6RD instance.

SUMMARY STEPS

1. configure2. service cgn instance-name3. service-type tunnel v6rd instance-name4. ttlvalue5. endor commit



DETAILED STEPS




Step 1




Step 2




Step 3

Configures the time-to-live value, in seconds, to be used for theIPv4 tunnel. The range is from 1 to 255.

ttlvalue

Example:RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)#ttl 220

Step 4

RP/0/RP0/CPU0:router(config-cgn-tunnel-6rd)












Configuring High AvailabilityISM and VSM supports high availability or 1:1 redundancy on different CGv6 applications.

Perform these tasks to configure HA.

Configuring Active or Standby ModulePerform this task to configure active or standby module.

SUMMARY STEPS

1. configure2. service cgn <instance name>3. service-location preferred-active node-id[preferred-standby node-id]4. end or commit5. reload

DETAILED STEPS




Step 1

Configures the infrastructure service virtual interface (SVI) for boththe module locations.

service cgn <instance name>

Example:RP/0/RP0/CPU0:router(config)# servicecgn cgn1

Step 2

Configures the preferred active and preferred standby nodes.service-location preferred-activenode-id[preferred-standby node-id]

Step 3

Example:RP/0/RP0/CPU0:router(config-if)#service-location preferred-active0/1/CPU0 preferred-standby 0/4/CPU0


Example:

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



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


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring High Availability






Once the configuration is complete, reload both the cards for changesto take effect and wait till in ‘APP READY’ state.

reload

Example:RP/0/RP0/CPU0:router#hw-mod location0/1/CPU0 reload

Step 5

Enabling Failure DetectionPerform this task to enable failure detection.

SUMMARY STEPS

1. configure2. service-cgv6-ha location node-iddatapath-test3. end or commit

DETAILED STEPS




Step 1

Configures role as CGv6 and failure detection for datapath tests.service-cgv6-ha locationnode-iddatapath-test

Step 2


Carrier Grade IPv6 over Integrated Services Module (ISM)Enabling Failure Detection


Example:RP/0/RP0/CPU0:router(config)#service-cgv6-ha location 0/1/CPU0datapath-test


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

•When you issue the end command, the system prompts you to commitchanges:


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

◦Entering yes saves configuration changes to the running configurationfile, exits the configuration session, and returns the router to EXECmode.

◦Entering no exits the configuration session and returns the router toEXEC mode without committing the configuration changes.

◦Entering cancel leaves the router in the current configuration sessionwithout exiting or committing the configuration changes.

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

By default, failure detection for data path is not triggered unless theabove commands are configured.

Note

To disable failure detection, use the no form of the command: no service-cgv6-halocation node-iddatapath-test

Configuration Examples for Implementing the Carrier GradeNAT

This section provides the following configuration examples for CGN:

Configuring a Different Inside VRF Map to a Different Outside VRF: ExampleThis example shows how to configure a different inside VRF map to a different outside VRF and differentoutside address pools:service cgn cgn1inside-vrf insidevrf1map outside-vrf outsidevrf1 address-pool 100.1.1.0/24!!


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuration Examples for Implementing the Carrier Grade NAT

inside-vrf insidevrf2map outside-vrf outsidevrf2 address-pool 100.1.2.0/24!service-location preferred-active 0/2/cpu0 preferred-standby 0/3/cpu0!interface ServiceApp 1vrf insidevrf1ipv4 address 210.1.1.1 255.255.255.0service cgn cgn1!router staticvrf insidevrf10.0.0.0/0 serviceapp 1!!interface ServiceApp 2vrf insidevrf2ipv4 address 211.1.1.1 255.255.255.0service cgn cgn1service-type nat44 nat1!router staticvrf insidevrf20.0.0.0/0 serviceapp 2!!interface ServiceApp 3vrf outsidevrf1ipv4 address 1.1.1.1 255.255.255.0service cgn cgn1service-type nat44 nat1!router staticvrf outsidevrf1100.1.1.0/24 serviceapp 3!!interface ServiceApp 4vrf outsidevrf2ipv4 address 2.2.2.1 255.255.255.0service cgn cgn1service-type nat44 nat1!router staticvrf outsidevrf2100.1.2.0/24 serviceapp 4!

Configuring Different Inside VRF Maps to Identical Outside VRF maps for NAT44:Example

This example shows how to configure different inside VRF maps to identical outside VRF maps:

Configure outsideServiceApp in the CGN configuration for the following ServiceApp pair:Note

• Two different inside vrf

• Two identical outside vrf

service cgn cgn-service-kykwifiservice-location preferred-active 0/0/CPU0service-type nat44 kykwifi-nat44portlimit 512alg ActiveFTP


Carrier Grade IPv6 over Integrated Services Module (ISM)Configuring Different Inside VRF Maps to Identical Outside VRF maps for NAT44: Example

alg rtspalg pptpAlginside-vrf INTERNET_PRIVATE_CGNATmap outside-vrf INTERNET outsideServiceApp ServiceApp2 address-pool 81.213.32.0/22external-logging syslogserveraddress 10.106.61.20 port 514!!inside-vrf INTERNET_PRIVATE_CGNAT2map outside-vrf INTERNET outsideServiceApp ServiceApp4 address-pool 81.213.36.0/22external-logging syslogserveraddress 10.106.61.20 port 514!

NAT44 Configuration: ExampleThis example shows 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.0encapsulation dot1q 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.0encapsulation dot1q 1!interface GigabitEthernet0/6/5/1.1vrf OutsideCustomer1ipv4 address 10.12.13.2 255.255.255.0encapsulation dot1q 1!interface ServiceApp1


Carrier Grade IPv6 over Integrated Services Module (ISM)NAT44 Configuration: Example

vrf 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.0


Carrier Grade IPv6 over Integrated Services Module (ISM)NAT44 Configuration: Example

encapsulation dot1q 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 Configuration: ExampleThis example shows 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


Carrier Grade IPv6 over Integrated Services Module (ISM)NAT64 Stateless Configuration: Example

!!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 !

!

DS Lite Configuration: Example

IPv6 ServiceApp and Static Route Configurationconfint serviceApp61

service cgn cgn1 service-type ds-liteipv6 address 2001:202::/32commit

exit

router staticaddress-family ipv6 unicast3001:db8:e0e:e01::/128 ServiceApp61 2001:202::2commitexit

end

IPv4 ServiceApp and Static Route Configurationconfint serviceApp41

service cgn cgn1 service-type ds-liteipv4 add 41.41.41.1/24commit

exit


Carrier Grade IPv6 over Integrated Services Module (ISM)DS Lite Configuration: Example

router staticaddress-family ipv4 unicast52.52.52.0/24 ServiceApp41 41.1.1.2commitexit

end

DS Lite Configurationservice cgn cgn1service-location preferred-active 0/2/CPU0 preferred-standby 0/4/CPU0service-type ds-lite dsl1portlimit 200bulk-port-alloc size 128map address-pool 52.52.52.0/24aftr-tunnel-endpoint-address 3001:DB8:E0E:E01::address-family ipv4interface ServiceApp41

address-family ipv6interface ServiceApp61

protocol tcpsession init timeout 300session active timeout 400mss 1200

external-logging netflow9serveraddress 90.1.1.1 port 99

external-logging syslogserveraddress 90.1.1.1 port 514

Bulk Port Allocation and Syslog Configuration: Exampleservice cgn cgn2service-type nat44 natAinside-vrf broadbandmap address-pool 100.1.2.0/24external-logging syslogserveraddress 20.1.1.2 port 514!!bulk-port-alloc size 64!!

DBL Configuration: Example

NAT44 Instanceservice cgn cgn1service-type nat44 nat1inside-vrf ivrfexternal-logging netflow version 9serveraddress x.x.x.x port xsession-logging


Carrier Grade IPv6 over Integrated Services Module (ISM)Bulk Port Allocation and Syslog Configuration: Example

DS-Lite Instanceservice cgn cgn1service-type ds-lite ds-lite1external-logging netflow9server session-logging

Services Redundancy Configuration (Active/Standby): ExampleActive Configurationconf tinterface ServiceInfra 1service-location 0/1/CPU0ipv4 address 50.1.1.1/24exit

hw-module service cgn location 0/1/CPU0commitexitStand By Configurationconf tinterface ServiceInfra 2service-location 0/2/CPU0ipv4 address 100.1.1.1/24exit

hw-module service cgn location 0/2/CPU0commitexitconf tservice cgn cgn1service-location preferred-active 0/1/CPU0 preferred-standby 0/2/CPU0commitexit

6RD Configuration: ExampleThis example shows a sample 6RD configuration:vrf ivrf!hw-module service cgn location 0/0/CPU0hw-module service cgn location 0/2/CPU0interface ServiceApp41vrf ivrfipv4 address 5.5.5.1 255.255.0.0service cgn cgn1 service-type tunnel v6rd!interface ServiceApp42ipv4 address 6.6.6.1 255.255.255.0service cgn cgn1 service-type tunnel v6rd!interface ServiceApp61ipv6 address 2001:db8:1617:1819::2/64service cgn cgn1 service-type tunnel v6rd!interface ServiceApp62ipv6 address 3001:db8:1617:181a::2/64service cgn cgn1 service-type tunnel v6rd!interface ServiceInfra1ipv4 address 1.1.1.1 255.255.255.0service-location 0/0/CPU0!


Carrier Grade IPv6 over Integrated Services Module (ISM)Services Redundancy Configuration (Active/Standby): Example

interface ServiceInfra2ipv4 address 2.2.2.2 255.255.255.0service-location 0/2/CPU0!router staticaddress-family ipv4 unicast8.37.0.0/16 8.36.0.18.42.25.0/24 8.36.5.210.1.2.0/24 GigabitEthernet0/3/0/210.64.83.49/32 8.36.0.122.23.24.26/32 6.6.6.2102.2.0.0/16 ServiceApp3192.168.3.0/24 GigabitEthernet0/3/0/3192.168.3.0/24 GigabitEthernet0/3/0/4202.153.144.0/24 8.36.0.1!address-family ipv6 unicast2001:db8::/32 ServiceApp612001:db8:1617:1819::/64 Null02001:db8:1617:1819::/128 ServiceApp612001:db8:1617:1819::1/128 ServiceApp613001:db8::/32 ServiceApp623001:db8:1617:181a::/64 Null03001:db8:1617:181a::/64 ServiceApp623001:db8:1617:181a::1/128 ServiceApp62!vrf ivrfaddress-family ipv4 unicast0.0.0.0/0 5.6.5.222.23.24.25/32 5.5.5.2192.168.3.5/32 10.1.2.3!!!service cgn cgn1service-location preferred-active 0/2/CPU0 preferred-standby 0/0/CPU0service-type tunnel v6rd 6rd1ttl 255path-mtu 1480bripv6-prefix 2001:db8::/32source-address 22.23.24.25unicast address 2001:db8:1617:1819::1!address-family ipv4interface ServiceApp41!address-family ipv6interface ServiceApp61!!service-type tunnel v6rd 6rd2bripv6-prefix 3001:db8::/32source-address 22.23.24.26unicast address 3001:db8:1617:181a::1!address-family ipv4interface ServiceApp42!address-family ipv6interface ServiceApp62!!!


Carrier Grade IPv6 over Integrated Services Module (ISM)6RD Configuration: Example

MAP-E Configuration on ISM: ExampleThis example shows a sample MAP-E configuration on ISM:hw-module service cgn location 0/0/CPU0interface ServiceApp1ipv4 address 30.30.30.1 255.255.255.0service cgn cgn1 service-type map-e m1!interface ServiceApp2ipv4 address 19.1.1.1 255.255.255.252ipv6 address 2001:101::/32service cgn cgn1 service-type map-e m1!interface ServiceInfra1ipv4 address 200.1.1.1 255.255.255.0service-location 0/0/CPU0!router staticaddress-family ipv4 unicast202.38.102.0/24 ServiceApp1 30.30.30.2!address-family ipv6 unicast2001:da8:a464:ffff::/64 ServiceApp2 2001:101::2!service cgn cgn1service-location preferred-active 0/0/CPU0service-type map-e m1cpe-domain ipv6 prefix 2001:da8:a464::/48cpe-domain ipv4 prefix 202.38.102.0/24aftr-endpoint-address 2001:da8:a464:ffff::/128sharing-ratio 16contiguous-ports 32path-mtu 1300

address-family ipv4interface ServiceApp1tcp mss 235

!address-family ipv6interface ServiceApp2tcp mss 1154!!

MAP-T Configuration on ISM: Examplehw-module service cgn location 0/0/CPU0interface ServiceApp4ipv4 address 30.30.30.1 255.255.255.0service cgn test service-type map-t!interface ServiceApp6ipv4 address 19.1.1.1 255.255.255.252ipv6 address 2001:101::/32service cgn test service-type map-t!interface ServiceInfra1ipv4 address 200.1.1.1 255.255.255.0service-location 0/0/CPU0!router staticaddress-family ipv4 unicast202.38.102.0/24 ServiceApp4 30.30.30.2!address-family ipv6 unicast


Carrier Grade IPv6 over Integrated Services Module (ISM)MAP-E Configuration on ISM: Example

2001:da8:a464:ffff::/64 ServiceApp6 2001:101::2!service cgn testservice-location preferred-active 0/0/CPU0service-type map-t xlat1cpe-domain ipv6 prefix 2001:da8:a464::/48cpe-domain ipv4 prefix 202.38.102.0/24external-domain ipv6 prefix 2001:da8:a464:ffff::/64sharing-ratio 64contiguous-ports 128

address-family ipv4interface ServiceApp4

tcp mss 235tos 100!

address-family ipv6interface ServiceApp6tcp mss 1154traffic-class 100df-override;!!

PPTP ALG Configuration: Example

NAT44 Instanceservice cgn cgn1service-location preferred-active 0/1/CPU0service-type nat44 inst1alg pptpAlg

•


Carrier Grade IPv6 over Integrated Services Module (ISM)PPTP ALG Configuration: Example


Carrier Grade IPv6 over Integrated Services Module (ISM)PPTP ALG Configuration: Example

carrier grade ipv6 over integrated services module (ism)€¦ · carrier grade ipv6 over integrated...

Documents