Information Technology Reference
In-Depth Information
Example 4-33
FIB Entry for 172.16.0.0
R3#show ip cef 172.16.0.0
172.16.0.0/16, version 23, cached adjacency 192.168.12.2
0 packets, 0 bytes, qos-group 2
via 192.168.23.2, 0 dependencies, recursive
next hop 192.168.23.2, GigabitEthernet6/0 via 192.168.23.2/32
valid cached adjacency
qos-group 2
To enable FIB lookup for the traffic destined for 172.16.0.0/16, policy lookup is enabled on
the interface of FastEthernet 10/0. The keyword
destination
is used in the command. If
there is a match for the destination address, a check is made into the FIB to determine if
there are any matching QoS entries. In this example, ip-qos-map is configured for the
interface, and QoS-group ID is set to 2 in FIB, which means that the QoS-group ID can be
used to set QoS policies. An input CAR is configured for traffic matching a QoS-group ID
of 2. A sample configuration is shown in Example 4-34.
Example 4-34
Sample Interface Configuration for QPPB
interface FastEthernet10/0
ip address 192.168.34.3 255.255.255.0
no ip directed-broadcast
bgp-policy destination ip-qos-map
rate-limit input qos-group 2 5000000 4000 8000 conform-action transmit
exceed-action drop
Example 4-35 shows the IP interface status. Example 4-36 shows traffic policing using
CAR. A similar configuration can be made for the traffic sourced from 172.16.0.0 to AS
300 (not shown). The incoming interface then is GigabitEthernet 6/0. An outbound CAR
should be configured on the interface of FastEthernet 10/0 to enforce the QoS policy.
Example 4-35
IP Interface Status of FastEthernet 10/0
R3#show ip interface FastEthernet 10/0 | include BGP
BGP Policy Mapping is enabled (output ip-qos-map)
Example 4-36
Interface CAR Status
R3#show interface FastEthernet 10/0 rate-limit
FastEthernet10/0
Input
matches: qos-group 2
params: 5000000 bps, 4000 limit, 8000 extended limit
conformed 112 packets, 168448 bytes; action: transmit
