ASCEND-ATMP-MIB :: atmpAgentForceFragmentation

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ASCEND-ATMP-MIB › atmpAgentForceFragmentation

atmpAgentForceFragmentation

Module: ASCEND-ATMP-MIB

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

OID (numeric): 1.3.6.1.4.1.529.24.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: To force fragmentation of large IP frames before they are sent to the peer agent even if the packet has the DF bit set. NOTE: this behavior is not standard and prevents MTU discovery mechanisms. This works in conjunction with atmpAgentGreMtu.

What is atmpAgentForceFragmentation?

This flag forces fragmentation of large IP packets before sending to peer agents, even if DF bit is set. Enabled (1) ensures delivery but prevents MTU discovery; disabled (2) allows MTU discovery.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.529.24.5
snmpwalk -v2c -c public <target> ASCEND-ATMP-MIB::atmpAgentForceFragmentation

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.529.24.5.1
snmpget -v2c -c public <target> ASCEND-ATMP-MIB::atmpAgentForceFragmentation.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::atmpAgentForceFragmentation 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.5atmpAgentForceFragmentationASCEND-ATMP-MIB