CPU's were pegged for a customer of mine in California. tracked it
down to 2 events that went down at that time with a large message
volume.
1) Peering between GLBX and Level3 dopped somewhere, causing many
prefixes to shift away from L3 paths.
2) Some IPv6 prefixes were aggressively bouncing f
2009/5/18 Adam Armstrong :
> David Storandt wrote:
>>
>> We're stuck in an engineering pickle, so some experience from this
>> crew would be useful in tie-breaking...
>>
>> We operate a business-grade FTTx ISP with ~75 customers and 800Mbps of
>> Internet traffic, currently using 6509/Sup2s for cor
Having recently received some de-bogon'ed addressing in or about this March,
I can tell you that the one problem I had was people that had not updated
their Bind Bogon filters (
http://www.cymru.com/Documents/secure-bind-template.html) and so were not
responding to requests from our address space,
OSPF (on cisco anyway) will balance 6 paths automatically assuming you
haven't messed with bandwidth or cost settings, and the paths have the
same iftype. If not, setting the bandwidth equally will also do the
trick. (I don't like messing with cost directly, just me)
I would also point out that
This reason is twofold, one is Resellers were just buying whatever cheap
gbics they could and bundling them with Procurve switches (I'm sure this
happens to other vendors too). Thus most of the profitable parts of
switch sales were being eroded by the resellers.
The other is that Procurve offers
> On Tue, 17 Jun 2008, Jay R. Ashworth wrote:
>
> > On Tue, Jun 17, 2008 at 01:03:32AM -0400, Steve Bertrand wrote:
> >> I would like to know ANYONE who has a policy strict enough, and
> >> enforces it so as to have even an almost perfect cabling
> >> infrastructure...is there such a thing?
> >
6 matches
Mail list logo
