PKTC-IETF-MTA-MIB :: pktcMtaDevProvisioningState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsPKTC-IETF-MTA-MIBpktcMtaDevProvisioningState

pktcMtaDevProvisioningState

Module: PKTC-IETF-MTA-MIB

OID (symbolic): PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningState

OID (numeric): 1.3.6.1.2.1.140.1.1.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object indicates the completion state of the MTA device provisioning process.

pass: If the configuration file could be parsed successfully and the MTA is able to reflect the same in its MIB, the MTA MUST return the value 'pass'.

inProgress: If the MTA is in the process of being provisioned, the MTA MUST return the value 'inProgress'.

failConfigFileError: If the configuration file was in error due to incorrect values in the mandatory parameters, the MTA MUST reject the configuration file, and the MTA MUST return the value

'failConfigFileError'.

passWithWarnings: If the configuration file had proper values for all the mandatory parameters but has errors in any of the optional parameters (this includes any vendor-specific Object Identifiers (OIDs) that are incorrect or not known to the MTA), the MTA MUST return the value 'passWithWarnings'.

passWithIncompleteParsing: If the configuration file is valid but the MTA cannot reflect the same in its configuration (for example, too many entries caused memory exhaustion), it must accept the CMS configuration entries related, and the MTA MUST return the value 'passWithIncompleteParsing'.

failureInternalError: If the configuration file cannot be parsed due to an Internal error, the MTA MUST return the value 'failureInternalError'.

failureOtherReason: If the MTA cannot accept the configuration file for any other reason than the ones stated above, the MTA MUST return the value 'failureOtherReason'.

When a final SNMP INFORM is sent as part of Step 25 of the MTA Provisioning process, this parameter is also included in the final INFORM message.

What is pktcMtaDevProvisioningState?

Reports how the MTA's last configuration-file parse went — pass, inProgress, or one of several failure/warning states like failConfigFileError or passWithWarnings — the first thing to check when a phone won't register after a config push.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.140.1.1.8
snmpwalk -v2c -c public <target> PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.140.1.1.8.1
snmpget -v2c -c public <target> PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningState.1

Start monitoring vendor-neutral, standards-based MIB, RFC 4682 (PacketCable/IPCablecom MTA provisioning) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningState OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, RFC 4682 (PacketCable/IPCablecom MTA provisioning) 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.140pktcIetfMtaMibPKTC-IETF-MTA-MIB
1.3.6.1.2.1.140.1pktcMtaMibObjectsPKTC-IETF-MTA-MIB
1.3.6.1.2.1.140.1.1pktcMtaDevBasePKTC-IETF-MTA-MIB
1.3.6.1.2.1.140.1.1.8pktcMtaDevProvisioningStatePKTC-IETF-MTA-MIB