Andrew,
On transit LSR's, the default behaviour is to place all MPLS packets in
output queue 0. To override this, use the "mpls-cos-map" statement.
Here's a snip from the documentation (JUNOS 5.0 Interfaces,
Class-of-Service, and Firewalls):
Classify and Map Incoming MPLS Packets
By default, all MPLS packets are placed into output transmission queue 0
(see item 3 in Figure 19). To map MPLS packets to multiple output
transmission queues based on the CoS field in the MPLS header, you
configure the software to use the MPLS CoS mapping by including the
mpls-cos-map statement at the [edit class-of-service input interfaces
interface-name] hierarchy level:
[edit class-of-service input]
interfaces {
interface-name {
mpls-cos-map;
}
}
Keep in mind that the mapping of EXP bits to queues is static (unlike
the IP precedence to queue mapping features). That is, EXP setting of
000 maps to queue 0, 100 maps to queue 2, etc...
Regards, Jack
> -----Original Message-----
> From: Andrew Smith [mailto:as160@yahoo.com]
> Sent: Wednesday, August 29, 2001 2:57 AM
> To: juniper-nsp@puck.nether.net
> Subject: LSP Scheduling Treatment
>
>
> Hi, all
>
> I have another basic question here. O.K. so I can
> setup LSPs with different COS bits at ingress, how do
> I configure the scheduling treatment base on this COS
> values on the LSPs?
>
> TIA for any pointers
> ---andrew
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with
> Yahoo! Messenger
> http://phonecard.yahoo.com/
>
>
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:37 EDT