Connecting IPv6 Isl ands with IPv4 MPLS
Juniper，Junos 6PE－LAB。
Many service providers are looking for ways to provide new revenue-generating services
to their customers. One such service is Internet Protocol version 6 (IPv6). Some enterprise
customers are beginning to experiment with this new version of IP , but are reluctant to
deploy it broadly. Interconnecting multiple sites that use IPv6 can be challenging. Also,
most service providers would prefer to carry this traffic without making major
modifications to their core network.
绿城百合@RTA# show
r1 {
interfaces {
fe-0/3/2 {
unit 12 {
vlan-id 12;
family inet6 {
address 8001::1/126;
}
}
}
lo0 {
unit 1 {
family inet6 {
address 9001::1/128;
}
}
}
}
protocols {
bgp {
group to-R2-p1 {
type external;
local-address 8001::1;
family inet6 {
unicast;
}
export policy1;
peer-as 100;
neighbor 8001::2;
}
}
}
policy-options {
policy-statement policy1 {
term 1 {
from {
family inet6;
route-filter 9001::1/128 exact;
}
then accept;
}
term 2 {
then reject;
}
}
}
routing-options {
autonomous-system 200;
}
}
r2 {
interfaces {
fe-0/3/2 {
unit 23 {
vlan-id 23;
family inet {
address 10.255.2.1/30;
}
family inet6;
family mpls;
}
}
fe-0/3/3 {
unit 12 {
vlan-id 12;
family inet6 {
address 8001::2/126;
}
}
}
lo0 {
unit 2 {
family inet {
address 10.255.255.16/32;
}
}
}
}
protocols {
rsvp {
interface fe-0/3/2.23;
}
mpls {
ipv6-tunneling;
label-switched-path to-p2 {
to 10.255.255.15;
}
interface fe-0/3/2.23;
}
bgp {
group to-pe2 {
type internal;
local-address 10.255.255.16;
family inet {
unicast;
}
family inet6 {
labeled-unicast {
explicit-null;
}
}
export nhs;
neighbor 10.255.255.15;
}
group to-ce1-r1 {
type external;
local-address 8001::2;
family inet6 {
unicast;
}
peer-as 200;
neighbor 8001::1;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface fe-0/3/2.23;
interface lo0.2 {
passive;
}
}
}
}
policy-options {
policy-statement nhs {
term 1 {
from protocol bgp;
then {
next-hop self;
}
}
}
}
routing-options {
autonomous-system 100;
}
}
r3 {
interfaces {
fe-0/3/3 {
unit 23 {
vlan-id 23;
family inet {
address 10.255.2.2/30;
}
family mpls;
}
unit 34 {
vlan-id 34;
family inet {
address 10.255.3.1/30;
}
family mpls;
}
}
lo0 {
unit 3 {
family inet {
address 10.255.255.220/32;
}
}
}
}
protocols {
rsvp {
interface fe-0/3/3.23;
interface fe-0/3/3.34;
}
mpls {
interface fe-0/3/3.23;
interface fe-0/3/3.34;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface fe-0/3/3.23;
interface fe-0/3/3.34;
interface lo0.0 {
passive;
}
}
}
}
}
r4 {
interfaces {
fe-0/3/2 {
unit 34 {
vlan-id 34;
family inet {
address 10.255.3.2/30;
}
family inet6;
family mpls;
}
unit 45 {
vlan-id 45;
family inet6 {
address 8002::1/126;
}
}
}
lo0 {
unit 4 {
family inet {
address 10.255.255.15/32;
}
}
}
}
protocols {
rsvp {
interface fe-0/3/2.34;
}
mpls {
ipv6-tunneling;
label-switched-path to-p1 {
to 10.255.255.16;
}
interface fe-0/3/2.34;
}
bgp {
group to-pe1 {
type internal;
local-address 10.255.255.15;
family inet {
unicast;
}
family inet6 {
labeled-unicast {
explicit-null;
}
}
export red-export;
neighbor 10.255.255.16;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface fe-0/3/2.34;
interface lo0.4 {
passive;
}
}
}
ripng {
group to-ce2 {
export red-import;
neighbor fe-0/3/2.45;
}
}
}
policy-options {
policy-statement red-export {
term 1 {
from protocol ripng;
then accept;
}
term 2 {
then reject;
}
}
policy-statement red-import {
from protocol bgp;
then accept;
}
}
routing-options {
autonomous-system 100;
}
}
r5 {
interfaces {
fe-0/3/3 {
unit 45 {
vlan-id 45;
family inet6 {
address 8002::2/126;
}
}
}
lo0 {
unit 5 {
family inet6 {
address 9001::5/128;
}
}
}
}
protocols {
ripng {
group to-pe2 {
export policy1;
neighbor fe-0/3/3.45;
}
}
}
policy-options {
policy-statement policy1 {
term 1 {
from {
family inet6;
route-filter 9001::5/128 exact;
}
then accept;
}
term 2 {
then reject;
}
}
}
routing-options {
autonomous-system 300;
}
}
[edit logical-systems]