You might have exhausted your label range. It might be make sense to check if there is a label assigned to that prefix in the LFIB.
--- On Wed, 11/6/08, Pshem Kowalczyk <[EMAIL PROTECTED]> wrote: From: Pshem Kowalczyk <[EMAIL PROTECTED]> Subject: [c-nsp] Route not getting imported into vrf To: "cisco-nsp" <[email protected]> Date: Wednesday, 11 June, 2008, 4:51 PM Hi, We have two PE (6500) connecting to multiply AS. Some of the routes are best on PE1, some on PE2. Today I've noticed that for some reason, some routes that are best on PE1 don't get installed in the vrf on PE2: BGP routing table entry for ab57:110118:aaa.bbb.224.0/19, version 133515951 Paths: (8 available, best #1, no table) Not advertised to any peer ddd3 ddd3 ddd3 ddd1 , (aggregated by ddd1 aaa.bbb.239.160) 172.16.31.240 (metric 60) from 172.16.31.240 (172.16.31.240) Origin IGP, metric 62, localpref 110, valid, internal, atomic-aggregate, best Community: ab57:5000 ab57:5700 Extended Community: RT:ab57:115 {snip the rest of the routes} the 172.16.31.240 is the loopback of the other PE (PE1). The weird thing is that despite the fact PE2 receives the route locally from one of it's eBGP peers (with lower localpref) it doesn't get installed either. There is no filtering on the import into the vrf. Any ideas what might be causing this? kind regards Pshem _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
