Alright, thanks all for your help.

On Thu, Mar 11, 2010 at 3:24 PM, Bryan Bartik <[email protected]> wrote:

> It's just legacy stuff left over. TDP was the old cisco proprietary
> protocol used to distribute labels. I guess the debug messages still have
> it.
>
>
> On Thu, Mar 11, 2010 at 1:12 PM, Victor Reyes II <[email protected]>wrote:
>
>> Bryan,
>>
>>       That did the trick. The LDP neighbor relationship came up. I just
>> have two last questions. When I entered "mpls ldp router-id Lo0 force"  I
>> got a console message which stated "%TDP-5-INFO: Default-IP-Routing-Table:
>> TDP ID removed" as shown below. Why would TDP be running since I enabled
>> "mpls label protocol ldp" globally? And would this happen every single time
>> one has multiple Loopback interfaces configured?
>>
>> Thanks
>>
>> R1 Output
>>
>> R1(config)#mpls ldp router-id lo0 ?
>>   force  Forcibly change the LDP router id
>>   <cr>
>>
>> R1(config)#mpls ldp router-id lo0 force
>> R1(config)#
>> *Mar  1 02:22:51.787: %TDP-5-INFO: Default-IP-Routing-Table: TDP ID
>> removed
>>
>>
>>
>> R2 Output
>>
>> R2(config)#
>> R2(config)#
>> *Mar  1 02:25:54.807: %TDP-5-INFO: Default-IP-Routing-Table: TDP ID
>> removed
>>
>>
>>
>>
>> On Thu, Mar 11, 2010 at 3:04 PM, Bryan Bartik <[email protected]>wrote:
>>
>>> Try "mpls ldp router-id lo0 force" with "force" at then end.
>>>
>>>
>>> On Thu, Mar 11, 2010 at 1:00 PM, Victor Reyes II <[email protected]>wrote:
>>>
>>>> Okay. So how can I change the LDP ID from Loopback1 to Loopback0.  I
>>>> tried the command "mpls ldp router-id lo0" but that did not help.
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Mar 11, 2010 at 2:57 PM, Wouter Prins <[email protected]> wrote:
>>>>
>>>>> R1#show mpls ldp discovery
>>>>>  Local LDP Identifier:
>>>>>     11.1.1.1:0
>>>>>     Discovery Sources:
>>>>>     Interfaces:
>>>>>         FastEthernet0/0 (ldp): xmit/recv
>>>>>  *           LDP Id: **22.2.2.2:0* <http://22.2.2.2:0/>*; no route*
>>>>>
>>>>> Last line says it all ;)
>>>>>
>>>>> On 11 March 2010 20:53, Victor Reyes II <[email protected]> wrote:
>>>>>
>>>>>> Bryan,
>>>>>>
>>>>>>      If you look at the configs R2 Loopback 0 (2.2.2.2) is in OSPF.
>>>>>>  Also, I do I have reachability between R1-loopback0 to R2-loopback0. 
>>>>>> Below
>>>>>> are the outputs. I believe I see the issue. R1 and R2 are using 11.1.1.1 
>>>>>> and
>>>>>> 22.2.2.2 as there LDP Identifier respectively. However, since neither
>>>>>> network are advertised in OSPF the LDP neighbor relationship is not 
>>>>>> coming
>>>>>> up. However I tried using the command "mpls ldp router-id lo0" on both
>>>>>> router to change the LDP identifier which did not work. What can I do?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>> R1 Outputs
>>>>>>
>>>>>> R1#show mpls ldp discovery
>>>>>>  Local LDP Identifier:
>>>>>>     11.1.1.1:0
>>>>>>     Discovery Sources:
>>>>>>     Interfaces:
>>>>>>         FastEthernet0/0 (ldp): xmit/recv
>>>>>>             LDP Id: 22.2.2.2:0; no route
>>>>>>
>>>>>> R1#sh ip ospf int brief
>>>>>> Interface    PID   Area            IP Address/Mask    Cost  State Nbrs
>>>>>> F/C
>>>>>> Lo0          1     0               1.1.1.1/32         1     LOOP  0/0
>>>>>> Lo1          1     0               11.1.1.1/24        1     LOOP  0/0
>>>>>> Fa0/0        1     0               10.1.12.1/24       10    BDR   1/1
>>>>>>
>>>>>>
>>>>>> R2 Outputs
>>>>>>
>>>>>> R2#sh ip ospf int brief
>>>>>> Interface    PID   Area            IP Address/Mask    Cost  State Nbrs
>>>>>> F/C
>>>>>> Lo0          1     0               2.2.2.2/32         1     LOOP  0/0
>>>>>> Fa0/1        1     0               10.1.23.2/24       10    BDR   1/1
>>>>>> Fa0/0        1     0               10.1.12.2/24       10    DR    1/1
>>>>>>
>>>>>>
>>>>>> R2#ping 1.1.1.1 source lo0
>>>>>>
>>>>>> Type escape sequence to abort.
>>>>>> Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
>>>>>> Packet sent with a source address of 2.2.2.2
>>>>>> !!!!!
>>>>>> Success rate is 100 percent (5/5), round-trip min/avg/max = 20/62/100
>>>>>> ms
>>>>>>
>>>>>>
>>>>>> R2#sh mpls ldp discovery
>>>>>>  Local LDP Identifier:
>>>>>>     22.2.2.2:0
>>>>>>     Discovery Sources:
>>>>>>     Interfaces:
>>>>>>         FastEthernet0/0 (ldp): xmit/recv
>>>>>>             LDP Id: 11.1.1.1:0
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 11, 2010 at 1:57 PM, Bryan Bartik 
>>>>>> <[email protected]>wrote:
>>>>>>
>>>>>>> Victor,
>>>>>>>
>>>>>>> I don't see your R2 loopbacks in OSPF, make sure you have
>>>>>>> reachability between the LDP router-ids. Can you ping from loopback to
>>>>>>> loopback? Give the output of "show mpls ldp discovery".
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 11, 2010 at 11:28 AM, Victor Reyes II <[email protected]
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> I tried your suggesting and it did not work either.
>>>>>>>>
>>>>>>>> Message sent from my Droid
>>>>>>>>
>>>>>>>> On Mar 11, 2010 1:19 PM, "Wouter Prins" <[email protected]> wrote:
>>>>>>>>
>>>>>>>> hi!
>>>>>>>>
>>>>>>>> 1.) create the loopback 0 interface as /32
>>>>>>>> 2.) remove the ospf network type from the loopback interface
>>>>>>>>
>>>>>>>> Let me know if that works out. :)
>>>>>>>>
>>>>>>>> On 11 March 2010 19:13, Victor Reyes II <[email protected]> wrote:
>>>>>>>>
>>>>>>>>> >
>>>>>>>>> > Hi,
>>>>>>>>> >
>>>>>>>>> >   I am trying to configure a simple MPLS config. However, I am
>>>>>>>>> have trouble getting the ...
>>>>>>>>>  _______________________________________________
>>>>>>>>> For more information regarding industry leading CCIE Lab training,
>>>>>>>>> please visit www.ipexpert.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Wouter Prins
>>>>>>>> [email protected]
>>>>>>>> CCIE #25628
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> For more information regarding industry leading CCIE Lab training,
>>>>>>>> please visit www.ipexpert.com
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Bryan Bartik
>>>>>>> CCIE #23707 (R&S, SP), CCNP
>>>>>>> Sr. Support Engineer - IPexpert, Inc.
>>>>>>> URL: http://www.IPexpert.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Wouter Prins
>>>>> [email protected]
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> For more information regarding industry leading CCIE Lab training,
>>>> please visit www.ipexpert.com
>>>>
>>>>
>>>
>>>
>>> --
>>> Bryan Bartik
>>> CCIE #23707 (R&S, SP), CCNP
>>> Sr. Support Engineer - IPexpert, Inc.
>>> URL: http://www.IPexpert.com
>>>
>>
>>
>
>
> --
> Bryan Bartik
> CCIE #23707 (R&S, SP), CCNP
> Sr. Support Engineer - IPexpert, Inc.
> URL: http://www.IPexpert.com
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to