Brocade Fabric Watch Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 21)

SNMP agent is configured to a specific error message level, error messages at that level trigger SNMP
traps.
An SNMP trap forwards the following information to an SNMP management station:
• Name of the element whose counter registered an event
• Class, area, and index number of the threshold that the counter crossed
• Event type
• Value of the counter that exceeded the threshold
• State of the element that triggered the alarm
• Source of the trap
You must configure the software to receive trap information from the network device. You must also
configure the SNMP agent on the switch to send the trap to the management station. You can configure
SNMP notifications using the snmpConfig command and you can configure notifications using Fabric
Watch.
For information on configuring the SNMP agent using the snmpConfig command, refer to the Fabric
OS Command Reference.
SNMP trap counters
• When a counter is in the "in-between" state, Fabric Watch sends an informational SNMP trap. Refer
to In-between buffer values on page 25 for an explanation of the concepts of "in-between"
boundaries and above high, below high, above low, and below low thresholds.
• When a counter is above the high threshold or below the low threshold, Fabric Watch sends a
warning SNMP trap except for the power supply area of the environment (ENV), CPU, and Memory
classes. The severity of a Fabric Watch SNMP trap for CPU and memory will always be
informational.
Refer to Threshold values on page 25 for a more thorough explanation of thresholds.
RASLog for switch events
Following an event, Fabric Watch adds an entry to the internal event log for an individual switch. The
RASLog stores event information but does not actively send alerts. Use the errShow command to view
the RASLog.
Locked port log
Following an event, the port log locks to retain detailed information about an event, preventing the
information from being overwritten as the log becomes full. This notification audit stores event
information but does not actively send alerts, which is done automatically when some thresholds are
exceeded and an alert is triggered.
For more information about locking, unlocking, and clearing the port log, refer to the Fabric OS
Command Reference.
Fabric Watch audit messages
Fabric Watch events caused by configuration value changes are tagged as Audit messages. When
managing SANs you may want to filter or audit certain classes of events to ensure that you can view
and generate an audit log for what is happening on a switch, particularly for security-related event
SNMP trap counters
Fabric Watch Administrators Guide 21
53-1003142-01