Restoring Nv Data - 3Com LANPLEX 6000 User Manual

Success
Failure
What if the module
configuration is
altered during a save?
Restoring
NV Data
Rule 1
Login incorrect.
Error: Could not open ftp session
If a session is successfully opened, a system message notifies you of the
success or failure of your save as in the following examples:
System NV data successfully stored in usr/jones/systemdata
of host 158.101.112.34.
Error - Configuration not stored.
The failure message varies depending on the problem encountered while
saving the NV data.
At the end of the save, you are returned to the previous menu.
During the save procedure, the current module configuration could be
altered. To detect this event, the software checksums the NVRAM before
and after the save. If the checksum is different, you are notified and
prompted to save the configuration again. In abnormal situations, this could
go on for an extended period, so you are given the option to terminate
the save. You are also prompted for a retry request upon network (ftp) I/O
failures. See the following example:
Error - Checksum failure, configuration of slot 4 changed
during save.
Error - Configuration not stored.
Do you wish to retry the save using the same parameters?
(y/n):
When you restore system NV data, the software presents you with a
proposal for how to restore the data. This proposal is based on the
restoration rules described below:
Exact Match — An exact match is one where the system IDs, module types,
slot assignments, and module revisions (if applicable) all match between
the saved configuration and the system on which you are restoring the
image.

Restoring NV Data

7-3