12.07.2015 Views

Version 3.1 SP2 Reference Guide - Extreme Networks

Version 3.1 SP2 Reference Guide - Extreme Networks

Version 3.1 SP2 Reference Guide - Extreme Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Event Types for AlarmsTable 38: SNMP Trap Events (continued)EventOSPF TX_RetransmitOSPF Virtual InterfaceAuthentication FailureOSPF Virtual InterfaceConfig ErrorOSPF Virtual InterfaceReceive Bad PacketOSPF Virtual InterfaceState ChangeOSPF Virtual InterfaceTX RetransmitOSPF Virtual NeighborState ChangeOverheatPing Probe FailedPing Test CompletedDefinitionAn ospfTxRetransmit trap signifies than an OSPF packet hasbeen retransmitted on a non- virtual interface. All packets thatmay be retransmitted are associated with an LSDB entry. TheLS type, LS ID, and Router ID are used to identify the LSDBentry.An ospfVirtIfAuthFailure trap signifies that a packet has beenreceived on a virtual interface from a router whoseauthentication key or authentication type conflicts with thisrouter’s authentication key or authentication type.An ospfVirtIfConfigError trap signifies that a packet has beenreceived on a virtual interface from a router whoseconfiguration parameters conflict with this router’s configurationparameters. Note that the event optionMismatch should causea trap only if it prevents an adjacency from forming.An ospfVirtIfRxBadPacket trap signifies that an OSPF packethas been received on a virtual interface that cannot be parsed.An ospfVirtIfStateChange trap signifies that there has been achange in the state of an OSPF virtual interface. This trapshould be generated when the interface state regresses (e.g.,goes from Point- to-Point to Down) or progresses to a terminalstate (i.e., Point-to-Point).An ospfVirtIfTxRetransmit trap signifies than an OSPF packethas been retransmitted on a virtual interface. All packets thatmay be retransmitted are associated with an LSDB entry. TheLS type, LS ID, and Router ID are used to identify the LSDBentry.An ospfVirtNbrStateChange trap signifies that there has been achange in the state of an OSPF virtual neighbor. This trapshould be generated when the neighbor state regresses (e.g.,goes from Attempt or Full to 1-Way or Down) or progresses toa terminal state (e.g., Full).<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Indicates the on boardtemperature sensor has reported an overheat condition. Thisindicates the temperature has reached the Overheat threshold.The switch will continue to function until it reaches its shutdownthreshold. The system will then shutdown until the unit hassufficiently cooled such that operation may begin again. A coldstart trap will be issued when the unit has come back on line.This trap is sent repetitively every 30 seconds until thetemperature goes back to normal.Generated when a probe failure is detected when thecorresponding pingCtlTrapGeneration object is set toprobeFailure(0) subject to the value ofpingCtlTrapProbeFailureFilter. The objectpingCtlTrapProbeFailureFilter can be used to specify thenumber of successive probe failures that are required beforethis notification can be generated.Generated at the completion of a ping test when thecorresponding pingCtlTrapGeneration object is set totestCompletion(4).<strong>Extreme</strong>Ware/<strong>Extreme</strong>XOS<strong>Version</strong><strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1<strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1<strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1<strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1<strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1<strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1<strong>Extreme</strong>Ware 6.1.9<strong>Extreme</strong>XOS 10.1All<strong>Extreme</strong>Ware 6.1.9Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>Ware 6.1.9Not supported in<strong>Extreme</strong>XOS692Ridgeline <strong>Reference</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!