Announcing the Winners of the Junos IP/MPLS Challenge!
Nov 18, 2013
We found out that we have a lot of IP/MPLS pros out there from our latest contest! Congrats to the winners and stay tuned for another challenge in December. See the solution to the challenge below the winners.
1st Place – 200 VM Units
2nd Place-100 VM Units Tim Hynard
3rd Place – 50 VM Units Peter Riad
Additional Winners - 10 VM Units
Mario Perez Benavides
"The problem in this challenges seems to be that PE2 is advertising its router-id/transport address as 172.16.22.2:
juniper@P> show ldp neighbor 172.16.2.1 extensive Address Interface Label space ID Hold time 172.16.2.1 ge-0/0/2.0 172.16.22.2:0 13 Transport address: 172.16.22.2, Configuration sequence: 1 Up for 1d 21:05:46 Reference count: 1 Hold time: 15, Proposed local/peer: 15/15 Hello flags: none Neighbor types: discovered
As this IP is not reachable via IP to form a LDP session:
juniper@P> show ldp session 172.16.22.2 Address State Connection Hold time Adv. Mode 172.16.22.2 Nonexistent Closed 0 DU juniper@P> show route 172.16.22.2 juniper@P>
So there are no LDP FECs exchanged between PE1 and PE2.
As this is a BGP free core router P does not have any knowledge of the routes thus the end-to-end ping does not work.
The solution would be to get Router PE2 to advertise a router-id/transport address at which it is reachable.
The easiest way would be to:
set routing-options router-id 172.16.22.22
as 172.16.22.22 is the loopback IP of PE2 and is reachable via ISIS from router P
juniper@P> show route 172.16.22.22 inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 172.16.22.22/32 *[IS-IS/18] 1d 21:08:55, metric 10 > to 172.16.2.1 via ge-0/0/2.0
Afterwards LDP LSPs should be up between PE1 and PE2 and the ping should succeed."