Rodolfo J. Paiz wrote: > At 11:09 10/14/2003, you wrote: >> Rodolfo, >> >> My MRTG Config file: ((Edited for my comm strings -- MYCOMMSTRING is >> substituted)) <snip> > > Thanks a lot, Brett. Using your config as a template I have been able > to get snmpd to stop reporting errors. Now it stops and starts > quietly, and "netstat -leanp" shows snmpd listening on 0.0.0.0:161 as > it should. However, issuing the test command "snmpget -v 1 localhost > COMMUNITY interfaces.ifNumber.0" results in an error of "Timeout: No > Response from localhost." > > I have also created a simple mrtg.cfg file based on your template > which I _think_ is correct. However, like the test snmpget command > running mrtg reports that no response was received. > > Although I didn't think that could be the problem, I have ruled out > firewall issues by temporarily clearing all rules and setting > policies to ACCEPT. But in testing again, same result. Of course port > 161 is not accessible from outside the box (only via the lo > interface), and port scans confirm that. > > Here is a copy of my /etc/snmpd/snmpd.conf: > > ------------------------------------------------ > com2sec local localhost COMMUNITY-1 > com2sec mynetwork aa.bb.cc.dd/29 COMMUNITY-2 > > # Note that I don't know what "v2c" or "v1" mean yet... have not > # found them in the documentation anywhere. Again, yet. > group MyRWGroup v2c local > group MyROGroup v1 mynetwork Based on your snmpget query above and looking at the sec.model setting for localhost... you need to be specifying a v2c type query (or change your query to the ip/community-2 address of this system for v1). i.e. snmpwalk -v2c -c COMMUNITY-1 localhost system ... snmpwalk -v1 -c COMMUNITY-2 hostname system ... snmpget -v2c -c COMMUNITY-1 localhost system.sysLocation.0 SNMPv2-MIB::sysLocation.0 = STRING: Linux RH-9.0 on AMD-K6/450, 196MB You might consider running a less restrictive snmpd until you get things figured out, try changing the sec.model section to any. i.e. group MyRWGroup any local group MyROGroup any mynetwork Now you can make a v1 or v2c type query. As for creating an initial mrtg config file... Try using the following command to get you started in the right direction: # cfgmaker COMMUNITY-1@localhost >mrtg.cfg Now edit mrtg.cfg to fit your needs, but be sure you do not edit the latter part of the Target entry. i.e. don't edit the 3:COMMUNITY-1@localhost: part shown in my example. Target[localhost_3]: 3:COMMUNITY-1@localhost: I typically change the localhost_3 part within the brackets to something a little more descriptive, like the hostname_interface number. FWIW: I have been using mrtg for years. Once you feel comfortable using mrtg/snmpget in a basic configuration, you can change mrtg to use rrdtool and display the mrtg graphs using routers.cgi. Routers.cgi is an incredible tool for displaying mrtg graphs. You can checkout routers.cgi at http://steveshipway.org/software Again, wait until you feel comfortable using mrtg/snmpget/snmpwalk in a basic configuration before trying rrdtool/routers.cgi Steve Cowles -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
