Is there any way without messing with the level of logging we have turned on today to suppress these messages in particular:
Mar 16 09:43:24: %TCP-6-BADAUTH: No MD5 digest from 206.223.143.84(179) to 206.223.143.81(13412) (RST) tableid - 0 Mar 16 09:43:32: %TCP-6-BADAUTH: No MD5 digest from 206.223.143.84(179) to 206.223.143.81(13412) (RST) tableid - 0 This is a BGP peer that is not coming online at the moment - we don't want to shutdown our actual session. Of course this only happens with MD5 enabled peers ;) Thanks, 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/
