Configure rate enforcement on your Frame Relay network that will
use a custom queue list to prioritize traffic before it gets
throttled based on protocol and port.
Scenario:
Your main office in Atlanta has a high-speed T1 Frame Relay connection. There is a bottleneck that exists at the other ends of
the PVCs that connect to Orlando and Houston. This is due to the
fact that Orlando and Houston only have 56K Frame Relay connections.
Install rate enforcement using custom queuing that will
prioritize traffic based on the following rules:
For all traffic destined for either Orlando or Houston:
Give IP a high priority
Give IPX a normal priority
Give CDP a low priority.
This should cause IPX and CDP to get throttled before IP gets
throttled.
For traffic destined to Orlando:
Give first priority to HTTP traffic
Give second priority to FTP traffic
Give last priority to all other traffic.
Notes:
Lab Tasks:
Cable the lab as shown in the diagram. Use the Adtran Atlas 550
to simulate the Frame Relay network.
Configure the serial interfaces that connect to the Frame Relay network for
Frame Relay encapsulation and set the LMI type to
ANSI. Use sub-interfaces on the router in Atlanta - This will
allow us to add rate enforcement profiles to each connection
independently. Use the DLCI number of each PVC as your
sub-interface number. Check your routing tables and verify
connectivity.
Create Frame Relay map class that will be used for both sites.
Limit the bandwidth to an average bandwidth of 28,000 bits per
second and peak a bandwidth to 56,000 bits per second. Call the
class "whole_interface". Point this map-class at
priority-group 2:
Create priority-group 2 which will prioritize traffic based on
our requirements:
On the Atlanta router:
Atlanta(config)#priority-list 2 protocol ip high
Atlanta(config)#priority-list 2 protocol ipx normal
Atlanta(config)#priority-list 2 protocol cdp low
Create Frame Relay map class that will be used for Orlando only.
Limit the bandwidth to an average bandwidth of 28,000 bits per
second and a peak bandwidth to 56,000 bits per second. Call the
class "sub_only". Point this map-class at
custom-queue-list 1:
Create extended access lists that will be used by the
custom-queue-list to specify both HTTP and FTP traffic. Because
these need to be prioritized differently, WWW before FTP, you must
create two lists.
On the Atlanta router:
Atlanta(config)#access-list 100 permit tcp any any eq www
Atlanta(config)#access-list 101 permit tcp any any eq ftp
Create custom-queue-list 1 which will prioritize traffic based
on our requirements.
On the Atlanta router:
Atlanta(config)#queue-list 1 protocol ip 1 list 100
Atlanta(config)#queue-list 1 protocol ip 2 list 101
Atlanta(config)#queue-list 1 default 3
Enable traffic shaping on the main serial interface. Note: the
frame-relay traffic-shaping command must be issued on the
interface itself, not the sub-interface.
Because we want the protocol priorities (map-class
whole_interface) to throttle all traffic to both sites, apply the
whole_interface map-class to the interface itself:
On the Atlanta router:
Atlanta(config)#int s0/0
Atlanta(config-if)#frame-relay class whole_interface
Because we want the application priorities (map-class sub_only)
to throttle traffic for only Orlando, apply the sub_only map-list to
the Orlando sub-interface:
On the Atlanta router:
Atlanta(config)#int s0/0.17
Atlanta(config-subif)#frame-relay class sub_only
What command/commands can be used to verify traffic shaping
using custom-queuing is turned on?