On Wed, 15 Sep 2010 14:50:58 -0500, Richard A Steenbergen <r...@e-gerbil.net> wrote:
>Is there a way to syslog a cspf or rsvp bandwidth reservation failure? The entry at 18:50:14.895 should be logged by rpd, if syslog config has daemon configured for warning or less severe. The message would be similar to the following: RPD_MPLS_PATH_BW_NOT_AVAILABLE: Unable to satisfy bandwidth configured for MPLS path <pathname> on LSP <lspname> >Maybe I'm just being really blind here, but I can't find a way to do it. >You can see these events in the cspf logs if you look at individual LSPs >with "show mplslsp NAME detail": > > 1119 Sep 15 19:32:11.635 CSPF failed: no route toward x.x.x.x[87 times] > 1118 Sep 15 18:50:14.902 Clear Call: CSPF computation failed > 1117 Sep 15 18:50:14.895 Deselected as active > 1116 Sep 15 18:50:14.895 x.x.x.x: Requested bandwidth unavailable > >But this seems like it should be syslog worthy, especially considering >it's already sysloging worthless stuff like bandwidth changes by default >too. Am I missing a sensible way to do this, or is this just in need of >a feature request? Cisco definitely does it: > >Sep 15 19:40:36.458 UTC: %MPLS_TE-5-LSP: LSP x.x.x.x 20554_1024: Path >Error from x.x.x.x: Admission control Failure (code 1, value 2, flag _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp