All TODR attributes of traffic optimization is enabled by a single CLI command. The output is always comma separated, and in a rigid format.

Standard TODR

The following is the format of a Standard TODR:

instance_id,flow_type,srcIP,dstIP,policy_id,dscp,
flow_first_pkt_rx_time_ms,flow_last_pkt_rx_time_ms,flow_cumulative_rx_bytes

Example:

1,0,173.39.13.38,192.168.3.106,0,0,
 1489131332693,1489131335924,342292

Where:

• instance_id: Instance ID.

• flow_type: Standard flow (0)

• srcIP: Indicates the source IP address.

• dstIP: Indicates the destination IP address.

• policy_id: Indicates the traffic optimization policy ID.

• dscp: Indicates the DSCP code for upstream packets.

• flow_first_pkt_rx_time_ms: Indicates the timestamp when the first packet was detected during traffic optimization.

• flow_last_pkt_rx_time_ms: Indicates the timestamp when the last packet was detected during traffic optimization.

• flow_cumulative_rx_bytes: Indicates the number of bytes transferred by this flow.

Large TODR

The following is a sample output of a Large TODR.

2,1,2606:ae00:c663:b66f:0000:0058:be03:ae01,0172:0020:0224:0059:2200:0000:0000:0033,0,0,
1489572442058,1489572444759,5051223,1489572444755,3900,3900,0,0,0,11,0,0,11,1,1,
1489572444755,1950,4,0,0,1,1489572446761,0,2010,0,0,1,1489572448771,0,2007,0,0,1,1489572450778,0,2008,
0,0,1,1489572452786,0,2005,0,0,1,1489572454791,0,2003,0,0,1,1489572456794,0,2005,0,0,1,1489572458799,0,
2003,0,0,1,1489572460802,0,1848,0,0,0,1489572462650,0,2002,0,0,1,1489572464652,0,107,0,0

Where:

• instance_id: Instance ID.

• flow_type: Large flow (1)

• srcIP: Indicates the source IP address.

• dstIP: Indicates the destination IP address.

• policy_id: Indicates the traffic optimization policy ID.

• dscp: Indicates the DSCP code for upstream packets.

• flow_first_pkt_rx_time_ms: Indicates the timestamp when the first packet was detected during traffic optimization.

• flow_last_pkt_rx_time_ms: Indicates the timestamp when the last packet was detected during traffic optimization.

• flow_cumulative_rx_bytes: Indicates the number of bytes transferred by this flow.

• large_detection_time_ms: Indicates the timestamp when the flow was detected as Large.

• avg_burst_rate_kbps: Indicates the average rate in Kbps of all the measured bursts.

• avg_eff_rate_kbps: Indicates the average effective rate in Kbps.

• final_link_peak_kbps: Indicates the highest detected link peak over the life of the Large flow.

• recovered_capacity_bytes: Indicates the recovered capacity in Kbps for this Large flow.

• recovered_capacity_ms: Indicates the timestamp of recovered capacity for this Large flow.

• phase_count: Indicates the Large flow phase count.

• min_gbr_kbps: Indicates the Minimum Guaranteed Bit Rate (GBR) in Kbps.

• max_gbr_kbps: Indicates the Maximum Guaranteed Bit Rate (MBR) in Kbps.

• phase_count_record: Indicates the number of phases present in this record.

• end_of_phases: 0 (not end of phases) or 1 (end of phases).

• Large flow phase attributes:

  • phase_type: Indicates the type of the phase

  • phase_start_time_ms: Indicates the timestamp for the start time of the phase.

  • burst_bytes: Indicates the burst size in bytes.

  • burst_duration_ms: Indicates the burst duration in milliseconds.

  • link_peak_kbps: Indicates the peak rate for the flow during its life.

  • flow_control_rate_kbps: Indicates the rate at which flow control was attempted (or 0 if non-flow control phase).

