you could go to the hubs and just enable the tunnel server and not connect anything to it.
this would cause the hub to listen on port 48003.
You then should be able to use net_connect to test the connection to this but it is only as good as a ping would be as this will not mean that the tunnel is up and working.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 03-26-2020 10:57 AM
From: Miller Grisepe Echagarreta Parra
Subject: Monitorig the port 48003 tunnel server
@Gene Howard That it's right, the server of the customer is Hub with client certificate. I thinked that the port 48003 was open when the tunnel it's established.
So There is a way to monitor that the secondary hub is on Online, beyond to use (attach / post) on subscriber. Right now we have in monitoring the Ip adress of the server via ICMP, but only this.
Original Message:
Sent: 03-26-2020 10:22 AM
From: Gene HOWARD
Subject: Monitorig the port 48003 tunnel server
most likely your client hub are setup as tunnel client and not tunnel servers.
as such they are not listening on port 48003
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
Original Message:
Sent: 03-26-2020 10:13 AM
From: Miller Grisepe Echagarreta Parra
Subject: Monitorig the port 48003 tunnel server
Hi everyone.
I need monitoring with net_connect probe the port 48003 tcp of all my clients hub, the necessity it's for have other controll point more.
When I test a telnet to port 48003 this not answer but the tunnel ssl it's working. If the port is tcp and all is working. Why not anwer the petition icmp? ¿any idea?