5-6
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 5 Configuring Virtual Servers
Configuring Virtual Servers
Virtual Server Usage Guidelines
The Virtual Server configuration window provides you with numerous configuration options. However,
instead of setting every option in one pass, configure your virtual server in stages. The first stage should
always be to establish basic “pass through” connectivity with simple load balancing and include minimal
additional features. This level of setup should verify that ports, VLANs, interfaces, SSL termination (if
applicable), and real servers have been set up properly, enabling basic connectivity.
After you establish this level of connectivity, additional virtual server features will be easier to configure
and troubleshoot.
Common features to add to a working basic virtual server are as follows:
• Health monitoring probes
• Session persistence (sticky)
• Additional real servers to a server farm
• Application protocol inspection
• Application acceleration and optimization
Table 5-1 identifies and describes virtual server configuration subsets with links to related topics for
configuration information.
Related Topics
• Configuring Virtual Servers, page 5-2
• Information About Using Device Manager to Configure Virtual Servers, page 5-5
• Virtual Server Testing and Troubleshooting, page 5-6
• Virtual Server Configuration Procedure, page 5-7
Virtual Server Testing and Troubleshooting
As outlined in the “Virtual Server Usage Guidelines” section on page 5-6, first set up a basic virtual
server that only enables connectivity and simple load balancing, such as round-robin between two real
servers. Next, use a client, such as a web browser, to send a request from the client network to the virtual
server VIP address. If the request is successful, you can now make changes or add virtual server features.
If the request is not successful, begin virtual server troubleshooting as outlined in the following
sequence:
1. Wait and retry your request after a minute or two, especially if the existing ACE configuration is
large. It can take seconds or even minutes for configuration changes to affect how traffic is handled
by ACE.
2. Click the Details button in the lower right of the Virtual Server page. The Details button displays
the output of the show service-policy CLI command.
3. Verify that the VIP State in the show service-policy CLI command output is INSERVICE. If the
VIP state is not INSERVICE, this may indicate the following:
–
The virtual server has been manually disabled in the configuration.
–
The real servers are all unreachable from ACE or manually disabled. If all of a virtual server's
real servers are out of service due to one of those reasons, the virtual server itself will be marked
Out Of Service.
Comments to this Manuals