perhaps you did a wr er (Write Erase, legacy command to erase NVRAM) instead
of a wr me, (write memory, legacy copy running-config startup-config
command). The file is stored in NVRAM so formatting NVRAM will also cause a
similar problem. Anything that damages or affects NVRAM (Non-Volatile RAM)
adversely (ie Electro magnetic radiation) may have the potential for causing
this also. Try holding a strong magnet outside the Pix case, just like a
videotape it may end up eraseing the NVRam. I make copies of my Pix config
weekly and save them in a especially secured directory. This allows me to
easily recreate my ruleset and replace a messed up config. This can be
accomplished in one of two ways. You can TFTP the actual config file to a
specail server (or your laptop/workstation). Or you can telnet/attach to the
console port and use a terminal emulation program to do a "Show
running-config", then copy and paste the output into a text document. The
config is not as easily to replace with a text file, but it is easier to
review/revise the rules (conduits/statics).
Ken
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, March 22, 2001 1:43 AM
To: [EMAIL PROTECTED]
Subject: RE:Configuration Erased
Hello,
I was just wondering, we're using PIX firewall and its configuration was
suddenly erased without me knowing what the reason is. Just want to ask
what are the possible reasons for this. Thank God, we put it back to normal
already.
-
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
