Cirrus
EmployeeI'd recommend using the -status parameter in the sideband connect command to your advantage. You can use this to test that the connection is established before sending data.
https://clouddocs.f5.com/api/irules/connect.html
# Connect to an external host with a connection timeout of 100 ms and an idle timeout of 30 seconds
# Use catch to handle any errors in the destination virtual server name or external host:port
# Check if the return value saved to $conn_id is not null
if {[catch {connect -timeout 1000 -idle 30 -status conn_status sideband_virtual_server} conn_id] == 0 && $conn_id ne ""}{
log local0. "Connect returns: $conn_id and conn status: $conn_status"
} else {
log local0. "Connection could not be established to sideband_virtual_server"
}
CirrusHi Kevin,
I already have this piece of code in my irules.I guess my issue wasnt clear to you.
The customer already has a bigIP set up that is connected to the customers pool.We are adding a mirroring Virtual server in the management portal that is connected to one of our pools.So the irules on the customer BigIP virtual server connects to our mirroring server and sends the request as soon a client sends a request to the customer website via the customer's BIGIP load balancer.
However if our Virtual server or the pool goes down or fails the customer set up gets error as for a short amount of time the requests from the client(user)to the customer website will get a ECONNRESET.We want to avoid this issue so that any failure on our end doesnt cause any issue for the customer website.
Could you please suggest if theres a way out.