Neither snmpwalk nor snmpbulkwalk are snmp protocol requests: only
successive getnext requests are able to walk thru a mib tree.
I already knew "snmpwalk" commands, sometimes called "snmpmany",
which perform these successive getnext requests, but I never
heard of "snmpbulkwalk". Can you explain what it is ?
--
o You can send me any ISO-8859-1 character, and attached documents such
as GIF or JPEG images, but *please* don't send me: HTML e-mails, or
Microsoft files such as Winword documents or Windows executables !
o Le meilleur produit du monde : http://www.openmaster.com
In article <362F3F82...@bull.net>, Olivier Miakinen
snmpbulkwalk (as the name implies) usually uses v2(c) GETBULK requests,
and as such will not be applicable to SNMP v1.
/Niels
--
Niels Baggesen, UNI-C, Olof Palmes Alle 38, DK-8200 Aarhus N, Denmark
Email: Niels.B...@uni-c.dk Tel: +45 89 37 66 69 Fax: +45 89 37 66 77
--- Never underestimate the bandwidth of a CD flying through the lab ---
nimms-noisespam@megsinet> snmpbulkwalk, from what I understand
nimms-noisespam@megsinet> executes snmpgetnext requests in order to
nimms-noisespam@megsinet> walk the mib table for OID's.
No, snmpbulkwalk uses a "getbulk" command which tells the agent to
return more than one variable for a single request. The biggest
user-level difference between snmpwalk and snmpbulkwalk is that
snmpbulkwalk uses less packets (by cramming more information into one
packet).
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."