F5 BIG-IP LTM pool no outbound traffic
Hello, I am trying to setup a new virtual server (port 80) on F5 BIG-IP. I can ping the VIP and all its member IP. I can ping to the self IP of the F5 from the member server. Service is http and it's running normaly when I'm accessing the server directly, but it gave me a blank page if I access it using the VIP. When I check the pool statistics, it shows bits & packet IN but no bits & packets OUT. I am totally new into this BIG-IP thing, can someone please guide me as clear as possible of what I should do to get this working? Thanks in advance :)
F5 App Error - Routing Table Could Not be Patched - MacOS
Hi All, I've been having issues with connecting to F5 VPN BIG-IP Edge client with the newer Macbook Pro with the i9 Processor 15" running the Mojave MacOS. It goes through the checks ok and before it connects it disconnects straight away and keeps reconnecting then disconnecting again. Using another mac machine (Macbook Air) I'm able to connect perfectly fine with the exact same settings. I've done a clean install on both machines to see if I could replicate the issue but it looks like it could either be a software/hardware locally with the machine not being able to write to the routing table. I've contacted the our F5 support team that we use and the logs say that it's connecting fine but it just drops out on the local machines end. Looking at the debugging logs I can see that I get an error: 2019-07-16, 15:45:35:000, 853, 853, edge, 48, Tunnel Server, Connecting state 2019-07-16, 15:45:36:000, 853, 853, edge, 2, Disconnected state, Error code, Routing table cannot be patched Can anyone shed some light on this issue? Or how to resolve the Routing Table cannot be patched? Any help would be greatly appreciated. Cheers, Gez
First Time setting up F5
Hi all, this is my first time setting up F5 VE from scratch which was different from managing one which is already setup. I have both application server up & running and both server's firewall is disable. The F5 external IP and the server's IP are on the same subnet and no firewall in between. 1) It seems F5 is able to reach port 5005 and 80 but not 15005. I check back on both servers and port 15005 is in "Listening" state Ltm::Node: 10.1.1.1 (10.1.1.1) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Node: 10.1.1.2 (10.1.1.2) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Pool: QA_Pool_15005 Status Availability : offline State : enabled Reason : The children pool member(s) are down Monitor : QA_15005 Minimum Active Members : 0 Current Active Members : 0 Ltm::Pool: QA_Pool_80 Status Availability : available State : enabled Reason : The pool is available Monitor : QA_80 Minimum Active Members : 0 Current Active Members : 2 Ltm::Pool: QA_Pool_5005 Status Availability : available State : enabled Reason : The pool is available Monitor : QA_5005 Minimum Active Members : 0 Current Active Members : 1
logger /Common/Interface_failsafe_monitor: interface 1.1 is not up (status: )
Hello F5 experts. I have an issue with our two load balancers. I am getting this error : logger /Common/Interface_failsafe_monitor: interface 1.1 is not up (status: ) Checked the load balancer interface 1.1 is showing as up. Checked the switch port which connects the interface 1.1 it is also up. Where can be this error comes from ? Many thanks for your help.First Time setting up F5
Hi all, this is my first time setting up F5 VE from scratch which was different from managing one which is already setup. I have both application server up & running and both server's firewall is disable. The F5 external IP and the server's IP are on the same subnet and no firewall in between. 1) It seems F5 is able to reach port 5005 and 80 but not 15005. I check back on both servers and port 15005 is in "Listening" state Ltm::Node: 10.1.1.1 (10.1.1.1) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Node: 10.1.1.2 (10.1.1.2) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Pool: QA_Pool_15005 Status Availability : offline State : enabled Reason : The children pool member(s) are down Monitor : QA_15005 Minimum Active Members : 0 Current Active Members : 0 Ltm::Pool: QA_Pool_80 Status Availability : available State : enabled Reason : The pool is available Monitor : QA_80 Minimum Active Members : 0 Current Active Members : 2 Ltm::Pool: QA_Pool_5005 Status Availability : available State : enabled Reason : The pool is available Monitor : QA_5005 Minimum Active Members : 0 Current Active Members : 1