How can developers manage nodes having F5 as gateway?
Hello Team, I have a Big IP F5 with AWAF module (version 17.1.1.1) whose floating IP address is configured as the gateway IP for all the nodes. I have created a standard virtual server to host HTTPs services with SSL bridging and AWAF policies. However, our web developers need to administer the content of the web servers via SSH and RDP. Can you advise what is the best way to provide management access to the several nodes? When attempting to SSH or RDP, the nodes are forwarding the response to the BIG IP which in turn is not forwarding the response to the edge firewall. Can you advise if a forwarding L2 or L3 virtual server can be useful in this scenario and how it can be used?
Cluster Cross subnet
Hi, We currently have two independent clusters of F5 in separate subnets (sites) and require a method for synchronizing the configuration between them. There is a restriction on the deployment where they must be in separate subnets. The two sites run active-active. The obvious issue for this is that the gateways are separate and when we attempt to synchronize the configuration, the gateway address is clobbered, resulting in the routing breaking. We've tried a few things including: sync only; doesn't synchronize everything ip gw pool w/ sync fail-over; server split routing looking at the files manually and syncing them with external script Does anybody have advice on how they would handle this situation? Thanks.