SNMP VS and Pool monitoring

Hi Matt,

 

 

Have you taken a look at F5's knowledge base?

 

 

Here are some solutions they have documented:

 

Click here

 

Click here

 

Click here

 

Click here

 

 

Hope this helps.

 

cb

cb,

 

 

Thanks for helping me out but I am still having a little trouble. I have created the user_alert.conf added the logger -p for syslog-ng but the alertd doesn't start back up. Anything I can do to troubleshoot this?

 

 

Thanks

 

 

Matt

If you try to start alertd using bigstart start alertd, you should see a syntax error with a line number noted in the standard output. Else, I think you can check /var/log/messages for the error. Chances are, you're missing a semi-colon at the end of one of the configuration items. If you get stuck, try posting the block that the error is in.

 

 

Aaron

Hi Aaron,

 

 

Thanks for the input. Here are the steps I used to try and setup a custom snmp trap.

 

 

I add this to the user_alert.conf file

 

 

alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_DOWN "Node (.*?) monitor status down." { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.12"

 

 

Then I run

 

 

logger -p local0.warning "Pool member 10.10.64.14:80 monitor status down."

 

 

Once I run that command I keep getting:

 

 

logger: Re-starting alretd

 

 

The restart message just keeps repeating itself over and over again

 

 

Sorry, the log file errors would be logged to is /var/log/ltm. Do you see any related errors in /var/log/ltm?

I added an invalid line to the alert.conf and see the following entry in /var/log/ltm:

Apr 14 17:48:49 bigip6400 alertd: 01100021:3: Couldn't process the /var/run/alert.conf: problems at line 408.

Do you have a close curly brace on the alert definition?

alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_DOWN "Node (.*?) monitor status down." {
        snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.12"}

Aaron

Aaron,

 

 

Thanks so much. That did it - I didn't even notice the missing trailing bracket.

 

 

Matt

I have a script that pools this every minute for a given f5 and stores it in a new log file daily, would this be useful?...If so, I'll post.