* Abel Alejandro
> I have a very strange behavior in my Juniper 4 X EX4200 switch
> cluster. I am running version 10.0S1.1.
I can't comment on your specific issue, but I can say I've had strange
behaviour in conjunction with mirroring, too. It might simply be that
mirroring isn't supported very
Hi All,
Do any of you know if it is possible to run IPv6 over a LAG bundle on an E320?
Whenever I try to configure anything to do with IPv6 on a lag interface I get
the following;
t-rex:lab(config-if)#ipv6 address ::dead:beef::1/64
% lower layer bind failed
Is this expecte
PR #431101. The PR synopsis indicates that it happens when you're
configured for "interface all", but this doesn't appear to be related.
We found the problem listening to an individual interface. TAC said
there is no planned fix for this, as it's believed to be a bug in
hardware. This was about a y
We didn't see any duplication, but we only run analyzers with input
ingress/egress both configured on the same interface, never one at a
time. And this was on a standalone 3200. Not sure if a 4200 VC
performs any different?
All we saw was a VLAN tag mismatch on the analyzer packets, no duplication
> unless the mirror capabilities of the switch are just broken
Sorry to be the bearer of bad news, but the mirror capabilities of the
switch are ... broken. When you mirror packets from one PFE to
another, the VLAN tags get scrambled. It's apparently a hardware
defect. You only get the correct VLA
Hello,
I have a very strange behavior in my Juniper 4 X EX4200 switch cluster.
I am running version 10.0S1.1.
The problem is that the switch seems to be duplicating packets with a
different vlan (unless the mirror capabilities of the switch are just
broken).
aalejan...@mop-ex4200# show ethernet-
6 matches
Mail list logo
