Judging on previous experience, I would blame EX, not MX. :) But just to be sure - can you add input counter filters to EX interface connected to MX? Just to be 100% sure that packets are coming in without weird 802.1p
hth nick On Thu, Nov 22, 2012 at 8:58 PM, Sebastian Wiesinger < [email protected]> wrote: > * Sebastian Wiesinger <[email protected]> [2012-11-22 16:45]: > > I tried forcing all packets to best-effort/loss-priority low on the MX > > but that didn't change anything. I'm currently suspecting the EX4200 > > to be the problem. > > Okay, now I found a workaround but I'm still not sure about the > original cause. I configured this class-of-service rewrite rule on > the interface to the service provider: > > swiesinger@sw1# show class-of-service > interfaces { > ge-0/0/10 { > unit 0 { > rewrite-rules { > ieee-802.1 service-provider-rewrite; > } > } > } > } > rewrite-rules { > ieee-802.1 service-provider-rewrite { > forwarding-class best-effort { > loss-priority low code-point 000; > loss-priority high code-point 000; > } > } > } > > So I'm rewriting the codepoints in the 802.1p field to what they > should have been from the beginning... and now it works. I'm confused. > > Regards > > Sebastian > > -- > GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) > 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE > SCYTHE. > -- Terry Pratchett, The Fifth Elephant > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
