TechNetBuddy

What the exam expects

“Routing and traffic control” covers route-policies and filters, route import, policy-based routing, and the QoS model: classification, marking (DSCP, 802.1p), policing and shaping, and queue scheduling.

Route import with a policy

import-route rip 1 route-policy RIP2OSPF imports only what the policy permits; apply cost sets the external metric. Combine with an ip ip-prefix list. Importing both ways on more than one router can loop routes: tag and filter them.

Policy-based routing

On an AR router: policy-based-route NAME permit node 10, if-match acl 3001, apply ip-address next-hop …, then ip policy-based-route NAME on the interface where the traffic enters. Packets that do not match follow the routing table. On S-series switches the same is a traffic behavior with redirect ip-nexthop.

QoS with MQC

DiffServ marks packets once at the edge and lets every hop treat them by class: EF for voice, AF classes for business data, BE for the rest. MQC builds the rule from three parts: a traffic classifier (if-match acl, dscp, any), a traffic behavior (deny, remark dscp, car cir, statistic, redirect) and a traffic policy pairing them, applied with traffic-policy NAME inbound|outbound. Policing (CAR) drops traffic above a rate; shaping queues it; schedulers such as PQ and WFQ decide which queue sends next.

Commands at a glance

[R1] traffic classifier VOICE
[R1-classifier-VOICE] if-match acl 3020
[R1] traffic behavior EF
[R1-behavior-EF] remark dscp ef
[R1-behavior-EF] car cir 512
[R1] traffic policy EDGE
[R1-trafficpolicy-EDGE] classifier VOICE behavior EF
[R1-GigabitEthernet0/0/0] traffic-policy EDGE inbound

Not modelled in the simulator: Queue scheduling, shaping and WRED are described, not simulated; CAR never drops a ping in this model. filter-policy and route tags are not modelled.