Hi, iBGP may not be supported as PE-CE protocol. Please see below doc. You may try to "configure  neighbor ip-address internal-vpn-client" http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/15-s/irg-15-s-book/irg-l3vpn-ibgp-pe-ce.html Regards, Akash ... View more

Hi Rajmohan, I don't think that for LSR to initiate targeted LDP session it is required to have tunnel configured on tail end but for targeted LDP to come up, tail end router also needs to send targeted LDP discovery packet and for that either you need to have tunnel configure or you can define static neighbor. Lab output: RP/0/RSP0/CPU0:R1 ----- RP/0/RSP0/CPU0:R2 1. when tunnel configured only on one side - R1 RP/0/RSP0/CPU0:R1#sh mpls ldp discovery Fri Jan 8 14:11:55.442 UTC Local LDP Identifier: 49.44.4.45:0 Discovery Sources: Interfaces: Bundle-Ether123 : xmit tunnel-te100 : xmit Target: 1.55.55.55 Targeted Hellos: 49.44.4.45 -> 1.55.55.55 (active), xmit  <<<<<< only xmit 2. configured static neighbor on tail end router (R2) RP/0/RSP0/CPU0:R2(config-ldp)# RP/0/RSP0/CPU0:R2(config-ldp)#neighbor 49.44.4.45 targeted RP/0/RSP0/CPU0:R1#sh mpls ldp discovery Fri Jan 8 14:12:23.042 UTC Local LDP Identifier: 49.44.4.45:0 Discovery Sources: Interfaces: Bundle-Ether123 : xmit tunnel-te100 : xmit Target: 1.55.55.55 Targeted Hellos: 49.44.4.45 -> 1.55.55.55 (active/passive), xmit/recv  <<<<<<< now it is receiving LDP Hellos LDP Id: 1.55.55.55:0 Hold time: 90 sec (local:90 sec, peer:90 sec) RP/0/RSP0/CPU0:R1#sh mpls ldp neighbor Fri Jan 8 14:12:30.927 UTC Peer LDP Identifier: 1.55.55.55:0 TCP connection: 1.55.55.55:646 - 49.44.4.45:43047 Graceful Restart: No Session Holdtime: 180 sec State: Oper; Msgs sent/rcvd: 6/63; Downstream-Unsolicited Up time: 00:00:00 LDP Discovery Sources: Targeted Hello (49.44.4.45 -> 1.55.55.55, active/passive) Addresses bound to this peer: Regards, Akash ... View more

Hi Vadym,    Perfect :)   Why do I need to enable targeted-hello [Akash] Nondirectly Connected MPLS LDP Sessions If the LSR is more than one hop from its neighbor, it is non-directly connected to its neighbor. For these nondirectly connected neighbors, the LSR sends out a targeted Hello message as a UDP packet, but as a unicast message specifically addressed to that LSR. The nondirectly connected LSR responds to the Hello message and the two routers begin to establish an LDP session. This is called extended discovery. The default behavior of an LSR is to ignore requests from other LSRs that send targeted Hello messages. You can configure an LSR to respond to requests for targeted Hello messages by issuing the  mpls ldp discovery targeted-hello accept  command.    why do you think the LSP is broken if we do not use LDP [Akash]  If LDP is not enabled over tunnel, R2 will not advertise any label to R3 over tunnel interface and R3 will send unlabeled traffic to R2 [only rsvp label which is implicit null] , and ip lookup will happen on R2 so this is not end to end LSP. If ip loopup is happening on core router, i would say LSP is broken here. But if LDP is enabled over tunnel, R2 will advertise local label to R3 over targeted LDP session. L3 will send labeled packet [implicit null for RSVP, IGP label advertised by R2] to R2 and R2 will do label swapping and send traffic to R1. All the path label switching and LSP is intact. If it would have been L3vpn scenario, traffic would have been blackholed on core router where tunnel is getting terminated. In your case all core routers are having routes to destination hence reachability is there but LSP still broken.   Regards, Akash ... View more

Hi,   LDP is not coming up due to password mismatch. On PE1 you have configured ctB$1pM while on core it is ctB$1PM. Please correct password on either side and check if LDP comes up.   From below logs it is clear that both routers are able to transmit/receive each other's LDP hello. It should be related to password only.   PE1#sh mpls ldp disc  Local LDP Identifier:     10.100.100.214:0     Discovery Sources:     Interfaces:         GigabitEthernet1/0/0 (ldp): xmit/recv             LDP Id: 10.100.100.1:0   P1#sh mpls ldp discov Local LDP Identifier: 10.100.100.1:0 Discovery Sources:   Interfaces:     GigabitEthernet0/10/0/2 : xmit/recv       LDP Id: 10.100.100.214:0, Transport address: 10.100.100.214           Hold time: 15 sec (local:15 sec, peer:15 sec) ... View more

Hi,   You can try below ACL   ipv4 access-list ABF_IGW 10 deny tcp any eq www 192.168.1.0/24 20 permit tcp any eq www any nexthop1 track IGW ipv4 192.168.2.1 !   Configure IP SLA and Tracking ipsla operation 1 type icmp echo    destination address 192.168.2.1    frequency 5 schedule operation 1 start-time now life forever !   track IGW type rtr 1 reachability !   Reference :   https://supportforums.cisco.com/document/145271/abf-acl-based-forwarding-asr9k   Regards, Akash ... View more