Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Basic DS-Lite Configuration

Requirements

• M Series Multiservice Edge routers with Multiservices PICs
• T Series Core routers with Multiservices PICs
• MX Series 3D Universal Edge routers with Multiservices DPCs

Configuration Overview and Topology

This example describes how configure an MX Series router with an MS-DPC as an AFTR to facilitate the flow shown in Figure 1.

Figure 1: DS-Lite Topology

In this example, the DS-Lite softwire concentrator, or AFTR, is an MX Series router with two Gigabit interfaces and a Services DPC. The interface facing the B4 element is ge-3/1/5 and the interface facing the Internet is ge-3/1/0.

Configuration

• Chassis Configuration
• Interfaces Configuration
• Network Address and Port Translation Configuration
• Softwire Configuration
• Service Set Configuration

Chassis Configuration

Step-by-Step Procedure

1. Enter the edit chassis hierarchy level.
   user@host# edit chassis
2. Configure the Layer 3 service package.
   [edit chassis]user@host# set fpc 0 pic 0 adaptive-services service-package layer-3

Interfaces Configuration

Step-by-Step Procedure

1. Go the [edit interfaces] edit hierachy level for ge-3/1/0, which faces the Internet.
   host# edit interfaces ge-3/1/0
2. Define the interface.
   [edit interfaces ge-3/1/0]user@host# set description AFTR-Internetuser@host# set unit 0 family inet address 128.0.0.2/24
3. Go to the [edit interfaces] hierachy level for ge-3/1/5, which faces the B4.
   user@host# up 1[edit]user@host# edit interfaces ge-3/1/5
4. Define the interface.
   [edit interfaces ge-3/1/5]user@host# set description AFTR-B4user@host# set unit 0 family inetuser@host# edit unit 0 family inet6[edit unit 0 family inet6]user@host# set service input service-set ssetuser@host# set service output service-set ssetuser@host# set address 2001:0:0:2::1/48
5. Go to the [edit interfaces] hierarchy level for sp-0/0/0, used to host the DS-Lite AFTR.
   [edit]user@host# edit interfaces sp-0/0/0
6. Define the interface.
   [edit interfaces sp-0/0/0]user@host# set description AFTR-B4user@host# set unit 0 family inetuser@host# edit unit 0 family inet6

Results

description AFTR-Internet;
unit 0 {
    family inet {
        address 128.0.0.2/24;
    }
}

description AFTR-B4;
unit 0 {
    family inet;
    family inet6 {
        service {
            input {
                service-set sset; 
            }
            output {
                service-set sset; 
            }
        }
        address 2001:0:0:2::1/48;
    }
}

unit 0 {
family inet;
family inet6;
}

Network Address and Port Translation Configuration

Step-by-Step Procedure

1. Go to the [edit services nat] hierarchy level.
   user@host# edit services nat[edit services nat]
2. Define a NAT pool p1.
   user@host# set pool p1 address 129.0.0.1/32 port automatic
3. Define a NAT rule, beginning with the match direction.
   [edit services nat]user@host# set rule r1 match-direction input
4. Define a term for the rule, beginning with a from clause.
   [edit services nat]user@host# set rule r1 term t1 from source-address 10.0.0.0/16
5. Define the desired translation in a then clause. In this case, use dynamic source translation.
   [edit services nat]user@host# set rule r1 term t1 then translated source-pool p1 translation-type napt-44
6. (Optional) Configure logging of translation information for the rule.
   [edit services nat]user@host# set rule r1 term t1 then syslog

Results

pool p1 {
    address 129.0.0.1/32;
    port {
        automatic;
    }
}
rule r1 {
    match-direction input;
    term t1 {
        from {
            source-address {
                10.0.0.0/16;
            }
        }
        then {
            translated {
                source-pool p1;
                translation-type {
                    napt-44;
                }
            }
            syslog;
        }
    }

Softwire Configuration

Step-by-Step Procedure

1. Go to the [edit services softwire] hierarchy level.
   user@host# edit services softwire
2. Define the DS-Lite softwire concentrator.
   [edit services softwire]user@host# set softwire-concentrator ds-lite ds-1 softwire-address 1001::1 mtu-v6 1460
3. Define the softwire rule.
   [edit services softwire]user@host# set rule r1 match-direction input term t1 then ds-lite ds1.

Results

softwire-concentrator {
    ds-lite ds1 {
        softwire-address 1001::1;
        mtu-v6 1460;
    }
}
rule r1 {
    match-direction input;
    term t1 {
        then {
            ds-lite ds1;
        }
    }
}

Service Set Configuration

Step-by-Step Procedure

1. Go to the [edit services service-set] hierarchy level, naming the service set.
   user@host# edit services service-set sset
2. Define the NAT rule to be used for IPv4-to-IPv4 translation.
   [edit services service-set sset]user@host# set nat-rules r1
3. Define the softwire rule to define the softwire tunnel.
   [edit services service-set sset]user@host# set softwire-rules r1
4. Define the interface service,
   [edit services service-set sset]user@host# set interface-service service-interface sp-0/0/0.0

   Tip: In order to avoid or minimize IPv6 fragmentation, you can configure a TCP maximum segment size (MSS) for your service set.

5. (Optional) Define a TCP MSS.
   [edit services service-set sset]user@host# set tcp-mss 1024

Results

syslog {
    host local {
        services any;
    }
}
softwire-rules r1;
nat-rules r1;
interface-service {
    service-interface sp-0/0/0;
}
}