Forum Discussion
Doran_Lum_13484
Nimbostratus
NimbostratusFirst 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
natheCirrocumulus
Doran,
What type of Monitor is QA_15005? Is it just a tcp one?
The best suggestion would be to run tcpdump on the f5 to see if this gives you any clues, are you seeing the return traffic, for example. I'd also confirm the settings in the monitor too.
Hope this helps.
N
Doran_LumYes It's TCP monitor for QA_15005. FOr the settings in monitor
Name: QA_15005 Alias Service Port: 15005 Monitor Instances Address: 10.1.1.1 Monitor Instances Service: 15005 Monitor Instances Address: 10.1.1.2 Monitor Instances Service: 15005
No return traffic when i run tcpdump command
- Doran_Lum
I'm really sorry it's my fault.. I was confused about the whole F5 structure, I thought the Pool are the ones that's facing the Public and VS will be the one reaching the application server.
I understand now that I should create a new VS with a new Virtual IP. Then it should be link up to the Pool which will load balance to the Application Server.
I realise I went to create Virtual Server with the same IP of the application server which is why I'm able to ping it from ssh.
Now I realize there's another issue, the F5 VE cannot reach any application server or any other server. where should I start the troubleshooting ?