s and 512 Kbps). In a nutshell, we create a policy map for each speed we'll encounter, and then tell the default class (class-default) on each subinterface what speed to shape to using the shape peak bps command: policy-map Frame-128 description [ - [ For 128k CIR - 256k burst ]--] class class-default shape peak 128000 policy-map Frame- 256 description [ -- [ For 256k CIR - 512k burst ]--] class class-default shape peak 256000 policy-map Frame-384 description [--] [ For 384k CIR - 768k burst ]--] class class-default shape peak 384000 policy-map Frame- - 512 description [--[ For 512k CIR - 1024k burst ]--] class class-default shape peak 512000 As stated previously, for this to work, you must have a subinterface for each branch's PVC. This adds a lot to the router's configuration, but as the saying goes, that's life. Traffic-Shaping Scenarios In the Ethernet handoff example, I used shape average, and here I'm using shape peak. The reason for the difference is that I'm configuring for Frame Relay now, which allows for bursting speeds. Where bursting is possible, use the peak option. Otherwise, use average. To apply this, use the service-policy command on the subinterfaces. Here's a sample of Branch 100's subinterface: interface Serial0/0.100 point-to-point description [< Branch 100 > ] bandwidth 256 ip address 10.10.20.1 255.255.255.252 frame-relay interface-dlci 100 service-policy output Frame-128 Observant readers will have noticed that I specified the bandwidth to be 256 Kbps, but applied the 128 Kbps policy map to the interface. This is due to the nature of Frame Relay bursting. For the graphs and stats to look right, the bandwidth needs to be the burst size. Traffic shaping is configured based on the CIR, though, and the CIR of this link is 128 Kbps. You can view the traffic-shaping status with the show policy-map interface interface- name command: Main-Office-Router#sho policy-map interface so/0.100 Serial0/0.100 Service-policy output: Frame-128 Class-map: class-default (match-any) 1147178 packets, 583516684 b