UMC1000TRAPS :: umc1TrapPitProvChgTableChange

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsUMC1000TRAPSumc1TrapPitProvChgTableChange

umc1TrapPitProvChgTableChange

Module: UMC1000TRAPS

OID (symbolic): UMC1000TRAPS::umc1TrapPitProvChgTableChange

OID (numeric): 1.3.6.1.4.1.2067.1.1.2.0.1000000006

Node type: NOTIFICATION-TYPE

Description: The trap contains the new row created in the Plug-In Provisioning Change Table. The management host compares this umc1SystemPitProvChgSeqNbr value with the last one received to determine if any traps have been lost. If this value is one greater than the last one received, no traps were lost, and the management host uses the five octets following the version octet in umc1SystemPitProvChgData, the second varbind, to retrieve the location and Plug-in type of the Plug-in whose provisioning data has changed. The value of the seventh octet in umc1SystemPitProvChgData for the given plug-in location and plug-in type is defined by 'DbActionType' in UMC1000.MIB. If the seventh octet indicates the record was deleted it must delete the plug-in provisioning database record for the given plug-in location and plug-in type. Otherwise, if the seventh octet indicates the record added or updated it must retrieve the provisioning database record from the octets following the seventh octet and update the provisioning data of the given plug-in location and plug-in type. If the value of umc1SystemPitProvChgSeqNbr is more than one (1) greater than the last one received, the management host determines it has lost one or more of these Traps. The management host attempts to retrieve the entry in the Plug-In Provisioning Change Table indexed by the last value umc1SystemPitProvChgSeqNbr received. If this entry cannot be retrieved, the management host determines that more traps have been lost than the number of entries the Plug-In Provisioning Change table can store. The management host then reads the entire Plug-In Provisioning Table to re-sync with that of the agent.

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> '' UMC1000TRAPS::umc1TrapPitProvChgTableChange
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.2067.1.1.2.0.1000000006

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]:51638->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (209131446) 24 days, 4:55:14.46
  SNMPv2-MIB::snmpTrapOID.0 = OID: UMC1000TRAPS::umc1TrapPitProvChgTableChange

Start monitoring Ubiquoss/UMC1000 fiber-to-copper media converter (link/module failure alarm notification status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UMC1000TRAPS::umc1TrapPitProvChgTableChange OID value, configure state conditions and alerts, and monitor any Ubiquoss/UMC1000 fiber-to-copper media converter (link/module failure alarm notification status) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.2067.1.1.2.0.1000000006umc1TrapPitProvChgTableChangeUMC1000TRAPS