SNMPD.INTERNAL(5)

📦
version 5.9.5.2 · 8 versions
, in alpine 3.23, alpine 3.24, arch rolling, fedora 44

✨ SNMPD.INTERNAL(5) ✨ — the Net-SNMP internal tea ☕

okay so bestie, this is the manual for snmpd.internal, the internal configuration of the Net-SNMP agent, and ngl it's giving backstage-pass energy 🎀

💖 NAME 💖

snmpd.internal — internal configuration of the Net-SNMP agent, fr fr

🦋 DESCRIPTION 🦋

So like, the snmpd.conf(5) man page is the main character here — it defines the syntax and behaviour of the main configuration directives you use to control how the Net-SNMP agent operates, plus all the management information it hands out. Periodt. 👑

But — and this is the plot twist 🫢 — there are several other configuration directives floating around that the agent also recognises. Many of them (though not all, bestie, not all) start with a leading underscore. These are typically used to retain configuration across agent restarts, and they are not intended for direct user access. They're the behind-the-scenes girlies.

This man page lists these directives, giving a brief lil indication of where they're used. For full details — go read the relevant source files. 📚

If you can't follow that source, you probably shouldn't be fiddling with these directives! 💀 Like, genuinely. Read the source or leave it alone.

🌸 AGENT BEHAVIOUR 🌸

  • quit — yep, that's it. That's the directive. no notes. 💅

🎀 ACCESS CONTROL 🎀

🌈 VACM Configuration 🌈

  • vacmView / vacmGroup / vacmAccess — these directives are used to retain dynamically configured access control settings. Your VACM settings, saved for later, slay. ✨

⭐ SYSTEM INFORMATION ⭐

🧚 System Group 🧚

  • setSerialNo — this directive is used to implement the advisory lock object snmpSetSerialNo. Locking things down, iconic behaviour. 🔒
  • psyslocation / psyscontact / psysname — these directives are used to retain dynamically configured system settings. Heads up though: they will be overridden by the corresponding sysLocation, sysContact and sysName directives. So like, they're the understudy, not the lead. 😭

🔥 ACTIVE MONITORING 🔥

🍓 Notification Handling 🍓

  • pauthtrapenable — this directive is used to retain the dynamically configured setting of whether the agent should generate authenticationFailure traps. And yes, it will be overridden by the corresponding authtrapenable directive. same energy as above, bestie. 🙈
  • snmpNotify*Table — literally just vibes and a wildcard, that's all the page says. 👀
  • targetAddr / targetParams — these directives are used to retain dynamically configured notification destination settings. Where the notifications go, lowkey important. 📬

💜 DisMan Event MIB 💜

  • _mteE*Table, _mteOTable, _mteT*Table — these directives are used to retain dynamically configured event, object and monitor trigger settings. Look at all those tables go. ✨
  • mteObjectsTable / mteTriggerTable — these directives are for compatibility with the previous disman/event-mib implementation. Nostalgia core, honestly. 🫶

🌈 DisMan Schedule MIB 🌈

  • _schedTable — this directive is used to retain dynamically configured scheduled events. Scheduling queen. 📅

👑 EXTENDING AGENT FUNCTIONALITY 👑

💅 Arbitrary Extension Commands 💅

  • extend-sh — that's the whole description. Short. Punchy. Mysterious. 🎀
  • exec2 / sh2 / execFix2 — these directives were defined by analogy with equivalent directives in the previous ucd-snmp/extensible implementation. They are deprecated, and should not be used. 🚫 Like, don't. This is your sign. 💀

🎀 FILES 🎀

  • /etc/snmp/snmpd.conf

🦋 SEE ALSO 🦋

and that's the whole page, bestie 💖 this was Net-SNMP, version V5.9.5.2, dated 06 Dec 2005 — yes the date is ancient, she's a vintage icon and we respect her 👑✨ mwah, go read the source 💅🫶

📦 where this page comes from