| bac-ref |
bac-name |
A reference to a BAC entry. |
| bac-ref |
bac-name |
A reference to a BAC entry. |
| bac-ref |
bac-name |
A reference to a BAC entry. |
| bac-ref |
bac-name |
A reference to a BAC entry. |
| bac-ref |
bac-name |
A reference to a BAC entry. |
| common-random-early-detection-parameters |
min-thresholdmax-thresholdmax-probability |
A set of parameters common to RED and WRED BAC algorithms. |
| common-random-early-detection-parameters |
min-thresholdmax-thresholdmax-probability |
A set of parameters common to RED and WRED BAC algorithms. |
| common-random-early-detection-parameters |
min-thresholdmax-thresholdmax-probability |
A set of parameters common to RED and WRED BAC algorithms. |
| common-random-early-detection-parameters |
min-thresholdmax-thresholdmax-probability |
A set of parameters common to RED and WRED BAC algorithms. |
| common-random-early-detection-parameters |
min-thresholdmax-thresholdmax-probability |
A set of parameters common to RED and WRED BAC algorithms. |
| max-probability |
max-probability |
Definition of maximum probability. |
| max-probability |
max-probability |
Definition of maximum probability. |
| max-probability |
max-probability |
Definition of maximum probability. |
| max-probability |
max-probability |
Definition of maximum probability. |
| max-probability |
max-probability |
Definition of maximum probability. |
| max-threshold |
max-threshold |
Definition of maximum threshold. |
| max-threshold |
max-threshold |
Definition of maximum threshold. |
| max-threshold |
max-threshold |
Definition of maximum threshold. |
| max-threshold |
max-threshold |
Definition of maximum threshold. |
| max-threshold |
max-threshold |
Definition of maximum threshold. |
| min-threshold |
min-threshold |
Definition of minimum threshold. |
| min-threshold |
min-threshold |
Definition of minimum threshold. |
| min-threshold |
min-threshold |
Definition of minimum threshold. |
| min-threshold |
min-threshold |
Definition of minimum threshold. |
| min-threshold |
min-threshold |
Definition of minimum threshold. |
| queue-counters |
total green yellow red |
Queue counters reported by frame type. |
| queue-counters |
total green yellow red |
Queue counters reported by frame type. |
| queue-counters |
total green yellow red |
Queue counters reported by frame type. |
| queue-counters |
total green yellow red |
Queue counters reported by frame type. |
| queue-counters |
total green yellow red |
Queue counters reported by frame type. |
| queue-counters-common |
out-frames out-octets congestion-discard-frames congestion-discard-octets |
Queue counters common to each frame type, e.g., green frames. |
| queue-counters-common |
out-frames out-octets congestion-discard-frames congestion-discard-octets |
Queue counters common to each frame type, e.g. green frames. |
| queue-counters-common |
out-frames out-octets congestion-discard-frames congestion-discard-octets |
Queue counters common to each frame type, e.g. green frames. |
| queue-counters-common |
out-frames out-octets congestion-discard-frames congestion-discard-octets |
Queue counters common to each frame type, e.g. green frames. |
| queue-counters-common |
out-frames out-octets congestion-discard-frames congestion-discard-octets |
Queue counters common to each frame type, e.g. green frames. |
| queues |
queue queue-statistics-enable |
Configuration data for queues. |
| queues |
queue queue-statistics-enable |
Configuration data for queues. |
| queues |
queue queue-statistics-enable |
Configuration data for queues.
This grouping exists for historical, backward compatibility
reasons: it provides per queue the original 'one byte' priority
and 'one byte' weight, and adds a second 'two bytes' weight. |
| queues |
queue queue-statistics-enable |
Configuration data for queues.
This grouping exists for historical, backward compatibility
reasons: it provides per queue the original 'one byte' priority
and 'one byte' weight, and adds a second 'two bytes' weight. |
| queues |
queue queue-statistics-enable |
Configuration data for queues.
This grouping exists for historical, backward compatibility
reasons: it provides per queue the original 'one byte' priority
and 'one byte' weight, and adds a second 'two bytes' weight. |
| queues-base |
queue queue-statistics-enable |
Configuration data for queues. |
| queues-base |
queue queue-statistics-enable |
Configuration data for queues. |
| queues-base |
queue queue-statistics-enable |
Configuration data for queues. |
| queues-extended-scheduling |
queue queue-statistics-enable |
Configuration data for queues.
This grouping exists for an up-to-date scheduling definition:
it provides per queue a 'two bytes' priority and a 'two bytes'
weight. |
| queues-extended-scheduling |
queue queue-statistics-enable |
Configuration data for queues.
This grouping exists for an up-to-date scheduling definition:
it provides per queue a 'two bytes' priority and a 'two bytes'
weight. |
| queues-extended-scheduling |
queue queue-statistics-enable |
Configuration data for queues.
This grouping exists for an up-to-date scheduling definition:
it provides per queue a 'two bytes' priority and a 'two bytes'
weight. |
| queue-statistics |
enqueued-frames enqueued-octets total green yellow red |
Statistics associated with queues. |
| queue-statistics |
enqueued-frames enqueued-octets total green yellow red |
Statistics associated with queues. |
| queue-statistics |
enqueued-frames enqueued-octets total green yellow red |
Statistics associated with queues. |
| queue-statistics |
enqueued-frames enqueued-octets total green yellow red |
Statistics associated with queues. |
| queue-statistics |
enqueued-frames enqueued-octets total green yellow red |
Statistics associated with queues. |
| reset-queue-counters |
reset-counters |
Statistics associated with queues. |
| reset-queue-counters |
reset-counters |
Statistics associated with queues. |
| reset-queue-counters |
reset-counters |
Statistics associated with queues. |
| reset-queue-counters |
reset-counters |
Statistics associated with queues. |
| reset-queue-counters |
reset-counters |
Statistics associated with queues. |
| scheduling-attributes |
priority extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-attributes |
priority extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-attributes |
priority extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-attributes |
priority extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-attributes |
priority extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-gen-attr |
priority weight extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-gen-attr |
priority weight extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-gen-attr |
priority weight extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-gen-attr |
priority weight extended-weight |
Configuration data for scheduling traffic from queues. |
| scheduling-gen-attr |
priority weight extended-weight |
Configuration data for scheduling traffic from queues. |
| tc-id-2-queue-id-mapping-profile-ref |
tc-id-2-queue-id-mapping-profile-name |
A reference to a traffic class ID to queue ID mapping
profile. |
| tc-id-2-queue-id-mapping-profile-ref |
tc-id-2-queue-id-mapping-profile-name |
A reference to a traffic class ID to queue ID mapping
profile. |
| tc-id-2-queue-id-mapping-profile-ref |
tc-id-2-queue-id-mapping-profile-name |
A reference to a traffic-class-id to queue-id mapping
profile. |
| tc-id-2-queue-id-mapping-profile-ref |
tc-id-2-queue-id-mapping-profile-name |
A reference to a traffic class ID to queue ID mapping
profile. |
| tc-id-2-queue-id-mapping-profile-ref |
tc-id-2-queue-id-mapping-profile-name |
A reference to a traffic-class-id to queue-id mapping
profile. |
| tm-root |
tm-root |
The root for traffic management data.
Traffic management involves the following aspects:
- the forwarding decision determined to egress a frame through
an outgoing traffic container (which can be an interface).
- the traffic container (which can be a bottleneck) is
associated to a scheduler resolving the contention of
different queues competing to access the traffic container.
- so after the outgoing traffic container is determined, the
system needs to determine in which queue of the traffic
container the frame must be directed. This takes place based
on the frame's traffic-class by means of the traffic-class-id
to queue-id mapping concept.
- at any time, the scheduler resolves which queue should
deliver the next frame to the egress traffic container by
looking at the scheduling-priority and scheduling-weight of
each of queues.
The tm-root represents the scheduling stage directly attached
to the bottleneck resource (typically an interface). |
| tm-root |
tm-root |
The root for traffic management data.
Traffic management involves the following aspects:
- the forwarding decision determined to egress a frame through
an outgoing traffic container (which can be an interface).
- the traffic container (which can be a bottleneck) is
associated to a scheduler resolving the contention of
different queues competing to access the traffic container.
- so after the outgoing traffic container is determined, the
system needs to determine in which queue of the traffic
container the frame must be directed. This takes place based
on the frame's traffic class by means of the traffic class ID
to queue ID mapping concept.
- at any time, the scheduler resolves which queue should
deliver the next frame to the egress traffic container by
looking at the scheduling-priority and scheduling-weight of
each of queues.
The tm-root represents the scheduling stage directly attached
to the bottleneck resource (typically an interface). |
| tm-root |
tm-root |
The root for traffic management data.
Traffic management involves the following aspects:
- the forwarding decision determined to egress a frame through
an outgoing traffic container (which can be an interface).
- the traffic container (which can be a bottleneck) is
associated to a scheduler resolving the contention of
different queues competing to access the traffic container.
- so after the outgoing traffic container is determined, the
system needs to determine in which queue of the traffic
container the frame must be directed. This takes place based
on the frame's traffic class by means of the traffic class ID
to queue ID mapping concept.
- at any time, the scheduler resolves which queue should
deliver the next frame to the egress traffic container by
looking at the scheduling-priority and scheduling-weight of
each of queues.
The tm-root represents the scheduling stage directly attached
to the bottleneck resource (typically an interface). |
| tm-root |
tm-root |
The root for traffic management data.
Traffic management involves the following aspects:
- the forwarding decision determined to egress a frame through
an outgoing traffic container (which can be an interface).
- the traffic container (which can be a bottleneck) is
associated to a scheduler resolving the contention of
different queues competing to access the traffic container.
- so after the outgoing traffic container is determined, the
system needs to determine in which queue of the traffic
container the frame must be directed. This takes place based
on the frame's traffic class by means of the traffic class ID
to queue ID mapping concept.
- at any time, the scheduler resolves which queue should
deliver the next frame to the egress traffic container by
looking at the scheduling-priority and scheduling-weight of
each of queues.
The tm-root represents the scheduling stage directly attached
to the bottleneck resource (typically an interface). |
| tm-root |
tm-root |
The root for traffic management data.
Traffic management involves the following aspects:
- the forwarding decision determined to egress a frame through
an outgoing traffic container (which can be an interface).
- the traffic container (which can be a bottleneck) is
associated to a scheduler resolving the contention of
different queues competing to access the traffic container.
- so after the outgoing traffic container is determined, the
system needs to determine in which queue of the traffic
container the frame must be directed. This takes place based
on the frame's traffic-class by means of the traffic-class-id
to queue-id mapping concept.
- at any time, the scheduler resolves which queue should
deliver the next frame to the egress traffic container by
looking at the scheduling-priority and scheduling-weight of
each of queues.
The tm-root represents the scheduling stage directly attached
to the bottleneck resource (typically an interface). |