From: AdrianG <ago...@le...> - 2009-10-05 10:12:06
|
Hi Jeff, thank you for your response, here the answer to your question: "Up to date" means what version of Net-SNMP? NET-SNMP version: 5.4.1 on the NMS server (Dapper) and the node What architecture are node1 and node2? they are both x86_64 Do node1 or node2 have any filesystems that are 2GB or larger in size? their file system is ext3 Here an output of /etc/fstab for node2 proc /proc proc defaults 0 0 /dev/md0 / ext3 defaults,errors=remount-ro 0 1 /dev/sda1 /boot ext3 defaults 0 2 /dev/sdb1 /boot2 ext3 defaults 0 2 /dev/sda4 none swap sw 0 0 /dev/sdb4 none swap sw 0 0 /dev/md1 /opt ext3 defaults 0 2 Here an output of df -h for node2 Filesystem Size Used Avail Use% Mounted on /dev/md0 49G 3.9G 43G 9% / varrun 1.5G 72K 1.5G 1% /var/run varlock 1.5G 0 1.5G 0% /var/lock udev 1.5G 52K 1.5G 1% /dev devshm 1.5G 0 1.5G 0% /dev/shm /dev/sda1 92M 11M 77M 12% /boot /dev/sdb1 92M 5.6M 81M 7% /boot2 /dev/md1 412G 7.7G 384G 2% /opt Another interesting stuff maybe is for testing purposes I deleted snmp service on node2 and I did a scan, snmp didn't come back, so it means that something is preventing to test port 161, not only query snmp data.. What is annoying is I can test the port fine with the following command: nc -v -v -z -u node2 161 (I changed the host address for privacy reason) So it means that the internal opennms poller cannot successfully scan port 161 for that node even though nc command successfully reach it .. So it let me think there is something wrong with openns only, with the poller... I trust if I re-add the node, problem will be fixed, so again it let me think that the problem is internal to opennms.. Thank you again, Adrian -- View this message in context: http://n2.nabble.com/SNMP-Collection-Stopped-for-single-device-tp3729269p3767957.html Sent from the OpenNMS - discuss mailing list archive at Nabble.com. |