mbination of upper- and lowercase. No matter how you enter names when using SLB or CSMs, the parser will convert them to uppercase. Configuring Server Load Balancing Once in ip slb configuration mode, add the real servers to be included in the server farm with the real ip-address command. Here, I've configured two real servers. The first one is in service, and the second is out of service: real 10.10.10.100 inservice real 10.10.10.101 no inservice The final configuration for the server farm is as follows: ip slb serverfarm GAD-FARM nat server real 10.10.10.100 inservice real 10.10.10.101 no inservice Virtual servers Virtual servers are configured in SLB with the ip slb vserver server-name command. You must configure the IP address for the virtual server, the port or ports on which it will listen, and the server farms to be used: ip slb vserver VIRT-GAD virtual 10.1.1.1 tcp 0 serverfarm GAD-FARM inservice This configuration creates a virtual server named VIRT-GAD that listens on the IP address 10.1.1.1 on all TCP ports (TCP port 0 indicates all ports). Any request that comes into this IP address using TCP will be load balanced to the real servers config- ured within the server farm GAD-FARM. To create a virtual server that listens to a specific port, enter the port number on the virtual command line. For example, if needed my VIRT-GAD virtual server to respond only to SSH, I would include port 22 instead of port 0: virtual 10.1.1.1 tcp 22 Port translation using SLB You can configure individual ports for virtual servers and real servers. Configuring a real server on one port-and assigning the server farm to a virtual server that listens on a different port-causes the router to perform port translation when load balancing. Here, I've created real servers listening on port 8080 in the server farm WEB-FARM, Chapter 27: Server Load-Balancing Technology and a virtual server named VIRTUAL-WEB that listens on port 80. When requests come into the virtual server on port 80, they will be forwarded to the real servers on port