enabled modules, and one nonfabric-enabled module: 6509-2# - sho mod Mod Ports Card Type Model Serial No. 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL04654F2K 8 Network Analysis Module WS-SVC-NAM-2 SAD093002B6 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL0485498A 2 Supervisor Engine 720 (Hot) WS-SUP720-3B SAL09358NE6 6 Firewall Module WS-SVC-FWM-1 SAD042408DF 4 CSM with SSL WS-X6066-SLB-S-K9 SAD094107YN 8 Intrusion Detection System WS-SVC-IDSM-2 SAD048102CG The module in slot 1 is the same as the Ethernet modules in the previous example. This module is fabric-only. Modules 4, 7, and 9 are all fabric-enabled, while module 8 is nonfabric-enabled. The output from the show fabric switching-mode command reveals that the single nonfabric-enabled blade has caused the supervisor to revert to a slower operating mode: 6509-2# sho fabric switching-mode Global switching mode is Truncated dCEF mode is not enforced for system to operate Fabric module is not required for system to operate Modules are allowed to operate in bus mode Truncated mode is allowed, due to presence of aCEF720, Standby supervisor module Module Slot Switching Mode Crossbar Crossbar Crossbar Crossbar Crossbar In this case, the module in question is a CSM, and is one of the more expensive modules available. Remember that cost does not equate to speed. The CSM is an excellent device, and I highly recommend it for situations where load balancing is a necessity, but in the case of extremely high throughput requirements, the service module may become a bottleneck. In the case of web site architecture, it would be extremely rare for more than 32 Gbps to be flowing through the frontend. Such throughput would be possible in the case of balancing large application server farms or databases on the backend. Using the show fabric status command on this switch indicates that not all fabric- enabled modules are created equal. The fabric-only module in slot 1 has two 20 Gbps channels to the fiber bus. The NAM in slot 4 is fabric-enabled, but only conne