[prev in list] [next in list] [prev in thread] [next in thread] 

List:       inet-access
Subject:    Re: Strange cisco problem --djv
From:       Keith Woodworth <kwoody () citytel ! net>
Date:       2003-10-24 6:41:24
[Download RAW message or body]

On Thu, 23 Oct 2003 jlewis@lewis.org wrote:

|->On Thu, 23 Oct 2003, Keith Woodworth wrote:
|->
|->> Hmm. Ok if thats the case if one does a wr mem does it only write that
|->> part of the config in memory to nvram? Leaving one with only a partial
|->> startup config? 
|->
|->Yes.  We've hosed several AS5x00 access-servers this way.  The 5200's in 
|->particular, once memory is sufficiently fragmented lose most of their 
|->Virtual-Templates and the ip address portion of ethernet0.  Do a wr mem at 
|->that point, and you will need console/dial access to fix it after the 
|->next reload.
|->
|->During the onset of nachi, when applying filtering to our dial servers, we 
|->had to be very careful to make sure there was sufficient "memory health" 
|->before making/saving config changes...otherwise, it was reload, then make 
|->changes and save.

shite...that does not bode well then for the 2 RSM's we have in a Cat5500.
I did some config changes (well just shuts on some vlans) to both of
them while in the midst of nachi spreads (there is still some traffic
there causing some pain) and did a wr mem a few times on them both. We
dont do many changes (just desc changes and shut/no shuts on vlans) to
them at least and we do have the config's backed up via tftp.

But still...damn this aint gonna be pretty if a failover happens.

thanks,
Keith



_______________________________________________
"Eat sushi frequently". - Avi
inet@inet-access.net is the human contact address.
list@inet-access.net is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]