Bring MPLS Network at Your Home Lab

Goal: Injected Full global bgp route into olive or dynamips

tools:
1. Olive
2. GNS3
3. VMware

First step Installing libbgpdump & p5-Net-BGP

to inject internet route to your home lab router you need to install BGPsimple

bgpsimple is simple BGP peering and route injection script
its just perl script allows to setup an BGP adjacency with a BGP peer, monitor the messages and updates received from that peer, and to send out updates from a predefined set of NLRIs/attributes. BGP session and message handling is done by Net::BGP.
The script was mainly written to take a file with BGP route information (TABLE_DUMP_V2 format) and to inject these routes over a BGP adjacency. It grew a little over the time, and has some additional features to tweak and filter those routes before advertising them to the peer.

UPDATE messages received will be logged. Currently, there is no implementation of any local routing policy (except the features and sanity checks described at the NOTES section). Furthermore, no adj-rib-in and adj-rib-out databases are maintained.

Please note that you might need to patch Net::BGP to get correct handling of AGGREGATOR attributes (see the end of this file), this got fixed in Net::BGP version 0.12.

You can redistribute and modify this script under the terms of the GNU General Public License version 3.

BGPsimple installation guide
1. install FreeBSD in VMware i dont explain detail installation freebsd on VMware and i’m not using ubuntu or others Linux distro. I just want simple installation and don’t want wasting time just for waiting the installation complete.
2. if your freebsd installed correctly in VMware you need connect your freebsd to internet to install bgpsimple.
3. install depedency software to run bgpsimple script, you just need to type this command to your freebsd.
   
  FreeBSD# cd /usr/ports/net/libbgpdump/ && make install clean
===> Vulnerability check disabled, database not found
===> Extracting for libbgpdump-1.4.99.9
=> MD5 Checksum OK for libbgpdump-1.4.99.9.tar.gz.
=> SHA256 Checksum OK for libbgpdump-1.4.99.9.tar.gz.
===> Patching for libbgpdump-1.4.99.9
===> Configuring for libbgpdump-1.4.99.9
checking for gcc… cc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…

  
   FreeBSD# cd /usr/ports/net/p5-Net-BGP/ && make install clean
    ===>  Vulnerability check disabled, database not found
   => Net-BGP-0.13.tar.gz doesn’t seem to exist in /usr/ports/distfiles/.
   => Attempting to fetch from ftp://ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Net/.

just wait until installation is completed

4. after installation libbgpdump & p5-Net-BGP complete download bgpsimple perl script at this link
   http://code.google.com/p/bgpsimple/downloads/list

Getting route information

