SFLOW-MIB :: sFlowMaximumHeaderSize

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SFLOW-MIB › sFlowMaximumHeaderSize

sFlowMaximumHeaderSize

Module: SFLOW-MIB

OID (symbolic): SFLOW-MIB::sFlowMaximumHeaderSize

OID (numeric): 1.3.6.1.4.1.4300.1.1.4.1.6

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

Description: The maximum number of bytes that should be copied from a sampled packet. The agent may have an internal maximum and minimum permissible sizes. If an attempt is made to set this value outside the permissible range then the agent should adjust the value to the closest permissible value.

What is sFlowMaximumHeaderSize?

This read-write value sets the maximum number of bytes copied from each sampled packet, defaulting to 128, with the agent adjusting out-of-range requests to its nearest supported value. Admins raise or lower it to trade off between capturing enough packet header detail (e.g. VLAN tags, deeper protocol headers) and the bandwidth/storage cost of larger sFlow datagrams. For example, an admin increases sFlowMaximumHeaderSize to 256 to make sure MPLS or QinQ-tagged headers are fully captured in each sample.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4300.1.1.4.1.6
snmpwalk -v2c -c public <target> SFLOW-MIB::sFlowMaximumHeaderSize

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4300.1.1.4.1.6.1
snmpget -v2c -c public <target> SFLOW-MIB::sFlowMaximumHeaderSize.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.4300.1.1.4.1.6.1 i <value>

Start monitoring network switch or router with sFlow support, vendor-neutral standards-based MIB (sFlow.org) (sampling agent configuration) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SFLOW-MIB::sFlowMaximumHeaderSize OID value, configure state conditions and alerts, and monitor any network switch or router with sFlow support, vendor-neutral standards-based MIB (sFlow.org) (sampling agent configuration) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.4300.1sFlowMIBSFLOW-MIB
1.3.6.1.4.1.4300.1.1sFlowAgentSFLOW-MIB
1.3.6.1.4.1.4300.1.1.4sFlowTableSFLOW-MIB
1.3.6.1.4.1.4300.1.1.4.1sFlowEntrySFLOW-MIB
1.3.6.1.4.1.4300.1.1.4.1.6sFlowMaximumHeaderSizeSFLOW-MIB