> 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.
I wasn't necessarily saying the problem was a result of bridging - it's the
Verizon East Coast ADSL bridge design is flawed.
You suggest beefing up the router gear - my point is it should be pulled and
not there at all. If we had a connection direct from the switch the excess
wormy virus riden Layer 3 traffic wouldn't flood an ATM switch and this
problem would not occur.
> 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).
It was August when Blaster started.
Has anyone else experienced this issue over the past year ? I'd be curious
on your setups (i.e. Circuit, Router platform, # custs) - we have a DS3 with
about 300 circuits running on a Cisco 7206 VXR which should be more than
enough power for right now.
Eric
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 Wed May 26 09:35:19 2004
This archive was generated by hypermail 2.1.8 : Tue Jan 11 2005 - 13:52:04 EST