Skip to main content
NetApp Knowledge Base

After configuring SNMP, destination port not responding to SNMP traps

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

  • Brocade FabricOS v9.2.0a, v9.2.0c3, v9.2.1b
  • Zabbix monitoring (as SNMP trap receiver)
  • SNMP

Issue

  • After configuring SNMP, destination port was not responding to SNMP traps.
  • SNMP trap recipient was configured on port 161, but traps were not being received by the monitoring server.
  • The switch’s network-level firewall (ipfilter policy) was blocking outbound SNMP traps on UDP port 162.
Example SNMP output:
2026/07/20-13:45:14 (IST), [SNMP-1005], 525, FID 128, INFO, P***************, SNMP configuration attribute, Trap Severity Level 1 , has changed from 0 to 4.
2026/07/20-13:45:14 (IST), [SNMP-1005], 526, FID 128, INFO, P***************, SNMP configuration attribute, Trap recipient port 1 , has changed from 162 to 161.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.