19.07.2013 Views

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3 WAN Aggregator <strong>QoS</strong> <strong>Design</strong><br />

Version 3.3<br />

Figure 3-11 Medium-Speed Frame Relay Links<br />

WAN Aggregator<br />

WAN Edge Link-Specific <strong>QoS</strong> <strong>Design</strong><br />

Note In some cases, however, administrators have chosen to enable FRF.12 on T1/E1 speed links, even though<br />

the fragment size for a 10-ms maximum serialization delay at such speeds is greater than the MTU of<br />

Ethernet (1500 bytes). The rationale behind doing so is to retain the Frame Relay dual-FIFO queuing<br />

mechanism at Layer 2, which can provide slightly superior service levels under certain conditions.<br />

Generally, this is not required however.<br />

Example 3-19 Medium-Speed (T1/E1) Frame Relay <strong>QoS</strong> <strong>Design</strong> Example<br />

!<br />

policy-map MQC-FRTS-1536<br />

class class-default<br />

shape average 1460000 14600 0 ! Enables MQC-Based FRTS<br />

service-policy WAN-EDGE ! Queues packets headed to the shaper<br />

!<br />

…<br />

!<br />

interface Serial2/0<br />

no ip address<br />

encapsulation frame-relay<br />

!<br />

interface Serial2/0.12 point-to-point<br />

ip address 10.1.121.1 255.255.255.252<br />

description 1536kbps FR Circuit to RBR-3745-Left<br />

frame-relay interface-dlci 102<br />

class FR-MAP-CLASS-1536 ! Binds the map-class to the FR DLCI<br />

!<br />

…<br />

!<br />

map-class frame-relay FR-MAP-CLASS-1536<br />

service-policy output MQC-FRTS-1536 ! Attaches nested MQC policies to map-class<br />

!<br />

Verification commands:<br />

show policy map<br />

show policy-map interface<br />

Frame Relay Link<br />

T1/E1<br />

Frame Relay<br />

Cloud<br />

High-Speed (Multiple T1/E1 and Greater) Frame Relay Links<br />

Branch Router<br />

Recommendation: Use IP CEF per-packet load balancing for load sharing across multiple physical<br />

Frame Relay links.<br />

When multiple Frame Relay circuits exist between a central WAN aggregation router and a remote<br />

branch router, as illustrated in Figure 3-12, it is recommended that IP CEF per-packet load balancing be<br />

used to load-share between the links. Multilink PPP over Frame Relay (MLPoFR) bundles are complex<br />

<strong>Enterprise</strong> <strong>QoS</strong> <strong>Solution</strong> <strong>Reference</strong> <strong>Network</strong> <strong>Design</strong> <strong>Guide</strong><br />

3-29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!