Diagnostic error codes and remedies for TFTP transfers
This section describes the error messages associated with TFTP transfer of configuration files, software images or flash images to or from a Ruckus device.
|
Error code |
Message |
Explanation and action |
|---|---|---|
|
1 |
Flash read preparation failed. |
A flash error occurred during the download. Retry the download. If it fails again, contact customer support. |
|
2 |
Flash read failed. |
|
|
3 |
Flash write preparation failed. |
|
|
4 |
Flash write failed. |
|
|
5 |
TFTP session timeout. |
TFTP failed because of a time out. Check IP connectivity and make sure the TFTP server is running. |
|
6 |
TFTP out of buffer space. |
The file is larger than the amount of room on the device or TFTP server. If you are copying an image file to flash, first copy the other image to your TFTP server, then delete it from flash. (Use the erase flash ... CLI command from the privileged exec model to erase the image in the flash.) If you are copying a configuration file to flash, edit the file to remove unnecessary information, then try again. |
|
7 |
TFTP busy, only one TFTP session can be active. |
Another TFTP transfer is active on another CLI session, or Web management session, or network management system. Wait, then retry the transfer. |
|
8 |
File type check failed. |
You accidentally attempted to copy the incorrect image code into the system. For example, you might have tried to copy a Chassis image into a Compact device. Retry the transfer using the correct image. |
|
16 |
TFTP remote - general error. |
The TFTP configuration has an error. The specific error message describes the error. Correct the error, then retry the transfer. |
|
17 |
TFTP remote - no such file. |
|
|
18 |
TFTP remote - access violation. |
|
|
19 |
TFTP remote - disk full. |
|
|
20 |
TFTP remote - illegal operation. |
|
|
21 |
TFTP remote - unknown transfer ID. |
|
|
22 |
TFTP remote - file already exists. |
|
|
23 |
TFTP remote - no such user. |
This section describes the error messages associated with the TFTP transfer of PoE firmware file to a Brocade device.
|
Message |
Explanation and action |
|---|---|
|
Firmware TFTP timeout. |
TFTP failed because of a time out. Check IP connectivity and make sure the TFTP server is running. |
|
Firmware is not valid for this platform. |
Each Power over Ethernet (PoE) firmware file delivered by Brocade is meant to be used on the specific platform only. If the file is used on a platform for which it is not meant, then this error message will display. Download the correct file, then retry the transfer. |
|
Firmware is not valid for the IEEE 802.3at (PoE-Plus) controller type. |
Each PoE firmware file delivered by Brocade is meant to be used on the specific platform only. If the file is used on a platform for which it is not meant, then this error message will display. Download the correct file, then retry the transfer. |
|
Firmware is not valid for the IEEE 802.3af PoE controller type. |
|
|
Firmware type cannot be detected from the firmware content. |
Each PoE firmware file delivered by Brocade is meant to be used on the specific platform and the specific PoE controller on the specified module. If the file is used for a platform for which it is meant, but the PoE controller is not same then this error message will display. Download the correct file, then retry the transfer. |
|
TFTP File not Valid for PoE Controller Type. |
|
|
Firmware TFTP remote file access failed. |
The TFTP server needs read access on the PoE firmware file. Check the permissions on the file, then try again. |