EDGECORE-TRAPS-MIB
- Source file
EDGECORE-TRAPS-MIB- Last revised
- Not declared
Imported Objects
| EDGECORE-BRIDGEMIBOBJECTS-MIB | rldot1dStpTrapVrblifIndex rldot1dStpTrapVrblVID |
| EDGECORE-DEVICEPARAMS-MIB | rndErrorDesc rndErrorSeverity |
| EDGECORE-MIB | rndNotifications |
| SNMPv2-SMI | NOTIFICATION-TYPE (no object page) |
Objects (0)
Dependencies (21) 4 direct · 17 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-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- BRIDGE-MIBrfc
- RFC1155-SMIrfc
- Accton-MIBedgecore
- EDGECORE-MIBedgecore
- P-BRIDGE-MIBrfc
- RMON-MIBrfc
- RFC-1212rfc
- RFC1213-MIBrfc
- RFC1271-MIBrfc
- TOKEN-RING-RMON-MIBrfc
- RMON2-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- Q-BRIDGE-MIBrfc
- EDGECORE-BRIDGEMIBOBJECTS-MIBedgecore
- EDGECORE-DEVICEPARAMS-MIBedgecore
- EDGECORE-TRAPS-MIBedgecoreselected
Notifications / Traps (80)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.259.10.1.14.89.0.10 |
This trap indicates that in order to perform the last SET request, a reset operation
of the router/bridge is required. This occurs when the layer 2 routing algorithm is changed between SPF and Spanning Tree. The reset can be performed manually or using the variable rndAction. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.12 |
This trap indicates that in the device finished a TFTP
transaction with the management station. variable rndErrorDesc and rndErrorSeverity provides the actual message text and severity respectively. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.13 |
This trap indicates that in the device aborted a TFTP session with
the management station. Variable rndErrorDesc and rndErrorSeverity provides the actual message text and severity respectively. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.136 |
A rsPingCompleted trap is sent at the completion
of a sequence of pings if such a trap was requested when the sequence was initiated. The trap severity is info. The trap text will specify the following information: rsPingCompletionStatus, rsPingSentPackets, rsPingReceivedPackets In addition to the above listed objects (which are always present), the message will also specify the following quantities: if any responses were received: rsPingMinReturnTime rsPingAvgReturnTime rsPingMaxReturnTime |
|
.1.3.6.1.4.1.259.10.1.14.89.0.137 |
This trap indicates that a PPP link got an unrecognized secret.
The bound variables rndErrorDesc, rndErrorSeverity(== warning ), interface Number. and pppSecurityIdentity |
|
.1.3.6.1.4.1.259.10.1.14.89.0.138 |
||
.1.3.6.1.4.1.259.10.1.14.89.0.139 |
||
.1.3.6.1.4.1.259.10.1.14.89.0.14 |
Informational trap indicating that the device has intiated a
TFTP session. rndErrorDesc will contain the file type in question |
|
.1.3.6.1.4.1.259.10.1.14.89.0.140 |
||
.1.3.6.1.4.1.259.10.1.14.89.0.141 |
Whenever main server fails and backup takes over or server comes
up after failure a trap of this type is issued. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.142 |
DHCP failed to allocate an IP address to a requesting host
because of memory shortage or inadequate configuration of available IP addresses. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.145 |
The IP SFFT overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.146 |
The IP NFFT overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.147 |
The IPX SFFT overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.148 |
The IPX NFFT overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.149 |
The IPM FFT overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.150 |
Indicates that the physical decription of the device has
changed |
|
.1.3.6.1.4.1.259.10.1.14.89.0.151 |
The trap is sent by a bridge when any of its configured ports
transitions from the Learning state to the Forwarding state. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.152 |
The trap is sent by a bridge when any of its configured ports
transitions from the Forwarding state to the Blocking state. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.153 |
Indicates that the packet drop due to the policy
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.154 |
Indicates that the packet has forward based on policy
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.156 |
An IGMP PROXY Table overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.157 |
An IGMP Message of v1 received on ifIndex.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.158 |
One or more VRRP entries deleted due to IP interface deletion or transition.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.159 |
Hot swap trap.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.160 |
Informational trap indicating that a port is added to a trunk
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.161 |
This warning is generated when a port removed from a trunk.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.162 |
Informational trap indicating that a port can not be added to
a trunk because of device limitations or diffrent swIfType. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.170 |
Informational trap indicating that a locked port receive
a frame with new source Mac Address. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.171 |
add gvrp dynamic vlan
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.172 |
remove gvrp dynamic vlan
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.173 |
vlan status was changed from dynamic to static
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.174 |
vlan status was changed from static to dynamic
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.175 |
Master receive trap from slave , and forward it as trap
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.176 |
Trap indicating the fan state.
rndErrorSeverity will be: 0 for fan state nomal, notPresent 1 for fan state warning, notFunctioning 2 for fan state critical 3 for fan state fatal The error text will specify the fan index, fan description and the exact fan state |
|
.1.3.6.1.4.1.259.10.1.14.89.0.177 |
Trap indicating the power supply state.
rndErrorSeverity will be: 0 for power supply state nomal, notPresent 1 for power supply state warning, notFunctioning 2 for power supply state critical 3 for power supply state fatal The error text will specify the power supply index, power supply description and the exact power supply state |
|
.1.3.6.1.4.1.259.10.1.14.89.0.178 |
Trap indicating the stack connection state
0 for stack state connected, 1 for stack state disconnected |
|
.1.3.6.1.4.1.259.10.1.14.89.0.179 |
Trap indicating that the temperature in the device has exceeded the
device specific safe temperature threshold. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.183 |
Informational trap indicating that adding dynamic mac/s
failed due to full hash chain. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.184 |
Informational trap indicating that port 802.1x status is authorized.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.185 |
Warning trap is indicating that port 802.1x status is unAuthorized.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.192 |
Warning trap is indicating port lock hase began.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.193 |
Warning trap is indicating port lock has ended.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.194 |
Warning trap indicating that the user was locked after
number of consecutives unsuccessful login attempts. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.202 |
Warning trap indicating - Port was suspended because there was BPDU Guard violation.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.203 |
Informational trap indicating that MAC authentication supplicant
is authenticated and is allowed to access the network. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.204 |
Warning trap is indicating that Radius server rejects
MAC authentication supplicant. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.205 |
Warning trap indicating - A loopback was detected on port.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.206 |
Warning trap indicating - A loopback detection resolved on port.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.207 |
Warning trap indicating - A port has been suspended by Loopback Detection.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.213 |
Warning trap indicating - A port has been suspended by Any application.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.214 |
Warning trap indicating - Special BPDU DB Overflow.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.215 |
Warning trap is indicating that supplicant was logged out
Since the port?s time-range state was changed to inactive. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.216 |
Warning trap is indicating that altough port?s time-range
Is active now, it can not start working in mode auto. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.217 |
Warning trap indicating - Port has multiple LLDP remote link neighbours -
EEE operational state will be FALSE. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.218 |
Warning trap indicating - Port has single LLDP remote link neighbour -
EEE operational can be TRUE. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.222 |
Informational trap indicating that stack slave is upgrading
to the image or boot version of the stack master. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.223 |
Warning trap indicating that stack slave is downgrading
to the image or boot version of the stack master. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.23 |
Automantic switchover to backup link because of main link fault.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.24 |
Communication returened to main link.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.3 |
An RX buffer overflow has occurred in one of the LAN or link
interfaces. The bound variable rndErrorDesc provides the interface number. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.36 |
This trap indicates that in an OpenGate IPX RIP table overflow.
The bound variable rndErrorDesc, rndErrorSeverity provides the actual message text and severity respectively. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.37 |
This trap indicates that in an OpenGate IPX SAP table overflow.
The bound variable rndErrorDesc, rndErrorSeverity provides the actual message text and severity respectively. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.4 |
Interport queue overflow has occurred in one of the LAN or link interfaces.
The bound variable rndErrorDesc provides the interface number. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.49 |
This trap indicates that message that fits FACS statenebt with
operation blockAndReport was forward to the interface. The bound variable rndErrorDesc, rndErrorSeverity(== info ) and interface Number. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.5 |
An overflow condition has occurred in the Routing Table. The Routing
Table is used for IP routing algorithm (RIP). |
|
.1.3.6.1.4.1.259.10.1.14.89.0.50 |
This trap indicates that auto comfiguration completetd succssefully.
The bound variable rndErrorDesc, rndErrorSeverity(== info ) |
|
.1.3.6.1.4.1.259.10.1.14.89.0.51 |
This trap indicates that an overflow condition has occurred in the
layer II Forward Table. The bound variable rndErrorDesc, rndErrorSeverity(== warning ) |
|
.1.3.6.1.4.1.259.10.1.14.89.0.53 |
This trap indicates that a connection establish between the Frame
relay Switch and the WanGate. The bound variable rndErrorDesc, rndErrorSeverity(== warning ) |
|
.1.3.6.1.4.1.259.10.1.14.89.0.54 |
This trap indicates that a connection between the Frame Relay Switch
and the WanGate failed. The bound variable rndErrorDesc, rndErrorSeverity(== warning ) |
|
.1.3.6.1.4.1.259.10.1.14.89.0.61 |
This trap indicates that the an error occured during initialization
The bound variable rndErrorDesc, rndErrorSeverity(== error ) |
|
.1.3.6.1.4.1.259.10.1.14.89.0.66 |
||
.1.3.6.1.4.1.259.10.1.14.89.0.67 |
||
.1.3.6.1.4.1.259.10.1.14.89.0.68 |
This warning is generated when an overflow occurs in the clients table.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.69 |
This warning is generated when a server does not respond to the dispatchers polling
and is thought to be inactive. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.70 |
The Zero Hop Routing connections Table has been overflown.
|
|
.1.3.6.1.4.1.259.10.1.14.89.0.71 |
The requested static connection was not accepted because there is
no available IP virtual address to allocate to it. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.72 |
The virtual IP address appeared as a source IP.
All the connections using it will be deleted and it will not be further allocated to new connections. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.73 |
The source IP address sent an ARP specifying a virtual IP
which was not allocated for this source. This virtual IP will not be allocated to connections of this specific source IP. |
|
.1.3.6.1.4.1.259.10.1.14.89.0.74 |
An incoming SNMP SET request was rejected because no such
requests (except action requests) are accepted after start of new configuration reception or during sending the current configuration to an NMS. |
