Self-generated Traffic Commands

Context

config>router

Description

This command enables the context to configure DSCP or dot1p re-marking for self-generated traffic (SGT).

Context

config>router>sgt-qos

Description

This set of commands configures DSCP marking for self-generated IP traffic or dot1p marking for self-generated non-IP traffic (specifically, IS-IS and ARP traffic).

When an IP or Layer 3 application is configured using the dscp-app-name parameter, the specified DSCP name or DSCP value is used for all packets generated by this application within the router instance in which it is configured. The value set in this command sets the DSCP value in the egress IP header. The egress QoS policy will not overwrite this value.

When a Layer 2 application is configured using the dot1p-app-name parameter, the specified dot1p priority value is used for all packets generated by this application within the router instance in which it is configured.

Only one name or value can be configured per application. If multiple entries are configured, a subsequent entry overrides the previously configured entry.

The fc-queue option redirects SGT applications to egress data queues rather than the default control queue by assigning them to a forwarding class. If this option is configured, the profile state must be set. All packets that are assigned to this forwarding class will be considered in-profile or out-of-profile based on the configuration. In case of congestion, the in-profile packets are preferentially queued over the out-of-profile packets.

If the fc-queue option is used with the dscp-app-name application, any configuration done using the sgt-qos>dscp command is ignored for packets generated by this application, as illustrated in the following examples:

sgt-qos>application telnet dscp cp1

sgt-qos>dscp cp1 fc af

sgt-qos>application ftp dscp cp1 fc-queue be profile out

sgt-qos>dscp cp1 fc af

In the first example, all packets generated by the Telnet application use DSCP CP1 and map to FC AF as configured in the dscp command. The dot1p bits of the outgoing packets are marked from the value that FC AF points to in the egress QoS policy.

In the second example, all packets generated by the FTP application use DSCP CP1 and map to FC BE as dictated by the fc-queue redirection. The dot1p bits of the outgoing packets are marked from the value that FC BE points to in the egress QoS policy. Because redirection is configured, the mapping configured with the dscp command is ignored.

If the fc-queue option is used with the dot1p-app-name application, the dot1p bits of the outgoing packets are marked with the value set with the dot1p-priority parameter, regardless of the value in the FC egress queue policy.

The no form of this command resets the DSCP or dot1p value for the application to its default value and resets the application to use the egress control queue.

Default

n/a

Parameters

dscp-app-name

the DSCP application name

Values

bgp, cflowd, dhcp, dns, ftp, icmp, igmp, ldp, mcfw, mld, ndis, ntp, ospf, pim, ptp, radius, rip, rsvp, snmp, snmp-notification, ssh, syslog, tacplus, telnet, tftp, traceroute, vrrp

Note:

• PTP in the context of SGT QoS is defined as Precision Timing Protocol and is an application in the 7705 SAR. The PTP application name is also used in areas such as event-control and logging. Precision Timing Protocol is defined in IEEE 1588-2008.

• PTP in the context of IP filters is defined as Performance Transparency Protocol. IP protocols can be used as IP filter match criteria; the match is made on the 8-bit protocol field in the IP header.

dscp-value

the value that maps to the DSCP name (the value none specifies that the default DSCP value for the application be used; see Table: Applications and Support for Configurable DSCP or dot1p Markings)

Values

none | 0 to 63

dscp-name

the DSCP to be associated with the forwarding class. Table: Valid DSCP Names lists the valid DSCP names.

dot1p-app-name

the dot1p application name

Values

arp, isis

dot1p-priority

the dot1p priority (the value none specifies that the default dot1p value for the application be used; see Table: Applications and Support for Configurable DSCP or dot1p Markings)

Values

none | 0 to 7

fc-name

the forwarding class assigned to SGT applications redirected to data queues

Values

be, l2, af, l1, h2, ef, h1, nc

profile {in | out}

the profile state of packets assigned to the specified forwarding class; this parameter must be specified when the fc-queue parameter is configured

Context

config>router>sgt-qos

Description

This command creates a mapping between the DSCP of the self-generated traffic and the forwarding class. The forwarding class dot1p network QoS policy mapping is used to mark the dot1p bits of the Layer 3 or IP application. For example, configuring the dscp-name parameter as be and the fc-name parameter as l1 results in marking the dot1p bits of the outgoing Ethernet frame, which is transporting self-generated IP traffic with DSCP bits set to BE, to the value that FC L1 points to in the network QoS policy (as configured in the config>qos>network>egress>fc context).

Based on this configured FC, the network QoS policy for the egress forwarding complex sets the IEEE 802.1 dot1p bits.

Multiple commands can be entered to associate some or all of the 64 DSCP values with the forwarding class. For undefined code points, packets are assigned to the default forwarding class for the DSCP value. This value can be seen in the show>router>sgt-qos>dscp-map output under the Default FC Value column.

The no form of the command resets the DSCP value to its default forwarding class.

Table: DSCP-to-Default FC Value Mapping  lists the default FC value for each DSCP value.

Default

See Table: DSCP-to-Default FC Value Mapping  for the default FC value for each DSCP value.

Parameters

dscp-name

the DSCP to be associated with the forwarding class. Table: Valid DSCP Names lists the valid DSCP names.

fc-name

the forwarding class name with which the DSCP will be associated

Values

be, l2, af, l1, h2, ef, h1, nc