[c-nsp] 7500 having problems after upgrade from 12.0.19S2 to 12.0.31S1

Bruce Pinsky bep at whack.org
Tue Nov 22 14:53:43 EST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert E.Seastrom wrote:
> Rodney Dunn <rodunn at cisco.com> writes:
> 
> 
>>On Tue, Nov 22, 2005 at 08:14:42AM -0500, Robert E.Seastrom wrote:
>>
>>
>>>ST merge was after 12.0(21)S.  The new BGP data structure is said to
>>>be more computationally efficient at the expense of memory efficiency.
>>
>>Absolutely correct. However, there is a memory gain too in that
>>for a full reconvergence it takes much much less transient memory
>>to reconverge.
> 
> 
> Wasn't aware of that.  Interesting.
> 
> 
>>Not pointed at Robert but a general comment:
>>
>>We can't code new features without making the image larger.
>>We do (even though some may not think so) try very very hard to
>>be extremely memory conscious when we code new features.
> 
> 
> I'm with you here.  By definition, adding features takes memory, and
> if my understanding is correct, there's already enough shared code
> between certain features that ripping out something we don't care
> about anymore (for instance, X.25) would not gain much unless we took
> out other stuff (for instance, FR) that we still want.
> 
> I think all in all Cisco has done a pretty good job of avoiding code
> bloat (reasonable people will disagree as to whether the same
> assessment applies to "feature list bloat" as well.  That's a
> discussion for another day, though I'm sure I'm not alone in wishing
> fervently that certain old releases would continue to be supported).
> 
> 


Yep, it is pretty good since the RSP4 is a 10 year old design.

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDg3dHE1XcgMgrtyYRAke1AKDQdx0opY0sqGCh5W2HONu1mefh2wCeLV4o
IouE4OCcTYfb3SB8tQVmOqo=
=5A75
-----END PGP SIGNATURE-----


More information about the cisco-nsp mailing list