Announcing the F5 Management Pack 1.7.0: iRules-based object health events

Hi Stephen,

 

 

It wasn't immediately clear to me what the new iRule related functionality was. But these related articles gave some good background info. Maybe others will find them useful as well:

 

 

 

iRules and the F5 Management Pack

 

http://devcentral.f5.com/weblogs/jbalog/archive/2010/03/05/irules-and-the-f5-management-pack.aspx

 

 

Starting with v1.7.0.390 the F5 Management Pack (F5 MP) has some built-in diagnostic capabilities based on iRules. Messages logged within iRules could be sent directly to the F5 Monitoring Service that now has an asynchronous TCP listener specifically designed to receive and process iRule messages, and based on these messages the F5 MP can write events into the Microsoft's System Center Operations Manager (SCOM) event data source, against the F5 device monitoring objects discovered. Putting it simply, you can mark an F5 monitoring object state in SCOM, as up and down or in warning state, directly from iRules.

 

 

 

 

 

Maintenance Mode Rules for the F5 Networks Management Pack

 

http://devcentral.f5.com/weblogs/druddell/archive/2010/03/05/maintenance-mode-rules-for-the-f5-networks-management-pack.aspx

 

 

A few releases ago we included a couple of new rules and new tasks to go with them. These rules and tasks will help you keep your Pool Members (LTM and GTM) in sync with your applications. These new rules are disabled by default, but we highly recommend enabling and integrating them into your deployment and existing distributed applications.

 

...

 

By enabling these rules, any time an LTM Pool Member or GTM Pool Member (Virtual Server) is put into maintenance mode, it will also disable the Pool Member within the interval specified in the overrides of the rule.

 

 

 

 

Thanks, Aaron