Forum Discussion
Shane_Terrick_9
May 13, 2013Nimbostratus
I added the following to the /config/user_alert.conf file
alert CHP_XR_NODE_DOWN "Node 10.25.65.86 monitor status down" {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.504";
email toaddress="terricksa@xxxx.com"
fromaddress="root@bigip.com"
body="There is a Node DOWN in CHP XR TST!"
}
I then rebooted the node to cause the node to go down as seen in the ltm log, but did not get the error when it did go down in the log.
May 13 13:14:19 LTM1 notice mcpd[3485]: 01070640:5: Node 10.25.65.86 monitor status down.
I was able to successfully test the TRAP with the logger command(recieved the email quickly)
logger -p local0.warning "Node 10.25.65.86 monitor status down"
Am I missing cycling something or since I rebooted, did it happen too quickly?