Email notification of node/vs down

Hi ingard,

 

 

Thanks for posting the solution. I didn't know about the db option for bigd.lognodestatuschange.

 

 

Aaron

Did anyone figure out how to substitute host name for IP in a pool member status alert?

The way I got this to work is a custom alert for each Node in front of the global one. Since it's a first match basis and you have to have a different alert name for each. The bold is the new one I inserted before the global wildcard.

 

Copied (with a few edits) from my /etc/alertd/alert.conf

 

* from bigd (CR36393) -- changed from mcpd messages in v9.2.0 (CR46190) and hotfix v9.0.5

 

* For the following 4 alerts, messages need to be used in pattern match to

 

* distiguish different ipaddr, port, etc. So, if these messages are changed,

 

* the changes in alert system need to be done accordingly.

 

*/

 

alert BIGIP_REVERSE_PROXY_DOWN "Pool member 192.168.1.1:8080 monitor status down." {

 

snmptrap OID=".1.2.6.1.4.1.3375.2.4.0.200";

 

email toaddress="joe@example.com,joe2@example.com"

 

fromaddress="BigIP@example.com"

 

body=""

 

}

 

alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_DOWN "Pool member (.*?): (.*?) monitor status down." {

 

snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10"

 

}

That's good to know

 

 

The issue with modifying the alert.conf (as opposed to the user_alert.conf) is that the alert.conf isn't saved in a UCS file by default and even if you manually configure it so the alert.conf is saved in a UCS file, it could get overwritten in an upgrade/hotfix installation. So if you have a checklist for post-upgrade items, I'd suggest adding a check of the alert.conf.

 

 

You can modify the files saved in a UCS following the steps in SOL4422:

 

 

SOL4422: Viewing and modifying the files that are configured for inclusion in a UCS archive

 

https://support.f5.com/kb/en-us/solutions/public/4000/400/sol4422.html (Click here)

 

 

hwidjaja had a good solution which doesn't involve editing the alert.conf (Click here).

 

 

Aaron

Thanks for that info Aaron! It's very appreciated especially since I'm very new to F5s, we have 10, and the newest code on one is 9.3.1 so I see updates in my future.

 

 

Can anyone tell me how you get the OID of the alert? I don't see it in the syslogs

Can you find it in /var/run/bigip_error_maps.dat?

I don't know for sure, but it's possible that any "MON_STATUS" OID will be triggered on *any* status change - so a change from up to down and back up may send off two alerts. Also note that a node status could affect a pool status, so if you're trapping on both it could case duplicates.

 

 

-Matt

Hi All,

 

 

I know it's a long time since this tread ended but I have a question if thats ok...?? Did you ever manage to get the pool name into the email alert ? If so how was this achieved..

 

many thanks

 

Dan

 

 

sorry.. ignore last post..... hadn't come onto the second page when i sent the update...

 

ta

 

dan