SNMPGET(1)

💖 SNMPGET(1) — the Net-SNMP girlie's guide to GET requests 💖

okay so bestie, welcome to snmpget, section 1 of the Net-SNMP manuals 🎀 this is the tool that communicates with a network entity using SNMP GET requests. yes it's giving main character energy. yes you're gonna slay.

---

✨ NAME ✨

snmpget — communicates with a network entity using SNMP GET requests 🦋

---

🌸 SYNOPSIS 🌸

snmpget [COMMON OPTIONS] [-Cf] AGENT OID [OID]...

---

💅 DESCRIPTION 💅

So snmpget is an SNMP application that uses the SNMP GET request to go query for information on a network entity. literally that's the whole job. it ate.

One or more object identifiers (OIDs) may be given as arguments on the command line. Each variable name is given in the format specified in variables(5) — so if you're confused about the format, that's your girl, go read her.

---

👑 OPTIONS 👑

• -Cf — okay so here's the tea 🍵 if -Cf is not specified, some applications (snmpdelta, snmpget, snmpgetnext and snmpstatus) will try to fix errors returned by the agent that you were talking to and resend the request. the only time this is really useful is if you specified a OID that didn't exist in your request and you're using SNMPv1, which requires "all or nothing" kinds of requests. SNMPv1 is highkey dramatic like that 😭

In addition to this option, snmpget takes the common options described in the snmpcmd(1) manual page. and note: snmpget REQUIRES an argument specifying the agent to query and at least one OID argument, as described there. no agent, no OID, no vibes. periodt. 💀

---

🍓 EXAMPLES 🍓

The command:

snmpget -c public zeus system.sysDescr.0

will retrieve the variable system.sysDescr.0 from the host zeus using the community string public :

system.sysDescr.0 = "SunOS zeus.net.cmu.edu 4.1.3_U1 1 sun4m"

iconic. we love a successful GET 🫶

If the network entity has an error processing the request packet, an error packet will be returned and a message will be shown, helping to pinpoint in what way the request was malformed. If there were other variables in the request, the request will be resent without the bad variable. so it just quietly drops the problem child and moves on, we've all been there 🙈

Here is another example. The -c and -v options are defined in the snmpcmd(1) manual page. (Note that system.sysUpTime is an incomplete OID, as it needs the .0 index appended to it — bestie the index is not optional, it's the whole personality ✨):

snmpget -v1 -Cf -c public localhost system.sysUpTime system.sysContact.0

This example will return the following:

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
This name doesn't exist: system.sysUpTime

Similarly, the command:

snmpget -v1 -c public localhost system.sysUpTime system.sysContact.0

Will return:

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
This name doesn't exist: system.sysUpTime

system.sysContact.0 = STRING: root@localhost

see how the second one still pulled system.sysContact.0 even though system.sysUpTime was a whole mess? that's the error-fixing behaviour doing its thing 💫

With the -Cf flag specified the application will not try to fix the PDU for you. you're on your own, girlboss. own it. 💅

---

🌈 SEE ALSO 🌈

snmpcmd(1), snmpwalk(1), variables(5).

---

okay that's the whole page, no notes 💜 go forth and GET responsibly

mwah 💋 this was Net-SNMP version V5.9.5.2, dated 18 Jun 2007, and yes she's still serving SNMPGET(1) realness all these years later 👑✨