ry, and shows the number of real servers in each server farm. To show detailed status information for the server farms, use the show module csm module# serverfarms detail command. This command shows the statuses of the server farms, and of every real server within them: Switch# sho mod csm 8 serverfarms detail CONTENT_FARM, type = SLB, predictor = RoundRobin nat = SERVER virtuals inservice = 1, reals = 5, bind id = 0, fail action = none inband health config: <none> retcode map = <none> Real servers: CONTENT_00, weight = 8, OPERATIONAL, conns = 25 CONTENT 01, weight = 8, OPERATIONAL, conns = 15 CONTENT_02, weight = 8, OPERATIONAL, conns = 22 CONTENT_03, weight = 8, OPERATIONAL, conns = 21 CONTENT_04, weight = 8, OPERATIONAL, conns = 15 Total connections = 98 [- text removed - -] Chapter 28: Content Switch Modules in Action I use this command a lot because it gives me a nice snapshot of the server farms, with connection details for each real server contained within them. Upgrading the CSM I'm including a section on how to upgrade the CSM because I've found the Cisco documentation to be lacking. This process may change with future releases. Here, I'll show you how to upgrade a CSM-S (the S indicates an included SSL daughter card) from Version 2.1 to 2.1(1). First, you must TFTP the new image to the supervisor's bootflash. The Cisco docu- mentation indicates that the image should be placed on the device sup-bootflash:, but, in my experience, this process will not work unless the image is located on the bootflash: device. If you're having trouble getting this to work, try another bootflash device. Then, using the tftp-server command, configure the TFTP server to serve the file you just loaded to the bootflash: Switch(config)# tftp-server bootflash:c6slb-csms-k9y9.2-1-1.bir To proceed, you'll need to control the CSM directly. To do this, issue the session command, followed by the module#, the keyword processor, and the processor# (which should always be zero): Switch# session slot 8 proc 0 The default escape character 