For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

smp_86112's avatar
smp_86112
Icon for Cirrostratus rankCirrostratus
Jul 29, 2008

Custom SNMP Traps - clarify "match string" usage

Reference the article posted by deb a few days ago:   http://devcentral.f5.com/Default.aspx?tabid=63&articleType=ArticleView&articleId=256     After reading this article, I...
management
monitoring
Deb_Allen_18's avatar
Deb_Allen_18
Historic F5 Account
Jul 29, 2008
The alert code is used to find a match string that is maintained in the bigip_error_maps.dat file. This is the method used by F5 development to maintain most of the alert match strings to build the running configuration @ runtime using the background process described in the article.

 

 

Alternatively, the match string may be specified in the alert.conf or user_alert.conf file. When creating custom traps, you will not create an error map, rather you will always define the match string in the user_alert.conf file.

 

 

The system receives both alert code and message, and attempts to match against the running alertd configuration, which includes both definitions, and will trigger the alert action for all definitions that match. (I clarified the beginning of the article, thanks for the feedback.)

 

 

Syslog-ng passes along the message string it received unmodified, and there is no way to customize the message.

 

 

Does that help?

 

 

/d