UMC1000-MIB :: umc1V5Index

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsUMC1000-MIBumc1V5Index

umc1V5Index

Module: UMC1000-MIB

OID (symbolic): UMC1000-MIB::umc1V5Index

OID (numeric): 1.3.6.1.4.1.2067.1.1.2.1.7.5.2.1.1

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: It contains the indices that identify a V5 record in the UMC system. The format of the indices depends on the type of the record that will be accessed. There are three (3) types of records, namely, Group provisioning records, Variant provisioning records and C-Channel provisioning records (V5.2 only). For the initial implementation the OCTET representation for each type of record is given below.

octet[0] Version number of the octet representation being used to define this INDEX. The version number for the initial implementation will be 0x01.

For Version number 0x01 the remaining octets will be defined as follows for each type of record:

1. For V5 Group Provisioning records.

octet[1] DB specifier octet. octet[2] Terminal number the V5 Group is associated with. See 'TerminalIdType' for the definition of valid Terminal values. octet[3] Group number the V5 Group is associated with. The See 'V5GroupIdType' for the definition of valid Group values.

2. For V5 Variant Provisioning records.

octet[1] DB specifier octet. octet[2] Terminal number the V5 Variant is associated with. See 'TerminalIdType' for the definition of valid Terminal values. octet[3] Group number the V5 Variant is associated with. The See 'V5GroupIdType' for the definition of valid Group values. octet[4] Variant identifier of the V5 Variant. Valid values are 0x00 and 0x01.

3. For V5.2 C-Channel Provisioning records.

octet[1] DB specifier octet. octet[2] Terminal number the V5.2 C-Channel is associated with. See 'TerminalIdType' for the definition of valid Terminal values. octet[3] Group number the V5.2 C-Channel is associated with. The See 'V5GroupIdType' for the definition of valid Group values. octet[4] C-Channel Set identifier. A valid value of the C-Channel Set identifier lies between 0x00 through 0x03.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2067.1.1.2.1.7.5.2.1.1
snmpwalk -v2c -c public <target> UMC1000-MIB::umc1V5Index

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2067.1.1.2.1.7.5.2.1.1.1
snmpget -v2c -c public <target> UMC1000-MIB::umc1V5Index.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.2067.1.1.2.1.7.5.2.1.1.1 s <value>

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::umc1V5Index 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 (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.1umc1SystemUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.1.7umc1ServiceUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.1.7.5umc1V5GrpUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.1.7.5.2umc1V5TableUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.1.7.5.2.1umc1V5EntryUMC1000-MIB
1.3.6.1.4.1.2067.1.1.2.1.7.5.2.1.1umc1V5IndexUMC1000-MIB