The original intention of the script was to feed as many routes to a peer as possible for testing purposes. To get large amounts of real world prefixes, dumps from a DFZ attached peers must be retrieved. Luckily, there are some ressources that provide such dumps, for example RIPE RIS (http://www.ripe.net/projects/ris/rawdata.html). Simply fetch a full dump from http://data.ris.ripe.net/rrc00/ (bview.).

The script cannot work with this binary data, some conversion has to be done. To do that, get the bgpdump library/utility (http://www.ris.ripe.net/source/). Compile bgpdump, then feed the dump through it. Make sure to specify the -m option to produce the condensed format:

FreeBSD#fetch http://data.ris.ripe.net/rrc16/2008.02/bview.20080201.0759.gz
create dump route with the name of bgproute

FreeBSD# zcat bview.20080201.0759.gz | bgpdump -m - > bgproute

Now testing BGP peering to Olive or dynamips

To interconnecting Olive <–> GNS3 <–> Vmware

I need cisco switch to connecting Vmware <–> olive
use c3600 as Vlan Switch
You need create cloud in your gns3, add your vmware interface and olive tap interface and connected to c3600 as vlan switch 
configure c3600 trunk port thaht connected to olive, and each port that connect to vmware configure
as access port, i hope you have deep knowledge about switching and running qemu script properly

test ping freebsd <–> Logical-system R3

FreeBSD# ping 172.16.0.13
PING 172.16.0.13 (172.16.0.13): 56 data bytes
64 bytes from 172.16.0.13: icmp_seq=0 ttl=64 time=21.533 ms
64 bytes from 172.16.0.13: icmp_seq=1 ttl=64 time=2.091 ms
64 bytes from 172.16.0.13: icmp_seq=2 ttl=64 time=1.928 ms
64 bytes from 172.16.0.13: icmp_seq=3 ttl=64 time=1.956 ms
^C
— 172.16.0.13 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.928/6.877/21.533/8.462 ms

YESSS…!!!! Connected

test ping freebsd <–> Logical-system T2

FreeBSD# ping 172.18.0.1
PING 172.18.0.1 (172.18.0.1): 56 data bytes
64 bytes from 172.18.0.1: icmp_seq=0 ttl=64 time=4.795 ms
64 bytes from 172.18.0.1: icmp_seq=1 ttl=64 time=1.763 ms
64 bytes from 172.18.0.1: icmp_seq=2 ttl=64 time=3.482 ms
64 bytes from 172.18.0.1: icmp_seq=3 ttl=64 time=1.827 ms
^C
— 172.18.0.1 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.763/2.967/4.795/1.261 ms
T2#

YESSSS…!!!! Connected

Now testing BGP peering to Olive
i use this topology from JNCIP study guide to test ebgp peering

This is Simple command  IBGP peering FreeBSD <–> Logical-System T2

FreeBSD# ./bgp_simple.pl -myas 65222 -myip 172.18.0.2 -peerip 172.18.0.1 -peeras 65222 -p bgproute -n

—————————————- CONFIG SUMMARY ————————————————–
Configured for an iBGP session between me (ASN65222, 172.18.0.2) and peer (ASN65222, 172.18.0.1).
Using 600 seconds as KeepAlive value and 1800 seconds as HoldTime value for this peer.
Will use prefixes from file myroute.
Maximum number of prefixes to be advertised: 20000.
Will spoof next hop address to 172.18.0.2.
———————————————————————————————————-
Update received from peer [172.18.0.1], ASN [65222]: prfx [10.0.0.0/8] aspath [64512] locprf [100] comm [] orig [IGP] agg [64512 10.0.3.5] nxthp [172.16.0.17]
Update received from peer [172.18.0.1], ASN [65222]: prfx [32.0.0.0/16] aspath [64512 420] locprf [100] comm [] orig [IGP] agg [] nxthp [172.16.0.17]
. . . .
Send Update: prfx [63.123.232.0/24] aspath [25152 23148 701 11486 11927] locprf [0] orig [IGP] nxthp [172.18.0.2]
Send Update: prfx [63.123.234.0/24] aspath [25152 23148 701 11486 11927] locprf [0] orig [IGP] nxthp [172.18.0.2]
Send Update: prfx [63.123.236.0/24] aspath [25152 23148 701 11486 26312] locprf [0] orig [IGP] nxthp [172.18.0.2]
Send Update: prfx [63.123.239.0/24] aspath [25152 23148 3356 2828 26312] locprf [0] orig [IGP] nxthp [172.18.0.2]
Send Update: prfx [63.123.245.0/24] aspath [25152 23148 701 11486 11927] locprf [0] orig [IGP] nxthp [172.18.0.2]
Send Update: prfx [63.124.1.0/24] aspath [25152 23148 701 22314] locprf [0] orig [IGP] nxthp [172.18.0.2]
Send Update: prfx [63.124.20.0/23] aspath [25152 23148 701 1699] locprf [0] orig [INCOMPLETE] nxthp [172.18.0.2]
Send Update: prfx [63.124.22.0/24] aspath [25152 23148 701 1699] locprf [0] orig [INCOMPLETE] nxthp [172.18.0.2]
Send Update: prfx [63.124.78.0/23] aspath [25152 23148 701 6619] locprf [0] orig [IGP] nxthp [172.18.0.2]

You can limit the number of prefix being injected,
i want to inject 50000 prefix just add (-m 50000)

FreeBSD# ./bgp_simple.pl -myas 65222 -myip 172.18.0.2 -peerip 172.18.0.1 -peeras 65222 -p bgproute -m 50000 -n 

[edit logical-systems]
AREMA@JNCIP# run show bgp summary logical-system r3   
Groups: 3 Peers: 6 Down peers: 1
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0            478436     476742          0          0      49969          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…
10.0.2.1              65001         56      66956       0       0       15:28 4/5/5/0              0/0/0/0
10.0.3.4              65000         68      66970       0       0       14:35 9/12/12/0            0/0/0/0
10.0.6.1              65000         37      66968       0       0       14:46 2/2/2/0              0/0/0/0
10.0.6.2              65000         13         42       0       1       11:35 Connect
172.16.0.14           65222     231807      43605       0       0        2:14 230989/231804/230991/0 0/0/0/0
172.16.0.18           65222      63614      66900       0       0       15:31 245738/246613/245738/0 0/0/0/0

YESSS….!!!! I got The Internet Route year 2008

AREMA@JNCIP# …protocol bgp aspath-regex ".* (701 33383) .*" logical-system r3   

inet.0: 246658 destinations, 478465 routes (245782 active, 0 holddown, 1689 hidden)
+ = Active Route, - = Last Active, * = Both

63.126.166.0/24    *[BGP/170] 00:09:24, localpref 100
                      AS path: 65222 25152 23148 701 33383 I
                      to 172.16.0.14 via fxp7.103
                    > to 172.16.0.18 via fxp7.204
                    [BGP/170] 00:03:38, localpref 100
                      AS path: 65222 25152 23148 701 33383 I
                    > to 172.16.0.14 via fxp7.103
192.85.23.0/24     *[BGP/170] 00:07:28, localpref 100, from 172.16.0.18
                      AS path: 65222 25152 23148 701 33383 I
                    > to 172.16.0.14 via fxp7.103
                      to 172.16.0.18 via fxp7.204
                    [BGP/170] 00:03:04, localpref 100
                      AS path: 65222 25152 23148 701 33383 I
                    > to 172.16.0.14 via fxp7.103
192.85.24.0/24     *[BGP/170] 00:07:28, localpref 100
                      AS path: 65222 25152 23148 701 33383 I
                      to 172.16.0.14 via fxp7.103

Now change the console to dynamips

Connected to Dynamips VM "Cisco" (ID 1, type c3600) - Console port

Cisco1>
*Mar  1 00:00:37.223: %BGP-5-ADJCHANGE: neighbor 172.19.0.1 Up

Cisco1#show ip bgp sum            
BGP router identifier 172.19.0.2, local AS number 420
BGP table version is 231353, main routing table version 231259
231352 network entries using 27068184 bytes of memory
231352 path entries using 12030304 bytes of memory
38705/38704 BGP path/bestpath attribute entries using 4799420 bytes of memory
35537 BGP AS-PATH entries using 1429944 bytes of memory
1 BGP community entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 45327876 total bytes of memory
BGP activity 466254/234901 prefixes, 466253/234901 paths, scan interval 60 secs

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
172.19.0.1      4 65010   79722      83   201434   17    0 00:04:03   231345

Cisco1#sh ip bgp regexp (701 33383)
BGP table version is 127592, local router ID is 172.19.0.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 63.126.166.0/24  172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.23.0      172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.24.0      172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.75.0      172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.88.0      172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.89.0      172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.123.0     172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.133.0     172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i
*> 192.85.154.0     172.19.0.1                             0 65010 64512 65222 25152 23148 701 33383 i

YESSS…!!!!   I got it this route  

If the BGP connection between bgpsimple and your Olive or dynamips router dies due to a hold timer expiring, you can get around this by doing two things:
this optional options to increase the holdtime and keepalive
keepalive is 1/3 holdtime

edit your bgpsimple script

FreeBSD#ee bgp_simple.pl
go to line 119 & 120 change

my $infile;
my $outfile;
my $prefix_limit;
my $verbose = 0;
my $dry;
my $next_hop_self = "0";
my $adj_next_hop = 0;
my $default_local_pref = 0;
my $myas;
my $myip;
my $peeras;
my $peerip;
my %regex_filter;
my $holdtime = 1500;
my $keepalive = 500;

SALAM SATU JIWA

LOYALITAS TANPA BATAS

TOTALLY PROUD WAS BORN AS AREMANIA

SAK LAWASE TETEP AREMANIA….

KALAH MENANG HATI SENANG ITULAH PERMAINAN…..

Tools : Juniper SRX-series, Olive, dynamips
Purpose: Simulate L2VPN - VPLS using Point-to-multipoin LSP in Juniper
Goal: Each CE can ping inet4/inet6
Note: In this lab i am using the real juniper device because Olive not support vpls encapsulation
Topology:

 

Comments:
1. Use ISIS as Core IGP Network
2. ALL PE use vpls BGP-signaling
3. BGP Configured with Route-Reflector (Since SRX210 not support BGP-RR so I use Olive that acts as BGP-RR for family l2vpn)
4. ALL PE use P2MP-LSP
5. All CE that connected to PE use the same subnet for IPv4 and IPv6

Almost All configuration same with earlier post but the differences are under protocol mpls hierarchy and routing-instance hierarchy

configuring protocol mpls (all PE use LSP-tunnel)

protocols {
    mpls {
        label-switched-path to-rr {
            to 10.1.2.4;
        }
        label-switched-path to-r2 {
            to 10.0.6.2;
        }
        label-switched-path p2mp-templet {
            template;
            optimize-timer 50;
            link-protection;
            p2mp;
        }
        label-switched-path to-r3 {
            to 10.0.3.3;
        }
        label-switched-path to-r6 {
            to 10.0.9.6;
        }
        interface ge-0/0/0.0;
        interface fe-0/0/6.0;
        interface fe-0/0/7.0 {
            disable;
        }
    }

configuring routing-instance

routing-instances {
    vpls {
        instance-type vpls;
        interface ge-0/0/1.0;
        route-distinguisher 10.0.9.7:10;
        provider-tunnel {
            rsvp-te {
                label-switched-path-template {
                    p2mp-templet;
                }
            }
        }
        vrf-target target:65000:10;
        protocols {
            vpls {
                site-range 10;
                no-tunnel-services;
                site R7 {
                    site-identifier 7;
                    interface ge-0/0/1.0;
                }
            }
        }
    }
 
Lets see the troubleshoot result

lab@AREMA-R7> show route |no-more

inet.0: 31 destinations, 32 routes (31 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
.
.
.

inet.3: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.3/32        *[RSVP/7] 18:41:47, metric 20
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r3
10.0.6.2/32        *[RSVP/7] 18:41:48, metric 30
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r2
10.0.9.6/32        *[RSVP/7] 18:41:48, metric 10
                    > to 10.0.8.1 via fe-0/0/6.0, label-switched-path to-r6
10.1.2.4/32        *[RSVP/7] 18:41:48, metric 30
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-rr

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

77.0000.0000.0000.0000.0007/88               
                   *[Direct/0] 18:43:15
                    > via lo0.0

mpls.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 18:43:18, metric 1
                      Receive
1                  *[MPLS/0] 18:43:18, metric 1
                      Receive
2                  *[MPLS/0] 18:43:18, metric 1
                      Receive
262146             *[VPLS/7] 17:35:22
                    > via lsi.1053189, Pop     
262147             *[VPLS/7] 00:08:13
                    > via lsi.1053192, Pop     
262150             *[VPLS/7] 17:24:16
                    > via lsi.1053191, Pop     
lsi.1053189        *[VPLS/7] 17:35:22, metric2 30
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r2
lsi.1053192        *[VPLS/7] 00:08:13, metric2 20
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r3
lsi.1053191        *[VPLS/7] 17:24:16, metric2 10
                    > to 10.0.8.1 via fe-0/0/6.0, label-switched-path to-r6

bgp.l2vpn.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.3:10:3:1/96               
                   *[BGP/170] 00:08:13, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r3
10.0.3.3:10:3:9/96               
                   *[BGP/170] 00:08:13, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r3
10.0.6.2:10:2:1/96               
                   *[BGP/170] 17:35:22, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r2
10.0.6.2:10:2:9/96               
                   *[BGP/170] 17:35:22, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r2
10.0.9.6:10:6:1/96               
                   *[BGP/170] 17:24:16, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.1 via fe-0/0/6.0, label-switched-path to-r6
10.0.9.6:10:6:9/96               
                   *[BGP/170] 17:24:16, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.1 via fe-0/0/6.0, label-switched-path to-r6
10.1.2.4:10:9:9/96               
                   *[BGP/170] 18:41:30, localpref 0, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-rr

vpls.l2vpn.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.3:10:3:1/96               
                   *[BGP/170] 00:08:13, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r3
10.0.3.3:10:3:9/96               
                   *[BGP/170] 00:08:13, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r3
10.0.6.2:10:2:1/96               
                   *[BGP/170] 17:35:22, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r2
10.0.6.2:10:2:9/96               
                   *[BGP/170] 17:35:22, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-r2
10.0.9.6:10:6:1/96               
                   *[BGP/170] 17:24:16, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.1 via fe-0/0/6.0, label-switched-path to-r6
10.0.9.6:10:6:9/96               
                   *[BGP/170] 17:24:16, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.1 via fe-0/0/6.0, label-switched-path to-r6
10.0.9.7:10:7:1/96               
                   *[L2VPN/170/-101] 18:43:15, metric2 1
                      Indirect
10.0.9.7:10:7:9/96               
                   *[L2VPN/170/-101] 18:41:18, metric2 1
                      Indirect
10.1.2.4:10:9:9/96               
                   *[BGP/170] 18:41:30, localpref 0, from 10.1.2.4
                      AS path: I
                    > to 10.0.8.9 via ge-0/0/0.0, label-switched-path to-rr

lab@AREMA-R7> show vpls connections extensive
Layer-2 VPN connections:

Legend for connection status (St)  
EI — encapsulation invalid      NC — interface encapsulation not CCC/TCC/VPLS
EM — encapsulation mismatch     WE — interface and instance encaps not same
VC-Dn — Virtual circuit down    NP — interface hardware not present
CM — control-word mismatch      -> — only outbound connection is up
CN — circuit not provisioned    <- — only inbound connection is up
OR — out of range               Up — operational
OL — no outgoing label          Dn — down                     
LD — local site signaled down   CF — call admission control failure     
RD — remote site signaled down  SC — local and remote site ID collision
LN — local site not designated  LM — local site ID not minimum designated
RN — remote site not designated RM — remote site ID not minimum designated
XX — unknown connection status  IL — no incoming label
MM — MTU mismatch               MI — Mesh-Group ID not availble
BK — Backup connection          ST — Standby connection
PF — Profile parse failure      PB — Profile busy
RS — remote site standby

Legend for interface status
Up — operational          
Dn — down

Instance: vpls
  Local site: R7 (7)
    Number of local interfaces: 1
    Number of local interfaces up: 1
    IRB interface present: no
    ge-0/0/1.0        
    lsi.1053189         2         Intf - vpls vpls local site 7 remote site 2
    lsi.1053192         3         Intf - vpls vpls local site 7 remote site 3
    lsi.1053191         6         Intf - vpls vpls local site 7 remote site 6
    Label-base        Offset     Size  Range     Preference
    262145            1          8      8         100  
    Label-base        Offset     Size  Range     Preference
    262153            9          8      1         100  
    connection-site           Type  St     Time last up          # Up trans
    2                         rmt   Up     Oct 22 17:58:31 2010           1
      Remote PE: 10.0.6.2, Negotiated control-word: No
      Incoming label: 262146, Outgoing label: 262151
      Local interface: lsi.1053189, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls vpls local site 7 remote site 2
      RSVP-TE P2MP lsp:
        Ingress branch LSP: 10.0.6.2:10.0.9.7:10:vpls:vpls, State: Up
        Egress branch LSP:  10.0.9.7:10.0.6.2:10:vpls:vpls, State: Up
    Connection History:
        Oct 22 17:58:31 2010  status update timer 
        Oct 22 17:58:31 2010  loc intf up                  lsi.1053189
        Oct 22 17:58:31 2010  PE route changed    
        Oct 22 17:58:31 2010  Out lbl Update                    262151
        Oct 22 17:58:31 2010  In lbl Update                     262146
        Oct 22 17:58:31 2010  loc intf down       
    3                         rmt   Up     Oct 23 11:25:41 2010           1
      Remote PE: 10.0.3.3, Negotiated control-word: No
      Incoming label: 262147, Outgoing label: 262151
      Local interface: lsi.1053192, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls vpls local site 7 remote site 3
      RSVP-TE P2MP lsp:
        Ingress branch LSP: 10.0.3.3:10.0.9.7:10:vpls:vpls, State: Up
        Egress branch LSP:  10.0.9.7:10.0.3.3:10:vpls:vpls, State: Up
    Connection History:
        Oct 23 11:25:41 2010  status update timer 
        Oct 23 11:25:41 2010  loc intf up                  lsi.1053192
        Oct 23 11:25:41 2010  PE route changed    
        Oct 23 11:25:41 2010  Out lbl Update                    262151
        Oct 23 11:25:41 2010  In lbl Update                     262147
        Oct 23 11:25:41 2010  loc intf down       
    6                         rmt   Up     Oct 22 18:09:37 2010           1
      Remote PE: 10.0.9.6, Negotiated control-word: No
      Incoming label: 262150, Outgoing label: 262151
      Local interface: lsi.1053191, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls vpls local site 7 remote site 6
      RSVP-TE P2MP lsp:
        Ingress branch LSP: 10.0.9.6:10.0.9.7:10:vpls:vpls, State: Up
        Egress branch LSP:  10.0.9.7:10.0.9.6:10:vpls:vpls, State: Up
    Connection History:
        Oct 22 18:09:37 2010  status update timer 
        Oct 22 18:09:37 2010  loc intf up                  lsi.1053191
        Oct 22 18:09:37 2010  PE route changed    
        Oct 22 18:09:37 2010  Out lbl Update                    262151
        Oct 22 18:09:37 2010  In lbl Update                     262150
        Oct 22 18:09:37 2010  loc intf down       
    9                         rmt   OL  
  Ingress RSVP-TE P2MP LSP: 10.0.9.7:10:vpls:vpls, Flood next-hop ID: 583

ab@AREMA-R7> show vpls statistics   
VPLS statistics:

Instance: vpls
   Local interface: lsi.1053189, Index: 68
   Remote PE: 10.0.6.2
     Current MAC count:                     1
   Local interface: lsi.1053192, Index: 71
   Remote PE: 10.0.3.3
     Current MAC count:                     1
   Local interface: lsi.1053191, Index: 72
   Remote PE: 10.0.9.6
     Current MAC count:                     0
   Local interface: ge-0/0/1.0, Index: 80
     Multicast packets:                  1017
     Multicast bytes  :                110526
     Flooded packets  :                     0
     Flooded bytes    :                     0
     Current MAC count:                     0

lab@AREMA-R7> show vpls flood        
Name: vpls
CEs: 1
VEs: 3
Flood Routes:
  Prefix    Type          Owner                 NhType          NhIndex
  0x44/32   IFF_FLOOD     lsi.1053189           comp            585    
  0x48/32   IFF_FLOOD     lsi.1053191           comp            585    
  0x47/32   IFF_FLOOD     lsi.1053192           comp            585    
  0x50/32   IFF_FLOOD     ge-0/0/1.0            comp            580    

lab@AREMA-R7> show vpls flood extensive
Name: vpls
CEs: 1
VEs: 3
  Flood route prefix: 0x44/32
  Flood route type: IFF_FLOOD
  Flood route owner: lsi.1053189
  Flood group name: __ves__
  Flood group index: 0
  Nexthop type: comp
  Nexthop index: 585
    Flooding to:
    Name             Type          NhType          Index
    __all_ces__      Group          comp            569    
        Composition: split-horizon
        Flooding to:
        Name             Type          NhType          Index
        ge-0/0/1.0       CE             ucst            532    

  Flood route prefix: 0x48/32
  Flood route type: IFF_FLOOD
  Flood route owner: lsi.1053191
  Flood group name: __ves__
  Flood group index: 0
  Nexthop type: comp
  Nexthop index: 585
    Flooding to:
    Name             Type          NhType          Index
    __all_ces__      Group          comp            569    
        Composition: split-horizon
        Flooding to:
        Name             Type          NhType          Index
        ge-0/0/1.0       CE             ucst            532    

  Flood route prefix: 0x47/32
  Flood route type: IFF_FLOOD
  Flood route owner: lsi.1053192
  Flood group name: __ves__
  Flood group index: 0
  Nexthop type: comp
  Nexthop index: 585
    Flooding to:
    Name             Type          NhType          Index
    __all_ces__      Group          comp            569    
        Composition: split-horizon
        Flooding to:
        Name             Type          NhType          Index
        ge-0/0/1.0       CE             ucst            532    

  Flood route prefix: 0x50/32
  Flood route type: IFF_FLOOD
  Flood route owner: ge-0/0/1.0
  Flood group name: __all_ces__
  Flood group index: 1
  Nexthop type: comp
  Nexthop index: 580
    Flooding to:
    Name             Type          NhType          Index
    __all_ces__      Group          comp            569    
        Composition: split-horizon
        Flooding to:
        Name             Type          NhType          Index
        ge-0/0/1.0       CE             ucst            532    
    Flooding to:
    Name             Type          NhType          Index
    __ves__          Group          comp            572    
        Composition: flood-to-all
        Flooding to:
        Name             Type          NhType          Index
        lsi.1053189      VE             indr            262142 
        lsi.1053191      VE             indr            262144 
        lsi.1053192      VE             indr            262143 

Tools : Juniper SRX-series, Olive, dynamips
Purpose: Simulate L2VPN - VPLS  Juniper
Goal: Each CE can ping inet4/inet6
Note: In this lab i am using the real juniper device because Olive not support vpls encapsulation
Topology:

Comments:
1. Use ISIS as Core IGP Network
2. R2,R3,R5 as PE use vpls BGP signaling
3. BGP Configured with Route-Reflector (Since SRX210 not support BGP-RR so I use Olive that acts as BGP-RR for family l2vpn)
4. R6,R7,R5 as PE use vpls LDP signaling
5. R5 acts as PE that interoperability between vpls BGP-Signaling and LDP-Signaling
6. All CE that connected to PE use the same subnet for IPv4 and IPv6

First Step configure IGP and MPLS under interface and protocol hierarchy

interfaces {
    ge-0/0/0 {
        description R7-R5;
        mtu 1540;
        unit 0 {
            family inet {
                address 10.0.8.10/30;
            }
            family iso;
            family mpls;
        }
    }
    fe-0/0/2 {
        description R7->LR_C2;
        vlan-tagging;
        unit 30 {
            vlan-id 30;
            family inet {
                address 172.16.0.25/30;
            }
            family iso;
            family mpls;
        }
    }
    fe-0/0/3 {
        description R7->R4;
        unit 0 {
            family inet {
                address 10.0.2.14/30;
            }
        }
    }
    fe-0/0/6 {
        description R7-R6;
        mtu 1540;
        unit 0 {
            family inet {
                address 10.0.8.2/30;
            }
            family iso;
            family mpls;
        }
    }
    lo0 {
        unit 0 {
            family inet {
                address 10.0.9.7/32;
            }
            family iso {
                address 77.0000.0000.0000.0000.0007.00;
            }
        }
    }
}

Configure protocol on each PE

For LDP-Signaling PE
protocols {
    mpls {
        interface ge-0/0/0.0;
        interface fe-0/0/6.0;
    }
    isis {
        level 1 {
            disable;
            wide-metrics-only;
        }
        interface ge-0/0/0.0;
        interface fe-0/0/6.0;
        interface lo0.0 {
            passive;
        }
    }
    ldp {
        interface ge-0/0/0.0;
        interface fe-0/0/6.0;
        interface fe-0/0/7.0 {
            disable;
        }
        interface lo0.0;
    }
}

For BGP-Signaling PE
protocols {
    mpls {
        interface ge-0/0/0.0;
        interface ge-0/0/1.0;
        interface fe-0/0/6.0;
    }
    bgp {
        group vpls {
            type internal;
            local-address 10.0.6.2;
            family l2vpn {
                signaling;
            }
            neighbor 10.1.2.4;
        }
    }
    isis {
        level 1 {
            disable;
            wide-metrics-only;
        }
        interface ge-0/0/0.0;
        interface ge-0/0/1.0;
        interface fe-0/0/6.0;
        interface lo0.0 {
            passive;
        }
    }
    ldp {
        interface ge-0/0/0.0;
        interface ge-0/0/1.0;
        interface fe-0/0/6.0;
        interface fe-0/0/7.0 {
            disable;
        }
        interface lo0.0;
    }
}

Configure encapsulation vpls in CE facing interface

interfaces {
    ge-0/0/1 {
        description R7-RIP_GW;
        encapsulation ethernet-vpls;
        unit 0 {
            family vpls;
        }
    }

Configure Instance for BGP-signaled PE
In this example i use maximum site 10
You must configuring route-distinguisher, vrf-target and no-tunnel-services

routing-instances {
    vpls {
        instance-type vpls;
        interface fe-0/0/3.0;
        route-distinguisher 10.0.6.2:10;
        vrf-target target:65000:10;
        protocols {
            vpls {
                site-range 10;
                no-tunnel-services;
                site R2 {
                    site-identifier 2;
                }
            }
        }
    }
}

Configure Instance for LDP-signaled PE

routing-instances {
    vpls {
        instance-type vpls;
        interface ge-0/0/1.0;
        route-distinguisher 10.0.9.7:10;
        vrf-target target:65000:10;
        protocols {
            vpls {
                no-tunnel-services;
                vpls-id 100;
                neighbor 10.0.3.5;
                neighbor 10.0.9.6;
            }
        }
    }
}

R5 is act as BGP to LDP signaling so the configuration is a bit different with other PE
you need to configure mesh-group (this command is hidden in srx210-series)

routing-instances {
    vpls {
        instance-type vpls;
        route-distinguisher 10.0.3.5:10;
        vrf-target target:65000:10;
        protocols {
            vpls {
                site-range 10;
                no-tunnel-services;
                site R5 {
                    site-identifier 5;
                }
                vpls-id 100;
                mesh-group ldp-1 {
                    neighbor 10.0.9.6;
                    neighbor 10.0.9.7;
                }
            }
        }
    }
}

Now Lets we troubleshoot the configuration

I will show route at R5

lab@AREMA-R5# run show route |no-more

inet.0: 30 destinations, 30 routes (30 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

….

inet.3: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.3/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.2 via ge-0/0/0.0
10.0.3.4/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0
10.0.6.1/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.2 via ge-0/0/0.0, Push 301184
10.0.6.2/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.2 via ge-0/0/0.0, Push 301296
                      to 10.0.2.10 via ge-0/0/1.0, Push 300048
10.0.9.6/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.8.5 via fe-0/0/6.0
10.0.9.7/32        *[LDP/9] 05:14:15, metric 1
                    > to 10.0.8.10 via fe-0/0/5.0
10.1.2.4/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0, Push 299776
10.1.2.5/32        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0, Push 299792

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

49.0000.0000.0000.0000.0005/88               
                   *[Direct/0] 2d 14:12:00
                    > via lo0.0

mpls.0: 23 destinations, 23 routes (23 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 2d 14:12:02, metric 1
                      Receive
1                  *[MPLS/0] 2d 14:12:02, metric 1
                      Receive
2                  *[MPLS/0] 2d 14:12:02, metric 1
                      Receive
262145             *[VPLS/7] 07:26:15
                    > via lsi.1048638, Pop     
262146             *[VPLS/7] 05:08:43
                    > via lsi.1048644, Pop     
262402             *[VPLS/7] 07:25:12
                    > via lsi.1048641, Pop     
262403             *[VPLS/7] 06:31:22
                    > via lsi.1048642, Pop     
301120             *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.2 via ge-0/0/0.0, Pop     
301120(S=0)        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.2 via ge-0/0/0.0, Pop     
301136             *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.2 via ge-0/0/0.0, Swap 301184
301152             *[LDP/9] 05:14:27, metric 1
                      to 10.0.2.2 via ge-0/0/0.0, Swap 301296
                    > to 10.0.2.10 via ge-0/0/1.0, Swap 300048
301168             *[LDP/9] 05:14:27, metric 1
                    > to 10.0.8.5 via fe-0/0/6.0, Pop     
301168(S=0)        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.8.5 via fe-0/0/6.0, Pop     
301184             *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0, Pop     
301184(S=0)        *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0, Pop     
301200             *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0, Swap 299776
301216             *[LDP/9] 05:14:27, metric 1
                    > to 10.0.2.10 via ge-0/0/1.0, Swap 299792
301232             *[LDP/9] 05:14:15, metric 1
                    > to 10.0.8.10 via fe-0/0/5.0, Pop     
301232(S=0)        *[LDP/9] 05:14:15, metric 1
                    > to 10.0.8.10 via fe-0/0/5.0, Pop     
lsi.1048638        *[VPLS/7] 07:26:15, metric2 1
                    > to 10.0.8.5 via fe-0/0/6.0, Push 262145
lsi.1048644        *[VPLS/7] 05:08:43, metric2 1
                    > to 10.0.8.10 via fe-0/0/5.0, Push 262145
lsi.1048641        *[VPLS/7] 07:25:12, metric2 1
                    > to 10.0.2.2 via ge-0/0/0.0, Push 262149, Push 301296(top)
                      to 10.0.2.10 via ge-0/0/1.0, Push 262149, Push 300048(top)
lsi.1048642        *[VPLS/7] 06:31:22, metric2 1
                    > to 10.0.2.2 via ge-0/0/0.0, Push 262149

bgp.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.3:10:3:1/96               
                   *[BGP/170] 06:31:22, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.2.2 via ge-0/0/0.0
10.0.6.2:10:2:1/96               
                   *[BGP/170] 07:25:12, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.2.2 via ge-0/0/0.0, Push 301296
                      to 10.0.2.10 via ge-0/0/1.0, Push 300048

vpls.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.3:10:3:1/96               
                   *[BGP/170] 06:31:22, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.2.2 via ge-0/0/0.0
10.0.3.5:10:5:1/96               
                   *[L2VPN/170/-101] 2d 14:11:57, metric2 1
                      Indirect
10.0.6.2:10:2:1/96               
                   *[BGP/170] 07:25:12, localpref 100, from 10.1.2.4
                      AS path: I
                    > to 10.0.2.2 via ge-0/0/0.0, Push 301296
                      to 10.0.2.10 via ge-0/0/1.0, Push 300048

l2circuit.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.9.6:NoCtrlWord:5:100:Local/96               
                   *[VPLS/7] 07:25:56, metric2 1
                    > to 10.0.8.5 via fe-0/0/6.0
10.0.9.6:NoCtrlWord:5:100:Remote/96               
                   *[LDP/9] 07:25:56
                      Discard
10.0.9.7:NoCtrlWord:5:100:Local/96               
                   *[VPLS/7] 05:08:43, metric2 1
                    > to 10.0.8.10 via fe-0/0/5.0
10.0.9.7:NoCtrlWord:5:100:Remote/96               
                   *[LDP/9] 05:08:43
                      Discard

lab@AREMA-R5# run show vpls connections
Layer-2 VPN connections:

Legend for connection status (St)  
EI — encapsulation invalid      NC — interface encapsulation not CCC/TCC/VPLS
EM — encapsulation mismatch     WE — interface and instance encaps not same
VC-Dn — Virtual circuit down    NP — interface hardware not present
CM — control-word mismatch      -> — only outbound connection is up
CN — circuit not provisioned    <- — only inbound connection is up
OR — out of range               Up — operational
OL — no outgoing label          Dn — down                     
LD — local site signaled down   CF — call admission control failure     
RD — remote site signaled down  SC — local and remote site ID collision
LN — local site not designated  LM — local site ID not minimum designated
RN — remote site not designated RM — remote site ID not minimum designated
XX — unknown connection status  IL — no incoming label
MM — MTU mismatch               MI — Mesh-Group ID not availble
BK — Backup connection          ST — Standby connection
PF — Profile parse failure      PB — Profile busy
RS — remote site standby

Legend for interface status
Up — operational          
Dn — down

Instance: vpls
  BGP-VPLS State
  Local site: R5 (5)
    connection-site           Type  St     Time last up          # Up trans
    2                         rmt   Up     Oct 20 16:17:42 2010           1
      Remote PE: 10.0.6.2, Negotiated control-word: No
      Incoming label: 262402, Outgoing label: 262149
      Local interface: lsi.1048641, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls vpls local site 5 remote site 2
    3                         rmt   Up     Oct 20 17:11:32 2010           1
      Remote PE: 10.0.3.3, Negotiated control-word: No
      Incoming label: 262403, Outgoing label: 262149
      Local interface: lsi.1048642, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls vpls local site 5 remote site 3
  LDP-VPLS State
  VPLS-id: 100
  Mesh-group connections: ldp-1
    Neighbor                  Type  St     Time last up          # Up trans
    10.0.9.7(vpls-id 100)     rmt   Up     Oct 20 18:34:10 2010           1
      Remote PE: 10.0.9.7, Negotiated control-word: No
      Incoming label: 262146, Outgoing label: 262145
      Negotiated PW status TLV: No
      Local interface: lsi.1048644, Status: Up, Encapsulation: ETHERNET
        Description: Intf - vpls vpls neighbor 10.0.9.7 vpls-id 100
    10.0.9.6(vpls-id 100)     rmt   Up     Oct 20 16:16:54 2010           2
      Remote PE: 10.0.9.6, Negotiated control-word: No
      Incoming label: 262145, Outgoing label: 262145
      Negotiated PW status TLV: No
      Local interface: lsi.1048638, Status: Up, Encapsulation: ETHERNET
        Description: Intf - vpls vpls neighbor 10.0.9.6 vpls-id 100

[edit]
lab@AREMA-R5# run show vpls flood
Name: vpls
CEs: 0
VEs: 4
Flood Routes:
  Prefix    Type          Owner                 NhType          NhIndex
  0x46/32   IFF_FLOOD     lsi.1048641           comp            592    
  0x47/32   IFF_FLOOD     lsi.1048642           comp            592    
  0x44/32   IFF_FLOOD     lsi.1048638           comp            590    
  0x45/32   IFF_FLOOD     lsi.1048644           comp            590    

[edit]
lab@AREMA-R5# run show vpls statistics
VPLS statistics:

Instance: vpls
   Local interface: lsi.1048638, Index: 68
   Remote PE: 10.0.9.6
     Current MAC count:                     0
   Local interface: lsi.1048644, Index: 69
   Remote PE: 10.0.9.7
     Current MAC count:                     0
   Local interface: lsi.1048641, Index: 70
   Remote PE: 10.0.6.2
     Current MAC count:                     2
   Local interface: lsi.1048642, Index: 71
   Remote PE: 10.0.3.3
     Current MAC count:                     8

[edit]
lab@AREMA-R5# run show route forwarding-table family vpls
Routing table: vpls.vpls
VPLS:
Destination        Type RtRef Next hop           Type Index NhRef Netif
default            perm     0                    rjct   562     1
lsi.1048638        user     0                    comp   590     3
lsi.1048644        user     0                    comp   590     3
lsi.1048641        user     0                    comp   592     3
lsi.1048642        user     0                    comp   592     3
00:00:48:3b:df:d9/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
00:10:db:7e:09:62/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
00:1e:e5:9b:8f:ed/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
00:24:01:d2:3e:d2/48 dynm     0                  indr 262145     5
                              10.0.2.10         Push 262149, Push 300048(top)   577     1 ge-0/0/1.0
00:24:1d:b5:8c:20/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
00:aa:00:00:01:e1/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
b0:c6:9a:88:df:02/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
b0:c6:9a:8b:29:82/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0
ca:00:0f:34:00:08/48 dynm     0                  indr 262145     5
                              10.0.2.10         Push 262149, Push 300048(top)   577     1 ge-0/0/1.0
cc:01:0f:34:00:00/48 dynm     0                  indr 262146    11
                              10.0.2.2          Push 262149   593     2 ge-0/0/0.0

[edit]
lab@AREMA-R5# run show bgp summary   
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l2vpn.0            2          2          0          0          0          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…
10.1.2.4              65000       1035       1036       0       4     7:26:12 Establ
  bgp.l2vpn.0: 2/2/2/0
  vpls.l2vpn.0: 2/2/2/0

[edit]
lab@AREMA-R5# run show ldp neighbor
Address            Interface          Label space ID         Hold time
10.0.9.6           lo0.0              10.0.9.6:0               32
10.0.9.7           lo0.0              10.0.9.7:0               40
10.0.8.10          fe-0/0/5.0         10.0.9.7:0               11
10.0.8.5           fe-0/0/6.0         10.0.9.6:0               14
10.0.2.2           ge-0/0/0.0         10.0.3.3:0               14
10.0.2.10          ge-0/0/1.0         10.0.3.4:0               14

PE1#sh ip arp f0/0
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  10.0.5.2                -   ca00.0f34.0008  ARPA   FastEthernet0/0
Internet  10.0.5.150             65   cc01.0f34.0000  ARPA   FastEthernet0/0
Internet  10.0.5.122              0   b0c6.9a8f.1745  ARPA   FastEthernet0/0
Internet  10.0.5.77              17   0024.01d2.3ed2  ARPA   FastEthernet0/0
Internet  10.0.5.111              1   0014.f60f.a5b1  ARPA   FastEthernet0/0
Internet  10.0.5.135            170   001d.729a.376f  ARPA   FastEthernet0/0

lab@AREMA-RIP-SW# run show arp no-resolve
MAC Address       Address         Interface     Flags
ca:00:0f:34:00:08 10.0.5.2        fe-0/0/5.0     none
00:24:01:d2:3e:d2 10.0.5.77       fe-0/0/5.0     none
00:14:f6:0f:a5:b1 10.0.5.111      fe-0/0/5.0     none
cc:01:0f:34:00:00 10.0.5.150      fe-0/0/5.0     none
Total entries: 4

lab@AREMA-RIP-SW# run ping rapid 10.0.5.2
PING 10.0.5.2 (10.0.5.2): 56 data bytes
!!!!!
— 10.0.5.2 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.170/19.633/41.061/16.754 ms

[edit interfaces fe-0/0/5]
lab@AREMA-RIP-SW# run ping rapid inet6 2001:100:cece::1
PING6(56=40+8+8 bytes) 2001:100:cece::100 –> 2001:100:cece::1
!!!!!
— 2001:100:cece::1 ping6 statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 4.244/14.976/44.500/14.979 ms

 

Tool Olive & GNS3 

Purpose: Emulate L3VPN & 6VPE between Cisco and Juniper

Goal: Each CE can ping inet4/inet6

Topology:

Comments:

1. Use OSPF on core Network 

2. CE1 (Juniper) PE1 (Cisco) P1(Juniper) P2(Cisco) PE2(Juniper) CE2(Cisco)

2. CE to PE use static route inet4/inet6 

3. Use LDP 

Example configuration on PE (Cisco)  

Create VRF vpnv6

!

vrf definition vpnv6

 rd 1000:777

 route-target export 1000:777

 route-target import 1000:777

 !

 address-family ipv4

 exit-address-family

 !

 address-family ipv6

 exit-address-family

!

Create routing vrf 

!

router bgp 1000

 no synchronization

 bgp log-neighbor-changes

 neighbor 2.2.2.2 remote-as 1000

 neighbor 2.2.2.2 update-source Loopback0

 no auto-summary

 !

 address-family vpnv4

  neighbor 2.2.2.2 activate

  neighbor 2.2.2.2 send-community both

 exit-address-family

 !

 address-family vpnv6

  neighbor 2.2.2.2 activate

  neighbor 2.2.2.2 send-community both

 exit-address-family

 !

 address-family ipv4 vrf vpnv6

  no synchronization

  redistribute connected

  redistribute static metric 100

 exit-address-family

 !

 address-family ipv6 vrf vpnv6

  redistribute connected

  redistribute static metric 100

  no synchronization

 exit-address-family

!

ip classless

ip route vrf vpnv6 10.10.2.0 255.255.255.0 192.168.2.1

!

!

no ip http server

no ip http secure-server

!

ipv6 route vrf vpnv6 888:1::/126 CECE:2::1

!

Create vrf for PE juniper 

        routing-instances {

            vpnv6 {

                instance-type vrf;

                interface fxp5.50;

                interface lo0.100;

                route-distinguisher 1000:777;

                vrf-import vpnv6-import;

                vrf-export vpnv6-export;

                vrf-target target:1000:777;

                vrf-table-label;

                routing-options {

                    rib vpnv6.inet6.0 {

                        static {

                            route 777:1::/126 next-hop cece:1::2;

                        }

                    }

                    static {

                        route 10.10.1.0/24 next-hop 192.168.1.2;

                    }

                }

            }

        }

create routing protocol bgp included

        protocols {

            mpls {

                ipv6-tunneling;

                icmp-tunneling;

                interface fxp4.30;

                interface lo0.41;

            }

            bgp {

                group tope1 {

                    type internal;

                    local-address 2.2.2.2;

                    family inet-vpn {

                        any;

                    }

                    family inet6-vpn {

                        any;

                    }

                    neighbor 1.1.1.1;

                }

            }

            ospf {

                traffic-engineering;

                area 0.0.0.0 {

                    interface fxp4.30;

                    interface lo0.41 {

                        passive;

                    }

                }

            }

            ldp {

                interface fxp4.30;

                interface lo0.41;

            }

        }

now at least one commity must-be added if we want to redistribute vrf routing to bgp core routing 

        policy-options {

            policy-statement vpnv6-export {

                term 1 {

                    from {

                        protocol static;

                        route-filter 10.10.1.0/24 exact;

                    }

                    then {

                        community add vpnv6;

                        accept;

                    }

                }

                term 2 {

                    from {

                        protocol static;

                        family inet6;

                    }

                    then {

                        community add vpnv6;

                        accept;

                    }

                }

                term 3 {

                    then reject;

                }

            }

            policy-statement vpnv6-import {

                term 1 {

                    from {

                        protocol bgp;

                        community vpnv6;

                    }

                    then accept;

                }

                term 2 {

                    then reject;

                }

            }

            community vpnv6 members target:1000:777;

        }

now let’s see the result 

root@Sioduy-Olive# run show bgp summary logical-system pe2 

Groups: 1 Peers: 1 Down peers: 0

Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending

bgp.l3vpn.0            3          3          0          0          0          0

bgp.l3vpn.2            0          0          0          0          0          0

Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…

1.1.1.1                1000          8          5       0       2          11 Establ

  bgp.l3vpn.0: 3/3/3/0

  bgp.l3vpn-inet6.0: 3/3/3/0

  vpnv6.inet.0: 3/3/3/0

  vpnv6.inet6.0: 3/3/3/0

root@Sioduy-Olive# run show route logical-system pe2 

vpnv6.inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.10.1.0/24       *[Static/5] 00:50:47

                    > to 192.168.1.2 via fxp5.50

10.10.2.0/24       *[BGP/170] 00:00:36, MED 100, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 21, Push 17(top)

172.17.1.1/32      *[BGP/170] 00:00:36, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 17, Push 17(top)

172.17.2.1/32      *[Direct/0] 01:37:25

                    > via lo0.100

192.168.1.0/30     *[Direct/0] 01:17:12

                    > via fxp5.50

192.168.1.1/32     *[Local/0] 01:17:12

                      Local via fxp5.50

192.168.2.0/30     *[BGP/170] 00:00:36, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 18, Push 17(top)

mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 01:47:44, metric 1

                      Receive

1                  *[MPLS/0] 01:47:44, metric 1

                      Receive

2                  *[MPLS/0] 01:47:44, metric 1

                      Receive

16                 *[VPN/0] 01:37:27

                      to table vpnv6.inet.0, Pop      

299888             *[LDP/9] 00:01:04, metric 1

                    > to 10.1.3.1 via fxp4.30, Pop      

299888(S=0)        *[LDP/9] 00:01:04, metric 1

                    > to 10.1.3.1 via fxp4.30, Pop      

299904             *[LDP/9] 00:01:04, metric 1

                    > to 10.1.3.1 via fxp4.30, Swap 18

299920             *[LDP/9] 00:00:56, metric 1

                    > to 10.1.3.1 via fxp4.30, Swap 17

                    

bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

1000:777:10.10.2.0/24                

                   *[BGP/170] 00:00:36, MED 100, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 21, Push 17(top)

1000:777:172.17.1.1/32                

                   *[BGP/170] 00:00:36, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 17, Push 17(top)

1000:777:192.168.2.0/30                

                   *[BGP/170] 00:00:36, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 18, Push 17(top)

inet6.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

::ffff:1.1.1.1/128 *[LDP/9] 00:00:56, metric 1

                    > to 10.1.3.1 via fxp4.30, Push 17

::ffff:10.1.1.0/126*[LDP/9] 00:01:04, metric 1

                    > to 10.1.3.1 via fxp4.30, Push 18

::ffff:10.1.2.0/126*[LDP/9] 00:01:04, metric 1

                    > to 10.1.3.1 via fxp4.30

vpnv6.inet6.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

777:1::/126        *[Static/5] 01:17:10

                    > to cece:1::2 via fxp5.50

888:1::/126        *[BGP/170] 00:00:36, MED 100, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 24, Push 17(top)

2001:100:1::1/128  *[BGP/170] 00:00:36, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 19, Push 17(top)

2001:200:1::1/128  *[Direct/0] 01:37:25

                    > via lo0.100

cece:1::/126       *[Direct/0] 01:17:12

                    > via fxp5.50

cece:1::1/128      *[Local/0] 01:17:12

                      Local via fxp5.50

cece:2::/126       *[BGP/170] 00:00:36, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 20, Push 17(top)

fe80::/64          *[Direct/0] 01:17:12

                    > via fxp5.50

fe80::2aa:0:3200:1e5/128

                   *[Local/0] 01:17:12

                      Local via fxp5.50

fe80::2aa:ff:fe00:1e0/128

                   *[Direct/0] 01:37:25

                    > via lo0.100

bgp.l3vpn-inet6.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

1000:777:888:1::/126               

                   *[BGP/170] 00:00:37, MED 100, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 24, Push 17(top)

1000:777:2001:100:1::1/128               

                   *[BGP/170] 00:00:37, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 19, Push 17(top)

1000:777:cece:2::/126               

                   *[BGP/170] 00:00:37, MED 0, localpref 100, from 1.1.1.1

                      AS path: ?

                    > to 10.1.3.1 via fxp4.30, Push 20, Push 17(top)

PE1# sh bgp all

For address family: VPNv4 Unicast

BGP table version is 12, local router ID is 1.1.1.1

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

              r RIB-failure, S Stale

Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path

Route Distinguisher: 1000:777 (default for vrf vpnv6)

*>i10.10.1.0/24     2.2.2.2                       100      0 i

*> 10.10.2.0/24     192.168.2.1            100         32768 ?

*> 172.17.1.1/32    0.0.0.0                  0         32768 ?

*> 192.168.2.0/30   0.0.0.0                  0         32768 ?

For address family: VPNv6 Unicast

BGP table version is 18, local router ID is 1.1.1.1

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

              r RIB-failure, S Stale

Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path

Route Distinguisher: 1000:777 (default for vrf vpnv6)

*>i777:1::/126      ::FFFF:2.2.2.2                100      0 i

*> 888:1::/126      ::                     100         32768 ?

*> 2001:100:1::1/128

                    ::                       0         32768 ?

*> CECE:2::/126     ::                       0         32768 ?

For address family: IPv4 Multicast

PE1# sh ip cef vrf vpnv6 10.10.1.0 detail 

10.10.1.0/24, epoch 0

  recursive via 2.2.2.2 label 16

    nexthop 10.1.1.2 FastEthernet0/0.1 label 299904

PE1# sh ipv6 cef vrf vpnv6 777:1::1 detail 

777:1::/126, epoch 0

  recursive via 2.2.2.2 label 16

    nexthop 10.1.1.2 FastEthernet0/0.1 label 299904

Time to trying traceroute CE to CE 

Traceroute inet4 from CE Cisco

CE2#traceroute 10.10.2.1 source 10.10.1.1        

Type escape sequence to abort.

Tracing the route to 10.10.2.1

  1 192.168.1.1 4 msec 4 msec 28 msec

  2 10.1.3.1 [MPLS: Labels 17/21 Exp 0] 560 msec 864 msec 356 msec

  3 10.1.2.1 [MPLS: Labels 299968/21 Exp 0] 444 msec 304 msec 292 msec

  4 192.168.2.2 [MPLS: Label 21 Exp 0] 500 msec 576 msec 512 msec

  5 10.10.2.1 848 msec 548 msec 996 msec

Traceroute inet4 from CE Juniper 

root@Sioduy-Olive# …oute logical-system ce1 10.10.1.1 source 10.10.2.1    

traceroute to 10.10.1.1 (10.10.1.1) from 10.10.2.1, 30 hops max, 40 byte packets

 1  192.168.2.2 (192.168.2.2)  156.684 ms  220.082 ms  104.520 ms

 2  10.1.1.2 (10.1.1.2)  228.051 ms  467.952 ms  159.210 ms

     MPLS Label=299904 CoS=0 TTL=1 S=0

     MPLS Label=16 CoS=0 TTL=1 S=1

 3  10.1.2.2 (10.1.2.2)  492.663 ms  315.623 ms  674.114 ms

     MPLS Label=16 CoS=0 TTL=1 S=0

     MPLS Label=16 CoS=0 TTL=2 S=1

 4  192.168.1.2 (192.168.1.2)  1168.506 ms  668.155 ms *

Traceroute inet6 from CE Cisco 

CE2#traceroute ipv6 

Target IPv6 address: 888:1::1

Source address: 777:1::1

Insert source routing header? [no]: 

Numeric display? [no]: 

Timeout in seconds [3]: 

Probe count [3]: 

Minimum Time to Live [1]: 

Maximum Time to Live [30]: 6

Priority [0]: 

Port Number [33434]: 

Type escape sequence to abort.

Tracing the route to 888:1::1

  1  *  *  * 

  2  *  *  * 

  3  *  *  * 

  4 CECE:2::2 624 msec 700 msec 708 msec

  5 888:1::1 360 msec 792 msec 416 msec

Traceroute inet6 from CE Juniper 

root@Sioduy-Olive# …gical-system ce1 777:1::1 source 888:1::1              

traceroute6 to 777:1::1 (777:1::1) from 888:1::1, 64 hops max, 12 byte packets

 1  cece:2::2 (cece:2::2)  182.869 ms  275.656 ms  205.303 ms

 2  * * *

 3  * * *

 4  777:1::1 (777:1::1)  747.897 ms  332.994 ms  478.554 ms

For detail configuration download at this link