7. Network QoS Policies

This chapter provides information to configure network QoS policies using the CLI.

7.1. Overview

Network QoS policies are available for use with network IP interfaces, network ports, and hybrid ports when operating in network mode.

On 7210 SAS, there are the following network QoS policy types: port and ip-interface.

The following types of QoS mapping decisions are applicable on a network IP interface:

  1. MPLS LSP EXP value mapping to FC (if defined)
  2. default QoS mapping
  3. MPLS LSP EXP mapping to profile

The default QoS mapping always exists on an IP interface and every received packet is mapped to the default, provided another explicitly defined matching entry does not exist.

The following types of QoS mapping decisions are applicable on a network port:

  1. Ethernet dot1p and IP DSCP value mapping (if defined) for use with IP packets
  2. default QoS mapping

The default QoS mapping always exists on network ports and every received packet is mapped to the default, provided another explicitly defined matching entry does not exist.

7.2. Network QoS Policy in Network Mode

The network QoS policy consists of an ingress and egress component.

A port network policy is applied to network and hybrid ports and used for classification/remarking of IP traffic using DSCP or dot1p values. Either DSCP or dot1p can be used for ingress classification but not both. Both DSCP and dot1p can be configured at egress for remarking.

An ip-interface network policy is applied to IP interfaces and used for classification/remarking of MPLS traffic using EXP values.

The ingress component of the port policy type defines how the DSCP or dot1p bits are mapped to the internal FC and profile state. The FC and profile state define the Per Hop Behavior (PHB) and the QoS treatment through the 7210 SAS. The ingress component of the ip-interface policy type defines how the EXP bits are mapped to the internal FC and profile state. The FC and profile state define the PHB and the QoS treatment through the 7210 SAS. The ingress profile assignments using MPLS-EXP bits are defined using the mpls-lsp-exp-profile-map policy, which defines the mapping between the MPLS LSP EXP bits and the profile (in or out) associated with a packet.

The mapping on each ip-interface or port policy defaults to the mappings defined in the default network QoS policy until an explicit policy is defined for the IP interface or port. It also defines the bandwidth-limiting parameters for the traffic mapped to each FC. Traffic mapped to each FC can be limited to configurable bandwidth values using separate meters for unicast and multipoint traffic (multipoint is used on IP Interfaces for MPLS traffic and for IP multicast traffic received on network or hybrid ports). On both network IP interface ingress and network port ingress, color-aware meters are provisioned by default to use the ingress profile assigned to the packet, if configured.

The total number of QoS resources—that is, ingress classification entries and policers—available for use with IP interfaces is limited. The software allocates these resources to an IP interface on a first-come-first-served basis. The number of resources used per IP interface limits the total number of IP interfaces configured on the system (the total number of IP interfaces allowed is also limited by the system).

The egress component of the network QoS ip-interface policy type defines the LSP EXP bits marking values associated with each FC. The egress component of the network QoS port policy type defines the DSCP or dot1p bits marking values associated with each FC.

By default, all ports configured in network mode use the default network policy ",1" and all network port IP interfaces use the default network policy "2". Default network policies "1" and "2" cannot be modified or deleted.

Non-default network policy parameters can be modified. The no form of the command reverts to the default values.

Changes made to a policy are applied immediately to all network ports, hybrid ports, or IP interfaces where the policy is applied. For this reason, when a policy requires several changes, Nokia recommends that you copy the policy to a work area policy ID. The work-in-progress copy can be modified, and then the original policy ID can be overwritten using the config qos copy command.

Refer to the CLI usage chapter in the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System Configuration Guide for information about the tasks and commands required to access the CLI and to configure and maintain 7210 SAS devices.

7.2.1. Network Qos Policy (ip-interface Type) Behavior for MPLS LSPs

