Section 7: QoS (6 Points)

• Configure a Traffic Class and apply it on incoming direction R6-e0/0, which will classify all BGP traffic and set IP precedence to immediate.

If you configured this correctly as shown in Example 5-40, you have scored 2 points.

Example 5-40 shows a configuration of Traffic Classification based on the concept of Modular QoS CLI configuration. You are going to create a Traffic Class and ACL to match the traffic you want to classify and then create a policy map to apply the class map and set the BGP traffic to precedence "immediate," to enable CEF and to apply to R6-E0/0. Also, the show commands verify if the Traffic Class is working properly.

Example 5-40. R6 Policy Classification Configuration and Verification

 R6#sh run Building configuration... Current configuration : 2609 bytes ! ip cef ! class-map match-all class1   match access-group 103 ! ! policy-map BGP_Policy   class class1    set ip precedence 2 ! interface Ethernet0/0  ip address 160.10.22.6 255.255.255.0  !  service-policy input BGP_Policy ! R6#sh ip access-lists 103 Extended IP access list 103     permit tcp any any eq bgp (33 matches) R6# ! R6#sh policy-map interface e0/0 Ethernet0/0   Service-policy input: BGP_Policy     Class-map: class1 (match-all)       35 packets, 2360 bytes       5 minute offered rate 0 bps, drop rate 0 bps       Match: access-group 103       QoS Set         ip precedence 2           Packets marked 35     Class-map: class-default (match-any)       2 packets, 146 bytes       5 minute offered rate 0 bps, drop rate 0 bps       Match: any R6# ! ! 

• Configure Committed Access Rate on R6-a3/0, so that web traffic will be sent but using IP precedence 5 for the web traffic that conforms to the first rate policy, nonconforming web traffic, and so that will use the IP precedence 0 (best effort). Any remaining traffic is limited to 8 Mbps, with a normal burst size of 16,000 bytes and an Excess Burst size of 24,000 bytes. Traffic that conforms is sent with an IP precedence of 5. Traffic that does not conform should be dropped.

If you configured this correctly as shown in Example 5-41, you have scored 2 points.

Example 5-41 has the configuration for CAR and the ACL necessary for that. The output from the show command verifies if the interface is correctly configured and using the desired criteria.

Example 5-41. R6CAR Configuration and Verification

 R6#sh run int a3/0 Building configuration... Current configuration : 359 bytes ! interface ATM3/0  ip address 170.100.10.1 255.255.255.0  rate-limit output access-group 101 20000000 24000 32000 conform-action set-prec- transmit 5 exceed-action set-prec-transmit 0  rate-limit output 8000000 16000 24000 conform-action set-prec-transmit 5 exceed- action drop ! end R6#sh ip access Extended IP access list 101     permit tcp any any eq www R6# R6#sh interfaces a3/0 rate-limit ATM3/0   Output     matches: access-group 101       params:  20000000 bps, 24000 limit, 32000 extended limit       conformed 0 packets, 0 bytes; action: set-prec-transmit 5       exceeded 0 packets, 0 bytes; action: set-prec-transmit 0       last packet: 11004728ms ago, current burst: 0 bytes       last cleared 03:03:11 ago, conformed 0 bps, exceeded 0 bps     matches: all traffic       params:  8000000 bps, 16000 limit, 24000 extended limit       conformed 290 packets, 18644 bytes; action: set-prec-transmit 5       exceeded 0 packets, 0 bytes; action: drop       last packet: 21060ms ago, current burst: 0 bytes       last cleared 03:03:11 ago, conformed 0 bps, exceeded 0 bps R6# 

• Configure policy-based routing on R1 such that all packets with a source of 160.10.11.10 prefer a next-hop 160.10.5.5 address.

If you configured this correctly as shown in Example 5-42, you have scored 2 points.

Example 5-42 shows the policy-based routing configuration that will set R5 as the next-hop for packets that the source is the address 160.10.11.10 or the Sw1.

Example 5-42. R1 Policy-Based Routing Configuration

 R1#sh run Building configuration... Current configuration : 126 bytes ! interface Ethernet0/0  ip address 160.10.11.1 255.255.255.0  ip policy route-map FROM_SW1 R1# ! access-list 1 permit 160.10.11.10 route-map FROM_SW1 permit 10  match ip address 1  set ip next-hop 160.10.5.5 end