TUT:snmpgetnext - Revision history

Ileadu: /* Basic Example */

2013-05-30T09:42:44Z

‎Basic Example

2011-06-30T23:36:41Z

2010-05-08T19:29:15Z

Reverted edits by Russel08 (Talk); changed back to last version by Dts12

2010-05-07T03:14:23Z

2007-08-02T16:26:34Z

Consitent section headings

@@ Line 7: / Line 7: @@
      % snmpgetnext -v 2c -c demopublic test.net-snmp.org SNMPv2-MIB::sysUpTime.0
      SNMPv2-MIB::sysContact.0 = Wes Hardaker wjhardaker@ucdavis.edu
 At first sight, this might seem an odd thing to do, but it is actually extremely useful,

← Older revision		Revision as of 23:36, 30 June 2011
Line 1:		Line 1:
−	The other main SNMP operation for retrieving information is the GETNEXT request - a "fuzzy-matching" version of GET.	+	The other main SNMP operation for retrieving information is the [[GETNEXT]] request - a "fuzzy-matching" version of GET, and is implemented by the [[snmpgetnext]] tool.

	== Basic Example ==		== Basic Example ==

← Older revision		Revision as of 19:29, 8 May 2010
Line 144:		Line 144:

	{{TUT:LIST}}		{{TUT:LIST}}
−	~~==Related Links:==~~
−
−	~~[http://www.healthandmuscle.com/'''fat-burning-furnace-review''']~~

← Older revision		Revision as of 03:14, 7 May 2010
Line 144:		Line 144:

	{{TUT:LIST}}		{{TUT:LIST}}
		+	==Related Links:==
		+
		+	[http://www.healthandmuscle.com/'''fat-burning-furnace-review''']

@@ Line 70: / Line 70: @@
-== Multiple Variables ==
+== Multiple Values ==
 Just as with [[TUT:snmpget|snmpget]], it's also possible to run a single GETNEXT request with several OIDs, and it will retrieve the next valid instance for each of these:
@@ Line 107: / Line 107: @@
-== Problems ==
+== Failed Requests ==
 If a GETNEXT request is given the very last valid instance (or an OID later than this), then the agent needs to indicate that there are no further values to retrieve.  With SNMPv1, this uses the same error as a GET request for a non-existant OID: