Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

Part No. 321327-B June 2006 4655 Great America Parkway Santa Clara, CA 95054 Upgrading to Ethernet Routing Switch 1600 Software Release 2.1 *321327-...
Author: Shon Page
27 downloads 0 Views 463KB Size
Part No. 321327-B June 2006 4655 Great America Parkway Santa Clara, CA 95054

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

*321327-B*

2

Copyright © Nortel Networks 2005 - 2006. All rights reserved. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of that license. The software license agreement is included in this document.

Trademarks Nortel, Nortel Networks, the Nortel logo and the Globemark are trademarks of Nortel Networks. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated. Java is a trademark of Sun Microsystems, Inc. The asterisk after a name denotes a trademarked item.

Restricted rights legend Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of conditions In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the right to make changes to the products described in this document without notice. Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein. Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission. SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).

321327-B

3

Nortel Networks software license agreement This Software License Agreement (“License Agreement”) is between you, the end-user (“Customer”) and Nortel Networks Corporation and its subsidiaries and affiliates (“Nortel Networks”). PLEASE READ THE FOLLOWING CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT. If you do not accept these terms and conditions, return the Software, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price. “Software” is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and is copyrighted and licensed, not sold. Software consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole or partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired the Software. You obtain no rights other than those granted to you under this License Agreement. You are responsible for the selection of the Software and for the installation of, use of, and results obtained from the Software. 1. Licensed Use of Software. Nortel Networks grants Customer a nonexclusive license to use a copy of the Software on only one machine at any one time or to the extent of the activation or authorized usage level, whichever is applicable. To the extent Software is furnished for use with designated hardware or Customer furnished equipment (“CFE”), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable. Software contains trade secrets and Customer agrees to treat Software as confidential information using the same care and discretion Customer uses with its own similar information that it does not wish to disclose, publish or disseminate. Customer will ensure that anyone who uses the Software does so only in compliance with the terms of this Agreement. Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly authorized; b) reverse assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneficiaries of this provision. Upon termination or breach of the license by Customer or in the event designated hardware or CFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction. Nortel Networks may audit by remote polling or other reasonable means to determine Customer’s Software activation or usage levels. If suppliers of third party software included in Software require Nortel Networks to include additional or different terms, Customer agrees to abide by such terms provided by Nortel Networks with respect to such third party software. 2. Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer, Software is provided “AS IS” without any warranties (conditions) of any kind. NORTEL NETWORKS DISCLAIMS ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligated to provide support of any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties, and, in such event, the above exclusions may not apply. 3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS OF, OR DAMAGE TO, CUSTOMER’S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN ADVISED OF THEIR POSSIBILITY. The for egoing limitations of remedies also apply to any developer and/or supplier of the Software. Such developer and/or supplier is an intended beneficiary of this Section. Some jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply. 4.

General a.

If Customer is the United States Government, the following paragraph shall apply: All Nortel Networks Software available under this License Agreement is commercial computer software and commercial computer software documentation and, in the event Software is licensed for or on behalf of the United States

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

4 Government, the respective rights to the software and software documentation are governed by Nortel Networks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections 12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities). b.

Customer may terminate the license at any time. Nortel Networks may terminate the license if Customer fails to comply with the terms and conditions of this license. In either event, upon termination, Customer must either return the Software to Nortel Networks or certify its destruction.

c.

Customer is responsible for payment of any taxes, including personal property taxes, resulting from Customer’s use of the Software. Customer agrees to comply with all applicable laws including all applicable export and import laws and regulations.

d.

Neither party may bring an action, regardless of form, more than two years after the cause of the action arose.

e.

The terms and conditions of this License Agreement form the complete and exclusive agreement between Customer and Nortel Networks.

f.

This License Agreement is governed by the laws of the country in which Customer acquires the Software. If the Software is acquired in the United States, then this License Agreement is governed by the laws of the state of New York.

321327-B

Contents 5

Contents Chapter 1: Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Software Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Flash File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Before Upgrading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Console Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 TFTP Server Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Case 4 Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Software Release 1.x to 2.1 Automatic Upgrade Procedure . . . . . . . . . . . . . . . . . . . . 14 Software Release 1.x to 2.1 Manual Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . 22 Software Release 2.x Upgrade Procedure using the CLI . . . . . . . . . . . . . . . . . . . . . . 27 Software Release 2.x Upgrade Procedure using the JDM . . . . . . . . . . . . . . . . . . . . . . 32 Software Release 2.1 to 1.x Downgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Default User Names and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 2: Calculating MD5 digest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Appendix A: CLI commands that require translation . . . . . . . . . . . . . . . . . 45 Commands that require manual translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Commands that translate with limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

6

Contents

321327-B

Chapter 1 Upgrade Procedures 7

Chapter 1 Upgrade Procedures This document describes the procedures necessary for upgrading the software of a Nortel Ethernet Routing Switch 1600 Series. The 1600 Series switch supports the Ethernet Routing Switch 1600 Series Command Line Interface (CLI) mode. This document contains the following topics: • • • • • • • • • • • •

“Software Filenames” on page 8 “Flash File System” on page 9 “Before Upgrading the Software” on page 10 “Console Port Settings” on page 10 “TFTP Server Network Topology” on page 11 “Software Release 1.x to 2.1 Automatic Upgrade Procedure” on page 14 “Software Release 1.x to 2.1 Manual Upgrade Procedure” on page 22 “Software Release 2.x Upgrade Procedure using the CLI” on page 27 “Software Release 2.x Upgrade Procedure using the JDM” on page 32 “Software Release 2.1 to 1.x Downgrade Procedure” on page 37 “Default User Names and Passwords” on page 39 “Related Documentation” on page 40

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

8 Chapter 1 Upgrade Procedures

Software Filenames Table 1 describes the Ethernet Routing Switch 1600 Software Release 2.1 files and the hardware they support. Note: The software file names depicted in Table 1 are indicative of the final versions of these files. During the Beta trial period, files are often appended with a build number to differentiate them from earlier builds. This is usually represented by appended a b and a build number (such as b022) to the end of the file name.

Table 1 Release 2.1 software files and associated hardware Module or file type

Filename

Pre-boot Monitor Software (1.x to 2.1 upgrade)

p16b2100.had

Conversion program image

p16a1310.img

Encryption-enabled Conversion program image

p16c1310.img

Run-time image

p16a2100.img

Boot Monitor Software

p16b2100.img

3DES SSH Encryption Module

p16c2100.img

DES SNMPv3 Encryption Module

p16c2100.des

MIB zip file

p16a2100_mib.zip

Java Device Manager (Device Manager) software jdm_600.exe image

To upgrade from Software Release 1.x to 2.1, the following files are required: • • • •

p16b2100.had p16a1310.img or p16c1310.img p16a2100.img p16b2100.img

These files are accessible through Nortel Support Portal at http://www.nortel.com/ support.

321327-B

Chapter 1 Upgrade Procedures 9

Flash File System The Ethernet Routing Switch 1600 Series boot and operational files are contained in the onboard flash memory. This section outlines the switch flash file system. Each 1600 Series switch has two onboard flash memory devices: •



