o Save: save configuration at the Running Config;
o Reset: undo changes made locally at the Running Config.
11.3 Queue Policing
Queue Policing menu allows configuring traffic limits at each queue in a port.
If one configuration is desired to be applied at all ports, then the row “*” should be
used, that is, configuration done in the “*” row will be replied to all ports. Possible
configurations are as follows.
o Port: shows the ports to be configured at this row;
o Queue enable: enable Queue Policing function at the port.
Checkbox selected means function enabled, and checkbox empty
means disabled. Reason Switches have a table with number of
rows equal to the number of ports and number of columns equal
to the number of QoS queues. Thus, each queue in each port can
be independently configured to do traffic queue policing. If a given
port at a given queue is enabled, Queue column displays possible
configuration to that queue. Possible configuration is as follows:
Rate: indicates the maximum allowed traffic on that port.
Traffic rates at the port higher than this field are not
allowed if function is enabled, then traffic close to the limit
will start packet losing based on the QoS configured.
Allowed values are integer values and limits depend on
the Unit used. Range of 100 to 1,000,000 is allowed when
kbps or fps units are used. Range of 1 to 32,000 is allowed
when Mbps or kfps units are used;
Unit: indicates which unit should be used with Rate value
to limit traffic. Allowed values are kbps, Mbps, fps and
kfps.
After one of the configurations described before is changed, there are buttons that
allows the user to save or discard the configurations.
o Save: save configuration at the Running Config;
o Reset: undo changes made locally at the Running Config.
11.4 Port Scheduler
Port Scheduler menu allows configuring priority type at each port. By default, Reason
Switches operates in strict priority. If necessary, up to 6 queues (except 6 and 7 CoS
queues) can be weighted, thus packet drop process should weight the queues
instead of waiting higher level queues to be empty. Besides, weighting process will
To Next Page
Loading...
Need help?
General
