 a real server into or out of service from within the server farm. This is useful because a real server can be in more than one server farm. If you were to make the real server inactive in the real server configuration, it would become inactive in every server farm in which it was configured. This can be useful, too, but it may not be what you want. It's handy to be able to make a real server inactive in one server farm while keeping it active in others. Virtual servers Virtual servers, or vservers, are configured using the vserver server-name CSM com- mand. The IP address for the vserver is specified with the virtual command, which is followed by the port to be balanced (or the keyword any for all ports). The server farm to include is referenced with the serverfarm command. For a sticky vserver, include the sticky command along with the timeout value in minutes. The replicate and persistent commands are defaults inserted by IOS: vserver V-CONTENT virtual 10.5.5.6 any serverfarm CONTENT FARM sticky 10 replicate csrp sticky replicate csrp connection persistent rebalance inservice Configuring Server Load Balancing Port redirection Port redirection is accomplished by specifying a port number for the real servers in the server farm, and a different port number in the virtual statement of the vserver. In this example, I've created a virtual server that balances requests on port 443 (HTTPS), and forwards those requests to the real servers on port 1443: serverfarm HTTP_FARM nat server no nat client real name CONTENT-01 1443 inservice real name CONTENT-02 1443 inservice real name CONTENT-03 1443 inservice vserver V-HTTP virtual 10.5.5.7 tcp https serverfarm HTTP FARM replicate csrp sticky replicate csrp connection persistent rebalance inservice Chapter 27: Server Load-Balancing Technology CHAPTER 28 Content Switch Modules in Action Figure 28-1 shows a simple load-balanced network that I've built to illustrate some common configuration tasks. The load balancer in use is a pair of Cisco Content Switch Modules in a pair of 