Juniper JUNOSE, Configuration Manual

Page: 431 / 738

0 in errors
0 in discard pkts
ASBR 3 in turn generates a new label, 50, to advertise with the VPN-IPv4 prefix to
its internal MP-BGP peer inside its autonomous system, AS 35. Indirect next
hop 4.4.4.4 is for the MP-IBGP peering between PE 4 (loopback address 4.4.4.4) and
ASBR 3. Indirect next hop 10.5.5.50 is ASBR 2.
host1:asbr3# show ip bgp vpn all field out-label
Prefix Out-label
10.10.10.11/32 44
host1:asbr3#
show ip bgp vpn all field in-label
Prefix In-label
10.10.10.11/32 50
host1:asbr3#
show ip bgp vpn all next-hops
Indirect next-hop 4.4.4.4
Resolution in IP route table of VR
IP indirect next-hop index 11
Reachable (metric 3)
Number of direct next-hops is 1
Direct next-hop ATM4/0.33 (33.33.33.2)
Resolution in IP tunnel-route table of VR
MPLS indirect next-hop index 28
Reachable (metric 3)
Number of direct next-hops is 1
Direct next-hop: MPLS next-hop 22
Reference count is 1
Indirect next-hop 10.5.5.50
Resolution in IP route table of VR
IP indirect next-hop index 4
Reachable (metric 0)
Number of direct next-hops is 1
Direct next-hop ATM6/1.21 (10.5.5.50)
Resolution in IP tunnel-route table of VR
MPLS indirect next-hop index 11
Reachable (metric 0)
Number of direct next-hops is 1
Direct next-hop ATM6/1.21.mpls
Reference count is 3
host1:asbr3#
show mpls forwarding brief
...
50 bgp swap to 44, on ATM6/1.21
In turn, ASBR 3 receives MPLS frames with label 50 (the in label) from PE 4 and
sends MPLS frames with label 44 (the out label) to ASBR 2.
PE 4 receives the VPN-IPv4 prefix with label 50:
host1:pe4# show ip bgp vpn all field out-label
Prefix Out-label
10.10.10.11/32 50
On PE 4, no in label is associated with the IPv4 prefix 10.10.10.11/32.
host1:pe4# show ip bgp vpn all field in-label
Prefix In-label
10.10.10.11/32 none
Providing IPv4 VPN Services Across Multiple Autonomous Systems
■ 395
Chapter 5: Configuring BGP-MPLS Applications