Re: Traffic IP as a gateway for servers (nodes)

Hi Mathew,

Yes - you can do this, and there's a description in the product documentation.

In short, you create a single-hosted traffic IP group that contains a front-end (public) and a back-end (private) traffic IP address, and set the 'keeptogether' flag in the group so that the IPs are raised on the same traffic manager. Use the back-end traffic IP address as the default route for your back-end servers.

Re: Traffic IP as a gateway for servers (nodes)

Hi Mathew,

The situation you cite from the docs is for the case where you want to have multiple active traffic managers. In that case, you have two (or more) default gateways and you need to partition your servers so that they use the correct gateway*. Yes - if one traffic manager goes down its partition is offline, and if all of the servers in a partition fail, you need to persuade the traffic manager to failover. It's not a great solution.

In the simpler case, you have one active traffic manager and use the configuration I suggested. I suspect that if you just have two nodes, you aren't going to need two active traffic managers?

regards

Owen

* It may be possible to overcome this using source-based routing on the back-end servers, keyed on the source MAC address. Mark Boddington's A guide to Policy Based Routing with Stingray (Linux and VA) illustrates how to do this on the traffic manager; you could replicate his 'Multiple Links' / 'Auto-Last-Hop' configuration on the back-end servers. I've not tried it, but if you're feeling confident, it's worth a go.