CISCO-WAN-AXIPOP-MIB :: frChanCnfChangeCount

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBfrChanCnfChangeCount

frChanCnfChangeCount

Module: CISCO-WAN-AXIPOP-MIB

OID (symbolic): CISCO-WAN-AXIPOP-MIB::frChanCnfChangeCount

OID (numeric): 1.3.6.1.4.1.351.110.5.1.2.1.1.1.64

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: This object is added only for FRSM12 card.

This counter tracks the number of configuration changes that happen on a channel. The counter is associated only with the end point and NOT with the connection itself.

This counter is used by the NMS to determine if a connection configuration had been modified and requires an upload. This functionality is conventionally achieved by time stamping using a time-of-day clock. However, in switches where time-of-day clock is not available, the following scheme is used:

The upload counter is incremented, when:

* assignment of connection to an end point channel. This happens when a connection is added and assigned this channel number. * de-assignment of connection from a channel number. This happens when a connection is deleted and the end point resource is released. * When there is a configuration change done to the connection that is associated with this end point channel number.

In a new system, an unutilised resouce (channel number) has a counter value of zero. When a connection is added to this channel end point, the counter is incremented. And is incremented for any of the above operations. When a connection is deleted the value of this counter is incremented and preserved till a new connection gets associated with this channel end point.

This object is not applicable to MGX Release 1.x.

What is frChanCnfChangeCount?

This read-only Counter, added specifically for the FRSM12 card, tracks the number of configuration changes made to a channel end-point, tied to the end-point itself rather than to the connection as a whole. Network management systems poll this counter, instead of relying on time-of-day timestamps (which are not always available on the switch), to detect that a connection's configuration was modified and therefore needs to be re-uploaded. For example, an NMS periodically comparing its cached frChanCnfChangeCount value against the live counter on an FRSM12 channel would know to re-fetch that channel's configuration as soon as the two values diverge.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.2.1.1.1.64
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::frChanCnfChangeCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.2.1.1.1.64.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::frChanCnfChangeCount.1

Start monitoring Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-AXIPOP-MIB::frChanCnfChangeCount OID value, configure state conditions and alerts, and monitor any Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) from a single console.

OID Breakdown

Upper-level ancestors (11 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.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.1frameRelayBASIS-MIB
1.3.6.1.4.1.351.110.5.1.2frChanBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.1.2.1frChanCnfGrpCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.1.2.1.1frChanCnfGrpTableCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.1.2.1.1.1frChanCnfGrpEntryCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.1.2.1.1.1.64frChanCnfChangeCountCISCO-WAN-AXIPOP-MIB