Contents

1   Commands

This document provides command syntax and usage guidelines for commands used in the configuration and operation of application traffic management. For an overview of application traffic management, see Reference [1]. For configuration tasks, see Reference [2].

1.1   access-group

access-group acl-name

no access-group

1.1.1   Command Mode

DPI policy configuration

1.1.2   Syntax Description

1.1.3   Default

None

1.1.4   Usage Guidelines

Associates a DPI traffic management policy with a DPI access control list.

1.1.5   Examples

[local]Redback(config-policy-dpi)#access-group myacl

1.2   action policy

action policy action-policy-name

no action policy [action-policy-name]

1.2.1   Command Mode

DPI policy configuration

1.2.2   Syntax Description

1.2.3   Default

No DPI traffic management action policy is configured.

1.2.4   Usage Guidelines

Associates a DPI traffic management policy with a DPI traffic management action policy.

1.2.5   Examples

[local]Redback(config-policy-dpi)#action policy a1

1.3   application

[seq sequence-number] application application-name [network network-prefix/prefix-length | any] class class-name

no seq sequence-number

1.3.1   Command Mode

DPI access control list configuration

1.3.2   Syntax Description

1.3.3   Default

None

1.3.4   Usage Guidelines

Creates an ACL statement to allow packets that meet the specified criteria. Use the CLI help with this command (application ?) or issue the show dpi traffic-management application command in any mode for a list of application names. If the seq sequence-number construct is not specified, the system assigns a sequence number.

1.3.5   Examples

[local]Redback(dpi-acl)#seq 10 application bittorrent class c1

[local]Redback(dpi-acl)#seq 40 application skype class c3

[local]Redback(dpi-acl)#application youtube class c5

1.4   category

[seq sequence-number] category category-name [network network-prefix/ prefix-length | any] class class-name

no seq sequence-number

1.4.1   Command Mode

DPI access control list configuration

1.4.2   Syntax Description

1.4.3   Default

None

1.4.4   Usage Guidelines

Creates an ACL statement to allow packets that meet the specified criteria. If seq sequence-number is not specified, the system assigns a sequence number.

Table 1 lists the valid keyword substitutions for the category-name argument.

1.4.5   Examples

[local]Redback(dpi-acl)#seq 20 category streaming network 1.1.1.0/24 class c1
[local]Redback(dpi-acl)#category gaming network 4.1.1.0/24 class c2 

1.5   class

class class-name

no class class-name

1.5.1   Command Mode

DPI action configuration

1.5.2   Syntax Description

1.5.3   Default

None

1.5.4   Usage Guidelines

Creates a class entry that defines actions applied to traffic mapped to a class. Allows different QoS policies to be applied to different sets (classes) of flows that are defined in the applied policy Access Control List (ACL).

If the class-name argument referenced by an ACL rule matches the class name in an action policy, the classified traffic is processed according to the class definition. If a rule for the class-name argument is not specified in the ACL policy, the class-based policy considers the class to be dormant and takes no action. If a rule for the class-name argument is specified in the ACL, but you do not include the class in the action policy (using this command), the SmartEdge® OS considers those packets to be in the default class.

1.5.5   Examples

[local]Redback(config-dpi-action)#class c0

1.6   clear dpi asp traffic-management statistics

clear dpi asp slot/port traffic-management statistics

1.6.1   Command Mode

exec

1.6.2   Syntax Description

1.6.3   Usage Guidelines

Clears all peak counters and all packet/byte counters.

1.6.4   Examples

[local]Redback#clear dpi asp 2/1 traffic-management statistics

1.7   clear dpi circuit traffic-management sessions

