06-06-2000 04:46 PM
# snmpnext MYHOST system.sysObjectID
snmpnext: No response arrived before timeout.
snmpnext: Possible causes include invalid community name, agent is not running, or the node is unaccessible.
# snmpget 127.0.0.1 system.sysDescr.0
snmpget: No response arrived before timeout.
snmpget: Possible causes include invalid community name, agent is not running, or the node is unaccessible.
I?m sure the snmpd is running, several times I reinitiates the snmpd, and the messages are the same.
the file snmpd.conf only have a line:
Solved! Go to Solution.
06-07-2000 06:04 AM
Which snmpd is actually running? Sun's default daemon is called snmpdx and the one provided with NNM is snmpdm. Each may have it's own snmpd.conf file floating around in /etc. Sun's is usually in /etc/snmp/conf while the NNM agent is usually /etc/snmp.conf. Make sure you have the right agent running and you're looking at the correct snmpd.conf file for it.
06-07-2000 06:28 PM
But the problem changes, whit the NNM snmp agent running the ovstart doesn?t work is like idle, and the NNM can?t connect to the agent, it is the same problem I expose yesterday.
Finally I found a way to run the ovstart, I need to kill the process of the NNM snmp, initiates the Solaris snmpdx, reinitiates the NNM snmpd, and then run the ovstart. Other way ovstart doesn?t work property.
Maybe I need a patch for either Solaris or NNM , an other ideas?
PD thank for the Help Davide, Antonio and Rich
06-08-2000 05:39 AM
As far as patches go, the latest NNM on Solaris patches for 5.01 are PSOV_02468, PSOV_02707, and PSOV_02732. 02468 is the really important one. These are available at http://ovweb.external.hp.com:80/cpe/patches/nnm/5.
You can use patchdiag to check the Solaris patches. Be sure to go to Sun site to get the latest patchdiag info.