Paul, You might be running into CSCsl72955. If so, you could try the workaround suggested by the following link or upgrade the code.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method =fetchBugDetails&bugId=CSCsl72955 Regards -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Paul Cosgrove Sent: Wednesday, March 25, 2009 11:55 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] BGP session resets if NLRI exchanged We are attempting to establish a new BGP session between one of our CRS-1 routers, and a Redback SE800 router owned by another provider. Am not familiar with Redbacks myself and we have not peered with any before (as far as we know anyway). The BGP session only remains up if no NLRI is exchanged. If the other provider sends any prefixes to us we reply with a "invalid length for attribute" notification; if we send any prefixes to them they reply with "invalid or corrupt AS path". The other provider uses VPNv4 within their network, though I understand that it is not configured on this peering. I'm wondering whether these errors could result if their router expects a RD (and sends one) on the advertisements, perhaps due to a software bug or typo in the config. Perhaps someone has seen this problem before? Paul. _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/