Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
well your best bet is normally to divide the problem in to two, in order to see if it's a cacti issue or a windows issue. use a mib browser, any will do on either windows or linux, and just manually query the device. you'll then be able to see if windows snmp is responding correctly for what you want to be able to obtain. under linux you should already have snmpwalk installed, so try "snmpwalk -v2c -ccacti 184.108.40.206" where 220.127.116.11 is the windows box and cacti is the community name. if that starts spewing out snmp oids then you're fine from the windows side. often you can have issues in terms of versions of snmp in use. v3 is still rare (and complicated) but v1 and v2c are standard and simple to configure. check you can successfully walk with both versions, that can often be a point of difference.
I'll see where the configuration problems are. Excellent information you shared. Honestly "ebarrasingly", I hadn't heard of the MIB browser.
I do know that I have SNMPwalk v2 installed on my linux box. It was one of the path requirments needed when I began the install process through the administration panel. I had to use yum to find the location for its "i believe" binary files. Once found, I corrected the path.
I've disabled the firewall but nothing yet. The only difference is that I'm on wireless. I'm not to sure if this makes a difference. Lastly, should community name be the same as a domain or workgroup? or does this really matter?
well many wireless adsl routers enable some forms of firewalled seperation incase the wireless is compromised, but i'd expect that to cover pings too. and no the community name is irrelevant, just as long as it's the same... it's just a nominal password-like string, (why would you think that an open standard had to relate to a M$ proprietary concept??)
yes, it's called tshark. wireshark comes normally in two packages, wireshark and wireshark-gnome. with just wireshark installed, you don't need X, and only have the tshark command to run in a console. the wireshark-gnome adds the actual wireshark program itself.
I tried using tshark on the cacti server with the following commands:
tshark -n -i eth0 -x port 161
tshark -n -i eth1 -x port 161
both came up with the same error:
tshark: the capture session could not be initiated (ioctl: No such device).
I did this command through putty and as root.
I also changed the settings on my windows clients to remove cacti from security but nothing. Any other ideas? Would definitely be nice to get this system going. I've been taking my time at this... as you may note the slow responses by the dates of my posts
I know eth0 shows that it has a fixed IP address as shown in ifconfig. I setup the server with a static ipaddress and it is able to receive updates when I need. I've also started the service snmpd... not to sure if this makes a difference