Table of Contents
Advertisement
Chapter 1
Introduction
Trap
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
The device generates the following traps when specific events occur:
Table: Event-Based Traps
Trap
rcRstpNewTopology
Section 1.7
ModBus Management Support
Modbus management support in RUGGEDCOM devices provides a simple interface for retrieving basic status
information. ModBus support simplifies the job of SCADA (Supervisory Control and Data Acquisition) system
integrators by providing familiar protocols for retrieving RUGGEDCOM device information. ModBus provides
mostly read-only status information, but there are some writable registers for operator commands.
The ModBus protocol PDU (Protocol Data Unit) format is as follows:
14
MIB
Section 2.6.1, "Available CLI Commands"
Severity
Alert
notification
Error
Warning
Warning
Error
Error
Error
MIB
RUGGEDCOM-STP-MIB
Event
This trap is generated when the device
topology becomes stable after a topology
change occurs on a switch port.
ModBus Management Support
RUGGEDCOM ROS
User Guide
.
Advertisement
Table of Contents
