EXTREME-V2TRAP-MIB
Extreme V2c traps
- Source file
EXTREME-V2TRAP-MIB- Last revised
- Identity
extremeV2Traps- Base OID
1.3.6.1.4.1.1916.4
Imported Objects
Net-SNMP examples using the extreme MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'EXTREME-V2TRAP-MIB' -M '/opt/observium/mibs/extreme:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'EXTREME-V2TRAP-MIB::extremeV2Traps'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'EXTREME-V2TRAP-MIB' -M '/opt/observium/mibs/extreme:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'EXTREME-V2TRAP-MIB::extremeV2Traps'
Objects (50)
Showing 50 of 50 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.0 |
||
.1.3.6.1.4.1.1916.4 |
||
.1.3.6.1.4.1.1916.4.1 |
||
.1.3.6.1.4.1.1916.4.1.0 |
||
|
Enumeration
|
.1.3.6.1.4.1.1916.4.1.0.7.1 |
|
|
Enumeration
|
.1.3.6.1.4.1.1916.4.1.0.7.2 |
|
.1.3.6.1.4.1.1916.4.1.0.7.4 |
||
.1.3.6.1.4.1.1916.4.12 |
||
.1.3.6.1.4.1.1916.4.12.0 |
||
.1.3.6.1.4.1.1916.4.13 |
||
.1.3.6.1.4.1.1916.4.13.0 |
||
.1.3.6.1.4.1.1916.4.2 |
||
.1.3.6.1.4.1.1916.4.2.0 |
||
.1.3.6.1.4.1.1916.4.3 |
||
.1.3.6.1.4.1.1916.4.3.0 |
||
.1.3.6.1.4.1.1916.4.3.1 |
||
.1.3.6.1.4.1.1916.4.3.10 |
||
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.11 |
|
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.12 |
|
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.13 |
|
|
Enumeration
|
.1.3.6.1.4.1.1916.4.3.14 |
|
.1.3.6.1.4.1.1916.4.3.15 |
||
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.16 |
|
.1.3.6.1.4.1.1916.4.3.17 |
||
.1.3.6.1.4.1.1916.4.3.18 |
||
.1.3.6.1.4.1.1916.4.3.19 |
||
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.2 |
|
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.20 |
|
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.21 |
|
|
OctetString
|
.1.3.6.1.4.1.1916.4.3.22 |
|
.1.3.6.1.4.1.1916.4.3.3 |
||
.1.3.6.1.4.1.1916.4.3.4 |
||
.1.3.6.1.4.1.1916.4.3.5 |
||
.1.3.6.1.4.1.1916.4.3.6 |
||
.1.3.6.1.4.1.1916.4.3.7 |
||
.1.3.6.1.4.1.1916.4.3.8 |
||
.1.3.6.1.4.1.1916.4.3.9 |
||
.1.3.6.1.4.1.1916.4.4 |
||
.1.3.6.1.4.1.1916.4.4.0 |
||
.1.3.6.1.4.1.1916.4.4.1 |
||
.1.3.6.1.4.1.1916.4.6 |
||
.1.3.6.1.4.1.1916.4.6.0 |
||
.1.3.6.1.4.1.1916.4.7 |
||
.1.3.6.1.4.1.1916.4.7.0 |
||
.1.3.6.1.4.1.1916.4.8 |
||
.1.3.6.1.4.1.1916.4.8.0 |
||
.1.3.6.1.4.1.1916.4.9 |
||
.1.3.6.1.4.1.1916.4.9.0 |
||
.1.3.6.1.4.1.1916.4.9.1 |
||
.1.3.6.1.4.1.1916.4.9.2 |
Dependencies (25) 16 direct · 9 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
- SNMPv2-SMIrfc
- SNMPv2-CONFrfc
- BGP4-MIBrfc
- RFC1155-SMIrfc
- SNMPv2-TCrfc
- EXTREME-BASE-MIBextreme
- EXTREME-BGP4V2-TC-MIBextreme
- INET-ADDRESS-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- EXTREME-BGP4V2-MIBextreme
- IANAifType-MIBrfc
- RFC-1212rfc
- RFC1213-MIBrfc
- EXTREME-EAPS-MIBextreme
- EXTREME-EDP-MIBextreme
- EXTREME-ESRP-MIBextreme
- EXTREME-LACP-MIBextreme
- EXTREME-NP-MIBextreme
- POWER-ETHERNET-MIBrfc
- EXTREME-POE-MIBextreme
- EXTREME-SYSTEM-MIBextreme
- SNMPv2-MIBrfc
- IF-MIBrfc
- EXTREME-VLAN-MIBextreme
- EXTREME-QOS-MIBextreme
- EXTREME-V2TRAP-MIBextremeselected
Notifications / Traps (46)
| 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.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. Traps will be reported only for significant states. |
|
.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.6 |
An overheat notification indicates that the on-board
temperature sensor has reported a temperature that is outside the normal operating range (either higher than the maximum or lower than the minimum of the range) and the switch is in an overheat (or overcold) condition. |
|
.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 |
|
.1.3.6.1.4.1.1916.4.1.0.1 |
Cpu HealthCheck has failed.
|
|
.1.3.6.1.4.1.1916.4.1.0.2 |
CPU Utilizations Rising trap generated when
extremeCpuUtilRisingThreshold is touched/crossed This trap is supported only in ExtremeWare. |
|
.1.3.6.1.4.1.1916.4.1.0.3 |
CPU Utilization Falling Trap is generated when the
extremeCpuAggregateUtilization falls below 80% of the extremeCpuUtilRisingThreshold This trap is supported only in ExtremeWare. |
|
.1.3.6.1.4.1.1916.4.1.0.4 |
Failed processor on module has been detected.
|
|
.1.3.6.1.4.1.1916.4.1.0.5 |
MSM failover occurred.
|
|
.1.3.6.1.4.1.1916.4.1.0.6 |
The master node performed a hitless MSM failover, but the
master failed to resume normal operation within the reelect timeout. Thus, a new master (this switch) was elected. |
|
.1.3.6.1.4.1.1916.4.1.0.7 |
Committed Information Rate exceeded.
|
|
.1.3.6.1.4.1.1916.4.1.0.8 |
An overheat (return to) normal notification indicates
that the on-board tempature sensor has reported a temperature that has returned to within the normal operating range from having been in an overheat (or overcold) condition. The temperature of the unit has sufficiently cooled to be below the maximum (or warmed to be above the minimum) of the normal operating range. |
|
.1.3.6.1.4.1.1916.4.12.0.1 |
This Notification indicates a change in the PoE PSU for the slot.
|
|
.1.3.6.1.4.1.1916.4.13.0.1 |
This Notification indicates when a LACP member-port has been added to the Aggregator.
|
|
.1.3.6.1.4.1.1916.4.13.0.2 |
This Notification indicates when a LACP member-port has been deleted from the Aggregator.
|
|
.1.3.6.1.4.1.1916.4.2.0.1 |
The extremeBgpPrefixReachedThreshold notification is generated
when the number of prefixes received over this peer session reaches the threshold limit. |
|
.1.3.6.1.4.1.1916.4.2.0.2 |
The extremeBgpPrefixMaxExceeded notification is generated
when the number of prefixes received over this peer session reaches the maximum configured limit. |
|
.1.3.6.1.4.1.1916.4.3.0.1 |
This trap will be generated, for a port on which limit-learning has been
configured, when a new MAC address exceeding the limit is learnt on that port. |
|
.1.3.6.1.4.1.1916.4.3.0.2 |
This trap will be generated when a MAC Address is learnt on a port on which
it is not not authorized. This will happen when the MAC address is statically configured as a 'secure mac' on some other port(s). |
|
.1.3.6.1.4.1.1916.4.3.0.3 |
This trap will be generated on a port for which lock-learning has been
configured, when a new MAC address is learnt on that port. |
|
|
extremeNetloginStationMac extremeNetloginStationAddr extremeNetloginPortIfIndex extremeNetloginAuthType extremeNetloginSystemTime extremeNetloginUser extremeNetloginSrcVlan extremeNetloginDestVlan extremeNetloginSessionStatus extremeNetloginAuthDataBase extremeNetloginMoveFromVlanList extremeNetloginMoveToVlanList
|
.1.3.6.1.4.1.1916.4.3.0.4 |
This trap will be generated when a netlogin supplicant passes
authentication and logs in successfully into the network. |
.1.3.6.1.4.1.1916.4.3.0.5 |
This trap will be generated when a netlogin supplicant logs out.
This trap is meant to notify logout event only for already authenticated and logged in supplicant. |
|
.1.3.6.1.4.1.1916.4.3.0.6 |
This trap will be generated upon authentication failure for a
netlogin supplicant |
|
.1.3.6.1.4.1.1916.4.3.0.7 |
This trap will be generated on a valn for which gratuitous ARP protection has been
configured, when a gratuitous ARP does not match the internal static or secured IP<->MAC binding. |
|
.1.3.6.1.4.1.1916.4.4.0.1 |
This trap is sent by Extreme's Network Management Applications when a change
in its inventory database occurs. This trap is not send by a router or switch. |
|
.1.3.6.1.4.1.1916.4.4.0.2 |
This trap is sent by Extreme's Network Management Applications when a change
in its Topology database occurs. This trap is not send by a router or switch. |
|
.1.3.6.1.4.1.1916.4.6.0.1 |
The extremeElrpVlanLoopDetected notification is generated
when the ELRP client detects a loop in the vlan. |
|
.1.3.6.1.4.1.1916.4.7.0.1 |
The extremeEapsStateChange notification is generated
when the EAPS domain has a state change. |
|
.1.3.6.1.4.1.1916.4.7.0.2 |
The extremeEapsFailTimerExpFlagSet notification is
generated when the EAPS domain's fail timer expires for the first time, while its state is not in Fail state. |
|
.1.3.6.1.4.1.1916.4.7.0.3 |
The extremeEapsFailTimerExpFlagClear notification is
generated when the EAPS domain's Fail timer expired flag is cleared. |
|
.1.3.6.1.4.1.1916.4.7.0.4 |
If a Transit is in Link-Down state, and it receives a
Health-Check-Pdu from the Master indicating the ring is Complete, it means there is some problem with the Transit switch that has issued this trap message. |
|
.1.3.6.1.4.1.1916.4.7.0.5 |
The extremeEapsPortStatusChange notification is
generated when an EAPS primary or secondary port changes state. |
|
.1.3.6.1.4.1.1916.4.7.0.6 |
The extremeEapsConfigChange notification is generated
when the EAPS configuration has changed. It is sent 30 seconds after the first change is made to limit the number of traps sent |
|
.1.3.6.1.4.1.1916.4.7.0.7 |
The extremeEapsLastStatusChangeTime notification is generated
10 seconds after a status change occurs. Within the 10 second period all status changes cause extremeEapsLastStatusChange variable to be updated. 10 seconds after the first change, this trap is sent. This is to ensure a management station is notified that a change occured, in case the regular traps are dropped due to be being sent while the network is converging. |
|
.1.3.6.1.4.1.1916.4.8.0.1 |
The extremeBgpPrefixReachedThreshold notification is generated
when the number of prefixes received over this peer session reaches the threshold limit. |
|
.1.3.6.1.4.1.1916.4.8.0.2 |
The extremeBgpPrefixMaxExceeded notification is generated
when the number of prefixes received over this peer session reaches the maximum configured limit. |
|
.1.3.6.1.4.1.1916.4.9.0.1 |
The extremeEapsFailTimerExpFlagSet notification is
generated when the EAPS domain's segment timer expires for the first time. |
|
.1.3.6.1.4.1.1916.4.9.0.2 |
The extremeEapsSegmentTimerExpFlagClear notification is
generated when the EAPS domain's Segment Fail timer expired flag is cleared. |
|
.1.3.6.1.4.1.1916.4.9.0.3 |
The extremeEapsSharedPortStateChange notification is generated
when the EAPS shared port state changes. |
|
.1.3.6.1.4.1.1916.4.9.0.4 |
The extremeEapsSharedPortRootBlockerChange notification is generated
when each switch detects a new rootblocker ID on the networks. |