CHIPCOMMIB :: chipModuleDown

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCHIPCOMMIBchipModuleDown

chipModuleDown

Module: CHIPCOMMIB

OID (symbolic): CHIPCOMMIB::chipModuleDown

OID (numeric): 1.3.6.1.4.1.49.0.16

Node type: NOTIFICATION-TYPE

Description: A chipSlotDown trap indicates that management communications with the slot indicated by chipModSlotIndex has been broken. This event usually occurs when a module has been physically removed from the concentrator. However, it is possible for this event to occur when the particular module fails.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' CHIPCOMMIB::chipModuleDown
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.49.0.16

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:57179->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (387638107) 44 days, 20:46:21.07
  SNMPv2-MIB::snmpTrapOID.0 = OID: CHIPCOMMIB::chipModuleDown

Start monitoring Chipcom (3Com) Ethernet/Token Ring switching hub or LAN concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CHIPCOMMIB::chipModuleDown OID value, configure state conditions and alerts, and monitor any Chipcom (3Com) Ethernet/Token Ring switching hub or LAN concentrator (legacy) from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.49chipcomCHIPAGENT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.49.0.16chipModuleDownCHIPCOMMIB