[c-nsp] BGP memory on a 6500
David Sinn
dsinn at dsinn.com
Tue Oct 3 15:29:36 EDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'll add in that having the utilization measurable by SNMP, instead
of just command-line, would make it a bit easier to allow people to
instrument when they want to start feeling uncomfortable. :)
David
On Oct 3, 2006, at 8:09 AM, Rodney Dunn wrote:
> I'll pass that on as I agree with you.
>
> Rodney
>
> On Tue, Oct 03, 2006 at 07:34:59AM -0400, Robert E. Seastrom wrote:
>>
>> Rodney Dunn <rodunn at cisco.com> writes:
>>
>>> We are putting in a warning that will go to the syslog when the
>>> hw reaches 95% capacity to give a earlier warning.
>>>
>>> What we've found is most people just miss/ignore the warning when
>>> the problem happens because they didn't realize at the time
>>> reachability
>>> to those destinations could be totally broken. But then a lot of
>>> times
>>> the prefixes are covered under a less specific if the same
>>> forwarding
>>> next hop so on the surface everything "just works".
>>
>> This is kind of a scary failure mode. Perhaps something more
>> noticeable than just a syslog entry (something that's printed out
>> after the banner motd for instance) might be good.
>>
>> ---Rob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFIrojLa9jIE3ZamMRAhC8AJ9fV8l8+6Klv/I1uGfjsn4PJ8fIHQCdEEmh
uuljqo7qkGEApdbh6Ib1JLk=
=M7cG
-----END PGP SIGNATURE-----
More information about the cisco-nsp
mailing list