Forum Discussion
Jolt/Tuxedo Pool Member Question
If I am reading the question correctly, it sounds like the Web server needs to communicate to the BIG-IP on port 9000 and on port 9050. Try creating two vs's using the same ip address; one using port 9000 and one using 9050. Create a pool for each with the members using the correct port. Since the BIG-IP is a default deny system, it will not listen for requests on port 9050 from the web server without the virtual server being created and enabled. Sounds like persistence is going to be required as well since you want the same member to respond on each port. Select a persistence method, such as source affinity persistence, and check the box "match across services" to force the same node to respond to the web server port 9000 and 9050.
- mski_151743May 02, 2014
Nimbostratus
Hi Greg, Right now, I have a port 9000 VIP (IP = 10.10.10.10 for example) listening on ANY port for testing purposes and Port Translation is turned on. No other pools are using this VIP in this QA environment. I have both pool members also listening on ANY port for testing purposes. Would this be the same as adding two new members with the other pair of ports? If I am understanding your suggestion correctly, do I need to have two members listing on 9000 and two members listening on 9050 in the same pool? I will try your suggestion, but I have to wait until 5/8. Thanks! Matt - mski_151743May 02, 2014
Nimbostratus
Sorry for the book, but here's some additional info in case it changes your suggestion above. I changed some info around, however, the ports are what I am to be using. I originally had the VIP listening on 9000, but opened it up to ANY for testing purposes because the application tests were failing across the F5. I have port translation checked on the VIP. At the pool level, I also opened them up to ANY ports for testing purposes. VIP: Name: test-vip-9000 IP: 10.1.5.20 Destination Port: Any Pool: Name: test-pool-9000 Health Monitors: test_monitor_9000 test_monitor_9050 Members: 10.1.8.20(0) 10.1.8.21(0) The application architect wants his Web server to start a session on destination port 9000, hit the VIP then go to 9050 or vice versa. His application works fine when his web server initiates a session on destination port 9000, hits the VIP and goes to a 9000 member. It also works when the destination port 9050 hits the VIP and goes to a 9050 pool member. To sum it up: Web Server destination port to VIP to member tests: Destination Port 9000 to VIP to 9000 member - application works. Destination port 9050 to VIP to 9050 member - application works. Destination Port 9000 to VIP to 9050 member - application fails. Destination Port 9050 to VIP to 9000 member - application fails.
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