Owner manual
Table Of Contents
- Contents
- Tables
- Preface
- Section I
- Basic Operations
- Chapter 1
- Starting a Command Line Management Session
- Chapter 2
- Basic Command Line Commands
- Chapter 3
- Basic Switch Commands
- DISABLE DHCPBOOTP
- DISABLE IP REMOTEASSIGN
- DISABLE TELNET
- ENABLE BOOTP
- ENABLE DHCP
- ENABLE IP REMOTEASSIGN
- ENABLE TELNET
- PING
- PURGE IP
- RESET SWITCH
- RESET SYSTEM
- RESTART REBOOT
- RESTART SWITCH
- SET ASYN
- SET IP INTERFACE
- SET IP ROUTE
- SET PASSWORD MANAGER
- SET PASSWORD OPERATOR
- SET SWITCH CONSOLETIMER
- SET SYSTEM
- SET TELNET INSERTNULL
- SET USER PASSWORD
- SHOW ASYN
- SHOW CONFIG DYNAMIC
- SHOW CONFIG INFO
- SHOW DHCPBOOTP
- SHOW IP INTERFACE
- SHOW IP ROUTE
- SHOW SWITCH
- SHOW SYSTEM
- Chapter 4
- Enhanced Stacking Commands
- Chapter 5
- Simple Network Time Protocol (SNTP) Commands
- Chapter 6
- SNMPv2 and SNMPv2c Commands
- Chapter 7
- Port Parameter Commands
- Chapter 8
- Port Statistics Commands
- Chapter 9
- MAC Address Table Commands
- Chapter 10
- Static Port Trunking Commands
- Chapter 11
- LACP Port Trunking Commands
- Chapter 12
- Port Mirroring Commands
- Chapter 13
- Networking Stack
- Section II
- Advanced Operations
- Chapter 14
- File System Commands
- Chapter 15
- File Download and Upload Commands
- Chapter 16
- Event Log and Syslog Server Commands
- Chapter 17
- Classifier Commands
- Chapter 18
- Access Control List Commands
- Chapter 19
- Class of Service (CoS) Commands
- Chapter 20
- Quality of Service (QoS) Commands
- ADD QOS FLOWGROUP
- ADD QOS POLICY
- ADD QOS TRAFFICCLASS
- CREATE QOS FLOWGROUP
- CREATE QOS POLICY
- CREATE QOS TRAFFICCLASS
- DELETE QOS FLOWGROUP
- DELETE QOS POLICY
- DELETE QOS TRAFFICCLASS
- DESTROY QOS FLOWGROUP
- DESTROY QOS POLICY
- DESTROY QOS TRAFFICCLASS
- PURGE QOS
- SET QOS FLOWGROUP
- SET QOS POLICY
- SET QOS PORT
- SET QOS TRAFFICCLASS
- SHOW QOS FLOWGROUP
- SHOW QOS POLICY
- SHOW QOS TRAFFICCLASS
- Chapter 21
- Denial of Service Defense Commands
- Section III
- IGMP Snooping, MLD Snooping, and RRP Snooping
- Chapter 22
- IGMP Snooping Commands
- Chapter 23
- MLD Snooping Commands
- Chapter 24
- RRP Snooping Commands
- Section IV
- SNMPv3
- Chapter 25
- SNMPv3 Commands
- ADD SNMPV3 USER
- CLEAR SNMPV3 ACCESS
- CLEAR SNMPV3 COMMUNITY
- CLEAR SNMPV3 NOTIFY
- CLEAR SNMPV3 TARGETADDR
- CLEAR SNMPV3 VIEW
- CREATE SNMPV3 ACCESS
- CREATE SNMPV3 COMMUNITY
- CREATE SNMPV3 GROUP
- CREATE SNMPV3 NOTIFY
- CREATE SNMPV3 TARGETADDR
- CREATE SNMPV3 TARGETPARAMS
- CREATE SNMPV3 VIEW
- DELETE SNMPV3 USER
- DESTROY SNMPv3 ACCESS
- DESTROY SNMPv3 COMMUNITY
- DESTROY SNMPv3 GROUP
- DESTROY SNMPv3 NOTIFY
- DESTROY SNMPv3 TARGETADDR
- DESTROY SNMPv3 TARGETPARMS
- DESTROY SNMPV3 VIEW
- PURGE SNMPV3 ACCESS
- PURGE SNMPV3 COMMUNITY
- PURGE SNMPV3 NOTIFY
- PURGE SNMPV3 TARGETADDR
- PURGE SNMPV3 VIEW
- SET SNMPV3 ACCESS
- SET SNMPV3 COMMUNITY
- SET SNMPV3 GROUP
- SET SNMPV3 NOTIFY
- SET SNMPV3 TARGETADDR
- SET SNMPV3 TARGETPARAMS
- SET SNMPV3 USER
- SET SNMPV3 VIEW
- SHOW SNMPV3 ACCESS
- SHOW SNMPV3 COMMUNITY
- SHOW SNMPv3 GROUP
- SHOW SNMPV3 NOTIFY
- SHOW SNMPV3 TARGETADDR
- SHOW SNMPV3 TARGETPARAMS
- SHOW SNMPV3 USER
- SHOW SNMPV3 VIEW
- Section V
- Spanning Tree Protocols
- Chapter 26
- Spanning Tree Protocol Commands
- Chapter 27
- Rapid Spanning Tree Protocols Commands
- Chapter 28
- Multiple Spanning Tree Protocol Commands
- Section VI
- Virtual LANs
- Chapter 29
- Port-based, Tagged, and Multiple Mode VLAN Commands
- Chapter 30
- GARP VLAN Registration Protocol Commands
- Chapter 31
- Protected Ports VLAN Commands
- Chapter 32
- MAC Address-based VLAN Commands
- Section VII
- Port Security
- Chapter 33
- MAC Address-based Port Security Commands
- Chapter 34
- 802.1x Port-based Network Access Control Commands
- Section VIII
- Management Security
- Chapter 35
- Web Server Commands
- Chapter 36
- Encryption Key Commands
- Chapter 37
- Public Key Infrastructure (PKI) Certificate Commands
- Chapter 38
- Secure Sockets Layer (SSL) Commands
- Chapter 39
- Secure Shell (SSH) Commands
- Chapter 40
- TACACS+ and RADIUS Commands
- Chapter 41
- Management ACL Commands
- Index
Chapter 15: File Download and Upload Commands
240 Section II: Advanced Operations
When uploading the master switch’s active AT-S63 image file to
another switch, the file is copied directly to the application block on the
other switch, automatically making it the active image file. It is not
copied to the file system. This results in a switch reset of the unit that
receives the image file. Some network traffic may be lost while the
switch reloads its operating software.
After the upload of a configuration file is complete, the switch that
received the configuration file marks it as the its active boot
configuration file and automatically resets. Some network traffic may
be lost while the switch reloads its operating software. After the reset is
complete, the switch operates with the parameter settings contained in
the uploaded configuration file.
When uploading a configuration file, the command syntax gives you
the choice of downloading the master switch’s current boot
configuration file or another configuration file in the switch’s file
system. To select the switch’s current configuration file, use the
SWITCHCFG option of the SRCFILE or FILE parameter. To upload
another configuration file, omit the SWITCHCFG option and instead
specify the file’s name.
If you use the SWITCHCFG option to upload the switch’s current boot
configuration file, the following information in the file is not included in
the transfer: IP address, subnet mask, gateway address, switch name,
contact, location, and the master mode setting. However, the switch
receiving the configuration file does not retain its current settings to
these parameters. Rather, they are returned to their default values.
If you choose to upload a configuration file from the master switch’s file
system by specifying its filename, the entire file without modification is
uploaded. This type of configuration file upload should be performed
with care. If you upload a configuration file that contains a manually
assigned IP address onto more than one switch, the switches will have
the same IP address.
A configuration file should only be uploaded onto a switch of the same
model from which the configuration file originated (for example,
AT-9408LC/SP to AT-9408LC/SP). Allied Telesyn does not
recommend uploading a configuration file onto a switch of a different
model (for example, AT-9408LC/SP to AT-9424T/SP). Undesirable
switch behavior may result.
Unlike some of the other LOAD and UPLOAD commands that support
copying files to and from a compact flash memory card, this command
does not. The configuration file most be stored in the master switch’s
file system and not on a compact flash memory card.