HP StorageWorks 1606 Brocade Fabric OS MIB Reference v6.3.0 (53-1001339-01, Ju - Page 23

Understanding SNMP basics 1 • connUnitSensorStatusChange • 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 or 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. 7. swPmgrEventTrap This trap is generated when an IPv6 address status change event occurs. 8. swIpv6ChangeTrap Fabric OS MIB Reference 5 53-1001339-01