Forum Discussion
Peter_Milanese_
Nimbostratus
NimbostratusNeed to add a balanced segment to our basic configuration
Currently, the setup is fairly basic, balanced web farm using a pair of LTMs. There's a public segment, and a dedicated backend. A few rules, but nothing to do with this.
What we need to do is put a completely foreign network on it in order to LB a temporary solution which resides on a physically separate network.
We now have
I (net1)
|
|
BIP
|
SW
|
Nodes (net2)
We want:
I (net1)
|
|
BIP <---> Client (net3) --- I
|
SW
|
Nodes (net2)
The client will not have their own backend, so I'll lay a port from the LTMs to their network. What are my options to isolate their network? Just a static on that port and snat to that network? Can the web servers route directly out, or should I route it through the LTMs anyhow?
1 Reply
Peter_Milanese_We decided to try something else here.
We created 2 front ends (routable), and 2 backends (nonroutable). The desire is to have them act as isolated clusters. We have the web services accessible on both, and the backend 1 is snating and can reach the outside via the default route. We are also able to setup a route to the 'non-default' gateway(public facing) from backend 2. We are not able to snat that out though.
Backend 2 hops through the BIP to other nodes on frontend 2, but does not seem to make the next hop from there (out to the net). This only works when we we the route with the frontend 2 VLAN resource.
How do I get backend 2 to get route to the frontend 2 next hop?
