So we are using Remedy behind an F5 LTM. Here are some knowns:
1. Remedy can be configured use the rpc portmapper (tcp/111 and udp/111) to relay the open tcp/udp port used by Remedy.
2. Remedy is configured to listed on a specific tcp/udp prot.
3. Remedy uses the rpc protocol over tcp or udp.
4. Remedy is not a true application cluster; sessions are tracked and independant to each node. We enabled source ip session persistence and set the expiration to the period of time that Remedy expires the floating license token.
Here is my current state:
1. We are able to handle rpc portmapper traffic so that users can connect to the Remedy farm ip address without specifying a tcp/udp port.
2. We are able to handle the remedy traffic through the ltm (rpc over tcp or udp)
3. We have a health check set up by verifying the port that Remedy is configured to listen on is open (tcp/2020).
Here is my problem:
1. Remedy can be listening on the tcp/2020 but not responding to client requests. We would like a health check that actually verifies the availability of the application server. Can you point me in the right direction as to how to accomplish this?
Thanks,
Axton Grams