RUGGEDCOM-TRAPS-MIB

        The RuggedCom MIB providing traps information.
    
Source file
RUGGEDCOM-TRAPS-MIB
Last revised
Identity
ruggedcomTrapsModule
Base OID
1.3.6.1.4.1.15004.4.1
Net-SNMP examples using the siemens MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'RUGGEDCOM-TRAPS-MIB' -M '/opt/observium/mibs/siemens:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RUGGEDCOM-TRAPS-MIB::ruggedcomTrapsModule'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'RUGGEDCOM-TRAPS-MIB' -M '/opt/observium/mibs/siemens:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RUGGEDCOM-TRAPS-MIB::ruggedcomTrapsModule'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (42)
.1.3.6.1.4.1.15004.4.1
.1.3.6.1.4.1.15004.4.1.1
.1.3.6.1.4.1.15004.4.1.1.1
Enumeration
.1.3.6.1.4.1.15004.4.1.1.1.1
.1.3.6.1.4.1.15004.4.1.1.1.2
.1.3.6.1.4.1.15004.4.1.1.10
.1.3.6.1.4.1.15004.4.1.1.11
.1.3.6.1.4.1.15004.4.1.1.12
.1.3.6.1.4.1.15004.4.1.1.13
.1.3.6.1.4.1.15004.4.1.1.13.1
.1.3.6.1.4.1.15004.4.1.1.13.2
.1.3.6.1.4.1.15004.4.1.1.13.3
.1.3.6.1.4.1.15004.4.1.1.14
.1.3.6.1.4.1.15004.4.1.1.14.1
Enumeration
.1.3.6.1.4.1.15004.4.1.1.14.2
.1.3.6.1.4.1.15004.4.1.1.14.3
.1.3.6.1.4.1.15004.4.1.1.19
.1.3.6.1.4.1.15004.4.1.1.19.1
Enumeration
.1.3.6.1.4.1.15004.4.1.1.19.2
.1.3.6.1.4.1.15004.4.1.1.19.3
.1.3.6.1.4.1.15004.4.1.1.19.4
.1.3.6.1.4.1.15004.4.1.1.19.5
Enumeration
.1.3.6.1.4.1.15004.4.1.1.19.6
.1.3.6.1.4.1.15004.4.1.1.19.7
Enumeration
.1.3.6.1.4.1.15004.4.1.1.19.8
.1.3.6.1.4.1.15004.4.1.1.2
.1.3.6.1.4.1.15004.4.1.1.2.1
.1.3.6.1.4.1.15004.4.1.1.2.2
.1.3.6.1.4.1.15004.4.1.1.3
.1.3.6.1.4.1.15004.4.1.1.4
.1.3.6.1.4.1.15004.4.1.1.5
.1.3.6.1.4.1.15004.4.1.1.5.1
.1.3.6.1.4.1.15004.4.1.1.5.2
.1.3.6.1.4.1.15004.4.1.1.6
.1.3.6.1.4.1.15004.4.1.1.6.1
.1.3.6.1.4.1.15004.4.1.1.6.2
.1.3.6.1.4.1.15004.4.1.1.6.3
.1.3.6.1.4.1.15004.4.1.1.7
.1.3.6.1.4.1.15004.4.1.1.8
.1.3.6.1.4.1.15004.4.1.1.9
.1.3.6.1.4.1.15004.4.1.5
.1.3.6.1.4.1.15004.4.1.5.2
Dependencies (5) 5 direct 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
  1. SNMPv2-SMIrfc
  2. RUGGEDCOM-MIBsiemens
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. RUGGEDCOM-SYS-INFO-MIBsiemens
  6. RUGGEDCOM-TRAPS-MIBsiemensselected
