UMC1000-MIB :: umc1TerminalSpanTableChangeHistoryData

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › UMC1000-MIB › umc1TerminalSpanTableChangeHistoryData

umc1TerminalSpanTableChangeHistoryData

Module: UMC1000-MIB

OID (symbolic): UMC1000-MIB::umc1TerminalSpanTableChangeHistoryData

OID (numeric): 1.3.6.1.4.1.2067.1.1.2.6.3.1.2

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: This object stores the near end and far end location of all inter terminal spans that were added to/deleted from the UMC system when umc1TrapTerminalSpanTableChange trap was emitted by the agent with umc1TerminalSpanTableChangeHistoryIndex sequence number. The umc1TerminalSpanTableChangeHistoryData contains multiple terminal span entries corresponding to the all inter terminal spans that were added to/deleted from the UMC system. Each entry in the umc1TerminalSpanTableChangeHistoryData consisting of action byte followed by packed terminal span record. For initial implementation the OCTET representation will be as follows:

Octet[0] Version number (currently 0x01)

For version 0x01 octet[1] Holds the number of spans in this history record.

octets[2] through [11] hold the packed record for the 1st Terminal Span being reported and are defined as follows. Octet[2] Length of record. Octet[3] Action octet which specifies that the record attached after the action object has been added to/deleted from the umc1TerminalSpanTable. See DbActionType for valid values and meaning of this octet. Octet[4] Near End Terminal Id Octet[5] Near End Shelf Id Octet[6] Near End Slot Id Octet[7-8] Near End plug-in type Octet[9] Far End Terminal Id Octet[10] Far End Shelf Id Octet[11] Far End Slot Id

octets[12] through [20] hold the packed record for the next Terminal and so forth, until up to octet[1] number of spans have been defined.

What is umc1TerminalSpanTableChangeHistoryData?

An encoded batch of one or more inter-terminal span add/delete records: a version byte, a count of spans in this record, and for each one a length, an action byte, and the near-end/far-end terminal/shelf/slot/plug-in-type location -- letting the EMS learn which spans changed without re-reading the whole span table.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2067.1.1.2.6.3.1.2
snmpwalk -v2c -c public <target> UMC1000-MIB::umc1TerminalSpanTableChangeHistoryData

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2067.1.1.2.6.3.1.2.1
snmpget -v2c -c public <target> UMC1000-MIB::umc1TerminalSpanTableChangeHistoryData.1

Start monitoring UMC1000 universal media converter chassis (per-shelf/slot facility alarm status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UMC1000-MIB::umc1TerminalSpanTableChangeHistoryData OID value, configure state conditions and alerts, and monitor any UMC1000 universal media converter chassis (per-shelf/slot facility alarm status) from a single console.

OID Breakdown

Upper-level ancestors (10 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.2067afcAFC-OIDS
1.3.6.1.4.1.2067.1afcProductsAFC-OIDS
1.3.6.1.4.1.2067.1.1umcAFC-OIDS
1.3.6.1.4.1.2067.1.1.2umc1000AFC-OIDS
Numeric OIDNameModule
1.3.6.1.4.1.2067.1.1.2.6umc1SpanUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.6.3umc1TerminalSpanTableChangeHistoryTableUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.6.3.1umc1TerminalSpanTableChangeHistoryEntryUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.6.3.1.2umc1TerminalSpanTableChangeHistoryDataUMC1000-MIB