Hi Tim, These commands behave differently:
Once again, "priority <bandwidth>" would police only in case of congestion while "priority + police rate" would police on rate configured. Regards, Jeff > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:cisco-nsp- > [EMAIL PROTECTED] On Behalf Of Tim Franklin > Sent: maandag 9 juni 2008 12:05 > To: Pelle > Cc: cisco-nsp > Subject: Re: [c-nsp] difference between "bandwidth" and "priority" command > inpolicy > > On Thu, June 5, 2008 8:45 am, Pelle wrote: > > > [1] this can either be configured as: > > > > class X > > priority <bandwidth> > > In my experience, it's quite variable (by IOS, platform, phase of moon, > etc) as to whether this *actually* implements a policer or not. There's > no harm, and a degree of safety in: > > class X > priority <bandwidth> > police rate <bandwidth> > > which is guaranteed to both provide the correct information to the > scheduler, and to police the class. > > Regards, > Tim. > > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/