I'll look at it but give me a bit. I'm finalizing the writeup for the real issue.
On Wed, Feb 18, 2009 at 04:17:10PM -0500, German Martinez wrote: > On Sun Mar 30, 2008, Hank Nussbacher wrote: > > It seems this bug is still open.. perhaps is not that important :) > > http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCso47162 > > German > > > > This will be fixed via: > > > > CSCso47162 > > Externally found enhancement (Sev6) bug: New (N) > > BGP-6-ASPATH message should print offending prefix(es) > > > > -Hank > > > > >Is there a reason why when Cisco provides a %BGP-6-ASPATH error message > > >like: > > > > > >%BGP-6-ASPATH: Invalid AS path [chars] received from [int]: [chars] > > >%BGP-6-ASPATH: Long AS path aa bb cc dd received from x.x.x.x: More than > > >configured MAXAS-LIMIT > > > > > >that they can't include the actual prefix causing the error message to > > >appear? As is, the error message is not that helpful without the prefix. > > > > > >Is this something I have to open a TAC request for? > > > > > >Thanks, > > >Hank > > > > _______________________________________________ > > 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/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
