Does the Juniper RE not the same as Cisco RSP. I think the control plane information all need to go to the RE, if RE had any issue, why the traffic don't have any issue?
Thanks and regards, Xu Hu On 18 Jul, 2012, at 22:32, "OBrien, Will" <obri...@missouri.edu> wrote: > Check your fxp0 configuration. You may be shipping return traffic out random > interfaces... > We are leaning toward putting all production traffic inside a virtual routing > instance/chassis and using the main routing instance just for management. > ________________________________________ > From: juniper-nsp-boun...@puck.nether.net > [juniper-nsp-boun...@puck.nether.net] on behalf of Morgan McLean > [wrx...@gmail.com] > Sent: Wednesday, July 18, 2012 1:34 AM > To: juniper-nsp@puck.nether.net > Subject: [j-nsp] MX80 poor monitoring, packet loss to RE, SNMP not responding > > I have a pair of MX80's that both are very unreliable in terms of trying to > monitor them. Any traffic destined to the RE, be it ICMP or SNMP seems to > be very hit or miss. Sometimes SNMP won't respond, pinging it gives me > maybe 50% loss on average, but it passes traffic fine. > > This causes issues with monitoring, false alerts, etc. I realize the > traffic destined for the RE is not as important, but the box is hardly > loaded and among maybe 50 other juniper devices I have, EX, SRX, only these > are giving me issues. > > Can anybody give me any insight? > > Thanks, > Morgan > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
