Yep - listen to JTAC. The parity error is definitely a sign that the memory on your switch is flakey - I had an EX4200 completely lock-up and drop out of a VC after 6 months of flawless operation. Rebooted it and it came good, 24 hours later it dropped right back out again with the parity error again.
RMA and everything is happy again. On 10/04/2013, at 2:50 PM, Luca Salvatore <[email protected]> wrote: > Wondering if anyone has seen any issues with EX switches running port > mirroring - specifically seeing the switch generate a 'parity error' and > crashing? > I have an EX4200 10.4r5.5, a few hours after turning on port mirroring the > switch crashed. It threw some memory parity errors which JTAC tells me means > the switch is faulty and should be replaced. > > The switch in question has been running fine for 3 years, but turning on a > ingress and egress port mirror (on a single port) seems to make the switch > have a bad day. The switch isn't busy, and the port that I'm mirroring has > about 80 to 100Mb of traffic. I'm mirroring the port to an IDS and would > like to keep it running for the foreseeable future. > > Any thoughts on this situation? > Thanks > Luca. > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
