Brocade Fabric OS MIB Reference Guide v6.1.0 (53-1000602-02, June 2008)

Fabric OS MIB Reference 5

53-1000602-02

Understanding SNMP Basics

• connUnitPortStatusChange

• connUnitEventTrap

The MIB-II system description swEventTrapLevel determines the output for the connUnitEventTrap.

Events in the Error Log of a severity at or above the configured threshold will generate SNMP traps.

The Fibre Alliance Trap (FA-TRAP) can be configured to send traps using the snmpConfig command.

Refer to the Fabric OS Command Reference for more information on this command.

HA Traps

Consider enabling these traps to monitor field-replaceable unit (FRU) status and control processor

(CP) status when you have a Brocade director in your environment:

• fruStatusChanged

This trap is generated by a FRU status change, such as a switch reboot or disabling or enabling

a FRU component such as (fandisable/fanenable, etc).

• cpStatusChanged

This trap is generated by a change in the status of a CP, including a reboot or firmware

download.

• fruHistoryTrap

This trap is generated when a FRU is added or removed. fruHistoryTrap is not generated when

standby CP is removed.

The high availability trap (HA-TRAP) can be configured to send traps using the snmpConfig

command. Refer to the Fabric OS Command Reference for more information on this command.

SW Traps

There are six specific traps defined in Brocade SW-TRAP:

1. swfault (no longer supported)

2. swSensorScn (no longer supported)

3. swFCPortScn

This trap is generated by a port state change.

4. swEventTrap

This trap is generated by any switch event reported to the system error log.

5. swFabricWatchTrap

This trap is generated when any Fabric Watch threshold is reached.

6. swTrackChangesTrap

This trap is generated by a login or a logout.

The Brocade trap (SW-TRAP) can be configured to send traps using the snmpConfig command.

Refer to the Fabric OS Command Reference for more information on this command.