Forum Discussion
Health Monitors for Non-default Route Domains
I currently have a non-default route domain (rd 1) set up for a group of hosts. Both route domain 0 and route domain 1 have strict isolation enabled. However, health monitors set up for hosts in route domain 1 are still being sourced from the non-floating IP in route domain 0. They are not able to reach the hosts and therefore the hosts are marked as down. If I go to the CLI and try to telnet to a host in route domain 1, such as hostA:443, it fails to connect. However, if I go to route domain 1 with 'rdsh 1' I am then able to connect to the host. Is there a way to make a health monitor use the non-floating IP in the route domain the host is in or do I need to make a route between the two? ...or something else? Thanks.
1 Reply
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