The force switch just allows for the changes you have made to take effect
more quickly without having to wait for the timers.
On Mon, Jun 22, 2009 at 7:45 PM, Jerry Chan <temjin1997_at_gmail.com> wrote:
> Hi Ernest,
>
> i will try it soon, but what is the reason to force it to modify the
> router-id? is that not only a idenidifier?
>
> THanks,
> Jerry
>
>
> 2009/6/22 Ernest Wambari <ewambari_at_gmail.com>
>
>> Hi Jerry,
>>
>> Try hard-coding the mpls router id's on both ends using the:"mpls ldp
>> router-id <int> force".
>>
>> Would be a good idea to setup loopback interfaces on R1 and R3 for this.
>>
>> Be sure to use the force switch or disable and enable ldp on each serial
>> interface after the change.
>>
>> HTH,
>>
>> W.
>>
>>
>> On Mon, Jun 22, 2009 at 7:30 PM, Jerry Chan <temjin1997_at_gmail.com> wrote:
>>
>>> Hi Ernest,
>>>
>>> thanks for your reply,
>>> i cannot see anything on R3 when i type "sh mpls ldp nei"
>>> and i only can see the peer on R1 with R2.
>>>
>>> Thanks,
>>> Jerry Chan
>>>
>>> 2009/6/22 Ernest Wambari <ewambari_at_gmail.com>
>>>
>>> Hi Jerry,
>>>>
>>>> Check your mpls ldp router-ids.
>>>>
>>>> Use the "sh mpls ldp nei" to see if R1 and R3 are peering via the
>>>> expected interfaces.
>>>>
>>>> As Joe mentioned,looks like they are not.
>>>>
>>>> Regards,
>>>>
>>>> W.
>>>>
>>>> On Mon, Jun 22, 2009 at 6:42 PM, Jerry Chan <temjin1997_at_gmail.com>wrote:
>>>>
>>>>> Hi all expert,
>>>>>
>>>>> *I am now studying the MPLS, start to do the LDP workbook. (using GNS3)
>>>>> however, it cannot form peer with a simple connection between R1--R3
>>>>> using a
>>>>> serial link or frame-relay.*
>>>>>
>>>>> R1. config
>>>>> =======
>>>>> ip cef
>>>>> mpls label protocol ldp
>>>>> !
>>>>> interface Serial1/3
>>>>> ip address 150.1.13.1 255.255.255.0
>>>>> mpls ip
>>>>> !
>>>>>
>>>>> R3. config
>>>>> =======
>>>>> ip cef
>>>>> mpls label protocol ldp
>>>>> !
>>>>> interface Serial1/3
>>>>> ip address 150.1.13.3 255.255.255.0
>>>>> clock rate 64000
>>>>> mpls ip
>>>>> !
>>>>>
>>>>> *it can ping , can form ospf peer, but cannot form ldp peer. Am I do
>>>>> the
>>>>> wrong things?
>>>>> when i type debug mpls ldp tran even on both R1 and R3, it give me like
>>>>> these.*
>>>>>
>>>>> Rack10R1#
>>>>> *Jun 22 16:22:45.203: ldp: Rcvd ldp hello; Serial1/3, from 150.1.13.3 (
>>>>> 150.1.13.3:0), intf_id 0, opt 0xC
>>>>> *Jun 22 16:22:45.215: ldp: ldp Hello from 150.1.13.3 (150.1.13.3:0) to
>>>>> 224.0.0.2, opt 0xC
>>>>> *Jun 22 16:22:45.215: ldp: local idb = Serial1/3, holdtime = 15000,
>>>>> peer
>>>>> 150.1.13.3 holdtime = 15000
>>>>> *Jun 22 16:22:45.219: ldp: Link intvl min cnt = 2, intvl = 5000, idb =
>>>>> Serial1/3
>>>>> *Jun 22 16:22:45.831: ldp: Send ldp hello; Serial1/3, src/dst
>>>>> 150.1.13.1/224.0.0.2, inst_id 0
>>>>>
>>>>> Rack10R3#
>>>>> *Jun 22 16:19:38.887: ldp: Ignore rcvd dir hello to 150.1.13.3 from
>>>>> 150.1.12.1, Serial1/3; no dhcb
>>>>> *Jun 22 16:19:39.519: ldp: Rcvd ldp hello; Serial1/3, from 150.1.13.1 (
>>>>> 150.1.12.1:0), intf_id 0, opt 0xC
>>>>> *Jun 22 16:19:39.523: ldp: Send ldp hello; Serial1/3, src/dst
>>>>> 150.1.13.3/224.0.0.2, inst_id 0
>>>>> *Jun 22 16:19:39.527: ldp: ldp Hello from 150.1.13.1 (150.1.12.1:0) to
>>>>> 224.0.0.2, opt 0xC
>>>>> *Jun 22 16:19:39.531: ldp: local idb = Serial1/3, holdtime = 15000,
>>>>> peer
>>>>> 150.1.13.1 holdtime = 15000
>>>>> *Jun 22 16:19:39.531: ldp: Link intvl min cnt = 2, intvl = 5000, idb =
>>>>> Serial1/3
>>>>> *Jun 22 16:19:39.535: ldp: Opening ldp conn; adj 0x6771C238, 150.1.13.3
>>>>> <->
>>>>> 150.1.12.1; with normal priority
>>>>>
>>>>> *please kinldy to give me some hits.
>>>>>
>>>>> Thanks
>>>>> *Jerry
>>>>>
>>>>>
>>>>> Blogs and organic groups at http://www.ccie.net
>>>>>
>>>>> _______________________________________________________________________
>>>>> Subscription information may be found at:
>>>>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 22 2009 - 19:47:59 ART
This archive was generated by hypermail 2.2.0 : Wed Jul 01 2009 - 20:02:37 ART