EXTREME-TRAP-MIB
- Source file
EXTREME-TRAP-MIB- Last revised
- Not declared
Imported Objects
Objects (2)
Showing 2 of 2 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.1916 |
||
.1.3.6.1.4.1.1916.0 |
Dependencies (15) 8 direct · 7 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- RFC1155-SMIrfc
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- EXTREME-BASE-MIBextreme
- IANAifType-MIBrfc
- RFC-1212rfc
- RFC1213-MIBrfc
- EXTREME-EDP-MIBextreme
- EXTREME-ESRP-MIBextreme
- INET-ADDRESS-MIBrfc
- EXTREME-SYSTEM-MIBextreme
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- EXTREME-VLAN-MIBextreme
- EXTREME-TRAP-MIBextremeselected
Notifications / Traps (16)
| Name | OID | Description |
|---|---|---|
.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. |
|
.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. |
|
.1.3.6.1.4.1.1916.0.12 |
Attached Redundant Power Supply device is indicating
an alarm condition. |
|
.1.3.6.1.4.1.1916.0.13 |
Attached Redundant Power Supply device is no longer
indicating an alarm condition. |
|
.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. |
|
.1.3.6.1.4.1.1916.0.15 |
Signifies that the value of the extremeSlotModuleState for
the specified extremeSlotNumber has changed. |
|
|
RFC1213-MIBsysUpTime RFC1213-MIBsysDescr EXTREME-VLAN-MIBextremeVlanIfIndex EXTREME-VLAN-MIBextremeVlanIfDescr EXTREME-ESRP-MIBextremeEsrpGroup EXTREME-ESRP-MIBextremeEsrpState EXTREME-ESRP-MIBextremeEsrpNetAddress RFC1213-MIBifPhysAddress EXTREME-ESRP-MIBextremeEsrpActivePorts EXTREME-ESRP-MIBextremeEsrpInternalActivePorts EXTREME-ESRP-MIBextremeEsrpTrackedActivePorts EXTREME-ESRP-MIBextremeEsrpTrackedIpRoutes
|
.1.3.6.1.4.1.1916.0.17 |
Signifies Esrp state change
|
.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. |
|
.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. |
|
.1.3.6.1.4.1.1916.0.20 |
This node discovers a new neighbor through Extreme Discovery
Protocol. |
|
.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. |
|
.1.3.6.1.4.1.1916.0.22 |
Cpu HealthCheck has failed.
This trap is supported only in ExtremeWare. |
|
.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. |
|
.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. |
|
.1.3.6.1.4.1.1916.0.8 |
A fan has transitioned out of a failure state and
is now operating correctly. |
|
.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 |