3Com CoreBuilder 3500, Implementation Manual

Page: 53 / 592

nvData Operations 53
nvData Operations
All of the system’s configurable parameters are saved in nonvolatile
memory. When you work with nonvolatile data (nvData), you can:
■
Save and restore your system configuration for backup.
■
Examine a saved nvData file header.
■
Reset system data to its factory default values, if necessary.
Saving nvData When you enter commands to save nvData, the system copies data that is
stored in nonvolatile memory to a disk file location that you specify. You
can use the
system nvdata save
option to save nvData from your
system to a:
■
File on another system remotely through FTP or TFTP.
■
PCMCIA flash card indirectly.
See the PCMCIA Flash Card User Guide for a detailed explanation about
how to save nvData to a PCMCIA flash memory card.
Important Considerations
Consider the following guidelines before you perform an
nvData save
operation:
■
When you use TFTP , before you save data to the file, you have to
create two files on the TFTP server. The screen display appears as
follows:
Select menu option: system nvdata save
Host IP Address [158.101.100.1]: 158.101.112.34
NV Control file (full pathname): [/tftpboot/mecca]
Enter an optional file label {?}: mecca2
Control File:mecca
Data File: mecca.nvd
Saving system ...
■
You must supply the host IP address and specify the file where you
want to save the data according to requirements of your TFTP and FTP
implementation.
■
Some TFTP implementations require that you store the file in the same
directory where the TFTP daemon (server) is running on a remote host.
■
Because TFTP does not provide user authentication, give the file loose
permissions to make it both readable and writable. TFTP does not
grant requests for file access.