Knowledgebase

Issue:

Trouble shooting errors when transfering files using netload on the Jetstream and CS9000.

Netload is the internal command line option of the server to initiate a TFTP transfer of firmware, configuration, etc ...(this should not be confused with the Windows Jetload utility to perform a serial file transfer of firmware.

Cause:

1. TFTP is not active on the remote host or is not responding to the TFTP request due to a communication problem.
2. File is not in the correct TFTP configured directory.
3. Incorrect or corrupted file.
4. TFTP security does not permit access to file.

Solution:

Console messages displayed for the above problems:

1.

TFTP: Timed Out
TFTP: Timed Out
TFTP: Timed Out
TFTP: Timed Out
TFTP: Timed Out
TFTP: Timed Out
?fail

Verify that a TFTP server daemon is running on the host; verify that the IP address in the host table is correct; and that the TFTP host can communicate to the Jetstream/CS9000.

2.

TFTP: Error code 256: File not found
?fail

Verify the file name and directory path.
Note that some TFTP server daemons will use "/" as the configured root directory while others require the full path to be specified.
The file name syntax used by Netload is always in UNIX format even for Windows TFTP services.

Example: the TFTP server application running on the Windows host called "NTserver" is configured so that the "root" directory is c:\tftp and the firmware file is c:\tftp\js8500.bin. The syntax for the netload command would be:
LS2000# netload software NTserver /js8500.bin

3.

TFTP: Transfer succeeeded
Programming flash...
FLASH: about to copy PROM to flash...
FLASH: download image size of x bytes not 1MB
FLASH: operation failed
failed
?not enough memory

If the file was FTP'd from another host, ensure that it was transfered in Binary mode; or download the file again from the Perle website.

4.

TFTP: Error code 512: Access violation
?fail

Verify the security setting configured for the TFTP server daemon and ensure that the file has read access.
Note that some TFTP server daemons will use "/" as the configured root directory while others require the full path to be specified.