144
Configuration and Image
User Guidelines
•
The location of a file system dictates the format of the source or destination URL.
•
The entire copying process may take several minutes and differs from protocol to protocol and
from network to network.
When the IPv6 address is a Link Local address (IPv6Z address), the outgoing interface name must be
specified. Refer to the usage guidelines for the interface name syntax.
The IPv6Z address format: <
ipv6-link-local-address
>%<
interface-name
>
–
interface-name
—
vlan
<
integer
> |
ch
<
integer
> |
isatap
<
integer
> | <
physical-port-name
> | 0
–
integer
— <
decimal-number
> | <
integer
><
decimal-number
>
–
decimal-number
— 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
–
physical-port-name
— Designated port number, for example g1.
If the egress interface is not specified, the default interface is selected. Specifying interface zone=0 is
the same as not defining an egress interface.
Understanding Invalid Combinations of Source and Destination
Some invalid combinations of source and destination exist. Specifically, the following cannot be
copied:
•
If the source file and destination file are the same file.
•
xmodem
cannot be a destination.
Can only be copied to
image
,
boot
and
null
.
•
tftp
cannot be the source and destination on the same copy.
•
*.prv files can't be copied.
Copy Character Descriptions
:
Copying image file from a Server to Flash Memory
Use the
copy source-url image
command to copy an image file from a server to Flash memory.
Copying boot file from a Server to Flash Memory
Use the
copy source-url boot
command to copy a boot file from a server to Flash memory.
Copying a Configuration File from a Server to the Running Configuration
Character
Description
!
For network transfers, an exclamation point indicates that the copy process is taking place.
Each exclamation point indicates the successful transfer of ten packets (512 bytes each).
.
For network transfers, a period indicates that the copy process timed out. Many periods in
a row typically mean that the copy process may fail.
5400_CLI.book Page 144 Wednesday, December 17, 2008 4:33 PM
Содержание PowerConnect 5424
Страница 114: ...114 Address Table Commands 5400_CLI book Page 114 Wednesday December 17 2008 4 33 PM ...
Страница 178: ...178 Ethernet Configuration Commands 5400_CLI book Page 178 Wednesday December 17 2008 4 33 PM ...
Страница 194: ...194 GVRP Commands 5400_CLI book Page 194 Wednesday December 17 2008 4 33 PM ...
Страница 204: ...204 IGMP Snooping Commands 5400_CLI book Page 204 Wednesday December 17 2008 4 33 PM ...
Страница 252: ...252 Line Commands 5400_CLI book Page 252 Wednesday December 17 2008 4 33 PM ...
Страница 268: ...268 LLDP Commands 5400_CLI book Page 268 Wednesday December 17 2008 4 33 PM ...
Страница 280: ...280 PHY Diagnostics Commands 5400_CLI book Page 280 Wednesday December 17 2008 4 33 PM ...
Страница 288: ...288 Port Monitor Commands 5400_CLI book Page 288 Wednesday December 17 2008 4 33 PM ...
Страница 300: ...300 QoS Commands 5400_CLI book Page 300 Wednesday December 17 2008 4 33 PM ...
Страница 308: ...308 Radius Commands 5400_CLI book Page 308 Wednesday December 17 2008 4 33 PM ...
Страница 326: ...326 RMON Commands 5400_CLI book Page 326 Wednesday December 17 2008 4 33 PM ...
Страница 386: ...386 SSH Commands 5400_CLI book Page 386 Wednesday December 17 2008 4 33 PM ...
Страница 400: ...400 Syslog Commands 5400_CLI book Page 400 Wednesday December 17 2008 4 33 PM ...
Страница 418: ...418 System Management 5400_CLI book Page 418 Wednesday December 17 2008 4 33 PM ...
Страница 432: ...432 TIC Commands 5400_CLI book Page 432 Wednesday December 17 2008 4 33 PM ...
Страница 440: ...440 Tunnel 5400_CLI book Page 440 Wednesday December 17 2008 4 33 PM ...
Страница 476: ...476 Voice VLAN 5400_CLI book Page 476 Wednesday December 17 2008 4 33 PM ...
Страница 490: ...490 Web Server 5400_CLI book Page 490 Wednesday December 17 2008 4 33 PM ...