Forum Discussion

Brandon_12607's avatar
Brandon_12607
Icon for Nimbostratus rankNimbostratus
Oct 27, 2016

SNMP TRAP

BIG IP 3600 11.5 So I have use these SNMP MIBs on quite a few F5s in our organization and it always works. On this 3600 I can't seem to get the MIBs to catch the certs.   alert CERTIFICATE_EXP...
BIG-IP
devops
TMSH
Brandon's avatar
Brandon
Icon for Cirrostratus rankCirrostratus
Oct 28, 2016

Yes and then u have to update the few things

 

In the file /etc/cron.weekly/5checkcert (delete the line in the file and add the one below)

 

cd /var/core

 

/usr/bin/tmsh -c "cd /; run /sys crypto check-cert stdout disabled"

 

Then you have to add all of the Partition Names into the alert.conf file. example Common, Partation2 and 3.

 

vi /config/user_alert.conf Type: I

 

alert CERTIFICATE_EXPIRED "Certificate (.) in file /Common/(.) expired" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.300"; email toaddress="cccc@yahoo.com" body="Certificate Expired on F5hostname1" }

 

alert CERTIFICATE_EXPIRED "Certificate (.) in file /Common/(.) will expire" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.301"; email toaddress="cccc@yahoo.com" body="Certificate will Expire on F5hostname1" }

 

alert CERTIFICATE_EXPIRED "Certificate (.) in file /Partition2/(.) expired" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.302"; email toaddress="cccc@yahoo.com" body="Certificate Expired on F5hostname1" }

 

alert CERTIFICATE_EXPIRED "Certificate (.) in file /Partition2/(.) will expire" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.303"; email toaddress="cccc@yahoo.com" body="Certificate will Expire on F5hostname1" }

 

alert CERTIFICATE_EXPIRED "Certificate (.) in file /Partition3/(.) expired" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.304"; email toaddress="cccc@yahoo.com" body="Certificate Expired on F5hostname1" }

 

alert CERTIFICATE_EXPIRED "Certificate (.) in file /Partition3/(.) will expire" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.305"; email toaddress="cccc@yahoo.com" body="Certificate will Expire on F5hostname1" }