Fale alerts about agents down
Fale alerts about agents down
(OP)
Hi,
I´m having false alerts about agents (system and log) that stop responding that we have verified that are not true. We´ve checked that the ping is right during these moments, and connected by terminal services to the server everything seems to work properly, even with a very good speed, but with objectview we receive a lot of timeouts.
Could anybody put some light into this?
Thanks in advance.
I´m having false alerts about agents (system and log) that stop responding that we have verified that are not true. We´ve checked that the ping is right during these moments, and connected by terminal services to the server everything seems to work properly, even with a very good speed, but with objectview we receive a lot of timeouts.
Could anybody put some light into this?
Thanks in advance.
RE: Fale alerts about agents down
Are they Heartbeat messages?
Do you get any aws_sadmin to many request messages?
Could you cut and paste a couple of them into your thread.
Ta
RE: Fale alerts about agents down
Host:Windows2000_Server Windows2000_Server caiW2kOs Poll Agent:caiW2kOs N/A DOWN W2K
RE: Fale alerts about agents down
Are you still getting the heartbeat errors?
RE: Fale alerts about agents down
RE: Fale alerts about agents down
Do you see any errors in the DSM machine's logs? In the agent machine's?
aws_sadmin.log should log when the DSM contacts it (you should see the IP address of the DSM machine).
If not, you probably have a network or an SNMP problem.
RE: Fale alerts about agents down
The reason I say this is because the Heartbeat message is generated by the DSM polling the agent, rather than the agent sending the trap.
I'm presuming that you still receive valid alerts from the agent, say for example if a CPU goes critical?
Try this:
On your Agent server, edit the aws_sadmin.cfg file to include the servers' primary IP address at the bottom. Like so: # TRAP_OVERRIDE_ADDR 141.202.123.345
On your DSM and core server(s), add the agent server to the local hosts file using the same IP as you just put in the aws_Admin file.
Delete the object from the worldview and rediscover it.
Restart awservices on the agent.
See if this works.
RE: Fale alerts about agents down
Regards