Datasheet

© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 5 of 14
The reboot progress of the service module will be reported through two different Cisco IOS Software SysLog
messages:
%PLATFORM_SM10G-3-NO_RESPONSE is shown right after the service module reload is executed and
simultaneously with all interface link up-down events pertaining to the service module itself.
%PLATFORM-6-FRULINK_INSERTED: occurs about 20 seconds after the previous event and indicates the
service module software is activated. Interface up-down events usually follow in about 5 seconds. At this
stage the service module is able to perform all of its networking functionalities but Flexible NetFlow.
%PLATFORM_SM10G-6-LINK_UP: occurring in about 3 minutes from the previous event, indicates that the
service module is able to operate normally in all its functions, including Flexible NetFlow.
3. The service module status can be also retrieved by executing the Cisco IOS Software command “show switch
service-modules.”
Additional information on updating a stack with archive download-sw can be found in the Cisco Catalyst 3560-X
and 3750-X configuration guides.
Architecture Overview
The service module is designed with the objective of providing intelligent applications such as Flexible NetFlow
without affecting switch forwarding and processor (CPU) performances. In this perspective, a new programmable
application-specific integrated circuit (ASIC) with Flexible NetFlow analysis capabilities connects to data lines in the
switch port ASIC dedicated to uplink ports, and a new CPU is responsible for various Flexible NetFlow tasks other
than interacting with the switch CPU and controlling the service module ASIC.
The service module ASIC is the Flexible NetFlow engine performing traffic analysis for each flow monitor. Statistics
reside in the ASIC cache, which can store a total number of 32K flows shared across flow monitors.
The Flexible NetFlow software process running on the service module CPU consists of several components
performing the following tasks.
The service module ASIC controller receives the Cisco IOS Software Flexible NetFlow configuration from the
switch CPU running Cisco IOS Software and programs the service module ASIC accordingly.
The Flexible NetFlow process maintains a database of flow statistics cache for the purpose of flow aging and
serving queries coming through Cisco IOS Software CLI “show flow monitor <name> cache” commands.
Periodically every 30 seconds it sends flow records statistics to the switch CPU.
The exporter component handles the flow-aging mechanism and sends expired flow statistics to the configured
collectors. Flow export packets are sent to the switch ASIC, which performs the forwarding action (Figure 1).