EXTREME-TRAP-MIB

File: EXTREME-TRAP-MIB.mib (9168 bytes)

Imported modules

RFC1155-SMI EXTREME-SYSTEM-MIB EXTREME-ESRP-MIB
EXTREME-VLAN-MIB EXTREME-EDP-MIB RFC1213-MIB
IF-MIB SNMPv2-SMI

Imported symbols

enterprises extremeSlotNumber extremeSlotModuleConfiguredType
extremeSlotModuleInsertedType extremeSlotModuleState extremePowerSupplyNumber
extremeFanNumber extremeCurrentTemperature extremeEsrpGroup
extremeEsrpState extremeEsrpNetAddress extremeEsrpActivePorts
extremeEsrpInternalActivePorts extremeEsrpTrackedActivePorts extremeEsrpTrackedIpRoutes
extremeVlanIfIndex extremeVlanIfDescr extremeEdpPortIfIndex
extremeEdpNeighborId extremeEdpEntryAge extremeEdpNeighborVlanName
extremeEdpNeighborVlanIpAddress sysUpTime sysDescr
ifPhysAddress ifDescr ifAlias
NOTIFICATION-TYPE

Defined Values

extremenetworks 1.3.6.1.4.1.1916
OBJECT IDENTIFIER    

extremeV1Traps 1.3.6.1.4.1.1916.0
OBJECT IDENTIFIER    

extremeOverheat 1.3.6.1.4.1.1916.0.6
A overheat trap indicates that the on board tempature sensor has reported a overheat condition. System will shutdown until unit has suficiently cooled such that operation may begin again. A cold start trap will be issued when the unit has come back on line.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeFanfailed 1.3.6.1.4.1.1916.0.7
A fan failed trap indicates one or more of the cooling fans inside the device has failed. A fanOK trap will be sent once the fan has attained normal operation.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeFanOK 1.3.6.1.4.1.1916.0.8
A fan has transitioned out of a failure state and is now operating correctly.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeInvalidLoginAttempt 1.3.6.1.4.1.1916.0.9
A user attempted to login to console or by telnet but was refused access due to incorrect username or password
Status: current Access: read-write
NOTIFICATION-TYPE    

extremePowerSupplyFail 1.3.6.1.4.1.1916.0.10
One or more sources of power to this agent has failed. Presumably a redundant power-supply has taken over.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremePowerSupplyGood 1.3.6.1.4.1.1916.0.11
One or more previously bad sources of power to this agent has come back to life without causing an agent restart.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeRpsAlarm 1.3.6.1.4.1.1916.0.12
Attached Redundant Power Supply device is indicating an alarm condition.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeRpsNoAlarm 1.3.6.1.4.1.1916.0.13
Attached Redundant Power Supply device is no longer indicating an alarm condition.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeSmartTrap 1.3.6.1.4.1.1916.0.14
Signifies that the value of one of the object identifiers (or the value of an object below that in the MIB tree) defined in the extremeSmartTrapRulesTable has changed, and hence a new entry has been created in the extremeSmartTrapInstanceTable. Such a trap is sent at most once every thirty seconds if one or more entry was created in the last thirty seconds.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeModuleStateChanged 1.3.6.1.4.1.1916.0.15
Signifies that the value of the extremeSlotModuleState for the specified extremeSlotNumber has changed.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeEsrpStateChange 1.3.6.1.4.1.1916.0.17
Signifies Esrp state change
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeSlbUnitAdded 1.3.6.1.4.1.1916.0.18
The server load balancer has activated a group of virtual servers that it normally would not activate. This may be due to the failure of another server load balancer.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeSlbUnitRemoved 1.3.6.1.4.1.1916.0.19
The server load balancer has deactivated a group of virtual servers that it normally has active. This indicates that something is wrong in the server load balancer; for example, its ping check may be failing.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeEdpNeighborAdded 1.3.6.1.4.1.1916.0.20
This node discovers a new neighbor through Extreme Discovery Protocol.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeEdpNeighborRemoved 1.3.6.1.4.1.1916.0.21
No EDP updates are received from this neighbor within the configured timeout period and this neighbor entry is aged out by the device.
Status: current Access: read-write
NOTIFICATION-TYPE    

extremeCpuHealthCheckFailed 1.3.6.1.4.1.1916.0.22
Cpu HealthCheck has failed.
Status: current Access: read-write
NOTIFICATION-TYPE