Allied Telesis AT-9000 User Manual 2

4
AlliedWare Plus™ Version 2.1.2
AT-9000 Layer 2-4 Gigabit Ethernet EcoSwitches
Software Release Notes
Please read this document before you begin to use the management software. The document has the following sections:
“Supported Platforms” on page 1
“Introduction to Upgrading the Switch” on page 2
“Upgrading the AT-9000 Switch to AlliedWare Plus Version 2.1.2 from Version 2.1.1” on
page 3
“Troubleshooting the Upgrade Procedure” on page 6
“Operational Notes” on page 6
“Resolved Issues” on page 7
“Known Issues” on page 8
“Changes to the AlliedWare Plus Command Line User’s Guide” on page 9
“Contacting Allied Telesis” on page 12
Caution:
The software described in this document contains certain cryptographic functionality and its export is restricted by U.S. law. As of this writing, it has been submitted for review as a “retail encryption item” in accordance with the Export Administration Regulations, 15 C.F.R. Part 730­772, promulgated by the U.S. Department of Commerce, and conditionally may be exported in accordance with the pertinent terms of License Exception ENC (described in 15 C.F.R. Part
740.17). In no case may it be exported to Cuba, Iran, Iraq, Libya, North Korea, Sudan, or Syria. If you wish to transfer this software outside the United States or Canada, please contact your local Allied Telesis sales representative for current information on this product’s export status.
Supported Platforms
Version 2.1.2 of the AlliedWare Plus™ Management Software is supported on these switches:
AT-9000/28
AT-9000/28SP
AT-9000/52
This version supports the following SFP modules:
AT-SPTX (Supported only at a speed of 1G.)
PN 613-001447 Rev A 1
AlliedWare Plus Version 2.1.2 Software Release Notes
AT-SPEX
AT-SPSX
AT-SPFX/2
AT-SPFX/15
AT-SPLX10
AT-SPLX40
AT-SPZX/80
AT-SPBD10-13
AT-SPBD10-14
AT-SPFXBD-LC-13
AT-SPFXBD-LC-15
What’s New in Version 2.1.2
The new VLAN stacking feature allows metro Ethernet networks to tag packets with unique
802.1Q headers to create encapsulated connections through the core, for multiple customer edge VLANs.
The web browser interface has been significantly enhanced to allow for more system
monitoring and control.
The command line interface has been enhanced to conform to the Allied Telesis CLI
standard.
The BANNER EXEC, BANNER MOTD, and BANNER LOGIN commands now support
messages with carriage returns.
You may now use the Telnet client from local and Telnet management sessions, whereas
before you could only use it from local management sessions.
The switch now supports digital diagnostic monitoring (DDM) for those SFP modules that
support it. The messages are entered in the event log.
Port descriptions now support up to 80 characters.
Introduction to Upgrading the Switch
You should determine the current version of the management software on the switch before updating it. The current management software will determine the appropriate upgrade process:
If the switch has the AT-S100 Management Software, refer to the AlliedWare Plus Version
2.1.1 Software Release Notes for the upgrade instructions. You may update the unit directly
to AlliedWare Plus version 2.1.2 from the AT-S100 Management Software, and skip AlliedWare Plus version 2.1.1.
If the switch already has AlliedWare Plus, you may upgrade it to version 2.1.2 using either the
command line interface or web browser interface. These software release notes contain the procedure for updating the management software using the command line interface. If you want to use the web browser interface, refer to the AlliedWare Plus Web Browser User’s Guide.
PN 613-001447 Rev A 2 Allied Telesis, Inc.
AlliedWare Plus Version 2.1.2 Software Release Notes
Upgrading the AT-9000 Switch to AlliedWare Plus Version 2.1.2 from Version 2.1.1
This section contains the procedure for upgrading the switch from AlliedWare Plus Version 2.1.1 to version 2.1.2, from the command line. Here are the upgrade requirements:
There must be a TFTP server on your network.
The switch must be assigned an IP address. For instructions, refer to the AT-9000 AlliedWare
Plus User’s Guide.
Caution:
The upgrade process is disruptive to network operations because it resets the switch. The switch does not forward network traffic during the reset.
There are three phases to upgrading the switch:
“Phase 1. Uploading the Active Boot Configuration File to Your TFTP Server” on page 3
“Phase 2: Downloading the New AlliedWare Plus Version 2.1.2 Management Software” on
page 4
“Phase 3: Updating the Commands” on page 4
Phase 1. Uploading the Active Boot Configuration File to Your TFTP Server
Allied Telesis recommends uploading the active boot configuration file from the switch to your TFTP server before updating the management software on the switch. You’ll use the file in phase 3 to check for v2.1.1 commands that are not compatible with v2.1.2. To upload the active boot configuration file:
1. Start the TFTP server on your network.
1. Start a local or remote management session on the switch.
2. When prompted, enter a username and password. The defaults are “manager” for the username and “friend” for the password.
3. Move to the Privileged Exec mode and enter the SHOW BOOT command to display the name of the active boot configuration file:
awplus# show boot
Here is an example of the information.
Current software : v2.1.1 Current boot image : v2.1.1 Backup boot image : Not set Default boot config: /cfg/boot.cfg Current boot config: /cfg/sw2bldg2.cfg (file exists)
The name of the active boot configuration file is displayed in the “Current boot config” line.
4. Use the COPY command to upload the boot configuration file from the switch to the TFTP server. Here is the format of the command:
copy flash tftp
ipaddress filename
.cfg
The IPADDRESS parameter is the IP address of the TFTP server. The FILENAME parameter is the name of the boot configuration file you want to upload from the switch to TFTP server. The filename extension must be “.cfg” for boot configuration files. The filename cannot contain spaces.
PN 613-001447 Rev A 3 Allied Telesis, Inc.
AlliedWare Plus Version 2.1.2 Software Release Notes
This example of the command uploads the boot configuration file “sw2bldg2.cfg to a TFTP server that has the IP address 149.182.34.15:
awplus# copy flash tftp 149.182.34.15 sw2bldg2.cfg
5. Go to Phase 2.
Phase 2: Downloading the New AlliedWare Plus Version 2.1.2 Management Software
To upgrade the switch to AlliedWare Plus Version 2.1.2 from AlliedWare Plus Version 2.1.1:
1. Store the AlliedWare Plus Version 2.1.2 Management Software on the TFTP server on your network.
2. If you have not already started the TFTP server, start it now.
3. If you have not already started a local or remote management session on the switch, start a session now.
4. Use the ENABLE command to move to the Privileged Executive mode.
awplus> enable awplus#
5. Use the COPY command to download the AlliedWare Plus Version 2.1.2 Management Software from the TFTP server to the switch. Here is the format of the command:
copy tftp flash
ipaddress filename
The IPADDRESS parameter specifies the IP address of the TFTP server on your network. The FILENAME parameter specifies the filename of the AlliedWare Plus Version 2.1.2 Management Software stored on the TFTP server. The extension must include the “.img” extension. The name cannot contain spaces or special characters.
In this example, the IP address of the TFTP server is 149.157.18.78 and the name of the management software file is “ats-9000-2.1.2.img:”
awplus# copy tftp flash 149.157.18.78 ats-9000-2.1.2.img
After receiving the file from the TFTP server, the switch writes it to flash memory and resets. The entire process takes several minutes. The switch is running the new software after it completes the reset.
6. Establish a new management session with the switch.
7. Enter the Privileged Exec mode and enter the WRITE command to same the configuration.
awplus> enable awplus# write
8. Go to Phase 3.
Phase 3: Updating the Commands
A few commands have changed from v2.1.1 to v2.1.2. If the switch encountered any of these commands in its boot configuration file when it reset, it skipped over them to remove them from its running configuration. To complete the upgrade procedure, you should print out the boot configuration file you uploaded to your TFTP server in Phase 1, and examine it for any of the modified commands. The modified commands are described here:
BANNER EXEC and BANNER MOTD Commands - The formats of these commands, which
are used to create the User Exec and Privileged Exec modes banner and message-of-the­day banner, have changed in v2.1.2. Where before a command and its banner message were included on the same line, they are now entered separately. The new formats are:
banner exec
banner motd
PN 613-001447 Rev A 4 Allied Telesis, Inc.
Loading...
+ 8 hidden pages