Simple NGVPN config ALL IN ONE Box. I use this in general to check the control plane.
+---------------------------+-----------------------------------------------+-------------------+
| r0 lo0.100 192.168.1.100 | Loop Cable: 1 |MPLS CLOUD |
| r1 lo0.101 192.168.1.101 | I2.111 I1.111 receiver |IGP-OSPF |
| r2 lo0.102 192.168.1.102 | C-RP +-----+ +------+ |MPLS-RSVP-LSP |
| r3 lo0.103 192.168.1.103 | - | R10 +-----+ R11 | |MVPN Mode : RPT-SPT|
| r4 lo0.104 192.168.1.104 | | | CE3 | |CE LAN| |C-RP:CE3 R10 lo0 |
| r5 lo0.105 192.168.1.105 | | +--+--I1.109+------+ +-------------------+
| r6 lo0.106 192.168.1.106 | ebgp | SAP 225.0.0.5 |
| r7 lo0.107 192.168.1.107 | | +--+--+I2.109 |
| r8 lo0.108 192.168.1.108 | | | R9 | LHR |
| r9 lo0.109 192.168.1.109 | - | PE3 | |
| r10 lo0.110 192.168.1.110 | +--+--+I1.49 SAP 225.0.0.5 |
| r11 lo0.111 192.168.1.111 | | receiver |
+---------------------------+ +--+--+I2.49 +-----+ |
| I2.24| R4 | I1.43 | R8 | |
| +----+P3 RR+----+ |CE LAN |
| | +-----+ | +--+--+ |
| | AS 100 | I1.68| |
| Source FHR I1.24 | | I2.43 |I2.68 |
| +-----+I1.1 +-----+ +--+--+I1.23 +--+--+ +-----+I1.56 +--+--+ |
| | R0 +---------+ R1 |I1.12 | R2 +---------+ R3 |I1.35 | R5 +---------+ R6 | |
| | CE1 | I2.1| PE1 +---------+ P1 | | P2 +---------+ PE2 | I2.56| CE2 | |
| +-----+ +-----+ I2.12+--+--+ I2.23+--+--+ I2.35+-----+ +-----+ |
| AS 64512 |I1.27 | I2.73 LHR AS 64512 |
| <----ebgp-----> | RR | <----ebgp-----> |
| | +-----+ | |
|P2MP LSP [Created Automatically in PE1]| | R7 | |P2MP LSP [Created Automatically in PE9]|
|192.168.1.105:100:11111:mvpn:vpna +----+ P4 +----+ 192.168.1.105:100:11111:mvpn:vpna |
|192.168.1.109:100:11111:mvpn:vpna I2.27 +-----+ I1.73 192.168.1.101:100:11111:mvpn:vpna |
|
||
+-----------------------------------------------------------------------------------------------+
| Template - MBGP Multicast VPN with PIM ASM as PE-CE Protocol #MVPN Mode : RPT-SPT |
+-----------------------------------------------------------------------------------------------+
| To Initiate Traffic: 'ping 225.0.0.5 bypass-routing interface ge-x/y/z.t ttl 10 count 10000 |
| source 1.1.1.1 interval 1 size 1000 logical-system r0' |
| There is requirement for tunnel interfaces for encapsulation &
| de-encapsulation in PE1 and PE9|
+-----------------------------------------------------------------------------------------------+
| Note: If the traffic is not seen in the egress PE [R9/R5];However
|tarffic is incrementing with| show mpls lsp p2mp statistics in
|transit;please deactiavte/activate of provider-tunnel in PE1/2|
+-----------------------------------------------------------------------------------------------+
Note: Please view in a fixed-width font such as Courier
# ping 225.0.0.5 bypass-routing interface ge-0/0/0.1 ttl 10 count 10000 source 1.1.1.1 interval 1 size 1000 logical-system r0 # Configuring Tunnel Interfaces on MX Series Routers # # You can create tunnel interfaces on MX Series routers by including the following statements at the [edit chassis] hierarchy level:
# set chassis fpc slot-number pic number tunnel-services bandwidth (1g | 10g | 20g | 40g) # [edit chassis] # fpc slot-number { # pic number { # tunnel-services { # bandwidth (1g | 10g | 20g | 40g);
# }
# }
# }
# fpc slot-number is the slot number of the DPC, MPC, or MIC. On the MX80 router, the range is 0 through 1. On other MX series routers, if two SCBs are installed, the range is 0 through 11. If three SCBs are installed, the range is 0 through 5 and 7 through 11.
#
# The pic number On MX80 routers, if the FPC is 0, the PIC number can only be 0. If the FPC is 1, the PIC range is 0 through 3. For all other MX series routers, the range is 0 through 3.
#
# bandwidth (1g | 10g | 20g | 40g) is the amount of bandwidth to reserve for tunnel traffic on each Packet Forwarding Engine.
#
logical-systems {
r0 {
interfaces {
ge-0/0/0 {
unit 1 {
vlan-id 1;
family inet {
address 1.1.1.1/30;
}
}
}
lo0 {
unit 100 {
family inet {
address 192.168.1.100/32;
}
}
}
}
protocols {
bgp {
export connected_to_bgp;
group PE_PEERING {
neighbor 1.1.1.2 {
local-address 1.1.1.1;
peer-as 100;
}
}
}
pim {
rp {
static {
address 192.168.1.110;
}
}
}
}
policy-options {
policy-statement connected_to_bgp {
from protocol direct;
then accept;
}
}
routing-options {
autonomous-system 64512;
}
}
r1 {
interfaces {
ge-0/0/0 {
unit 12 {
vlan-id 12;
family inet {
address 1.1.12.1/30;
}
family mpls;
}
}
ge-0/0/1 {
unit 1 {
vlan-id 1;
family inet {
address 1.1.1.2/30;
}
}
}
lo0 {
unit 101 {
family inet {
address 192.168.1.101/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/0.12;
}
mpls {
label-switched-path r1-to-r5 {
to 192.168.1.105;
}
label-switched-path r1-to-r4 {
to 192.168.1.104;
}
label-switched-path r1-to-r7 {
to 192.168.1.107;
}
label-switched-path r1-to-r9 {
to 192.168.1.109;
}
interface ge-0/0/0.12;
}
bgp {
group ibgp-to-rr {
type internal;
local-address 192.168.1.101;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
family inet-mvpn {
signaling;
}
neighbor 192.168.1.104;
neighbor 192.168.1.107;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.101;
interface ge-0/0/0.12;
}
}
}
routing-instances {
vpna {
instance-type vrf;
interface ge-0/0/1.1;
route-distinguisher 100:11111;
provider-tunnel {
rsvp-te {
label-switched-path-template {
default-template;
}
}
}
vrf-target target:100:111111;
vrf-table-label;
routing-options {
multicast {
ssm-groups 239.0.0.0/8;
}
}
protocols {
bgp {
group vpna {
neighbor 1.1.1.1 {
local-address 1.1.1.2;
peer-as 64512;
as-override;
}
}
}
pim {
rp {
static {
address 192.168.1.110;
}
}
interface all {
mode sparse;
}
}
mvpn {
mvpn-mode {
rpt-spt;
}
}
}
}
}
routing-options {
autonomous-system 100;
}
}
r10 {
interfaces {
ge-0/0/0 {
unit 109 {
vlan-id 109;
family inet {
address 1.1.109.1/30;
}
}
}
ge-0/0/1 {
unit 111 {
vlan-id 111;
family inet {
address 1.1.111.1/30;
}
}
}
lo0 {
unit 110 {
family inet {
address 192.168.1.110/32;
}
}
}
}
protocols {
igmp {
interface ge-0/0/1.111;
}
bgp {
export connected_to_bgp;
group PE_PEERING {
neighbor 1.1.109.2 {
local-address 1.1.109.1;
peer-as 100;
}
}
}
pim {
rp {
local {
address 192.168.1.110;
}
}
interface ge-0/0/0.109;
}
}
policy-options {
policy-statement connected_to_bgp {
from protocol direct;
then accept;
}
}
routing-options {
autonomous-system 64512;
}
}
r11 {
interfaces {
ge-0/0/0 {
unit 111 {
vlan-id 111;
family inet {
address 1.1.111.2/30;
}
}
}
lo0 {
unit 111 {
family inet {
address 192.168.1.111/32;
}
}
}
}
protocols {
igmp {
interface ge-0/0/0.68;
}
sap {
listen 225.0.0.5;
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 1.1.111.1;
}
}
}
r2 {
interfaces {
ge-0/0/0 {
unit 23 {
vlan-id 23;
family inet {
address 1.1.23.1/30;
}
family mpls;
}
unit 24 {
vlan-id 24;
family inet {
address 1.1.24.1/30;
}
family mpls;
}
unit 27 {
vlan-id 27;
family inet {
address 1.1.27.1/30;
}
family mpls;
}
}
ge-0/0/1 {
unit 12 {
vlan-id 12;
family inet {
address 1.1.12.2/30;
}
family mpls;
}
}
lo0 {
unit 102 {
family inet {
address 192.168.1.102/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/1.12;
interface ge-0/0/0.23;
interface ge-0/0/0.24;
interface ge-0/0/0.27;
}
mpls {
interface ge-0/0/1.12;
interface ge-0/0/0.23;
interface ge-0/0/0.24;
interface ge-0/0/0.27;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/1.12;
interface lo0.102;
interface ge-0/0/0.23;
interface ge-0/0/0.24;
interface ge-0/0/0.27;
}
}
}
}
r3 {
interfaces {
ge-0/0/0 {
unit 35 {
vlan-id 35;
family inet {
address 1.1.35.1/30;
}
family mpls;
}
}
ge-0/0/1 {
unit 23 {
vlan-id 23;
family inet {
address 1.1.23.2/30;
}
family mpls;
}
unit 43 {
vlan-id 43;
family inet {
address 1.1.43.2/30;
}
family mpls;
}
unit 73 {
vlan-id 73;
family inet {
address 1.1.73.2/30;
}
family mpls;
}
}
lo0 {
unit 103 {
family inet {
address 192.168.1.103/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/1.23;
interface ge-0/0/1.43;
interface ge-0/0/0.35;
interface ge-0/0/1.73;
}
mpls {
interface ge-0/0/1.23;
interface ge-0/0/1.43;
interface ge-0/0/0.35;
interface ge-0/0/1.73;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/1.23;
interface lo0.103;
interface ge-0/0/1.43;
interface ge-0/0/0.35;
interface ge-0/0/1.73;
}
}
}
}
r4 {
interfaces {
ge-0/0/0 {
unit 43 {
vlan-id 43;
family inet {
address 1.1.43.1/30;
}
family mpls;
}
}
ge-0/0/1 {
unit 24 {
vlan-id 24;
family inet {
address 1.1.24.2/30;
}
family mpls;
}
unit 49 {
vlan-id 49;
family inet {
address 1.1.49.2/30;
}
family mpls;
}
}
lo0 {
unit 104 {
family inet {
address 192.168.1.104/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/1.24;
interface ge-0/0/0.43;
interface ge-0/0/1.49;
}
mpls {
label-switched-path r4-to-r1 {
to 192.168.1.101;
}
label-switched-path r4-to-r5 {
to 192.168.1.105;
}
label-switched-path r4-to-r9 {
to 192.168.1.109;
}
label-switched-path r4-to-r7 {
to 192.168.1.107;
}
interface ge-0/0/1.24;
interface ge-0/0/0.43;
interface ge-0/0/1.49;
}
bgp {
group ibgp-to-rr_client {
type internal;
local-address 192.168.1.104;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
family inet-mvpn {
signaling;
}
cluster 192.168.1.104;
neighbor 192.168.1.101;
neighbor 192.168.1.105;
neighbor 192.168.1.109;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/1.24;
interface lo0.104;
interface ge-0/0/0.43;
interface ge-0/0/1.49;
}
}
}
routing-options {
autonomous-system 100;
}
}
r5 {
interfaces {
ge-0/0/0 {
unit 56 {
vlan-id 56;
family inet {
address 1.1.56.1/30;
}
}
}
ge-0/0/1 {
unit 35 {
vlan-id 35;
family inet {
address 1.1.35.2/30;
}
family mpls;
}
}
lo0 {
unit 105 {
family inet {
address 192.168.1.105/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/1.35;
}
mpls {
label-switched-path r5-to-r1 {
to 192.168.1.101;
}
label-switched-path r5-to-r4 {
to 192.168.1.104;
}
label-switched-path r5-to-r7 {
to 192.168.1.107;
}
label-switched-path r5-to-r9 {
to 192.168.1.109;
}
interface ge-0/0/1.35;
}
bgp {
group ibgp-to-rr {
type internal;
local-address 192.168.1.105;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
family inet-mvpn {
signaling;
}
neighbor 192.168.1.104;
neighbor 192.168.1.107;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/1.35;
interface lo0.105;
}
}
}
routing-instances {
vpna {
instance-type vrf;
interface ge-0/0/0.56;
route-distinguisher 100:11111;
vrf-target target:100:111111;
vrf-table-label;
routing-options {
multicast {
ssm-groups 239.0.0.0/8;
}
}
protocols {
bgp {
group vpna {
neighbor 1.1.56.2 {
local-address 1.1.56.1;
peer-as 64512;
as-override;
}
}
}
pim {
rp {
static {
address 192.168.1.110;
}
}
interface all {
mode sparse;
}
}
mvpn {
mvpn-mode {
rpt-spt;
}
}
}
}
}
routing-options {
autonomous-system 100;
}
}
r6 {
interfaces {
ge-0/0/1 {
unit 56 {
vlan-id 56;
family inet {
address 1.1.56.2/30;
}
}
unit 68 {
vlan-id 68;
family inet {
address 1.1.68.1/30;
}
}
}
lo0 {
unit 106 {
family inet {
address 192.168.1.106/32;
}
}
}
}
protocols {
igmp {
interface ge-0/0/1.68;
}
bgp {
export connected_to_bgp;
group PE_PEERING {
neighbor 1.1.56.1 {
local-address 1.1.56.2;
peer-as 100;
}
}
}
pim {
rp {
static {
address 192.168.1.110;
}
}
interface ge-0/0/1.56;
}
}
policy-options {
policy-statement connected_to_bgp {
from protocol direct;
then accept;
}
}
routing-options {
autonomous-system 64512;
}
}
r7 {
interfaces {
ge-0/0/0 {
unit 73 {
vlan-id 73;
family inet {
address 1.1.73.1/30;
}
family mpls;
}
}
ge-0/0/1 {
unit 27 {
vlan-id 27;
family inet {
address 1.1.27.2/30;
}
family mpls;
}
}
lo0 {
unit 107 {
family inet {
address 192.168.1.107/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/1.27;
interface ge-0/0/0.73;
}
mpls {
label-switched-path r7-to-r1 {
to 192.168.1.101;
}
label-switched-path r7-to-r5 {
to 192.168.1.105;
}
label-switched-path r7-to-r9 {
to 192.168.1.109;
}
label-switched-path r7-to-r4 {
to 192.168.1.104;
}
interface ge-0/0/1.27;
interface ge-0/0/0.73;
}
bgp {
group ibgp-to-rr_client {
type internal;
local-address 192.168.1.107;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
family inet-mvpn {
signaling;
}
cluster 192.168.1.107;
neighbor 192.168.1.101;
neighbor 192.168.1.105;
neighbor 192.168.1.109;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/1.27;
interface lo0.107;
interface ge-0/0/0.73;
}
}
}
routing-options {
autonomous-system 100;
}
}
r8 {
interfaces {
ge-0/0/0 {
unit 68 {
vlan-id 68;
family inet {
address 1.1.68.2/30;
}
}
}
lo0 {
unit 108 {
family inet {
address 192.168.1.108/32;
}
}
}
}
protocols {
igmp {
interface ge-0/0/0.68;
}
sap {
listen 225.0.0.5;
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 1.1.68.1;
}
}
}
r9 {
interfaces {
ge-0/0/0 {
unit 49 {
vlan-id 49;
family inet {
address 1.1.49.1/30;
}
family mpls;
}
}
ge-0/0/1 {
unit 109 {
vlan-id 109;
family inet {
address 1.1.109.2/30;
}
}
}
lo0 {
unit 109 {
family inet {
address 192.168.1.109/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/0/0.49;
}
mpls {
label-switched-path r9-to-r1 {
to 192.168.1.101;
}
label-switched-path r9-to-r4 {
to 192.168.1.104;
}
label-switched-path r9-to-r7 {
to 192.168.1.107;
}
label-switched-path r9-to-r5 {
to 192.168.1.105;
}
interface ge-0/0/0.49;
}
bgp {
group ibgp-to-rr {
type internal;
local-address 192.168.1.109;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
family inet-mvpn {
signaling;
}
neighbor 192.168.1.104;
neighbor 192.168.1.107;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/0.49;
interface lo0.109;
}
}
}
routing-instances {
vpna {
instance-type vrf;
interface ge-0/0/1.109;
route-distinguisher 100:11111;
provider-tunnel {
rsvp-te {
label-switched-path-template {
default-template;
}
}
}
vrf-target target:100:111111;
vrf-table-label;
routing-options {
multicast {
ssm-groups 239.0.0.0/8;
}
}
protocols {
bgp {
group vpna {
neighbor 1.1.109.1 {
local-address 1.1.109.2;
peer-as 64512;
as-override;
}
}
}
pim {
rp {
static {
address 192.168.1.110;
}
}
interface all {
mode sparse;
}
}
mvpn {
mvpn-mode {
rpt-spt;
}
}
}
}
}
routing-options {
autonomous-system 100;
}
}
}
interfaces {
ge-0/0/0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
}
ge-0/0/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
}
}
↧
Re: Implemented VRF import and export policy and MVPN stopped working
↧