This section provides the following examples:
Two logical interface units, 0 and 1, are shaped to rates 2 Mbps and 3 Mbps, respectively. The delay-buffer rates are 750 Kbps and 500 Kbps, respectively. The actual delay buffers allocated to each logical interface are 1 second of 750 Kbps and 2 seconds of 500 Kbps, respectively. The 1-second and 2-second values are based on the following calculations:
- delay-buffer-rate < [16 x 64 Kbps]): 1 second of delay-buffer-rate
- delay-buffer-rate < [8 x 64 Kbps]): 2 seconds of delay-buffer-rate
For more information about these calculations, see Maximum Delay Buffer for NxDS0 Interfaces.
Oversubscribing a Channelized Interface
- chassis {
-
- fpc 3 {
-
- pic 0 {
-
q-pic-large-buffer;
- }
- }
- }
- interfaces {
-
- t1-3/0/0 {
- per-unit-scheduler;
- }
- }
- class-of-service {
-
- traffic-control-profiles {
-
- tc-profile1 {
- shaping-rate 2m;
- delay-buffer-rate 750k; # 750 Kbps is less
than 16 x 64 Kbps
- scheduler-map sched-map1;
- }
-
- tc-profile2 {
- shaping-rate 3m;
- delay-buffer-rate 500k; # 500 Kbps is less
than 8 x 64 Kbps
- scheduler-map sched-map2;
- }
- }
-
- interfaces {
-
- t1-3/0/0 {
-
- unit 0 {
- output-traffic-control-profile tc-profile1;
- }
-
- unit 1 {
- output-traffic-control-profile tc-profile2;
- }
- }
- }
- }
Apply a traffic-control profile to a logical interface representing a DLCI on an FRF.16 bundle:
Oversubscribing an LSQ Interface
- interfaces {
-
- lsq-1/3/0:0 {
- per-unit-scheduler;
-
- unit 0 {
- dlci 100;
- }
-
- unit 1 {
- dlci 200;
- }
- }
- }
-
- class-of-service {
-
- traffic-control-profiles {
-
- tc_0 {
- shaping-rate percent 100;
- guaranteed-rate percent 60;
- delay-buffer-rate percent 80;
- }
-
- tc_1 {
- shaping-rate percent 80;
- guaranteed-rate percent 40;
- }
- }
-
- interfaces {
-
- lsq-1/3/0 {
-
- unit 0 {
- output-traffic-control-profile tc_0;
- }
-
- unit 1 {
- output-traffic-control-profile tc_1;
- }
- }
- }
- }