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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AppendixTable 38: SNMP Trap Events (continued)EventWireless Off ChannelScan FinishedWireless Off ChannelScan StartedWireless Port BootFailedWireless Port StateChangedWireless Probe InfoAddedWireless Probe InfoRemovedlldp Remote TableChangedDefinition<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Generated when an offchannelscan finishes running.<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Generated when an offchannelscan starts running.<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Sent by the platform if awireless port fails to boot too many times.<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Generated when a wirelessport moves into enabled, disabled, or online state.<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Generated when a newstation is added to the probe info table. Generated only if thevalue of extremeWirelessProbeInfoSendAddedTrap is true.<strong>Extreme</strong> <strong>Networks</strong> proprietary trap. Generated when a stationis removed from the probe info table. Generated only if thevalue of extremeWirelessProbeInfoSendRemovedTrap is true.A lldpRemTablesChange notification is sent when the value oflldpStatsRemTableLastChangeTime changes. It can be utilizedby an NMS to trigger LLDP remote systems table maintenancepolls.Note that transmission of lldpRemTablesChange notificationsare throttled by the agent, as specified by the'lldpNotificationInterval' object.<strong>Extreme</strong>Ware/<strong>Extreme</strong>XOS<strong>Version</strong><strong>Extreme</strong>Ware 7.3Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>Ware 7.3Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>Ware 7.3Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>Ware 7.3Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>Ware 7.3Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>Ware 7.3Not supported in<strong>Extreme</strong>XOS<strong>Extreme</strong>XOS 11.4Configuring SNMP Trap EventsThere are a number of SNMP events that require configuration on the switch before they can be used inRidgeline alarm definitions. If the configuration is not done on the switch, no trap events are generated,and no Ridgeline alarms for those events can occur. The Ping and OSPF traps fall into this category.To configure the switch to send one of these traps, you must use a tool that allows you to set the valueof the appropriate SNMP variable. Tools such as SNMPc can be used to perform this function. Thefollowing information assumes that you have a thorough understanding of SNMP and an appropriateSNMP utility.Refer to the appropriate MIBs for details of the variable settings:● Ping MIB: pingmib.mib (RFC 2925)●OSPF v2 MIB: RFC 1850 or RFC 1850tTable 39: Trap Variable ConfigurationTrapPing Probe FailedVariablesset pingCtlTrapGeneration bit 0 ON to enable trap.set pingCtlTrapProbeFailureFilter to specify the number ofsuccessive probe failures that must occur to generate a ProbeFailed trap.Ridgeline <strong>Reference</strong> <strong>Guide</strong>695

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

Saved successfully!

Ooh no, something went wrong!