[ hmm, some strange echo effect on this list ]
> > I would like to get interested partied together for a quick chat and
> > get your temperature on the situation so I can determine my course of
> > action. Please email me or call if interested - I'm hot to pursue /
> > lead the action.
>
> The description sounds like an overloaded router rather than anything to do
> with bridging. No? Seems like it would be more reasonable to figure out
> what the resource issue is and have that addressed.
>
> mm
>
> It is a router, we were told it is the Redbacks - of course due to the
> bridge design there can multiple ISP PVC's going through it so we feel the
> effects. With the West Coast DPVC solution - we get the DS3 directly from a
> switch vs bridge through router.
Sure it's a router, but you were saying it is a result of bridging.
My point is that that's not clear. The router might (and probably
would) be overloaded no matter what the bridging or PVC
configuration. So the approach may be more along the lines of
installing more router hardware than turning away from the bridge
groups that they used.
At any rate, I don't think we've seen it here, at least not recently.
There was an event once a year or more ago where DSL was crawling, and
Verizon had to do some router reloads or reconfigurations. We could
see it clear little by little as it seemed they addressed each router
in turn. The issue wasn't clear: some reports pointed to viral
activity (much as you mentioned in this thread), possibly overloading
the flow caches (e.g. so they may have turned that off).
mm
Recent archives of the list can be found at
http://www.westnet.com/verizonisp/
Send 'unsubscribe' in the body to verizonisp-request@westnet.com to leave.
Received on Tue May 25 15:53:26 2004
This archive was generated by hypermail 2.1.8 : Tue Jan 11 2005 - 13:52:04 EST