ASCEND-ATMP-MIB :: atmpPktsForcedToFragment

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ASCEND-ATMP-MIB › atmpPktsForcedToFragment

atmpPktsForcedToFragment

Module: ASCEND-ATMP-MIB

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

OID (numeric): 1.3.6.1.4.1.529.24.16.1.24

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: The number of packets forced to pre-fragment despite the DF bit. Not valid for tunnels in local client mode.

What is atmpPktsForcedToFragment?

This counter tracks packets forced to fragment due to MTU settings despite DF bit. Shows impact of MTU configuration. 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.24
snmpwalk -v2c -c public <target> ASCEND-ATMP-MIB::atmpPktsForcedToFragment

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.529.24.16.1.24.1
snmpget -v2c -c public <target> ASCEND-ATMP-MIB::atmpPktsForcedToFragment.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::atmpPktsForcedToFragment 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.24atmpPktsForcedToFragmentASCEND-ATMP-MIB