Have you re-established the peering after applying the command "mpls ldp
router-id Loopback99"? The LDP router-id of Lo99 will be used when the
peering is started again. You need to do either
> clear mpls ldp neighbor (A.B.C.D|*)
or
> mpls ldp router-id Loopback99 force
to force the change immediately.

Does that solve your issue?

Martin


On 6/2/2011 9:08 PM, Samir Idris wrote:
> Hi Guys,
> 
> I am just wondering when I do "mpls ldp route-id lo99" should it not start
> peering sending neighbour it's identity as lo99?  I am peering R1 and R2.
> Gere is the config:
> 
> --------------------------------------------------------------------
> 
> R1:
> 
> R1#sh run | s mpls
>  mpls ip
> mpls ldp router-id Loopback99
> 
> Building configuration...
> Current configuration : 72 bytes
> !
> interface Loopback99
>  ip address 111.111.111.111 255.255.255.255
> end
> 
> R1#sh run int lo0
> Building configuration...
> Current configuration : 65 bytes
> !
> interface Loopback0
>  ip address 200.0.0.1 255.255.255.255
> end
> 
> R2:
> 
> R2#sh run | s mpls
> mpls label protocol ldp
>  mpls ip
> mpls ldp router-id Loopback0
> 
> R2#sh run int lo0
> Building configuration...
> Current configuration : 65 bytes
> !
> interface Loopback0
>  ip address 200.0.0.2 255.255.255.255
> end
> R2#sh run int lo99
> Building configuration...
> Current configuration : 72 bytes
> !
> interface Loopback99
>  ip address 222.222.222.222 255.255.255.255
> end
> ----------------------------------------------------------------------
> Peering happens but regardless it picks the highest loopback on both the
> routers:
> 
> R1#sh mpls ldp ne
>     Peer LDP Ident: 222.222.222.222:0; Local LDP Ident 200.0.0.1:0
>         TCP connection: 222.222.222.222.16331 - 200.0.0.1.646
>         State: Oper; Msgs sent/rcvd: 47/46; Downstream
>         Up time: 00:23:03
>         LDP discovery sources:
>           FastEthernet0/1, Src IP addr: 192.168.12.2
>         Addresses bound to peer LDP Ident:
>           192.168.12.2    192.168.24.2    192.168.23.2    192.168.25.2
>           200.0.0.2       222.222.222.222
> 
> R2#sh mpls ldp ne
>     Peer LDP Ident: 200.0.0.1:0; Local LDP Ident 222.222.222.222:0
>         TCP connection: 200.0.0.1.646 - 222.222.222.222.16331
>         State: Oper; Msgs sent/rcvd: 47/47; Downstream
>         Up time: 00:23:25
>         LDP discovery sources:
>           FastEthernet0/0, Src IP addr: 192.168.12.1
>         Addresses bound to peer LDP Ident:
>           10.10.10.1      192.168.12.1    200.0.0.1       111.111.111.111
> 
> Cany anyone guide?  Thanks.
> 
> Regards,
> Samir Idris.
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please 
> visit www.ipexpert.com
> 
> Are you a CCNP or CCIE and looking for a job? Check out 
> www.PlatinumPlacement.com
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Reply via email to