version 1 showing authors affecting page license.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
SNMPGET |
|
|
2 |
!!!SNMPGET |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
NEAT TRICKS |
|
|
8 |
NOTES |
|
|
9 |
---- |
|
|
10 |
!!NAME |
|
|
11 |
|
|
|
12 |
|
|
|
13 |
snmpconf - creates and modifies snmp configuration files |
|
|
14 |
!!SYNOPSIS |
|
|
15 |
|
|
|
16 |
|
|
|
17 |
snmpconf [[options] [[fileToCreate] |
|
|
18 |
|
|
|
19 |
|
|
|
20 |
Start with: |
|
|
21 |
|
|
|
22 |
|
|
|
23 |
snmpconf -g basic_setup |
|
|
24 |
|
|
|
25 |
|
|
|
26 |
Or even just: |
|
|
27 |
|
|
|
28 |
|
|
|
29 |
snmpconf |
|
|
30 |
!!DESCRIPTION |
|
|
31 |
|
|
|
32 |
|
|
|
33 |
snmpconf is a simple perl script that walks you through |
|
|
34 |
setting up a configuration file step by step. It should be |
|
|
35 |
fairly straight forward to use. Merely run it and answer its |
|
|
36 |
questions. |
|
|
37 |
|
|
|
38 |
|
|
|
39 |
In its default mode of operation, it prompts the user with |
|
|
40 |
menus showing sections of the various configuration files it |
|
|
41 |
knows about. When the user selects a section, a sub-menu is |
|
|
42 |
shown listing of the descriptions of the tokens that can be |
|
|
43 |
created in that section. When a description is selected, the |
|
|
44 |
user is prompted with questions that construct the |
|
|
45 |
configuration line in question. |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
Finally, when the user quits the program any configuration |
|
|
49 |
files that have been edited by the user are saved to the |
|
|
50 |
local directory, fully commented. |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
A particularly useful option is the -g switch, which walks a |
|
|
54 |
user through a specific set of configuration questions. Run |
|
|
55 |
__snmpconf -g basic_setup__ for an example. |
|
|
56 |
!!OPTIONS |
|
|
57 |
|
|
|
58 |
|
|
|
59 |
-f |
|
|
60 |
|
|
|
61 |
|
|
|
62 |
Force overwriting existing files in the current directory |
|
|
63 |
without prompting the user if this is a desired thing to |
|
|
64 |
do. |
|
|
65 |
|
|
|
66 |
|
|
|
67 |
-i |
|
|
68 |
|
|
|
69 |
|
|
|
70 |
When finished, install the files into the location where the |
|
|
71 |
global system commands expect to find them. |
|
|
72 |
|
|
|
73 |
|
|
|
74 |
-p |
|
|
75 |
|
|
|
76 |
|
|
|
77 |
When finished, install the files into the users home |
|
|
78 |
directory's .snmp subdirectory (where the applications will |
|
|
79 |
also search for configuration files). |
|
|
80 |
|
|
|
81 |
|
|
|
82 |
-I DIRECTORY |
|
|
83 |
|
|
|
84 |
|
|
|
85 |
When finished, install the files into the directory |
|
|
86 |
DIRECTORY. |
|
|
87 |
|
|
|
88 |
|
|
|
89 |
-a |
|
|
90 |
|
|
|
91 |
|
|
|
92 |
Don't ask any questions. Simply read in the various known |
|
|
93 |
configuration files and write them back out again. This has |
|
|
94 |
the effect of |
|
|
95 |
neat tricks'' section |
|
|
96 |
below. |
|
|
97 |
|
|
|
98 |
|
|
|
99 |
-r all|none |
|
|
100 |
|
|
|
101 |
|
|
|
102 |
Read in either all or none of the found configuration files. |
|
|
103 |
Normally snmpconf prompts you for which files you wish to |
|
|
104 |
read in. Reading in these configuration files will merge |
|
|
105 |
these files with the results of the questions that it asks |
|
|
106 |
of you. |
|
|
107 |
|
|
|
108 |
|
|
|
109 |
-R file,... |
|
|
110 |
|
|
|
111 |
|
|
|
112 |
Read in a specific list of configuration files. |
|
|
113 |
|
|
|
114 |
|
|
|
115 |
-g groupname |
|
|
116 |
|
|
|
117 |
|
|
|
118 |
Groups of configuration entries can be created that can be |
|
|
119 |
used to walk a user through a series of questions to create |
|
|
120 |
an initial configuration file. There are no menus to |
|
|
121 |
navigate, just a list of questions. Run __snmpconf -g |
|
|
122 |
basic_setup__ for a good example. |
|
|
123 |
|
|
|
124 |
|
|
|
125 |
-G |
|
|
126 |
|
|
|
127 |
|
|
|
128 |
List all the known groups |
|
|
129 |
|
|
|
130 |
|
|
|
131 |
-c configdir |
|
|
132 |
|
|
|
133 |
|
|
|
134 |
snmpconf uses a directory of configuration information to |
|
|
135 |
learn about the files and questions that it should be |
|
|
136 |
asking. This option tells snmpconf to use a different |
|
|
137 |
location for configuring itself. |
|
|
138 |
|
|
|
139 |
|
|
|
140 |
-q |
|
|
141 |
|
|
|
142 |
|
|
|
143 |
Run slightly more quietly. Since this is an interactive |
|
|
144 |
program, I don't recommend this option since it only removes |
|
|
145 |
information from the output that is designed to help |
|
|
146 |
you. |
|
|
147 |
|
|
|
148 |
|
|
|
149 |
-d |
|
|
150 |
|
|
|
151 |
|
|
|
152 |
Turn on *lots* of debugging output. |
|
|
153 |
|
|
|
154 |
|
|
|
155 |
-D |
|
|
156 |
|
|
|
157 |
|
|
|
158 |
Add even more debugging output in the form of perl variable |
|
|
159 |
dumps. |
|
|
160 |
!!NEAT TRICKS |
|
|
161 |
|
|
|
162 |
|
|
|
163 |
snmpconf -g basic_setup |
|
|
164 |
|
|
|
165 |
|
|
|
166 |
Have I mentioned this command enough yet? It's designed to |
|
|
167 |
walk someone through an initial setup for the snmpd demon. |
|
|
168 |
Really, you should try it. |
|
|
169 |
|
|
|
170 |
|
|
|
171 |
snmpconf -R /usr/local/snmp/snmpd.conf -a -f |
|
|
172 |
snmpd.conf |
|
|
173 |
|
|
|
174 |
|
|
|
175 |
Automatically reads in a snmpd.conf file (for example) and |
|
|
176 |
adds comments to them describing what each token does. Try |
|
|
177 |
it. It's cool. |
|
|
178 |
!!NOTES |
|
|
179 |
|
|
|
180 |
|
|
|
181 |
snmpconf is actually a very generic utility that could be |
|
|
182 |
easily configured to help construct just about any kind of |
|
|
183 |
configuration file. Its default configuration set of files |
|
|
184 |
are snmp based. |
|
|
185 |
---- |