[j-nsp] High latency and slow connections

[Gary Tate]

Are the pings transiting the M5 or source from the RE?

You say you have a fastethernet connected box.  Where is this box 
connected, is it on the production network or connected to the 
management network via fxp0?

If the FE Box is on the network, is there any other equipment in the 
path?  Do you have a way to isolate a path to carry out transit pings 
across the M5 only?

It is hard to think of a cause for such a dramatic increase in the data 
plane of the M5, only buffering would introduce such delays and as the 
interfaces have low levels of traffic this would not be the case.  If 
however the pings are being sourced from the RE there may be some 
increased control traffic that is taking precedence over the pings.

Gary

On Wednesday, Nov 5, 2003, at 07:12 US/Pacific, Blaz Zupan wrote:

> A Juniper M5 running 5.5R1.2 has two STM-1's and a gigabit ethernet
> connection. It's been running fine for ages (uptime is 366 days). 
> Today, we
> suddenly started seeing extremely high latency through the box (40 ms 
> ping
> from a fast ethernet connected box, where it was usually below 1 ms). 
> All
> connections exhibit this, no matter which interface they're comming 
> from or
> where they're going to. Traffic levels on all interfaces are normal, 
> no high
> packet per second rates. No configuration changes.
>
> Only unusual thing that has happened today, one of the two STM-1's has 
> gone
> down for about two minutes, this was the first outage on that STM-1 
> for the
> past 365 days, the outage was because of a problem with the SDH 
> equipment.
>
> I have scheduled an emergency reboot of the box because at this point 
> that's
> all I can do. I'll upgrade to 5.7 as well to get rid of the annoying
> "temperature sensor failed" messages.
>
> Any idea what could be going on. Anyone seen something simmilar?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>