The following files are required for the CFIP to start:
–
‘boot.ini’ file, - device boot configuration file. This file is a text file and contains the name of the
firmware file which must be executed on start-up. The file name can be freely changed, but its
default name is ‘boot.ini’; hereinafter, it is assumed that this file has default filename. The most
important factor concerning this file is that it must be uploaded with ‘B’ and ‘e’ attribute flags
(flags are case sensitive!), only then it will be treated as executive script.
Attribute flags for ‘boot.ini’ file:
B
– query run at boot;
e
– executive script
For information how to upload files in the Flash disk, please refer to
Chapter 7
.
–
Firmware file, - this file is the main firmware executable for the appropriate CFIP model. The file
name can be freely changed, but its default name will contain the version and CFIP model, e.g.,
‘cfipf000.elf.ezip’. The most important factor concerning this file is that it must be uploaded with
‘E’ and ‘c’ attribute flags, otherwise this file will not be used as the firmware.
Attribute flags for firmware file:
E
– executable binary;
c
- compressed
Notes:
–
The files are uploaded from PC to Flash disk using TFTP/FTP (via Ethernet management port), or
using Xmodem protocol (via RS232 serial port), for more information about file upload please
refer to
Chapter 7
; configuration backup files are created by CFIP management system.
–
The flash disk may store other files as well, for example - previous firmware versions,
configuration backup files, - up to 6.5 Mb (about 5 firmware files).
–
The attribute flags for files are case sensitive.
–
The file names can be changed, but it is very important that the file has the necessary attribute
flags; otherwise, the file will not be used either as firmware, or as ‘boot.ini’ type file.
–
There are no file extensions in the file system; either file, when edited, is treated as ASCII text
file.
–
When uploading the file, if the Flash disk stores the file with the same filename as for the file
being uploaded, it will be overwritten with the new file.
Configuration backup files
Using ‘
cfg backup <filename>
’ command, the user can create the backup file of the current CFIP
configuration. The configuration backup file is a text file and, when created, contains the current
configuration script, - the same configuration script that is stored in EEPROM. Please refer to
Chapter
7
for more information on configuration script.
The configuration backup files are stored on Flash disk, where they can be edited or downloaded
to PC. The backup configuration file can be applied in run-time, by consecutively entering ‘
cfg restore
<filename>
’ and ‘
cfg run
’ commands. Note: the configuration restored from file is not stored in
EEPROM and, therefore it will be lost during CFIP restart. To save it in EEPROM use
‘write’
command.
The user can create and store several configuration files to quickly revert to other CFIP site
configurations.
Working with files
The following commands are intended to operate with files stored in Flash disk in the
management controller.
CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide
•
Rev. 1.13
•
© SAF Tehnika JSC 2015
105