–
74
–
Chapter 3
| Basic Management Tasks
Managing System Files
◆
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
level1-5261.bix
(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
Level1-5261.BIX
from
the server even though
Level1-5261.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,
level1-2651.bix
and
Level1-2651.bix
are considered to be unique files. Thus, if the upgrade file is
stored as
Level1-2651.bix
on a case-sensitive server, then the switch (requesting
level1-5261.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
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 swi
tch’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.
◆
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.
Summary of Contents for GEL-5261
Page 14: ...14 Contents Glossary 551 Index 559...
Page 26: ...26 Figures...
Page 30: ...30 Section I Getting Started...
Page 42: ...42 Section II Web Configuration IP Services on page 527...
Page 45: ...Chapter 2 Using the Web Interface NavigatingtheWebBrowserInterface 45 Figure 1 Dashboard...
Page 62: ...62 Chapter 2 Using the Web Interface NavigatingtheWebBrowserInterface...
Page 180: ...Chapter 6 Address Table Settings Issuing MAC Address Traps 180...
Page 208: ...Chapter 8 Congestion Control Storm Control 208 Figure 121 Configuring Storm Control...
Page 228: ...228 Chapter 10 Quality of Service Attaching a Policy Map to a Port...
Page 332: ...Chapter 12 Security Measures ARP Inspection 332 Figure 207 Displaying the ARP Inspection Log...
Page 436: ...Chapter 13 Basic Administration Protocols LBD Configuration 436...
Page 488: ...488 Chapter 14 Multicast Filtering Filtering MLD Query Packets on an Interface...
Page 498: ...Chapter 15 IP Tools Address Resolution Protocol 498...
Page 517: ...517 Chapter 16 IP Configuration Setting the Switch s IP Address IP Version 6 interface...
Page 542: ...540 Section III Appendices...
Page 560: ...Glossary 558...
Page 570: ...568 Index E062017 ST R01...