Forum Discussion
John_Harrison
Jan 16, 2012Altostratus
I have not yet rebooted but I have found the issue with my syslog-ng config not being set through the b command, a previous sysadmin had renamed the syslog-ng.conf link in the etc/syslog-ng/ directory. Setting that back the way it's supposed to be has put me to the same functionality as before without the risk of a reboot reset.
Since the previous sysadmin was making changes I'm wondering if the alert.conf file is correct.
The end of mine shows:
alert BIGIP_LOG_EMERG "^[0-9]{8}:0: (.*)" {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.29"
}
alert BIGIP_LOG_ALERT "^[0-9]{8}:1: (.*)" {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.30"
}
alert BIGIP_LOG_CRIT "^[0-9]{8}:2: (.*)" {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.31"
}
/* we not alert those two until we make sure the log level for
each message is accurate.
alert BIGIP_LOG_ERR "^[0-9]{8}:3: (.*)" {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.32"
}
alert BIGIP_LOG_WARNING "^[0-9]{8}:4: (.*)" {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.33"
}
How does this determine what traps are logged?
Could someone post a clean alert.conf for me to compare with?
Thanks in advance.