Default Service Configuration Reference Tables
Introduction
This chapter describes the default service configuration provided with Cisco SCA BB. The default service configuration serves as a starting point for creating a service configuration tailored to meet customer needs.
Filter Rules
Filter rules allow you to instruct the Cisco SCE platform to ignore some types of flow based on Layer 3 and Layer 4 properties of the flow, and transmit the flows without any changes.
Table 1-1 lists the filter rules defined in the default service configuration.
Information About Protocols
Protocols are divided into four groups:
- Generic protocols—Protocols that are used for transactions not mapped to a service by one of the more specific protocol types.
- Signature-based protocols—Protocols that are classified according to a Layer 7 application signature. This group includes the most common protocols, such as HTTP and FTP, and a large group of popular Peer-to-Peer protocols.
- IP protocols—Protocols (such as ICMP), other than TCP and UDP protocols that are identified according to the IP protocol number of the transaction.
- Port-based protocols—TCP and UDP protocols that are classified according to their well-known ports. The default configuration includes more than 600 common port-based protocols.
You may add new protocols (for example, to classify a new gaming protocol that uses a specific port) and edit or remove existing ones.
In Cisco SCA BB Console, protocols are listed in ASCII order.
The tables in the following sections list the protocols defined in the default service configuration:
- Generic Protocols
- Signature-Based Protocols
- IP Protocols
- Port-Based Protocols
- Protocols Identified on Unidirectional Flows
Generic Protocols
Three generic protocols (IP, TCP, and UDP) serve as default containers for classifying transactions of the relevant type (IP, TCP, or UDP) that are not classified as belonging to a more specific protocol.
A transaction is classified as belonging to one of the generic protocols if it meets both the following conditions:
- It was not classified as belonging to a signature-based protocol.
- It was not classified as belonging to an IP or port-based protocol that is mapped to a service.
Table 1-2 list the generic protocols.
Signature-Based Protocols
A transaction is classified as belonging to one of the signature-based protocols if it is carried on the well-known port of the protocol or matches the signature of the protocol.

Note Table 1-3 lists only signature-based protocols that are not Peer-to-Peer, VoIP, or SIP protocols (these protocols are listed in the following tables). However, the Signature-Based Protocols Filter in the Console lists all signature-based protocols.

Note Behavioral Upload/Download—Transactions that have download packet flow characteristics and do not match a more specific signature are classified to this protocol. This protocol applies to downloads both from the network side and from the subscriber side.

Note Generic Non-Established TCP—IPv4 TCP flows that are not established properly (syn-ack is missing) are mapped to this protocol.
Table 1-4 lists the signature-based peer-to-peer protocols.
|
|
|
|
---|---|---|---|
Table 1-5 lists the signature-based VoIP protocols.
|
|
|
|
---|---|---|---|

Note The protocols ICQ VoIP, Primus, SIP, and Yahoo VoIP over SIP are also signature-based SIP protocols.
IP Protocols
Table 1-6 lists the IP protocols supported by Cisco SCA BB.
|
|
|
---|---|---|
Port-Based Protocols
Table 1-7 lists the TCP/UDP port-based protocols defined in the Cisco SCA BB default service configuration.
|
|
|
|
---|---|---|---|
Protocols Identified on Unidirectional Flows
When unidirectional classification is enabled, the protocols listed in Table 1-8 can be detected on unidirectional flows.
- When a unidirectional flow (inbound or outbound) passes through the SCE platform, it is matched against this set of protocol signatures.
- When a bidirectional flow passes through the SCE platform, the protocol library tries to match it to one of its standard (bidirectional) protocol signatures.
|
|
---|---|
Services
Services are the building blocks of service configurations. Classification of a transaction to a service determines the accounting and control that apply to the corresponding transaction. Services are organized in an hierarchal structure used for both accounting and control.
Table 1-9 lists the services defined in the default service configuration. Two service usage counters, Global Usage Counter and Subscriber Usage Counter, are used to accumulate information about the transactions classified under each service. Both these counter have the same name.
An asterisk is appended to a service usage counter name whenever the counter applies to more than one service.
RDR Settings
The Cisco SCE platforms generate and transmit Raw Data Records (RDRs) that contain a wide variety of information and statistics, depending on the configuration of the system.
Table 1-10 lists the RDR settings defined in the default service configuration.
|
|
|
|
|
|
---|---|---|---|---|---|
Default is ON for service configurations created in Virtual Links mode. |
|||||
Rules
Rules are a set of configurable instructions telling the application how to handle flows classified to a service.
The default service configuration contains a single rule for the default service. Until you create other rules, the default service rule applies to all traffic processed by the SCE platform.
System Mode
The default System Operational Mode is Report Only, which means that the system is used for reporting but does not control traffic.
The default System Topological Mode is Duplex, which means that all inbound and outbound traffic go through the SCE platform.

Note When unidirectional classifications enabled, there are some changes to the default service configuration:
- There are no predefined flavors.
- No service elements include a specified flavor.
- Periodic quota management mode is selected.