The following behavior is supported with the use of network IP interface QoS policies for LDP and RSVP (with FRR/PHP) MPLS LSPs.

  1. The system assigns a default mpls-lsp-exp-profile-map policy to LSPs that are set up using LDP. Users have an option to change the global policy. A new mpls-lsp-exp-profile-map policy allows the user to assign different profile values for MPLS EXP bits for MPLS packets received over different IP interface. This is helpful for use with primarily RSVP LSP with FRR 1:1. For LDP LSPs, or when using the FRR facility, Nokia recommends using a single mpls-lsp-exp-profile-map policy for all IP interfaces. With PHP enabled, the egress LER receives only the VC labeled packets, and the profile mapping is performed using a global mpls-lsp-exp-profile-map policy.
  2. The new policy separates the profile mapping and FC mapping. The FC is always derived from the network policy. The EXP-to-FC mapping configured in the network policy is used. EXP-to-profile mapping is derived from the mpls-lsp-exp-profile policy associated with the network QoS policy.
  3. Each IP interface can define a unique network policy, each possibly using a different mapping for MPLS LSP EXP bits to FC. It allows for the use of more than 32 distinct network policies, provided network classification resources are available for use.
  4. If the user receives traffic on RSVP LSP and LDP LSP with the same value in the EXP bits, the system provides the same QoS treatment. The system always uses the FC and the meter from the network QoS policy for all MPLS traffic received on an IP interface, irrespective of whether it is LDP or RSVP LSP.

7.2.2. DSCP Marking CPU Self-Generated Traffic

DSCP marking for CPU generated traffic is configurable by the user; see QoS for Self-Generated (CPU) Traffic on Network Interfaces for more information. Table 29 lists the default values.

Table 29:  DSCP and dot1p Marking  

Protocol

IPv4

DSCP Marking

Dot1P Marking

Default FC

DSCP Values (Decimal)

Dot1P Values

OSPF

Yes

Yes

Yes

NC

48

7

ISIS

Yes

No

Yes

NC

-

7

TLDP

Yes

Yes

Yes

NC

48

7

RSVP

Yes

Yes

Yes

NC

48

7

SNMP

Yes

Yes

Yes

H2

34

4

NTP

Yes

Yes

Yes

NC

48

7

TELNET

Yes

Yes

Yes

H2

34

4

FTP

Yes

Yes

Yes

H2

34

4

TFTP

Yes

Yes

Yes

H2

34

4

SYSLOG

Yes

Yes

Yes

H2

34

4

TACACS

Yes

Yes

Yes

H2

34

4

RADIUS

Yes

Yes

Yes

H2

34

4

SSH

Yes

Yes

Yes

H2

34

4

ICMP Req

Yes

Yes

Yes

NC

0

7

ICMP Res

Yes

Yes

Yes

NC

0

7

ICMP Unreach

Yes

Yes

Yes

NC

0

7

SCP

Yes

Yes

Yes

H2

34

4

PIM (SSM)

Yes

Yes

Yes

NC

STP

NA

NA

Yes

NC

-

7

CFM

NA

NA

Yes

NC

-

7

ARP

NA

NA

Yes

NC

-

7

Trace route

Yes

Yes

Yes

NC

0

7

TACPLUS

Yes

Yes

Yes

H2

34

4

IGMP

Yes

Yes

Yes

NC

48

7

DNS

Yes

Yes

Yes

H2

34

4

BGP

Yes

Yes

Yes

NC

48

7

PTP

Yes

Yes

Yes

H2

48

7

Note:

  1. For PTP messages, based on the type of the message (event or non-event), the DSCP value used is either 0x30 (h1) or 0x38 (nc), and the dot1p value is always 7.
  2. DSCP and dot1P values in the table are applicable when remarking is disabled at the port level.

7.2.2.1. QoS for Self-Generated (CPU) Traffic on Network Interfaces

DSCP, FC, and IEEE 802.1p values can be specified for use by protocol packets generated by the node. This enables prioritization or deprioritization of every protocol (as required).

DSCP marking for internally generated control and management traffic should be used for a specified application. This can be configured per routing instance; for example, OSPF packets can carry a different DSCP marking for the base instance than for a VPRN service. ARP and IS-IS are not IP protocols, so only 802.1p values can be configured.

The DSCP value can be set per application. When an application is configured to use a specified DSCP value and an FC, the 802.1p and MPLS EXP bits are marked in accordance with the network (default 802.1p value of 7) or access (default 802.1p value of 0) egress policy, as it applies to the logical interface the packet is egressing.

Configuring self-generated QoS is supported in the base router and VPRN service contexts.

