 8080: ip slb serverfarm WEB-FARM nat server real 10.10.10.101 8080 inservice real 10.10.10.102 8080 inservice real 10.10.10.103 8080 inservice ip slb vserver VIRTUAL-WEB virtual 10.1.1.1 tcp 80 serverfarm WEB-FARM inservice Content Switch Modules All configuration for the CSM is done in IOS, using the module ContentSwitchingModule module# command. This command can be abbreviated module CSM module#. Here, I'm configuring a CSM residing in slot 8 of a 6509: module CSM 8 CSMs can be installed in pairs, with one module in each of two physical switches. A dedicated VLAN needs to be created for the stateful failover traffic. This VLAN should have its own physical links, if possible. Failover is called fault tolerance in the CSM, and is configured with the ft com- mand. You must specify a group (you will probably need only one) and the VLAN being used for stateful failover traffic. Fault tolerance is similar in behavior to HSRP in that each side must be configured with a priority. You can configure preemption to have the CSM failback to the primary when it comes back online after a failure: ft group 1 vlan 88 priority 15 preempt Because the CSM is a physical device and not just a software feature like SLB, you must configure the VLANs that the CSM will be using. The CSM works with client VLANs and server VLANs: the client VLAN is where the virtual servers will reside, and the server VLAN is where the real servers will reside. Configuring Server Load Balancing Content Switch Modules can operate in bridged mode, where the virtual servers and real servers reside in the same VLAN. This configu- ration is not recommended and not covered here. See the Cisco documentation for more details. For my examples, I will use VLAN 3 for the client side, and VLAN 4 for the server side. The IP network for VLAN 3 will be 10.5.5.0/24. The IP network for VLAN 4 will be 10.10.10.0/24. When configuring the client VLAN, you must configure the IP address of the CSM on the VLAN, and an alternate IP address for the failover CSM. This IP address 