Release Notes for Catalyst 6500 Series Content Switching Module Software Release 2.2(8) Current Release—May 15, 2003 Previous Releases—2.2(7), 2.2(6), 2.2(5), 2.2(4), 2.2(3), 2.2(2), 2.1(4), 2.1(3), 2.1(2), 2.1(1), 1.2(2), 1.2(1), 1.1 This publication describes the features, modifications, and caveats for the Catalyst 6500 Series Content Switching Module (CSM) software release 2.2(8) running Cisco IOS Release 12.1(13)E3 or Catalyst operating system 7.5 or higher.
System Requirements System Requirements This section describes the system requirements for the Catalyst 6500 Series CSM software release 2.2(7). Memory Requirements The Catalyst 6500 Series CSM memory is not configurable. Hardware Supported Before you can use the Catalyst 6500 Series CSM, you must have a Supervisor Engine 1A or a Supervisor Engine 2 with a Multilayer Switch Feature Card (MSFC1 or MSFC2), a Policy Feature Card (PFC), and any module with ports to connect server and client networks.
System Requirements Product Number Product Description Minimum Software Version Recommended Software Version Recommended IOS Release Recommended Catalyst OS Releases WS-X6066-SLB-APC with Supervisor Engine 1A or Supervisor Engine 2 Content Switching Module 2.2(2) 2.2(2) 12.1(11b)E N/A WS-X6066-SLB-APC with Supervisor Engine 1A or Supervisor Engine 2 Content Switching Module 2.2(3) 2.2(3) 12.
System Requirements Software release 2.1(3) and 2.13(a) requires Cisco IOS Release 12.1(8a)EX or 12.1(11b)E. However, Cisco IOS Release 12.1(11b)E includes some Cisco IOS commands that refer to CSM 2.2 features that are not supported by a CSM 2.1 image. Software release 2.1(4) requires Cisco IOS Release 12.1(8a)EX or 12.1(11b)E. However, Cisco IOS Release 12.1(11b)E includes some Cisco IOS commands that refer to CSM 2.2 features that are not supported by a CSM 2.1 image. Software release 2.
System Requirements Table 1 Software Release/Orderable Product Number Matrix (continued) Software Release Image Filename Orderable Product Number Orderable Product Number Spare 12.1(11b)E c6kslb-apc.2-1-1.bin c6kslb-apc.2-1-3a.bin c6kslb-apc.2-1-4.bin c6kslb-apc.2-2-1.bin c6kslb-apc.2-2-2b.bin cc6kslb-apc.2-2-3a.bin c6kslb-apc.2-2-4.bin c6kslb-apc.2-2-5.bin c6kslb-apc.2-2-6.bin SC6K-2.1-CSM SC6K-2.2-CSM SC6K-2.1-CSM= SC6K-2.2-CSM= 12.1(13)E3 c6kslb-apc.2-1-1.bin c6kslb-apc.2-1-3a.bin c6kslb-apc.
System Requirements Feature Set Table 2 describes the CSM features and software descriptions. Table 2 CSM Feature Set Description Feature Image Filename Orderable Software Product Numbers Supported Hardware Supervisor 1A with MSFC and PFC c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Supervisor 2 c6slb-apc.2-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Cisco IOS All releases SC6K-2.2-CSM Catalyst Operating System c6kslb-apc.2-2-7.bin SC6K-2.2-CSM FTP c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.
System Requirements Table 2 CSM Feature Set Description (continued) Feature Route health injection Image Filename Orderable Software Product Numbers c6slb-apc.1-1-1.bin (requires release 12.1(7)E SC6K-2.1-CSM SC6K-2.2-CSM c6slb-apc.1-2-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Round-robin c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Weighted round-robin (WRR) c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Least connections c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.
New and Changed Information Table 2 CSM Feature Set Description (continued) Feature Image Filename Orderable Software Product Numbers Stickiness Cookie c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM SSL ID c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Source IP c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM HTTP redirection c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Sticky state c6slb-apc.1-1-1.bin SC6K-2.1-CSM SC6K-2.2-CSM Full stateful failover (connection redundancy) c6kslb-apc.
Limitations and Restrictions • When receiving out-of-order UDP fragments, the CSM will bridge the packets to the appropriate peer VLAN in the bridging-mode. • There is an enhancement to the predictor IP hash and cookie hash. The CSM will perform a secondary hash if the first hash value resolves in mapping to an out-of-service real server. This allows even distribution of connections.
Caveats • When configuring CSMs for fault tolerance, we recommend that you configure a dedicated link for the fault-tolerant VLAN. Note Fault tolerance requires CSM release 1.2 or higher. Note Configuring stateful redundancy with CSMs in separate chassis requires a gigabit link between the CSMs. Caveats These sections describe the following release caveats: • Open Caveats in Release 2.2(8), page 11 • Resolved Caveats in Release 2.2(8), page 15 • Open Caveats in Release 2.
Caveats • Open Caveats in Release 1.2(1), page 52 • Resolved Caveats in Release 1.2(1), page 54 • Open Caveats in Release 1.1, page 55 Open Caveats in Release 2.2(8) This section describes known limitations that exist in CSM software release 2.2(8). • CSCea02255 The CSM processes the TCP connection, although the MAC address is not intended for that port. Occasionally, the switch floods a SYN (synchronize) packet to all bridge ports.
Caveats • CSCdz12163 The CSM drops packets because the multilayer switch (MLS) card and the multilayer switch feature card (MSFC) use different MAC addresses. This problem remains in software releases prior to the Catalyst 7.5.1 software release. If any Supervisor Engine 2 in the switch is still running a software release prior to the 7.5.1 software release and the traffic is forwarded by that switch, the CSM drops the packet. Workaround: None.
Caveats • CSCdy29182 When multiple CSM users perform a do copy xx running-config from a CSM submode in Cisco IOS, the next command entered will fail with the message “% CSM parser state not found.” This problem occurs only if the file copied to running-config contains at least one CSM command. When the CSM command in the file copied to running-config is run, it overwrites the current CSM configuration parser state.
Caveats • CSCdv29125 In firewall configurations using an HTTP 1.1 redirect virtual server, a connection going through the firewalls may remain open after a redirect virtual server connection is established. Workaround: None. This connection closes when it times out. • CSCdv11685 You cannot configure different fault-tolerant pairs to use the same fault-tolerant VLAN. Workaround: Use a different fault-tolerant VLAN for each fault-tolerant CSM pair.
Caveats Resolved Caveats in Release 2.2(8) This section describes caveats that have been resolved in CSM software release 2.2(8). • • • Open Caveats in Release 2.2(7) This section describes known limitations that exist in CSM software release 2.2(7). • CSCdz61644 Some restricted CSM port commands return “failure” instead of “feature not supported.” Workaround: None • CSCdz61386 The last module in the chassis may not be shut down gracefully.
Caveats Release 2.2(x) does not support RTSP UDP streaming when a client NAT is enabled. If this configuration is set up, the server attempts to open a UDP connection. Some RTSP clients then fall back on interleaved mode (inline TCP). This mode will work in the application software, although the connection is sent to fastpath.
Caveats – Traffic into the CSM from an IP address must arrive on the same VLAN that the CSM uses to send to that IP address. Ensure that all traffic received by the CSM from a specific destination address arrives on the same VLAN that the CSM uses to reach that destination if the CSM is configured with a route as follows: Router(config)# module csm 4 Router(config-module-csm)# vlan 10 client Router(config-slb-vlan-client)# route 10.0.0.0 255.255.255.0 gateway 1.1.1.
Caveats Workaround: None. Open Caveats in Release 2.2(6) This section describes known limitations that exist in CSM software release 2.2(6). • CSCdw84018 Release 2.2(x) does not support RTSP UDP streaming when a client NAT is enabled. If this configuration is set up, the server attempts to open a UDP connection. Some RTSP clients then fall back on interleaved mode (inline TCP). This mode will work in the application software, although the connection is sent to fastpath.
Caveats Router(config-module-csm)# vlan 20 client Router(config-slb-vlan-client)# gateway 2.2.2.2 To make this configuration valid, delete the gateway command from either VLAN 10 or VLAN 20. Note NOTE: Do not use the gateway command in more than one VLAN. – Traffic into the CSM from an IP address must arrive on the same VLAN that the CSM uses to send to that IP address.
Caveats • CSCdy87767 CSM TCP health probes are using an incorrect Maximum Segment Size (MSS) value of 1480. The correct default MSS option value should be 1460. Most of the servers ignore the high MSS value from the health probe messages. Workaround: None. • CSCdy80475 Connection replication does not work after removing and adding a fault-tolerant VLAN. After removing the fault-tolerant VLAN between two CSMs, both fault-tolerant modules become active as expected.
Caveats Open Caveats in Release 2.2(5) This section describes known limitations that exist in CSM software release 2.2(5). • CSCdy33708 A virtual server configured with the service FTP option does not work if the client NAT option is enabled for the serverfarm and the FTP mode is passive. The passive mode has the client initiating the data connection (port 20). This caveat has been fixed for the port mode.
Caveats – Multiple routes on the CSM to the same destination are supported, but all such routes need to go through gateways on the same VLAN. Ensure that all routes to any particular destination go through the same VLAN.
Caveats • CSCdy47910 In CSM release 2.2(4), when you configure the route subnet netmask gateway gateway-address command, the gateway-address cannot be in the specified subnet netmask. You cannot configure a route which overlaps the VLAN subnet interface. Workaround: None • CSCdy36736 In previous releases, after the real server failed with the inband health check option, the removal of the inband health option would not enable the server.
Caveats • CSCdv29125 In firewall configurations using an HTTP 1.1 redirect virtual server, a connection going through the firewalls may remain open after a redirect virtual server connection is established. Workaround: None. This connection closes when it times out. • CSCdu57891 The output from the show interface gigabit slot/port command may erroneously indicate that one or more of the CSM gigabit ports are down. Workaround: Disregard the display. • CSCdu82478 In CSM software release 2.
Caveats This problem occurs only when the CSM is receiving many Layer 7 connections in which the portion of the traffic to be parsed (typically either the HTTP headers or SSL hello messages) spans multiple packets, and those connections are terminated before the CSM has received all of the packets that require parsing.
Caveats • CSCdy06651 It is not possible to configure an inband health probe to permanently disable a real server. When you configure the health retries count failed seconds command with a failed value of zero, the CSM should permanently disable the real server after it has first detected a failure. Instead, the CSM immediately re-enables the server for load balancing. This caveat occurs in CSM releases 2.2(1), 2.2(2a), and 2.2(3). It is fixed in release 2.2(4) and all other CSM versions.
Caveats Open Caveats in Release 2.2(3) This section describes known limitations that exist in CSM software release 2.2(3). • CSCdw84018 Release 2.2(x) does not support RTSP UDP streaming when a client NAT is enabled. If this configuration is set up, the server attempts to open a UDP connection. Some RTSP clients then fall back on interleaved mode (inline TCP). This mode will work in the application software, although the connection is sent to fastpath.
Caveats – Multiple routes on the CSM to the same destination are supported, but all such routes need to go through gateways on the same VLAN. Ensure that all routes to any particular destination go through the same VLAN.
Caveats Note • This issue does not apply to UDP frames that the CSM simply repeats from one bridged VLAN to another with no NAT operation. CSCdx66661 When the active CSM in a redundant pair is reset and the fault tolerance preempt option is enabled, it is possible for some traffic to be misdirected toward the standby CSM. This condition will persist until the standby CSM is reset. This issue exists in CSM releases 1.x, 2.1(1), 2.1(2), 2.1(3), 2.2(1), and 2.2(2a).
Caveats The packet is dropped and the ICMP error is sent back to the host where the packet originated. This action tells the originating host that it needs to reduce the size of its packets before they can be routed. Recent system implementations also include the MTU of the next hop in the ICMP message so that the source knows how big its packets can be. Workaround: Disable the path MTU discovery on the servers behind the CSM.
Caveats Open Caveats in Release 2.2(2) This section describes known limitations that exist in CSM software release 2.2(2). • CSCdx17864 When Layer 7 features are enabled on the CSM, the CSM may drop the IP frames it receives if those frames contain multiple IP options. The following features require Layer 7 functionality: URL regular expression matching, cookie regular expression matching, cookie sticky, URL hash sticky, SSL ID sticky, and generic HTTP header parsing.
Caveats • CSCdw49073 The CSM does not support creating more than 127 virtual servers with the same virtual IP (VIP) address, even though the CLI does allow you to configure more than 127 virtual servers. If you use the CLI to configure more than 127 virtual servers, the 128th and subsequent virtual servers will not function properly. Workaround: Do not configure more than 127 virtual servers on the same VIP.
Caveats Router(config-module-csm)# vlan 10 client Router(config-slb-vlan-client)# route 10.0.0.0 255.255.255.0 gateway 1.1.1.1 For load balancing to function properly, all traffic arriving from the 10.0.0.0/24 subnet must reach the CSM through VLAN 10. Resolved Caveats in Release 2.2(2) This section describes caveats that have been resolved in CSM software release 2.2(2). • CSCdx20633 DNS probe functionality has changed slightly.
Caveats • CSCdx08115 Health probes can run on 32 VLAN interfaces only. The CSM 2.2(1) release supports 255 VLANs. However, when more than 32 VLANs are configured, the CSM VLAN interface IP addresses is not functional for the 33rd and subsequent VLANs. The CSM VLAN interface IP address is the IP address configured in the VLAN submode under module csm slot. By not being functional, the VLAN addresses will not respond to ICMP requests, nor will health probing functionality work through these interfaces.
Caveats • CSCdu82478 In CSM software release 2.x, it is important that packets transmitted from the CSM toward a client (server) are transmitted on the same VLAN as packets received by the CSM from that same client (server). This constraint may be satisfied as follows: – Multiple routes on the CSM to the same destination are supported, but all such routes need to go through gateways on the same VLAN. Ensure that all routes to any particular destination go through the same VLAN.
Caveats • CSCdw49073 Configuring more than 128 VIPs with the same IP address can result in unpredictable balancing behavior. The CSM should restrict the user from configuring more than 128 VIPs with the same IP address. Workaround: Do not configure more than 127 virtual servers on the same VIP. • CSCdu04990 If the CSM parses a cookie to make a connection when the connection is closed, the connection will be listed as being current.
Caveats • CSCdu54735 If the version of software running on the CSM does not correspond to the version of Cisco IOS software running on the Catalyst switch, a spurious memory access message may be displayed when the CSM is inserted into a Catalyst 6500 Series chassis. Workaround: If the versions of software do not correspond, either the Cisco IOS or the CSM software must be upgraded for the module to function.
Caveats Open Caveats in Release 2.1(4) This section describes known limitations that exist in CSM software release 2.1(4). • CSCdu82478 In the CSM software release 2.x, it is important that packets transmitted from the CSM toward a client (server) are transmitted on the same VLAN as packets received by the CSM from that same client (server).
Caveats • CSCdw49073 The CSM does not support creating more than 127 virtual servers with the same virtual IP (VIP) address, even though the CLI does enable you to configure more than 127 virtual servers. If you use the CLI to configure more than 127 virtual servers, the 128th and subsequent virtual servers will not function properly. Workaround: Do not configure more than 127 virtual servers on the same VIP.
Caveats This error is returned by a router that receives a packet too large for it to forward when the DF bit is set. Note This error is sent only if the DF bit is set; otherwise, packets are just fragmented and passed through. The packet is dropped and the ICMP error is sent back to the host where the packet originated. This action tells the originating host that it needs to reduce the size of its packets before they can be routed.
Caveats • CSCdx78285 Under heavy load, it is possible for the CSM to reject incoming connections in the mistaken belief that it is low on resources. If this issue occurs, you will notice a rapid increase in the values displayed in the line entitled Pending event: Re-use too soon in the output of the show module csm tech proc 1 command. This issue exists in CSM releases 1.x, 2.1(1), 2.1(2), 2.1(3), 2.2(1), and 2.2(2a). Workaround: None.
Caveats – Multiple routes on the CSM to the same destination are supported, but all such routes need to go through gateways on the same VLAN. Ensure that all routes to any particular destination go through the same VLAN.
Caveats • CSCdx17864 When Layer 7 features are enabled on the CSM, the CSM may drop the IP frames it receives if those frames contain multiple IP options. The following features require Layer 7 functionality: URL regular expression matching, cookie regular expression matching, cookie sticky, URL hash sticky, SSL ID sticky, and generic HTTP header parsing. This issue exists in the following CSM releases: 1.x, 2.1(1), 2.1(2), 2.1(3) 2.2(1), 2.2(2).
Caveats This condition causes performance problems with the next in-service server. In the worst case scenario, this condition may cause the next in-service server to fail, which in turn may cause the servers in the server farm to fail. • CSCdw81611 The CSM drops or corrupts UDP fragments. This issue was originally introduced in Release 2.1.1 and is resolved in Release 2.2.1. Both the drop and the corruption issues are located only in fragments other than the first fragment.
Caveats Open Caveats in Software Release 2.1(2) This section describes known limitations that exist in CSM software release 2.1(2). • CSCdu57891 The output from the show interface gigabit slot/port command may erroneously indicate that one or more of the CSM gigabit ports are down. Workaround: Ignore the display. • CSCdu82478 In the Content Switching Module (CSM) software release 2.1.
Caveats Resolved Caveats in Software Release 2.1(2) This section describes caveats that have been resolved in CSM software release 2.1(2). • CSCdw05136 In CSM software release prior to 2.1(1), IP fragments are not supported and are dropped. In software release 2.1(1) of the CSM code, a simple form of support for handling UDP fragments was added. There is a defect in the code handling UDP fragments in 2.1(1). When a CSM running software release 2.
Caveats • CSCdw24384 In a configuration in which connections arrive at a CSM through a redundant router pair running HSRP, it is possible that connections arrive from the standby HSRP peer. When returning traffic back through that redundant router pair, the CSM must send the traffic to the HSRP virtual MAC address shared by the two routers. In CSM software releases 1.2(1) and 2.1(1), the CSM incorrectly forwards such traffic to the real MAC address of the standby router.
Caveats • CSCdv00464 Issuing the clear interface gigabit slot/port command for a CSM gigabit port may not clear the counters. Workaround: None. • CSCdv11685 Do not configure different fault-tolerant pairs to use the same FT VLAN. Workaround: Use a different FT VLAN for each fault-tolerant CSM pair. • CSCdv29125 In firewall configurations using an HTTP 1.1 redirect virtual server, a connection going through the firewalls may remain open after a redirect virtual server connection is established.
Caveats Resolved Caveats in Software Release 2.1(1) This section describes caveats that have been resolved in CSM software release 2.1(1). • CSCdu04990 If the CSM parses a cookie to make a connection when the connection is closed, the connection will be listed as being current. If the client makes a connection again after the sticky timer expires, then one more connection goes into a closing state, thereby incrementing the counter by one. Workaround: None.
Caveats • CSCdu54735 If the version of software running on the CSM does not correspond to the version of Cisco IOS software running on the Catalyst switch, a spurious memory access message may be displayed when the CSM is inserted into a Catalyst 6500 Series chassis. Workaround: If the versions of software do not correspond, either the Cisco IOS or the CSM software must be upgraded for the module to function. Open Caveats in Release 1.
Caveats • CSCdu05559 During heavy traffic conditions in a fault-tolerant configuration, the primary CSM may not be able to send heartbeat messages to the secondary CSM. This condition causes both the primary and secondary CSMs to become active, creating a bridge loop in the network. Workaround: Reboot the primary CSM.
Caveats Resolved Caveats in Release 1.2(2) This section describes caveats that have been resolved in CSM software release 1.2(2). • CSCdw24071 In CSM software versions 1.1(1), 1.2(1), and 1.2(1) or earlier, the CSM may fail if it receives a TCP RST frame on a connection at an inappropriate time. This condition may be triggered if an RST frame arrives immediately following a valid data frame on the same connection.
Caveats – Unknown real servers with unknown bind IDs and weights show up. – Virtual servers send an RST to all connection requests. – CSM performance becomes very slow. Workaround: Do not configure both a DFP agent and a manager on the CSM while it is balancing traffic. • CSCdu38154 Under a heavy FTP connection load you may see warnings about FTP not finding associated sessions. These messages are benign. Workaround: None.
Caveats You can determine that the mask has been changed by comparing the virtual server output for the show running command with the output from the show ip slb vserver detail command. Workaround: Create a Cisco IOS standard IP access list, assign it to an slb policy, and assign the policy to the virtual server. Resolved Caveats in Release 1.2(1) This section describes caveats that have been resolved in CSM software release 1.2(1).
Caveats • CSCdt73118 Although it is possible to configure the Catalyst 6500 Series switch remotely using an HTTP server, the CSM does not support this mode of configuration. Workaround: None. • CSCdt76588 The CSM appears not to see some SYN ACKs when forwarding a heavy flow of traffic. Workaround: None. • CSCdt77071 When a cookie sticky group or SSL sticky group is created and then associated with a virtual server, the virtual server changes its type to IP sticky.
Caveats • CSCdt42091 Intensive Telnet/FTP probing may cause a device that is being probed to stop responding. (Generally this represents a fault in the device being probed.) Workaround: Probe the device at a slower rate and increase the probe interval value. • CSCdt42937 If the CSM is forwarding traffic while configuration is occurring, error messages may appear on the screen. Workaround: Ignore these error messages.
Caveats • CSCdt77071 When a cookie sticky or SSL sticky group is created and then associated with a virtual server, the virtual server changes its type to IP sticky. Workaround: Create a policy, associate the sticky group with it, and then associate the policy with the virtual server. • CSCdt78663 When using RHI (Route Health Injection) in a fault-tolerant configuration, traffic from a VIP may go into a routing loop because the standby CSM replies to the VIP ARP request before the active CSM replies.
Troubleshooting Troubleshooting CSM error messages may be received and reported in the system log (syslog). This section describes these messages. Message Banners When syslog messages are received, they are preceded by one of the following banners: Where # is the slot number of the CSM module.
Troubleshooting Error Message SLB-LCSC: DFP agent disabled server , protocol , port Explanation The configured DFP agent has reported a weight of 0 for the specified real server. Error Message SLB-LCSC: DFP agent re-enabled server , protocol , port Explanation The configured DFP agent has reported a non-zero weight for the specified real server. Diagnostic Messages Error Message SLB-DIAG: WatchDog task not responding.
Related Documentation Error Message SLB-FT: heartbeat interval is identical again Explanation The heartbeat intervals of different CSMs in the same fault-tolerance group have been reconfigured to be identical. The fault-tolerance feature will be re-enabled. Error Message SLB-FT: The configurations are not identical between the members of the fault tolerant pair.
Obtaining Documentation • Catalyst 6500 Series Command Reference • Catalyst 6500 Series IOS Software Configuration Guide • Catalyst 6500 Series IOS Command Reference • ATM Software Configuration and Command Reference—Catalyst 5000 Family and Catalyst 6500 Series Switches • System Message Guide—Catalyst 6500 Series, 5000 Family, 4000 Family, 2926G Series, 2948G, and 2980G Switches • For information about MIBs, refer to http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.
Obtaining Technical Assistance Ordering Documentation You can find instructions for ordering documentation at this URL: http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm You can order Cisco documentation in these ways: • Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace: http://www.cisco.com/en/US/partner/ordering/index.shtml • Nonregistered Cisco.
Obtaining Additional Publications and Information Opening a TAC Case The online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.
Obtaining Additional Publications and Information • Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources.
Obtaining Additional Publications and Information This document is to be used in conjunction with the documents listed in the “Related Documentation” section. CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.
Obtaining Additional Publications and Information Release Notes for Catalyst 6500 Series Content Switching Module Software Release 2.
