Hello Steve Thank you for this video really appreciate that. I've got one query like In my environment I have got one service for which the nodes are showing not available on BIG IP. we have got everything setup on BIG-IP , we have got send string and we configured receive string of 200 OK but still it marks the pool as down. when I do curl command through CLI it shows 200 OK for the application but for some strange reason BIG-IP couldn't sync up with the servers. How do I determine that whether the service is actually available and its really indeed sending 200 OK back to BIG-IP. I have 2 servers placed one at each data centers and have got BIG-IP to load balancing the traffic btw them. I have got another services running fine on BIG-IP but this is the only service causing me a pain as I couldn't determine if it's an issue with BIG-IP or the server it self. Any help would really appreciable. Thanks again for your time
Hi Sam, I apologize for the delayed response. Have you done any captures on the pool members themselves to see the HTTP response codes they are sending when the monitor sends the request? Also, to narrow down your capture, remember health monitors use a self IP and not a SNAT IP. If using SNAT, the floating (SNAT) IP will be the client translated address where as the self ip does health monitoring and other system functions.
Really informative and quick thanks Steve.
Superb !!!
And how do we TShoot for Application SLOWNESS Issues ?
Really good and helpful. How do we verify if one customized monitor (example nprd-USS-DEV-API-443-monitor ) is used by multiple pool members or VIP.
thank you, makes sense
Thanks Steve.
Hi Steve, my question is if I have 2 node members, how to monitor each member using https?
Same question
Use a curl command but instead of using url just type the backend server ip
Hello Steve, can you show how to monitor for more than one node member each having its distinct http get url for health check?
did you have a solution to your question? I need to do that exactly.
Hello Steve Thank you for this video really appreciate that. I've got one query like In my environment I have got one service for which the nodes are showing not available on BIG IP. we have got everything setup on BIG-IP , we have got send string and we configured receive string of 200 OK but still it marks the pool as down. when I do curl command through CLI it shows 200 OK for the application but for some strange reason BIG-IP couldn't sync up with the servers. How do I determine that whether the service is actually available and its really indeed sending 200 OK back to BIG-IP. I have 2 servers placed one at each data centers and have got BIG-IP to load balancing the traffic btw them. I have got another services running fine on BIG-IP but this is the only service causing me a pain as I couldn't determine if it's an issue with BIG-IP or the server it self. Any help would really appreciable. Thanks again for your time
Hi Sam, I apologize for the delayed response. Have you done any captures on the pool members themselves to see the HTTP response codes they are sending when the monitor sends the request? Also, to narrow down your capture, remember health monitors use a self IP and not a SNAT IP. If using SNAT, the floating (SNAT) IP will be the client translated address where as the self ip does health monitoring and other system functions.