The system administrator can use the same Zen Load Balancer appliance with diferent networks. To allow this we included and configured iproute2. This creates a independent route table with a default gateway for each network while at the same time you can specify a global route table using the default gateway.
Here is an example of a more advanced interface configuration:
- Real interface: This is an interface named eth0, in this example, and is where outside physical hardware in your network interfaces with the Zen appliance
- Virtual network interface: This is an interface named eth0:1 or eth0:cl, in this example. It is a virtual interface on a real interface and is where you can run the virtual services (Farms) where users will consume your load balanced services
- Vlan network interface: This is an interface named eth0.1, for example, with a vlan of 1. If you use vlans on your network then you can configure settings here.
- Virtual network interface on vlan: This is an interface named eth0.1:1 or eth0.1:cl and is a virtual interface on vlan interface. Only applicable if you are using vlans on your network.
If you are going to segment traffic for the appliance and for the services by putting the appliance on it’s own subnet then you can configure a default gateway for all of the interfaces listed in the “Table interfaces” section. Then in the and other default gateway in the “Default GW” section would be the one that handles the traffic for the appliance itself.
Note: The Web GUI interface and Zen Cluster interface settings will be locked the moment you bind them to those respective functions (GUI Interface & Zen Cluster). If you need to change any settings you will have to disable or change the interface service to modify them.