Mission-critical traffic is not getting a minimum bandwidth of 192 kbps in this policy-map configuration. What should be done to correct the problem?
policy-map test
class mission-critical
bandwidth 192
shape average 128000
queue-limit 64
A.
Change the bandwidth statement to the bandwidth 192000 command.
B.
Replace the bandwidth statement with the priority 192 command.
C.
Set the shape rate to a CIR that is higher than 192 kbps.
D.
Use the shape peak command instead of the shape average command.
E.
Increase the maximum queue size for the mission-critical traffic class using the queue-limit 128 command.
F.
Decrease the maximum queue size for the mission-critical traffic class using the queue-limit 40 command.
Explanation:
Traffic shaping allows rate control of traffic leaving an interface in order to match its flow to the speed of the remote target interface and to ensure that the traffic conforms to policies defined for it. Therefore, traffic adhering to a particular profile can be shaped to meet downstream requirements, eliminating bottlenecks in topologies with data-rate mismatches. GTS can be configured to shape traffic for all traffic exiting an interface using the traffic-shape command:
Router(config-if)# traffic-shape rate bit-rate [ burst-size [ excess-burst-size ]]
Alternatively, traffic defined by an ACL can be shaped independently of other traffic exiting an interface using the command:
Router(config-if)# traffic-shape group access-list-number bit-rate [ burst-size [ excess-burst-size ]]