All MIBs › AVICI-BAY-MIB › aviciBayFanNotification
aviciBayFanNotification
Module: AVICI-BAY-MIB
OID (symbolic): AVICI-BAY-MIB::aviciBayFanNotification
OID (numeric): 1.3.6.1.4.1.2474.1.4.2.0.2
Node type: NOTIFICATION-TYPE
Description: A Fan notification is sent when the specified fan detects a fault or clears a fault. The current ambient air temperature entering the fan is reported in the aviciBayFanCurrTemp object. All existing fan faults are reported in the aviciBayFanCurrFailures object as a bitmap. If no failures exist, this object contains a 0. A human readable description of the event triggering this notification is included in the aviciSysTrapDescr object.
Communication Failure: This failure indicates that the cooling module has been removed or the cooling module firmware is no longer communicating with the bay controller. If a communication failure occurs, the fans will run in autonomous mode until communication with the bay controller is reestablished. Once communication is established, the failure is cleared.
General Failure: This failure indicates that the cooling module firmware is able to communicate with the bay controller and is reporting a broken fan. This could mean that the fan is burned out, jammed, or the firmware is unable to sense fan speed due to tachometer failure. When the problem is corrected, the failure is cleared.
Filter Blocked: This failure indicates that the fan detected that the filter is blocked. When the obstruction is removed from the filter or the clogged air filter is replaced, this failure will clear.
Bad or absent internal thermistor: This failure indicates that the fan internal thermistor is missing or is not functioning. If the thermister is not functioning, the fan cannot sense the incoming ambient air temperature. The ambient temperature is used to control fan speed in autonomous mode and when there are no modules reporting their current temperature.
Bad or absent external thermistor: This failure indicates that the fan external thermistor is expected to be installed and is not functioning.
Minor temperature threshold: This failure indicates that the incoming ambient air temperature is above the minor threshold temperature, but below the major threshold temperature. Either the cooling system in the building has failed, or it has insufficient cooling capacity for the equipment in the room. A rapid rise in temperature usually indicates cooling system failure whereas a slow rise usually indicates insufficient cooling capacity. When the temperature drops below the minor threshold, this failure will clear.
Major temperature threshold: This failure indicates that the incoming ambient air temperature is above the major threshold temperature, but below the critical threshold temperature. Either the cooling system in the building has failed, or it has insufficient cooling capacity for the equipment in the room. A rapid rise in temperature usually indicates cooling system failure whereas a slow rise usually indicates insufficient cooling capacity. When the temperature drops below the major threshold, this failure will clear.
Critical temperature threshold: This failure indicates that the incoming ambient air temperature is above the critical threshold temperature. Either the cooling system in the building has failed, or it has insufficient cooling capacity for the equipment in the room. A rapid rise in temperature usually indicates cooling system failure whereas a slow rise usually indicates insufficient cooling capacity. When the temperature drops below the critical threshold, this failure will clear.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' AVICI-BAY-MIB::aviciBayFanNotification snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.2474.1.4.2.0.2
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:52130->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (464354722) 53 days, 17:52:27.22 SNMPv2-MIB::snmpTrapOID.0 = OID: AVICI-BAY-MIB::aviciBayFanNotification
Start monitoring Avici Systems core/backbone routers (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVICI-BAY-MIB::aviciBayFanNotification OID value, configure state conditions and alerts, and monitor any Avici Systems core/backbone routers (legacy) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2474 | avici | AVICI-SMI |
| 1.3.6.1.4.1.2474.1 | aviciMibs | AVICI-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2474.1.4 | aviciBayMIB | AVICI-BAY-MIB |
| 1.3.6.1.4.1.2474.1.4.2 | aviciBayNotifications | AVICI-BAY-MIB |
| 1.3.6.1.4.1.2474.1.4.2.0 | aviciBayNotificationPrefix | AVICI-BAY-MIB |
| 1.3.6.1.4.1.2474.1.4.2.0.2 | aviciBayFanNotification | AVICI-BAY-MIB |