You're right, those prefixes are not ours! The hunt is now on to find out where this was happening. The router that I posted the logs from before does not appear to be redistributing anything other than connected and statics into OSPF - I'll have to find out if someone has changed the config since or if it was happening elsewhere in the network......
Thanks for the likely answer and explanation, Oli. Reuben On 3/08/2007 10:32 PM, Oliver Boehmer (oboehmer) wrote: >> The reason I am bringing this up is that I'm considering if the >> problem may not have been directly caused by this 7200, but may be >> caused by some other external factor. The only thing which strikes >> me as a possibility is that someone or something >> flooded/redistributed an entire BGP feed into OSPF. Does that sound >> like a possibility? > > It actually sounds like a likely cause. Both of the prefixes LDP > complained about above (150.82.0.0/16 and 192.232.71.0/24) are Internet > prefixes (from different ASN, so likely not yours), so the only reason > LDP would be concerned about them was if they were advertised by an IGP > at some point of time (as we don't assign labels to BGP prefixes). > > As "Tag Control" is the main dispatching process for all sorts of MPLS > events, I could imagine that the router was pretty busy allocating (and > later de-allocating) labels :-| > > oli _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