The any-match = TRUE, a wildcard configuration, is the only supported condition for this trigger and so this is applicable to all the flows of the subscriber.

Following is a sample configuration:

configure
    active-charging service service_name
        trigger-action trigger_action_name
            traffic-optimization
            exit
        trigger-condition trigger_condition_name1
            any-match = TRUE
            exit
        service-scheme service_scheme_name
            trigger sess-setup
                priority priority_value trigger-condition trigger_condition_name1 trigger-action trigger_action_name
                exit
        subs-class sub_class_name
            apn = apn_name
            exit
        subscriber-base subscriber_base_name
            priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name
            end

The trigger conditions related to QCI can be used for this trigger, and so this is applicable to all the flows of specific bearers.

The following is a sample configuration:

configure
    active-charging service service_name
        trigger-action trigger_action_name
            traffic-optimization
            exit
        trigger-condition trigger_condition_name1
            any-match = TRUE
            exit
        trigger-condition trigger_condition_name2
            qci = qci_value
            exit
        service-scheme service_scheme_name
            trigger bearer-creation
                priority priority_value trigger-condition trigger_condition_name2 trigger-action trigger_action_name
                exit
            exit
        subs-class sub_class_name
            apn = apn_name
            exit
        subscriber-base subscriber_base_name
            priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name
            end

The trigger conditions related to rule-name and QCI can be used here, and so this is related to specific flow.

The following is a sample configuration:

configure
    active-charging service service_name
        trigger-action trigger_action_name
            traffic-optimization
            exit
        trigger-condition trigger_condition_name1
            any-match = TRUE
            exit
        trigger-condition trigger_condition_name2
            qci = qci_value
            exit
        trigger-condition trigger_condition_name3
            rule-name = rule_name
            exit
        service-scheme service_scheme_name
            trigger bearer-creation
                priority priority_value trigger-condition trigger_condition_name3 trigger-action trigger_action_name
                exit
            exit
        subs-class sub_class_name
            apn = apn_name
            exit
        subscriber-base subscriber_base_name
            priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name
            end

Notes:

• trigger_condition_name3 can have only rules, only QCI, both rule and QCI, or either of rule and QCI.

The following table illustrates the different levels of Traffic Optimization and their corresponding Subscriber Class configuration and Triggers.

subs-class sc1
    any-match = TRUE
    exit

subs-class sc1
    rulebase = prepaid
    exit

subs-class sc1
    apn = cisco.com
    exit

trigger-condition TC1
    qci = 1
    exit

trigger-condition TC1
    qci = 1
    rule-name = tcp
    multi-line-or all-lines
    exit

The output of this show command has been enhanced to display if the UDP traffic optimization is Enabled or Disabled. Following are the fields that has been introduced:

• Traffic Optimization:

  • UDP: Enabled/Disabled

The show active-charging traffic-optimization counters sessmgr { all | instance number } CLI command is introduced where:

• counters – Displays aggregate flow counters/statistics from CUTO engine.

Following are the new field/counters:

• Traffic Optimization Flows:

  • Active Normal Flow Count:

  • Active Large Flow Count:

  • Active Managed Large Flow Count:

  • Active Unmanaged Large Flow Count:

  • Total Normal Flow Count:

  • Total Large Flow Count:

  • Total Managed Large Flow Count:

  • Total Unmanaged Large Flow Count:

  • Total IO Bytes:

  • Total Large Flow Bytes:

  • Total Recovered Capacity Bytes:

  • Total Recovered Capacity ms:

This show command has been introduced in Exec Mode, where:

• traffic-optimization – Displays all traffic optimization options.

• info – Displays CUTO engine information.

The output of this CLI command displays the version, mode, and configuration values.

Following are the new fields/counters:

• Version:

• Mode:

• Configuration:

  • Threshold Bytes:

  • Lower Bandwidth:

  • Upper Bandwidth:

  • Min Session Time:

  • Min Session Size: