[j-nsp] EX4200 cluster duplicating traffic or broken mirror?

[Norman Elton]

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 year ago, so if someone hears otherwise,
please let us know.

Norman

On Mon, Sep 13, 2010 at 5:42 PM, Tim Harman <Tim.Harman at vector.co.nz> wrote:
> Is there a PR for this you know of, or a KB or similar?
> Something I can show our Network Ops guys so they're aware of it?
>
> Many thanks,
>
>
> --
> Tim Harman
> Senior Network Architect
> Vector Networks
> P: +64 9 978 8335
> M: +64 27 223 5435
> E: Tim.Harman at vector.co.nz
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Norman Elton
> Sent: Tuesday, 14 September 2010 8:14 a.m.
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] EX4200 cluster duplicating traffic or broken
> mirror?
>
>> 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 VLAN tags when the source and destination interfaces are
> on the same PFE.
>
> Norman
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> The information contained in this e-mail is confidential and may
> be legally privileged. If you have received it in error, you may
> not read, use, copy or disclose this email. If you are not the
> intended recipient, please let us know by reply e-mail
> immediately and then delete this email from your system. We
> shall
> not be responsible for any changes to, or interception of, this
> email or any attachment after it leaves our information systems.
> We accept no responsibility for viruses or defects in this email
> or any attachments.
>