The first flash memory device is used to store the pre-boot monitor software image. This device is 500 kilobytes (kb) in size and is not directly accessible. It is updated when a new pre-boot monitor software image is installed on the switch. The second flash memory device is 16 megabytes (MB) is size and is partioned into two sections: • The boot flash memory is 2 megabytes (MB) and contains the boot-monitor image file. The boot-monitor image is not directly accessible. It is updated using a special boot-monitor update mechanism that writes to the reserved area. • The system flash memory is 14 MB and is used to store the switch runtime images, configuration files, system log, and other general storage.

Prior to Software Release 2.1, the Ethernet Routing Switch 1600 Series file system was not directly accessible. Software Release 2.1 introduces the ability to access this file system. The switch file system now supports long filename conventions similar to those found in the Microsoft* Windows* family of operating systems. Files stored in the system flash in Software Release 2.1 are always found in the /flash directory. To verify the contents of the system flash device in Software Release 2.1, do either of the following: • •

In the Command Line Interface use the dir or ls commands. In the Device Manager: • Select Edit > File System from the menu. • Select the Flash Files tab from the FileSystem screen. The current contents of the system flash device are displayed.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

10 Chapter 1 Upgrade Procedures

Before Upgrading the Software Before upgrading to Ethernet Routing Switch 1600 Software Release 2.1, do the following: •



Read the entire upgrade procedure before attempting to upgrade the software on the switch. The upgrade procedure causes interruption of normal switch operation. Take special note of the following cautionary messages: — The configuration file generated by Software Release 2.1 contains options that are not backward-compatible with software release 1.x. Loading a 2.1 configuration file on a 1.x run-time image generates errors and causes the image to abort loading the configuration file. — Be aware that if there is a failure in connectivity to the TFTP server, the file on the system flash is deleted if it has the same name as a file that is being copied to switch through TFTP. If the server is not available, or if the file on the server does not exist, the p16a2100.img file is deleted on the flash (if previously existing). To preserve the original file, either rename the file or make a backup copy on the flash before beginning the copying process.

Console Port Settings Throughout the various upgrade procedures presented in this book, the console port is one of the options for connecting to the switch. Unless otherwise noted in the procedure, ensure that any terminal emulation software used to connect to the console port uses the settings outlined in Table 2. Table 2 Default Console Port Settings

321327-B

Value

Setting

Baud Rate

9600

Data Bits

8

Parity

None

Stop Bits

1

Flow Control

None

Chapter 1 Upgrade Procedures 11

TFTP Server Network Topology The upgrade procedures described in the book make extensive use of TFTP servers to upload and download files to and from the switch. Figure 1 illustrates the network topologies where connection to a TFTP server is and isn’t possible. Figure 1 TFTP Network Topologies

Before attempting any of the upgrade procedures, ensure that the TFTP server that will be used conforms to a network topology that will allow for a successful upgrade.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

12 Chapter 1 Upgrade Procedures

Case 4 in Figure 1 on page 11 illustrates a special case where an automatic upgrade could be possible with additional configuration. Refer to “Case 4 Additional Configuration” for the additional steps necessary.

Case 4 Additional Configuration Case 4 in Figure 1 on page 11 illustrates a network topology where an Ethernet Routing Switch 1612 or 1624 connects to a TFTP server from an out-of-band port but the TFTP server exists on a remote subnet and is accessed through a router. In this instance an automatic upgrade is possible with additional switch configuration. For the purposes of this explanation, assume the following network layout applies to the network devices in Case 4: • • •

Ethernet Routing Switch 1612 or 1624 out-of-band IP address is 100.1.1.2/16 TFTP Server IP address is 192.168.1.135/24 The Router gateway to the TFTP Server is 192.168.1.1/24 and the Router gateway to the Ethernet Routing Switch 1612 or 1624 is 100.1.1.1/16

To enable an automatic upgrade in this instance, complete these tasks: 1

Complete steps 1 and 2 of the procedure outlined in “Software Release 1.x to 2.1 Automatic Upgrade Procedure” on page 14.

2

Before proceeding with step 3 of the upload configuration procedure, create a static route that will enable the switch to communicate with the TFTP Server. This is accomplished with the create iproute command. This command has the following syntax: create iproute

Following the assumptions outlined above, the command issued for this example would be: create iproute 192.168.1.0/24 100.1.1.1 The create iproute command will create a static route entry in the routing table.

321327-B

Chapter 1 Upgrade Procedures 13

Use the show iproute static command to confirm the change to the routing table. Following the example assumptions outlined, the routing table for the switch in Case 4 would look like this: IP Address/Netmask Gateway Cost Protocol ------------------ --------------- -------- -------192.168.1.0/24 100.1.1.1 1 Static

3

Proceed with the remainder of the automatic upgrade procedure.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

14 Chapter 1 Upgrade Procedures

Software Release 1.x to 2.1 Automatic Upgrade Procedure Caution: Prior to starting the upgrade, refer to “Software Filenames” on page 8 for the correct software versions used in this process.

This section outlines the procedure necessary to upgrade from Software Release 1.x to Software Release 2.1. Note: The switch can be downgraded to Software Release 1.x after an upgrade to Software Release 2.1 has been performed. Refer to “Software Release 2.1 to 1.x Downgrade Procedure” on page 37 for this downgrade procedure. To upgrade the switch to Software Release 2.1, follow this procedure: Note: Throughout this procedure command syntax will be presented in this font. Where applicable, commands will be followed by an example presented in this font. 1

Copy the upgrade files to the TFTP server that will be used during the upgrade procedure (Refer to “TFTP Server Network Topology” on page 11 for network topologies that will support TFTP server connection). These files are listed in “Software Filenames” on page 8 and can be acquired from the Nortel Support Portal at http://www.nortel.com/support.

2

Connect to the switch using the console port and terminal emulation software or connect to the switch through Telnet. Refer to “Console Port Settings” on page 10 for console port connection parameters.

3

Save the existing switch configuration to a TFTP server. This will serve as a backup should switch configuration not be completed successfully or a downgrade to Software Release 1.x is required. upload configuration

upload configuration 192.168.249.230 pre_upgrade_configuration.txt

321327-B

Chapter 1 Upgrade Procedures 15

4

Download the conversion program to the switch. This conversion program will temporarily upgrade the switch to an intermediary software release (Software Release 1.3) and prepare it for a final upgrade to Software Release 2.1. Refer to “Software Filenames” on page 8 for the appropriate filename. download firmware

download firmware 192.168.249.230 p16a1310.img Note: During this step the conversion program will be downloaded to the switch and upgrade the switch to the intermediary software release. Do not interrupt the switch during this process. When this process is completed the switch will be running Software Release 1.3. If the upgrade procedure is being performed through a telnet session, connectivity to the switch will be lost when the switch reboots with the new software image. Reconnect to the switch and log in to ensure that upgrade has been successful. 5

Download the new pre-boot monitor software to the switch. This new pre-boot monitor software will upgrade the switch to a new bootrom which supports SMLT failover features. Caution: Do not power cycle the switch during the remainder of this procedure except when instructed. Power cycling the switch during this step can cause irreversible damage to the pre-boot monitor software and switch. download prom

