CLI Reference Guide-R01

Table Of Contents
Chapter 1
| Initial Switch Configuration
Automatic Installation of Operation Code and Configuration Settings
– 62 –
The host portion of the upgrade file location URL must be a valid IPv4 IP
address. DNS host names are not recognized. Valid IP addresses consist of four
numbers, 0 to 255, separated by periods.
The path to the directory must also be defined. If the file is stored in the root
directory for the FTP/TFTP service, then use the “/” to indicate this (e.g.,
ftp://192.168.0.1/).
The file name must not be included in the upgrade file location URL. The file
name of the code stored on the remote server must be ECS4130.bix (using
lower case letters as indicated).
The FTP connection is made with PASV mode enabled. PASV mode is needed to
traverse some fire walls, even if FTP traffic is not blocked. PASV mode cannot be
disabled.
The switch-based search function is case-insensitive in that it will accept a file
name in upper or lower case (i.e., the switch will accept ECS4130.BIX from the
server even though ECS4130.bix was requested). However, keep in mind that
the file systems of many operating systems such as Unix and most Unix-like
systems (FreeBSD, NetBSD, OpenBSD, and most Linux distributions, etc.) are
case-sensitive, meaning that two files in the same directory, ecs4130.bix and
ECS4130.BIX are considered to be unique files. Thus, if the upgrade file is stored
as ECS4130.BIX (or even Ecs4130.bix) on a case-sensitive server, then the switch
(requesting ECS4130.BIX) will not be upgraded because the server does not
recognize the requested file name and the stored file name as being equal. A
notable exception in the list of case-sensitive Unix-like operating systems is
Mac OS X, which by default is case-insensitive. Please check the documentation
for your servers operating system if you are unsure of its file systems behavior.
Note that the switch itself does not distinguish between upper and lower-case
file names, and only checks to see if the file stored on the server is more recent
than the current runtime image.
If two operation code image files are already stored on the switchs file system,
then the non-startup image is deleted before the upgrade image is transferred.
The automatic upgrade process will take place in the background without
impeding normal operations (data switching, etc.) of the switch.
During the automatic search and transfer process, the administrator cannot
transfer or update another operation code image, configuration file, public key,
or HTTPS certificate (i.e., no other concurrent file management operations are
possible).
The upgrade operation code image is set as the startup image after it has been
successfully written to the file system.
The switch will send an SNMP trap and make a log entry upon all upgrade
successes and failures.