RMA Time out

KS-Soft · Post by **KS-Soft** » Mon Jun 05, 2006 7:52 am

HostMonitor and RMA uses the same code to perform tests...
Its good to use some network packet analyzer (sniffer) to check what is going on.
BTW Do you use some tests based on TCP protocol (TCP, POP, IMAP, HTTP, URL)? Such tests work fine?

Regards
Alex

Nadir · Post by **Nadir** » Mon Jun 05, 2006 9:55 am

I use DNS and SMTP tests and they works fine.

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Jun 05, 2006 10:27 am

Nadir wrote:Why problem doesn't appear when HM performs tests itself without agent? I don't think problems comes from network.

It depends on where is target system situated. If it is situated in the same network(host) with RMA then you are right, it is not a network problem.

Could you enable RMA logging (using rma_cfg.exe utility) and check log1.txt, log2.txt files in RMA's directory?

Regards,
Max

KS-Soft · Post by **KS-Soft** » Mon Jun 05, 2006 10:34 am

Why problem doesn't appear when HM performs tests itself without agent?

If HostMonitor can perform the test, why do you use agent?
Anyway, we cannot solve this problem until we see what is going on in your network. Do you have sniffer?

Regards
Alex

Nadir · Post by **Nadir** » Tue Jun 06, 2006 7:07 am

Could you enable RMA logging (using rma_cfg.exe utility) and check log1.txt, log2.txt files in RMA's directory?

In failure audit log I can read

Windows socket error: Connection reset by remote host (10054), on API 'send

If HostMonitor can perform the test, why do you use agent?

I monitor network through Firewall --> RMA increases security and decreases the network traffic.

Any idea to slove problem.

KS-Soft Europe · Post by **KS-Soft Europe** » Tue Jun 06, 2006 7:29 am

Nadir wrote:Windows socket error: Connection reset by remote host (10054), on API 'send

According to Microsoft:
Error 10054 - An existing connection was forcibly closed by the remote host.
A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a reboot.

So, you may increase timeout. I do not know what is going on in your network, but timeout you have specified is not enough. As I wrote above, you have to increase first timeout vale in rma_cfg utility and second on HostMonitor's side in "Agent Connection Parameters" dialog.

Regards,
Max

Nadir · Post by **Nadir** » Tue Jun 06, 2006 7:42 am

you have to increase first timeout vale in rma_cfg utility

I have already specified 120 (I think unit is sec)

second on HostMonitor's side in "Agent Connection Parameters" dialog.

Also 120

Do you think, I must still increase value?

KS-Soft Europe · Post by **KS-Soft Europe** » Tue Jun 06, 2006 7:51 am

Nadir wrote:Do you think, I must still increase value?

Yes, I do. First try to increase timeout in "Agent Connection Parameters" and if it does not help increase timeout in rma_cfg utility. Try 180 sec.

Regards,
Max

Nadir · Post by **Nadir** » Tue Jun 06, 2006 8:07 am

Ok, thanks for help

KS-Soft · Post by **KS-Soft** » Tue Jun 06, 2006 4:46 pm

What we are talking here about? If RMA does not receive responce from SNMP agent within 120 sec, I think responce never will be received. So 300 or 500 sec timeout will not help.

Windows socket error: Connection reset by remote host (10054), on API 'send

If this message appears 120 sec after connection was established, this means HostMonitor dropped connection because it did not hear responce from RMA. HostMonitor did not hear responce from RMA because you are using 120 sec timeout for SMTP test and RMA did not receive responce from SNMP agent.
So, if you increase HostMonitor/RMA communication timeout, you will receive "Timeout error" responce from the agent. Otherwise HostMonitor will drop connection and show "Read error" message.

Thereby what the problem is very clear to me - RMA does not receive responce from SNMP agent. Of course I cannot say what the reason of the problem. I see 3 posibilities: bug in SNMP agent, network problem, some 3rd party software problem (e.g. antivirus monitor, content monitoring software, personal firewall installed on RMA's system or target system may lead to such problems).

Conclusions

1) Instead of increasing timeout you should increase Retries parameter of the test. If you are not using some slow dial-up connection, I would recommend the following parameters for SNMP test:
- Retries: 3
- Timeout: 10 sec
120 sec timeout for HostMonitor<->RMA communication is Ok.

2) If you want to find the reason of the problem, you should forget about RMA and check network, system and SNMP agent.

monitor network through Firewall --> RMA increases security and decreases the network traffic.

I understand. But if network is protected by firewall, how HostMonitor is able to perform the test (you said the same test performed by HostMonitor works fine)?
You have opened 161 port on firewall and checked the same target system using the same test items? In such case I would eliminate 1st and 2nd reason of the problem. Then something wrong on system where RMA is installed.

Regards
Alex

Nadir · Post by **Nadir** » Wed Jun 07, 2006 1:43 am

You have opened 161 port on firewall and checked the same target system using the same test items?

Yes I have

I would recommend the following parameters for SNMP test:
- Retries: 3
- Timeout: 10 sec
120 sec timeout for HostMonitor<->RMA communication is Ok.

Ok, I will test these parameters

Thanks