[Contents] [Prev] [Next] [Index] [Report an Error]

Example: DLCI Class of Service on a Channelized IQ Interface Configuration

This example applies class of service at the logical interface level on a clear channel T3 interface derived from a channelized DS3 IQ interface. (For more information on configuring a channelized DS3 IQ interface, see Example: Channelized DS3 IQ Interface Configuration.)

Configure a scheduler map, complete with the desired transmit rates, buffer sizes, and service classes. Once the scheduler map is ready, enable logical interface-level class of service with the per-unit-scheduler statement at the [edit interfaces interface-name] hierarchy level. Also, configure a DLCI for each logical interface with the dlci dlci-number statement at the [edit interfaces interface-name unit unit-number] hierarchy level. Finally, configure the logical interfaces for class of service with the scheduler-map and shaping-rate statements at the [edit class-of-service interfaces interface-name unit unit-number] hierarchy level. These statements specify which scheduler map to associate with each logical interface and how much bandwidth to reserve for the DLCI queues.



[edit]
interfaces {


ct3-3/1/0 {
               
no-partition interface-type
t3; # This converts the channelized DS3 IQ
}




t3-3/1/0 {
               
per-unit-scheduler; # This enables scheduling at the logical interface level.
encapsulation frame-relay;


                 
unit 0 {# The
logical interface where scheduler map sched-0 takes effect.
                 
dlci 100; #
The DLCI affected by scheduler map sched-0.


family inet {
address 10.40.1.1/30;
}


}





unit 1 {# The logical interface
where scheduler map sched-1 takes effect.

dlci 101; # The DLCI affected
by scheduler map sched-1.


family inet {
address 10.40.2.1/30;
}


}


}


}
class-of-service {


interfaces {



t3-3/1/0 { # This specifies
the channel where the scheduled DLCI is located.



unit 0 { # This specifies the
logical interface for the first scheduled DLCI.

scheduler-map sched-0; # This
applies a scheduler map to the first DLCI.

shaping-rate 10m; # This reserves
bandwidth for scheduler map sched-0.
}




unit 1 { # This specifies the logical interface for the
second scheduled DLCI.
scheduler-map sched-1; # Applies a scheduler map to the
second DLCI.
shaping-rate 10m; # This reserves bandwidth for scheduler
map sched-1.
}


}


}





scheduler-maps {




sched-0 { # This is where classes
of service are associated with a scheduler.
forwarding-class assured-forwarding scheduler af;
forwarding-class best-effort scheduler be;
forwarding-class expedited-forwarding scheduler ef;
}





sched-1 { # This is where classes
of service are associated with a scheduler.
forwarding-class assured-forwarding scheduler af-1;
forwarding-class best-effort scheduler be-1;
forwarding-class expedited-forwarding scheduler ef-1;
}


}




schedulers {


af {
transmit-rate percent 10;
buffer-size percent 10;
}




be {
transmit-rate percent 20;
buffer-size percent 20;
}




ef {
transmit-rate percent 70;
buffer-size percent 70;
}




af-1 {
transmit-rate percent 10;
buffer-size percent 10;
}




be-1 {
transmit-rate percent 30;
buffer-size percent 30;
}




ef-1 {
transmit-rate percent 60;
buffer-size percent 60;
}


}


}

[Contents] [Prev] [Next] [Index] [Report an Error]