Printer-MIB :: prtGeneralConfigChanges

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsPrinter-MIBprtGeneralConfigChanges

prtGeneralConfigChanges

Module: Printer-MIB

OID (symbolic): Printer-MIB::prtGeneralConfigChanges

OID (numeric): 1.3.6.1.2.1.43.5.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Counts configuration changes within the printer. A configuration change is defined to be an action that results in a change to any MIB object other than those that reflect status or level, or those that act as counters or gauges. In addition, any action that results in a row being added or deleted from any table in the Printer MIB is considered a configuration change. Such changes will often affect the capability of the printer to service certain types of print jobs. Management applications may cache infrequently changed configuration information about sub units within the printer. This object should be incremented whenever the agent wishes to notify management applications that any cached configuration information for this device is to be considered 'stale'. At this point, the management application should flush any configuration information cached about this device and fetch

new configuration information.

The following are examples of actions that would cause the prtGeneralConfigChanges object to be incremented:

- Adding an output bin - Changing the media in a sensing input tray - Changing the value of prtInputMediaType

Note that the prtGeneralConfigChanges counter would not be incremented when an input tray is temporarily removed to load additional paper or when the level of an input device changes.

NOTE: The above description has been modified from RFC 1759 for clarification.

What is prtGeneralConfigChanges?

This read-only Counter32 increments each time the printer's configuration changes in a way that would make cached MIB data stale, such as a tray or bin being added or removed, media type being changed in a tray, or a row being added to any Printer MIB table. Monitoring tools poll this counter and, when it changes, know to re-fetch tray/bin/marker configuration instead of relying on cached values, e.g. detecting that a technician just added a new output bin.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.43.5.1.1.1
snmpwalk -v2c -c public <target> Printer-MIB::prtGeneralConfigChanges

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.43.5.1.1.1.1
snmpget -v2c -c public <target> Printer-MIB::prtGeneralConfigChanges.1

Start monitoring vendor-neutral, standards-based MIB, network-attached printers and MFPs from any vendor (RFC 3805) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Printer-MIB::prtGeneralConfigChanges OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, network-attached printers and MFPs from any vendor (RFC 3805) 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.43printmibPrinter-MIB
1.3.6.1.2.1.43.5prtGeneralPrinter-MIB
1.3.6.1.2.1.43.5.1prtGeneralTablePrinter-MIB
1.3.6.1.2.1.43.5.1.1prtGeneralEntryPrinter-MIB
1.3.6.1.2.1.43.5.1.1.1prtGeneralConfigChangesPrinter-MIB