This module defines types and identities used in OpenConfig models related to quality-of-service (QoS)
openconfig-extensions
description:
Type definition for different queueing behaviours that
are available to a scheduler.
type: enumeration
description:
Base identity for supported queue types, primarily
defined by their drop behavior / strategy
description:
When the queue is filled to capacity, newly arriving packets
are discarded until there is room in the queue to accept new
traffic. Packets are not differentiated, i.e., all packets
are treated identically.
base identity: QOS_QUEUE_TYPE
description:
Queue management based on Random Early Detection (RED). RED
drops packets based on a drop probability that is based on the
average queue length, and settings of mininum and maximum
queue thresholds. On ECN-capable devices, packets may be
marked instead of dropped to signal congestion to the
sender.
base identity: QOS_QUEUE_TYPE
description:
Queue management based on a variant of RED in which the packet
drop probability is based on its traffic class.
base identity: QOS_QUEUE_TYPE
description:
Base identity to describe supported QoS scheduler types.
description:
Token bucket scheduler with a single rate (committed information
rate) and two colors (conforming and exceeding). The scheduler
behavior is governed by two parameters, the CIR which
determines the rate of token fill (bps) and the committed
burst size (depth of the token bucket in bytes).
base identity: QOS_SCHEDULER_TYPE
description:
Token bucket scheduler with two buckets, one filled at the
committed information rate (CIR) in bps, and the second filled
at the peak information rate (PIR) in bps when the first
bucket is full. The first bucket depth is
the committed burst size (bytes), and the second is the
excess burst size (bytes). Traffic is categorized in three
colors as follows: traffic that falls within the
the CIR is conforming, traffic that is greater than the CIR
but less than the PIR is exceeding, and traffic that is
greater than PIR is violating.
base identity: QOS_SCHEDULER_TYPE
This module defines configuration and operational state data related to network quality-of-service.
openconfig-extensions
description:
Base identity for supported shared buffer limit types.
description:
The maximum buffer space that the queue is allowed to use from the shared
buffer is specified as a static-limit which is expressed in bytes.
base identity: SHARED_BUFFER_LIMIT_TYPE
description:
The maximum buffer space that the queue is allowed to use from the shared
buffer is dynamically determined based on the current usage pattern of the
shared buffer and a dynamic-limit which is expressed as a scaling factor
on the free space in the shared buffer.
base identity: SHARED_BUFFER_LIMIT_TYPE
description:
Top-level container for QoS data
nodetype: container (rw)
description:
Configuration data for global QoS
nodetype: container (rw)
description:
Operational state data for global QoS
nodetype: container (ro)
description:
Enclosing container for the list of interface references
nodetype: container (rw)
description:
List of interfaces referenced by QoS entities.
The interface referenced is based on the interface and
subinterface leaves within the interface-ref container -
which reference an entry in the /interfaces/interface list -
and should not rely on the value of the list key.
nodetype: list (rw)
list keys: [interface-id]
description:
Reference to the interface-id list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
nodetype: container (rw)
description:
Identifier for the interface.
nodetype: leaf (rw)
type: string
description:
Operational state data
nodetype: container (ro)
description:
Identifier for the interface.
nodetype: leaf (ro)
type: string
description:
Reference to an interface or subinterface. The interface
that is being referenced is uniquely referenced based on
the specified interface and subinterface leaves. In contexts
where a Layer 3 interface is to be referenced, both the
interface and subinterface leaves must be populated, as
Layer 3 configuration within the OpenConfig models is
associated with a subinterface. In the case where a
Layer 2 interface is to be referenced, only the
interface is specified.
The interface/subinterface leaf tuple must be used as
the means by which the interface is specified, regardless
of any other context information (e.g., key in a list).
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Top-level container for QoS data for the ingress
interface
nodetype: container (rw)
description:
Configuration data for QoS on ingress interface
nodetype: container (rw)
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the input (rx) queueing.
This leaf is used in deployment cases where the operator or system
requires common allocation profiles covering unicast and multicast
packets.
nodetype: leaf (rw)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only multicast packets on
the interface - if specified, the unicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to unicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (rw)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only unicast packets on
the interface - if specified, the multicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to multicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for QoS on ingress interface
nodetype: container (ro)
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the input (rx) queueing.
This leaf is used in deployment cases where the operator or system
requires common allocation profiles covering unicast and multicast
packets.
nodetype: leaf (ro)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only multicast packets on
the interface - if specified, the unicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to unicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (ro)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only unicast packets on
the interface - if specified, the multicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to multicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (ro)
type: leafref
description:
Classifiers to be applied to the interface.
nodetype: container (rw)
description:
A list of classifiers that should be applied to the interface
nodetype: list (rw)
list keys: [type]
description:
Reference to the classifier name.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters for the list of classifiers.
nodetype: container (rw)
description:
Reference to the classifier to be applied to ingress traffic on
the interface
nodetype: leaf (rw)
type: leafref
description:
Type of packets matched by the classifier.
nodetype: leaf (rw)
type: enumeration
description:
Operational state parameters for the list of classifiers.
nodetype: container (ro)
description:
Reference to the classifier to be applied to ingress traffic on
the interface
nodetype: leaf (ro)
type: leafref
description:
Type of packets matched by the classifier.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container for the list of match terms in the
classifier
nodetype: container (rw)
description:
List of match terms in the classifier associated with the
interface
nodetype: list (ro)
list keys: [id]
description:
Reference to match term id list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state data for match terms in the classifier
associated with an interface
nodetype: container (ro)
description:
Reference to match terms in the classifier
nodetype: leaf (ro)
type: leafref
description:
Count of the number of packets matching this classifier
match term on the interface.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Count of the number of octets (bytes) matching this
classifier match term on the interface.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Surrounding container for a list of queues that are
instantiated on an interface.
nodetype: container (rw)
description:
Top-level container for the queue associated with this
interface
nodetype: list (rw)
list keys: [name]
description:
Reference to the name of the queue
instantiated on the interface.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the queue associated with the
interface
nodetype: container (rw)
description:
Reference to the queue associated with this interface.
A queue may be explicitly configured, or implicitly created
by the system based on default queues that are instantiated
by a hardware component, or are assumed to be default on
the system.
nodetype: leaf (rw)
type: string
description:
The queue management profile that is to be used for the queue
on the interface.
For example, the system may use a profile which specifies that
WRED curves are used for setting an ECN mark in the IP header
instead of dropping a packet in order to signal impending
congestion and for determining when there is sufficient
congestion to tail drop packets.
A single profile is available per queue - which applies to all packets
that are enqueued to the specified queue, whether they are unicast or
multicast.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for the queue associated with the
interface
nodetype: container (ro)
description:
Reference to the queue associated with this interface.
A queue may be explicitly configured, or implicitly created
by the system based on default queues that are instantiated
by a hardware component, or are assumed to be default on
the system.
nodetype: leaf (ro)
type: string
description:
The queue management profile that is to be used for the queue
on the interface.
For example, the system may use a profile which specifies that
WRED curves are used for setting an ECN mark in the IP header
instead of dropping a packet in order to signal impending
congestion and for determining when there is sufficient
congestion to tail drop packets.
A single profile is available per queue - which applies to all packets
that are enqueued to the specified queue, whether they are unicast or
multicast.
nodetype: leaf (ro)
type: leafref
description:
Maximum observed queue length
nodetype: leaf (ro)
type: oc-yang:counter64
units: bytes
description:
Average observed queue length
nodetype: leaf (ro)
type: oc-yang:counter64
units: bytes
description:
Number of packets transmitted by this queue
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets trasmitted by this queue
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of packets dropped by the queue due to overrun, that is tail-drop
or AMQ (RED, WRED, etc) induced drops as indicated by the attached
queue-management-profile
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets dropped by the queue due to overrun, that is tail-drop
or AMQ (RED, WRED, etc) induced drops as indicated by the attached
queue-management-profile
nodetype: leaf (ro)
type: oc-yang:counter64
description:
number of packets for which ECN codepoint has been changed from ECT to CE
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets for which ECN codepoint has been changed from ECT to CE
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of packets selected by AQM
For RED/WRED AQM this counter counts:
- all packets enqueued while queue utilization was greater then max-threshold
- packs enqueued while queue utilization was between min-threshold and max-threshold, with probability derived from RED/WRED slope
Packets are counted regardless of its ECN codepoint
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets of packets selected by AQM
For RED/WRED AQM this counter counts:
- all octets enqueued while queue utilization was greater then max-threshold
- octets enqueued while queue utilization was between min-threshold and max-threshold, with probability derived from RED/WRED slope
Octets are counted regardless of its ECN codepoint
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Scheduler policy associated with the interface.
nodetype: container (rw)
description:
Configuration parameters relating to a scheduler policy on
an interface.
nodetype: container (rw)
description:
The scheduler policy to be applied to traffic on this interface.
nodetype: leaf (rw)
type: leafref
description:
Operational state parameters relating to a scheduler policy
on an interface.
nodetype: container (ro)
description:
The scheduler policy to be applied to traffic on this interface.
nodetype: leaf (ro)
type: leafref
description:
Schedulers within the applied scheduler-policy.
nodetype: container (ro)
description:
List of the schedulers that are part of the scheduler-policy
specified.
nodetype: list (ro)
list keys: [sequence]
description:
Reference to the sequence ID for the scheduler.
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state parameters relating to the scheduler
policy.
nodetype: container (ro)
description:
Reference to the sequence ID of the scheduler within
the current scheduler policy.
nodetype: leaf (ro)
type: leafref
description:
The number of packets that were considered conforming by
the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of octets in packets that were considered
conforming by the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of packets that were considered exceeding by
the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of octets in packets that were considered
exceeding by the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of packets that were considered violating by
the policer.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of octets in packets that were considered
violating by the policer.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Surrounding container for the list of egress interfaces
for which virtual output queues are instantiated on this
interface.
nodetype: container (rw)
description:
List of egress interfaces for which a virtual output
queue is instantiated at this interface.
nodetype: list (rw)
list keys: [name]
description:
Name used to refer to the egress interface.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters relating to the interface
for which the VOQs are instantiated.
nodetype: container (rw)
description:
Name used to refer to the egress interface.
nodetype: leaf (rw)
type: string
description:
Operational state parameters relating to the interface
for which the VOQs are instantiated.
nodetype: container (ro)
description:
Name used to refer to the egress interface.
nodetype: leaf (ro)
type: string
description:
Surrounding container for a list of queues that are
instantiated on an interface.
nodetype: container (rw)
description:
Top-level container for the queue associated with this
interface
nodetype: list (rw)
list keys: [name]
description:
Reference to the name of the queue
instantiated on the interface.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the queue associated with the
interface
nodetype: container (rw)
description:
Reference to the queue associated with this interface.
A queue may be explicitly configured, or implicitly created
by the system based on default queues that are instantiated
by a hardware component, or are assumed to be default on
the system.
nodetype: leaf (rw)
type: string
description:
Operational state data for the queue associated with the
interface
nodetype: container (ro)
description:
Reference to the queue associated with this interface.
A queue may be explicitly configured, or implicitly created
by the system based on default queues that are instantiated
by a hardware component, or are assumed to be default on
the system.
nodetype: leaf (ro)
type: string
description:
Maximum observed queue length
nodetype: leaf (ro)
type: oc-yang:counter64
units: bytes
description:
Average observed queue length
nodetype: leaf (ro)
type: oc-yang:counter64
units: bytes
description:
Number of packets transmitted by this queue
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets trasmitted by this queue
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of packets dropped by the queue due to overrun, that is tail-drop
or AMQ (RED, WRED, etc) induced drops as indicated by the attached
queue-management-profile
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets dropped by the queue due to overrun, that is tail-drop
or AMQ (RED, WRED, etc) induced drops as indicated by the attached
queue-management-profile
nodetype: leaf (ro)
type: oc-yang:counter64
description:
number of packets for which ECN codepoint has been changed from ECT to CE
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets for which ECN codepoint has been changed from ECT to CE
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of packets selected by AQM
For RED/WRED AQM this counter counts:
- all packets enqueued while queue utilization was greater then max-threshold
- packs enqueued while queue utilization was between min-threshold and max-threshold, with probability derived from RED/WRED slope
Packets are counted regardless of its ECN codepoint
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets of packets selected by AQM
For RED/WRED AQM this counter counts:
- all octets enqueued while queue utilization was greater then max-threshold
- octets enqueued while queue utilization was between min-threshold and max-threshold, with probability derived from RED/WRED slope
Octets are counted regardless of its ECN codepoint
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Top-level container for QoS data related to the egress
interface.
nodetype: container (rw)
description:
Configuration data for QoS on the egress interface
nodetype: container (rw)
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This leaf is used in deployment cases where the operator or system
requires common allocation profiles covering unicast and multicast
packets.
nodetype: leaf (rw)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only multicast packets on
the interface - if specified, the unicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to unicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (rw)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only unicast packets on
the interface - if specified, the multicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to multicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for QoS on the egress interface
nodetype: container (ro)
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This leaf is used in deployment cases where the operator or system
requires common allocation profiles covering unicast and multicast
packets.
nodetype: leaf (ro)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only multicast packets on
the interface - if specified, the unicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to unicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (ro)
type: leafref
description:
The buffer allocation profile that is to be used for the interface.
This profile specifies how memory that is available to the interface
should be allocated amongst the queues that are instantiated on the
interface.
This reference specifies the policy that should be used for memory
allocated to the output (tx) queueing.
This buffer allocation profile applies to only unicast packets on
the interface - if specified, the multicast-buffer-allocation-profile
governs the allocation profile used for memory dedicated to multicast.
If a system does not support, or an operator does not require separate
buffer-allocation-profiles, this is specified by use of the
buffer-allocation-profile leaf.
nodetype: leaf (ro)
type: leafref
description:
Classifiers to be applied to the interface.
nodetype: container (rw)
description:
A list of classifiers that should be applied to the interface
nodetype: list (rw)
list keys: [type]
description:
Reference to the classifier name.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters for the list of classifiers.
nodetype: container (rw)
description:
Reference to the classifier to be applied to ingress traffic on
the interface
nodetype: leaf (rw)
type: leafref
description:
Type of packets matched by the classifier.
nodetype: leaf (rw)
type: enumeration
description:
Operational state parameters for the list of classifiers.
nodetype: container (ro)
description:
Reference to the classifier to be applied to ingress traffic on
the interface
nodetype: leaf (ro)
type: leafref
description:
Type of packets matched by the classifier.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container for the list of match terms in the
classifier
nodetype: container (rw)
description:
List of match terms in the classifier associated with the
interface
nodetype: list (ro)
list keys: [id]
description:
Reference to match term id list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state data for match terms in the classifier
associated with an interface
nodetype: container (ro)
description:
Reference to match terms in the classifier
nodetype: leaf (ro)
type: leafref
description:
Count of the number of packets matching this classifier
match term on the interface.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Count of the number of octets (bytes) matching this
classifier match term on the interface.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Surrounding container for a list of queues that are
instantiated on an interface.
nodetype: container (rw)
description:
Top-level container for the queue associated with this
interface
nodetype: list (rw)
list keys: [name]
description:
Reference to the name of the queue
instantiated on the interface.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the queue associated with the
interface
nodetype: container (rw)
description:
Reference to the queue associated with this interface.
A queue may be explicitly configured, or implicitly created
by the system based on default queues that are instantiated
by a hardware component, or are assumed to be default on
the system.
nodetype: leaf (rw)
type: string
description:
The queue management profile that is to be used for the queue
on the interface.
For example, the system may use a profile which specifies that
WRED curves are used for setting an ECN mark in the IP header
instead of dropping a packet in order to signal impending
congestion and for determining when there is sufficient
congestion to tail drop packets.
A single profile is available per queue - which applies to all packets
that are enqueued to the specified queue, whether they are unicast or
multicast.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for the queue associated with the
interface
nodetype: container (ro)
description:
Reference to the queue associated with this interface.
A queue may be explicitly configured, or implicitly created
by the system based on default queues that are instantiated
by a hardware component, or are assumed to be default on
the system.
nodetype: leaf (ro)
type: string
description:
The queue management profile that is to be used for the queue
on the interface.
For example, the system may use a profile which specifies that
WRED curves are used for setting an ECN mark in the IP header
instead of dropping a packet in order to signal impending
congestion and for determining when there is sufficient
congestion to tail drop packets.
A single profile is available per queue - which applies to all packets
that are enqueued to the specified queue, whether they are unicast or
multicast.
nodetype: leaf (ro)
type: leafref
description:
Maximum observed queue length
nodetype: leaf (ro)
type: oc-yang:counter64
units: bytes
description:
Average observed queue length
nodetype: leaf (ro)
type: oc-yang:counter64
units: bytes
description:
Number of packets transmitted by this queue
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets trasmitted by this queue
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of packets dropped by the queue due to overrun, that is tail-drop
or AMQ (RED, WRED, etc) induced drops as indicated by the attached
queue-management-profile
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets dropped by the queue due to overrun, that is tail-drop
or AMQ (RED, WRED, etc) induced drops as indicated by the attached
queue-management-profile
nodetype: leaf (ro)
type: oc-yang:counter64
description:
number of packets for which ECN codepoint has been changed from ECT to CE
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets for which ECN codepoint has been changed from ECT to CE
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of packets selected by AQM
For RED/WRED AQM this counter counts:
- all packets enqueued while queue utilization was greater then max-threshold
- packs enqueued while queue utilization was between min-threshold and max-threshold, with probability derived from RED/WRED slope
Packets are counted regardless of its ECN codepoint
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of octets of packets selected by AQM
For RED/WRED AQM this counter counts:
- all octets enqueued while queue utilization was greater then max-threshold
- octets enqueued while queue utilization was between min-threshold and max-threshold, with probability derived from RED/WRED slope
Octets are counted regardless of its ECN codepoint
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Scheduler policy associated with the interface.
nodetype: container (rw)
description:
Configuration parameters relating to a scheduler policy on
an interface.
nodetype: container (rw)
description:
The scheduler policy to be applied to traffic on this interface.
nodetype: leaf (rw)
type: leafref
description:
Operational state parameters relating to a scheduler policy
on an interface.
nodetype: container (ro)
description:
The scheduler policy to be applied to traffic on this interface.
nodetype: leaf (ro)
type: leafref
description:
Schedulers within the applied scheduler-policy.
nodetype: container (ro)
description:
List of the schedulers that are part of the scheduler-policy
specified.
nodetype: list (ro)
list keys: [sequence]
description:
Reference to the sequence ID for the scheduler.
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state parameters relating to the scheduler
policy.
nodetype: container (ro)
description:
Reference to the sequence ID of the scheduler within
the current scheduler policy.
nodetype: leaf (ro)
type: leafref
description:
The number of packets that were considered conforming by
the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of octets in packets that were considered
conforming by the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of packets that were considered exceeding by
the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of octets in packets that were considered
exceeding by the scheduler.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of packets that were considered violating by
the policer.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The number of octets in packets that were considered
violating by the policer.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Enclosing container for QoS classifiers
nodetype: container (rw)
description:
List of classifier elements
nodetype: list (rw)
list keys: [name]
description:
Reference to list key name
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for classifers
nodetype: container (rw)
description:
User-assigned name of the classifier
nodetype: leaf (rw)
type: string
description:
Type of classifier.
nodetype: leaf (rw)
type: enumeration
description:
Operational state data for classifiers
nodetype: container (ro)
description:
User-assigned name of the classifier
nodetype: leaf (ro)
type: string
description:
Type of classifier.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container for ths list of terms
nodetype: container (rw)
description:
List of match terms used in the classifier
nodetype: list (rw)
list keys: [id]
description:
Reference to id list key.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for list of match criteria in a QoS
classifier
nodetype: container (rw)
description:
Identifier for the match term
nodetype: leaf (rw)
type: string
description:
Operational state data for list of match criteria in a
QoS classifier
nodetype: container (ro)
description:
Identifier for the match term
nodetype: leaf (ro)
type: string
description:
Conditions for the classifier term. Packets must match all of
the criteria specified within the match condition to be considered
matching the term.
nodetype: container (rw)
description:
Ethernet header fields
nodetype: container (rw)
description:
Configuration data
nodetype: container (rw)
description:
Source IEEE 802 MAC address.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Source IEEE 802 MAC address mask.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address mask.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Ethertype field to match in Ethernet packets
nodetype: leaf (rw)
type: oc-pkt-match-types:ethertype-type
description:
State Information.
nodetype: container (ro)
description:
Source IEEE 802 MAC address.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Source IEEE 802 MAC address mask.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address mask.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Ethertype field to match in Ethernet packets
nodetype: leaf (ro)
type: oc-pkt-match-types:ethertype-type
description:
Top level container for IPv4 match field data
nodetype: container (rw)
description:
Configuration data for IPv4 match fields
nodetype: container (rw)
description:
Source IPv4 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv4-prefix
description:
Reference to a IPv4 address prefix Set
to match the source address
nodetype: leaf (rw)
type: leafref
description:
Destination IPv4 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv4-prefix
description:
Reference to a IPv4 address prefix set
to match the destination address
nodetype: leaf (rw)
type: leafref
description:
Value of diffserv codepoint.
nodetype: leaf (rw)
type: oc-inet:dscp
description:
A list of DSCP values to be matched for incoming packets. AN OR match should
be performed, such that a packet must match one of the values defined in this
list. If the field is left empty then any DSCP value matches unless the 'dscp'
leaf is specified. It is not valid to specify both 'dscp' and 'dscp-set together.'
nodetype: leaf-list (rw)
type: oc-inet:dscp
description:
In the IPv4 header field, this field is known as the Total
Length. Total Length is the length of the datagram, measured
in octets, including internet header and data.
In the IPv6 header field, this field is known as the Payload
Length, which is the length of the IPv6 payload, i.e., the rest
of the packet following the IPv6 header, in octets.
nodetype: leaf (rw)
type: uint16
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (rw)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (rw)
type: uint8
description:
State information for IPv4 match fields
nodetype: container (ro)
description:
Source IPv4 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv4-prefix
description:
Reference to a IPv4 address prefix Set
to match the source address
nodetype: leaf (ro)
type: leafref
description:
Destination IPv4 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv4-prefix
description:
Reference to a IPv4 address prefix set
to match the destination address
nodetype: leaf (ro)
type: leafref
description:
Value of diffserv codepoint.
nodetype: leaf (ro)
type: oc-inet:dscp
description:
A list of DSCP values to be matched for incoming packets. AN OR match should
be performed, such that a packet must match one of the values defined in this
list. If the field is left empty then any DSCP value matches unless the 'dscp'
leaf is specified. It is not valid to specify both 'dscp' and 'dscp-set together.'
nodetype: leaf-list (ro)
type: oc-inet:dscp
description:
In the IPv4 header field, this field is known as the Total
Length. Total Length is the length of the datagram, measured
in octets, including internet header and data.
In the IPv6 header field, this field is known as the Payload
Length, which is the length of the IPv6 payload, i.e., the rest
of the packet following the IPv6 header, in octets.
nodetype: leaf (ro)
type: uint16
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (ro)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (ro)
type: uint8
description:
Top container for ICMPv4 filtering
nodetype: container (rw)
description:
Configuration attributes for ICMPv4 filtering
nodetype: container (rw)
description:
ICMPv4 type to be matched.
nodetype: leaf (rw)
type: identityref
description:
ICMPv4 code to be matched.
nodetype: leaf (rw)
type: identityref
description:
State attributes for ICMPv4 filtering
nodetype: container (ro)
description:
ICMPv4 type to be matched.
nodetype: leaf (ro)
type: identityref
description:
ICMPv4 code to be matched.
nodetype: leaf (ro)
type: identityref
description:
Top-level container for IPv6 match field data
nodetype: container (rw)
description:
Configuration data for IPv6 match fields
nodetype: container (rw)
description:
Source IPv6 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv6-prefix
description:
Reference to a IPv6 address prefix set
to match the source address
nodetype: leaf (rw)
type: leafref
description:
Source IPv6 Flow label.
nodetype: leaf (rw)
type: oc-inet:ipv6-flow-label
description:
Destination IPv6 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv6-prefix
description:
Reference to a IPv6 address prefix set
to match the destination address
nodetype: leaf (rw)
type: leafref
description:
Destination IPv6 Flow label.
nodetype: leaf (rw)
type: oc-inet:ipv6-flow-label
description:
Value of diffserv codepoint.
nodetype: leaf (rw)
type: oc-inet:dscp
description:
A list of DSCP values to be matched for incoming packets. AN OR match should
be performed, such that a packet must match one of the values defined in this
list. If the field is left empty then any DSCP value matches unless the 'dscp'
leaf is specified. It is not valid to specify both 'dscp' and 'dscp-set together.'
nodetype: leaf-list (rw)
type: oc-inet:dscp
description:
In the IPv4 header field, this field is known as the Total
Length. Total Length is the length of the datagram, measured
in octets, including internet header and data.
In the IPv6 header field, this field is known as the Payload
Length, which is the length of the IPv6 payload, i.e., the rest
of the packet following the IPv6 header, in octets.
nodetype: leaf (rw)
type: uint16
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (rw)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (rw)
type: uint8
description:
Operational state data for IPv6 match fields
nodetype: container (ro)
description:
Source IPv6 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv6-prefix
description:
Reference to a IPv6 address prefix set
to match the source address
nodetype: leaf (ro)
type: leafref
description:
Source IPv6 Flow label.
nodetype: leaf (ro)
type: oc-inet:ipv6-flow-label
description:
Destination IPv6 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv6-prefix
description:
Reference to a IPv6 address prefix set
to match the destination address
nodetype: leaf (ro)
type: leafref
description:
Destination IPv6 Flow label.
nodetype: leaf (ro)
type: oc-inet:ipv6-flow-label
description:
Value of diffserv codepoint.
nodetype: leaf (ro)
type: oc-inet:dscp
description:
A list of DSCP values to be matched for incoming packets. AN OR match should
be performed, such that a packet must match one of the values defined in this
list. If the field is left empty then any DSCP value matches unless the 'dscp'
leaf is specified. It is not valid to specify both 'dscp' and 'dscp-set together.'
nodetype: leaf-list (ro)
type: oc-inet:dscp
description:
In the IPv4 header field, this field is known as the Total
Length. Total Length is the length of the datagram, measured
in octets, including internet header and data.
In the IPv6 header field, this field is known as the Payload
Length, which is the length of the IPv6 payload, i.e., the rest
of the packet following the IPv6 header, in octets.
nodetype: leaf (ro)
type: uint16
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (ro)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (ro)
type: uint8
description:
Top container for ICMPv6 filtering
nodetype: container (rw)
description:
Configuration attributes for ICMPv6 filtering
nodetype: container (rw)
description:
ICMPv6 type to be matched.
nodetype: leaf (rw)
type: identityref
description:
ICMP code to be matched.
nodetype: leaf (rw)
type: identityref
description:
State attributes for ICMPv6 filtering
nodetype: container (ro)
description:
ICMPv6 type to be matched.
nodetype: leaf (ro)
type: identityref
description:
ICMP code to be matched.
nodetype: leaf (ro)
type: identityref
description:
Transport fields container
nodetype: container (rw)
description:
Configuration data
nodetype: container (rw)
description:
Source port or range
nodetype: leaf (rw)
type: oc-pkt-match-types:port-num-range
description:
Reference to a port set
to match the source port
nodetype: leaf (rw)
type: leafref
description:
Destination port or range
nodetype: leaf (rw)
type: oc-pkt-match-types:port-num-range
description:
Reference to a port set
to match the destination port
nodetype: leaf (rw)
type: leafref
description:
Mode that is used for matching detailed fields at the transport
layer. When EXPLICIT is specified, the implementation should
match based on the explicit flags that are specified in the
corresponding leaf. When BUILTIN is specified, the implementation
must expand the contents of the corresponding leaf to the flags
and/or fields that match the pre-defined built-in values.
nodetype: leaf (rw)
type: enumeration
description:
Specifies how the contents of the explicit-details-flags list
are to be treated. ANY implies that any of the flags may match,
where ALL indicates that all the flags must be matched.
nodetype: leaf (rw)
type: enumeration
description:
An explicit list of the TCP flags that are to be matched. The
mechanism for the match is specified by the explicit-detail-match-mode
leaf.
nodetype: leaf-list (rw)
type: identityref
description:
Specifies a built-in (alias) for a match condition that matches
multiple flags, or specifies particular logic as to the flag matches
to be implemented. This leaf is only valid when the detail-match-mode
leaf is BUILTIN.
nodetype: leaf (rw)
type: enumeration
description:
State data
nodetype: container (ro)
description:
Source port or range
nodetype: leaf (ro)
type: oc-pkt-match-types:port-num-range
description:
Reference to a port set
to match the source port
nodetype: leaf (ro)
type: leafref
description:
Destination port or range
nodetype: leaf (ro)
type: oc-pkt-match-types:port-num-range
description:
Reference to a port set
to match the destination port
nodetype: leaf (ro)
type: leafref
description:
Mode that is used for matching detailed fields at the transport
layer. When EXPLICIT is specified, the implementation should
match based on the explicit flags that are specified in the
corresponding leaf. When BUILTIN is specified, the implementation
must expand the contents of the corresponding leaf to the flags
and/or fields that match the pre-defined built-in values.
nodetype: leaf (ro)
type: enumeration
description:
Specifies how the contents of the explicit-details-flags list
are to be treated. ANY implies that any of the flags may match,
where ALL indicates that all the flags must be matched.
nodetype: leaf (ro)
type: enumeration
description:
An explicit list of the TCP flags that are to be matched. The
mechanism for the match is specified by the explicit-detail-match-mode
leaf.
nodetype: leaf-list (ro)
type: identityref
description:
Specifies a built-in (alias) for a match condition that matches
multiple flags, or specifies particular logic as to the flag matches
to be implemented. This leaf is only valid when the detail-match-mode
leaf is BUILTIN.
nodetype: leaf (ro)
type: enumeration
description:
MPLS header fields
nodetype: container (rw)
description:
Configuration parameters relating to fields within
the MPLS header.
nodetype: container (rw)
description:
The value of the MPLS traffic class (TC) bits,
formerly known as the EXP bits.
nodetype: leaf (rw)
type: oc-mpls:mpls-tc
description:
Match MPLS label value on the MPLS header.
The usage of this field indicated the upper
range value in the top of the stack.
The range that is used is inclusive. The match that
is done for a particular received pkt_label is:
start-label-value <= pkt_label <= end-label-value.
The 20-bit label value in an MPLS label
stack as specified in RFC 3032.
This label value does not include the
encodings of Traffic Class and TTL.
nodetype: leaf (rw)
type: oc-mpls:mpls-label
description:
Match MPLS label value on the MPLS header.
The usage of this field indicated the upper
range value in the top of the stack.
The range that is used is inclusive. The match that
is done for a particular received pkt_label is:
start-label-value <= pkt_label <= end-label-value.
The 20-bit label value in an MPLS label
stack as specified in RFC 3032.
This label value does not include the
encodings of Traffic Class and TTL.
nodetype: leaf (rw)
type: oc-mpls:mpls-label
description:
Time-to-live MPLS packet value match.
nodetype: leaf (rw)
type: uint8
description:
Operational state parameters relating to fields
within the MPLS header
nodetype: container (ro)
description:
The value of the MPLS traffic class (TC) bits,
formerly known as the EXP bits.
nodetype: leaf (ro)
type: oc-mpls:mpls-tc
description:
Match MPLS label value on the MPLS header.
The usage of this field indicated the upper
range value in the top of the stack.
The range that is used is inclusive. The match that
is done for a particular received pkt_label is:
start-label-value <= pkt_label <= end-label-value.
The 20-bit label value in an MPLS label
stack as specified in RFC 3032.
This label value does not include the
encodings of Traffic Class and TTL.
nodetype: leaf (ro)
type: oc-mpls:mpls-label
description:
Match MPLS label value on the MPLS header.
The usage of this field indicated the upper
range value in the top of the stack.
The range that is used is inclusive. The match that
is done for a particular received pkt_label is:
start-label-value <= pkt_label <= end-label-value.
The 20-bit label value in an MPLS label
stack as specified in RFC 3032.
This label value does not include the
encodings of Traffic Class and TTL.
nodetype: leaf (ro)
type: oc-mpls:mpls-label
description:
Time-to-live MPLS packet value match.
nodetype: leaf (ro)
type: uint8
description:
Actions to be applied for packets matching the specified
classification rules.
nodetype: container (rw)
description:
Actions to be applied to packets that match the classifier
term.
nodetype: container (rw)
description:
References the forwarding group or class to which the
matched packets should be assigned
nodetype: leaf (rw)
type: leafref
description:
Operational state parameters associated with classifier term
actions
nodetype: container (ro)
description:
References the forwarding group or class to which the
matched packets should be assigned
nodetype: leaf (ro)
type: leafref
description:
Remark actions to be associated with packets that match the
classifier term. Where a packet matches these criteria, the
specified rewrite actions should be performed.
nodetype: container (rw)
description:
Configuration parameters relating to remarking packets.
nodetype: container (rw)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (rw)
type: uint8
description:
Operational state parameters relating to remarking packets.
nodetype: container (ro)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (ro)
type: uint8
description:
Enclosing container for list of forwarding groups
nodetype: container (rw)
description:
List of forwarding groups. Forwarding groups are
logical groups of traffic that will receive common
forwarding treatment.
nodetype: list (rw)
list keys: [name]
description:
Reference to name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for forwarding groups
nodetype: container (rw)
description:
Name of the forwarding group
nodetype: leaf (rw)
type: string
description:
Set the priority for the forwarding group for
local transmission through the device, e.g.,
across a switching fabric. Higher priorities
are considered to be better, such that traffic
with fabric priority 128 is considered to be
higher priority than that with fabric priority
0.
nodetype: leaf (rw)
type: uint8
description:
Output queue for packets in this forwarding group.
This leaf applies to both multicast and unicast
packets. Where a user or system requires separate
queueing for multicast and unicast the unicast-output-queue
and multicast-output-queue leaves should be specified.
nodetype: leaf (rw)
type: leafref
description:
Output queue for unicast packets within this
forwarding group. Where an operator or system does
not require separate queueing for multicast and
unicast this leaf is not specified.
nodetype: leaf (rw)
type: leafref
description:
Output queue for multicast packets within this
forwarding group. Where an operator or system does
not require separate queueing for multicast and
unicast this leaf is not specified.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for forwarding groups
nodetype: container (ro)
description:
Name of the forwarding group
nodetype: leaf (ro)
type: string
description:
Set the priority for the forwarding group for
local transmission through the device, e.g.,
across a switching fabric. Higher priorities
are considered to be better, such that traffic
with fabric priority 128 is considered to be
higher priority than that with fabric priority
0.
nodetype: leaf (ro)
type: uint8
description:
Output queue for packets in this forwarding group.
This leaf applies to both multicast and unicast
packets. Where a user or system requires separate
queueing for multicast and unicast the unicast-output-queue
and multicast-output-queue leaves should be specified.
nodetype: leaf (ro)
type: leafref
description:
Output queue for unicast packets within this
forwarding group. Where an operator or system does
not require separate queueing for multicast and
unicast this leaf is not specified.
nodetype: leaf (ro)
type: leafref
description:
Output queue for multicast packets within this
forwarding group. Where an operator or system does
not require separate queueing for multicast and
unicast this leaf is not specified.
nodetype: leaf (ro)
type: leafref
description:
Enclosing container for the list of queues
nodetype: container (rw)
description:
List of defined queues
nodetype: list (rw)
list keys: [name]
description:
Reference to the queue name list key.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for queues
nodetype: container (rw)
description:
User-defined name of the queue
nodetype: leaf (rw)
type: string
description:
An optional identifier which may be required by some hardware to map
the named queue to a hardware queue
nodetype: leaf (rw)
type: uint8
description:
Operational state data for queues
nodetype: container (ro)
description:
User-defined name of the queue
nodetype: leaf (ro)
type: string
description:
An optional identifier which may be required by some hardware to map
the named queue to a hardware queue
nodetype: leaf (ro)
type: uint8
description:
Enclosing container for the list of configured scheduler policies.
nodetype: container (rw)
description:
List of scheduler policies. A scheduler policy is a set of schedulers
that are to be applied together. Each scheduler within a scheduler
policy takes an input, and outputs it according to a scheduling
discipline that is specified within it. The schedulers consume
resources according to the specification that is provided - which
may be absolute resource limits, or relative.
nodetype: list (rw)
list keys: [name]
description:
Reference to the name of the scheduler policy
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters relating to a scheduler policy.
nodetype: container (rw)
description:
Name for the scheduler policy.
nodetype: leaf (rw)
type: string
description:
Operational state parameters relating to a scheduler policy.
nodetype: container (ro)
description:
Name for the scheduler policy.
nodetype: leaf (ro)
type: string
description:
Schedulers within the scheduler policy.
nodetype: container (rw)
description:
List of defined QoS traffic schedulers.
nodetype: list (rw)
list keys: [sequence]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for QoS schedulers
nodetype: container (rw)
description:
Sequence number for the scheduler within the scheduler
policy. Schedulers are processed from lowest sequence
to highest.
nodetype: leaf (rw)
type: uint32
description:
Sets the type of scheduler, i.e. the scheduling algorithm
used to serve inputs.
nodetype: leaf (rw)
type: identityref
description:
Priority of the scheduler within the scheduler policy.
nodetype: leaf (rw)
type: enumeration
description:
Operational state data for QoS schedulers
nodetype: container (ro)
description:
Sequence number for the scheduler within the scheduler
policy. Schedulers are processed from lowest sequence
to highest.
nodetype: leaf (ro)
type: uint32
description:
Sets the type of scheduler, i.e. the scheduling algorithm
used to serve inputs.
nodetype: leaf (ro)
type: identityref
description:
Priority of the scheduler within the scheduler policy.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container
nodetype: container (rw)
description:
List of input sources for the scheduler.
nodetype: list (rw)
list keys: [id]
description:
Reference to list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for scheduler input sources
nodetype: container (rw)
description:
User-defined identifier for the scheduler input
nodetype: leaf (rw)
type: string
description:
Describes the type of input source for the scheduler
nodetype: leaf (rw)
type: enumeration
description:
Reference to a queue that is an input source for the
scheduler
nodetype: leaf (rw)
type: leafref
description:
For priority schedulers, this indicates the priority of
the corresponding input. Higher values indicate higher
priority. For weighted round-robin schedulers, this leaf
indicates the weight of the corresponding input.
nodetype: leaf (rw)
type: uint64
description:
Operational state data for scheduler input sources
nodetype: container (ro)
description:
User-defined identifier for the scheduler input
nodetype: leaf (ro)
type: string
description:
Describes the type of input source for the scheduler
nodetype: leaf (ro)
type: enumeration
description:
Reference to a queue that is an input source for the
scheduler
nodetype: leaf (ro)
type: leafref
description:
For priority schedulers, this indicates the priority of
the corresponding input. Higher values indicate higher
priority. For weighted round-robin schedulers, this leaf
indicates the weight of the corresponding input.
nodetype: leaf (ro)
type: uint64
description:
Top-level container for scheduler output data
nodetype: container (rw)
description:
Configuration data for scheduler output
nodetype: container (rw)
description:
Describes the type of output sink for the scheduler.
nodetype: leaf (rw)
type: enumeration
description:
When the scheduler output type is a child scheduler,
this leaf provides a reference to the downstream
scheduler.
nodetype: leaf (rw)
type: leafref
description:
When the scheduler output type is a forwarding group,
this leaf provides a reference to the forwarding group.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for scheduler output
nodetype: container (ro)
description:
Describes the type of output sink for the scheduler.
nodetype: leaf (ro)
type: enumeration
description:
When the scheduler output type is a child scheduler,
this leaf provides a reference to the downstream
scheduler.
nodetype: leaf (ro)
type: leafref
description:
When the scheduler output type is a forwarding group,
this leaf provides a reference to the forwarding group.
nodetype: leaf (ro)
type: leafref
description:
Top-level container for data related to a 1 rate, 2 color
shaper.
nodetype: container (rw)
description:
Configuration data for 1 rate, 2 color shapers
nodetype: container (rw)
description:
Committed information rate for the single-rate token
bucket scheduler. This value represents the rate at which
tokens are added to the bucket.
nodetype: leaf (rw)
type: uint64
units: bps
description:
Committed information rate for the single-rate token
bucket scheduler. This value represents the rate at which
tokens are added to the bucket. It is expressed as a
percentage of the total bandwidth allocated to the
context in which the scheduler is referenced.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Committed information rate for the single-rate token
bucket scheduler. This value represents the rate at which
tokens are added to the bucket. It is expressed as a
percentage of the unallocated bandwidth available in the
context in which the scheduled is referenced.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Committed burst size for the single-rate token bucket
scheduler. This value represents the depth of the token
bucket.
nodetype: leaf (rw)
type: uint32
units: bytes
description:
The type of scheduler that is being configured.
nodetype: leaf (rw)
type: oc-qos-types:queue-behavior
description:
When the scheduler is specified to be a shaper - the
maximum depth of the queue in bytes is the value
specified by this leaf.
nodetype: leaf (rw)
type: uint32
units: bytes
description:
When the scheduler is specified to be a shaper - the
maximum depth of the queue in packets is the value
specified by this leaf.
nodetype: leaf (rw)
type: uint32
units: packets
description:
The queue depth specified as a percentage of the total
available buffer that is avaialble.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Operational state data for 1 rate, 2 color shapers
nodetype: container (ro)
description:
Committed information rate for the single-rate token
bucket scheduler. This value represents the rate at which
tokens are added to the bucket.
nodetype: leaf (ro)
type: uint64
units: bps
description:
Committed information rate for the single-rate token
bucket scheduler. This value represents the rate at which
tokens are added to the bucket. It is expressed as a
percentage of the total bandwidth allocated to the
context in which the scheduler is referenced.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Committed information rate for the single-rate token
bucket scheduler. This value represents the rate at which
tokens are added to the bucket. It is expressed as a
percentage of the unallocated bandwidth available in the
context in which the scheduled is referenced.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Committed burst size for the single-rate token bucket
scheduler. This value represents the depth of the token
bucket.
nodetype: leaf (ro)
type: uint32
units: bytes
description:
The type of scheduler that is being configured.
nodetype: leaf (ro)
type: oc-qos-types:queue-behavior
description:
When the scheduler is specified to be a shaper - the
maximum depth of the queue in bytes is the value
specified by this leaf.
nodetype: leaf (ro)
type: uint32
units: bytes
description:
When the scheduler is specified to be a shaper - the
maximum depth of the queue in packets is the value
specified by this leaf.
nodetype: leaf (ro)
type: uint32
units: packets
description:
The queue depth specified as a percentage of the total
available buffer that is avaialble.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Action to be applied to packets that are scheduled within the
CIR of the one-rate, two-colour scheduler. Packets that receive
a token from the in-CIR bucket are said to be conforming and
have all of the specified actions applied.
nodetype: container (rw)
description:
Configuration parameters relating to conforming packets for the
1r2c scheduler.
nodetype: container (rw)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (rw)
type: uint8
description:
Operational state parameters relating to conforming packets
for the 1r2c scheduler.
nodetype: container (ro)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (ro)
type: uint8
description:
Action to be applied to packets that are scheduled above the CIR
of the one-rate, two-colour shaper. Packets that do not receive a
token from the in-CIR bucket are said to be exceeding, and have
all of the specified actions applied.
nodetype: container (rw)
description:
Configuration parameters relating to exceeding packets for
the 1r2c scheduler.
nodetype: container (rw)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (rw)
type: uint8
description:
If set to true, packets within this context are dropped.
nodetype: leaf (rw)
type: boolean
description:
Operational state parameters relating to exceeding
packets for the 1r2c scheduler.
nodetype: container (ro)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (ro)
type: uint8
description:
If set to true, packets within this context are dropped.
nodetype: leaf (ro)
type: boolean
description:
Top-level container for data for a 2 rate, 3 color policer.
nodetype: container (rw)
description:
Configuration data for 2 rate, 3 color policers.
nodetype: container (rw)
description:
Committed information rate for the dual-rate token
bucket policer. This value represents the rate at which
tokens are added to the primary bucket.
nodetype: leaf (rw)
type: uint64
units: bps
description:
Committed information rate for the dual-rate token bucket
policer. This value represents the rate at which tokens
are added to the primary bucket. It is expressed as a
percentage of the total bandwidth available within the
context the scheduler is instantiated.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Committed information rate for the dual-rate token
bucket policer. This value represents the rate at which
tokens are added to the primary bucket. It is expressed
as a percentage of the remaining bandwidth within the
context the scheduler is instantiated.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Peak information rate for the dual-rate token bucket
policer. This value represents the rate at which tokens
are added to the secondary bucket.
nodetype: leaf (rw)
type: uint64
units: bps
description:
Peak information rate for the dual-rate token bucket
policer. This value represents the rate at which tokens
are added to the secondary bucket. The value is expressed
as a percentage of the total bandwidth available in the
context in which the scheduler is instantiated.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Peak information rate for the dual-rate token
bucket policer. This value represents the rate at which
tokens are added to the secondary bucket. It is expressed
as a percentage of the remaining bandwidth within the
context the scheduler is instantiated.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Committed burst size for the dual-rate token bucket
policer. This value represents the depth of the token
bucket.
nodetype: leaf (rw)
type: uint32
units: bytes
description:
Excess burst size for the dual-rate token bucket policer.
This value represents the depth of the secondary bucket.
nodetype: leaf (rw)
type: uint32
units: bytes
description:
Operational state data for 2 rate, 3 color policers.
nodetype: container (ro)
description:
Committed information rate for the dual-rate token
bucket policer. This value represents the rate at which
tokens are added to the primary bucket.
nodetype: leaf (ro)
type: uint64
units: bps
description:
Committed information rate for the dual-rate token bucket
policer. This value represents the rate at which tokens
are added to the primary bucket. It is expressed as a
percentage of the total bandwidth available within the
context the scheduler is instantiated.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Committed information rate for the dual-rate token
bucket policer. This value represents the rate at which
tokens are added to the primary bucket. It is expressed
as a percentage of the remaining bandwidth within the
context the scheduler is instantiated.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Peak information rate for the dual-rate token bucket
policer. This value represents the rate at which tokens
are added to the secondary bucket.
nodetype: leaf (ro)
type: uint64
units: bps
description:
Peak information rate for the dual-rate token bucket
policer. This value represents the rate at which tokens
are added to the secondary bucket. The value is expressed
as a percentage of the total bandwidth available in the
context in which the scheduler is instantiated.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Peak information rate for the dual-rate token
bucket policer. This value represents the rate at which
tokens are added to the secondary bucket. It is expressed
as a percentage of the remaining bandwidth within the
context the scheduler is instantiated.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Committed burst size for the dual-rate token bucket
policer. This value represents the depth of the token
bucket.
nodetype: leaf (ro)
type: uint32
units: bytes
description:
Excess burst size for the dual-rate token bucket policer.
This value represents the depth of the secondary bucket.
nodetype: leaf (ro)
type: uint32
units: bytes
description:
Action to be applied to the packets that are scheduled
within the CIR of the policer. All packets that receive
a token from this bucket have all actions specified
applied to them
nodetype: container (rw)
description:
Configuration parameters for the conform action of a
2r3c policer.
nodetype: container (rw)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (rw)
type: uint8
description:
Operational state parameters relating to the conform
action of a 2r3c policer.
nodetype: container (ro)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (ro)
type: uint8
description:
Action to be applied to the packets that are scheduled
within the PIR of the policer. Packets that receive a
token from within the PIR allocation have all the
specified actions applied to them
nodetype: container (rw)
description:
Configuration parameters relating to the action
applied to exceeding packets.
nodetype: container (rw)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (rw)
type: uint8
description:
If set to true, packets within this context are dropped.
nodetype: leaf (rw)
type: boolean
description:
Operational state parameters relating to the action
applied to exceeding packets.
nodetype: container (ro)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (ro)
type: uint8
description:
If set to true, packets within this context are dropped.
nodetype: leaf (ro)
type: boolean
description:
Action to be applied to the packets that are scheduled
above the PIR of the policer. Packets that do not receive
a token from either bucket have all specified actions
applied to them.
nodetype: container (rw)
description:
Configuration parameters relating to the action
applied to violating packets.
nodetype: container (rw)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (rw)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (rw)
type: uint8
description:
If set to true, packets within this context are dropped.
nodetype: leaf (rw)
type: boolean
description:
Operational state parameters relating to the action
applied to violating packets.
nodetype: container (ro)
description:
Sets the 6-bit DSCP (differentiated services code point)
value in the IP packet header.
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit class-of-service value in the
Ethernet packet header for 802.1Q VLAN-tagged packets,
also known as PCP (priority code point).
nodetype: leaf (ro)
type: uint8
description:
Sets the 3-bit traffic class value (also referred to as EXP
or CoS) in MPLS packets.
nodetype: leaf (ro)
type: uint8
description:
If set to true, packets within this context are dropped.
nodetype: leaf (ro)
type: boolean
description:
Surrounding container for buffer allocation profiles.
nodetype: container (rw)
description:
A buffer allocation profile describes a mapping between the queues
that are instantiated on an interface and the memory that is allocated
to them on the forwarding complex that they are instantiated. Profiles
(like queues) are defined in the abstract and instantiated by being
configured on a particular interface. Separate allocation profiles may
be used for ingress and egress traffic, with the profile being specified
within the /qos/interfaces/interface list.
nodetype: list (rw)
list keys: [name]
description:
Reference to the unique name used as a key for each buffer profile.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters for a buffer-allocation-profile.
nodetype: container (rw)
description:
Unique string identifying the buffer allocation profile, used to
reference to the profile on interfaces.
nodetype: leaf (rw)
type: string
description:
Operational state parameters relating to a buffer-allocation-profile.
nodetype: container (ro)
description:
Unique string identifying the buffer allocation profile, used to
reference to the profile on interfaces.
nodetype: leaf (ro)
type: string
description:
Surrounding container for the queues that are referenced under a
buffer-allocation-policy.
nodetype: container (rw)
description:
Buffer allocation profile for a specific queue on the interface.
nodetype: list (rw)
list keys: [name]
description:
Reference to the name of the queue being referenced under the buffer
allocation profile.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters relating to a queue within a buffer allocation
profile.
nodetype: container (rw)
description:
Reference to the queue being referenced within the buffer allocation profile.
nodetype: leaf (rw)
type: leafref
description:
This is the dedicated buffer that is carved for the queue, this is the minimum
number of bytes reserved for this queue.
This leaf is mutualy exclusive with dedicated-buffer-temporal leaf
nodetype: leaf (rw)
type: uint64
units: bytes
description:
This is the dedicated buffer that is carved for the queue. The the minimum
number of bytes reserved for this queue is calculated by multiplying by interface speed
queue is attached to and queues minimum, guarantaed transmit share (derived
form WRR schedulers weights).
This leaf shouldbot be used for strict priority scheduled queues.
This leaf is mutualy exclusive with dedicated-buffer leaf
nodetype: leaf (rw)
type: uint64
units: microseconds
description:
If the flag is true, then the queue is allowed to use buffers from shared pool
in additional to the dedicated buffers assigned for this queue.
nodetype: leaf (rw)
type: boolean
description:
The type of limit used to specify the amount of buffer space that the queue
is allowed to use from the shared pool.
nodetype: leaf (rw)
type: identityref
description:
If the shared-buffer-limit-type is STATIC, then static-shared-buffer-limit is
the maximum number of bytes that the queue is allowed to use from the shared
pool.
This leaf is mutualy exclusive with static-shared-buffer-limit-temporal leaf.
nodetype: leaf (rw)
type: uint32
units: bytes
description:
If the shared-buffer-limit-type is STATIC, then static-shared-buffer-limit-temporal is
the maximum number of bytes that the queue is allowed to use from the shared
pool.
The the number of bytes is calculated by multiplying static-shared-buffer-limit-temporal
by interface speed the queue is attached to and queues minimum, guarantaed transmit share
(derived form WRR schedulers weights).
This leaf shouldbot be used for strict priority scheduled queues.
This leaf is mutualy exclusive with static-shared-buffer-limit leaf.
nodetype: leaf (rw)
type: uint32
units: microseconds
description:
If shared-buffer-limit-type is DYNAMIC_BASED_ON_SCALING_FACTOR, the scaling
factor and the current free space in the shared pool is used to determine the
maximum buffer sapce from the shared pool that the queue is allowed to use.
Example: If a queue is using 79MB and the other queues are using 11MB, the
free buffer is 10MB. If the configured scaling factor is 3 for the queue, the
maximum buffer space from the shared pool that the queue is allowed to use is
calculated as (free buffer * 2^scaling factor) ie. 10MB*2^3 = 80MB. Since the
current usage is 79MB which is < 80MB, the packet is queued.
nodetype: leaf (rw)
type: int32
description:
Operational state parameters relating to a queue wtihin a buffer allocation
profile.
nodetype: container (ro)
description:
Reference to the queue being referenced within the buffer allocation profile.
nodetype: leaf (ro)
type: leafref
description:
This is the dedicated buffer that is carved for the queue, this is the minimum
number of bytes reserved for this queue.
This leaf is mutualy exclusive with dedicated-buffer-temporal leaf
nodetype: leaf (ro)
type: uint64
units: bytes
description:
This is the dedicated buffer that is carved for the queue. The the minimum
number of bytes reserved for this queue is calculated by multiplying by interface speed
queue is attached to and queues minimum, guarantaed transmit share (derived
form WRR schedulers weights).
This leaf shouldbot be used for strict priority scheduled queues.
This leaf is mutualy exclusive with dedicated-buffer leaf
nodetype: leaf (ro)
type: uint64
units: microseconds
description:
If the flag is true, then the queue is allowed to use buffers from shared pool
in additional to the dedicated buffers assigned for this queue.
nodetype: leaf (ro)
type: boolean
description:
The type of limit used to specify the amount of buffer space that the queue
is allowed to use from the shared pool.
nodetype: leaf (ro)
type: identityref
description:
If the shared-buffer-limit-type is STATIC, then static-shared-buffer-limit is
the maximum number of bytes that the queue is allowed to use from the shared
pool.
This leaf is mutualy exclusive with static-shared-buffer-limit-temporal leaf.
nodetype: leaf (ro)
type: uint32
units: bytes
description:
If the shared-buffer-limit-type is STATIC, then static-shared-buffer-limit-temporal is
the maximum number of bytes that the queue is allowed to use from the shared
pool.
The the number of bytes is calculated by multiplying static-shared-buffer-limit-temporal
by interface speed the queue is attached to and queues minimum, guarantaed transmit share
(derived form WRR schedulers weights).
This leaf shouldbot be used for strict priority scheduled queues.
This leaf is mutualy exclusive with static-shared-buffer-limit leaf.
nodetype: leaf (ro)
type: uint32
units: microseconds
description:
If shared-buffer-limit-type is DYNAMIC_BASED_ON_SCALING_FACTOR, the scaling
factor and the current free space in the shared pool is used to determine the
maximum buffer sapce from the shared pool that the queue is allowed to use.
Example: If a queue is using 79MB and the other queues are using 11MB, the
free buffer is 10MB. If the configured scaling factor is 3 for the queue, the
maximum buffer space from the shared pool that the queue is allowed to use is
calculated as (free buffer * 2^scaling factor) ie. 10MB*2^3 = 80MB. Since the
current usage is 79MB which is < 80MB, the packet is queued.
nodetype: leaf (ro)
type: int32
description:
Surrounding container for the list of configured
queue management profiles.
nodetype: container (rw)
description:
A queue management profile within the OpenConfig QoS model
specifies how packets are ECN marked/dropped for a particular
instance of a queue on a particular interface. for example,
whether RED, or WRED is applied to manage the queue's occupancy.
nodetype: list (rw)
list keys: [name]
description:
Reference to the unique name used to reference the queue
management profile
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters relating to the queue
management profile.
nodetype: container (rw)
description:
Unique string name used for the queue management profile.
nodetype: leaf (rw)
type: string
description:
Operational state parameters relating to the queue
management profile.
nodetype: container (ro)
description:
Unique string name used for the queue management profile.
nodetype: leaf (ro)
type: string
description:
Configuration and operational state parameters relating to
Weighted Random Early Detection (WRED).
nodetype: container (rw)
description:
Uniform WRED parameters. These parameters are applied to all the
traffic coming into system.
nodetype: container (rw)
description:
Configuration parameters relating to the WRED.
nodetype: container (rw)
description:
The mininum threshold parameter for a RED-managed queue in bytes.
When the average queue length is less than minth, all packets are admitted
to the queue. Mututally exclusive with min-threshold-percent and
max-threshold-percent.
nodetype: leaf (rw)
type: uint64
units: bytes
description:
The maximum threshold parameter for a RED-managed queue in bytes.
When the average queue length exceeds the maxth value, all packets are
dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold-percent and max-threshold-percent.
nodetype: leaf (rw)
type: uint64
units: bytes
description:
The mininum threshold parameter for a RED-managed queue in percent.
When the average queue length is less than minth, all packets are
admitted to the queue. Mutually exclusive with min-threshold and
max-threshold.
nodetype: leaf (rw)
type: uint64
units: oc-types:percentage
description:
The maximum threshold parameter for a RED-managed queue in percent.
When the average queue length exceeds the maxth value, all packets
are dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold and max-threshold.
nodetype: leaf (rw)
type: uint64
units: oc-types:percentage
description:
When this leaf is true and the number of packets in the queue
is between the minimum threshold and the maximum threshold, if
the ECN field on the packet indicates that the endpoints are ECN
capable (that is, the ECT bit is set to 1 and the CE bit is set
to 0, or the ECT bit is set to 0 and the CE bit is set to 1) and
the WRED algorithm determines that the packet should have been
dropped based on the drop probability, the ECT and CE bits for
the packet are changed to 1, and the packet is transmitted.
nodetype: leaf (rw)
type: boolean
default: false
description:
When this leaf is true and the packet and if the ECN field in
the packet indicates that the endpoints are not ECN capable and
the and the WRED algorithm determines that the packet should
have been dropped based on the drop probability, the packet
is dropped.
nodetype: leaf (rw)
type: boolean
default: false
description:
The average queue size depends on the previous average as well as
the current size of the queue.
average queue size = (previous average queue size)*(1-2^{-n})+
(current queue size)*(2^{-n})
where n is the user-configurable exponential weight factor.
The previous average is more important for high values of n. Peaks
and lows in queue size are smoothed by a high value. For low values
of n, the average queue size is close to the current queue size.
When this leaf is not present, implementation default value is
applied.
nodetype: leaf (rw)
type: uint32
description:
If the queue depth is between min and max threshold then this
the probability with which packets are dropped or marked.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Operational state parameters relating to the WRED.
nodetype: container (ro)
description:
The mininum threshold parameter for a RED-managed queue in bytes.
When the average queue length is less than minth, all packets are admitted
to the queue. Mututally exclusive with min-threshold-percent and
max-threshold-percent.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
The maximum threshold parameter for a RED-managed queue in bytes.
When the average queue length exceeds the maxth value, all packets are
dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold-percent and max-threshold-percent.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
The mininum threshold parameter for a RED-managed queue in percent.
When the average queue length is less than minth, all packets are
admitted to the queue. Mutually exclusive with min-threshold and
max-threshold.
nodetype: leaf (ro)
type: uint64
units: oc-types:percentage
description:
The maximum threshold parameter for a RED-managed queue in percent.
When the average queue length exceeds the maxth value, all packets
are dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold and max-threshold.
nodetype: leaf (ro)
type: uint64
units: oc-types:percentage
description:
When this leaf is true and the number of packets in the queue
is between the minimum threshold and the maximum threshold, if
the ECN field on the packet indicates that the endpoints are ECN
capable (that is, the ECT bit is set to 1 and the CE bit is set
to 0, or the ECT bit is set to 0 and the CE bit is set to 1) and
the WRED algorithm determines that the packet should have been
dropped based on the drop probability, the ECT and CE bits for
the packet are changed to 1, and the packet is transmitted.
nodetype: leaf (ro)
type: boolean
default: false
description:
When this leaf is true and the packet and if the ECN field in
the packet indicates that the endpoints are not ECN capable and
the and the WRED algorithm determines that the packet should
have been dropped based on the drop probability, the packet
is dropped.
nodetype: leaf (ro)
type: boolean
default: false
description:
The average queue size depends on the previous average as well as
the current size of the queue.
average queue size = (previous average queue size)*(1-2^{-n})+
(current queue size)*(2^{-n})
where n is the user-configurable exponential weight factor.
The previous average is more important for high values of n. Peaks
and lows in queue size are smoothed by a high value. For low values
of n, the average queue size is close to the current queue size.
When this leaf is not present, implementation default value is
applied.
nodetype: leaf (ro)
type: uint32
description:
If the queue depth is between min and max threshold then this
the probability with which packets are dropped or marked.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Configuration and operational state parameters
relating to Random Early Detection (RED).
nodetype: container (rw)
description:
Uniform RED parameters. These parameters are applied to all
the traffic coming into system.
nodetype: container (rw)
description:
Configuration parameters relating to the RED.
nodetype: container (rw)
description:
The mininum threshold parameter for a RED-managed queue in bytes.
When the average queue length is less than minth, all packets are admitted
to the queue. Mututally exclusive with min-threshold-percent and
max-threshold-percent.
nodetype: leaf (rw)
type: uint64
units: bytes
description:
The maximum threshold parameter for a RED-managed queue in bytes.
When the average queue length exceeds the maxth value, all packets are
dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold-percent and max-threshold-percent.
nodetype: leaf (rw)
type: uint64
units: bytes
description:
The mininum threshold parameter for a RED-managed queue in percent.
When the average queue length is less than minth, all packets are
admitted to the queue. Mutually exclusive with min-threshold and
max-threshold.
nodetype: leaf (rw)
type: uint64
units: oc-types:percentage
description:
The maximum threshold parameter for a RED-managed queue in percent.
When the average queue length exceeds the maxth value, all packets
are dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold and max-threshold.
nodetype: leaf (rw)
type: uint64
units: oc-types:percentage
description:
When this leaf is true and the number of packets in the queue
is between the minimum threshold and the maximum threshold, if
the ECN field on the packet indicates that the endpoints are ECN
capable (that is, the ECT bit is set to 1 and the CE bit is set
to 0, or the ECT bit is set to 0 and the CE bit is set to 1) and
the WRED algorithm determines that the packet should have been
dropped based on the drop probability, the ECT and CE bits for
the packet are changed to 1, and the packet is transmitted.
nodetype: leaf (rw)
type: boolean
default: false
description:
When this leaf is true and the packet and if the ECN field in
the packet indicates that the endpoints are not ECN capable and
the and the WRED algorithm determines that the packet should
have been dropped based on the drop probability, the packet
is dropped.
nodetype: leaf (rw)
type: boolean
default: false
description:
Operational state parameters relating to the RED.
nodetype: container (ro)
description:
The mininum threshold parameter for a RED-managed queue in bytes.
When the average queue length is less than minth, all packets are admitted
to the queue. Mututally exclusive with min-threshold-percent and
max-threshold-percent.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
The maximum threshold parameter for a RED-managed queue in bytes.
When the average queue length exceeds the maxth value, all packets are
dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold-percent and max-threshold-percent.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
The mininum threshold parameter for a RED-managed queue in percent.
When the average queue length is less than minth, all packets are
admitted to the queue. Mutually exclusive with min-threshold and
max-threshold.
nodetype: leaf (ro)
type: uint64
units: oc-types:percentage
description:
The maximum threshold parameter for a RED-managed queue in percent.
When the average queue length exceeds the maxth value, all packets
are dropped (or marked if ECN is enabled). Mutually exclusive with
min-threshold and max-threshold.
nodetype: leaf (ro)
type: uint64
units: oc-types:percentage
description:
When this leaf is true and the number of packets in the queue
is between the minimum threshold and the maximum threshold, if
the ECN field on the packet indicates that the endpoints are ECN
capable (that is, the ECT bit is set to 1 and the CE bit is set
to 0, or the ECT bit is set to 0 and the CE bit is set to 1) and
the WRED algorithm determines that the packet should have been
dropped based on the drop probability, the ECT and CE bits for
the packet are changed to 1, and the packet is transmitted.
nodetype: leaf (ro)
type: boolean
default: false
description:
When this leaf is true and the packet and if the ECN field in
the packet indicates that the endpoints are not ECN capable and
the and the WRED algorithm determines that the packet should
have been dropped based on the drop probability, the packet
is dropped.
nodetype: leaf (ro)
type: boolean
default: false