Chapter 3
| Basic Management Tasks
Managing System Files
– 82 –
◆
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-L3lite.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-L3lite.BIX
from
the server even though
Level1-L3lite.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-L3lite.bix
and
Level1-L3lite.bix
are considered to be unique files. Thus, if the upgrade file is
stored as
Level1-L3lite.bix
(or even
level1-L3lite.bix
) on a case-sensitive server,
then the switch (requesting
level1-L3lite.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 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.
◆
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.
Содержание GTL-2881
Страница 30: ...Figures 30 Figure 450 Showing RIP Peer Information 669 Figure 451 Resetting RIP Statistics 670 ...
Страница 34: ...Section I Getting Started 34 ...
Страница 48: ...Section II Web Configuration 48 Unicast Routing on page 651 ...
Страница 151: ...Chapter 4 Interface Configuration VLAN Trunking 151 Figure 69 Configuring VLAN Trunking ...
Страница 152: ...Chapter 4 Interface Configuration VLAN Trunking 152 ...
Страница 229: ...Chapter 8 Congestion Control Automatic Traffic Control 229 Figure 135 Configuring ATC Interface Attributes ...
Страница 230: ...Chapter 8 Congestion Control Automatic Traffic Control 230 ...
Страница 596: ...Chapter 14 Multicast Filtering Multicast VLAN Registration for IPv6 596 ...
Страница 620: ...Chapter 15 IP Configuration Setting the Switch s IP Address IP Version 6 620 ...
Страница 670: ...Chapter 18 Unicast Routing Configuring the Routing Information Protocol 670 Figure 451 Resetting RIP Statistics ...
Страница 672: ...Section III Appendices 672 ...
Страница 678: ...Appendix A Software Specifications Management Information Bases 678 ...
Страница 688: ...Appendix C License Statement GPL Code Statement Notification of Compliance 688 ...
Страница 696: ...Glossary 696 ...
Страница 706: ...GTL 2881 GTL 2882 E112016 ST R01 ...