download prom 192.168.249.230 p16b2100.had

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

16 Chapter 1 Upgrade Procedures

6

Specify the parameters that will be used to upgrade the switch to Software Release 2.1. Execute the following commands to set these parameters: Caution: It is important that the System IP address is NOT modified while the switch is running Software Release 1.3. Modification of the System IP address while running Software Release 1.3 will prevent the software upgrade from proceeding successfully. Software Release 1.3 is only meant to provide an intermediary software base to facilitate the upgrade to Software Release 2.1. The only configuration modifications that should take place are those done with the config upgrade commands outlined in this step. a

config upgrade image_file

The config upgrade image_file command is used to specify the image file that will be used to upgrade the switch to Software Release 2.1. This command has the following syntax: config upgrade image_file

config upgrade image_file p16a2100.img b

config upgrade tftp_server

The config upgrade tftp_server command is used to specify the TFTP server that contains the software image that will be used to upgrade the switch to Software Release 2.1. This command has the following syntax: config upgrade tftp_server

config upgrade tftp_server 192.168.249.230

Note: If the TFTP server specified by this command is unreachable during the upgrade process the process will fail. Ensure that the TFTP server is running and reachable by the switch. If the TFTP server is reachable, the software will notify the user and also warn the user that if the server is unreachable the upgrade will fail.

321327-B

Chapter 1 Upgrade Procedures 17

c

config upgrade net_mgmt_ip

Note: This step is necessary for the Ethernet Routing Switch 1648 only.

The config upgrade net_mgmt_ip command is used to specify the management IP address of the switch. This command has the following syntax: config upgrade net_mgmt_ip

config upgrade net_mgmt_ip 192.168.0.13/24 The following conditions apply to the IP interface used in this command: — The IP interface specified in this command must be an existing IP interface. A new IP interface cannot be configured using this command. — The IP interface specified in this command must be routable to the TFTP server used in the upgrade procedure. Note: The subnet mask can be specifed using either full mask notation (i.e.: 255.255.255.0) or a Variable Length Subnet Mask (VLSM) d

config upgrade mgmt_port

Note: This step is necessary for the Ethernet Routing Switch 1648 only.

The config upgrade mgmt_port command is used to configure the switch management port. config upgrade mgmt_port

config upgrade mgmt_port 48 7

Save the current configuration using the Save command. The current switch configuration will be translated into a format that can be used by Software Release 2.1. After this process has completed the message You are safe to upgrade firmware 2.x will be displayed. Save Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

18 Chapter 1 Upgrade Procedures

8

Backup the new Software Release 2.1-compatible configuration to the TFTP server. upload translated_conf

upload translated_conf 192.168.249.230 translated_configuration.txt 9

Download the new bootflash to the switch. During this process, a new boot monitor image will be downloaded to the switch, installed, and the flash system formatted with DOS-FS. This process takes a considerable amount of time and under no circumstances should the switch be reset. After the successful completion of this process, the switch will reboot and the Software Release 2.1 runtime image will be downloaded using the parameters specified in step 5. Do not interupt the switch during this process. download firmware p16b2100.img

download firmware 192.168.249.230 p16b2100.img 10 Log into the upgraded switch. If this upgrade is being performed remotely, reconnect the telnet session and log into the switch. 11 Save the current configuration and boot configuration settings on the switch. save config save bootconfig Note: The boot configuration file boot.cfg has been introduced to the Ethernet Routing Switch 1600 Series in Software Release 2.1. The conversion program will automatically convert and save the 1.x configuration to this new file. To completely remove those boot settings from the runtime configuration file config.cfg, and to ensure the settings have been saved into boot.cfg, users must use both the save config and save bootconfig commands to finalize the conversion process. 12 Verify that the switch configuration has been successfully converted. show config

321327-B

Chapter 1 Upgrade Procedures 19

13 Copy the runtime image to the system flash. Note: This step is only necessary if the switch will boot from the system flash later. If the switch will always boot from another device, such as the TFTP server specified during the upgrade process, disregard this step. Copy the Software Release 2.1 software image to the system flash. copy :

copy 192.168.249.230:p16a2100.img /flash/p16a2100.img 14 Set the switch boot locations. The Ethernet Routing Switch 1600 Series allows for up to three boot locations (primary, secondary, tertiary) per switch. The boot location specifies where the switch will look for the software image file after a successful boot. Perform the following tasks to complete this step: a

Set the primary boot location. config bootconfig choice primary image-file

The parameter can specify either a file resident in the system flash or resident on a TFTP server. To indicate a file resident in the system flash, enter /flash/ followed by the file name. The following command example would be used to specify a switch whose primary boot location is the system flash: config bootconfig choice primary image-file /flash/p16a2100.img To indicate a file resident on a TFTP server, enter the IP address of the TFTP server followed by a colon and then the name of the file. The following command example would be used to specify a switch whose primary boot location is a TFTP server: config bootconfig choice primary image-file 192.168.249.230:p16a2100.img

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

20 Chapter 1 Upgrade Procedures

b

Set secondary and tertiary boot locations. Setting secondary and tertiary locations are not mandatory but should be specified as a best practice. Table 3 lists the options available when specifying boot locations. Up to three boot locations (primary, secondary, tertiary) can be specified.

Table 3 Boot Location Options Boot Location

Command Options

Primary

config bootconfig choice backup-config-file primary config-file

config bootconfig choice backup-config-file secondary config-file

config bootconfig choice backup-config-file tertiary config-file

Seconday

Tertiary

primary image-file

secondary image-file

tertiary image-file

These commands change the entries in the switch boot configuration file (boot.cfg). Optionally, a copy of the boot configuration file could be uploaded to a TFTP server, manipulated with a text editor, and downloaded to the switch.

321327-B

Chapter 1 Upgrade Procedures 21

15 Save the current configuration and boot configuration settings on the switch and verify those settings. save config save bootconfig show bootconfig choice

Note: The 3DES SSH Encryption Module and DES SNMPv3 Encryption Module are optional file uploads but are dependent upon each other. To use SNMPv3 both modules (p16c2100.img and p16c2100.des) must be present on the switch. Please note that the automatic upgrade procedure does NOT load either file to flash memory. To use these files they will have to be manually uploaded to the switch and switch reconfiguration may be necessary.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

22 Chapter 1 Upgrade Procedures

Software Release 1.x to 2.1 Manual Upgrade Procedure Caution: This manual upgrade procedure is provided only as an emergency alternative to the “Software Release 1.x to 2.1 Automatic Upgrade Procedure” on page 14. Should the automatic upgrade procedure fail, or not be possible because of network topology issues, use this procedure instead.

Caution: Prior to starting the upgrade, refer to “Software Filenames” on page 8 for the correct software versions used in this process.

This section outlines the procedure necessary to upgrade from Software Release 1.x to Software Release 2.1. Note: The switch can be downgraded to Software Release 1.x after an upgrade to Software Release 2.1 has been performed. Refer to “Software Release 2.1 to 1.x Downgrade Procedure” on page 37 for this downgrade procedure. To upgrade the switch to Software Release 2.1, follow this procedure: Note: Throughout this procedure command syntax will be presented in this font. Where applicable, commands will be followed by an example presented in this font.

