Could be a good idea. Just ask TAC to file a bug for this. Arie On Sat, Mar 22, 2008 at 7:28 PM, Hank Nussbacher <[EMAIL PROTECTED]> wrote:
> 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/
