Thanks for explanation.
But I am still confused, as I have some statements configured
(and successfully commited) under class-of-service using new
syntax.
What do you mean by "bootup your router with new CoS cli"?
Do I need to enable new CoS somehow special?
Maybe that is the reason, why my attempts to deploy
two separate forwarding classes for be and voip are failing....
I understand that I have some limitations because my router
has old FPCs (not extended), but what I need to do is just
assure that traffic with ip_precedence 5 will be emitted first.
I know that this is "priority queuing", which is nt supported
on old, non Enhanced FPCs, but I was hoping that maybe i will
be able to differentiate traffic into 2 classes, police be class
to 80% of interface capacity, and then I will have remaining 20%
reserved for voip class.
Any ideas how to approach this issue on Juniper M20 with old FPCs?
Thanks in advance,
Przemek
On Mon, 2002-06-03 at 14:31, George Zhou wrote:
> Hello Przemek,
>
> In JunOS 5.3, the old CoS cli/mode still exists. But if
> you bootup your router with new CoS cli, the cosd will kick in,
> and you will get error messages from "show chassis cos".
>
> This command is removed from JunOS 5.4 and above..
>
> Thanks,
>
> - George
>
> >
> > All,
> >
> > How come this command is still available in JunOS 5.3?
> > It is removed from documentation for 5.3, and I believe
> > it is showing improper information about queue assignments:
> > ...
> > bits 000 output-queue 0;
> > bits 001 output-queue 0;
> > bits 010 output-queue 0;
> > bits 011 output-queue 0;
> > bits 100 output-queue 0;
> > bits 101 output-queue 0;
> > bits 110 output-queue 0;
> > bits 111 output-queue 0;
> > ...
> >
> > Thanks,
> >
> > Przemek
> >
> >
> >
>
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:36 EDT