I'm back to studying Service Provider material... but instead of continuing where I left off, INE Vol 1 Multicast Labs, I'm reading/re-reading 'MPLS Fundamentals'.
A lab I set up for AToM comes from chapter 10 of the book.
I tried to recreate the configuration from memory and being that it's only a few lines, I thought it would be easy.
I missed the configuration "mpls ldp router-id loopback 0 force" and until I put that command in, the VC never came up. This lab was for a simple HDLC connection.
What's the significance of this command? Why does the MPLS router-id have to be set?
Hmm...
*** Edit
I'm assuming the LDP router-id has to be the same has the xconnect peer. I'm guessing if I didn't for the router-id to be the loopback but specified the outgoing interfaces as the xconnect peers, it would have worked. Time to lab it up.
*** Edit 2
Odd, I tested it out, removed the mpls ldp router-id force command, clear mpls ldp nei *, xconnect to the serial interface of the remote end, the L2 VC circuit showed up, but the CE router interfaces never came up.
Sunday, February 28, 2010
Monday, February 15, 2010
Side Tracked - Passed CCNA Voice.
With 2010 comes new goals, both personal and professional. I decided to take some time to study, lab up, and take the CCNA Voice 640-460 exam. Overall it was pretty straightforward, I studied using a single router with an AIM-CUE for CME and CUE, CBT-Nuggets and the OECG. No access to an UC-500 but that's ok. Was this a personal goal? No, it was work related.
Now I'm debating on CCVP... what to do... what to do...
Now I'm debating on CCVP... what to do... what to do...
Subscribe to:
Comments (Atom)