CISCO-VTP-MIB :: vtpVlanApplyStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VTP-MIBvtpVlanApplyStatus

vtpVlanApplyStatus

Module: CISCO-VTP-MIB

OID (symbolic): CISCO-VTP-MIB::vtpVlanApplyStatus

OID (numeric): 1.3.6.1.4.1.9.9.46.1.4.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The current status of an 'apply' operation to instanciate the Edit Buffer as the new global VLAN information (for this management domain). If no apply is currently active, the status represented is that of the most recently completed apply. The possible values are:

inProgress - 'apply' operation in progress;

succeeded - the 'apply' was successful (this value is also used when no apply has been invoked since the last time the local system restarted);

configNumberError - the apply failed because the value of vtpVlanEditConfigRevNumber was less or equal to the value of current value of managementDomainConfigRevNumber;

inconsistentEdit - the apply failed because the modified information was not self-consistent;

tooBig - the apply failed because the modified information was too large to fit in this VTP Server's non-volatile storage location;

localNVStoreFail - the apply failed in trying to store the new information in a local non-volatile storage location;

remoteNVStoreFail - the apply failed in trying to store the new information in a remote non-volatile storage location;

editBufferEmpty - the apply failed because the Edit Buffer was empty (for this management domain).

someOtherError - the apply failed for some other reason (e.g., insufficient memory).

notPrimaryServer - the apply failed because the local device is not a VTP primary server for VLAN database type when managementDomainVersionInUse is version3(4).

What is vtpVlanApplyStatus?

This read-only INTEGER reports the outcome of the most recent (or currently running) apply operation that commits the VTP VLAN edit buffer as the new global VLAN configuration, distinguishing states like inProgress, succeeded, configNumberError, and inconsistentEdit. An administrator checks this after triggering vtpVlanEditOperation's apply to confirm whether the staged VLAN changes actually took effect or failed, and why. For example, a status of configNumberError after an apply attempt tells the admin the configuration revision number needs adjusting, likely via vtpVlanEditConfigRevNumber, before retrying.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.46.1.4.1.1.2
snmpwalk -v2c -c public <target> CISCO-VTP-MIB::vtpVlanApplyStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.46.1.4.1.1.2.1
snmpget -v2c -c public <target> CISCO-VTP-MIB::vtpVlanApplyStatus.1

Start monitoring Cisco Catalyst switches (VLAN Trunking Protocol) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VTP-MIB::vtpVlanApplyStatus OID value, configure state conditions and alerts, and monitor any Cisco Catalyst switches (VLAN Trunking Protocol) from a single console.

OID Breakdown

Upper-level ancestors (8 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.46ciscoVtpMIBCISCO-VTP-MIB
1.3.6.1.4.1.9.9.46.1vtpMIBObjectsCISCO-VTP-MIB
1.3.6.1.4.1.9.9.46.1.4vlanEditCISCO-VTP-MIB
1.3.6.1.4.1.9.9.46.1.4.1vtpEditControlTableCISCO-VTP-MIB
1.3.6.1.4.1.9.9.46.1.4.1.1vtpEditControlEntryCISCO-VTP-MIB
1.3.6.1.4.1.9.9.46.1.4.1.1.2vtpVlanApplyStatusCISCO-VTP-MIB