When an Access Gateway is not licensed as a load balancer, you can configure a virtual server with one real server bound to it. Multiple real servers cannot be load balanced, but the virtual server can provide health monitoring and failover capabilities. You can use the capability to configure failover to multiple servers running the Web Interface. For example, you configured two servers running the Web Interface with the IP addresses 172.16.100.81 and 172.16.100.82. These are called WISRV01 and WISRV02. If WISRV01 fails, the Access Gateway can automatically route Web Interface requests to WISRV02.
To configure failover to the Web Interface
- In the Configuration Utility, in the navigation pane, expand the Virtual Servers and Services node.
- Click Services and then click Add.
- In Service Name, type the name of the service, such as WISRV01.
- In Server, type the IP address of the server running the Web Interface and click Create.
- Repeat Steps 3 and 4 to create the service for a second server running the Web Interface, click Create, and then click Close.
- Click Virtual Servers and then click Add.
- In Name, type a name for the virtual server.
- On the Services tab, select one of the Web Interface services, and click Create.
- Repeat Steps 7 and 8, selecting the second Web Interface service.
- Clear Directly Addressable because this virtual server does not require a specific IP address. Click Create and then click Close.
- Select the first virtual server and click Open.
- On the Advanced tab, in Backup Virtual Server, select the second virtual server and click OK.
When the Access Gateway is configured to use Web Interface failover, when these steps are complete, use the primary virtual server address instead of the Web Interface address when configuring the home page in global settings or as part of a session policy. All Web Interface traffic goes to the first virtual server you configured. If this server fails and the second virtual server is running, users automatically failover to the second virtual server.