Alexander Arseniev wrote: > > The FC in JUNOS is the same as "qos-group" in CSCO IOS - invisible > > internal-only field which travels along with packet content across the > > switch, but is never inserted in the actual packet. The FC has > > significance for choosing output scheduling, RED drop, marking.
I have come across a problem with the fixed port classifier. I would be grateful if someone could help me out. My lab setup is at ftp://ftp.sibptus.ru/pub/vas/lab2.pdf Normally I see frames from HostA arriving at HostC with COS=3. I also want frames from HostB to arrive at HostC with COS=6. However, when I enable the rewrite-rules section at Sw3, frames from HostA no more have COS=3 (i.e. the COS field is cleared). I am ready to provide any additional detail. Below is my QoS configuration. admin@sw-kedr> show configuration class-of-service | no-more forwarding-classes { queue 0 bk; queue 1 be; queue 2 ee; queue 3 ca; queue 4 vi; queue 5 vo; queue 6 ic; queue 7 nc; } interfaces { ge-0/0/0 { unit 0 { forwarding-class ic; } } inactive: ge-0/0/22 { unit 0 { rewrite-rules { ieee-802.1 output; } } } ge-0/0/23 { unit 0 { rewrite-rules { ieee-802.1 output; } } } } rewrite-rules { ieee-802.1 output { forwarding-class bk { loss-priority high code-point 000; loss-priority low code-point 000; } forwarding-class be { loss-priority high code-point 001; loss-priority low code-point 001; } forwarding-class ee { loss-priority high code-point 010; loss-priority low code-point 010; } forwarding-class ca { loss-priority high code-point 011; loss-priority low code-point 011; } forwarding-class vi { loss-priority high code-point 100; loss-priority low code-point 100; } forwarding-class vo { loss-priority high code-point 101; loss-priority low code-point 101; } forwarding-class ic { loss-priority high code-point 110; loss-priority low code-point 110; } forwarding-class nc { loss-priority high code-point 111; loss-priority low code-point 111; } } } {master:0} admin@sw-kedr> -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:[email protected] _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
