
Frame Relay Overview
117376-C Rev. 00
2-27
All traffic that goes to a traffic-shaped VC (VC1 or VC2) is queued as high,
normal, or low priority at the VC level, and then it travels, by priority order, to a
shaping queue within the driver. Normal VC traffic is queued as high, normal, or
low priority at the driver level. At the driver level:
• Interrupt priority traffic, DLCMI/LMI requests (the LMI box in Figure 2-10
),
has the highest priority. You cannot change this.
• Shaped priority traffic (the Shaping box in Figure 2-10
) has the second
highest priority.
• Normal VC traffic (not shaped) has lower priority than shaped traffic. You can
still prioritize normal VC traffic as high, normal, or low.
Queuing and prioritization only matter when the traffic rate exceeds the VC line
rate or the CIR. If the total of all traffic is below the CIR, the router just transmits
it.
You cannot prioritize between VCs on which you have enabled traffic shaping.
The router schedules traffic among them in a round-robin manner.
For information about configuring filters for protocol prioritization, see
Configuring Traffic Filters and Protocol Prioritization.
Traffic Shaping for SVCs
Traffic shaping for SVCs works according to the descriptions in the previous
topics, except that SVCs derive the committed burst, excess burst, and throughput
values from a combination of the traffic shaping attributes and parameters that you
configure, and values that the frame relay network imposes. The network values
are called link layer core (LL Core) values,
Requesting Quality of Service for SVCs
When you configure traffic shaping for an SVC, you have several alternatives to
achieve the QoS that will best serve your network:
• You can set the SVC Traffic Shaping Disable attribute or parameter to Enable
without providing values for the traffic shaping attribute or parameters. The
SVCs you configure in this way use LL Core values that the network
provides.
Comentarios a estos manuales