Tunnel From xx(hub)*** alarms

[Anon Anon]

Is there any way to change the message string for these types of alarms.

I need the HUB name to be first...like
"xx(hub)***: Tunnel has disconnected"

[Anon Anon]

In my experience, none of the alarm messages from the hub are configurable.  The lack of the hub name (or "tunnel description" from the hub config) in the alarm messages has also caused us some grief in the past.  Recently I wrote a custom probe to find out from the hub which tunnels are down and generate more useful alarm messages by reading the hub.cfg file to get the tunnel descriptions.  (We used to use net_connect to make sure remote hubs were still listening on the tunnel port, but that did not always alert us when some other kind of tunnel problem would occur.)  I think this is working much better for us than the default alarms from the hub itself.

I can go into more detail about how our probe does this if you are interested in doing the same.

Regards,
Keith

[Anon Anon]

I have actually used the logmon probe as well to watch the hub.log for errors relating to connection by doing this as well you can also send a hub restart command when the alarm is seen.

[Anon Anon]

Could you by chance post some information on how you are doing this with logmon? commands, errors watched, profiles etc that might help. I am wanting to do the same thing for tunnels that drop.

[Anon Anon]

If you could help us with your solution with logmon + message to restart hub. I'm having the same problem and this would help us a lot!