Forum Discussion
New Wildcard Virtual Server isn't Working
Here's my test log:
-Confirmed I can use 10.53.81.163 - Can access google.ca -Setup a new Access rule in the WCCP ACL to send it to the f5 -Tracert indicates that it's making it to the F5 -Tried standard profile. -Tried automap -Tried Persistence -Tried all :80 pool members -Setup a :443 pool -Tried setting up http/https profiles -TCPDump revealed the traffic is at least making it to the LTM -Stats indicate the VIPs haven't been used so the VIP is configured incorrectly. -Disabled the Secure VIP and Set the other VIP to All ports -I can ping the WSA (216.205.91.9) from the Qual LTM -Confirmed that both of these virtual devices are in the same VLANs, 216 and 2040. (Neither of them Private VLANs) -Reviewed the TCP handshake of a Performance Layer4 virtual server: According to the VIP/Pool stats no packets have been received for the duration of the testing We never get to "LTM sends SYN request to Node" in this flow so it looks like the VIP isn't intercepting this traffic for processing. https://support.f5.com/csp/article/K8082l4
Familiarized myself with the basic overview of Wild Card Virtual Servers: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-concepts-11-5-0/2.html
They recommend the following: "We recommend that when you define transparent nodes that need to handle more than one type of service, such as a firewall or a router, you specify an actual port for the node and turn off port translation for the virtual server."
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com