> Once upon a time Turnando Fuad shaped the electrons to say...
> >I talked to a Livingston Rep at the Interop in Las Vegas about this problem
> >earlier this year and was told that it was known internally that the PM2eR
> >couldn't handle a full T1 load. This momentary lockup problem started after
>
> Do you know who he was? Because that is not true. The PM-2R/eR can run
> a full T1. The limitations come with the shared load of the async/ISDN ports.
> If there is heavy packet traffic coming in on the async ports, and the T1 is
> also busy, then you can get delays and drops. Again, it was never, ever meant
> as a central site high capacity router. It was always meant as a POP in a
> box to run at a remote site without the need for an additional router.
>
I don't recall the name now. But we were even negotiating a router deal
with Livingston where we would get 50% off the router because of this
problem.
Whether it's a central site or not is relative. A small POP may have 30
ports and a large POP may have 200 ports with quite a few PM2es and even
servers on that network. It's up to the ISP to manage that bandwidth and
the router manufacturer to ensure that we get the full T1 bandwidth/load
consistently. And we had more than a fully loaded PM2eR30 when we
experienced this problem. The issue at hand is the limitation of the W1 on
the PM2eR. Can the W1 port handle the full T1 load with the 30 serial
ports fully loaded. You mentioned above that it can get delays and drops.
Maybe that's the lock up problem or perceived as one.
Turnando Fuad
NSNet