Forum Discussion
Pirlo
Nimbostratus
Aug 23, 2017GTM Topo Failure
I have GTM Topolgy failover scenario I am trying to get working and
cannot identify proper solution.
The below configuration works as expected
WIP Configured as Topolgy with 3 pools and wo...
gsharri
Altostratus
Aug 23, 2017Try this config. I think this will do what you want:
- NY pool. LB methods preferred: RR, alternate: none, fallback: none
- Phx pool.LB methods preferred: RR, alternate: your_choice, fallback: your_choice
- Assign pools to wideip. Wideip LB method: topology
- Custom topology region containing NA, SA, Oceania
- Topology record NA,SA,O > NY pool, weight 100
- Topology record: NA,SA,O > Phx pool, weight 50
- GTM will select the matching record with the highest weight (NY pool) but if all NY members are unavailable and alt/fallback LB methods=none it will then move on to a matching record with a lower weight (Phx pool).
- When NY is available again name resolution will resume to NY but you can set manual resume on the NY pool so GTM doesn't switch back automatically.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects