"I am experiencing a weird loss of configuration data on one of the DECserver 90M+ units we have. I have properly set up the unit, and left it on the table powered on, during a time period of approximately a month, the unit lost power several times (which I guess should NOT be a problem), and after checking it today, it lost its PORT related settings, but not settings related to INTERNET ADRESS / NAME etc. only PORT settings (for all ports, not just #1, which could be explained in other ways). Therefore I have 2 questions:
- Does the unit contain a battery that powers its memory? If it does, how can I make sure it is "dead"?
- Is there a command that "stores" the settings permanently and if so, which one is it?
If you have any other ideas which could help explain why some (PORT related) settings get "lost", I would be most grateful. Thanks in advance."
The DECserver does not contain a battery.
The command used to configure a DECserver 90M+ will determine whether your configuration is STORED (permanent) or WORKING (temporary).
Note:
The SHOW command will show you the current contents of the working configuration in VRAM.
The LIST command will show you the current contents of the stored configuration in NVRAM.
DECserver Stored Configuration
All stored configuration parameters are entered using the DEFINE command. The DECserver stored configuration resides in NVRAM and is read and implemented at every boot. You must perform a re-boot to activate the new configuration that was entered using the DEFINE command.
DECserver Working Configuration
All working configuration parameters are entered using the SET command. The working configuration is the VRAM memory for all running operations. The DECserver working configuration is a combination of the current NVRAM configuration PLUS any changes made as a "temporary" parameter.
If you configured the DECserver 90M+ using the SET command, then by definition, upon re-boot the configuration will use the settings stored in NVRAM, which will override your working configuration. If this happens, you need to re-enter your configuration using the DEFINE command and perform a re-boot to activate the new configuration.
For more details on the SET/DEFINE commands, please refer to page 4-1 of the Command Reference Guide and beginning on page 2-3 of the Management Guide.