321327-B

1

Copy the upgrade files to the TFTP server that will be used during the upgrade procedure (Refer to “TFTP Server Network Topology” on page 11 for network topologies that will support TFTP server connection). These files are listed in “Software Filenames” on page 8 and can be acquired from the Nortel Support Portal at http://www.nortel.com/support.

2

Connect to the switch using the console port and terminal emulation software. Refer to “Console Port Settings” on page 10 for console port connection parameters.

Chapter 1 Upgrade Procedures 23

3

Save the existing switch configuration to a TFTP server. This will serve as a backup should switch configuration not be completed successfully or a downgrade to Software Release 1.x is required. upload configuration

upload configuration 192.168.249.230 pre_upgrade_configuration.txt Note: It may be necessary to add a static route entry before uploading the configuration to the TFTP server. Refer to “TFTP Server Network Topology” on page 11 and “Case 4 Additional Configuration” on page 12 for further information. 4

Download the conversion program to the switch. This conversion program will temporarily upgrade the switch to an intermediary software release (Software Release 1.3.1) and prepare it for a final upgrade to Software Release 2.1. Refer to “Software Filenames” on page 8 for the appropriate filename. download firmware

download firmware 192.168.249.230 p16a1310.img Note: During this step the conversion program will be downloaded to the switch and upgrade the switch to the intermediary software release. Do not interrupt the switch during this process. When this process is completed the switch will be running Software Release 1.3.1. Reconnect to the switch and log in to ensure that upgrade has been successful.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

24 Chapter 1 Upgrade Procedures

5

Reconnect to the switch and download the new pre-boot monitor software. This new pre-boot monitor software will upgrade the switch to a new bootrom which supports SMLT failover features. Caution: Do not power cycle the switch during the remainder of this procedure except when instructed. Power cycling the switch during this step can cause irreversible damage to the pre-boot monitor software and switch. download prom

download prom 192.168.249.230 p16b2100.had 6

Save the current configuration using the Save command. The current switch configuration will be translated into a format that can be used by Software Release 2.1. After this process has completed the message You are safe to upgrade firmware 2.x will be displayed. Save

7

Backup the new, Software Release 2.1-compatible configuration to the TFTP server. upload translated_conf

upload translated_conf 192.168.249.230 translated_configuration.txt 8

Download the new bootflash to the switch. During this process, a new boot monitor image will be downloaded to the switch, installed, and the flash system formatted with DOS-FS. This process takes a considerable amount of time and under no circumstances should the switch be reset. download firmware p16b2100.img

download firmware 192.168.249.230 p16b2100.img 9

When the message Press to stop auto-boot... is displayed, press the Enter key to enter the boot monitor configuration mode. Note: Refer to Table 2 on page 10 to ensure that the terminal application in use has the proper connection settings.

321327-B

Chapter 1 Upgrade Procedures 25

10 At the boot monitor prompt, configure the IP address, static route entries for the management interface, and the managment IP address of the TFTP server in use. Use these commands to perform this task: net mgmt ip

net mgmt ip 192.168.249.56/24 net mgmt route [add | del]

net mgmt route add 192.168.249.0/24 gateway 192.168.249.1 net mgmt tftp

net mgmt tftp 192.168.249.230 11 In the boot monitor prompt, set the management port for the switch if the switch being upgraded is an Ethernet Routing Switch 1648. set-mgmt-port

set-mgmt-port 1/48 12 Copy the runtime image and configuration file (created in step 6) to the system flash. copy :

copy 192.168.249.230:p16a2100.img p16a2100.img copy 192.168.249.230:translated_configuration.txt config.cfg 13 Set the switch boot and configuration file locations. The Ethernet Routing Switch 1600 Series allows for up to three boot and configuration file locations (primary, secondary, tertiary) per switch. The boot location specifies where the switch will look for the software image file after a successful boot. Perform the following tasks to complete this step: a

Set the primary location. choice primary image-file choice primary config-file

The parameter specifies a file resident in the system flash. The following command examples would be used to specify a switch whose primary boot and configuration file location is the system flash: choice primary image-file p16a2100.img Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

26 Chapter 1 Upgrade Procedures

choice primary config-file config.cfg b

Set secondary and tertiary boot locations. Setting secondary and tertiary locations are not mandatory but should be specified as a best practice. Table 4 lists the options available when specifying boot locations. Up to three boot locations (primary, secondary, tertiary) can be specified.

Table 4 Boot Location Options Boot Location

Command Options

Primary

choice primary backup-config-file choice primary config-file choice primary image-file

Seconday

choice secondary backup-config-file choice secondary config-file choice secondary image-file

Tertiary

choice tertiary backup-config-file choice tertiary config-file choice tertiary image-file

14 Save the current configuration and reboot the switch. save boot

15 After the device completely reboots, save the current boot and switch configuration settings. save config save bootconfig Note: The boot configuration file boot.cfg has been introduced to the Ethernet Routing Switch 1600 Series in Software Release 2.1. The conversion program will automatically convert and save the 1.x configuration to this new file. To completely remove those boot settings from the runtime configuration file config.cfg, and to ensure the settings have been saved into boot.cfg, users must use both the save config and save bootconfig commands to finalize the conversion process.

321327-B

Chapter 1 Upgrade Procedures 27

Software Release 2.x Upgrade Procedure using the CLI This section outlines the procedure used to upgrade a switch running a 2.x version of the software to a newer version of the software using the Command Line Interface. To perform a 2.x upgrade, follow this procedure: Note: Throughout this procedure command syntax will be presented in this font. Where applicable, commands will be followed by an example presented in this font. 1

Copy the upgrade files to the TFTP server that will be used during the upgrade procedure (Refer to “TFTP Server Network Topology” on page 11 for network topologies that will support TFTP server connection). These files are listed in “Software Filenames” on page 8 and can be acquired from the Nortel Support Portal at http://www.nortel.com/support.

2

Connect to the switch using either the console port or a telnet session. Refer to “Console Port Settings” on page 10 for console connection parameters. Note: If the switch will not use the system flash as the primary boot location, skip steps 3 to 6 and proceed to step 7. Otherwise, continue with step 3.

3

Back up the current switch configuration and boot configuration to a TFTP server. Use the copy command to copy the current configuration files. copy :

copy /flash/config.cfg 192.168.249.230:config.cfg copy /flash/boot.cfg 192.168.249.230:boot.cfg

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

28 Chapter 1 Upgrade Procedures

4

Ensure that sufficient space is available in the system flash to store the new image files prior to attempting to upload them to the switch. Use the dir command at any prompt to receive a listing of the files currently stored in the flash memory as well as the amount of used and free space available.

5

If there is insufficient space in the system flash memory, use the rm command to remove files. Note: Nortel recommends having no less than 8MBs of space free in the system flash before proceeding with the upgrade procedure. This command has the following syntax: rm /flash/

rm /flash/p16a2100.img Note: After issuing the rm command, the switch will prompt for confirmation of file deletion with the message Are you sure ?. Type y and press Enter to confirm file deletion. 6

