>Looks like you get 12 queues per MX80/104 for ingress shaping. Doesn't seem to >be tied to QX at all. Egress you get per unit on the MIC slots though. > >https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/cos-configuring-ingress-hierarchical-cos-on-trio-mpc-mic.html > >https://www.juniper.net/documentation/en_US/junos/topics/concept/cos-hierarchical-scheduling-understanding-fine-grained-queuing-for.html
So according to this, ingress scheduling is supported on the MX80 MIC slots. My question remains, which is, wtf is up with the inconsistent commit error? I checked PRs, but I've yet to find anything relevant. -evt On Fri, Oct 5, 2018, 8:45 PM Alexander Arseniev via juniper-nsp < juniper-nsp@puck.nether.net> wrote: > Hello, > Egress scheduling/shaping on MIC ports - correct, that's why I said > "roughly" equal. > Ingress scheduling/shaping requires Q or EQ MPC which is not > supported on MX80. > Thanks > Alex > > ------ Original Message ------ > From: sth...@nethelp.no > To: arsen...@btinternet.com; juniper-nsp@puck.nether.net > Sent: 05/10/2018 20:20:06 > Subject: Re: [j-nsp] MX80 Input Scheduling/Shaping > > >>Ingress scheduling is supported only on Q and EQ MPCs - Juniper MX > >>series book, 2nd ed, page 598. > >> > >>MX80 COS capabilities are roughly equal to MPC1, without Q. > > > >Disagree. MX80 does per-VLAN queuing/scheduling/shaping just fine for > >ports on MICs. *Not* for the builtin 10G ports. > > > >Steinar Haug, Nethelp consulting, sth...@nethelp.no > > _______________________________________________ > 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 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp