NTNTECH-CHASSIS-CONFIGURATION-MIB :: uimCfgEthMumIndex

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › NTNTECH-CHASSIS-CONFIGURATION-MIB › uimCfgEthMumIndex

uimCfgEthMumIndex

Module: NTNTECH-CHASSIS-CONFIGURATION-MIB

OID (symbolic): NTNTECH-CHASSIS-CONFIGURATION-MIB::uimCfgEthMumIndex

OID (numeric): 1.3.6.1.4.1.8059.1.1.1.1.1.1.3.1.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Translates to the physical slot number that a MUM200-2/2000-2 module 
exists within a chassis. The Mini/Micro DSLAMs' physical location is
set to 1 by default.  See below,  

 chassis type     physical location(s) translation
 ------------     --------------------------------          
   IPD12000       MUM in slots 13,14 = uimCfgEthMumIndex 1,2 respecitively 
   IPD4000        MUM in slot 5      = uimCfgEthMumIndex 1 
   Mini DSLAM     NA                             = uimCfgEthMumIndex 1
   Micro DSLAM    NA                             = uimCfgEthMumIndex 1
   
Note: when configuring an ethernet UIM, the user must enter the
      index of the MUM, see above table, that corresponds with the
      IP address of the remote SNMP agent.

What is uimCfgEthMumIndex?

Identifies which MUM slot (1 or 2 on an IPD12000, always 1 elsewhere) hosts the Ethernet UIM this table row describes; when configuring an Ethernet UIM, the admin must supply the index matching the remote agent's IP.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8059.1.1.1.1.1.1.3.1.1.1
snmpwalk -v2c -c public <target> NTNTECH-CHASSIS-CONFIGURATION-MIB::uimCfgEthMumIndex

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.8059.1.1.1.1.1.1.3.1.1.1.1
snmpget -v2c -c public <target> NTNTECH-CHASSIS-CONFIGURATION-MIB::uimCfgEthMumIndex.1

Start monitoring Paradyne nTech DSLAMs with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NTNTECH-CHASSIS-CONFIGURATION-MIB::uimCfgEthMumIndex OID value, configure state conditions and alerts, and monitor any Paradyne nTech DSLAMs from a single console.

OID Breakdown

Upper-level ancestors (9 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.8059ntntechRootMIBNTNTECH-ROOT-MIB
1.3.6.1.4.1.8059.1ntntechNamingTreeNTNTECH-ROOT-MIB
1.3.6.1.4.1.8059.1.1ntntechChassisNTNTECH-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.8059.1.1.1ntntechChassisConfigurationMIBNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1chsCfgMIBObjectsNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1.1chsCfgParameterConfigurationNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1.1.1prmCfgMultiplexerUplinkModuleNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1.1.1.3mumCfgUplinkInterfaceModuleNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1.1.1.3.1uimCfgEthTableNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1.1.1.3.1.1uimCfgEthEntryNTNTECH-CHASSIS-CONFIGURATION-MIB
1.3.6.1.4.1.8059.1.1.1.1.1.1.3.1.1.1uimCfgEthMumIndexNTNTECH-CHASSIS-CONFIGURATION-MIB