ASCEND-ATMP-MIB :: atmpPktsFailedFragment

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ASCEND-ATMP-MIB › atmpPktsFailedFragment

atmpPktsFailedFragment

Module: ASCEND-ATMP-MIB

OID (symbolic): ASCEND-ATMP-MIB::atmpPktsFailedFragment

OID (numeric): 1.3.6.1.4.1.529.24.16.1.25

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: The number of packets that required to be fragmented but were dropped because atmpAgentForceFragemtnation was disable and the DF bit was set. Not valid for tunnels in local client mode.

What is atmpPktsFailedFragment?

This counter tracks packets dropped because fragmentation was needed but disabled. Indicates MTU mismatch issues. Not valid for local client mode tunnels.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.529.24.16.1.25
snmpwalk -v2c -c public <target> ASCEND-ATMP-MIB::atmpPktsFailedFragment

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.529.24.16.1.25.1
snmpget -v2c -c public <target> ASCEND-ATMP-MIB::atmpPktsFailedFragment.1

Start monitoring Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ASCEND-ATMP-MIB::atmpPktsFailedFragment OID value, configure state conditions and alerts, and monitor any Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) 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.529ascendASCEND-MIB
1.3.6.1.4.1.529.24atmpGroupASCEND-MIB
Numeric OIDNameModule
1.3.6.1.4.1.529.24.16atmpTunnelTableASCEND-ATMP-MIB
1.3.6.1.4.1.529.24.16.1atmpTunnelEntryASCEND-ATMP-MIB
1.3.6.1.4.1.529.24.16.1.25atmpPktsFailedFragmentASCEND-ATMP-MIB