A3COM0012-TRAPTABLE2

MIB Reference — IPNetwork Monitor

All MIBsA3COM0012-TRAPTABLE2

Category: SNMP Framework

Description:

Defines trap notification objects for 3Com devices to report fault and status events.

Imported Objects

From A3COM0004-GENERIC

localSnmpOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1213-MIB

DisplayString

What Is A3COM0012-TRAPTABLE2?

This is a 3Com private MIB defining a generic SNMP trap notification table used across various 3Com networking devices to report fault and status events. It exposes configuration data for trap destinations (address, community, protocol) alongside a trap category and throttle mechanism, the plumbing that determines which events get reported and how often. While it doesn't expose granular hardware sensors itself, it underpins software/hardware fault monitoring by controlling how status and fault traps such as link-state or hardware failures are dispatched to management stations, and its throttle setting reveals whether trap-flood protection is active. As a legacy 3Com MIB it likely works alongside device-specific fault MIBs and standard SNMP notification concepts to actually generate the events being forwarded. It is typically deployed on older 3Com switches/routers where administrators configure and monitor how fault/status notifications are relayed to a network management system. Network engineers evaluating or troubleshooting this functionality can download the A3COM0012-TRAPTABLE2 file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in A3COM0012-TRAPTABLE2. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • configured trap destinations
  • trap category
  • trap throttle rate
  • trap row status

Supported Devices

  • 3Com switch
  • 3Com router/networking device

Monitoring Examples

An administrator reviews snmpTrapTable / snmpTrapEntry entries to confirm snmpTrapDestination and snmpTrapCommunity are correctly configured for a given snmpTrapCategory, and checks snmpTrapThrottle to ensure trap storms are rate-limited. If snmpTrapRowStatus shows an entry not active, or snmpTrapNextFreeIndex never changes despite known device faults, trap forwarding to the NMS may be broken.

OIDs
OID symbolicOID numericTypeAccessDescription
snmpTrapTable1.3.6.1.4.1.43.10.10.2not-accessibleThis table can store the destination addresses of SNMP managers that wish to receive traps from this device.
snmpTrapEntry1.3.6.1.4.1.43.10.10.2.1not-accessibleThis table can store the destination addresses of SNMP managers that wish to receive traps from this device.
INT snmpTrapIndex1.3.6.1.4.1.43.10.10.2.1.1INTEGERread-onlyThis is the unique identifier for this row in the snmpTrapTable. When creating a new row, a manager can read the value of the snmpTrapNextFreeIndex object and (if non-zero) can use this value as the index of the new row to be created. The actual number of rows that can be created on any particular device depends on the memory and processing resources available at the time.
STR snmpTrapDestination1.3.6.1.4.1.43.10.10.2.1.2DisplayStringread-writeThis DisplayString is the network address of the device to which SNMP traps will be sent. This is an IP or IPX address. The following formats can be used. IP nnn.nnn.nnn.nnn - dotted format IPX AABBCCDD:AABBCCDDEEFF - network : node Destination addresses must be unique within this table. An error is returned if an attempt is made to add a duplicate address.
INT snmpTrapProtocol1.3.6.1.4.1.43.10.10.2.1.3INTEGERread-onlyThis defines the transport protocol to use when sending an SNMP trap. At present, this value is determined by the format/value of snmpTrapDestionation which is currently un-ambiguous and so this object is read-only.
STR snmpTrapCommunity1.3.6.1.4.1.43.10.10.2.1.4DisplayStringread-writeSNMP Community String to be used when sending Traps to this destination.
OCT snmpTrapCategory1.3.6.1.4.1.43.10.10.2.1.5OCTET STRINGread-write32 Bit Mask indicating which Trap categories that the snmpTrapDestination is interested in. '00000001'h - High Priority Configuration Traps '00000002'h - Low Priority Configuration Traps '00000004'h - High Priority Security Traps '00000008'h - Low Priority Security Traps '00000010'h - Alarms & Polling Traps '00000020'h - Regular Heartbeat Traps '00000040'h - End Station Table Traps '00000080'h - reserved '00000100'h - Physical Entity Traps '00000200'h - Facility Traps '00000400'h - Service Related Traps A value of 0xFFFFFFFF enables all traps.
INT snmpTrapThrottle1.3.6.1.4.1.43.10.10.2.1.6INTEGERread-writeThe maximum rate at which that snmpTrapDestination is willing to receive traps, specified as the minimum interval in milliseconds between traps. For example, a value of 2000 will limit traps sent to this destination to one trap every 2 seconds. A value of zero indicates that no trap throttling is required.
INT snmpTrapRowStatus1.3.6.1.4.1.43.10.10.2.1.7INTEGERread-writeThe SNMPv2 RowStatus convention. Notes: Because this is such a simple table:- 1) Writing any data to a destroyed row, changes its state to active. 2) There is no notReady or notInService state. Each row is either active or destroyed.
INT snmpTrapNextFreeIndex1.3.6.1.4.1.43.10.10.3INTEGERread-onlyIndicates the the next value of snmpTrapIndex which can be used to create a new trap destination entry. This value is zero if there are no free rows in the table.

RFC description

3Com SNMP trap destination and delivery configuration for sending traps to network management stations.

Start monitoring Legacy 3Com switches/routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download A3COM0012-TRAPTABLE2