I have a 4.3.4 ASR9010 (RSP4G/Trident based, up-to-date fpd versions) directly connected to the following with no issues:
2 x RSP4/Trident based XR 4.3.1 2 x ME3600 15.3(3)S 3 x ME3600 15.1(2)EY1a 1 x ME3600 15.3(1)S My config is a little more generic tho: mpls ldp router-id Loopback0 graceful-restart session protection log neighbor graceful-restart session-protection ! mldp make-before-break delay 0 logging notifications ! interface TenGigE0/0/0/0 ! interface TenGigE0/0/0/3 ! interface TenGigE0/0/0/4 ! interface TenGigE0/0/0/6 ! interface TenGigE0/0/0/8 ! interface TenGigE0/0/0/9 ! interface TenGigE0/0/0/12 ! interface TenGigE0/1/0/0 ! ! Are your fpd versions up to date too? On Mar 26, 2014, at 7:31 AM, Richard Hartmann <[email protected]> wrote: > Dear all, > > > I am having issues bringing up LDP on several interfaces on an ASR9001 > with IOS XR 4.3.4. All other machines I am referring to in this email > and in the rest of our backbone are happily talking with each other. > > In the context of this setup two ASR9001 and two ME3600x are relevant. > All four machines use different IOS versions, so I will designate them > as: > > > Machines: > * ASR-4.3.4 > * ASR-4.3.0 > * ME-15.3(2)S1 > * ME-15.3(1)S > > Relevant interconnections: > ASR-4.3.4 Te0/0/2/1 <> Te0/2 ME-15.3(2)S1 > ASR-4.3.4 Te0/0/2/2 <> Te0/1 ME-15.3(1)S > ASR-4.3.4 Te0/0/2/3 <> Te0/0/2/3 ASR-4.3.0 > > > > Now the problem is that TenGigE0/0/2/2 and TenGigE0/0/2/3 are stuck in > xmit, while TenGigE0/0/2/1 goes into xmit/recv as it should: > > RP/0/RSP0/CPU0:ASR-4.3.4#sh mpls ldp discovery > Local LDP Identifier: ASR-4.3.4:0 > Discovery Sources: > Interfaces: > TenGigE0/0/2/1 : xmit/recv > LDP Id: ME-15.3(2)S1:0, Transport address: ME-15.3(2)S1 > Hold time: 15 sec (local:15 sec, peer:15 sec) > > TenGigE0/0/2/2 : xmit > > TenGigE0/0/2/3 : xmit > > Targeted Hellos: > ASR-4.3.4 -> C6500 (active/passive), xmit/recv > LDP Id: C6500:0 > Hold time: 90 sec (local:90 sec, peer:90 sec) > > ASR-4.3.4 -> C6500 (active/passive), xmit/recv > LDP Id: C6500:0 > Hold time: 90 sec (local:90 sec, peer:90 sec) > > ASR-4.3.4 -> ME-15.3(1)S (active/passive), xmit/recv > LDP Id: ME-15.3(1)S:0 > Hold time: 90 sec (local:90 sec, peer:90 sec) > > ASR-4.3.4 -> different ME with 15.3(1)S (active/passive), xmit/recv > LDP Id: different ME with 15.3(1)S:0 > Hold time: 90 sec (local:90 sec, peer:90 sec) > > ASR-4.3.4 -> C6500 (active/passive), xmit/recv > LDP Id: C6500:0 > Hold time: 90 sec (local:90 sec, peer:90 sec) > > ASR-4.3.4 -> ASR-4.3.0 (active/passive), xmit/recv > LDP Id: ASR-4.3.0:0 > Hold time: 90 sec (local:90 sec, peer:90 sec) > > RP/0/RSP0/CPU0:ASR-4.3.4#sh run > <snip> > ipv4 access-list mpls-ldp-advertisement > 10 permit ipv4 Loopbacks any > 20 permit ipv4 Interconnects any > 30 deny ipv4 any any > </snip> > <snap> > mpls oam > ! > mpls ldp > discovery targeted-hello accept > label > allocate for mpls-ldp-advertisement > ! > interface TenGigE0/0/2/1 > discovery transport-address interface > ! > interface TenGigE0/0/2/2 > discovery transport-address interface > ! > interface TenGigE0/0/2/3 > discovery transport-address interface > ! > ! > </snap> > > mpls-ldp-advertisement is the same on all machines and allows the > relevant loopback and interface IPs. > Adding/removing `discovery transport-address interface` does not have > any effect. > The other sides of the interconnects are happily talking LDP among > each other. All interconnects are configured to accept MPLS > > Other than an upgrade of ASR-4.3.0 and ME-15.3(1)S I am out of ideas, > but I would prefer to do this _after_ I got the above to work if at > all possible... > > > Thanks, > Richard > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
