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.
Download Component Files<br />
Managing Automatic Remote Configuration Download<br />
Instruction File Usage <strong>Guide</strong>lines<br />
• The instruction file is case sensitive and can contain only the keywords provided in the instruction file<br />
output example.<br />
• The keywords can be placed in any order.<br />
• If the Keyword:Value format is incorrect, the information on that line is discarded.<br />
• Firmware version must be provided in the format as specified in the example.<br />
• Pathnames provided must contain the complete path to the file location.<br />
• If any file is not required, the value is provided as “None”. For example, if a debug configuration file is<br />
not required to be downloaded, the instruction file syntax is as follows:<br />
Debug filename:None<br />
Debug location:None<br />
• The header line is the first line of the instruction file and begins with “!” character.<br />
• Header line contents are logged to the switch log along with the other contents of the instruction file.<br />
• The header and comment lines begin with “!” character.<br />
Firmware Upgrade Files<br />
Firmware files are also known as image files. These files have the .img extension.<br />
Firmware files may be different based on the Omni<strong>Switch</strong> platform. The relevant firmware files are downloaded<br />
from the location mentioned in the instruction file. The filenames of the firmware files must exactly<br />
match the files which are to be downloaded. The filenames are in the *.img format. Modified filenames<br />
are not recognized.<br />
Details about the different firmware files and file names can be found in “Managing System Files” on<br />
page 2-1.<br />
Firmware files are downloaded only when the firmware version in the instruction file is higher than the<br />
firmware version present on the switch.<br />
Bootup Configuration File<br />
The bootup configuration (vcboot.cfg) file is not present during the initial bootup process when a new<br />
switch is integrated in to the network. The vcboot.cfg file is automatically generated and stored in the<br />
/flash/working directory when a write memory command is issued.<br />
During the automatic remote configuration process, the bootup configuration file is downloaded from the<br />
FTP/SFTP server and stored as vcboot.cfg in the /flash/working directory of the switch.<br />
If no script file is downloaded, the switch boots up normally according to the configurations specified in<br />
the vcboot.cfg file when the remote configuration download process is completed.<br />
Debug Configuration File<br />
The debug configuration file is used for setting specific Omni<strong>Switch</strong> settings and must only be used as<br />
directed by Service and Support. During the automatic remote configuration process, the debug<br />
configuration file is downloaded with the filename AlcatelDebug.cfg.<br />
page 12-14 Omni<strong>Switch</strong> <strong>AOS</strong> Release 8 <strong>Switch</strong> <strong>Management</strong> <strong>Guide</strong> May 2014