version 2 showing authors affecting page license.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
SNMPWALK |
|
|
2 |
!!!SNMPWALK |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
SEE ALSO |
|
|
8 |
---- |
|
|
9 |
!!NAME |
|
|
10 |
|
|
|
11 |
|
|
|
12 |
snmpwalk - communicates with a network entity using SNMP GET Next Requests. |
|
|
13 |
!!SYNOPSIS |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
snmpwalk [[common arguments] [[-C APPOPTS] |
|
|
17 |
[[objectID] |
|
|
18 |
!!DESCRIPTION |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
Snmpwalk is an SNMP application that uses GET NEXT Requests |
|
|
22 |
to query for a tree of information about a network |
|
|
23 |
entity. |
|
|
24 |
|
|
|
25 |
|
|
|
26 |
A variable may also be given on the command line. This |
|
|
27 |
variable specifies which portion of the object identifier |
|
|
28 |
space will be searched using GET NEXT Requests. All |
|
|
29 |
variables in the subtree below the given variable are |
|
|
30 |
queried and their values presented to the user. Each |
|
|
31 |
variable name is given in the format specified in |
|
|
32 |
variables(5). |
|
|
33 |
|
|
|
34 |
|
|
|
35 |
If the |
|
|
36 |
|
|
|
37 |
|
|
|
38 |
For example |
|
|
39 |
|
|
|
40 |
|
|
|
41 |
''snmpwalk zeus public system'' |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
will retrieve all of the variables under |
|
|
45 |
system: |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
''system.sysDescr.0 ='' |
|
|
49 |
'' |
|
|
50 |
system.sysObjectID.0 = OID: |
|
|
51 |
enterprises.hp.nm.hpsystem.10.1.1 |
|
|
52 |
system.sysUpTime.0 = Timeticks: (155274552) 17 days, |
|
|
53 |
23:19:05 |
|
|
54 |
system.sysContact.0 ='' '' |
|
|
55 |
system.sysName.0 ='' '' |
|
|
56 |
system.sysLocation.0 ='' '' |
|
|
57 |
system.sysServices.0 = 72'' |
|
|
58 |
|
|
|
59 |
|
|
|
60 |
If the network entity has an error processing the request |
|
|
61 |
packet, an error packet will be returned and a message will |
|
|
62 |
be shown, helping to pinpoint why the request was |
|
|
63 |
malformed. |
|
|
64 |
|
|
|
65 |
|
|
|
66 |
If the tree search causes attempts to search beyond the end |
|
|
67 |
of the MIB, a message will be displayed: |
|
|
68 |
|
|
|
69 |
|
|
|
70 |
''End of MIB.'' |
|
|
71 |
!!OPTIONS |
|
|
72 |
|
|
|
73 |
|
|
|
74 |
In addition to the arguments defined in the snmpcmd(1) |
|
|
75 |
manual page, the following options are supported as |
|
|
76 |
well: |
|
|
77 |
|
|
|
78 |
|
|
|
79 |
-Ci |
|
|
80 |
|
|
|
81 |
|
|
|
82 |
Includes the requested oid in the search range. Normally |
|
|
83 |
snmpwalk uses getnexts starting with the oid you request and |
|
|
84 |
returns all results in the MIB tree below the one you |
|
|
85 |
requested. Sometimes, you may wish to include the OID |
|
|
86 |
specified on the command line in the printed results if it |
|
|
87 |
is a valid OID in the tree itself. This option lets you do |
|
|
88 |
this. |
|
|
89 |
|
|
|
90 |
|
|
|
91 |
-Cp |
|
|
92 |
|
|
|
93 |
|
|
|
94 |
Upon completion, snmpwalk will print the number of variables |
|
|
95 |
found during the walk. |
|
|
96 |
|
|
|
97 |
|
|
|
98 |
-Cc |
|
|
99 |
|
|
|
100 |
|
|
|
101 |
Don't Check whether the returned OID's are increasing. Some |
|
|
102 |
agents (!LaserJets are an example) returns OID's out of |
|
|
103 |
order, but can complete the walk anyway. Other agent's |
|
|
104 |
return OIDs that are out of order and can cause snmpwalk to |
|
|
105 |
loop infinitely until stopped. By default, snmpwalk tries to |
|
|
106 |
detect this behavior and warns you when it hits an agent |
|
|
107 |
acting illegally. Use -Cc to turn off this |
|
|
108 |
behavior. |
|
|
109 |
!!SEE ALSO |
|
|
110 |
|
|
|
111 |
|
|
|
112 |
snmpcmd(1), variables(5). |
|
|
113 |
---- |