Advertisement
Upgrading from the 2.00.48 release to the 2.01.20 release requires some additional steps for users who utilize
GVRP. When upgrading to the 2.01.20 image, the user should only reconfigure GVRP on inter-switch links (ISLs).
GVRP was enabled by default in the 2.00.48 image on all edge ports; only non-default commands are displayed
in the config, so only the set GVRP disable commands would be listed in a config file created in a 2.00.48 image.
In the 2.01.20 image, the situation is the opposite. Any ―GVRP disable‖ commands are ignored. For any ports on
which the user wants GVRP ―enabled‖, the user must log back in and reconfigure those ports to ―enable‖. Any
ports which the user wants to be ―disabled‖ will require no action.
Configuration files that were created in the 1.xx.xx track can be applied to a switch/stack using the 2.xx.xx track,
however the steps defined above for configuring GVRP must be observed.
Upgrading from 2.xx.xx to 3.xx.xx
Release 3 contains an improved method of stack communications which resolves some stack related issues seen
in unusual circumstances with Release 1 and Release 2 code. This new communication is not compatible with the
methods used in Release 1 and Release 2 code. Therefore, when upgrading the stack to Release 3, it is
important that you ensure the new code has been successfully downloaded to all members of the stack before
issuing a stack reset (which will cause the stack to begin using the just downloaded code). If all members are not
successfully updated before issuing a reset, units not updated will need to be removed from the stack and
upgraded individually.
To upgrade to Release 3, it is highly recommended that you first upgrade to the latest Release 2 code (02.01.37)
as detailed above. This release contains additional safeguards that check that proper code versions exist on all
members of a stack.
To upgrade from a 2.xx.xx version to a 3.xx.xx version follow the steps below:
1. At switch prompt, execute the ―dir‖ command. This will display the file names of the images existing on
device.
2. If running version 2.01.37 and a backup image exists, use the ―delete <file name>‖ command to remove
the backup image.
Use the ―copy tftp://<tftp server IP>/<path>/<image name> system:image‖ command to download the new
Release 3 image. This image is downloaded, sent to all stack members, and marked as a ―backup‖ code
image. If this download to any of the stack members is unsuccessful, an error message should be
generated.
3. Issue the ―show version‖ command to verify that the new Release 3 code image exists on all stack
members as the ―backup‖ image. If not, you should manually push this code to any stack member that is
not properly updated using the ―set switch copy-fw‖ command.
4. Once all stack members contain the new software image, use the ―set boot system <image name>‖
command to set the newly downloaded image as the ―active‖ image.
5. Stack will reboot using the updated code.
If you have a unit that is running Release 2 or older software, and you want to use the unit in a stack running
Release 3 software, you must boot the unit as a standalone unit and update its code to Release 3 before cabling
it into the existing stack.
Router Capacities
The following table defines the router capacities:
Feature
ARP Dynamic
ARP Static
Route Table
OSPF Areas
08/13/2008 P/N: 9038155-52
F0615-O
Capacity
Subject to Change Without Notice
CUSTOMER RELEASE NOTES
2024
512
2500
4
Page: 5 of 41
Advertisement
