3Com 3500 manual System nvData save, Important Considerations Tftp

system nvData save 107

system nvData save

✓3500

9000

✓9400

✓3900

✓9300

Stores nonvolatile (NV) data on a server. The CoreBuilder 3500 uses the Trivial File Transfer Protocol (TFTP) or File Transfer protocol (FTP) to transfer the files to the host, depending on the setting for the system fileTransfer option. The SuperStack II Switch 3900, Switch 9300, and the CoreBuilder 9400 use TFTP to transfer files.

Valid Minimum Abbreviation

sy nv s

Important Considerations (TFTP)

■To store NV data, you must first create two files on the TFTP server before you send the data:

■Control file — Use any filename that is meaningful to you. Example: ctrlfile

■NV data file — Use the control filename plus the .nvd extension. Example: ctrlfile.nvd

■When the system saves NV data, it writes it to a disk file on a host computer (that is, a server) using TFTP or FTP. You can then retrieve the data from the disk file with the restore option.

■Some TFTP implementations require that you store the files in the same directory in which the TFTP daemon (server) is running on the remote host.

■Some TFTP implementations require a full path, while other implementations allow you to specify only the file name, and the system saves the file to the default TFTP directory. Consult your network administrator or TFTP documentation for details about your host system’s TFTP implementation.

■Because TFTP provides no user authentication, give loose permissions to the control file and the NV data file on the remote host (that is, make the files publicly readable and writable). TFTP servers do not grant requests for file access.