Why wouldn’t the agent that points to the F5 GTM URL point to
wherever the F5
wants to have it communicate with? So you’re saying the BCP RHQ server
storage node has to join the Prod storage node cluster for this failover to
BCP to work, even with the F5 GTM URL being used?
Don't confuse the storage node configuration with the agent configration. Two
different things. The agent's failover list is determined when a new server is added
to the RHQ HA environment and shared to the agent the next time the agent connects to the
server or when the agent periodically asks for its failover list (which happens every hour
by default).
The storage cluster stuff is handled independently/differently from that. I dont know much
about the storage node cluster config; someone else would have to chime in there about
storage nodes.
When the agent needs to connect to a server, it looks for the hostname and port of the
server to use (the data you see in failover.dat) and will use the proper Jboss/Remoting
protocol (which is typically either servlet or sslservlet). So the URL it tries to connect
to will be some jboss/remoting URL like
"servlet://server-hostname:7080/jboss-remoting-servlet-invoker/ServerInvokerServlet"
I don't know how you are telling the agent to use this F5 GTM URL you refer to, but I
have a feeling the agent isn't using the URL you think it is using. But that's
just a guess. Turn on agent debug, and look at the debug messages it spews when trying to
make connections during its failover and see what its trying to connect to.