Although Juniper Networks has attempted to provide accurate information in this guide, Juniper Networks does not warrant or guarantee the accuracy of the
information provided herein. Third party product descriptions and related technical details provided in this document are for information purposes only and such
products are not supported by Juniper Networks. All information provided in this guide is provided "as is", with all faults, and without warranty of any kind, either
expressed or implied or statutory. Juniper Networks and its suppliers hereby disclaim all warranties related to this guide and the information contained herein,
whether expressed or implied of statutory including, without limitation, those of merchantability, fitness for a particular purpose and noninfringement, or arising
from a course of dealing, usage, or trade practice.
Page 1
Third party product descriptions and related technical details provided in this document are for information purposes only and such products are not supported by Juniper Networks. All information provided in this guide is provided “as is”, with all faults, and without warranty of any kind, either expressed or implied or statutory.
4 Terminology • 6rd prefix: This is an IPv6 prefix selected by the service provider for use by a 6rd domain. There is exactly one 6rd prefix for a given 6rd domain. An SP can deploy 6rd with a single 6rd domain or multiple 6rd domains.
Hairpinning traffic occurs between two 6rd domains. • 6rd anycast is where a 6rd domain can be hosted on multiple S-PICs with one S-PIC actively handling all 6rd traffic at any given time.6to4: 6to4 is an IPv4 tunnel-based transition mechanism defined in RFC-3056. It was designed to allow different IPv6 domains communicate with other IPv6 domains through IPv4 clouds without explicit IPv4 tunnels.
7 Configuration Examples In this section, an MX Series router is configured with an MS-DPC as a 6rd Border relay. The 6rd feature is supported in a layer 3 package only. Assume that the PIC is in fPC 3 slots 0 and 1:...
IMPLEMENTATION GUIDE - 6rd Configuration Guide 7.2 Basic 6rd Configuration To configure 6rd, the user must configure the softwire rule. A sample softwire rule looks like the following: [edit services] user@router# show softwire softwire-concentrator { v6rd v6rd-dom1 { softwire-address 30.30.30.1;...
Once 6rd is configured, the services PIC daemon (spd) on the routing engine installs routes for the softwire concentrator IPv4 address and 6rd domain’s IPv6 prefix so that they point to the S-PIC. for the previous example, the following routes are installed: user@router# run show route 30.30.30.1...
Page 9
In this case, all statically configured routes are exported, and since all services PIC daemon installed routes are static routes, this exports 6rd routes as well. Once the routing policy is in place, apply that to OSPf as in...
IMPLEMENTATION GUIDE -6rd Configuration Guide 7.4.2 Next-hop Style Service Set [edit interfaces] user@router#show interfaces { sp-3/0/0 { unit 0 { family inet; family inet6; unit 1 { family inet; family inet6; service-domain inside; unit 2 { family inet; family inet6;...
--- 30.30.30.1 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss 7.6 6rd Domain to Internet This example describes how a 6rd concentrator can be configured for a 6rd domain, D1, to provide IPv6 Internet connectivity. 7.6.1 Interfaces Configuration...
It is mandatory to configure a stateful firewall rule that accepts all traffic in both input and output direction for 6rd to work. However, this is not enforced through the CLI. This is because in IPv6, gratuitous v6 packets are expected (due to anycast) to be detected and should not be dropped.
{ accept; 7.7 6to4 Using 6rd This example describes how to implement 6to4 using the 6rd feature. In this example, 6rd domain D3 has an IPv6 prefix of 2002::0/16, which is a well-known 6to4 prefix. 7.7.1 Interfaces Configuration D1 Ingress interface:...
7.8 6rd Anycast (Redundancy) The 6rd anycast feature is used to configure multiple S-PICs to back up a 6rd domain’s traffic. However, for a given 6rd domain, only one S-PIC is actively processing the traffic at any point in time (called primary PIC). Other PICs are in standby mode, but these standby S-PICs can actively process 6rd traffic of some other 6rd domains (possibly provide other services such as NAT, etc).
{ service-interface sp-3/1/0; Note that both the previous service sets use the softwire rule, which refers to the same 6rd domains. 7.8.3 Softwire Concentrator Configuration [edit services] user@router# show softwire softwire-concentrator { v6rd v6rd-dom1 { softwire-address 30.30.30.1;...
Page 20
When sp-3/0/0 goes down, the routes pointing to sp-3/0/0 are deleted and therefore all traffic is now sent to sp- 3/1/0. As there is no state synchronization between S-PICs and 6rd is supposed to be stateless, packet loss is minimal.
IPv6 services over IPv4 infrastructure, there might be situations where a provider might need to deploy both DS-Lite and 6rd. 6rd can be configured with DS-Lite on the same PIC and in the same service set. The following subsections show configuration details of such a scenario where both DS-Lite and 6rd are configured in the same service set.
This service set has a stateful firewall rule and 6rd rule for 6rd service. In addition, there is a softwire rule for DS-Lite and a NAT rule to translate all the DS-Lite traffic. The NAT rule performs NAPT translation in the forward direction on the source address and port of the DS-Lite traffic.
9 Operations and Management There are two classes of commands that can be used to check the workings of the 6rd implementation: CLI and debug. The debug commands are used from the services DPC/PIC console, and the CLI follows the traditional Juniper implementation.
Please refer to the appendix for CLI commands related to 6rd operations. 10 ALG Support Currently, 6rd supports ICMPv6 ALG. The following CLI output shows flows created when a host in the 6rd domain D1 pings a server in the IPv6 Internet.
Page 28
IMPLEMENTATION GUIDE -6rd Configuration Guide 2) CLI Syntax: show services softwire count Description: This CLI will display all the current softwire count for a service set for both Ds-Lite and V6rd. Example: regress@sledding# run show services softwire count Interface Service set...
Page 29
IMPLEMENTATION GUIDE - 6rd Configuration Guide Errors ------ Softwire Creation Failed Flow Creation Failed Slow Path Failed Packet not IPv4-in-IPv6 IPv6 Fragmentation Error Slow Path Failed - IPv6 Next Header Offset Decapsulated Packet not IPv4 Fast Path Failed - IPv6 Next Header Offset...
Page 30
IMPLEMENTATION GUIDE -6rd Configuration Guide 5) CLI Syntax: show services softwire statistics v6rd Description: This CLI will display statistics of v6rd for each service pic. Example: regress@billiard> show services softwire statistics v6rd 6rd Statistics: Service PIC Name :sp-0/1/0 Statistics ----------...
Page 31
IMPLEMENTATION GUIDE - 6rd Configuration Guide Errors ------ Softwire Creation Failed Flow Creation Failed Slow Path Failed Packet not IPv6-in-IPv4 Slow Path Failed - IPv6 Next Header Offset Decapsulated Packet not IPv6 Encapsulation Failed - No packet memory No Softwire ID...
Description: This CLI will filter out flows from CLI “show softwire services flows” based on both specified v6rd initiator ip and concentrator ip. Example: regress@ billiard # run show services softwire flows v6rd concentrator 2.2.2.2 initiator 3.3.3.3 Figure 3: Topology used to illustrate CLI commands for 6rd deployment and operations Router CONFIG : =============== interfaces { sp-0/0/0 {...
Page 33
IMPLEMENTATION GUIDE - 6rd Configuration Guide family inet; family inet6; unit 1 { family inet; family inet6; service-domain inside; unit 2 { family inet; family inet6; service-domain outside; ge-3/1/0 { unit 0 { family inet { address 200.200.200.1/24; ge-3/1/5 { unit 0 { family inet;...
Page 34
IMPLEMENTATION GUIDE -6rd Configuration Guide then { accept; syslog; softwire { ipv6-multicast-interfaces all; softwire-concentrator { ds-lite ds1 { softwire-address 1001::1; mtu-v6 9192; rule dslite-rule { match-direction input; term t1 { then { ds-lite ds1; nat { pool dslite-pool1 { address-range low 33.33.33.1 high 33.33.33.32;...
[rfC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, “Softwire Problem Statement”, rfC 4925, July 2007. About Juniper Networks Juniper Networks is in the business of network innovation. from devices to data centers, from consumers to cloud providers, Juniper Networks delivers the software, silicon and systems that transform the experience and economics of networking.
Need help?
Do you have a question about the 6rd and is the answer not in the manual?
Questions and answers