Did this work in some other release?
Pls also check the "show log messages" output by first removing the classifier
from the GigE interface and commit, then apply the classifier and then commit
again. This is to see if COSD is spitting out any errors during the commit
related to this classifier and interface when it is committed. Also check "show
class-of-services interface ge-x/y/z.<unit>" to see if th classifier is
associated with the interface or not. Also, note the classifier index shown in
this output.
Some more checks if you are still willing :)
Log into cfeb0
- start shell pfe network cfeb0
- show ifl brief (check ifl index for ge-x/y/z.<unit>)
- show cos ifl-subunit <ifl index>
Also collect this command from cfeb0
- show cos classifier
In this output, check the classifier index shows the above ifl index attached
to it.
Thanks,
Nilesh.
----- Original Message -----
From: juniper-nsp-boun...@puck.nether.net <juniper-nsp-boun...@puck.nether.net>
To: meryem Z <merye...@hotmail.com>
Cc: juniper-nsp@puck.nether.net <juniper-nsp@puck.nether.net>
Sent: Tue Feb 16 21:26:53 2010
Subject: Re: [j-nsp] dscp classifier doesn't work - junos 9.6
On 16/02/2010, at 10:14 PM, meryem Z wrote:
>
> Hello ,
>
> I have an M7i router with junos 9.6 R3 .
>
> Below it's hardware config :
>
> Hardware inventory:
> Item Version Part number Serial number Description
> Chassis A6156 M7i
> Midplane REV 05 710-008761 CY8948 M7i Midplane
> Power Supply 0 Rev 06 740-008537 6122911 AC Power Supply
> Routing Engine REV 12 740-009459 9005089909 RE-5.0
> CFEB REV 07 750-010463 CY8890 Internet Processor II
> FPC 0 E-FPC
> PIC 0 REV 11 750-002970 CZ3397 4x OC-3 SONET, SMIR
> PIC 1 REV 08 750-010238 CY7657 1x G/E SFP, 1000 BASE
> Xcvr 0 REV 01 740-011782 PAR1XC7 SFP-SX
> PIC 2 REV 09 750-007641 CW5063 1x G/E IQ, 1000 BASE
> Xcvr 0 REV 01 740-011782 PAR1XFB SFP-SX
> PIC 3 REV 10 750-005723 CZ9407 2x OC-3 ATM-II IQ,
> SMIR
> FPC 1 E-FPC
> PIC 2 BUILTIN BUILTIN 1x Tunnel
> PIC 3 REV 08 750-009099 CY5909 1x G/E, 1000 BASE
> Xcvr 0 REV 01 740-011782 PAR1XC3 SFP-SX
> Fan Tray Rear Fan Tray
>
>
> I configuerd a group on a sub-interface on the IQ PIC 2 , including
> classifier , re-write rules and scheduler map.
>
> I'm sending traffic on this sub-interface , correctly marked (0xB8 for ef) ,
> using iperf traffic generator. Iperf server is connected to an extreme alpine
> switch.
>
> when I issue show interface queue i see that all the traffic is on the BE
> queue , no matter the marking is.
>
> my Cos configuration is :
>
> mer...@liscr2> show configuration class-of-service interfaces ge-0/2/0 unit
> 1004
> apply-groups cos_customer_ivo;
>
> mer...@liscr2> show configuration groups cos_customer_ivo
> class-of-service {
> interfaces {
> <ge-*/*/*> {
> unit <*> {
> scheduler-map sch_map_ivo;
> classifiers {
> dscp classify_dscp;
> }
> rewrite-rules {
> dscp rewrite_dscp;
> ieee-802.1 default;
> }
> }
> }
> }
> }
>
>
> mer...@liscr2> show configuration class-of-service classifiers dscp
> classify_dscp
> import default;
> forwarding-class best-effort {
> loss-priority high code-points 000001;
> }
>
> mer...@liscr2>
>
> Is there anything wrong with the config ?
>
>
> Thank you.
Hi Meryem,
Perhaps you can try with a MF classifier (ie. firewall) that matches on the
DSCP field to verify that the traffic is being marked correctly upon ingressing
into ge-0/2/0.1004? You can have an action of a forwarding class as well:
[edit firewall family inet]
r...@r1# show
filter foo {
term 1 {
from {
dscp ef;
}
then forwarding-class expedited-forwarding;
}
}
Then you can verify everything before you switch back to BA classification.
Truman
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
