Routing

Hi Experts

Which table is used for L2VPN forwarding, when the traffic enters in to the interface (binds to some remote site id) which is in L2VPN routing instance. The show route table <routing instance name>.l2vpn.0 commands shows the remote site route with outer and innet label.

ps@lagavulin> show route table pine
pine.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.200.86.7:10:3:5/96
*[L2VPN/170/-101] 2w5d 22:06:26, metric2 1
Indirect
10.200.86.9:10:6:3/96
*[BGP/170] 23:08:57, localpref 100, from 10.200.86.9
AS path: I
> to 192.168.86.1 via ge-0/0/2.0, label-switched-path lagavulin-to-tormore
to 192.168.86.1 via ge-0/0/2.0, label-switched-path lagavulin-to-tormore-v2

My question is that how router knows that local interface of the router binds to what inner and outer lable???

Thanks

Hi

on ingress PE and egress PE, each local interface is bind to remote site ID and each remote site send the L2VPN route through MBGP with label base and offset not the actual VPN label. The ingress PE calculates the VPN label (innet lable using local site ID and lable base and offset and outer label as usual in Kompella draft. using the protocol nexthop of BGP route. The egress PE router calculates the same VPN lable using the remote site ID with label base and offset.

The outer label can be view using show route table <instance name>.l2vpn.0 extensive

The inner label can be view using show l2vpn connection instance <name of the routing instance>

(The outgoing label is for push and incoming label is for POP)

HTH

Thanks dear. But why in L2VPN, the inner label is not send by egress PE to ingress PE like it is in L3VPN?