Interface Types And Qos Parameters; Controlled-Interface Types; Table 25: Valid And Invalid Parameter Names - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

Interface Types and QoS Parameters

Copyright © 2010, Juniper Networks, Inc.

Table 25: Valid and Invalid Parameter Names

Valid Names Invalid Names
n1 1
f+ 1n
– +
– +foo
– min
– max
Parameter names are case-sensitive. For example, max-subscriber-bw and
max-Subscriber-bw are different parameter names.
Because the shaping rate and shared-shaping rates determine the maximum scheduler
rates, and the assured rate determines minimum scheduler rates, we recommend that
you use min or max operands in the parameter name.
You can specify the following attributes in a parameter definition to control the scope
of a parameter on interfaces:

Controlled-interface types

Instance-interface types
Subscriber-interface types
Controlled-Interface Types
Controlled-interface types specify interface types for queues and scheduler nodes that
a parameter instance can control. You can define up to four controlled-interface types
for each parameter definition by issuing the controlled-interface-type command in QoS
Parameter Definition Configuration mode. Examples of controlled interface types include
atm-vp (ATM virtual paths), atm-vc (ATM virtual circuits), and VLAN (virtual LANs).
For example, if you specify controlled-interface types of atm-vc and vlan, then you can
use the parameter instance to shape or weight an ATM VC or VLAN node. However,
because you did not specify ip, the system does not allow this parameter in a scheduler
profile that was referenced in a QoS profile with an ip node (for example, ip node
scheduler-profile test1).
Controlled-Interface Type Example
In this example, you configure a parameter definition for a scheduler hierarchy in which
a VLAN represents a subscriber. The parameter definition specifies that the parameter
controls VLAN nodes and queues and sets the maximum rate for any parameter instance.
Chapter 25: Configuring a QoS Parameter
217