Jacob, This seems to be normal. Please refer the below link,
http://www.juniper.net/techpubs/software/junos/junos82/swconfig82-cos/html/cos-ba-classifiers5.html Thanks -Ashok -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacob Gårder Sent: Wednesday, May 02, 2007 8:57 PM To: juniper-nsp@puck.nether.net Subject: [j-nsp] Default mappings of experimental bits in 8.2 Hi all! I've noticed a change (bug?) in the default behavior of the MPLS-exp mapping form JUNOS 8.1 to 8.2. The AF-traffic is marked with 100/101 and EF-traffic is marked with 010/011. Shouldn't this be vice versa? Is this corrected in 8.3? Best regards, jacob -------------------- [EMAIL PROTECTED]> show class-of-service classifier name exp-default Classifier: exp-default, Code point type: exp, Index: 9 Code point Forwarding class Loss priority 000 best-effort low 001 best-effort high 010 expedited-forwarding low 011 expedited-forwarding high 100 assured-forwarding low 101 assured-forwarding high 110 network-control low 111 network-control high [EMAIL PROTECTED]> show class-of-service rewrite-rule name exp-default Rewrite rule: exp-default, Code point type: exp, Index: 27 Forwarding class Loss priority Code point best-effort low 000 best-effort high 001 expedited-forwarding low 010 expedited-forwarding high 011 assured-forwarding low 100 assured-forwarding high 101 network-control low 110 network-control high 111 _______________________________________________ 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