The default values for self-generated traffic on network interfaces are the following:

  1. routing protocols (for example, OSPF and BGP)
    1. FC: Network Control (NC)
    2. DSCP value: NC1 (not applicable for ARP and IS-IS)
    3. 802.1p value: according to the egress QoS policy (7 by default)
  2. management protocols (for example, SSH and SNMP)
    1. FC: Network Control (NC)
    2. DSCP value: AF41
    3. 802.1p value: according to the egress QoS policy (7 by default)
Note:

  1. ICMP echo requests (type 8) and ICMPv6 echo requests (type 128) initiated from the router use the DSCP value set using the sgt-qos command. The FC value is NC by default, or the value specified in the ping command parameter fc fc-name.
  2. Configurable values for BFD are not supported.
  3. On access SAP egress and access port egress, when remarking is not enabled, the dot1p value for all IP packets generated by the node is set to zero. To enable dot1p marking, remarking must be enabled.

7.2.2.2. Default DSCP Mapping Table

Table 30 lists the DSCP mapping between DSCP name and DSCP values (decimal, hexadecimal, and binary) and label.

Table 30:  Default DSCP Mapping Table 

DSCP Name

DSCP Value Decimal

DSCP Value Hexadecimal

DSCP Value Binary

Label

Default

0

0x00

0b000000

be

nc1

48

0x30

0b110000

h1

nc2

56

0x38

0b111000

nc

ef

46

0x2e

0b101110

ef

af11

10

0x0a

0b001010

assured

af12

12

0x0c

0b001100

assured

af13

14

0x0e

0b001110

assured

af21

18

0x12

0b010010

l1

af22

20

0x14

0b010100

l1

af23

22

0x16

0b010110

l1

af31

26

0x1a

0b011010

l1

af32

28

0x1c

0b011100

l1

af33

30

0x1d

0b011110

l1

af41

34

0x22

0b100010

h2

af42

36

0x24

0b100100

h2

af43

38

0x26

0b100110

h2

default  1

0

    Note:

  1. The default FC mapping is used for all DSCP names/values for which there is no explicit FC mapping.

7.3. Basic Configurations

A basic network QoS policy must:

  1. have a unique policy ID
  2. specify the default-action
  3. have a QoS policy scope of template or exclusive

7.3.1. Create a Network QoS Policy (ip-interface Type) for Network Mode

Configuring and applying QoS policies other than the default policy is optional. A default network policy of the ip-interface type is applied to each IP interface.

To create a network QoS policy of the ip-interface type, define the following.

  1. Specify a network policy ID value. The system does not dynamically assign a value.
  2. Set the network-policy-type parameter to ip-interface.
  3. Include a description that provides a brief overview of policy features.
  4. Use egress marking and remarking to specify the egress LSP EXP marking map; otherwise, the default values are applied. The following are defined:
    1. remarking
      The remark policy-id command specifies the policy, which defines the mapping of the FC-to-packet header priority profile and bits.
      The remarking command uses the associated policy configured with the remark policy-id command to determine which priority bits to mark on egress.
      When remarking is enabled, MPLS EXP bits for all MPLS LSR and LER traffic are marked on egress on the specified network IP interface. Remarking is based on the FC-to-LSP EXP bit mapping that is defined in the remark policy and associated under the egress node of the network QoS policy. The EXP marking values used depend on the configured remark policy. If the user does not attach an explicit policy, the default policy is used.
      When remarking is disabled for MPLS LSR traffic, EXP values received on ingress are not modified on egress. For MPLS LER traffic where the node adds the MPLS encapsulation, MPLS EXP bits are set based on the mapping specified in the policy associated with the IP interface. If the user does not attach an explicit policy, the default policy is used.
    2. FC criteria
      The FC name represents an egress queue. Specify FC criteria to define the egress characteristics of the queue and the marking criteria of packets flowing through it.
    3. LSP EXP
      The EXP is used for all packets requiring marking that egress on this FC queue that are in or out of profile.
  5. Specify ingress criteria using the following:
    1. default action
      Defines the default action to take for packets that have undefined bits set. The default action specifies the FC to which these packets are assigned.
    2. LSP EXP
      Creates a mapping between the LSP EXP bits of the network ingress MPLS traffic and the FC. Ingress MPLS traffic that matches the specified EXP bits are assigned to the corresponding FC. The user has an option to specify the mapping of the LSP EXP bits to a profile (in or out). Ingress traffic that matches the specified EXP bits is assigned the corresponding profile.

