4507:write erase then reload and NVRAM config is still there!

[news2010a]

This one I do not understand. Yesterday I did 'write erase' on (2) 4507, reload it and that worked fine, the configuration was deleted.

Today I have new set of 4507's. I do 'write erase', reload it, power cycle it and then I see the 'show run' configuration intact.

Image and platform is the same I successfully completed yesterday.

Any ideas what could be wrong?

(2) sup. iv engines like the one yesterday.

cat4500-entservicesk9-mz.122-40.SG.bin

[Edison Ortiz]

When you reload, were you prompted to save config? and you said 'y'? If so, you copied the running config back to the startup config thus undoing the write erase routine.

[news2010a]

I did not. Here is the actual output below. Once it came back online, it showed up as 'mysw4-standby>' what is normal given the redundant Sup IV. The problem is that all running-config is intact there. Strange?

mysw4#wri erase

Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]y[OK]

Erase of nvram: complete

mysw4#reload

Proceed with reload? [confirm]y

**********************************************************

* *

* Welcome to Rom Monitor for WS-X4515 System. *

* Copyright (c) 2002 by Cisco Systems, Inc. *

* All rights reserved. *

* *

**********************************************************

[Edison Ortiz]

After typing 'write erase' - can you verify the 'show startup' no longer has the current config?

Can you also verify the config-register is set to 0x2102?

[news2010a]

Immediately after doing the 'write erase', confirm=yes, I do 'show startup' and

#show startup

startup-config is not present

'show ver' tells me that:

Configuration register is 0x2102

[ktwaddell]

'Immediately after doing the 'write erase', confirm=yes, I do 'show startup' and

#show startup

startup-config is not present'

at this point, I would do a wri and then reload, see what you get!

[news2010a]

So the intention is, we would copy from startup-config to running-config?

Since startup-config = nothing, we expect to clear it that way, right?

[ktwaddell]

well you could say that yeah

[nigwilli]

I have seen this response before with wr erase, try:

Edison's suggrestion first, then

erase nvram:startup-config

reload

NB: Do not save the running Config

[Edison Ortiz]

Try the command 'erase nvram:' and make sure not to reply 'y' during reload.

__

Edison.