Forum Discussion
Customize monitor
One of the main points of having a customer monitor is to check that the port you are using for actual traffic is available. It seems less than ideal to monitor a separate port. What happens if a firewall rule is added in between your BIG-IP and back end servers that blocks 6161, but not 8443? Then as far as your BIG-IP knows, the pool member is available and will send traffic to it, but since the traffic port is being blocked, clients won't be able to connect.
I would advise you to monitor the same port you intend on sending traffic to. That will keep the clients and bosses happy. (:
Is there a specific reason you want to monitor a different port?
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