Hi,
I have setup a linux agent and can detect it using SNMP ping type object but can not communicate when I change it to SMC host type. I've got this error "Please check host/agent and retry."
I'm using correct seed and port for snmp.
Any help is greatly appreciated.
TIA.
Same problem here with 3.6 server/console piece running on a Sun Sparc machine. I can monitor all sorts of sun servers with no problem,
I even tried the newest Linux agent from Halcyon's site... No avail..
The agent starts up fine on our RH Linux 2.4.21 server and netstat or lsof shows it bound to the correct port. The logs seem to be fine... I've ripped it out and reinstalled several times... domain-config.x seems to be built correctly...
Any ideas or stuff I can check?
Thanks
-RMB
For now since there are 2 Linux Agents (the Halcyon version and the SunMC 3.6 version), I have to make sure to ask which people are using :)
In general these are the things I have people check:
a) the Linux Agent process is actually running
b) double-check the /var/opt/SUNWsymon|PrimeAlert/cfg/domain-config.x file to make sure it's using the port you think it is
c) use netstat to confirm that port is in use
d) are you sure the seed is correct: reseed if you're not sure. If you can't remember, go reseed your SunMC Server as well
e) make a "SNMP Ping" type icon first and see if it reports up/down. That confirms SNMPv1 communication. If it works, try to change it to a regular Agent (which uses SNMPv2usec). If that fails, you definately have a seed/security issue
f) does the Agent have multiple interfaces/networks? The Agent will only generate a security key for one of them. If you're not sure which network it's using, edit the /var/opt/SUNWsymon|PrimeAlert/cfg/domain-config.x file to use an IP instead of a hostname (to be positive it's using the same network it can see the SunMC Server) in the "agent" section, then reseed/restart and try all steps again.
If you get to step f) and have switched things to IPs, and reseeded etc and it still doesn't work, you probably have a firewall issue.
If you're using the Halcyon Agent you can contact support@halcyoninc.com or sales@halcyoninc.com to get more direct help.
Regards,
Mike.Kirk@HalcyonInc.com
http://www.@HalcyonInc.com
Thanks for the help Mike,
I tried the SNMPv1 thing and it works.
There are multiple interfaces so I specified the IP address in the domain file and re-seeded/config'd it again...
Still nada... No firewalls... Everything hooked to the same switch and there's no odd duplex conflicts or anything..
When installing all of our Sun agents I'd always get the following message after entering in the seed and taking the default SNMP "community string".
"Crypt Utilities package (SUNWcry) was not found. Encrypted SNMP communication is not supported"
I got a similiar (I think) message when doing the Linux install:
"PKCS11 library (PKCS11_API.so) was not found. Encrypted SNMP Communication is not supported."
Now, all of our Sun server agents work fine but do you think it might have something to do with that missing library?
Thanks!
-RMB
> I fixed our problem by just turing off SNMP
> encryption on the server... It's just a hundred or so
> development machines so we really didn't need it
> anyway...
That would do it: although you should be able to leave your Server on auto-negotiate for encryption (i.e. if it's available, use it, if not, just use normal authentication):
http://docs.sun.com/app/docs/doc/817-7961/6mn8bt7bo?a=view
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
