Traffic Classifications

Traffic classifications allows users to apply a network policy (defined in the policy.conf within the configuration archive for a traffic processor group) to a portion of traffic. Additionally, users are able to collect detailed flow statistics for that subset of traffic.

• Log into the Management System at https:{MS_IP} with superadmin credentials provided by Cisco.
• From the Platform menu, select Settings and Traffic Classification.

• Click on Create Traffic Classification for {Traffic Processor Group Name} of the desired group of traffic processors to configure.

• Configure the following sections and then click on Create.

Configuration

This section contains all the network policies that can be applied and the ability to collect statistics. It’s required to fill out the Policy and the Tag fields.

Make sure to set the Tag name to something to identify the data flows for this classification.

Alternate Policy

This is an optional configuration. This section enables users to alternate between the policy defined in the Configuration section and this Alternate Policy at a predefined interval (15-minute, 30-minute, or 60-minute interval) for a configurable time window. After this time window ends, the original policy in Configuration will be applied.

Identifier(s)

Users can set one or more traffic identifiers when creating or editing based on:

• Priority: Determines the order in which traffic classifications are evaluated. Higher priority classifications (indicated by a smaller priority value, with 0 being the highest) that match a traffic flow will have their flow control policies applied, overriding lower priority classifications. The default classification should always have the lowest priority to ensure other classifications’ policies are applied as intended.

• Type: Specifies whether the policy applies to ALL traffic or is specific to a PROTOCOL.

• Policy: The flow control policy to be applied to traffic flows that match this classification and do not match any higher priority classifications. Available policies are defined in the group’s configuration on the Software page.

• Identifiers: The criteria used to match traffic flows to this classification. These can include source IP address, destination port, transport protocol, and other parameters. Expanding the column displays the identifier type and its values.
  Users can configure one or more traffic identifiers based on:

  1. Source IPv4: The IPv4 address of the originating device.
  2. Destination IPv4: The IPv4 address of the target server.
  3. Source IPv6: The IPv6 address of the originating device.
  4. Destination IPv6: The IPv6 address of the target server.
  5. Protocol: The network protocol:
     • TCP
     • UDP
     • QUIC
  6. Hostname: The hostname of the destination server.
  7. Direction: Classifies traffic flow as uplink or downlink based on per-direction thresholds:
     • uplink
     • downlink
     • Frequency Band (MHz)
     • Bandwidth (MHz)

  If MPC is enabled, the following identifiers can be configured:

    - APN
    - eNodeB IP
    - ECI
    - QCI
    - DSCP
  

  For network troubleshooting on specific devices, the following identifiers can be configured if enabled by Cisco:

    - IMSI
    - MEI
    - MSISDN
  

  In wireline deployments, the following identifiers can be configured:

    - Subscriber Class
    - Subscriber Location
  

  At least one identifier must be configured to create a traffic classification. Note that a traffic flow must match all defined identifier rules within a classification to be associated with that classification.

• Tag: A unique, user-defined name for the traffic classification.

• Alternate Policy: An optional secondary policy type to be activated and deactivated at specified time intervals within a defined date range.

• Flow Network Optimization Enabled: An indicator (On/Off) for the collection of flow network optimization statistics for traffic matching this classification.

• Elephant Trace Enabled: An indicator (On/Off) for the collection of elephant flow statistics for traffic matching this classification.

At least one identifiers needs to be configured in order to create a traffic classification. Note that only traffic matching ALL identifier rules defined in a given traffic classification will match to the traffic classification.

After all required fields are filled out, the Create button will become available to click to add the traffic classification to the table.

Traffic Classification Page

Edit an existing Traffic Classification

To modify an existing classification, select it from the list and choose EDIT. Both actions will navigate you to the following page:

Creating and Editing Classifications Options

Complete the Configuration, Identifier(s), and optionally the Alternate Policy sections. Select Save to apply changes to an existing one. You can also reorder existing classification priorities by dragging and dropping each classification to its desired position in the list.

Delete an existing Traffic Classification

To remove classifications, select the target classification(s) and select the DELETE option.

NOTE: The APPLY CHANGES button is used to send the changes to the traffic processors after traffic classifications have been created or updated or deleted. If you do not click the APPLY CHANGES button, the changes will not take effect.

Apply changes