29.04.2019 Views

OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Troubleshooting<br />

Managing Automatic Remote Configuration Download<br />

Error Description Table<br />

The following table provides information on the common server connection failures and file download<br />

errors that can occur during Automatic Remote Configuration:<br />

Error Type Error Description<br />

User Login<br />

Auto-Config<br />

Abort<br />

TFTP Response<br />

Timeout<br />

User logged in via console, Automatic<br />

Remote configuration is<br />

aborted.<br />

Instruction File not Downloaded<br />

and the Max try 3 For TFTP reached.<br />

DHCP client is automatically stopped only if<br />

a user logs in to the switch through console<br />

port before getting the DHCP lease.<br />

Instruction file not downloaded due to TFTP<br />

not reachable.<br />

Primary/<br />

Secondary<br />

Server<br />

Connection<br />

File Download<br />

and File<br />

Location Errors<br />

Download of file: from Primary Server<br />

Failed<br />

Starting download of file: from Secondary<br />

Server<br />

Download Failed - using both Pri & Sec IP<br />

Transfer error <br />

Download failed for configuration<br />

file <br />

Not all image files are downloaded<br />

Unable to download the firmware<br />

version<br />

Unable to download boot config file<br />

File download failure from primary server.<br />

File download failure from both primary and<br />

secondary server.<br />

File transfer failure.<br />

Configuration file download failure.<br />

Some of the image files are not downloaded.<br />

File location errors occur when the<br />

corresponding files are not available in the<br />

locations as mentioned in the instruction file.<br />

Unable to download AlcatelDebug.cfg<br />

Unable to download script file<br />

Script File Errors<br />

The different types of script file errors and the troubleshooting techniques for such errors are as follows:<br />

• If any script file command fails, it is logged in to a file *.err (* is the script file name) in the /flash<br />

directory and the remaining commands are implemented. In such an instance, check the *.err file. The<br />

script file commands can be manually implemented and debugged in the order specified in the script<br />

file.<br />

• If the script file name mentioned in the instruction file is incorrect, then an error is logged in the switch<br />

log or swlog.log file. In such an instance, check the swlog.log file. The script file can be downloaded<br />

manually from the FTP/SFTP servers and implemented onto the Omni<strong>Switch</strong>.<br />

page 12-22 Omni<strong>Switch</strong> <strong>AOS</strong> Release 8 <strong>Switch</strong> <strong>Management</strong> <strong>Guide</strong> May 2014

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!