guruprasadr Sat, 07/18/2009 - 04:42
User Badges:
  • Gold, 750 points or more

HI Siva,


Sample Config with N/W eg:


PE3 ----> P ----> PE4


PE3:

----

mpls ldp neighbor 172.16.0.4 targeted ldp


PE4:

----

mpls ldp neighbor 172.16.0.3 targeted ldp


1) Before the 'config' ensure the IGP reach ability between PE3-PE4 is Up & Running.


2) LDP between PE3-P & P-PE4 is Up & Running.


Please see below some show output after successful configuration:


From PE3:

---------

PE3#sh mpls ldp nei

Peer LDP Ident: 172.16.0.4:0; Local LDP Ident 172.16.0.3:0

TCP connection: 172.16.0.4.35909 - 172.16.0.3.646

State: Oper; Msgs sent/rcvd: 37/36; Downstream

Up time: 00:00:10

LDP discovery sources:

Targeted Hello 172.16.0.3 -> 172.16.0.4, active, passive

Addresses bound to peer LDP Ident:

172.16.34.2 172.16.0.4 172.16.46.1 172.16.11.1

172.16.4.1



From PE4:

---------

Peer LDP Ident: 172.16.0.3:0; Local LDP Ident 172.16.0.4:0

TCP connection: 172.16.0.3.646 - 172.16.0.4.35909

State: Oper; Msgs sent/rcvd: 38/41; Downstream

Up time: 00:02:34

LDP discovery sources:

Targeted Hello 172.16.0.4 -> 172.16.0.3, active, passive

Addresses bound to peer LDP Ident:

172.16.0.3 172.16.34.1 172.16.36.1 172.16.10.1

172.16.3.1



Hope I am Informative, Pls Rate if HELPS


Best Regards,


Guru Prasad R.

Harold Ritter Sat, 07/18/2009 - 17:47
User Badges:
  • Cisco Employee,

Siva,


There is a very limited number of scenarios in which you need to explicitly configure targeted LDP. Most of the time the targeted LDP session will be implicitly configured by either configuring VPLS, EoMPLS or LDP over TE tunnels. Could you please tell us what you are trying to achieve.


Regards

Actions

This Discussion