FoundryNet / Error codes / SNMP tooBig
SNMP error code

tooBig (1) — error-status 1 — response would not fit

The agent's reply exceeds what it can encode in one PDU, usually because the request asked for too many variables at once.

Start free All protocols

Diagnosis

When you hit this


Resolution

How to fix it

  1. Lower max-repetitions
    Reduce it until the response fits. Ten to twenty is safe on most embedded agents.
  2. Split the request
    Several small GETs are more reliable than one large one, especially against industrial gear.

Normalization

What Forge does about it

A request that fails on some points and succeeds on others still normalizes. The tags that arrived resolve to canonical fields as usual; the ones that did not come back are listed in unresolved_tags and excluded from coverage_pct, so a partial read reports as partial instead of quietly looking complete.


Connect

Normalize SNMP telemetry

One MCP endpoint serves every protocol adapter. 16,908 curated mappings, 366 canonical fields.

# normalize telemetry from SNMP — and 13 other protocols
claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \
  --header 'Authorization: Bearer YOUR_FORGE_KEY'
✓ forge connected — 32 tools available

Related

Keep reading

Other SNMP codes: noSuchName genErr authorizationError

Other protocols: Modbus OPC UA MQTT / Sparkplug B FANUC FOCAS EtherNet/IP PROFINET / S7 BACnet/IP J1939 (CAN) MTConnect ROS 2 (DDS) MAVLink HTTP / REST CSV ingest

All error codes · All OEMs · All protocols

Industrial AI fails at the data layer. The Machine Agent explains why, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.