Brocade Communications Systems Brocate Ethernet Access Switch 6910 - Manual (Page 708)

658 Brocade 6910 Ethernet Access Switch Configuration Guide
53-1002581-01
Managing System Files
32
Automatic Operation Code Upgrade
Use the System > File (Automatic Operation Code Upgrade) page to automatically download an
operation code file when a file newer than the currently installed one is discovered on the file
server. After the file is transferred from the server and successfully written to the file system, it is
automatically set as the startup file, and the switch is rebooted.
CLI References
• "upgrade opcode auto" on page 72
• "upgrade opcode path" on page 73
Usage Guidelines
• If this feature is enabled, the switch searches the defined URL once during the bootup
sequence.
• FTP (port 21) and TFTP (port 69) are both supported. Note that the TCP/UDP port bindings
cannot be modified to support servers listening on non-standard ports.
• 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 es020000.bin (using upper case and lower case letters
exactly as indicated here). Enter the file name for other switches described in this manual
exactly as shown on the web interface.
• 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 ES020000.BIN from the server even though
es020000.bin 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,
es020000.bin and ES020000.BIN are considered to be unique files. Thus, if the upgrade file
is stored as ES020000.BIN (or even Es020000.bin) on a case-sensitive server, then the switch
(requesting es020000.bin) 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 server’s operating system if you are unsure of its file
system’s 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 switch’s 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.