I should have elaborated a bit more. The MPLS router-id is like the OSPF router-id and will go ahead and choose the highest loopback (if one exists). Just like with OSPF the router-id won't change until reload, and so to force this behavior we issue the "force" option after the "mpls ldp router-id" command. This will allow us the change the router-id on-the-fly without needing to reload the router.
HTH Thank you, Steve Di Bias Network Engineer - Information Systems Valley Health System - Las Vegas Office - 702- 369-7594 Cell - 702-241-1801 [email protected] -----Original Message----- From: Di Bias, Steve Sent: Thursday, June 02, 2011 1:01 PM To: 'Samir Idris'; [email protected] Subject: RE: [OSL | CCIE_RS] mpls ldp router-id? Samir, use the force! "mpls ldp router-id lo0 force" ;) Thank you, Steve Di Bias Network Engineer - Information Systems Valley Health System - Las Vegas Office - 702- 369-7594 Cell - 702-241-1801 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Samir Idris Sent: Thursday, June 02, 2011 12:09 PM To: [email protected] Subject: [OSL | CCIE_RS] mpls ldp router-id? 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 UHS Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient (s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this information is prohibited. If this was sent to you in error, please notify the sender by reply e-mail and destroy all copies of the original message. _______________________________________________ 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