Copy the new image files to the system flash. Note: Software image files can be obtained from the Nortel Support Portal located at http://www.nortel.com/support. Use the copy command to copy the image files from a TFTP server to the system flash. This command has the following syntax: copy : /flash/

copy 192.168.249.230:p16a2100.img /flash/p16a2100.img copy 192.168.249.230:p16b2100.img /flash/p16b2100.img copy 192.168.249.230:p16b2100.had /flash/p16b2100.had

321327-B

Chapter 1 Upgrade Procedures 29

Perform this task for every image file that must be copied to the switch. As outlined in “Software Filenames” on page 8, the following files could be needed for the upgrade process: • • • • •

Software Image File - p16a2100.img (required) Pre-boot Monitor Image File - p16b2100.had (required for complete SMLT solution and to run p16b2100.img) Boot Monitor Image File - p16b2100.img (required) 3DES SSH Encryption Module - p16c2100.img (optional) DES SNMPv3 Encryption Module - p16c2100.des (optional) Note: The 3DES SSH Encryption Module and DES SNMPv3 Encryption Module are optional file uploads but are dependent upon each other. To use SNMPv3 both modules must be present on the switch.

7

The boot configuration file must be edited to indicate the new software image files to use. Use the config bootconfig choice command to edit the switch boot configuration file. The boot configuration file allows for up to three different boot locations (primary, secondary, tertiary) to be stored. This ensures that the switch has redundant paths to the software image files in case of failure. The config bootconfig choice command has the following syntax: config bootconfig choice image-file

The following is an example of using this command to instruct the switch to boot from an image file resident in the system flash: config bootconfig choice primary image-file /flash/p16a2100.img The following is an example fo using this command to instruct the switch to boot from an image file resident on a TFTP server: config bootconfig choice primary image-file 192.168.249.230:p16a2100.img 8

Save the changes to the boot configuration file. save bootconfig

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

30 Chapter 1 Upgrade Procedures

9

Confirm the boot configuration file changes. show bootconfig choice show bootconfig flags

10 Reboot the switch to use the new software image. In the CLI, use the boot command to reboot the switch. This command has the following syntax: boot [-y]

The following is an example of using this command to instruct the switch to boot from a file located in the system flash: boot /flash/p16b2100.img The following is an example of using this command to instruct the switch to boot from a file located on a TFTP server: boot 192.168.249.230:p16b2100.img 11 Confirm the switch reboot. After the boot command is issued the following confirmation message is displayed: Are you sure you want to re-boot the switch (y/n)?

Type y and press Enter to confirm the reboot and load the new software build. 12 Log back into the switch using the console port or telnet to ensure that the switch has rebooted successfully. 13 Reboot the switch again to use the new pre-boot monitor software image. In the CLI, use the boot command to reboot the switch. This command has the following syntax: boot [-y]

The following is an example of using this command to instruct the switch to boot from a file located in the system flash: boot /flash/p16b2100.had

321327-B

Chapter 1 Upgrade Procedures 31

The following is an example of using this command to instruct the switch to boot from a file located on a TFTP server: boot 192.168.249.230:p16b2100.had Note: The pre-boot monitor software image version can only be viewed in the device console. This software version is displayed when the device boots. A device running with an old pre-boot monitor will display version 0.00.003 or 0.00.004. After completing this upgrade process, the pre-boot monitor version will be 2100b003. 14 Confirm the switch reboot. After the boot command is issued the following confirmation message is displayed: Are you sure you want to re-boot the switch (y/n)?

Type y and press Enter to confirm the reboot and load the new software build. 15 Log back into the switch using the console port or telnet to ensure that the switch has rebooted successfully.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

32 Chapter 1 Upgrade Procedures

Software Release 2.x Upgrade Procedure using the JDM This section outlines the procedure used to upgrade a switch running a 2.x version of the software to a newer version of the software using the Java Device Manager (JDM). To perform a 2.x upgrade, follow this procedure: Note: Throughout this procedure command syntax will be presented in this font. Where applicable, commands will be followed by an example presented in this font 1

Copy the upgrade files to the TFTP server that will be used during the upgrade procedure (Refer to “TFTP Server Network Topology” on page 11 for network topologies that will support TFTP server connection). These files are listed in “Software Filenames” on page 8 and can be acquired from the Nortel Support Portal at http://www.nortel.com/support.

2

Connect to the switch using the Java Device Manager. Note: If the switch will not use the system flash as the primary boot location, skip steps 3 to 6 and proceed to step 7. Otherwise, continue with step 3.

3

Back up the current switch configuration and boot configuration to a TFTP server. Select Edit > File System from the menu. This will open the FileSystem dialog. Select the Copy File tab. The fields on this tab are as follows: • •



321327-B

Source - This is the source file that will be copied to the TFTP server. Enter the literal string /flash/ followed by the file name. Destination - This is the destination of the file being copied. Enter the IP address of the TFTP server and the name of the file to be copied separated by a colon (:). Action - Select the start option button to indicate that the file transfer process is ready to begin.

Chapter 1 Upgrade Procedures 33

After setting these fields click Apply to begin. The Result field should indicate success when the upload is complete. Click Refresh to update the display of the Result field. 4

Ensure that sufficient space is available in the system flash to store the new image files prior to attempting to upload them to the switch. Select Edit > File System from the menu. This will open the FileSystem dialog. Select the Device Info tab to display information on the total amount and free space in the system flash and the Flash Files tab to display the files currently stored in the system flash memory.

5

If there is insufficient space in the system flash memory, use the rm command in the CLI to remove files. Note: Nortel recommends having no less than 8MBs of space free in the system flash before proceeding with the upgrade procedure. This command has the following syntax: rm /flash/

rm /flash/p16a2100.img Note: After issuing the rm command, the switch will prompt for confirmation of file deletion with the message Are you sure ?. Type y and press Enter to confirm file deletion. 6

Copy the new image files to the system flash. Note: Software image files can be obtained from the Nortel Support Portal located at http://www.nortel.com/support. Select Edit > File System from the menu. This will open the FileSystem dialog. Select the Copy File tab. The fields on this tab are as follows: •



Source - This is the source file that will be copied to the switch. Enter the IP address of the TFTP server and the name of the file to be copied separated by a colon (:). Destination - This is the destination of the file being copied. Enter the literal string /flash/ followed by the destination file name. Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

34 Chapter 1 Upgrade Procedures



Action - Select the start option button to indicate that the file transfer process is ready to begin.

After setting these fields click Apply to begin. The Result field should indicate success when the upload is complete. Click Refresh to update the display of the Result field. Perform this task for every image file that must be copied to the switch. As outlined in “Software Filenames” on page 8, the following files could be needed for the upgrade process: • • • • •

Software Image File - p16a2100.img (required) Pre-boot Monitor Image File - p16b2100.had (required for complete SMLT solution and to run p16b2100.img) Boot Monitor Image File - p16b2100.img (required) 3DES SSH Encryption Module - p16c2100.img (optional) DES SNMPv3 Encryption Module - p16c2100.des (optional) Note: The 3DES SSH Encryption Module and DES SNMPv3 Encryption Module are optional file uploads but are dependent upon each other. To use SNMPv3 both modules must be present on the switch.

