Forum Discussion
How to Force Failover to Second Node
After playing with this all day, I've made no progress. The docs say you can create a custom monitor and apply to a node. Then if the node is in mulitple pools and the monitor marks the node as down, it's show as down in all the pools. The monitor I created is a http type and is doing a GET /rotation.html\r\n and looking for a text string, "PONG!". The monitor is in the same partition as the node. When I try to add the monitor to the node it's not in the list, the list only contains what looks like default monitors in the common partition. This is all being done in the GUI. So do I need to do this from the cli like the second reponse to the initial post implies?
- JGSep 13, 2013
Cumulonimbus
Can't tell if the monitor is really not applied. But did you test your monitor with a command line tool, such as curl or telnet? Some Web servers will not work if protocol version is missing. So the send string should be "GET /rotation.html HTTP/1.0\r\n\r\n" instead. Apply this on the pool level first and edit the file to make sure it works at all.
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