* Occasionally the logical subinterface counters will return wildly
incorrect data, then mysteriously fix itself on its own after a couple
days. We've had difficulty reproducing this one, but I've heard reports
of this exact same issue from others doing the same testing, so it
can't
be
Hi Massimo !
Thx for your advice.
We have two reaseons to look at the new MPC Hardware. First we do have the
problem, that our Peering MX-960 node slots are nearly full and we need th
16port 10G Card to replace old 4x10G DPCs.
Here we have a seconde usecase where we think about using the new
On Fri, Aug 27, 2010 at 12:07:53PM +0100, Daniel Goscomb wrote:
I raised a JTAC case on exactly this yesterday for an MX80. At the
moment it seems logical units are reporting the overall usage of the
entire interface rather than their own.
We haven't tested vlan tagged interfaces with
On Fri, Aug 27, 2010 at 01:45:42PM +0200, Prochaska Gerhard wrote:
Our main goal is to use all ports of the card. Thats why we are at a
proof of concept LAB in amsterdam at the Juniper site from 2nd to
3rd of September. We want to see if we can break the 120G Limitation
by using 2ports
On Saturday, August 28, 2010 03:49:08 am Richard A
Steenbergen wrote:
We haven't tested vlan tagged interfaces with multiple
units yet, our counter bug (which matches what other
people have told me they've seen as well) was on an
untagged interface with a single .0 logical subint. The
On Sat, Aug 28, 2010 at 09:32:20AM +0800, Mark Tinka wrote:
This reminds me of an issue in JUNOS 9.3R2.8 on the EX3200 where SNMP
won't tell us about traffic on an interface if the 'description' is
applied to the logical unit.
Our NOC saw this and figured out the workaround was to move
6 matches
Mail list logo