7

The boot configuration file must be edited to indicate the new software image files to use. Select Edit > Chassis from the menu. This will open the Chassis dialog. Select the Boot Config tab. On this tab are three fields used to edit the boot configuration file. The boot configuration file allows for up to three different boot locations (primary, secondary, tertiary) to be stored. This ensures that the switch has redundant paths to the software image files in case of failure. These three fields are: • • •

PrimaryImageSource SecondaryImageSource TertiaryImageSource

To boot from the system flash enter /flash/ followed by the image file name (i.e.: /flash/p16a2100.img). To boot from a TFTP server enter the IP addressand the file name separated by a colon (:) (i.e.: 192.168.249.230:p16a2100.img).

321327-B

Chapter 1 Upgrade Procedures 35

8

Once changes to the boot configuration file are complete, save the configuration. Click Apply on the Boot Config tab and select Actions > Save Boot Config from the menu..

9

Use the CLI to confirm the boot configuration file changes. show bootconfig choice show bootconfig flags

10 Reboot the switch to use the new software image. In the CLI, use the boot command to reboot the switch. This command has the following syntax: boot [-y]

The following is an example of using this command to instruct the switch to boot from a file located in the system flash: boot /flash/p16b2100.img The following is an example of using this command to instruct the switch to boot from a file located on a TFTP server: boot 192.168.249.230:p16b2100.img 11 Confirm the switch reboot. After the boot command is issued the following confirmation message is displayed: Are you sure you want to re-boot the switch (y/n)?

Type y and press Enter to confirm the reboot and load the new software build. 12 Log back into the switch using the Java Device Manager to ensure that the switch has rebooted successfully. 13 Reboot the switch again to use the new pre-boot monitor software image. In the CLI, use the boot command to reboot the switch. This command has the following syntax: boot [-y]

The following is an example of using this command to instruct the switch to boot from a file located in the system flash: boot /flash/p16b2100.had

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

36 Chapter 1 Upgrade Procedures

The following is an example of using this command to instruct the switch to boot from a file located on a TFTP server: boot 192.168.249.230:p16b2100.had Note: The pre-boot monitor software image version can only be viewed in the device console. This software version is displayed when the device boots. A device running with an old pre-boot monitor will display version 0.00.003 or 0.00.004. After completing this upgrade process, the pre-boot monitor version will be 2100b003. 14 Confirm the switch reboot. After the boot command is issued the following confirmation message is displayed: Are you sure you want to re-boot the switch (y/n)?

Type y and press Enter to confirm the reboot and load the new software build. 15 Log back into the switch using the console port or telnet to ensure that the switch has rebooted successfully.

321327-B

Chapter 1 Upgrade Procedures 37

Software Release 2.1 to 1.x Downgrade Procedure This section outlines the procedure used to downgrade a switch running Software Release 2.1 to an earlier version. Read and understand this procedure thoroughly before attempting it. Note: This downgrade procedure will reset the switch to factory defaults. A Software Release 1.x-compatible configuration should have been saved before upgrading the switch to Software Release 2.1.

Note: Software Release 1.3 is only meant to provide an intermediary software base to facilitate the upgrade to Software Release 2.1. If a downgrade is necessary, downgrade to a full, 1.x software version such as Software Release 1.2. To accomplish this task, follow this procedure: Note: Throughout this procedure command syntax will be presented in this font. Where applicable, commands will be followed by an example presented in this font. 1

Download the runtime file that correspond to the desired software version from the Nortel Support Portal at http://www.nortel.com/support. The file used in this procedure is p16a1230.img.

2

Connect to the switch through the console port using an appropriate terminal or terminal emulation software. Refer to “Console Port Settings” on page 10 for connection parameters.

3

Reset the switch using the reset command. This command has the following syntax: reset [-y]

Use the -y option to skip the switch reset confirmation message.

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

38 Chapter 1 Upgrade Procedures

4