7.3.2. Configuring Network QoS Policy (port Type) for Network Mode

To create a network QoS policy of the port type when operating in network mode, define the following:

  1. Specify a network policy ID value. The system does not dynamically assign a value.
  2. Set the network-policy-type parameter to port.
  3. Include a description that provides a brief overview of policy features.
  4. Modify the egress DSCP and dot1p marking map; otherwise, the default values are applied.
    1. remarking
      When enabled, this command remarks all IP packets that egress the specified network port. The remarking is based on the FC-to-DSCP bit mapping defined in the remark policy and associated under the egress node of the network QoS policy for all IP traffic. FC-to-dot1p marking for MPLS packets is not supported; it is supported only for IP packets.
    2. FC criteria
      The FC name represents an egress queue. Specify FC criteria to define the egress characteristics of the queue and the marking criteria of packets flowing through it.
    3. DSCP and dot1p
      Specify the DSCP and dot1p value to use for IP packets requiring marking that egress on this FC queue that are in or out of profile.
  5. Specify ingress criteria as either DSCP or dot1p (but not both) to FC mapping for all IP packets. Define the following:
    1. default action
      Defines the default action to take for packets that have undefined DSCP or dot1p bits set. The default action specifies the FC to which these packets are assigned.
    2. DSCP or dot1p
      Creates a mapping between the DSCP or dot1p bits of network ingress IP traffic and the FC. Ingress IP traffic that match the specified DSCP or dot1p bits are assigned to the corresponding FC.

Use the following syntax to create a network QoS policy.

CLI Syntax:
config>qos#
network policy-id [network-policy-type network-policy-type]
description description-string
scope {exclusive|template}
egress
remarking
remark <policy-id>
ingress
default-action fc {fc-name} profile {in|out}
lsp-exp lsp-exp-value fc fc-name profile {in | out}
fc {fc-name}
meter {meter-id}
multicast-meter {id}
meter meter-id [multipoint]
adaptation-rule cir {closest | max | min} pir {closest | max | min}
cbs {size-in-kbits}
mbs {size-in-kbits}
mode {trtcm | srtcm}
rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
mpls-lsp-exp-profile policy-id

The following is a sample configuration output of a network QoS policy.

A:Dut-B>config>qos>network# info detail
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm1
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default kbits
                    cbs default kbits
                exit
                dscp be fc be profile out
                dscp ef fc ef profile in
                dscp cs1 fc l2 profile in
                dscp nc1 fc h1 profile in
                dscp nc2 fc nc profile in
                dscp af11 fc af profile in
                dscp af12 fc af profile out
                dscp af41 fc h2 profile in
            exit
            egress
                no remarking
                remark 1
            exit
----------------------------------------------
A:Dut-B>config>qos>network#

7.3.3. Default Network Policy Values Available in Network Mode

The default network policy for IP interfaces is identified as policy-id “2”. Default policies cannot be modified or deleted. Table 31 lists default network policy parameters.

Table 31:  Network Policy Defaults for Policy Type IP-interface  

Field

Default

description

Default network QoS policy.

scope

template

ingress

default-action

fc be profile out (default action profile out is applicable only for port policies and not for ip-interface policies)

egress

remarking

fc af:

  lsp-exp-in-profile

3

  lsp-exp-out-profile

2

fc be:

  lsp-exp-in-profile

0

  lsp-exp-out-profile

0

fc ef:

  lsp-exp-in-profile

5

  lsp-exp-out-profile

5

fc h1:

  lsp-exp-in-profile

6

  lsp-exp-out-profile

6

fc h2:

  lsp-exp-in-profile

4

  lsp-exp-out-profile

4

fc l1:

  lsp-exp-in-profile

3

  lsp-exp-out-profile

2

fc l2:

  lsp-exp-in-profile

1

  lsp-exp-out-profile

1

fc nc:

  lsp-exp-in-profile

