___________________________________________________________ CAUTION -- READ THIS NOTICE SINGLE-INSTANCE STP ISSUE WHEN MIGRATING FROM 06.6.x to 07.1.x In the HP Procurve 9304M and 9308M Routing Switches May 2001 ___________________________________________________________ CONTENTS Introduction Issue Migration Procedure Caution Regarding Reboots, Reloads, and Changes to the Path Cost or Priority _________________________ INTRODUCTION One of the enhancements in software release 07.1.x for the HP Procurve 9304M and 9308M Routing Switches is support for up to 4,095 port-based VLANs in a single-instance spanning tree environment. This support required a change to the position of the port-based VLAN commands in the running-config and startup-config files. o In software release 06.6.x, the VLAN commands are placed BEFORE the "spanning-tree single" command. o In software release 07.1.x, the VLAN commands are placed AFTER the "spanning-tree single" command. This introduced a software issue that Hewlett-Packard is currently resolving. The following information provides a workaround to the issue prior to the permanent fix becoming available. _________________________ ISSUE As a result of the changed command positions, if you boot a device using software release 07.1.x but also load a startup-config file created using software release 06.6.x, the CLI parser does not find the "spanning-tree single" command before the VLAN commands. The parser therefore assumes that the single-instance STP feature is not enabled. When the device finishes booting, it contains a separate spanning tree for each VLAN on which STP is enabled (multi- instance STP), instead of a single-instance spanning tree consisting of all the VLANs on which STP is enabled. _________________________ MIGRATION PROCEDURE NOTE: You need to use this procedure only if you are upgrading a device from software release 06.6.x to software release 07.1.x and are using single-instance STP. To Migrate Your Single-instance STP Configuration from 06.6.x to 07.1.x: 1. Make a backup copy of the startup-config file. You will need this file if you decide to revert to the 06.6.x release for any reason. a. Make sure the device has IP access to a TFTP server. b. Enter one of the following commands at the Privileged EXEC level of the CLI to copy the device's startup-config file onto the TFTP server: - Copy startup-config tftp - ncopy startup-config tftp 2. Boot the device using software release 07.1.x. 3. Disable single-instance STP by entering the following command at the global CONFIG level of the CLI: no spanning-tree single 4. Enable STP (not single-instance STP) in each of the port-based VLANs that you want to include in the single- instance spanning tree. When you re-enable single- instance STP, all the VLANs in which you enabled STP will become members of the single-instance spanning tree. Other VLANs (in which STP is disabled) will not become part of the single-instance spanning tree. To enable STP in a VLAN a. Enter the following command at the global CONFIG level of the CLI to go to the configuration level of the CLI for that VLAN: vlan b. At the configuration level for the selected VLAN enter this command: spanning-tree 5. Enable single-instance STP. To do so, enter the "exit" command to return to the global CONFIG level of the CLI, then enter this command: spanning-tree single 6. Save the configuration. You cannot use the configuration file you saved using 06.6.x on a device running 07.1.x. 7. Reload the 07.1.x software. NOTE: When you reload, use the startup-config file you saved in Step 6. If you try to use a startup-config file saved while running 06.6.x, the single-instance STP configuration will not be loaded. _________________________ CAUTION REGARDING REBOOTS, RELOADS, AND CHANGES TO THE PATH COST OR PRIORITY After completing the migration steps described above, if you want to change the path cost or priority for an interface, do so only in the running-config by executing a command similar to the one shown below. HOWEVER, DO NOT USE THE "write memory" COMMAND, OR REBOOT OR RELOAD THE ROUTING SWITCH, BECAUSE DOING SO WILL CAUSE SEVERE NETWORK PROBLEMS. For example, suppose that for port 1 in slot 1 you want to change the path cost to "1" and the priority to "32". In this case, you would execute the following in the CLI: spanning-tree single eth 1/1 path-cost 1 priority 32 Entering the above command changes the path cost and priority in the running-config. However, due to other aspects of the STP issue in release 07.1.x, REBOOTING OR RELOADING THE ROUTING SWITCH WITH PATH COST AND PRIORITY SETTINGS MODIFIED IN THE STARTUP-CONFIG AFTER DOING THE ABOVE SOFTWARE MIGRATION RESULTS IN A LOSS OF PATH-COST/PRIORITY DATA, WHICH CAN CAUSE SEVERE NETWORK PROBLEMS. Hewlett-Packard is resolving the above issues in the next 7.1.x software release. This new release will be numbered HIGHER THAN 07.1.22. Please visit the "software" area of the HP Procurve website periodically (at http://www.hp.com/go/hpprocurve) to check for this new release. (c) Copyright Hewlett-Packard Company 2001. All rights reserved.