ATM-FORUM-M4-MIB :: atmfM4VcUpcNpcCurrSuspect

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsATM-FORUM-M4-MIBatmfM4VcUpcNpcCurrSuspect

atmfM4VcUpcNpcCurrSuspect

Module: ATM-FORUM-M4-MIB

OID (symbolic): ATM-FORUM-M4-MIB::atmfM4VcUpcNpcCurrSuspect

OID (numeric): 1.3.6.1.4.1.353.100.1.22.1.1

Node type: OBJECT-TYPE

Type: TruthValue

Access: read-only

Description: If true, the statistics in this entry may be unreliable.

What is atmfM4VcUpcNpcCurrSuspect?

Indicates whether the current-interval UPC/NPC statistics for a virtual channel may be unreliable or inaccurate. If this flag is true, the collected performance measurements should be treated with caution.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.353.100.1.22.1.1
snmpwalk -v2c -c public <target> ATM-FORUM-M4-MIB::atmfM4VcUpcNpcCurrSuspect

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.353.100.1.22.1.1.1
snmpget -v2c -c public <target> ATM-FORUM-M4-MIB::atmfM4VcUpcNpcCurrSuspect.1

Start monitoring ATM switches and network elements (M4 interface) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ATM-FORUM-M4-MIB::atmfM4VcUpcNpcCurrSuspect OID value, configure state conditions and alerts, and monitor any ATM switches and network elements (M4 interface) from a single console.

OID Breakdown

Upper-level ancestors (7 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.353atmForumATM-FORUM-ILMI40-MIB
Numeric OIDNameModule
1.3.6.1.4.1.353.100atmfM4MIBATM-FORUM-M4-MIB
1.3.6.1.4.1.353.100.1atmfM4MIBObjectsATM-FORUM-M4-MIB
1.3.6.1.4.1.353.100.1.22atmfM4VcUpcNpcCurrTableATM-FORUM-M4-MIB
1.3.6.1.4.1.353.100.1.22.1atmfM4VcUpcNpcCurrEntryATM-FORUM-M4-MIB
1.3.6.1.4.1.353.100.1.22.1.1atmfM4VcUpcNpcCurrSuspectATM-FORUM-M4-MIB