clear dpi circuit {agent-circuit-id agent-circuit-id | agent-remote-id agent-remote-id | slot/port[:chan-num[:sub-chan-num] circuit-id | username subscriber} traffic-management sessions

1.7.1   Command Mode

exec

1.7.2   Syntax Description

1.7.3   Usage Guidelines

Clears all the traffic management sessions for the specified subscriber.

The circuit-id argument represents the following keywords and arguments; see Table 2.

clips [clips-session] | pppoe [pppoe-session] | vlan-id vlan-id [pppoe [pppoe-session] | clips [clips-session]] | vpi-vci vpi vci [pppoe [pppoe-session] | clips [clips-session]]

1.7.4   Examples

[local]Redback#clear dpi circuit username joe@local traffic-management sessions 

1.8   clear dpi circuit traffic-management statistics

clear dpi circuit {agent-circuit-id agent-circuit-id | agent-remote-id agent-remote-id | slot/port[:chan-num[:sub-chan-num] circuit-id | username subscriber} traffic-management statistics

1.8.1   Command Mode

exec

1.8.2   Syntax Description

1.8.3   Usage Guidelines

Clears all peak counters and all packet/byte counters for the specified subscriber.

1.8.4   Examples

[local]Redback#clear dpi circuit username joe@local traffic-management statistics 

1.9   conform mark dscp

conform mark dscp dscp-class

no conform mark dscp

1.9.1   Command Mode

DPI QoS profile rate configuration

1.9.2   Syntax Description

1.9.3   Default

No action is taken on packets that conform to the configured rate.

1.9.4   Usage Guidelines

Marks packets that conform to the configured Quality of Service (QoS) rate with a Differentiated Services Code Point (DSCP) value.

You can configure the rate using the rate command. Only one mark instruction can be in effect at a time. To change the mark instruction, enter the conform mark dscp command, specifying a new value for the dscp-class argument, which supersedes the one previously configured.

Table 4 lists the keywords for the dscp-class argument.

For more information about DSCP values, see RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers.

1.9.5   Examples

The following example configures the DPI, qos_prof_01, to mark all packets that conform to the configured rate with a DSCP value representing a high priority of expedited forwarding (ef):

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#conform mark dscp ef 

1.10   conform mark precedence

conform mark precedence prec-value

no conform mark precedence

1.10.1   Command Mode

DPI QoS profile rate configuration

1.10.2   Syntax Description

1.10.3   Default

No action is taken on packets that conform to the configured rate.

1.10.4   Usage Guidelines

Marks packets that conform to the configured QoS rate with a drop precedence value corresponding to the Assured Forwarding (AF) class of the packet.

You configure the QoS rate by using the rate command.

In general, the level of forwarding assurance of an IP packet is based on:

• Resources allocated to the AF class to which the packet belongs
• Current load of the AF class, and, in case of congestion within the class
• Drop precedence of the packet. In case of congestion, the drop precedence of a packet determines the relative importance of the packet within the AF Differentiated Services Code Point (DSCP) class

Packets with a lower drop precedence value are preferred and protected from being lost, and packets with a higher drop precedence value are discarded.

With AF classes AF1 (AF11, AF12, AF13), AF2 (AF21, AF22, AF23), AF3 (AF31, AF32, AF33), and AF4 (AF41, AF42, AF43), the second integer represents a drop precedence value. Table 5 shows how the AF drop precedence value of an incoming packet is changed when it exits the SmartEdge router after being tagged with a new drop precedence. (See also RFC 2597, Assured Forwarding PHB Group.)

Only one mark instruction can be in effect at a time. To change the mark instruction, enter the conform mark precedence command, specifying a new value for the prec-value argument, which supersedes the one previously configured.

1.10.5   Examples

The following example configures the DPI QoS profile qos_prof_01 to mark all packets that conform to the configured rate with a drop precedence value of 1 and drops all packets that exceed the rate:

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#conform mark precedence 1 

1.11   conform mark priority

conform mark priority {group-num | ignore} [{drop-precedence {group-num | ignore} | af-drop drop-value}]

no conform mark priority

1.11.1   Command Mode

DPI QoS profile rate configuration

1.11.2   Syntax Description

1.11.3   Default

No action is taken on packets that conform to the configured rate. Default mapping of priority groups to queues is listed in Table 6.

1.11.4   Usage Guidelines

Marks packets that conform to the configured QoS rate with a priority group number, a drop-precedence value, or both, while leaving the packet’s IP header DSCP value unmodified. To configure the QoS rate rate, enter the rate command.

A priority group is an internal value used by the SmartEdge OS to determine into which egress queue the inbound packet is placed. The Type of Service (ToS) value, DSCP value, and Multiprotocol Label Switching (MPLS) experimental (EXP) bits are unchanged by this command. The actual queue number depends on the number of queues configured on the egress circuit.

The SmartEdge OS uses the factory preset or default mapping of a priority group to queue, according to the number of queues configured on a circuit; see Table 6.

Only one mark instruction can be in effect at a time. To change the mark instruction, enter the conform mark priority command, specifying a new value for the group-num argument. This supersedes the value previously configured.

1.11.5   Examples

The following example configures the policy to mark all packets that conform to the configured rate with priority group number 3 and drops all packets that exceed the rate:

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#conform mark priority 3 

1.12   debug dpi asp traffic-management

debug dpi asp slot/asp-id traffic-management message-type trace {buffer | console | external} [level level]

1.12.1   Command Mode

exec

1.12.2   Syntax Description

1.12.3   Usage Guidelines

Enables the generation of debug messages for the traffic management application on a specific ASE card.

Separate levels and message-types can be configured for the console and an external log server.

1.12.4   Examples

[local]Redback#debug dpi asp 1 / 2 traffic-management all log console level alert

1.13   default-class

default-class class-name

no default-class

1.13.1   Command Mode

DPI action configuration

DPI access control list configuration

1.13.2   Syntax Description

1.13.3   Default

No default class is configured.

1.13.4   Usage Guidelines

Specifies a class to use to map all traffic that is not otherwise classified. The default class defined in the DPI ACL policy is used to map all traffic that was not classified into one of the classes defined in the DPI ACL policy. The default class defined in the DPI action policy is used to map all traffic assigned to a class that is not defined in the action policy.

1.13.5   Examples

[local]Redback(config-dpi-action)#default-class default

1.14   dpi access-list

dpi access-list acl-name

no dpi access-list acl-name

1.14.1   Command Mode

global configuration

1.14.2   Syntax Description

1.14.3   Default

No DPI ACL policy is configured.

1.14.4   Usage Guidelines

Creates or selects a DPI ACL policy and enters DPI access control list configuration mode.

1.14.5   Examples

[local]Redback(config)#dpi access-list b1

1.15   dpi qos profile

dpi qos profile profile-name [policing | metering]

no dpi qos profile profile-name [policing | metering]

1.15.1   Command Mode

global configuration

1.15.2   Syntax Description

1.15.3   Default

No DPI is configured.

1.15.4   Usage Guidelines

Creates or selects a DPI QoS profile and enters DPI QoS profile configuration mode. If policing or metering is not specified, a bidirectional QoS profile is implied.

1.15.5   Examples

[local]Redback(config)#dpi qos profile q1

[local]Redback(config)#dpi qos profile q2 policing

1.16   dpi traffic-management action policy

dpi traffic-management action policy name

no dpi traffic-management action policy name

1.16.1   Command Mode

global configuration

1.16.2   Syntax Description

1.16.3   Default

No DPI traffic management action policy is configured.

1.16.4   Usage Guidelines

Creates or selects a DPI traffic management action policy and enters DPI action configuration mode.

1.16.5   Examples

[local]Redback(config)#dpi traffic-management action policy a1

1.17   dpi traffic-management maximum sessions

dpi traffic-management maximum sessions max-sessions [exceed class class-name]

no dpi traffic management maximum sessions max-sessions [exceed class class-name]

1.17.1   Command Mode

global configuration

1.17.2   Syntax Description

1.17.3   Default

Session limiting is disabled by default. When session limiting is enabled, the default action is to drop all packets associated with sessions that exceed the allowed maximum value.

1.17.4   Usage Guidelines

Enables subscriber session limiting and specifies the maximum number of allowed sessions per subscriber. In addition, specifies whether packets associated with sessions that exceed the session limit are dropped, or mapped to an action policy class. The no form of this command disables subscriber session limiting.

1.17.5   Examples

[local]Redback(config)#dpi traffic-management maximum sessions 300 exceed class cl_01

1.18   dpi traffic-management policy

dpi traffic-management policy {default | policy-name}

no dpi traffic-management policy {default | policy-name}

no dpi traffic-management policy

1.18.1   Command Mode

global configuration

subscriber configuration

1.18.2   Syntax Description

1.18.3   Default

No DPI traffic management policy is configured.

1.18.4   Usage Guidelines

In global configuration mode, creates or selects a DPI traffic management policy and enters DPI policy configuration mode.

In subscriber configuration mode, applies a DPI traffic management policy to a subscriber, default subscriber, or subscriber profile.

1.18.5   Examples

Create the DPI traffic management policy p1.

(config)#dpi traffic-management policy p1

Apply the DPI traffic management policy p1 to subscriber joe.

[isp1]Redback(config-ctx)#subscriber name joe
[isp1]Redback(config-sub)#dpi traffic-management policy p1

1.19   dpi traffic-management resource-failure-action

dpi traffic-management resource-failure-action drop

no dpi traffic-management resource-failure-action

1.19.1   Command Mode

global configuration

1.19.2   Syntax Description

1.19.3   Default

Application traffic bypasses the failed ASP and continues to forward subscriber traffic.

1.19.4   Usage Guidelines

Drops application traffic when a resource fails. Use the no form of the command to bypass the ASP and continue to forward subscriber traffic in the event of a resource failure.

1.19.5   Examples

[local]Redback(config)#dpi traffic-management resource-failure-action drop

1.20   dpi traffic-management signature-file

dpi traffic-management signature-file sig-filename

no dpi traffic-management signature-file

1.20.1   Command Mode

global configuration

1.20.2   Syntax Description

1.20.3   Default

The SmartEdge uses the built-in signature file.

1.20.4   Usage Guidelines

Use the dpi traffic-management signature-file command to configure a signature file to use for DPI traffic-management. You cannot configure a signature-file, if it does not support the rules in an existing DPI access-list.

Use the no form of the command to use the default (built-in) signature file.

Signature-file names are in the format, App-Name-Major-Minor.sdf

Where:

App-Name is the Application name, such as P2P.

Major is the DPI Engine Major Number; the value must be equal to or less than the current installed DPI Engine version.

Minor is the signature-file release number.

sdf is the file extension, which stands for Signature Definition File.

For example, P2P-3-1.sdf is a signature file about P2P applications for DPI engine 3, release 1.

1.20.5   Examples

[local]Redback(config)#dpi traffic-management signature-file p2p-3-1.sdf

1.21   dpi traffic-management statistics

dpi traffic-management statistics [interim-interval minutes]

{no | default} dpi traffic-management statistics [interim-interval minutes]

1.21.1   Command Mode

global configuration

1.21.2   Syntax Description

1.21.3   Default

Statistics reporting is disabled by default. When statistics reporting is enabled, the default interim-interval is 15 minutes.

1.21.4   Usage Guidelines

Enables statistics reporting and configures the frequency to send statistics to an external server. The no form of this command disables reporting.

1.21.5   Examples

[local]Redback(config)#dpi traffic-management statistics interim-interval 30

1.22   exceed drop

exceed drop

no exceed drop

1.22.1   Command Mode

DPI QoS profile rate configuration

1.22.2   Default

All packets exceeding the QoS rate and burst tolerance are dropped.

1.22.3   Usage Guidelines

Specifies how packets are dropped when the traffic rate exceeds the QoS rate and burst tolerance.

Configure the traffic rate and burst tolerance with the rate command.

1.22.4   Examples

The following example drops packets that exceed the traffic rate and burst tolerance:

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#exceed drop 

1.23   exceed mark dscp

exceed mark dscp dscp-class

no exceed mark dscp

1.23.1   Command Mode

DPI QoS profile rate configuration

1.23.2   Syntax Description

1.23.3   Default

Packets that exceed the configured rate are dropped.

1.23.4   Usage Guidelines

Marks packets that exceed the configured QoS rate and burst tolerance with a DSCP value.

To configure the rate, enter the rate command. Only one mark instruction can be in effect at a time. To change the mark instruction, enter the exceed mark dscp command, specifying a new value for the dscp-class argument. This supersedes the one previously configured.

Table 4 lists the keywords for the dscp-class argument.

For more information about DSCP values, see RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers.

Use the no or default form of this command to return to the default behavior of not taking any action on packets that conform to the configured rate.

1.23.5   Examples

The following example configures the DPI, qos_prof_01, to mark all packets that exceed the configured rate with a DSCP value representing a high priority of expedited forwarding (ef):

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#exceed mark dscp ef 

1.24   exceed mark precedence

exceed mark precedenceprec-value

no exceed

1.24.1   Command Mode

DPI QoS profile rate configuration

1.24.2   Syntax Description

1.24.3   Default

Packets that exceed the configured rate are dropped.

1.24.4   Usage Guidelines

Marks packets that exceed the configured QoS rate with a drop precedence value corresponding to the AF class of the packet.

To configure the rate, enter the rate command.

In general, the level of forwarding assurance of an IP packet is based on: (1) the resources allocated to the AF class to which the packet belongs, (2) the current load of the AF class, and, in case of congestion within the class, (3) the drop precedence of the packet. In case of congestion, the drop precedence of a packet determines the relative importance of the packet within the AF class. Packets with a lower drop precedence value are preferred and protected from being lost, and packets with a higher drop precedence value are discarded.

With AF classes AF1 (AF11, AF12, AF13), AF2 (AF21, AF22, AF23), AF3 (AF31, AF32, AF33), and AF4 (AF41, AF42, AF43), the second integer represents a drop precedence value. Table 5 shows how the AF drop precedence value of an incoming packet is changed when it exits the SmartEdge router after being tagged with a new drop precedence. (See also RFC 2597, Assured Forwarding PHB Group.)

Only one mark instruction can be in effect at a time. To change the mark instruction, enter the exceed mark precedence command, specifying a new value for the prec-value argument, which supersedes the one previously configured.

Use the no or default form of this command to return to the default behavior of dropping packets that exceed the rate.

1.24.5   Examples

The following example configures the DPI, qos_prof_01, to mark all packets that exceed the configured rate with an IP precedence value of 3.

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#exceed mark precedence 3 

1.25   exceed mark priority

exceed mark priority {group-num | ignore} [{drop-precedence {group-num | ignore} | af-drop drop-value}]

no exceed mark priority

1.25.1   Command Mode

DPI QoS profile rate configuration

1.25.2   Syntax Description

1.25.3   Default

Packets that exceed the configured rate are dropped.

1.25.4   Usage Guidelines

Marks packets that exceed the QoS rate and burst tolerance with a priority group number, a drop-precedence value, or both, while leaving the packet’s IP header DSCP value unmodified.

To configure the QoS rate, enter the rate command.

A priority group is an internal value used by the SmartEdge OS to determine into which egress queue the inbound packet is placed. The ToS value, DSCP value, and MPLS EXP bits are unchanged by this command. The actual queue number depends on the number of queues configured on the circuit. For more information, see the num-queues command in Reference [3].

The SmartEdge OS uses the factory preset or default mapping of a priority group to queue, according to the number of queues configured on a circuit; see Table 6.

Only one mark instruction can be in effect at a time. To change the mark instruction, enter the exceed mark priority command, specifying a new value for the group-num argument. This supersedes the value previously configured.

Note:  

By default, the SmartEdge OS assigns a priority group to each egress queue, according to the number of queues configured on a circuit. You can override the default mapping of packets into egress queues by creating a customized queue priority map using the qos queue-map command (in global configuration mode).

Use the no or default form of this command to return to the default behavior.

1.25.5   Examples

The following example configures the policy to mark all packets that exceed the configured rate with priority group number 3:

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000
[local]Redback(dpi-qos-rate)#exceed mark priority 3 

1.26   log detection

log detection

no log detection

1.26.1   Command Mode

DPI action class configuration

1.26.2   Default

Log detection is not enabled by default.

1.26.3   Usage Guidelines

Generates a log entry when application or protocol traffic is detected in traffic mapped to the class. Enabling logging may impact performance.

1.26.4   Examples

[local]Redback(config-dpi-action-class)#log detection

1.27   mark dscp

mark dscp dscp-class

no mark dscp dscp-class

1.27.1   Command Mode

DPI QoS profile configuration

1.27.2   Syntax Description

1.27.3   Default

Packets are not assigned a DSCP priority.

1.27.4   Usage Guidelines

Assigns a QoS DSCP priority to packets.

For more information about DSCP values, see RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers.

1.27.5   Examples

The following example configures the DPI qos_prof_02, to mark all packets as high-priority packets:

[local]Redback(config)#dpi qos profile qos_prof_02
[local]Redback(dpi-qos)#mark dscp ef 

1.28   mark precedence

mark precedence prec-value

no mark precedence prec-value

1.28.1   Command Mode

DPI QoS profile configuration

1.28.2   Syntax Description

1.28.3   Default

Packets are not marked with an explicit drop precedence value.

1.28.4   Usage Guidelines

Assigns a QoS drop precedence value to packets corresponding to the AF class of the packets.

In general, the level of forwarding assurance of an IP packet is based on:

• Resources allocated to the AF class to which the packet belongs
• Current load of the AF class, and, in case of congestion within the class
• Drop precedence of the packet. In case of congestion, the drop precedence of a packet determines the relative importance of the packet within the AF DSCP class

Packets with a lower drop precedence value are preferred and protected from being lost, while packets with a higher drop precedence value are discarded.

For more information see RFC 2597, Assured Forwarding PHB Group.

With AF classes AF1 (AF11, AF12, AF13), AF2 (AF21, AF22, AF23), AF3 (AF31, AF32, AF33), and AF4 (AF41, AF42, AF43), the second integer represents a drop precedence value. Table 5 shows how the AF drop precedence value of an incoming packet is changed when it exits the SmartEdge router after being tagged with a new drop precedence. (See also RFC 2597, Assured Forwarding PHB Group.)

Only one mark instruction can be in effect at a time. To change the mark instruction, enter the mark precedence command, specifying a new value for the prec-value argument, which supersedes the one previously configured.

1.28.5   Examples

The following example configures the DPI, qos_prof_02, to mark all packets as preferred packets.

[local]Redback(config)#dpi qos profile qos_prof_02
[local]Redback(dpi-qos)#mark precedence 1 

1.29   mark priority

mark priority {group-num | ignore} [{drop-precedence {group-num | ignore} | af-drop drop-value}]

no mark priority

1.29.1   Command Mode

DPI QoS profile configuration

1.29.2   Syntax Description

1.29.3   Default

The PD QoS values for a packet are not modified.

1.29.4   Usage Guidelines

Sets the internal Packet Descriptor (PD) QoS classification value for specified packets, while preserving the packet’s IP header DSCP value.

A priority group is an internal value used by the SmartEdge OS to determine into which egress queue the inbound packet is placed. The ToS value, DSCP value, and MPLS EXP bits are unchanged by this command. The actual queue number depends on the number of queues configured on the egress circuit. For more information, see the num-queues command.

The SmartEdge OS uses the factory preset or default mapping of a priority group to queue, according to the number of queues configured on a circuit; see Table 6.

Only one mark instruction can be in effect at a time. To change the mark instruction, enter the mark priority command, specifying a new value for the group-num argument. This supersedes the value previously configured.

Note:  

By default, the SmartEdge OS assigns a priority group to each egress queue, according to the number of queues configured on a circuit. You can override the default mapping of packets into egress queues by creating a customized queue priority map using the qos queue-map command (in global configuration mode).

If neither the drop-precedence nor the af-drop keyword is specified, the priority bits are set to the specified value and the drop-precedence bits are cleared.

1.29.5   Examples

The following example configures the DPI, qos_prof_02, to mark all packets as high-priority packets:

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#mark priority 2 

1.30   protocol

For UDP and TCP:

[seq sequence-number] protocol {udp | tcp} {network network-prefix/prefix-length | any} {cond source-port | range source-start-port source-end-port | any} {cond dest-port | range dest-start-port dest-end-port | any} class class-name

no seq sequence-number

For other protocols:

[seq sequence-number] protocol protocol {network network-prefix/prefix-length | any} class class-name

no seq sequence-number

1.30.1   Command Mode

DPI access control list configuration

1.30.2   Syntax Description

1.30.3   Default

None

1.30.4   Usage Guidelines

Creates an ACL statement to allow packets that meet the specified criteria. If seq sequence-number is not specified, the system assigns a sequence number.

The cond source-port and cond dest-port constructs are mutually exclusive with the range source-start-port source-end-port and range dest-start-port dest-end-port constructs.

Table 7 lists the valid keyword substitutions for the protocol argument.

Table 8 lists the valid keyword substitutions for the cond argument.

Table 9 lists the valid keyword substitutions for the source-port, source-start-port, source-end-port, dest-port, dest-start-port, or dest-end-port argument when it is used to specify a TCP port.

Table 10 lists the valid keyword substitutions for the source-port, source-start-port, source-end-port, dest-port, dest-start-port, or dest-end-port argument when it is used to specify a UDP port.

1.30.5   Examples

[local]Redback(dpi-acl)#seq 20 udp any eq echo class c5
[local]Redback(dpi-acl)#tcp any any any class c6 

1.31   qos profile

qos profile profile-name [policing | metering]

no qos profile profile-name [policing | metering]

1.31.1   Command Mode

DPI action class configuration

DPI traffic-management policy configuration

1.31.2   Syntax Description

1.31.3   Default

No QoS profile is configured.

1.31.4   Usage Guidelines

Creates or selects a QoS profile and enters DPI QoS profile configuration mode. One policing and one metering QoS profile can be applied to a single DPI action class or traffic management policy. Neither policing nor metering QoS profiles can be applied together with a bidirectional QoS profile. When used in DPI traffic-management policy configuration mode, applies traffic control actions to all traffic associated with a specified subscriber.

1.31.5   Examples

[local]Redback(config-dpi-action-class)#qos profile q1

[local]Redback(config-dpi-action-class)#qos profile q2 policing

[local]Redback(config-dpi-policy)#dpi qos profile sub_qos1 

1.32   rate

rate kbps {burst bytes | time-burst msec}

1.32.1   Command Mode

DPI QoS profile configuration

1.32.2   Syntax Description

1.32.3   Default

Rate is calculated based on the default values for the kbps, bytes, and msec arguments.

1.32.4   Usage Guidelines

Sets the rate and burst tolerance for traffic on the subscriber record to which the QoS policy is attached.

Rate limits apply to an aggregate of inbound and outbound directions.

1.32.5   Examples

[local]Redback(config)#dpi qos profile qos_prof_01
[local]Redback(dpi-qos)#rate 64 burst 3000 

1.33   show dpi asp access-list

show dpi asp slot/asp-id access-list [list-name]

1.33.1   Command Mode

all modes

1.33.2   Syntax Description

1.33.3   Usage Guidelines

Displays information about one or all ACLs configured on the ASE card in the specified slot and port.

1.33.4   Examples

[local]Redback#show dpi asp 2/1 access-list
  acl_01
  acl_02

[local]Redback# show dpi asp 2/1 access-list acl_01
  Default Class: cc
    seq 10 application bit-torrent class dd
    seq 20 application bit-torrent class dd
    seq 30 application bit-torrent class dd
    seq 40 application bit-torrent class dd
    seq 50 category p2p class cc
    seq 60 protocol tcp any range 1 65535 range 1 65535 class dd
    seq 70 application bit-torrent network 1.2.3.4/0 
    class hh
    seq 80 application bit-torrent network 1.2.3.4/1 
    class hh

1.34   show dpi asp qos profile

show dpi asp slot/asp-id qos profile [profile-name]

1.34.1   Command Mode

all modes

1.34.2   Syntax Description

1.34.3   Usage Guidelines

Displays information about one or all QoS profiles configured on the ASE card in the specified slot and port.

1.34.4   Examples

[local]Redback#show dpi asp 2/1 qos profile
  q1
  q2
  q34

[local]Redback#show dpi asp 2/1 qos profile q1
  Rate:  12312 kbps    Burst: 23 bytes   
  Time-burst: 0 milli-seconds
  Conf-mark-priority   Conf-mark-prec  Conf-mark-
  dscp
      0xff               0xff               0x16
  Exceed-mark-priority   Exceed-mark-prec  Exceed-mark-
  dscp
      0xff                0x2               0xff

    Jitter : 0
  Delay  : 123123
  Reorder: 12 (random)
  

1.35   show dpi asp traffic-management action policy

show dpi asp slot/asp-id traffic-management action policy [policy-name]

1.35.1   Command Mode

all modes

1.35.2   Syntax Description

1.35.3   Usage Guidelines

Displays information about one or all DPI traffic management action policies configured on the ASE card in the specified slot and port.

1.35.4   Examples

[local]Redback#show dpi asp 2/1 traffic-management action policy
  apol_01
  apol_02

[local]Redback#show dpi asp 2/1 traffic-management action policy apol_01
  Default Class:
  class c1
    Qos Profile: q1 [Bidirectional]
    Statistics: Enable
    Log Events: Detection
  class c2
    Qos Profile: q2 [Policing]
    Qos Profile: q3 [Metering]
    Statistics: Enable
    Log Events: Detection

1.36   show dpi asp traffic-management application

show dpi asp slot/asp-id traffic-management application

1.36.1   Command Mode

all modes

1.36.2   Syntax Description

1.36.3   Usage Guidelines

Displays a list of applications supported by the current signature file on an ASE card.

1.36.4   Examples

[local]Redback#show dpi asp 4/2 traffic-management application
bit-torrent
fast-track
edonkey
gnutella
open-fast-track
skype
yahoo-messenger
google-talk
windows-live-messenger
rtp
rtsp
blackberry
imap
microsoft-media-services
shoutcast
netbios
quick-time
syncml
wap2
quake
half-life-2
doom-3
world-of-warcraft
tencent-qq
aol-instant-messenger
wireless-village
all-peers
direct-connect
ares
mxit
hamachi
fring
paltalk
http
sip
itunes
cool-streaming
max-tv
ppmate
apple-juice
100-bao
go-boogy
hot-line
kugoo
poco
tesla
soribada
baidu
citrix
imesh
kad-network
manolito
soulseek
warez

1.37   show dpi asp traffic-management category

show dpi asp slot/asp-id traffic-management category [category-name]

1.37.1   Command Mode

all modes

1.37.2   Syntax Description

1.37.3   Usage Guidelines

Displays a list of categories supported by the current signature file or the applications included in a specified category.

1.37.4   Examples

The following example provides a list of the application categories supported by the signature file in use:

[local]Redback#show dpi asp 4/2 traffic-management category
all
file-transfer
gaming
instant-messaging
p2p
social-networks
streaming
transport
voip

1.38   show dpi asp traffic-management policy

show dpi asp slot/asp-id traffic-management policy [policy-name]

1.38.1   Command Mode

all modes

1.38.2   Syntax Description

1.38.3   Usage Guidelines

Displays information about one or all DPI traffic management policies configured on the ASE card in the specified slot and port.

1.38.4   Examples

[local]Redback#show dpi asp 2/1 traffic-management policy
  pol_01
    Access Group: acl_01
    Action Policy: apol_01

[local]Redback#show dpi asp 2/1 traffic-management policy
  p1
    Access Group: acl1
    Action Policy: ap1
    qos profile sub_01

1.39   show dpi asp traffic-management signature-file

show dpi asp slot/asp-id traffic-management signature-file

1.39.1   Command Mode

all modes

1.39.2   Syntax Description

1.39.3   Usage Guidelines

Displays information about the signature file for the specified ASP; it could be the configured signature-file or the built-in one.

1.39.4   Examples

The following example displays information about the built-in signature file, configures a new signature file, and then displays information about the configured signature-file.

[local]Redback#show dpi asp 6/1 traffic-management signature-file
  Signature Configured: [Built-in]
  Signature Applied: [Built-in]
  Error: None
  Signature-file Version: 4-25
  DPI Engine Version: 4-25
[local]Redback#configuration
Enter configuration commands, one per line, 'end' to exit
[local]Redback(config)#dpi traffic-management signature-file /md/P2P-4-35.sdf
[local]Redback#show dpi asp 6/1 traffic-management signature-file  Signature Configured: P2P-4-35.sdf
  Signature Applied: P2P-4-35.sdf
  Error: None
  Signature-file Version: 4-35
  DPI Engine Version: 4-25

1.40   show dpi asp traffic-management statistics

show dpi asp slot/asp-id traffic-management statistics {packet [in | out] | protocol [protocol-name] | sessions | signature-file | subscriber}

1.40.1   Command Mode

all modes

1.40.2   Syntax Description

1.40.3   Usage Guidelines

Use the show dpi asp traffic-management statistics command to display traffic management statistics. Use the packet keyword to display traffic-management statistics for packets.

Use the in | out keywords to limit the display by direction.

Use the protocol keyword to display ASP counters per application; for example, the total number of packets and bytes received, dropped, and so on.

Use the signature-file keyword to display signature-file statistics for the configured or built-in signature-file for an ASP.

Use the subscriber keyword to display the current number of active subscribers, maximum subscriber count (historical), number of subscribers being processed with the specified profile, number of subscribers being processed with the default profile, and other subscriber statistics.

1.40.4   Examples

[local]Redback#show dpi asp 2/1 traffic-management statistics protocol
Protocol: bit-torrent
       Packets Received: 4110091
       Bytes Received: 2747344474
       Packets Dropped: 0
       Bytes Dropped: 0
       Flow Count: 1000
       Packets Inspected: 1000
       Packets Rate Limited: 0
       Packets Sent: 4110091
       Bytes Sent: 2747344474
  Protocol: fast-track
       Packets Received: 0
       Bytes Received: 0
       Packets Dropped: 0
       Bytes Dropped: 0
       Flow Count: 0
       Packets Inspected: 0
       Packets Rate Limited: 0
       Packets Sent: 0
       Bytes Sent: 0
      
  Protocol: edonkey
       Packets Received: 0
       Bytes Received: 0
---(more)---


[local]Redback#show dpi asp 2/1 traffic-management statistics protocol bit-torrent
Protocol: bit-torrent
           Packets Received: 18
           Bytes Received: 15238
           Packets Dropped: 10
           Bytes Dropped: 14720
           Flow Count: 1
           Packets Inspected: 1
           Packets Rate Limited: 10
           Packets Sent: 8
           Bytes Sent: 518


[local]Redback#show dpi asp 2/1 traffic-management statistics subscriber
  Current Subscriber Count: 1000
  Maximum Subscriber Count: 1000
  Subscribers Exceeding Session Limit: 100
  Subscribers Per Profile:
           Profile-Name                  Subscriber-Count
               dpi_pol_1                  1000


[local]Redback#show dpi asp 2/1 traffic-management statistics packet
  Packets Received: 1147051577
  Bytes Received: 765585355073
  Packets Dropped: 0
  Bytes Dropped: 0
  Packets Inspected: 903794
  Packets Rate Limited: 0
  Packets Sent: 1147051577
  Bytes Sent: 765585355073
  Non-TCP/UDP Packets Received: 1594308
  Packets Bypassed: 0 

[local]Redback#show dpi asp 2/1 traffic-management statistics packet in
  Packets Received: 1617332757
  Bytes Received: 791013170998
  Packets Dropped: 0
  Bytes Dropped: 0
  Packets Inspected: 1043009228
  Packets Rate Limited: 0
  Packets Sent: 1617332757
  Bytes Sent: 791013170998
  Non-TCP/UDP Packets Received: 2085990886
  Packets Bypassed: 0

[local]Redback#show dpi asp 2/1 traffic-management statistics sessions
 Sessions:
   TCP:
     Pending Classification: 125
     Total: 948
   UDP:
     DNS: 0
     Pending Classification: 0
     Total: 1000

1.41   show dpi circuit

show dpi circuit {agent-circuit-id agent-circuit-id | agent-remote-id agent-remote-id | slot/port[:chan-num[:sub-chan-num] [circuit-id] | username subscriber} traffic-management [sessions | statistics sessions | statistics [packet [in | out]] {class | protocol}]

1.41.1   Command Mode

all modes

1.41.2   Syntax Description

1.41.3   Usage Guidelines

Displays security service specific information per subscriber, including:

• The service enabled for the subscriber
• Whether the subscriber is receiving the specified service
• Whether the service is being bypassed
• Whether traffic for this subscriber is being dropped due to a lack of operational ASPs
• The specific ASP that is providing the service

Use the sessions keyword to display a summary of all active (TCP, UDP) sessions for the specified subscriber, including the standard 5-tuple and the class applied to the flow; one line is displayed per subscriber session. Use the statistics keyword to display the subscriber statistics, including session statistics.

1.41.4   Examples

[local]Redback#show dpi circuit username p2_1@local
  Assigned-ASP 2/1
  ASP-State: Up
  Services Configured: P2P-Traffic-Management[test]
  Services Applied: P2P-Traffic-Management[test]
  Service State: Normal

[local]Redback#show dpi circuit username p2_1@local traffic-management sessions
Source-IP  Source-  Transport      Dest-        Dest-IP 
           Port                    Port
12.1.0.1   32768    tcp        6881     112.1.1.1  
P2P-Protocol       Class-Protocol   
bit-torrent          c34

[local]Redback#show dpi circuit username p2_1@local traffic-management statistics class
  Class: c100
        Direction: Egress
        Packets Received: 2
        Bytes Received: 80
        Packets Dropped: 0
        Bytes Dropped: 0
        Flow Count: 0
        Packets Inspected: 2
        Packets Rate Limited: 0
        Packets Sent: 2
        Bytes Sent: 80
  Class: c100
        Direction: Ingress
        Packets Received: 1
        Bytes Received: 40
        Packets Dropped: 0
        Bytes Dropped: 0
        Flow Count: 0
        Packets Inspected: 1
        Packets Rate Limited: 0
        Packets Sent: 1
        Bytes Sent: 40
  Class: c34
        Direction: Egress
        Packets Received: 58
        Bytes Received: 3390

[local]Redback#show dpi circuit username p2_1@local traffic-management statistics protocol
  Protocol: bit-torrent
        Direction: Egress
        Packets Received: 106
        Bytes Received: 6166
        Packets Dropped: 0
        Bytes Dropped: 0
        Flow Count: 1
        Packets Inspected: 1
        Packets Rate Limited: 0
        Packets Sent: 106
        Bytes Sent: 6166
  Protocol: bit-torrent
        Direction: Ingress
        Packets Received: 283
        Bytes Received: 266422
        Packets Dropped: 177
        Bytes Dropped: 260544
        Flow Count: 1
        Packets Inspected: 0
        Packets Rate Limited: 177
        Packets Sent: 106
        Bytes Sent: 5878

[local]Redback#show dpi circuit username user1@domain.com traffic-management statistics packet
        Packets Received: 6144
        Bytes Received: 4479456
        Packets Dropped: 856
        Bytes Dropped: 34240
        Packets Inspected: 64
        Packets Rate Limited: 0
        Packets Exceeding Session Limit: 1100
        Bytes Exceeding Session Limit: 187592
        Packets Sent: 6144
        Bytes Sent: 4479456
        TCP Resets Originated: 0

[local]Redback#show dpi circuit username user1@domain.com traffic-management statistics session
 Sessions:
   TCP:
     Pending Classification: 1
     Total: 2
   UDP:
     DNS: 0
     Pending Classification: 1
     Total: 1

1.42   show dpi traffic-management

show dpi traffic-management {signature-file [sig-filename {application | category}] | application | category [category-name]}

1.42.1   Command Mode

all modes

1.42.2   Syntax Description

1.42.3   Usage Guidelines

Displays traffic management applications or categories supported by the current or built-in signature file .

With the signature-file keyword, displays the configured and applied signature-file, version of DPI Engine, active signature-file, and any errors. With the signature-file sig-filename construct, displays the applications or categories supported by the signature file.

1.42.4   Examples

The following example displays the categories supported by the current signature-file on the XCRP card.

[local]Redback#show dpi traffic-management category
all
file-transfer
gaming
instant-messaging
p2p
social-networks
streaming
transport
voip

The following example displays the applications supported by the p2p-3-1.sdf signature file.

 [local]Redback#show dpi traffic-management signature-file p2p-3-1.sdf application
bit-torrent
fast-track
edonkey
gnutella
open-fast-track
skype
yahoo-messenger
google-talk
windows-live-messenger
rtp
rtsp
blackberry
imap
microsoft-media-services
shoutcast
netbios
quick-time
syncml
wap2
quake
half-life-2
doom-3
world-of-warcraft
tencent-qq
aol-instant-messenger
wireless-village
all-peers
direct-connect
ares
mxit
hamachi
fring
paltalk
http
sip
itunes
cool-streaming
max-tv
ppmate
apple-juice
100-bao
go-boogy
hot-line
kugoo
poco
tesla
soribada
baidu
citrix
imesh
kad-network
manolito
soulseek
warez
joost
orb
peercasting
pplive
slingbox
windows-media-player
youtube
zattoo
winny
flashstreaming
zrtp
ants-p2p
rdp
sopcast
veetle
zepp
nntp
rtmp
your-freedom
spotify
audition
facebook
hulu
opera-mini

1.43   show security asp statistics

show security asp slot/asp-id statistics {packet slot | system}

1.43.1   Command Mode

all modes

1.43.2   Syntax Description

1.43.3   Usage Guidelines

Displays statistics for the ASP on the specified ASE card.

1.43.4   Examples

[local]Redback#show security asp 2/1 statistics system


Memory Information :
  Total Dynamic Memory: 1073726296 Bytes
  Memory Allocated: 518697592 Bytes
  Memory Available: 555028704 Bytes
  Allocation Failures: 0 Bytes

Packet Statistics :
  Bypassed packets: 
    Unknown Subscribers:  0
    Memory Overload: 0
  Replicated packets
    slot 1: 19108908
    slot 5: 817923
    slot 6: 817923
    slot 10: 19108908

[local]system1#show security asp 2/2 statistics system

Memory Information :
  Total Dynamic Memory: 1073726296 Bytes
  Memory Allocated: 518928728 Bytes
  Memory Available: 554797568 Bytes
  Allocation Failures: 0 Bytes

Packet Statistics :
  Bypassed packets: 0
    Unknown Subscribers:  0
    Memory Overload: 0
  Replicated packets
    slot 1: 19179631
    slot 5: 837430
    slot 6: 837430
    slot 10: 19179631

1.44   show security asp system

show security asp slot/asp-id system

1.44.1   Command Mode

all modes

1.44.2   Syntax Description

1.44.3   Usage Guidelines

Displays system-level information stored on the ASP, such as a list of slots populated with cards, card type and PPA type of traffic cards installed, and the state of each populated slot.

1.44.4   Examples

[local]Redback#show security asp 2/1 system

Control Plane :
     Slot         Card-Type           State
      2           ase                   Up
      4           ge-20-port            Up

Data Plane :
     Slot         Card-Type           State
      2           ase                   Up
      4           ge-20-port            Up

Glossary

Reference List