Inline 6rd and 6to4 Softwires
Inline 6rd and 6to4 Configuration Guidelines
Keep the following points in mind when you are configuring and using inline 6rd and 6to4.
You can configure a maximum of 1024 softwire concentrators on a single line card.
Reassembly of 6rd IPv4 packet from CE is not added as part of this release.
6rd multicast is not supported.
Any ICMPv4 errors generated in the IPv4 access network (between CPE and border relays) are dropped on the border relay. They are not converted into IPv6 errors and forwarded to IPv6 side.
6rd/6to4 Anycast and load balancing can be configured only using next-hop style service-interface configuration, not interface style.
The si- interface input features are not exercised for packets flowing to the 6rd tunnel.
Bandwidth for traffic from the 6rd tunnel is limited by the available PFE bandwidth; bandwidth for traffic to the 6rd tunnel is limited by the internal VRF loopback bandwidth. SI-IFD loopback bandwidth configuration under the [edit chassis] hierarchy has no impact on the 6rd loopback bandwidth.
If the packet length is more than Tunnel MTU for downlink packets after encapsulating with an IPv4 header, the packet is dropped as v4 MTU errors. For these packet drops an ICMPv6 packet too big error message is sent back to the sender. Typically 6rd Tunnel MTU is configured with a high value so if the packet size is larger than the configured value, fragmentation occurs at the egress interface (towards the IPv4 access network).
Configuring Inline 6rd
Junos OS supports inline 6rd on all Modular Port Concentrator (MPC) line cards on MX Series routers. This saves customers the cost of using MS-DPCs for the required tunneling, encapsulation, and decapsulation processes. Anycast is supported for 6to4 (next-hop service interfaces only). Hairpinning is also supported for traffic between 6rd domains.
Junos OS supports inline 6rd on the following MPCs:
MPC5 and MPC6—Support starting in Junos OS Release 15.1R3.
MPC7, MPC8, and MPC9—Support starting in Junos OS Release 17.2R1.
MPC10E-15C-MRATE and MPC10E-10C-MRATE—Support starting in Junos OS Release 20.3R1.
MX2K-MPC11E—Support starting in Junos OS Release 20.3R1.
To implement the inline functionality, you configure service interfaces on the MPC as inline services interfaces (si-) rather than as multiServices (ms-) interfaces.
Configuring the Bandwidth for Inline Services
You must provide bandwidth configuration for inline services on the modular port concentrator (MPC) used for inline 6rd processing.
To configure bandwidth:
- Specify the MPC and logical interface, and the desired
bandwidth, 1g or 10g.user@host# set chassis fpc mpc-number pic logical-interface-number inline-services bandwidth bandwidth
For example:
user@host# set chassis fpc 0 pic 0 inline-services bandwidth 10g
Configuring the Interfaces
Configure the si- interfaces for 6rd control and data. 6rd services must be configured on port 0.
To configure the si- interfaces:
- Configure the 6rd services on port 0 and include units
for IPv4 and IPv6.user@host# set interfaces si-mpc-number/logical-interface-number/0 unit 0 family inetuser@host# set interfaces si-mpc-number/logical-interface-number/0 unit 0 family inet6
For example:
user@host# set interfaces si-0/0/0 unit 0 family inetuser@host# set interfaces si-0/0/0 unit 0 family inet6 - Configure the media interfaces for the inside service
domain.user@host# set interfaces si-mpc-number/logical-interface-number/0 unit unit-number family inetuser@host# set interfaces si-mpc-number/logical-interface-number/0 unit unit-number family inet6user@host# set interfaces si-0/0/0 unit unit-number service-domain inside
For example:
user@host# set interfaces si-0/0/0 unit 1 family inetuser@host# set interfaces si-0/0/0 unit 1 family inet6user@host# set interfaces si-0/0/0 unit 1 service-domain inside - Configure the media interfaces for the outside service
domain.user@host# set interfaces si-mpc-number/logical-interface-number/0 unit unit-number family inetuser@host# set interfaces si-mpc-number/logical-interface-number/0 unit unit-number family inet6user@host# set interfaces si-mpc-number/logical-interface-number/0 unit unit-number service-domain outside
For example:
user@host# set interfaces si-0/0/0 unit 2 family inetuser@host# set interfaces si-0/0/0 unit 2 family inet family inet6user@host# set interfaces si-mpc-number/logical-interface-number/0 unit unit-number service-domain outside - Configure the IPv4-facing interface for use with an interface-style
or next-hop service set.
To configure for use with an interface-style service set, configure input and output service and specify the service set.
user@host# set interfaces ge-mpc-number/logical-interface-number/port unit unit-number family inet service input service-set service-set-nameuser@host# set interfaces ge-mpc-number/logical-interface-number/port unit unit-number family inet service output service-set service-set-nameuser@host# set interfaces ge-mpc-number/logical-interface-number/port unit unit-number family inet address ip-addressFor example:
user@host# set interfaces ge-0/2/7 unit 0 family inet service input service-set vrf-intf-service-setuser@host# set interfaces ge-0/2/7 unit 0 family inet service output service-set vrf-intf-service-setuser@host# set interfaces ge-0/2/7 unit 0 family inet address 10.10.10.1/16To configure for use with a next-hop style service set, omit the service input and service output references.
user@host# set interfaces ge-mpc-number/logical-interface-number/port unit unit-number family inetuser@host# set interfaces ge-mpc-number/logical-interface-number/port unit unit-number family inet address ip-addressFor example:
user@host# set interfaces ge-0/2/7 unit 0 family inetuser@host# set interfaces ge-0/2/7 unit 0 family inet address 10.10.10.1/16
- Configure the IPv6 facing interface.user@host# set interfaces ge-mpc-number/logical-interface-number/port unit unit-number family inet6 address ipv6-address
For example:
user@host# set interfaces ge-0/2/8 unit 0 family inet6 address 3abc::1/16
Configuring the Softwire Concentrator and Rule
Define the softwire concentrator and rule used for encapsulation and decapsulation of IPv6 over IPv4 packets for CE.
To define the softwire concentrator:
- Specify a 6rd softwire concentrator and its address.user@host# set services softwire softwire-concentrator v6rd concentrator-name softwire-address ip-address
For example:
user@host# set services softwire softwire-concentrator v6rd swire01-rd1 softwire-address 30.30.30.1 - Configure the IPv4 address prefix for the customer edge
network and the IPv6 address prefix for the 6rd domain.user@host# set services softwire softwire-concentrator v6rd concentrator-name ipv4-prefix ipv4-prefix v6rd-prefix v6rd-prefix
For example:
user@host# set services softwire softwire-concentrator v6rd swire01-rd1 ipv4-prefix 10.10.0.0/16 v6rd-prefix 3040::0/16 - Configure the size, in bytes, of the maximum transmission
unit mtu-ipv4 for IPv6 packets encapsulated in IPv4. Compute
this as the maximum expected IPv4 packet size plus 20.user@host# set services softwire softwire-concentrator v6rd concentrator-name set mtu-ipv4 number-of-bytes
For example:
user@host# set services softwire softwire-concentrator v6rd swire01-rd1 set mtu-ipv4 9192
To configure the softwire rule:
- Specify the softwire rule, specifying the direction of
traffic to be tunneled and the 6rd softwire concentrator to be used.user@host# set services softwire rule softwire-rule-name match-direction match-direction term rule-term-number then v6rd concentrator-name
For example:
user@host# set services softwire rule swire01-r1 match-direction input term t1 then v6rd swire01-rd1
Configuring the Service Set
To configure an interface style or next-hop service set for 6rd processing:
- Specify an interface style service set.user@host# set services service-set service-set-name softwire-rules softwire-rule-name service-interface interface-name
For example:
user@host# set services service-set vrf-intf-service-set softwire-rules swire01-r1 service-interface si-0/0/0.0or
- Configure a next-hop service set.user@host# set services service-set service-set-name softwire-rules softwire-rule-nameuser@host# set services service-set service-set-name next-hop-service inside-service-interface inside-interface outside-service-interface outside-interfaceuser@host# set services service-set vrf-nh-service-set softwire-rules swire01-r1user@host# set services service-set vrf-nh-service-set next-hop-service inside-service-interface si-0/0/0.1 outside-service-interface si-0/0/0.2
Configuring the Routing Instance
To configure the routing instance:
- Specify the routing instance and each interface it serves.user@host# set routing-instance routing-instance-name instance-type vrf interface interface-name
For example:
user@host# set routing-instance v6rd-vrf instance-type vrf interface si-0/0/0.1user@host# set routing-instance v6rd-vrf instance-type vrf interface interface ge-0/2/7.0 - Specify the route distinguisher and vrf-target.user@host# set routing-instance v6rd-vrf route-distinguisher 1.1.1.1:1user@host# set routing-instance v6rd-vrf vrf-target target:100:100
Examples: 6rd and 6to4 Configurations
The 6rd and 6to4 features are supported on Multiservices 100, 400, and 500 PICs on M Series routers, and on MX Series routers equipped with Multiservices DPCs. MX Series routers with MS-MPCs or MS-MICs support inline 6rd and inline 6to4 features.
Example: 6rd with Interface-Style Service Set Configuration
Example: 6rd with Next-Hop-Style Service Set Configuration
Example: 6rd Anycast Configuration
Example: Hairpinning Between 6rd Domains Configuration
This example uses an interface service-set and a next-hop service set as hairpinning domains.