Alcatel-Lucent 7710 SR OS, Interface Configuration Manual

Page: 188 / 436

Configuration Commands
Page 188 7710 SR OS Interface Configuration Guide
max-rate
Syntax max-rate rate
no max-rate
Context config>port>ethernet>egress-scheduler-override
config>port>sonet-sdh>path>egress-scheduler-override
config>port>tdm>ds3>egress-scheduler-override
config>port>tdm>ds1>channel-group>egress-scheduler-override
config>port>tdm>e3>egress-scheduler-override
config>port>tdm>e1>channel-group>egress-scheduler-override
Description This command overrides the max-rate parameter found in the port-scheduler-policy associated with
the port. When a max-rate is defined at the port or channel level, the port scheduler policies max-rate
parameter is ignored.
The egress-scheduler-override max-rate command supports a parameter that allows the override
command to restore the default of not having a rate limit on the port scheduler. This is helpful when
the port scheduler policy has an explicit maximum rate defined and it is desirable to remove this limit
at the port instance.
The no form of this command removes the maximum rate override from the egress port or channels
port scheduler context. Once removed, the max-rate parameter from the port scheduler policy
associated with the port or channel will be used by the local scheduler context.
Parameters rate — Specifies the explicit maximum frame based bandwidth limit. This value overrides the QoS
scheduler policy rate.
Values 1 — 40000000, max
egress-scheduler-policy
Syntax egress-scheduler-policy port-scheduler-policy-name
no egress-scheduler-policy
Context config>port>ethernet
config>port>tdm>ds3
config>port>tdm>ds1>channel-group
config>port>tdm>e3
config>port>tdm>ds3>channel-group
Description This command enables the provisioning of an existing port-scheduler-policy to a port or channel.
The egress-scheduler-override node allows for the definition of the scheduler overrides for a specific
port or channel.
When a port scheduler is active on a port or channel, all queues and intermediate service schedulers
on the port are subject to receiving bandwidth from the scheduler. Any queues or schedulers with
port-parent associations are mapped to the appropriate port priority levels based on the port-parent
command parameters. Any queues or schedulers that do not have a port-parent or valid intermediate
scheduler parent defined are treated as orphaned and are handled based on the port scheduler policies
default or explicit orphan behavior.