Conformance Groups (25)
A group of objects that define RuggedCom generic traps.
.1.3.6.1.4.1.15004.4.1.5.2.1
A group of objects that define RuggedCom power supply failure trap.
.1.3.6.1.4.1.15004.4.1.5.2.2
The RuggedCom notifications group.
.1.3.6.1.4.1.15004.4.1.5.2.3
The RuggedCom notifications group for devices that do not use
the concept of configuration revision number.
.1.3.6.1.4.1.15004.4.1.5.2.4
A group of objects that define RuggedCom power supply identification.
.1.3.6.1.4.1.15004.4.1.5.2.5
The RuggedCom notifications group.
.1.3.6.1.4.1.15004.4.1.5.2.6
The RuggedCom Hot-swap Module notifications group.
.1.3.6.1.4.1.15004.4.1.5.2.7
A group of objects that define RuggedCom fan bank failure trap.
.1.3.6.1.4.1.15004.4.1.5.2.8
A group of objects that define RuggedCom Module State Change trap.
.1.3.6.1.4.1.15004.4.1.5.2.9
A group of objects for insecurity indication.
.1.3.6.1.4.1.15004.4.1.5.2.10
The RuggedCom Hot-swap Module notifications group.
.1.3.6.1.4.1.15004.4.1.5.2.11
A group of objects for insecurity indication.
.1.3.6.1.4.1.15004.4.1.5.2.12
A group of objects for RTC Battery Low indication.
.1.3.6.1.4.1.15004.4.1.5.2.13
A group of objects for security certificate expiry indication.
.1.3.6.1.4.1.15004.4.1.5.2.14
A group of objects for security certificate expiry indication.
.1.3.6.1.4.1.15004.4.1.5.2.15
A group of objects for device error indication.
.1.3.6.1.4.1.15004.4.1.5.2.16
A group of objects to notify device login events.
.1.3.6.1.4.1.15004.4.1.5.2.17
A group of objects to notify GMRP events.
.1.3.6.1.4.1.15004.4.1.5.2.18
A group of objects to notify GMRP events.
.1.3.6.1.4.1.15004.4.1.5.2.19
A group of objects to notify Mcast CPU Filter Table events.
.1.3.6.1.4.1.15004.4.1.5.2.20
A group of objects to notify IGMP events.
.1.3.6.1.4.1.15004.4.1.5.2.21
rcMacAddrAuthFailedTrap (unresolved reference)
A group of objects to notify MAC Address Authentication events.
.1.3.6.1.4.1.15004.4.1.5.2.22
A group of objects to notify BPDU events.
.1.3.6.1.4.1.15004.4.1.5.2.23
A group of objects to notify serial communication events.
.1.3.6.1.4.1.15004.4.1.5.2.24
A group of trap objects to notify password successfully changed
.1.3.6.1.4.1.15004.4.1.5.2.25
Notifications / Traps (46)
NameOIDDescription
.1.3.6.1.4.1.15004.5.1
A generic trap generated by RuggedCom devices.
.1.3.6.1.4.1.15004.5.13
A use of default keys for secure services (SSH and SSL) indication
trap generated by RuggedCom devices.
.1.3.6.1.4.1.15004.5.14
A boot software version indication trap generated by RuggedCom
devices.
.1.3.6.1.4.1.15004.5.15
A trap indicating that the device's RTC Battery level is low enough
that there may be a problem after the next device reboot cycle.
It is generated by RuggedCom devices.
.1.3.6.1.4.1.15004.5.16
A trap indicating that at least one security certificate on the device
is within 30 days of expiration. It is generated by RuggedCom devices.
.1.3.6.1.4.1.15004.5.17
The bfaTrap is generated when Brute Force Attack is detected
on the unit and source of attack is blocked, or released.
Different devices might block attacking IP address for all the
IP services, others might block the service on which
attack is detected for all IP addresses, while some might just
give a status of unit being under attack.
.1.3.6.1.4.1.15004.5.2
A trap generated when a power supply fails or comes up. The first
trap would be generated on first power supply failure. The state
of power supply (failed or restored ) is retrieved via object
powerSupplyDescription at the time when trap is generated.
The status of power supply units in device can be retrieved via
objects rcDeviceStsPowerSupply1 and rcDeviceStsPowerSupply2.

