[j-nsp] Network-control queue counter increases on ccc-configured interface
Mark Tinka
mtinka at globaltransit.net
Thu Jan 26 22:02:58 EST 2012
On Friday, January 27, 2012 01:32:16 AM Keegan Holley wrote:
> This is good for some, but it's hard to recommend a
> queuing policy to someone without understanding what
> they do with their network. I've made due in the past
> with only 4 queues, especially when juniper pic's only
> had 4.
I've always thought 4 queues (including 'nc') were more than
enough.
Anything more than 4 is just a variation of the main 3 (be,
ef, af), and only serves to create more complicated products
that your sales folk can sell and make a little bit more
money (sales guys don't care how complicated the network
becomes, as long as they close the sale and guarantee their
commissions - those 3AM calls in the morning are for you,
not them).
But is it really worth the effort? Maybe, maybe not,
especially since trying to provide any kind of scheduling
for Internet access is just a waste of time. If you take
that aside, really, how much more do you need to carve out
for VPN-type services?
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20120127/74218e75/attachment.sig>
More information about the juniper-nsp
mailing list