7

  lsp-exp-out-profile

7

Table 32 lists default parameters for a network QoS policy ip-interface type, LSP EXP-to-FC mapping on ingress. Color-aware policing is supported on network ingress.

Table 32:  Default Network QoS Policy of ip-interface Type, LSP EXP-to-FC Mapping on Ingress  

LSP EXP Value

FC Ingress

Profile

0

be

Out

1

l2

In

2

af

Out

3

af

In

4

h2

In

5

ef

In

6

h1

In

7

nc

In

The default network policy for port is identified as policy-id 1. Default policies cannot be modified or deleted. The following is a sample configuration output that shows the parameters for the default network port type policy:

*A:ALA>config>qos>network# info detail 
----------------------------------------------
            description "Default network-port QoS policy."
            scope template
            ingress
                default-action fc be profile out
                meter 1 create
                    mode trtcm 
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default
                    cbs default
                exit
                dscp be fc be profile out 
                dscp ef fc ef profile in 
                dscp cs1 fc l2 profile in 
                dscp nc1 fc h1 profile in 
                dscp nc2 fc nc profile in 
                dscp af11 fc af profile in 
                dscp af12 fc af profile out 
                dscp af41 fc h2 profile in 
            exit
            egress
                 no remarking
                 remark 1
            exit
           
 
 
----------------------------------------------
*A:ALA>config>qos>network#
 

The following is a sample configuration output for the default remark policy used for dot1p and DSCP marking.

fc af
                    dscp-in-profile af11
                    dscp-out-profile af12
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                exit
                fc be
 [no] de-mark
                    [no] dot1p 
                    dscp-in-profile be
                    dscp-out-profile be
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 0
                    dot1p-out-profile 0
                exit
                fc ef                 
                    dscp-in-profile ef
                    dscp-out-profile ef
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 5
                    dot1p-out-profile 5
                exit
                fc h1
                    dscp-in-profile nc1
                    dscp-out-profile nc1
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 6
                    dot1p-out-profile 6
                exit
                fc h2
                    dscp-in-profile af41
                    dscp-out-profile af41
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 4
                    dot1p-out-profile 4
                exit
                fc l1
                    dscp-in-profile af21
                    dscp-out-profile af22
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 3
                    dot1p-out-profile 2
                exit
                fc l2
                    dscp-in-profile cs1
                    dscp-out-profile cs1
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 1
                    dot1p-out-profile 1
                exit
                fc nc
                    dscp-in-profile nc2
                    dscp-out-profile nc2
                    no lsp-exp-in-profile
                    no lsp-exp-out-profile
                    no dot1p-lsp-exp-in-profile
                    no dot1p-lsp-exp-out-profile
                    dot1p-in-profile 7
                    dot1p-out-profile 7
                exit

7.4. Resource Allocation for Network QoS Policy

This section describes the allocation of QoS resources for network QoS policies of the ip-interface and port type.

When an IP interface is created, a default network QoS policy of the ip-interface type is applied. For the default policy, two meters and two classification entries in hardware are allocated.

The resources are allocated to a network policy only when a port is configured for the IP interface. When a network port is configured, a default network QoS policy of the port type is applied.

For every FC in use, the system allocates two classification entries in hardware, provided the FC is configured to use both the unicast meter and multicast meter, or provided the default meter 9 is configured in the policy. If multiple match criteria entries map to the same FC, each of these are allocated two classification entries in hardware; for example, if there are two match-criteria entries that map to FC “af,” a total of four classification entries are allocated in hardware, and if there are four match-criteria entries that map to FC “af,” a total of eight classification entries are allocated in hardware.

For every meter or policer in use, the system allocates one meter in hardware. A meter or policer is considered in use when it is associated with an FC in use.

The number of IP interfaces and network ports allowed is limited by the number of classification resources available in hardware, subject to the system limit on the number of IP interfaces and network or hybrid ports supported by the system.

7.4.1. Determining Number of Resources and Meters

This section provides information about calculating the number of resources and determining the number of meters.

7.4.1.1. Calculating the Number of QoS Resources

To calculate the number of QoS resources used by an IP interface, determine the following items:

  1. number of match-criteria entries used to identify the FC
  2. number of FCs to use

