On Tue, May 25, 2004 at 01:27:32PM -0400, Eric Kagan wrote:
> We just spent the morning battling Verizon where we had about 100
> customer bouncing in and out of service. We had confirmed out network
> was clean - router was under 50% CPU and could not figure out the
> issue. After many calls to Verizon saying it was "our" Layer 3 issue,
> we finally reached someone who did a PVC by PVC comparison and found
> another ISP with infected customers that were actually flooding the
> Redbacks - hence causing problems on our DS3.
>
> We have run in to this problem more than once "we call it the Verizon
> Bridge Group Flood problem" regardless it sucks and causes us a lot of
> pain. Has anyone else run in to this before ?
>
> I propose a crusade to get Verizon East to fix their network properly
> with Direct PVC and get the Redback Bridging setup to go away. We
> need to propose as we once tried a while back a one time DPVC charge,
> or let them host individual Redbacks per ISP customer vs. shared.
>
> 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
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.
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 14:58:55 2004
This archive was generated by hypermail 2.1.8 : Tue Jan 11 2005 - 13:52:04 EST