The message Power On Self Test will be displayed. Before this diagnostic test is more than sixty percent complete, press and hold the number key (#) (on a standard 101 or 104 North American keyboard, press and hold the SHIFT and 3 keys simultaneously) until the the following message appears: Please change your baud rate to 115200 for Z-modem or press CTRL-C to go to the boot menu

5

Disconnect the console session, change the connection baud rate to 115200, and reconnect.

6

Using the options available in the terminal emulation software, use a Zmodem transfer to move the software image (p16a1230.img) acquired in step 1 to the switch.

7

After the file transfer is complete, the switch will load the new runtime image.

8

Disconnect the terminal session, change the baud rate to 9600, and reconnect. The switch will boot with the Software Release 1.x software.

9

Add a management IP and route for the switch. config ipif System ipaddress /

config ipif System ipaddress 192.168.249.14/255.255.255.0 create iproute default

create iproute default 192.168.249.1 10 Download and install the 1.x configuration backup that was created before the switch was upgraded to Software Release 2.1. download configuration

download configuration 192.168.249.230 pre_upgrade_configuration.txt 11 Use the save command to save the switch configuration.

321327-B

Chapter 1 Upgrade Procedures 39

Default User Names and Passwords The runtime software default login user names and passwords are shown in Table 5. Table 5 Default login user names and passwords Access level

User name

Password

RWA

rwa

rwa

RW

rw

rw

RO

ro

ro

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

40 Chapter 1 Upgrade Procedures

Related Documentation This section lists the documentation specific to the Ethernet Routing Switch 1600 Series platform. You can download current versions of technical documentation for your Ethernet Routing Switch 1600 Series from the Nortel Support Portal at http://www.nortel.com/support. Technical manuals and release notes can be printed and copied freely from the Internet. Documents acquired from the Internet can be viewed, printed, and searched using Adobe Reader*. Adobe Reader can be downloaded for free from the Adobe web site. The following list outlines the documenation in the Ethernet Routing Switch 1600 Series suite: • • • • • • • • • •

321327-B

Installing the Ethernet Routing Switch 1600 Series (Part Number 316860-D) Upgrading to Ethernet Routing Switch 1600 Series Software Release 2.1 (Part Number 321327-B) Configuring IP Routing and Multicast Operations using the CLI (Part Number 321711-B) Configuring IP Routing and Multicast Operations using Device Manager (Part Number 321712-B) Configuring and Managing Security using Device Manager (Part Number 321713-B) Configuring and Managing Security using the CLI (Part Number 321714-B) Configuring QoS and Filters using the CLI (Part Number 321715-B) Configuring QoS and Filters using Device Manager (Part Number 321716-B) Configuring VLANs, Spanning Tree, and Static Link Aggregation using the CLI (Part Number 321717-B) Configuring VLANs, Spanning Tree, and Static Link Aggregation using Device Manager (Part Number 321718-B)

Chapter 2 Calculating MD5 digest 41

Chapter 2 Calculating MD5 digest The md5 command calculates MD5 digest for files on the switch's flash and either displays the output on screen or stores the output in a file. An MD5 command option compares the MD5 digest calculated with what is present in a checksum file on flash and displays the compared output on the screen. By verifying the MD5 checksum, it can be verified that the file transferred properly to the switch. This command is available from both the boot monitor and runtime CLI. Use the md5 command with reserved files (for example, a password file) only if sufficient permissions have been granted to access these files. A checksum file is provided with the images for download. Transfer the image files to the switch and use the md5 command to ensure that the checksum of the images on the switch is the same as the checksum file. To calculate MD5 digest for files on the switch's flash, and to display the output on screen or to store the same in a file, enter the following command: Note: Throughout this chapter command syntax will be presented in this font. Where applicable, commands will be followed by an example presented in this font. ERS-1612:1# md5

ERS-1612:1# md5 p16a2100.img MD5 (p16a2100.img) = f6ddb971dafcfb8c59e42269f8f60265

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

42 Chapter 2 Calculating MD5 digest

The md5 command includes the following options: md5 followed by: wildcard (*)

Calculates md5 checksum of all files.

-f

Stores the result of md5 checksum to a file on flash. If the output file specified with the -f option is one of the: • reserved filenames on the switch, the command fails with the error message:

Error: Invalid operation. •

files for which md5 checksum is to be computed, the command fails with the error message:

Ethernet Routing Switch-1612:1# md5 *.cfg -f config.cfg Error: Invalid operation on file If the checksum filename specified by the -f option already exists on the switch (and is not one of the reserved filenames), the following message displays on the switch:

File exists. Do you wish to overwrite? (y/n) -r

321327-B

Reverses the output and may be used with the -f option to store the output to a file. The -r option cannot be used with the -c option.

Chapter 2 Calculating MD5 digest 43 md5 followed by: -a

Adds data to the output file instead of overwriting it. You cannot use the -a option with the -c option.

-c

Compares the checksum of the specified file by with the MD5 checksum present in the checksum file name. You can specify the checksum file name using the -f option. When the checksum filename is not specified, the file /flash/ checksum.md5 is used for comparison. If the supplied checksum filename and the default file are not available on flash, the following error message displays: Error: Checksum file not present. The -c option also: • calculates the checksum of files specified by

filename • •

compares the checksum with all keys in the checksum file, even if filenames don't match displays the output of comparison

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

44 Chapter 2 Calculating MD5 digest

The following files are examples of output files used with md5 command options: ERS-1612:1# md5 *.img MD5 (p16a2100.img) = f6ddb971dafcfb8c59e42269f8f60265 MD5 (p16b2100.img) = 746b308e5eb02118670d2bc2bab15b61 ERS-1612:1# md5 *.img -f checksum.md5 ERS-1612:1# more checksum.md5 MD5 (/flash/p16a2100.img) = f6ddb971dafcfb8c59e42269f8f60265 MD5 (/flash/p16b2100.img) = 746b308e5eb02118670d2bc2bab15b61 ERS-1612:1# md5 *.img -r f6ddb971dafcfb8c59e42269f8f60265 p16a2100.img 746b308e5eb02118670d2bc2bab15b61 p16b2100.img ERS-1612:1# md5 *.img -c -f p16a2100.md5 /flash/p16a2100.img Match f6ddb971dafcfb8c59e42269f8f60265 p16a2100.img /flash/p16b2100.img Match 746b308e5eb02118670d2bc2bab15b61 p16b2100.img.unstamp ERS-1612:1#

Note: There is no MIB support for this command.

321327-B

Appendix A CLI commands that require translation 45

Appendix A CLI commands that require translation During the upgrade process a new configuration file is created based on the Ethernet Routing Switch 8000 CLI. The version 1.3 upgrade process translates the 1.2.x configuration files to version 2.1 and generates a file containing a list of 1.2.x CLI commands that cannot be automatically upgraded. This section details those commands which must be manually translated as well as those commands which are partially translated by the switch.

Commands that require manual translation Commands in Table 6 are not translated during the upgrade process and must be manually translated by inputting their equivalents where applicable. Table 6 CLI commands not translated during software upgrade (Sheet 1 of 5) Command

Comments

Platform config log_state [enabled|disabled]

No 8000 equivalent CLI

config remote_user log state [enabled|disabled]

No 8000 equivalent CLI

enable snmp authenticate traps

config sys set sendAuthenticationTrap true

disable snmp authenticate traps

config sys set sendAuthenticationTrap false

enable snmp traps

No 8000 equivalent CLI

disable snmp traps

No 8000 equivalent CLI

disable post

No 8000 equivalent CLI

enable telnet {}

8000 implementation does not permit TCP port number configuration

config password_aging

No 8000 equivalent CLI

config secure_mode [normal|high]

No 8000 equivalent CLI

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

46 Appendix A CLI commands that require translation

Table 6 CLI commands not translated during software upgrade (Sheet 2 of 5) Command

Comments

DNS Relay config dnsr [[primary|secondary] nameserver |[add|delete] static ]

No 8000 equivalent CLI

disable dnsr {cache | static }

No 8000 equivalent CLI

enable dnsr {cache | static }

No 8000 equivalent CLI

SNTP (Simple Network Time Protocol) config sntp Unicast Polling Interval {} No 8000 equivalent CLI Port configuration config scheduling ports [ | all] class_id max_packet

No 8000 equivalent CLI

config ports [ | all ]learning disabled

No 8000 equivalent CLI

Refer to Upgrading to Ethernet Routing Switch 1600 config mgmt_port {speed [auto | 10_half | 10_full | 100_half |100_full] | flow_control [enabled | disabled] | Series Software Release 2.1 (321327-B) state [enabled |disabled]} STP/FDB/VLAN config stp fbpdu enable (MSTP/RSTP/STP)

No 8000 equivalent CLI

enable stp (MSTP)

No 8000 equivalent CLI

disable stp (MSTP)

No 8000 equivalent CLI

create mac_priority vlan dst_mac_addr No 8000 equivalent CLI priority create fdbfilter vlan mac_address ff-ff-ff-ff-ff-ff

No 8000 equivalent CLI

create vlan [ip-subnet {arp_classification_id }

No IP Subnet VLAN support in version 2.x

config ipif directed-broadcast [enabled|disabled]

No 8000 equivalent CLI

config vlan_ports [ | all] ingress_checking [enabled | disabled]

No 8000 equivalent CLI

config vlan_ports [ | all] acceptable_frame [all|onlyTagged]

No 8000 equivalent CLI

321327-B

Appendix A CLI commands that require translation 47

Table 6 CLI commands not translated during software upgrade (Sheet 3 of 5) Command

Comments

IGMP Snooping config igmp_snooping [ |all] host_timeout

No 8000 equivalent CLI

config igmp_snooping [ |all] router_timeout

No 8000 equivalent CLI

config igmp_snooping [ |all] leave_timer

No 8000 equivalent CLI

config igmp_snooping querier [ |all] { No 8000 equivalent CLI query_interval | max_response_time | robustness_variable | last_member_query_interval } disable igmp_snooping {filtering}

No 8000 equivalent CLI

enable igmp_snooping {filtering|forward_mcrouter_only}

No 8000 equivalent CLI

ARP/IP/DVMRP/IGMP/VRRP config arp_req_rate_limit

No 8000 equivalent CLI

enable arp_req_rate_limit

No 8000 equivalent CLI

disable arp_req_rate_limit

No 8000 equivalent CLI

create arpentry

No 8000 equivalent CLI

config ipif { state [enabled|disabled]}

No 8000 equivalent CLI

create ipif { state [enabled|disabled]}

No 8000 equivalent CLI

config dvmrp [ipif | all ] {metric | probe | neighbor_timeout | state [enabled|disabled]} enable dvmrp & disable dvmrp

No 8000 equivalent CLI

disable dvmrp

No 8000 equivalent CLI

config igmp [ipif |all state [enabled|disabled]

No 8000 equivalent CLI

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

48 Appendix A CLI commands that require translation

Table 6 CLI commands not translated during software upgrade (Sheet 4 of 5) Command

Comments

disable vrrp

No 8000 equivalent CLI

create vrrp ipif {authtype [none|simple authdata |ip authdata ]}

No 8000 equivalent CLI

create vrrp ipif preempt true

No 8000 equivalent CLI

Routing/RIP/OSPF config rip [ipif |all] {authentication [ enabled | disabled ]}

No 8000 equivalent CLI

create route redistribute dst rip src [ local | static | ospf[all|internal|external|type_1|type_2|inter+e1|inter +e2] ]{metric }

No 8000 equivalent CLI

create ospf host_route area

No 8000 equivalent CLI

Security TACACS+/MD5 keys/SSH config authentication admin [console | telnet | ssh | all] No 8000 equivalent CLI {tacacs+ | local | none} config authentication admin local_password

No 8000 equivalent CLI

config authentication login [console | telnet | ssh | all] {tacacs+ | local | none}

No 8000 equivalent CLI

config login_authen response_timeout

No 8000 equivalent CLI

enable admin

No 8000 equivalent CLI

create md5 key

No 8000 equivalent CLI

config ssh user authmode [hostbased [hostname | hostname_IP ] | password | publickey|none]

No 8000 equivalent CLI

config ssh algorithm No 8000 equivalent CLI [3DES|AES128|AES192|AES256|arcfour|blowfish|cas t128|twofish128|twof ish192|twofish256|MD5|SHA1|RSA|DSA] [enabled|disabled] config ssh authmode publickey[enabled|disabled]

321327-B

No 8000 equivalent CLI

Appendix A CLI commands that require translation 49

Table 6 CLI commands not translated during software upgrade (Sheet 5 of 5) Command

Comments

config ssh authmode hostbased enabled|disabled]

No 8000 equivalent CLI

config ssh server authfail

No 8000 equivalent CLI

config ssh server port

No 8000 equivalent CLI

config ssh server rekey [10min|30min|60min|never]

No 8000 equivalent CLI

Traffic Control config traffic control [|all] threshold {dlf [enabled threshold | disabled] }

No 8000 equivalent CLI

config ethernet 1/1-1/52tx-flow-control disable

No 8000 equivalent CLI

config ethernet 1/1-1/52tx-flow-control

No 8000 equivalent CLI

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

50 Appendix A CLI commands that require translation

Commands that translate with limitations The upgrade process translates some commands with limitations. Commands in Table 7 are translated with limitations during the upgrade process. Table 7 CLI commands translated with limitations during the software upgrade (Sheet 1 of 3) Phase 1 (Release 1.x)

Phase 2 (Release 2.x)

Limitation

Platform (boot mode) config bootconfig cli timeout config serial_port { baud_rate [9600|19200|38400|115200] | auto_logout [never|2_minutes|5_minutes|10_m inutes|15_minutes] }

If the timeout option was set to never in the original config, it defaults to the maximum value(65535).

enable telnet {}

config bootconfig flags telnetd

Telnet port defaults to 23 during upgrade.

enable web {}

config web-server enable config web-server http-port

The maximum port number is 49515. Any port outside this range defaults to 49515.

Simple Network Time Protocol (SNTP) "config time Daylight-Saving-Time state [enabled|disabled] config time Daylight-Saving-Time offset config time Daylight-Saving-Time start end "

config bootconfig tz dst-offset config bootconfig tz dst-end dst-start

If state enabled is configured then all Daylight-Saving settings convert. If state is disabled, then all settings are lost.

Spanning Tree (MSTP/RSTP/STG) config stp ports {externalCost [auto | ] |hellotime | protocol-migration [true|false] |edgeport [true|false] | p2p [forcetrue|forcefalse|auto]| state [enable | disable]}

config ethernet / All STP time values are expressed -/ mstp cist in 1/100 second in Phase 2. hello-time

config stp mst_ports instance_id {internalCost [auto | ]}

config ethernet mstp msti pathcost

321327-B

Phase 2 does not support auto cost . Therefore it is set to the default value in MSTP/RSTP/STG. NOTE: The default value differs between protocols and MLT).

Appendix A CLI commands that require translation 51

Table 7 CLI commands translated with limitations during the software upgrade (Sheet 2 of 3) Phase 1 (Release 1.x)

Phase 2 (Release 2.x)

Limitation

config vlan create byport-mstprstp

In Phase 1, VLAN_1 can be assigned to any MST instance. In Phase 2, VLAN_1 must be in CIST.

config fdb aging_time

config vlan fdb-entry aging-time

The Phase 1 global aging time is assigned to all VLANs in Phase 2.

create fdbfilter vlan mac_address

config vlan fdb-filter add The config vlan port drop fdb-filter add port drop command is executed on all ports in the VLAN in Phase 2.

Spanning Tree (MSTP) config stp_vlan instance_id add

FDB

VLAN config 802.1p default_priority [ config ethernet qos | all ] priority [0 | 4 | 6 | 7] qos-level

In Phase 2, the "priority" range is 1..6. Any priority "7" setting is converted to a value of 6.

create vlan {vid }

VLAN ID range is [1..4000] in Phase 2. All VLAN IDs greater than 4000 are lost after conversion.

IGMP Snooping config router_ports [add|delete]

config vlan ip igmp mrouter

In Phase1, an mrouter can be configured without enabling IGMP Snoop. In Phase 2, if IGMP Snoop is disabled on the VLAN no "mrouter" port can be configured.

config ip arp aging

In Phase 2 the maximum ip arp aging value is 32767. Any value greater than 32767 defaults to 32767.

ARP config arp_aging time

OSPF create ospf area type [normal | stub {stub_summary [enabled|disabled] | metric }]

config ip ospf area create The stub_summary config ip ospf area stub [enabled|disabled] option is not available in Phase 2. config ip ospf area stub-metric

Upgrading to Ethernet Routing Switch 1600 Software Release 2.1

52 Appendix A CLI commands that require translation

Table 7 CLI commands translated with limitations during the software upgrade (Sheet 3 of 3) Phase 1 (Release 1.x)

Phase 2 (Release 2.x)

Limitation

Traffic Control config traffic control { config ethernet [|all] { broadcast [enabled bcast-mcast-rate-limit |disabled] | multicast [enabled | [] disabled] |

321327-B

1. The default Bcast and Mcast rate limit percentage value is 20. 2. Only if both Bcast and Mcast are disabled in Phase 1 will Bcast and Mcast be disabled in Phase 2.

Suggest Documents