hi
I want to test tcpport all computer ( all subnet ) At network. if host is alive and windows, may perform tcp test.
I dont want to use Dependent Test. because, total computers are approximately 3000.
PING and TCP Port test together
BTW
If you need to setup similar tests for many systems, you may use Replicator
http://www.ks-soft.net/hostmon.eng/replicator/index.htm
Also Ping and TCP tests allows you to specify a range of IPv4 addresses (e.g. 10.10.1.100 - 10.10.1.254). In this case, HostMonitor will create a separate test for each of the addresses within that range. This allows you to create 3000 tests in a minute.
Regards
Alex
If you need to setup similar tests for many systems, you may use Replicator
http://www.ks-soft.net/hostmon.eng/replicator/index.htm
Also Ping and TCP tests allows you to specify a range of IPv4 addresses (e.g. 10.10.1.100 - 10.10.1.254). In this case, HostMonitor will create a separate test for each of the addresses within that range. This allows you to create 3000 tests in a minute.
Regards
Alex
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
You may write a script. HostMonitor provides serveral ways to handle user-made scripts:hilmiesen wrote:Actually, I want to write script. Firstly, Script may do Ping-Test, secondly, Tcp-Test. Two tests must do together.
1. "Active Script" test method: http://www.ks-soft.net/hostmon.eng/mfra ... htm#script
2. "Shell Script" test method: http://www.ks-soft.net/hostmon.eng/mfra ... m#chkShell
3. "External" test method: http://www.ks-soft.net/hostmon.eng/mfra ... m#execheck
However, to implemet such a script, you should use some third-party utilities or components. Beside that, what results are you expected to see? Anyway, it is not a HostMonitor way.hilmiesen wrote:ip range: 192.168.1.1 - 192.168.1.254
192.168.2.1 - 192.168.2.254
I would suggest you to create just two tests in HostMonitor:
1. Ping.
2. TCP Port
and make ping test as a Master for second one. After that, you may use "Replicator" tool, described above, to spread this tests over specified range. It's pretty easy: http://www.ks-soft.net/hostmon.eng/replicator/index.htm
Regards,
Max
I still do not understand why do you need this.
If you want to perform several TCP or other tests for each system, then there is a reason to setup Ping test as master test. So you will receive single alert when system shutdown or there is some network problem.
If you want to perform single(!!) TCP test for each system, why do you need Ping as master test?? Just perform single TCP test. If service works then of course ping test will be passed as well.
If TCP test fails, then you may use Ping test to check is this specific service problem or network problem. In such case you should setup TCP test as master test and start Ping test only if TCP test fails.
This way you reduce HostMonitor system load and network traffic...
Unless most of your systems shutdown most of the time. In such case your way (Ping then TCP) will be more efficient.
Regards
Alex
If you want to perform several TCP or other tests for each system, then there is a reason to setup Ping test as master test. So you will receive single alert when system shutdown or there is some network problem.
If you want to perform single(!!) TCP test for each system, why do you need Ping as master test?? Just perform single TCP test. If service works then of course ping test will be passed as well.
If TCP test fails, then you may use Ping test to check is this specific service problem or network problem. In such case you should setup TCP test as master test and start Ping test only if TCP test fails.
This way you reduce HostMonitor system load and network traffic...
Unless most of your systems shutdown most of the time. In such case your way (Ping then TCP) will be more efficient.
Regards
Alex