ytes 5 minute offered rate 23000 bps, drop rate 0 bps Match: any Traffic Shaping Target/Average Sustain Excess Interval Increment Limit bits/int bits/int (bytes) 256000/128000 Adapt Queue Packets Bytes Packets Bytes Shaping Active Depth Delayed Delayed Active 1146896 583184180 411456 434751961 no Again, don't worry if it says Shaping Active = no. It's only showing whether shaping is active during the millisecond you press Return. It changes off/on constantly. The important facts are that packets have been delayed and the drop rate is 0 bps. You can also see from this output that even though we only configured the CIR of 128 Kbps, it has assumed a burst of 2x, as shown by the Target/Average Rate. Chapter 32: Designing QoS CHAPTER 33 The Congested Network A congested network is one where there's too much data and not enough bandwidth to support it. QoS can help with a congested network, but it cannot cure the root problem. The only ways to cure congestion on a network are to add more bandwidth or reduce the amount of data trying to flow over it. That being said, let's look at a congested network and see how we might ease the pain using QoS. Determining Whether the Network Is Congested How do you know if your network is congested? Let's look at our favorite two-building company again (Figure 33-1). Building A Building B Figure 33-1. Typical two-building network Users at each building have been complaining that access to the other building is slow. So, let's take a look at the interfaces on one of the routers that connects the T1 between buildings. Here's the output from the show interface command for the serial interface on Building B's router: Bldg-B-Rtr#sho int so/o Serialo/o is up, line protocol is up Hardware is PowerQUICC Serial Description: <[ T1 WAN Link ]> Internet address is 10.10.10.2/30 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 42/255, rxload 249/255 Encapsulation PPP, loopback not set Keepalive set (10 sec) LCP Open Open: IPCP, CDPCP Last input 00:00:00, output 00:00:00, o