The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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 allow you to instruct the SCE platform to ignore some types of flow based on Layer 3 and Layer 4 properties of the flow, and transmit the flows unchanged.
Table 1-1 lists the filter rules defined in the default service configuration.
Protocols are divided into four groups:
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:
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:
Table 1-2 list the generic 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.
|
|
|
|
---|---|---|---|
|
|
|
|
---|---|---|---|
Note The protocols ICQ VoIP, Primus, SIP, and Yahoo VoIP over SIP are also signature-based SIP protocols.
Table 1-6 lists the IP protocols supported by Cisco SCA BB.
|
|
|
---|---|---|
Table 1-7 lists the TCP/UDP port-based protocols defined in the Cisco SCA BB default service configuration.
|
|
|
|
---|---|---|---|
When unidirectional classification is enabled, the protocols listed in Table 1-8 can be detected on unidirectional flows.
|
|
---|---|
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.
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 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.
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.