Email notification of node/vs down

After beeing pointed towards numerous links in the kb I think we finally got a breakthrough. Excerpt - mail from f5 support:

 

 

----------------------

 

 

Here is my test pool with 2 monitors applied to pool member 10.0.0.12:80:

 

 

pool mspiggy {

 

lb method member ratio

 

min active members 1

 

monitor all http

 

members

 

10.0.0.10:http

 

priority 2

 

10.0.0.11:http

 

priority 2

 

10.0.0.12:http

 

priority 2

 

monitor http and http_test

 

10.0.0.13:http

 

priority 2

 

10.0.0.14:http

 

}

 

 

 

Enable database key: bigd.lognodestatuschange

 

 

[root@pegleg:Active] ucs b db bigd.lognodestatuschange enable

 

[root@pegleg:Active] ucs b db bigd.lognodestatuschange

 

Bigd.LogNodeStatusChange = enable

 

 

 

[root@pegleg:Active] ucs tail -f /var/log/ltm

 

 

1:- if only apply 1 monitor http to pool member, 10.0.0.12:80

 

 

Oct 6 14:22:54 pegleg mcpd[1486]: 01070639:5: Pool member 10.0.0.12:80 session status enabled.

 

Oct 6 14:22:54 pegleg bigd[1599]: 01060001:5: Service detected UP for ::ffff:10.0.0.12:80 monitor http.

 

Oct 6 14:22:55 pegleg mcpd[1486]: 01070727:5: Pool member 10.0.0.12:80 monitor status up.

 

 

...

 

2:- If applied 2 monitors (see above pool mspiggy configurations), http_test monitor failed, you can see:

 

 

Oct 6 14:23:14 pegleg bigd[1599]: 01060001:5: Service detected UP for ::ffff:10.0.0.12:80 monitor http.

 

Oct 6 14:23:25 pegleg bigd[1599]: 01060001:5: Service detected DOWN for ::ffff:10.0.0.12:80 monitor http_test.

 

Oct 6 14:23:25 pegleg mcpd[1486]: 01070638:5: Pool member 10.0.0.12:80 monitor status down.

 

Oct 6 14:23:28 pegleg mcpd[1486]: 01070639:5: Pool member 10.0.0.12:80 session status enabled.

 

 

You can configure alertd to use which monitor strings written down in /var/log/ltm, and you can define to send snmp trap for the strings you defined to monitor, see SOL3727

 

 

-----------------------------

 

 

ingard