Table of Contents
Advertisement
Chapter 1
Introduction
Trap
fallingAlarm
lldpRemoteTablesChange
The device also generates the following proprietary traps:
Table: Proprietary Traps
Trap
genericTrap
powerSupplyTrap
swUpgradeTrap
cfgChangeTrap
weakPasswordTrap
defaultKeysTrap
Generic traps carry information about events in their severity and description objects. They are sent at the same
time an alarm is generated for the device. The following are examples of RUGGEDCOM generic traps:
NOTE
Information about generic traps can be retrieved using the CLI command alarms. For more
information about the alarms command, refer to
Table: Generic Traps
Trap
heap error
NTP server failure
real time clock failure
failed password
MAC address not learned by switch fabric
BootP client: TFTP transfer failure
received looped back BPDU
received two consecutive confusing BPDUs on port, forcing down
GVRP failed to learn – too many VLANs
The device generates the following traps when specific events occur:
Table: Event-Based Traps
Trap
rcRstpNewTopology
12
MIB
LLDP-MIB
MIB
RUGGEDCOM-TRAPS-MIB
Section 2.6.1, "Available CLI
Severity
Alert
notification
Error
Warning
Warning
Error
Error
Error
Warning
MIB
RUGGEDCOM-STP-MIB
Commands".
Event
This trap is generated when the device
topology becomes stable after a topology
change occurs on a switch port.
RUGGEDCOM ROS
User Guide
SNMP Traps
- Quick Links:
- Cli Command Syntax
Hide quick links:
Advertisement
Table of Contents
