[j-nsp] VPLS stuck in VC-Dn - inet.3 lookup problem

[Adam Vitkovsky]

Hi Alberto,

You need a working LSP (label switched path) end to end.

If you are running l2vpn AF between ASBRs (optB inter-as-mpls-vpn) the VC label gets signalled between the PEs via BGP l2vpn AF.
Remember the PEs will install the route only when they have reachability to the NH. Which in your case is the local-AS ASBR (if you're using NHS at the ASBR which I assume you are) so you are fine there.
You can check if the routes are exchanged by inspecting BGP l2vpn routing table

However the transport (hop-by-hop) labels need to be exchanged and stitched together end to end. 
Within AS this is taken care of by LDP or RSVP.
And usually in Inter-AS scenarios engineers tend to use RFC3107 (BGP-LU) i.e. BGP to exchange labels for NHs between ASBRs.

If you are not introducing remote-as PE routes into local AS with unchanged NH I guess you end up with PW stitching
Because each time BGP NH changes the associated label changes as well -which in this case is the VC label.
In that case you build a PW from ingress PE to ASBR another between ASBRs and another from ASBR to egress PE and you stitch these three pieces together.

It would be easiest to use (optC inter-as-mpls-vpn) so a RR that does not change NHs for VPN prefixes and RFC3107 end to end i.e. between PE to ASBR to ASBR to PE so ingress and egress PEs have direct reachability and hierarchical LSP to their NHs.
In which case they can signal PW end to end.


adam
> -----Original Message-----
> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf
> Of Alberto Santos
> Sent: 22 June 2015 23:39
> To: <juniper-nsp at puck.nether.net>
> Subject: [j-nsp] VPLS stuck in VC-Dn - inet.3 lookup problem
> 
> Hi,
> 
> I'm set upping VPLS + Inter AS option B with the following topology and I'm
> noticing a lookup problem between ASBRs.
> 
> LAN |--(AC)-----PE-----P----ASBR1----ASBR2----(AC)------| LAN
> 
> since I'm only running eBGP family l2vpn, ASBR2 does not have any other
> route in inet3 that could be use to bring the vpls connection up.
> 
> I tried to setup a /32 static route, it fixed the VPLS singling, but I'm
> still not learning any MAC address through VPLS.
> 
> has anyone experienced that before?
> 
> 
> ASBR2
> 
> user at ASBR2-re0# run show route 192.168.1.1
> 
> inet.0: 17 destinations, 18 routes (17 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
> 
> 192.168.1.0/30     *[Direct/0] 4d 06:01:43
>                     > via xe-1/0/0.100
> 
> 
> Instance: VPN2000
>   Local site: Site(3)
>     connection-site           Type  St     Time last up          # Up trans
>     1                         rmt   VC-Dn  Jun 23 00:21:05 2015           1
>       Remote PE: 192.168.1.1, Negotiated control-word: No
>       Incoming label: 800080, Outgoing label: 800002
>       Local interface: vt-1/1/10.1049344, Status: Up, Encapsulation: VPLS
>         Description: Intf - vpls VPN2000 local site 3 remote site 1
> ---------------------------
> 
> 
> 
> 
>  run show route
> inet.0: 17 destinations, 18 routes (17 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
> 
> 192.168.1.0/30     *[Direct/0] 4d 06:16:57
>                     > via xe-1/0/0.100
> 
> inet.3: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
> 
> 192.168.1.1/32     *[Static/5] 00:13:27
>                       to table inet.0
> 
> 
>  run show vpls connections
>     1                         rmt   Up     Jun 23 00:23:32 2015           2
>       Remote PE: 192.168.1.1, Negotiated control-word: No
>       Incoming label: 800080, Outgoing label: 800002
>       Local interface: vt-1/1/10.1049344, Status: Up, Encapsulation: VPLS
>         Description: Intf - vpls VPN2000 local site 3 remote site 1
> 
> 
> 
> 
> BR
> Alberto
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp