noSuchName (2) — error-status 2 — object does not exist

SNMPv1's response when a requested OID is not present on the agent. In v2c and v3 this is replaced by per-variable noSuchObject or noSuchInstance exceptions, which are more precise.

Start free All protocols

Diagnosis

When you hit this

Polling a MIB the device does not implement.
Requesting a table row instance that does not exist, such as an interface index that has been removed.
Using an enterprise MIB OID against a device from a different vendor.

Resolution

How to fix it

Walk before you get
An snmpwalk of the subtree shows exactly which OIDs exist. Guessing at instance suffixes is the usual cause.
Prefer v2c for clearer errors
v2c distinguishes noSuchObject from noSuchInstance, which tells you whether the MIB is missing or just that row.
Check the instance suffix
Scalar objects need a .0 suffix. Omitting it is a very common noSuchName.

Normalization

What Forge does about it

This is a configuration or addressing mistake on the wire, upstream of anything Forge sees. Where Forge helps is the step after you fix it: once the point returns data, its vendor tag name maps to a canonical field automatically, so you do not also have to hand-maintain a name table for every point you just re-addressed.