Forum Discussion
How to stop SNMP trap notifications to NOC operators console ??
Hi, - we have 8900 LTMs running 11.4.1 code. The issue we are having is that we need to suppress ( stop LTM from generating) large number of traps from going to Operations console. None of the instructions seen on F5 websites seem very clear as to how to do this. The link "http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-implementations-11-1-0/21.html" is not very clear at all. In some place it says to modify "/etc/alertd/alert.conf" ...but then this link says " NOT TO". Below are the list of TRAPS we need to stop coming from the LTMs....Would it be possible to provide us with an example of how to go about achieving this. Time is really of the essence here. Many Thanks in advance John "5": - bigipCpuFanSpeedLow "11": - bigipServiceUp "13": - bigipNodeUp "16": - bigipActiveActive "18": - bigipFeatureOnline "40": - bigipGtmPoolAvail "41": - bigipGtmPoolNotAvail "43": - bigipGtmPoolEnabled "44": - bigipGtmLinkAvail "47": - bigipGtmLinkEnabled "48": - bigipGtmWideIpAvail "51": - bigipGtmWideIpEnabled "52": - bigipGtmPoolMbrAvail "55": - bigipGtmPoolMbrEnabled "56": - bigipGtmServerAvail "59": - bigipGtmServerEnabled "60": - bigipGtmVsAvail "63": - bigipGtmVsEnabled "64": - bigipGtmDcAvail "67": - bigipGtmDcEnabled "68": - bigipHardDiskFailure "69": - bigipGtmAppObjAvail "71": - bigipGtmAppAvail "77": - bigipGtmBoxAvail "79": - bigipAsmFtpRequestBlocked "80": - bigipAsmFtpRequestViolation "85": - bigipAsmSmtpRequestBlocked "86": - bigipAsmSmtpRequestViolation "100": - bigipGtmProberPoolEnabled "104": - bigipGtmProberPoolMbrEnabled "106": - bigipAvrAlertsMetricSmtp "134": - bigipDosAttackStop "135": - bigipLtmVsAvail "137": - bigipLtmVsEnabled "146": - bigipTrafficGroupActivate "147": - bigipPsPowerOn
6 Replies
- Cory_50405
Noctilucent
Within /etc/alertd/alert.conf, you'll see a list of all traps. In order to disable an alert, copy the stanza of the alert to be disabled over to /config/user_alert.conf and comment out the line pertaining to the OID, like this:
alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10" }Save the file and then perform 'bigstart restart alertd' suppress the desired alerts. Adding these trap omissions to /config/user_alert.conf ensures that they'll persist through a reboot/upgrade.
- MSurfer_152388
Nimbostratus
Awesome...thank u very much.. J
- nitass
Employee
just for reference.
sol11234: Disabling default SNMP traps
http://support.f5.com/kb/en-us/solutions/public/11000/200/sol11234.html- MSurfer_152388
Nimbostratus
Awesome...thank u very much....:-0) J
- nitass_89166
Noctilucent
just for reference.
sol11234: Disabling default SNMP traps
http://support.f5.com/kb/en-us/solutions/public/11000/200/sol11234.html- MSurfer_152388
Nimbostratus
Awesome...thank u very much....:-0) J
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com