Only the FCs used by the match-criteria classification entries are considered in the “number of FCs” and are therefore are referred to as “FCs in use”. In network policies of the ip-interface type, a default multipoint meter 9 is created in a policy; for policies of the port type, a default multipoint meter needs to be explicitly configured by the user, if required.

Use the following rules to compute the number of classification entries per FC in use.

  1. If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and default meter 9 (if configured) for all other traffic types (that is, broadcast, multicast, and unknown-unicast). This requires two classification entries in hardware. If default multipoint meter 9 is not configured, the FC uses the unicast meter for all traffic types. In this case, the FC requires a single classification entry in hardware.
  2. If an FC is in use and is created with an explicit unicast meter, use that meter for unicast traffic and use default meter 9 (if configured) for all other traffic types. This requires two classification entries in hardware. If default multipoint meter 9 is not configured, the FC uses the unicast meter for all traffic types. In this case, the FC requires a single classification entry in hardware.
  3. If an FC is in use and is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and a multicast meter for all other kinds of traffic. This requires two classification entries in hardware.

Given the number of match criteria and the number of FCs in use, the following equation calculates the total number of classification entries (TC) per policy:

TC = ? 2 * E(i)

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

where:

  1. E(i) is the number of match-criteria entries that classify packets to FCi. For the 7210 SAS platforms, the maximum number of classification entries per policy can be 64 (including default).

In the worst case, only two classification entries are used per match-criteria in a network policy, because only two traffic types are supported.

7.4.1.2. Determining the Number of Meters or Policers

Determine the number of meters or policers (TP) to use. A maximum of 16 meters per network policy are available.

The number of TPs used is the number of meters configured in the policy. Among that number, only those meters configured for use with an FC are considered during resource allocation. Meters that are created but not associated with an FC are not counted for resource allocation.

7.4.2. Network QoS Policies Resource Usage Examples

Note:

In the examples in this section, the profile configuration is not shown. In practice, the user must configure the mpls-lsp-exp-profile policy and associate it with the network policy. The association of a profile policy with the network QoS policy does not affect the resource calculation methodology.

7.4.2.1. Example 1

network 1 network-policy-type ip-interface create
     description “network-policy-1”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 9 multipoint create
                exit
            exit
     egress
exit
 

The number of classification entries (TC) used is calculated using the following.

(2 * 0)nc + (2 * 0)h1 + (2 * 0)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 0)af + (2 * 0)l2 + (2 * 1)be = 2

The number of meters (TP) used is 2 (meter 1 and 9).

7.4.2.2. Example 2

network 2 network-policy-type ip-interface create
     description “network-policy-2”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2
                    multicast-meter 12
                exit
                lsp-exp 2 fc af 
            exit
            egress
            exit
       exit

The number of classification entries (TC) used is calculated using the following.

(2 * 0)nc + (2 * 0)h1 + (2 * 0)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 0)l2 + (2 * 1)be = 4

The number of meters (TP) used is 4 (meters 1, 2, 9, and 12).

7.4.2.3. Example 3

network 3 network-policy-type ip-interface create
     description “network-policy-3”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2
                    multicast-meter 12
                exit
                fc "be" create
                    meter 2
                    multicast-meter 12
                exit
                lsp-exp 2 fc af 
            exit
            egress
exit
exit
 

The number of classification entries (TC) used are calculated using the following.

(2 * 0)nc + (2 * 0)h1 + (2 * 0)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 0)l2 + (2 * 1)be = 4

The number of meters (TP) used is 2 (meters 2 and 12).

7.4.2.4. Example 4

network 4 network-policy-type ip-interface create
     description “network-policy-4”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 9 multipoint create
                exit
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
exit
exit
 

The number of filter entries (TC) used is calculated using the following.