powerSupplyIdentifier object is recommended to be added as an optional
parameter to the list of objects.
successUsrChgPwd (unresolved reference)
.1.3.6.1.4.1.15004.5.20
A trap generated when a user's password is successfully changed.
.1.3.6.1.4.1.15004.5.20.1
Admin Level Password Changed
.1.3.6.1.4.1.15004.5.20.2
Operator Level Password Changed
.1.3.6.1.4.1.15004.5.20.3
Guest Level Password Changed
.1.3.6.1.4.1.15004.5.20.4
RADIUS authenticate key changed
.1.3.6.1.4.1.15004.5.20.5
Tacacs+ authenticate key changed
.1.3.6.1.4.1.15004.5.20.6
Data Storage pass-phrase changed
.1.3.6.1.4.1.15004.5.20.7
SNMP community character string changed
.1.3.6.1.4.1.15004.5.20.8
SNMP authenticate key changed
.1.3.6.1.4.1.15004.5.20.9
SNMP private Key changed
rcDeviceErrSystem (unresolved reference)
.1.3.6.1.4.1.15004.5.24
A device error indication trap generated by RuggedCom devices.
.1.3.6.1.4.1.15004.5.25
A trap indicating unknown private key from an SNMP V3 user.
loginUser loginMgmtApp loginRemoteIP loginAccessLevel (unresolved reference)
.1.3.6.1.4.1.15004.5.26
A trap informing successful login to the device.
loginUser loginMgmtApp loginRemoteIP loginAccessLevel (unresolved reference)
.1.3.6.1.4.1.15004.5.27
A trap indicating login failure attempt to the device.
.1.3.6.1.4.1.15004.5.28
A trap indicating excessive login failure attempts to the device.
.1.3.6.1.4.1.15004.5.29
A trap indicating GMRP cannot learn more addresses
.1.3.6.1.4.1.15004.5.3
A generic trap generated upon software upgrade.
The rate at which this notification can be provided is 60 seconds.
.1.3.6.1.4.1.15004.5.30
A trap indicating GVRP cannot learn more VLANs
.1.3.6.1.4.1.15004.5.31
A trap indicating Mcast CPU filtering table is full
.1.3.6.1.4.1.15004.5.32
A trap indicating IGMP Group Membership table full
.1.3.6.1.4.1.15004.5.33
A trap indicating IGMP Mcast Forwarding table full
.1.3.6.1.4.1.15004.5.34
A trap indicating MAC address not learned
.1.3.6.1.4.1.15004.5.36
A trap generated to indicate that IEEE1588 PTP lost master clock, in holdover state now.
.1.3.6.1.4.1.15004.5.37
A trap generated to indicate that IEEE1588 PTP BMC foreign master comparison error.
ifIndex (unresolved reference)
.1.3.6.1.4.1.15004.5.38
A trap generated upon port security violation.
.1.3.6.1.4.1.15004.5.4
A generic trap generated upon configuration change.
The rate at which this notification can be provided is 60 seconds.
ifIndex (unresolved reference)
.1.3.6.1.4.1.15004.5.40
A trap generated when looped back BPDU received on the port.
ifIndex (unresolved reference)
.1.3.6.1.4.1.15004.5.41
A trap generated when BPDU Guard is activated on the port.
.1.3.6.1.4.1.15004.5.42
A trap generated to indicate serial communication is blocked.
.1.3.6.1.4.1.15004.5.43
A trap generated to indicate unknown route for serial protocol.
.1.3.6.1.4.1.15004.5.44
A trap generated to indicate the console service changed.
.1.3.6.1.4.1.15004.5.44.1
Local Console Enabled
.1.3.6.1.4.1.15004.5.44.2
Local Console Disabled
.1.3.6.1.4.1.15004.5.49
A trap generated when a file transfer events takes place.
.1.3.6.1.4.1.15004.5.5
A generic trap generated upon configuration change by
device that does not use the concept of configuration
revision number.
.1.3.6.1.4.1.15004.5.6
A trap generated when a fan bank fails or fails to comes up. The
first trap would be generated on first fan bank failure. The state
of fan bank (failed or restored ) is retrieved via object
fan bank Description at the time when trap is generated.
The status of power supply units in device can be retrieved via
objects rcDeviceStsFanBank1 and rcDeviceStsFanBank2.
.1.3.6.1.4.1.15004.5.7
A trap generated when a ROX 2 Module changes state. The first
traps would be generated during initial start up.
.1.3.6.1.4.1.15004.5.8
A weak password indication trap generated by RuggedCom devices.
.1.3.6.1.4.1.15004.5.9
A trap generated when ROX 2 sees that, for a given slot, the configured module type
does not match the detected module type. The first
traps would be generated during initial start up.