RMA connection manner

plambrecht · Post by **plambrecht** » Thu Jan 06, 2005 8:08 am

Hi,

I would like to have the RMA connections changed.
Now, the HMA server has to connect to the RMA agent. To accomplish this, we have to open a port on the remote firewall.

However, it is not always possible to open the port, because the firewall is not always managed by us.

It would be more convenient that the RMA connects to the HMA server.
This way, I only have to open a port on My firewall. On the client side, no changes have to be made, as the RMA uses the exisitng internet access to connect to my firewall...

You see the idea and the benefits ?

regards

Pieter

KS-Soft · Post by **KS-Soft** » Thu Jan 06, 2005 12:18 pm

Yes I see the idea and the benefits. But it will not be implemented in nearest versions because requires significant changes and some new function. E.g. if remote system/network fall down, no tests will be performed. HostMonitor should react somehow when it does not receive any requests from agent for a while...

Regards
Alex

plambrecht · Post by **plambrecht** » Fri Jan 07, 2005 2:10 am

Alex,

Indeed, it would be a big change...
Benefits all over:
You could add an alert to the RMA config, that if it is not connected, that an alert is generated bij AHM...
Some simple keep-alive feature ?
scheduled dial-out of the RMA would be something cool also...
That would allow us to monitor sites without a fixed internet connection...

Maybe v5 ?

P.

KS-Soft · Post by **KS-Soft** » Sun Jan 09, 2005 6:07 pm

May be, but not in 5.0. More likely 5.80

Regards
Alex

plambrecht · Post by **plambrecht** » Fri Jun 10, 2005 6:32 am

Alex,

Just to check if you have any upcoming plans for this change...
Maybe together with the servcie and admin console split ?

Greetz

P.

KS-Soft · Post by **KS-Soft** » Fri Jun 10, 2005 2:54 pm

Yes, may be together...

Regards
Alex

sdendle · Post by **sdendle** » Sat Jun 25, 2005 5:56 pm

This feature sounds ideal for some of the things we have been planning to do.
Perhaps RMA could have a heartbeat that is sent to AHM. If it cannot connect to AHM it could use another medium to transfer (at least the error at the time) information. E-mail for bad triggers for example.

plambrecht · Post by **plambrecht** » Thu Oct 06, 2005 3:30 am

Alex...

Any idea when this might get implemented ?
I'm missing about 25 remote sites that I should be monitoring, because they use a dynamic ip

Pieter

KS-Soft · Post by **KS-Soft** » Thu Oct 06, 2005 7:04 pm

This task has "medium" priority and requires a lot of changes.
May be in version 6...

Regards
Alex

plambrecht · Post by **plambrecht** » Fri Nov 04, 2005 5:17 am

Alex,

I've been thinking about this problem...
There might be a middle way...

We can keep the connection from the HMA server to the RM Agent.

But the RMA should send a hartbeat to the HMA server on a regular base (changable in the INI file).
the HMA Server should detect the public IP, and if it is different then the one in the HMA database, it should change it in the RMA database to the new one... the RMA name and password can be used to make it more secure.

Do you think that's an temp workaround ?

Pieter

KS-Soft · Post by **KS-Soft** » Fri Nov 04, 2005 10:29 am

We can keep the connection from the HMA server to the RM Agent.
But the RMA should send a hartbeat to the HMA server on a regular base (changable in the INI file).

Sorry, I am not sure I understand you. What application establishes TCP connection? HostMonitor? In this case I don't see how "hartbeat" can be useful?
If connection is established by RMA, we return to previous task...

the HMA Server should detect the public IP

How?

Regards
Alex

plambrecht · Post by **plambrecht** » Fri Nov 04, 2005 10:33 am

The problem is that a lot of customers have a dynamic public IP.

With the current AHM, it is not possible to connect to a RMA that has a dynamic IP.
We could use DynIP or something, but that is not always an option...

If the RMA could tell HMA what IP address it has, then most of the problems are solved with dynamic IP's...

P.

KS-Soft · Post by **KS-Soft** » Fri Nov 04, 2005 1:22 pm

Still not following. How RMA can inform about new IP address? If connection established by HostMonitor, it means address the same. If address has been changed (and DNS is not used), HostMonitor cannot establish connection to agent, so agent cannot inform about new address.

May be you mean that agent should connect to HostMonitor for single purpose - send new address. Test execution should be performed as before - connection from HostMonitor. Is that what you mean?

Regards
Alex

plambrecht · Post by **plambrecht** » Sun Nov 06, 2005 10:58 am

Yes ! that's the idea !

The current setup (HMA connects to RMA) remains, but the Agent connects at a regular interval to the HMA to send his public IP address...

Could that be done ?
It would be a great comprimise for now..

There are several ways the HMA could detect the public IP..
1. the HMA servers checks from wht public IP the RMA connects to give the IP address
2. the RMA can detect it's public IP through a webpage like www.whatismyip.com and transfer that to the HMA

Thx already

Pieter

KS-Soft · Post by **KS-Soft** » Mon Nov 07, 2005 9:28 pm

H'm... Yes, such option could be implemented sooner..

Regards
Alex