(2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16

The number of meters (TP) used is 2 (meters 1 and 9).

7.4.2.5. Example 5

network 5 network-policy-type ip-interface create
     description “network-policy-5”
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                exit
                fc "be" create
                exit
                fc "ef" create
                exit
                fc "h1" create
                exit
                fc "h2" create
                exit
                fc "l2" create
                exit
                fc "nc" create
                exit
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
exit

The number of classification entries (TC) used is calculated using the following.

(2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16

The number of meters (TP) used is 2 (meters 1 and 9). Note that meters 2 and 12 are not accounted for because they are not associated with any FC.

7.4.2.6. Example 6

network 6 network-policy-type ip-interface create
     description “network-policy-6”
 
            ingress
                default-action fc be 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 3 create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2
                    multicast-meter 12
                exit
                fc "be" create
                exit
                fc "ef" create
                exit
                fc "h1" create
                    meter 3
                exit
                fc "h2" create
                exit
                fc "l2" create
                exit
                fc "nc" create
                    meter 3
                exit
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
exit
exit

The number of classification entries (TC) used is calculated using the following.

(2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16

The number of meters (TP) used is 5 (meters 1, 2, 3, 9, and 12).

7.4.2.7. Example 7

network 2 network-policy-type ip-interface create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be 
                meter 1 create
                    mode trtcm 
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default
                    cbs default
                exit
                meter 9 multipoint create
                    mode trtcm 
                    adaptation-rule cir closest pir closest
                    rate cir 0 pir max
                    mbs default
                    cbs default
                exit
                lsp-exp 0 fc be 
                lsp-exp 1 fc l2 
                lsp-exp 2 fc af 
                lsp-exp 3 fc af 
                lsp-exp 4 fc h2 
                lsp-exp 5 fc ef 
                lsp-exp 6 fc h1 
                lsp-exp 7 fc nc 
            exit
            egress
                no remarking 
exit
exit

The number of classification entries (TC) used is 2.

The number of meters (TP) used is 2.

7.4.2.8. Example 8

network 8 network-policy-type ip-interface create
     description “network-policy-8”
            ingress
                default-action fc nc 
                meter 1 create
                exit
                meter 2 create
                exit
                meter 3 create
                exit
                meter 4 create
                exit
                meter 5 create
                exit
                meter 7 multipoint create
                exit
                meter 8 multipoint create
                exit
                meter 9 multipoint create
                exit
                meter 12 multipoint create
                exit
                fc "af" create
                    meter 2           
                    multicast-meter 12
                exit
                fc "ef" create
                    meter 4
                    multicast-meter 8
                exit
                fc "h2" create
                exit
                fc "l2" create
                    meter 3
                    multicast-meter 7
                exit
                fc "nc" create
                    meter 4
                    multicast-meter 8
                exit
                lsp-exp 1 fc l2 
                lsp-exp 3 fc af 
                lsp-exp 5 fc ef 
                lsp-exp 7 fc nc 
            exit
            egress
exit

The number of classification entries (TC) used is calculated using the following.

(2 * 2)nc + (2 * 0)h1 + (2 * 1)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 1)l2 + (0 * 0)be = 10

The numbers of meters (TP) used is 6 (meters 2, 3, 4, 7, 8, and 12).

7.5. Service Management Tasks

This section provides information about service management tasks.

7.5.1. Deleting QoS Policies

A network policy is associated by default with IP interfaces and network ports.

You can replace the default policy with a non-default policy, but you cannot remove default policies from the configuration. When you remove a non-default policy, the policy association reverts to the appropriate default network policy.

7.5.2. Remove a Policy from the QoS Configuration

Use the following syntax to delete a network policy.

CLI Syntax:
config>qos# no network network-policy-id

7.5.3. Copying and Overwriting Network Policies

You can copy an existing network policy to a new policy ID value or overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.

Use the following syntax to overwrite a network policy.

CLI Syntax:
config>qos# copy network source-policy-id dest-policy-id [overwrite]

The following is a sample configuration output.

A:ALA-12>config>qos# info detail
---------------------------------------------
...
        network 1 create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be profile out
...
        network 600 create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be profile out
...
        network 700 create
            description "Default network QoS policy."
            scope template
            ingress
                default-action fc be profile out
...
---------------------------------------------
A:ALA-12>config>qos# 
 

7.5.4. Editing QoS Policies

You can change existing policies, except the default policies, and entries in the CLI. The changes are applied immediately to all networks where the policy is applied. To prevent configuration errors, use the copy command to make a duplicate of the original policy to a work area, make the edits, and then overwrite the original policy.