User`s guide

4. Create an snmpCol.conf file.
Issue this command:
/tmp/csgmkcnf
5. Back up the existing /usr/OV/conf/snmpCol.conf file.
The existing
snmpCol.conf
file contains your current collection configuration. (If you made any modifications in the
configuration, see Section 1, Task 3: Create a Test PDB and Process, Reduce, and Report on Your Data
, the changes that
you made are included in this file. In this step you will save those changes but not use them.)
Issue this command:
cd /usr/OV/conf
cp -p snmpCol.conf snmpCol.conf.orig
6. During the following actions, monitor the contents of the snmpCollect trace file.
Messages are appended to the
snmpCollect
trace file as data collection takes place. The best way to monitor these
messages is with the following steps:
a. Open a new xterm window.
b.
c. Issue these commands in the new window:
cd /usr/OV/log
tail -f snmpCol.trace
Messages will be displayed as they are appended to the trace file.
7. Begin logging data using the new snmpCol.conf file.
a.
b. To stop the snmpCollect daemon, issue this command:
/usr/OV/bin/ovstop snmpCollect
c. To copy your config file over the existing config file, issue this command:
cp /tmp/snmpCol.conf /usr/OV/conf/snmpCol.conf
d. To restart the snmpCollect daemon, issue this command:
/usr/OV/bin/ovstart snmpCollect
Note: If at any time you want to return to using your former configuration, repeat this action except issue this command
as the copy command:
cp -p /usr/OV/conf/snmpCol.conf.orig /user/OV/conf/snmpCol.conf
8. Watch the trace file as snmpCollect runs.
You may see a message that looks like this:
Wed Aug 16 11:30:19 1995 : Next object after ipRoutingDiscards
(.1.3.6.1.2.1.4.23) is not supported by agent on dimes.unx.sas.com.
Use snmpwalk or MIB browser to verify the object exists on this node
In this example, the message indicates that snmpCollect will not be able to collect ipRoutingDiscards