While they don't cover the exact event that you are referring to, there are examples of event scripts that change the configuration in response to a system event in the Day One: Applying Junos Event Automation guide:
http://www.juniper.net/us/en/local/pdf/day-one-guides/7100110-en.pdf For example, take a look at the set-admin-down.slax script discussed in pages 58-60. (FYI, some of the quotes in the example scripts of the linked PDF got mangled into a different character so be careful when cutting and pasting as you might have to modify the scripts before they can be executed. We're in the process of getting the PDF fixed). > -----Original Message----- > From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- > boun...@puck.nether.net] On Behalf Of Ricardo Tavares > Sent: Wednesday, February 24, 2010 4:35 PM > To: Juniper-Nsp > Subject: [j-nsp] event script: "set protocols overload' if more than > "x" SIB is/are failed > > Hi Fellows, > > Have anyone created an event-script that change the router conf based > on a SIB failure event? > > The idea is isolate a router that is still operational considering the > routing plane but not so ok considering the forwarding plane (one or > more SIB failed). > > I think that is possible to write some kind of event-script to do that. > Someone have implemented something like that and, if possible, share > the solution? > > Best Regards, > Ricardo Tavares > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
