Traverse/TransNav Upgrade Guide

Transcription

1 Traverse/TransNav Upgrade Guide TR5.0.x/TN6.0.x October 2011 R

2 Copyright 2011 Force10 Networks, Inc. All rights reserved. Force10 Networks reserves the right to change, modify, revise this publication without notice. Trademarks Force10 Networks and E-Series are registered trademarks of Force10 Networks, Inc. Traverse, TraverseEdge, TraversePacketEdge, TransAccess, are registered trademarks of Force10 Networks, Inc. Force10, the Force10 logo, and TransNav are trademarks of Force10 Networks, Inc. or its affiliates in the United States and other countries and are protected by U.S. and international copyright laws. All other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, Force10 Networks, Inc. reserves the right to make changes to products described in this document without notice. Force10 Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) described herein.

3 CONTENTS Chapter 1 Software Upgrades General Software Compatibility Card Software Download Setup System Software Upgrades Download Download Traverse Node Software to the TransNav Server System Software Upgrades Activation Bulk Config (Upgrade Helper) Software Upgrade and Activation Shortcut Menus Software Revert Chapter 2 Release TR5.0.x Traverse Software Upgrade Release TR4.0.x Upgrade Overview Node Software Upgrade Flowchart (Top Level) Before You Begin Requirements for Software Upgrade Compatibility and Guidelines Traverse System Software Upgrade Compatibility Notes Guidelines for Software Upgrade Traverse Node Software Upgrade Process Card Software Download Set-up Software Activation Process Control Card Software Upgrade Activation Software Upgrade Activation (All Other Protected Cards) Activate Software (All Unprotected Cards) Spare Control Card Software Activation Spare Card Software Activation (All Other Types) Verify Protection Status Perform a Forced Switch Perform a Manual Switch Clear Protection Switch User selectable FPGA Upgrade Capability Overview to Upgrade TE-206 Nodes from TransNav Requirements for Upgrading TE-206 Node Software Downloading TE-206 Node Software Upgrading TE-206 Node Software from TransNav Chapter 3 TE-100 Release TE3.2.3 System Software Upgrade Release TE3.2.3 Upgrade Overview Before You Begin Required Equipment and Tools Upgrade Guide, Release TR5.0.x 1

4 Compatibility and Guidelines TE-100 Platform SW Upgrade Compatibility Notes Guidelines for Software Upgrade Node Software Upgrade Process Software Activation Process Activate Software - Control Module Spare Control Module Software Activation Chapter 4 Replacing Existing Traverse Hardware Software Compatibility Software Version Verification Electrostatic Discharge Protection Required Equipment and Tools Replacement Card Type and Software Version Preparing a Card for Removal and Replacement Remove a Card Card Placement Guidelines GCM Card Replacement as Standby LED Indicators Insert a Replacement Card Replace the Front Inlet Fan Tray Card Replace the Traverse 600 Fan Assembly Fan Assembly Air Filter Installation (Traverse 600) Chapter 5 Upgrade to a Traverse Front Inlet Fan Tray Precautions and Assumptions Required Equipment and Tools FIFT Upgrade Instructions Check the New Fan Module Chapter 6 Upgrade a DCS-96 to a DCS-IO Shelf Install, Commission, and Create DCS Services on the DCS-384 Shelf Upgrade the Hardware in the DCS-96 Shelf Upgrade the DCS-96 Shelf to a DCS-IO Shelf Upgrade Guide, Release TR5.0.x

5 Chapter 1 Software Upgrades Introduction This chapter describes the following administrative functions selected through the Admin menu on the graphical user interface (GUI): System Software Upgrades Download System Software Upgrades Activation Bulk Config (Upgrade Helper) Software Upgrade and Activation Shortcut Menus Software Revert Important: Software upgrade requires a specified order. You must first upgrade the management server software, followed by control cards, and then line cards. For step-by-step software upgrade procedures for Traverse nodes, see Chapter 2 Release TR5.0.x Traverse Software Upgrade. Important: To upgrade management server software, see the TransNav Management System GUI Guide, Chapter 3 Administration s, Upgrade Server Software. General Software Compatibility Control Cards. Each control card is partitioned and capable of holding two versions of software. The new software is downloaded onto the card s backup partition during a software upgrade. You activate the new software after the software has been successfully downloaded. Software upgrade activation reboots each card and activates the back-up partition with the newly downloaded software. Provisioning data stored on the node control card is migrated to the backup partition before reboot. A UGCM-XM card is available for use with Traverse shelves that offers extended memory to support an increased number of services. Force10 recommends updating both GCMs on a shelf to the UGCM-XM to avoid potential service failure during upgrades. Management Software. The TransNav software simultaneously manages various node releases to accommodate longer-term upgrade paths. For a detailed product Upgrade Guide, Release TR5.0.x 3

6 compatibility matrix, see the Product Compatibility Matrix table in the Release Notes corresponding to your upgrade release. Replacement cards. Software version numbers are broken down as follows (SW Version: ): Position 1 shows the major software release number. Position 2 shows the minor software release number. Position 3 shows the release build number. Position 4 shows the software batch to build number. An INCOMPATSW:Incompatible software alarm is generated when: A replacement card with a (major.x.x.x) software version lower than the compatibility ID of the Active control card the lowest software version the Active control card can work with is placed in the node. The Active control card (major.x.x.x) software version is lower than the compatibility ID of the replacement card. The Active control card with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement card. A SWMIS: Software version mismatch alarm is generated when a replacement card with either an earlier or later (major.minor.build.x) version of software than the software running on the control card is placed in the node. In this case, use the procedures in this Card Software Download Setup Software upgrades are done at the node level. Prior to upgrading the software, an FTP server must be set up to allow the software to be downloaded to the node from an accessible directory on a server. FTP Server Setup. Use the following steps to set up the FTP server: Start the FTP service Configure the FTP service with a username and password Make sure the service can access the directory where the node software was unzipped The following procedure provides steps on how to begin a software upgrade by setting software download times for each card using the SW Upgrade dialog box. It takes a fully loaded Traverse-specific node 20 to 60 minutes to download the new software onto all cards. The time required to download software is dependent on the IP bandwidth available to the Traverse node and the type of GCM that is installed. Force10 recommends downloading no more than three nodes at a time. Download times can increase if there are multiple nodes using the same DCC channel. 4 Upgrade Guide, Release TR5.0.x

7 System Software Upgrades Download Click a Traverse node in Map View. From the Admin menu, select SW Upgrade to display the SW Upgrade dialog box. Figure 1 Software Upgrade Dialog Box The SW Upgrade dialog box allows you to enter the following information: Server IP Address: IP address of the machine where the new software resides. Username: Name of user on the machine where the new software resides. Base Path: Path where the new software resides. Password: Password of the user name on the machine where the new software resides. The following items are listed for each card in the node: Slot #: Slot number of the card. Card Type: Type of card inserted in the slot. Relative Path: The system automatically fills in the relative path to the card for the software upgrade. Download Time: The time it takes to transfer new software from the server to the backup partition of the card. Click the box corresponding to the card. Use the up and down arrows or type in the box to specify the download time. Download Status: Displays the software download status. Valid values are: NONE INPROGRESS FAILED OK ABORTED Upgrade Type: Select one of the following upgrade types: INIT: Completely erase backup partition of card and copy all files. MERGE: Do not erase backup partition; overwrite existing files and add new files. Current SW Version: Current software version of the card. Standby SW Version: Software version on standby (in the card backup partition) for the upgrade Both of these parameters are in the format A.B.C.D, where: A = major software release number B = minor software release number C = release build number Upgrade Guide, Release TR5.0.x 5

8 D = software patch to build Command buttons are as follows: Bulk Config: Display the Bulk Config (Upgrade Helper) dialog box. The Upgrade Helper allows you to select the download time, activation time, and upgrade type for all of the cards in the node. Update: Update configuration information. Revert: Cancel configuration information. Done: Close dialog box. You can also view the following information on the selected card s Config tab: Slot Number. Selected card slot number. Type: Selected card type. ICI: Current compatibility identifier. This identifier indicates the lowest software version compatibility with that of the highlighted card s Current SW Version. Module ID: A unique module (card) identifier. You must first download the software for the upgrade from the Force10 Networks corporate website onto a TransNav server before proceeding with the upgrade procedures. Choose one of the following download procedures, depending on the TransNav EMS platform (i.e., PC or Solaris) for your network. Download the TransNav Management System or Traverse node software from the Force10 Networks corporate website ( From Services & Support, select Customer Login. Enter your Force10 User ID and Password, then click Login. Select the Software Center tab, then select Traverse/Traverse Edge from the list of available software under isupport at the left side of the screen. A list of software releases and the corresponding release notes for each software release displays. 6 Upgrade Guide, Release TR5.0.x

9 Figure 2 Force10 Software Center Screen Right-click the software release to download the WinZip software file to a directory on your management server. The file must be able to be accessed by the current user. For any required help with this procedure, contact your system administrator. Upgrade Guide, Release TR5.0.x 7

10 Download Traverse Node Software to the TransNav Server Use these steps to download the Traverse node software to the TransNav server. Table 3 Download Traverse Node Software to the TransNav Server 1 Navigate to the directory where the Traverse node software files were previously downloaded from the Force10 Networks website. Figure 4 Example PC System Explorer Window File Listing 2 Right-click the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number). For Windows PC systems, select the WinZip > Extract to command. For Solaris systems, copy the flash.n.n.n.n.zip file to the desired directory for download (accessible from the FTP file server). Execute the following: gunzip flash.n.n.n.n.zip 8 Upgrade Guide, Release TR5.0.x

11 Table 3 Download Traverse Node Software to the TransNav Server (continued) 3 From the Extract dialog box, select a user-defined folder path directory that is accessible by the Windows FTP service (e.g., /upgrade/files), then click Extract to download the flash files into the /<user-defined>/flash directory. Important: Verify the Use folder names check box is selected to keep the./flash relative path structure in the zip file intact upon download. Figure 5 Extract Dialog Box 4 The Download Traverse Node Software to the TransNav Server procedure is complete. Continue to 5 of the Chapter 1 Traverse Release TR4.0.0 Software Upgrade, Traverse Node Software Upgrade Process. System Software Upgrades Activation Click a Traverse node in Map View. From the Admin menu, select SW Activation to display the SW Activation dialog box. Figure 6 SW Activation Dialog Box The SW Activation dialog box allows you to enter the following information: The following items are listed for each card in the node: Upgrade Guide, Release TR5.0.x 9

12 Slot #: Slot number of the card. Card Type: Type of card inserted in the slot. Activate Time: Click the box corresponding to the card. Use the up and down arrows or type in the box to specify the activation time. If two control cards are set to the same activation time, the standby control card will reboot first, followed by the active control card. Act (Activation) Status: Displays the software activation status. Activation refers to the reboot of the card from the backup partition (the part which contains the new software). Valid values are: NONE INPROGRESS FAILED OK Act (Activation) Type: Select one of the following: NSA (Non-Service-Affecting) (default): Do not allow activation of card if services are active on that card. SA (Service-Affecting): Activate card, even if services are active on that card. SPARE (Non-Service-Affecting): Reboot the spare control card. Warm Rbt: A hitless warm reboot function to restart the processor without affecting traffic. Ignore FPGA Upgd: A user-selectable FPGA upgrade capability. You can accept or ignore the FPGA card software change. Important: Force10 recommends using this capability only after careful consideration has been taken to assure the FPGA change for the card is non-critical in nature to your deployment. Current SW Version: Current software version of the card. Standby SW Version: Software version on standby (in the card backup partition) for the upgrade. Command buttons are as follows: Update: Update configuration information. Revert: Cancel configuration information. Done: Close dialog box. Bulk Config (Upgrade Helper) From the SW Upgrade dialog box, click on any row. Click the Bulk Config command button. The Upgrade Helper dialog box displays. The Upgrade Helper allows you to select the download time, activation time, and upgrade type for all of the cards in the Traverse node. Figure 7 Upgrade Helper Dialog Box 10 Upgrade Guide, Release TR5.0.x

13 The Upgrade Helper dialog box allows you to configure the following parameters for all of the cards in the node: Download Time: From the drop-down list, select one of the following options: Now: Start the upgrade now. Set time: Click the up and down arrows to set the specific time. Clear time: Clear the time and start over. Upgrade Type: Select one of the following options: INIT (default): Completely erase backup partition of cards and copy all files. MERGE: Do not erase backup partition; overwrite existing files and add new files. Automatically fill in rel. paths for equipped slots: The system automatically fills in the Rel Path column on the main software upgrade screen. Command buttons are as follows: OK: Update the SW Upgrade dialog box with the information in the Upgrade Helper dialog box and close Upgrade Helper dialog box. Cancel: Cancel configuration information and close the dialog box. Software Upgrade and Activation Shortcut Menus Both the SW Upgrade and SW Activation dialog boxes provide a shortcut menu. From the SW Upgrade dialog box, right-click a row to display the shortcut menu. Figure 8 Software Upgrade Shortcut Menu The shortcut menu allows you to perform the following actions: Abort Download: Stop copying files from the server to that card. Clear Download Time: Clear the download time that has been set for that card. From the SW Activation dialog box, right-click a row to display the shortcut menu. Figure 9 Software Activation Shortcut Menu Upgrade Guide, Release TR5.0.x 11

14 The shortcut menu includes: Clear Activation Time: Clear the activation time that has been set for that card. Software Revert Use the following procedures to revert to a previous software version used on the node and TransNav management system. Revert Node Software Revert TransNav Management System Software Revert Node Software. Important: This If you procedure expect to is revert service an affecting. entire node, Force10 recommends you call the Technical Assistance Center for assistance. Important: Configuration data will be lost if any configuration was Table 10 Revert performed Node after Software the upgrade. 1 Connect to the node using the Node CLI. 2 Perform the software revert command on every card that has been upgraded to the desired software load. Execute this command in the following card order: Line cards, one at a time Standby control card (e.g., GCM) Active control card CLI command sequence: For cards 1 to n (in the order described above): exec upgrade switch-to-stdby-load slot <slot#> Are you sure you want to execute this command? YES. To revert a single card exec equipment restart slot <slot#> Are you sure you want to execute this command? YES. To revert all node software: exec node restart Are you sure you want to execute this command? YES. Traffic will go down until the cards come back up. 12 Upgrade Guide, Release TR5.0.x

15 Table 10 Revert Node Software (continued) 3 Verify the node software level has been revised to the desired version and that the system is running the desired software load. 4 The Revert Node Software procedure is complete. If problems occur, call the Technical Assistance Center. Revert TransNav Management System Software. Table 11 Revert TransNav Management System Software 1 Stop the upgraded TransNav server. 2 Start the previous version of software on the TransNav server. 3 Open the previous software version of the Client GUI. Verify the nodes and services are correct (i.e., nodesync/com are cleared). Note: Provisioning done after the upgrade may be lost 4 The Revert TransNav Management System Software procedure is complete. Upgrade Guide, Release TR5.0.x 13

16 14 Upgrade Guide, Release TR5.0.x

17 Chapter 2 Release TR5.0.x Traverse Software Upgrade Introduction Release TR4.0.x Upgrade Overview This chapter provides the following information including steps on how to initiate and complete software upgrades to Traverse nodes in your network using the TransNav GUI. Complete the TR5.0.x software upgrade of all cards in a Traverse node using the release TN6.0.x TransNav management system graphical user interface (GUI). Release TR4.0.x Upgrade Overview Node Software Upgrade Flowchart (Top Level) Before You Begin Compatibility and Guidelines Traverse Node Software Upgrade Process User selectable FPGA Upgrade Capability To revert a software upgrade to a previous version, see Chapter 1 Software Upgrades, Revert Node Software. On SONET systems only, to upgrade software to TE-206 nodes using the TransNav GUI, see the following information: Overview to Upgrade TE-206 Nodes from TransNav Requirements for Upgrading TE-206 Node Software Downloading TE-206 Node Software Upgrading TE-206 Node Software from TransNav Release TR5.0.x provides a unified release for the Traverse and TransNav products supporting SONET and SDH networks and services. This software release supports: Traverse in-service software upgrade to TR5.0.x from the following previous releases: TR3.0.x, TR3.2.1, TR3.2.2, TR3.2.3, TR3.2.3.x, TR3.2.4, and TR4.0.x. Point releases (as necessary) for the TR5.0.x Traverse nodes. Upgrades of TE-206 nodes from the TransNav system (SONET only). User-selectable Field Programmable Gate Array (FPGA) upgrade capability. Upgrade Guide, Release TR5.0.x 15

18 Simultaneous TransNav Management System (TN6.0.x) software management of the following associated releases: Traverse Releases TR3.0.x, TR3.2.1, TR3.2.2, TR3.2.3, TR3.2.3.x, TR3.2.4, and TN4.0.x TE-100 nodes on Release TE3.2.3 TE-206 nodes on Release R04.06.x (SONET only) Note: If your systems are on an earlier release, contact your Sales representative. 16 Upgrade Guide, Release TR5.0.x

19 Node Software Upgrade Flowchart (Top Level) The diagram below shows a top-level flow for the node software upgrade process. Node Software Upgrade Top-Level Flowchart IMPORTANT! For details, refer to the specific software upgrade procedures in the manual or contact the Technical Assistance Center. Begin Read release nodes, upgrade compatibility notes, guidelines, and all upgrade procedures Operations Manager Operations Manager creates a comprehensive upgrade plan Upgrade Team Read and understand the release notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company's comprehensive upgrade plan Old or unsupported software? YES Contact your Sales representative End NO Major release? NO YES Follow the Node Upgrade Process Card upgrade End OPS Figure 12 Node Software Upgrade Process Flowchart Upgrade Guide, Release TR5.0.x 17

20 Before You Begin Review these requirements before you begin. Table 13 Traverse Node Software Upgrade Requirements Requirement Compose and have ready for the Upgrade Team a comprehensive network upgrade plan. Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company s comprehensive upgrade plan. The software upgrade feature for this release supports Traverse TR3.0.x, TR3.2.2, TR3.2.3, TR3.2.3.x or TR3.2.4 and TR4.0.x to TR5.0.x and TransNav TN4.2.x to TN.6.0.x upgrades. Have the required equipment and tools ready. Reference Your company s Operations Manager is responsible for this task. See Release Notes TR5.0.x and TN6.0.x Read through this entire chapter If you have TE-206 nodes in your (SONET only) network, read the TraverseEdge 206 Users Guide, Chapter 18, Maintenance. Contact your company s Operations Manager. If you are upgrading from an earlier Traverse or TransNav software release, contact the Force10 Technical Assistance Center. Chapter 4 Replacing Existing Traverse Hardware, Required Equipment and Tools Requirements for Software Upgrade Compatibility and Guidelines The following items are required for a Traverse system software upgrade to a node or multiple nodes in a domain: TransNav management system server connected to a gateway Traverse node Identify spare cards and have them available for upgrade Access to the Force10 corporate website at Note: Use this procedure to download the management server software from the Force10 Networks corporate website. A Customer Portal Account is required. Read the compatibility topics that are relevant to your specific upgrade. Traverse System Software Upgrade Compatibility Notes Guidelines for Software Upgrade For information on general software compatibility of control cards, management software and replacement cards, see Chapter 1 Software Upgrades, General Software Compatibility. 18 Upgrade Guide, Release TR5.0.x

21 Traverse System Software Upgrade Compatibility Notes Guidelines for Software Upgrade Review this information to understand the important compatibility items for Traverse and TransNav software releases. General. Release TN6.0.x TransNav management system software: manages the in-service software upgrade from Release TR3.0.x, TR3.2.2, or TR3.2.3, TR3.2.3.x, TR3.2.4 or TR4.0.x manages a network of mixed nodes running Release TR3.0.x, TR3.2.2, or TR3.2.3, TR3.2.3.x, TR3.2.4, or TR4.0.x for functions including: - Service management (provisioning, activation, deactivation, deletion, etc.) - Alarms and performance monitoring (on-demand and periodic) - Node and card addition and deletion - Loopback - External commands on protection groups manages a network of mixed nodes running TraverseEdge 100 (TE-100) Release TE manages a network of mixed nodes running TraverseEdge 206 (TE-206) Release R x No longer recognizes any legacy Ethernet configuration data and does not store it in the TransNav database. The upgrade capability manages the arrival of older version cards and allows for download and activation of such cards to the TR5.0.x release. Line-derived timing cards (e.g., OC-3/STM-1) support only one timing reference. When a service provider replaces an old card with a new card, they should plan for and make the line-derived timing reference provisioning changes accordingly (i.e., move the timing references to different cards). Upon in-service replacement, the Traverse system raises and alarm and uses the timing reference of the lowest-numbered port on the card that was previously provisioned with multiple timing references, and ignores the timing provisioning for the higher-numbered ports. The Traverse system allows in-service replacement and upgrade of a UTMX-24 card with a UTMX-48 card, but not vice versa. Software Upgrade for TR5.0.x Release. Hitless software upgrades and warm restarts are available unless otherwise noted in the specific maintenance software Release Notes. Software Upgrade from Traverse Releases. Support for in-service Traverse node software upgrades from Release TR3.0.x, TR3.2.2, or TR3.2.3, TR3.2.3.x, TR3.2.4, or TR4.0.x for all network topologies: UPSR, BLSR, linear 1+1 chain, mesh, or combinations of these topologies. Review the following guidelines for software upgrades: Review the requirements in Requirements for Software Upgrade Conduct upgrades in a specific maintenance window when you expect no user-initiated service state changes. For larger network upgrades, the entire upgrade process may span several nights. Force10 suggests starting the upgrade from the farthest node of the network (if possible) and work towards the server. Upgrade Guide, Release TR5.0.x 19

22 Do not perform any new service creation, deletion, activation or deactivation (e.g., for Ethernet or End-to-End services) until you complete the upgrade on the TransNav server and all network nodes. Verify that all communication links between nodes are operational and have no loss of signal (LOS) or data communications channel (DCC) alarms. Do not change any fiber/link or other network (node, slot, port) objects during the upgrade. Perform an upgrade on spare cards, unless you plan to upgrade spares at a later time (see User selectable FPGA Upgrade Capability for details). Software upgrade is to be errorless. Release Notes for TR5.0.x define any potential exceptions. This document resides on the Force10 website at on the Customer Support website. A Customer Portal Account is required. If you do not have a Customer Portal Account, you can request one from the Force10 website at by selecting Services & Support, then Account Request. 20 Upgrade Guide, Release TR5.0.x

23 Traverse Node Software Upgrade Process Traverse and TransNav support in-service software upgrades from Release TR3.0.x, TR3.2.2, or TR3.2.3, TR3.2.3.x, TR3.2.4, or TR4.0.x to TR5.0.x. Note: If you have one or more nodes in your system with a node name that begins with a number, call the Force10 Technical Assistance Center before upgrading. Note: If you have TE-206 nodes that are managed by TransNav in a SONET only system, see the TraverseEdge 206 Users Guide, Chapter 18, Maintenance, for upgrade instructions. Complete the software upgrade procedures in the following order: Table 14 Traverse Node Software Upgrade Process Reference 1 Have you read through, and do you understand, all the Before You Begin items? 2 Do you have the items required for upgrade ready? 3 Upgrade the Traverse software (includes first exporting the current database off the TransNav server). Note: Do not uninstall the previous version. Mark the directory as -old and remove the Icon from the desktop. Note: NETSYNC alarms will be present when you start the GUI, after the server software upgrade, and before upgrading the node software. The master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects. NETSYNC alarms must be manually cleared by the user once all nodes are upgraded. 4 Download the new Traverse node software to the TransNav server. Before You Begin Requirements for Software Upgrade TransNav Management System GUI Guide, Chapter 3 Administration s, Upgrade Server Software Chapter 1 Software Upgrades, Download Traverse Node Software to the TransNav Server 5 Download the software to the cards. Card Software Download Set-up 6 Activate the new software. Software Activation Process 7 The Traverse Node Software Upgrade Process is complete. Upgrade Guide, Release TR5.0.x 21

24 Card Software Download Set-up Software upgrades are done at the node level. Prior to upgrading the software, an FTP server must be set up to allow the software to be downloaded to the node from an accessible directory on a server. FTP Server Setup. Use the following steps to set up the FTP server: Start the FTP service Configure the FTP service with a username and password Make sure the service can ace ss the directory where the node software was unzipped The following procedure provides steps on how to begin a software upgrade by setting software download times for each card using the SW Upgrade dialog box. Note: (Traverse only.) It takes a fully loaded Traverse-specific node 20 to 60 minutes to download the new software onto all cards. The time required to download software is dependent on the IP bandwidth available to the Traverse node and the type of GCM that is installed. Force10 recommends downloading no more than three nodes at a time. Download times can increase if there are multiple nodes using the same DCC channel for downloading software files. The software download process is completely non-service-affecting. It does not require you to stand by during the download. Table 15 Card Software Download Set-up 1 In Shelf View, select SW Upgrade from the Admin menu to display the SW Upgrade dialog box. Figure 16 Software Upgrade Dialog Box 2 Server IP Address: Enter the TransNav server IP address where the new node software version was downloaded. (For example: aaa.bbb.ccc.ddd) 3 Base Path: Enter the directory path on the TransNav server to the node software files. (For example: /files/node/flash) 4 Username: Enter the user name with File Transfer Protocol (FTP) permission access to the TransNav server where the new node software version resides. (For example: ftpusername) 22 Upgrade Guide, Release TR5.0.x

25 Table15 Card Software Download Set-up (continued) 5 Password: Enter the user password with FTP permission access to the TransNav server where the new node software version resides. (For example: ftppassword) 6 Click Update and verify that there were no errors in the FTP session. Note: This action should fill in the data for each installed card in the Relative Path columns. Verify the Relative Path is set for each installed card. Relative Path: A literal sub-directory path (in relation to the Base Path directory) where the software resides for each card. It is based on the type of card in the slot and is case sensitive. For example: ds3 Important: The Relative Path and Upgrade Type values must be set by the system before the download starts. The default upgrade type is INIT. Upgrade Guide, Release TR5.0.x 23

26 Table 15 Card Software Download Set-up (continued) 7 Use the following steps to bulk download the software. To manually set the download time, skip to step 8. From the SW Upgrade dialog box, click the Bulk Config command button. The Upgrade Helper dialog box displays. Figure 17 Upgrade Helper Dialog Box Download Time: Set the time to begin the download. Approximate software download times for Control cards is 5 to 10 minutes; for all other cards the download time is 2 to 5 minutes. The download for all cards on a node can be started simultaneously. Valid values are: Now: Start the upgrade now. Set time: Click the up and down arrows to set the specific time. If a specific time is entered, all cards will be scheduled to start download at that time. Clear time: Clear the time and start over. Note: Now will always work, but the node must have a valid NTP server configured for future scheduling to work correctly. Upgrade Type: Select one of the following options: INIT (default): Completely erase backup partition of cards and copy all files.always use this option unless working with Force10 Technical Assistance. MERGE: Do not erase backup partition; overwrite existing files and add new files. Automatically fill in rel. paths for equipped slots: The system automatically fills in the Rel Path column on the main software upgrade screen. Click OK to apply the bulk download options. 24 Upgrade Guide, Release TR5.0.x

27 . Table15 Card Software Download Set-up (continued) 8 To manually set the download time, you can Clear Download Time for any card by right-clicking the card in the SW Upgrade dialog box and clicking the Update button. If necessary, you can Abort Download to any card by right-clicking the card in the SW Upgrade dialog box. Note: Force10 recommends that you do not leave the card in the upgrade abort state. Clear the download time and click the Update button to clear the abort state. Figure 18 SW Upgrade Clear Download Time Note: From the Download Time drop-down box, select Set time to manually adjust the time. Select part of the time string (e.g., month, day, hour). Use the up and down arrows or manually re-enter the time to reset the value. Figure 19 Software Upgrade Download Times Upgrade Guide, Release TR5.0.x 25

28 Table 15 Card Software Download Set-up (continued) 9 Click Update on the SW Update dialog box to start the downloads. The software upgrade begins based on the dates and times entered in the Download Time field. You do not have to stand by during the software download; it does not affect traffic or system performance. You can view the status of the software upgrade in the Download Status field of the SW Upgrade dialog box. The following status displays: NONE: The software download has not begun. INPROGRESS: The software download has begun, but is not complete. OK: The software download has successfully completed. ABORTED: The software download has stopped. FAILED: The software download has failed. Retry the software download. Contact Force10 s Technical Assistance Center if the software download fails a second time. 10 Continue only when the Download Status is OK and the newly downloaded software version displays in Standby SW Version field for all cards to be upgraded (select each card row and check the Standby SW Version field). This indicates the software download has successfully completed. 11 The Card Software Download Set-up procedure is complete. For Traverse, depending on the procedure where you started, return to either: 6 of the Node Software Upgrade Flowchart (Top Level) 3 of the Spare Card Software Activation (All Other Types) For TE-100, return to 6 of the Traverse Node Software Upgrade Process. Software Activation Process The new software is not active until the software is activated and system reboots each card. The reboot loads and executes the new software and, in the case of the control card, upgrades the database. Important: Read all important notes below before beginning the activation process. Important: Software activation should start at the node farthest from the server that is connected to the head-end node, then work inward. 26 Upgrade Guide, Release TR5.0.x

29 Important: Any unprotected traffic residing on an Enhanced GCM (EGCM) with Optics or VCX daughter card will experience an outage until the EGCM is restored from activation if a cold reboot is performed. Important: During software activation, the card automatically reboots. Do not execute any external commands on the cards during software activation. Important: If you are performing software activation on an Ethernet card that is using RSTP, selecting the warm reboot option may result in service interruption of network-wide Ethernet applications that include Bridge services on that card. Force10 recommends that you deactivate Bridge services on an Ethernet card that is using RSTP before scheduling a software upgrade with a warm reboot of that card. Important: Due to re-partitioning of the FLASH chip, GCM upgrades to will take approximately 8 to 10 minutes per GCM to upgrade instead of the 2 to 3 minutes necessary to upgrade releases prior to TR The Power LED on the GCM cards will blink red/green while the Active Standby light remains dark. The Major/Critical and Minor LEDs may blink or may remain dark. THIS IS EXPECTED BEHAVIOR FOR UPGRADES TO THIS RELEASE. Upgrade Guide, Release TR5.0.x 27

30 Table 20 Software Activation Process Reference 1 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server? 2 Did you download the node software to the TransNav server? 3 Is the card software download complete? 4 Activate software for: Standby GCM Spare (standby) GCM(s). Unless you plan to upgrade your spare cards at a later time. See page -44 Active GCM 5 Activate software for all cards set up in a protection group in the following order: protecting card working card 6 Activate software for all unprotected cards. 7 Upgrade software for all other types of spare cards, unless you want to upgrade your spare cards at a later time. TransNav Management System GUI Guide, Chapter 3 Administration s, Upgrade Server Software Traverse Node Software Upgrade Process FTP Server Setup Control Card Software Upgrade Activation Software Upgrade Activation (All Other Protected Cards) Activate Software (All Unprotected Cards) Spare Card Software Activation (All Other Types) 8 The Software Activation Process is complete. 28 Upgrade Guide, Release TR5.0.x

31 Control Card Software Upgrade Activation The new software is not active until the system reboots each card. The reboot activates the backup partition with the newly downloaded software on the control card at each node. Important: Do not start the Activate Software Control Card procedure until the downloaded software version displays. This indicates the software download has completed successfully. The software version displays in the SW Activation dialog box, Standby SW Ver field for all cards. The activation is scheduled for each card based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for node GCMs. Table 21 Activate Software Control Card 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a control card and click the Config tab. 3 Click the standby control card Activate Time field in the SW Activation dialog box; the current date and time displays. Figure 22 SW Activation Activate Time 4 Select the activation type Act Type. Always set the activation type to SA. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control card. SA (service-affecting): Will activate and reboot the control card regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control card. Do not use this option for upgrading operational control cards. 5 If the card does not require a cold restart, then always select to warm reboot (Warm Rbt). Upgrade Guide, Release TR5.0.x 29

32 Table 21 Activate Software Control Card (continued) 6 Always ignore the FPGA Upgrade check box. See User selectable FPGA Upgrade Capability for details about this parameter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Force10 recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 7 Click Update. 8 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status displays: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Contact Force10 Technical Assistance if the software activation fails. Note: If the Ignore FPGA check box was selected, clear the check box and click Update. If the activation fails again, contact Force10 Technical Assistance 9 Verify that the new software version activation is complete and it displays in the SW Activation dialog box, Current SW Ver field. Important: If there are any unexpected discrepancies here, STOP and contact Force10 Technical Assistance Figure 23 Act Status and Current SW Ver Fields 10 With the standby control card selected in Shelf View, select the Alarms tab and check the Alarms dialog box. Verify that the following alarms caused by the reboot have cleared: EQFAIL, EQRMV, EQCOMM, DBRED 11 A SWMIS: Software version mismatch alarm is generated since the standby control card software version is now mismatched with the active control card. This is normal behavior. 30 Upgrade Guide, Release TR5.0.x

33 Table 21 Activate Software Control Card (continued) 12 If you have spare control cards to software upgrade at this time, remove the standby control card from the shelf and install the spare (standby) control card. Complete the Spare Control Card Software Activation procedure. Note: The spare GCM must be compatible with the existing GCM. If it is not, special steps must be take to upgrade the spare card. 13 Repeat s 3 through 8 on the active controller. 14 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Contact the Force10 Technical Assistance if the software activation fails a second time. Note: If the Ignore FPGA check box was selected, clear the check box and click Update. If the activation fails again, contact Force10 Technical Assistance. Important: The activation status will show INPROGRESS, then NONE until the card has completed the upgrade; then it will show OK. This is normal behavior. 15 Verify that the new software version activation is complete and it is displayed in the SW Activation dialog box, Current SW Ver field. Note: Activating the active control card causes the new software to upgrade and a switchover to the standby controller. 16 From Shelf View, select the Alarms tab. Check the Alarms dialog box to verify the following alarms, caused by the reboot, have cleared: EQFAIL, COM, EQRMV, EQCOMM, DBRED 17 The SWMIS: Software version mismatch alarm generated on the previously standby control card clears as both control card software versions now match. However, this alarm is now generated for all other cards in the system as their software versions are now mismatched with the control cards. This is normal behavior. 18 The Control Card Software Upgrade Activation procedure is complete. Continue to 5 of the Software Activation Process. Upgrade Guide, Release TR5.0.x 31

34 Software Upgrade Activation (All Other Protected Cards) Follow these step-by-step instructions to set up software upgrade activation for all other protected cards. Important: Upgrade the entire protection group first before continuing to the next protection group. Table 24 Software Upgrade Activation All Other Protected Cards 1 Proceed with software upgrade activation for other protected cards after the software activation has successfully completed on both the control cards (Act Status=OK) and any service-affecting alarms on the node are cleared. Always activate one card a time. Activate the standby card first and then the working cards. Software upgrade activation on other protected cards should be performed in the following order for all cards set up in a protection group: VT cards Optical cards (OC-3 through OC-192) GBE cards All other cards 2 Verify and record the standby/active status for cards/ports set up in a protection group. Refer to the Verify Protection Status procedure for more details. 3 Click the standby card Activate Time field to display Now. Figure 25 SW Activation Activate Time 4 Set the activation type Act Type to SA for the card. Valid types are: NSA (non-service-affecting): Default. Will not activate a card if it has any active services. SA (service-affecting): Activates the software and reboots the card regardless of any services. 32 Upgrade Guide, Release TR5.0.x

35 Table 24 Software Upgrade Activation All Other Protected Cards (continued) 5 Leave the FPGA upgrade check box clear to allow the FPGA to update. See User selectable FPGA Upgrade Capability for details about this parameter. 6 Warm restart the card. Select the Warm Rbt checkbox. 7 Click Update. 8 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following statuses display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation with the Warm Rbt check box cleared. Contact Force10 Technical Assistance if the software activation fails a second time. 9 Verify that the new software version is displayed in SW Activation dialog box, Current SW Ver field. Figure 26 Act Status and Current SW Ver Fields 10 With the card selected in Shelf View, check the Alarms dialog box to verify the following alarms have cleared: EQCOMM (communication link failed): caused by the reboot EQRMV (equipment removed): caused by an improperly seated or removed card SWMIS (software mismatch): caused by a software version mismatch with the active control card. 11 Repeat s 3 through 10 for each working card in the protection group. 12 Repeat s 2 through 11 for the next protection group. 13 The Software Upgrade Activation All Other Protected Cards procedure is complete. Continue to 6 of the Software Activation Process. Upgrade Guide, Release TR5.0.x 33

36 Activate Software (All Unprotected Cards) Use the following step-by-step instructions to set up software upgrade activation for all unprotected cards: Table 27 Activate Software All Unprotected Cards 1 Proceed with software upgrade activation on all unprotected cards after the software activation has successfully completed (Act Status=OK) on both the control cards and then other protected cards before clearing any service-affecting alarms on the node. 2 On the SW Activation dialog box, click the unprotected card Activate Time field to display Now. 3 In the activation type (Act Type) column, set the value to SA for the card. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control card. SA (service-affecting): Will activate and reboot the control card regardless of its active or standby status. 4 Warm restart the card. Select the Warm Rbt check box. 5 Click Update. 6 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation with the Warm Rbt check box cleared. Contact Force10 Technical Assistance if software activation fails a second time. 7 Verify the new software version displays in SW Activation dialog box, Current SW Ver field. Figure 28 Act Status and Current SW Ver Fields 34 Upgrade Guide, Release TR5.0.x

37 Table 27 Activate Software All Unprotected Cards (continued) 8 With the unprotected card selected in Shelf View, check the Alarms dialog box to verify the following alarms have cleared: EQCOMM (communication link failed): caused by the reboot EQRMV (equipment removed): caused by an improperly seated or removed card SWMIS (software mismatch): caused by a software version mismatch with the active control card. 9 Repeat s 2 through 9 for all unprotected cards. 10 Verify the network is alarm free, or validate and record any alarms present after the upgrade. 11 Verify the restoration of all the services. 12 The Activate Software All Unprotected Cards procedure is complete. Depending on the procedure from which you came, continue to either: 7 of the Software Activation Process 4 of the Spare Card Software Activation (All Other Types) Upgrade Guide, Release TR5.0.x 35

38 Spare Control Card Software Activation The new software is not active until the system activates the software and reboots the spare (standby) control card. The reboot loads and executes the new software. Important: This procedure assumes you have completed upgrading (downloading and activating the new software for) the standby and active control cards. Important: If the software versions are different, call Force10 Technical Assistance for assistance Important: A spare control card can only be upgraded in a shelf that has the same type of control card. For example, if the standby Traverse GCM is a GCM with OC-48 card, you can only upgrade GCM with OC-48 cards in this procedure. If the standby TE-100 system card is an OC-48 card, you can only upgrade with another OC-48 system card. Follow these step-by-step instructions to set up software upgrade activation for spare control cards. Table 29 Activate Software Spare Control Cards 1 Remove the upgraded standby control card by restarting the card through the TransNav management system, then removing the card from the shelf. 2 Insert the spare (standby) control card. 3 Once the spare control card is online and the EQRMV alarm is clear, download the new software version to the card using the FTP Server Setup procedure. Note: From this point, you have up to 30 minutes to complete the download and activation software process. The card software versions and other data will be invalid until the upgrade is complete. Note: The EQCOMM alarm will not clear. The standby states and software versions will not be updated. 4 Once the new software downloads to the spare control card, activate the software using the steps described for the standby control card in the Control Card Software Upgrade Activation procedure. 5 Repeat s 1 through 4 for each spare control card. 36 Upgrade Guide, Release TR5.0.x

39 Table 29 Activate Software Spare Control Cards (continued) 6 Once the upgrade and activation is complete for all the spare control cards you can either: Leave the last spare in place to act as the new standby card. You must reboot the card again. Restore the original standby control card into the standby slot. 7 The Activate Software Spare Control Cards procedure is complete. Depending on the procedure from which you came, continue to 18 of the procedure Control Card Software Upgrade Activation Upgrade Guide, Release TR5.0.x 37

40 Spare Card Software Activation (All Other Types) The new software is not active until the system activates the software and reboots the spare cards that are not control cards. The reboot loads and executes the new software. The activation is scheduled for each card based on the date and time entered in the Activate Time field of the SW Activation dialog box. Use the following step-by-step instructions to set up the software upgrade activation for the spare cards. Table 30 Activate Software Spare Cards (All Other Types) 1 Insert the spare card in an unused slot in the shelf. 2 Once the spare card is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the card using the procedure, Card Software Download Set-up. If the software on the spare card is incompatible with the active controller, the system will raise an EQINCMPSW alarm. 3 Once the new software downloads to the spare card, activate the software using the steps described in the procedure Software Upgrade Activation (All Other Protected Cards). 4 Repeat s 1 through 3 for each spare card. 5 The Activate Software Spare Cards (All Other Types) procedure is complete. Continue to 8 of the Software Activation Process. 38 Upgrade Guide, Release TR5.0.x

41 Verify Protection Status Follow these step-by-step instructions to verify the protection status (Standby or Active) of a card/port in a protection group: Table 31 Verify Protection Status 1 From Map View, double-click on a node to display the Shelf View. 2 Click the Protection tab to display the Protection Groups dialog box. Figure 32 Protection Groups Dialog Box 3 Select the protection group. 4 Click Edit to display the Protection Group Configuration dialog box. 5 The status displays in the Protection field - either Active or Standby. Figure 33 Equipment Protection Group Configuration Dialog Box 6 The Verify Protection Status procedure is complete. Continue to 3 of the procedure Software Upgrade Activation (All Other Protected Cards). Upgrade Guide, Release TR5.0.x 39

42 Perform a Forced Switch Use the following step-by-step instructions to perform a user-initiated forced protection switch on a 1:N equipment protection only. Table 34 Perform a Forced Switch 1 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 2 Select the protection group. Figure 35 Protection Groups Dialog Box 3 Click Edit to display the Protection Group Configuration dialog box. 4 Right-click the card or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Forced from the shortcut menu. Figure 36 Protection Group Forced Switch 5 The Confirm Force Switch dialog box displays. Click Yes to confirm. 6 Verify the card shows a FORCED alarm (forced protection switch). 7 The active card or port is switched to standby. 40 Upgrade Guide, Release TR5.0.x

43 Perform a Manual Switch For cards in a protection group requiring a cold restart activation due to FPGA changes, a manual protection switch may be performed. Follow these step-by-step instructions to perform a manual protection switch to switch the active card (with the old software) from the active to the standby state. Table 37 Perform a Manual Switch 1 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 2 Select the protection group. Figure 38 Protection Groups Dialog Box 3 Click Edit to display the Protection Group Configuration dialog box. 4 Right-click the card or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Manual from the shortcut menu. Figure 39 Protection Group Manual Switch 5 The Confirm Manual Switch dialog box displays. Click Yes to confirm. Upgrade Guide, Release TR5.0.x 41

44 Table 37 Perform a Manual Switch (continued) 6 The active card or port is switched to standby. 7 The Perform a Manual Switch procedure is complete. If you were in the procedure: Control Card Software Upgrade Activation, then return to 13. Software Upgrade Activation (All Other Protected Cards), then return to Upgrade Guide, Release TR5.0.x

45 Clear Protection Switch Use the following step-by-step instructions to clear (release) a user-initiated protection switch. Table 40 Clear Protection Switch 1 From Map View, double-click on a node to display the Shelf View. 2 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 3 Select the protection group. Figure 41 Protection Groups Dialog Box 4 Click Edit to display the Protection Group Creation dialog box. 5 Right-click the Standby card/port in the Protection Group Creation dialog box to display a shortcut menu. Select Clear from the shortcut menu. Figure 42 Protection Group Clear Protection Switch 6 The Confirm Release dialog box displays. Click Yes to confirm the force switch release. Upgrade Guide, Release TR5.0.x 43

46 Table 40 Clear Protection Switch (continued) 7 Verify that the protection alarm has cleared. The standby card or port is switched back to its original active status. 8 The Clear Protection Switch procedure is complete. User selectable FPGA Upgrade Capability In some cases, upgrading from one Traverse release to another requires a new FPGA image for a card or set of cards. Accepting this new FPGA image can resolve an issue that is unique to a certain deployment. The user-selectable FPGA upgrade capability (force warm reboot) gives you the choice to ignore the FPGA card software change because it is non-critical in nature to your deployment. This capability allows the upgrade to proceed in a hitless fashion without loading the new FPGA image. Important: If a decision has been made to use Ignore FPGA, Force10 recommends performing a cold reboot to load the new FPGA image as soon as possible during a network maintenance window. From the SW Activation dialog box, if you select to ignore the new FPGA image and the existing FPGA image remains compatible with the new software, the system performs a warm upgrade for the card. Figure 43 User-selectable FPGA Upgrade Parameter 44 Upgrade Guide, Release TR5.0.x

47 Overview to Upgrade TE-206 Nodes from TransNav The TransNav GUI can be used to manage SONET systems that include TE-206 nodes using functions including performing software downloads, upgrades, commits and fallbacks to TE-206 nodes. The following directories have been added to the Force10 EMS directory on the management server to facilitate managing TE-206 nodes: nodedb, nodesoftware, and tl1log. From the TransNav GUI, the following basic functions can be performed on the TE-206 nodes: Software Upgrade: The complete process of downloading software to the NE and switching the running software on the NE from a previous version to a newer version. Software Upgrade (using the EMS) can only be performed on one NE at a time. If the software has already been downloaded onto the NE, the software upgrade process automatically skips the download step. The NE undergoes a soft reset during the software upgrade process which is non-traffic affecting, however, communication to the node is lost during the upgrade process. After the upgrade process the new software will be in the Not Commit State. In this state, the software will automatically Fallback to the previous load as a result of an NE reset. To prevent this from happening, you should transition the NE to either the Commit or Commit with Fallback state. Software Download: The process of transferring the software from the EMS to the NE. It is a subset of the Software Upgrade process. Software Download is available as a separate function for two reasons; Use the Software Download function if you prefer to download the new software to the NE at one point in time, and then upgrade the NE to the software at a future point in time (possibly during the maintenance window that night); Use the Software Download function to download the software on multiple NEs simultaneously. Note: To fully upgrade an NE, use the Software Upgrade feature. If you want to bulk software download first and then upgrade at a later time, first use Software Download and then Software Upgrade. NE Software Commit: After an NE has been upgraded to new software, the NE is in the Not Commit state. In this state the software will automatically Fallback to the previous load as a result of an NE reset. To prevent this from happening, move the NE to either the Commit or Commit with Fallback state. Committing software locks the new software load into the NE. The states are described below: Not Commit: Default state after a software upgrade. In the Not Commit state, an NE reset causes the node to Fallback to the previous software version. Commit - Software has been Committed on the NE. There is no Fallback option after the NE has entered the Commit state. Commit with Fallback: (CommitFallBk) Commit the software on the NE, but allows you the option of falling back for a specified period of between 1 and 120 hours. After the fallback timer expires, the node automatically transitions to the Commit state. Fallback: Software fallback is the process of reverting the software back to the old version from the new version. This is usually done because a problem has been discovered on the new software load. Fallback can only be performed on a node that is in the Not Commit state or the Commit with fallback state. Upgrade Guide, Release TR5.0.x 45

48 Resolve Firmware Mismatch: If the NE contains new software that is expecting new firmware, the NE generates a firmware mismatch alarm. The EMS resolves the firmware mismatch alarm by loading the new firmware into the node. The new firmware may be part of the software load that is downloaded, but it is not upgraded during software upgrade. To resolve the firmware mismatch, the EMS must hard reset the NE which causes at least one traffic switch during the hard reset process. Resolve Software Mismatch: If the NE contains software on one or more CCTs that does not match the rest of the node, the NE generates a software mismatch alarm. The EMS resolves this software mismatch alarms by loading the correct software on all the mismatched CCTs and performs a software upgrade (after user confirmation) on the system components that contain the incorrect version of software. This process is non-service affecting. Figure 44 NE Software Dialog Box, View Software TID - The TID of the NE Vendor - The maker of the NE. Model - The model number of the NE. Current Version - The currently running version of the NE software Secondary Version - The software loaded in the NEs secondary bank of RAM. If software has been downloaded but not yet upgraded, it appears in the Secondary Version field. During a software upgrade, the software loaded in the secondary bank becomes the currently running version of software; the current version becomes the secondary version. Latest Version Available - This field is related to the software loads on the TransNav Server. It displays the latest version of software available in the TransNav software download directory for the given NE type. Status - The current status of the software on the NE (Commit, Not Committed, Commit with Fallback, Commit with FWMM, or Disconnected). 46 Upgrade Guide, Release TR5.0.x

49 Requirements for Upgrading TE-206 Node Software Downloading TE-206 Node Software Review the following guidelines prior to upgrading TE-206 node software from the TransNav GUI in a SONET-only system: TE-206 nodes must be running release R software to be discovered by TransNav release TN4.2.3 or higher. (TE-206 nodes running Release R or lower must be upgraded from an external application, such as TN-Xpert or TN-Sight/TL1). Upgrades of TE-206 node software from the TransNav GUI must be performed manually; they cannot be scheduled. Upgrade software version must be in the nodesoftware directory in the EMS directory on the server prior to upgrading TE-206 node software. Downloads can be performed across multiple TE-206 nodes simultaneously. Use the following procedure to download node-level software from the TransNav management system in a SONET-only system for discovered TE-206 nodes for upgrade at a later time. Prior to downloading the TE-206 software, be sure the requirements for upgrading the software have been met. For more information, see the section, Requirements for Upgrading TE-206 Node Software. To fully upgrade the software on a node, see the section Upgrading TE-206 Node Software from TransNav. Table 45 Downloading TE-206 Node Software 1 In the TransNav GUI, from Map View select the TE-206 node to update. 2 Select Admin, SW Upgrade. The NE Software dialog box displays. Figure 46 NE Software Dialog Box 3 The current running version and state of the software for the nodes and equipment is listed. Highlight the node to where the software will be downloaded. To download to multiple nodes simultaneously, click the first node, hold the Shift key and click the last node to upgrade. Note: Force10 recommends upgrading a maximum of five nodes at a time. Upgrade Guide, Release TR5.0.x 47

50 Table 45 Downloading TE-206 Node Software 4 While the nodes are highlighted (continue to hold down the Shift key), right-click and select Download from the shortcut menu. The Select Software Version dialog box displays. Figure 47 Select Software Version Dialog Box Select the software version to be used from the Software Versions parameter. 5 Click OK to begin downloading the selected software version. The NE Software Download dialog box displays. 6 Click Start at the bottom of the dialog box to begin the download. The status displays in the Status pane: Figure 48 NE Software Download Dialog Box, Status 7 When the download completes, click Close. 8 The Downloading TE-206 Node Software procedure is complete. 48 Upgrade Guide, Release TR5.0.x

51 Upgrading TE-206 Node Software from TransNav The complete process of downloading software to the node and switching the running software on the node from a previous version to a newer version is performed by an upgrade. This process can only be performed on one node at a time. If the software has already been downloaded onto the node, the download step is ignored. During the upgrade, the node undergoes a soft reset. The soft reset is non-traffic affecting, however communication to the node is lost during the upgrade process. Before beginning the upgrade, be sure the requirements for upgrading the software have been met. For more information, see Requirements for Upgrading TE-206 Node Software. Upgrading TE-206 nodes from TransNav in a SONET-only system consists of first upgrading the software and, if necessary, the firmware and bootloader. Table 49 Upgrading TE-206 Node Software from TransNav 1 In the TransNav GUI, from Map View select the specific TE-206 node to upgrade. 2 Select Admin, SW Upgrade. The NE Software dialog box displays. Figure 50 NE Software Dialog Box 3 Highlight the TE-206 node to be upgraded. Figure 51 Select TE-206 Node to Upgrade Upgrade Guide, Release TR5.0.x 49

52 Table 49 Upgrading TE-206 Node Software from TransNav 4 From the NE Software dialog box, select Actions, Upgrade from the menu or right-click for a pull-down menu. The NE Software Upgrade dialog box displays. Figure 52 TE-206 NE Software Upgrade Dialog Box Click Start at the bottom of the dialog box to begin the upgrade. The upgrade status displays in the Status pane. A node database backup is performed and the software downloaded to the node if it was not previously downloaded. Some items are disabled based on the status of the software on the node. 5 When the software upgrade completes, click Close. 6 If necessary, upgrade the firmware and bootloader. 7 The Upgrading TE-206 Node Software from TransNav procedure is complete. 50 Upgrade Guide, Release TR5.0.x

53 Chapter 3 TE-100 Release TE3.2.3 System Software Upgrade Introduction Release TE3.2.3 Upgrade Overview Complete the ReleaseTE3.2.3 software upgrade of all TraverseEdge 100 (TE-100) modules using the TransNav management system graphical user interface (GUI). This chapter provides the following information including step-by-step procedures on how to initiate and complete software upgrades using the TransNav GUI. Release TE3.2.3 Upgrade Overview Before You Begin Required Equipment and Tools Compatibility and Guidelines Node Software Upgrade Process To revert a software upgrade to a previous version, see Chapter 1 Software Upgrades, Revert Node Software. Release TE3.2.3 provides a unified release for the TE-100 product supporting SONET or SDH networks and services. This software release supports: TE-100 software upgrade from Release TE3.0.x to Release TE3.2.3 not an in-service upgrade In-service software upgrade TE3.2.x point releases (as necessary) for TE-100 nodes TE-100 warm reboot and hitless upgrade features are unavailable Simultaneous TransNav management system node software management to accommodate longer-term upgrade paths: Release TR3.0.0, TR3.2.1, and TR3.2.2 Traverse nodes Release TE3.2.x TE-100 nodes Release R TE-206 nodes Upgrade Guide, Release TR5.0.x 51

54 Before You Begin Review this information before you begin. Table 53 Node Software Upgrade Requirements Requirement Compose and have ready for the Upgrade Team a comprehensive network upgrade plan. Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company s comprehensive upgrade plan. The software upgrade feature for this release supports TransNav 3.0.x to TN3.2.3 upgrades. Have the required equipment and tools ready. Reference Your company s Operations Manager is responsible for this task. Refer to Release Notes TE3.2.3 Read through this entire chapter Contact your company s Operations Manager If you are upgrading from an earlier TransNav software release, contact the Force10Technical Assistance Center (TAC). Required Equipment and Tools Required Equipment and Tools This section lists required equipment and tools for both hardware and software upgrades. Software. The following items are required to upgrade TE-100 system software to a node or multiple nodes in a domain: TransNav management system server connected to a TE-100 node or gateway Traverse node Access to the Force10 corporate website at Note: Use this procedure to install the management server software from the Force10 Networks corporate website. A Customer Portal Account is required. If you do not have a Customer Portal Account, you can request one from the Force10 website at by selecting Services & Support, then Account Request. Hardware. Use the following hardware equipment and tools to place modules in a TE-100 shelf. General. Electrostatic Discharge (ESD) wrist strap. 1-slot wide blank faceplates are required in any empty slots to ensure EMI protection and proper cooling. Blank faceplates must be ordered separately. TE-100 Shelf. 1 or 2 System modules (and any spares) 52 Upgrade Guide, Release TR5.0.x

55 Compatibility and Guidelines TE-100 Platform SW Upgrade Compatibility Notes Guidelines for Software Upgrade Node Software Upgrade Process Read the compatibility topics that are relevant to your specific upgrade. TE-100 Platform SW Upgrade Compatibility Notes Guidelines for Software Upgrade For information on software compatibility of control cards, management software and replacement cards, see Chapter 1 Software Upgrades, General Software Compatibility. Review this information to understand the important compatibility items for the TE-100 and TransNav TN4.2.x software release. TE-100 software upgrade from Release TE3.0.x.y to Release TE This is not an in-service upgrade. In-service TE3.2.x point release software upgrades (as necessary) for TE-100 nodes. TransNav manages the in-service software upgrade for Release TE3.2.x maintenance releases. TE-100 hitless upgrade and warm reboot features are unavailable in this release. Review the following guidelines for software upgrade: Conduct upgrades in a specific maintenance window when you expect no user-initiated service state changes. Start the upgrade from the services egress node of the network (if possible). Do not perform any new service creation, deletion, activation or deactivation (e.g., for Ethernet) until you complete the upgrade on the TransNav server and all network nodes. Do not change any fiber/link or other network (node, slot, port) objects during the upgrade. Due to the use of FTP libraries, bulk software downloads may fail so schedule software downloads to the TE-100 system modules at least 5 minutes apart. Perform an upgrade on spare modules. Software upgrade is to be errorless. Release Notes TN3.2.x define any potential exceptions. Depending on your requirements and current software load, you can choose either a hitless (warm reboot) or a cold reboot (which may be service affecting) upgrade. Complete the software upgrade procedures in the following order: Table 54 Node Software Upgrade Process Reference 1 Have you read through, and do you understand, all of the Before You Begin items? 2 Do you have the required equipment and tools ready? Before You Begin Required Equipment and Tools Upgrade Guide, Release TR5.0.x 53

56 Table 54 Node Software Upgrade Process (continued) Reference 3 Upgrade the TransNav management system server software (includes first exporting the current database off the TransNav server). Note: Do not uninstall the previous software version. Mark the directory as old and remove the icon from the desktop. 4 Download the new node software to the TransNav server. 5 Download the software to the modules. TransNav Management System GUI Guide, Chapter 3 Administration s, Upgrade Server Software Chapter 1 Software Upgrades, System Software Upgrades Download Chapter 1 Software Upgrades, FTP Server Setup 6 Activate the new software. Software Activation Process 7 The Node Software Upgrade Process is complete. Software Activation Process The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software. Important: Read all important notes below before beginning the activation process. Important: Software activation should start at the node farthest from the server that is connected to the head end node, then working inward. Important: During software activation, the modules automatically reboot. Do not execute any external commands on the modules during software activation. Table 55 Software Activation Process Reference 1 Did you complete the upgrade of TransNav EMS server and client software, and download the node software to the TransNav server? 2 Did you download the node software to the TransNav server? See the TransNav Management System GUI Guide, Chapter 3 Administration s, Upgrade Server Software Software Activation Process 54 Upgrade Guide, Release TR5.0.x

57 Table 55 Software Activation Process (continued) Reference 3 Is the module software download complete? 4 Activate software for: Standby control module Spare (standby) control module(s), unless you are using the remote upgrade capability and want to upgrade your spare modules at a later time (see Chapter 2 Release TR5.0.x Traverse Software Upgrade, User selectable FPGA Upgrade Capability). Active control module Chapter 1 Software Upgrades, FTP Server Setup Activate Software - Control Module 5 The Software Activation Process is complete. Continue to 7 of the Node Software Upgrade Process. Upgrade Guide, Release TR5.0.x 55

58 Activate Software - Control Module The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software on the control module. Important: Do not start the Activate Software Control Module procedure until the downloaded software version displays in the SW Upgrade dialog box, Standby SW Ver field for all modules, indicating the software download has successfully completed. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for control modules. Table 56 Activate Software Control Module 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a control module and click the Config tab. 3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box. 3 Figure 57 Card Configuration Protection Status 56 Upgrade Guide, Release TR5.0.x

59 Table 56 Activate Software Control Module (continued) 4 Click the standby control module Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. Figure 58 SW Upgrade Activate Time 5 Change the activation type Act Type (default=nsa) to SA for standby control module activation. Valid values are: NSA (non-service-affecting). Default. Indicates the activation type will not reboot (activate) an active control module. SA (service-affecting): Indicates the activation type will reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Indicates the activation type will reboot the spare (standby) control module. 6 Click Update. Important: View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Force10Technical Assistance Center if the software activation fails a second time. Upgrade Guide, Release TR5.0.x 57

60 Table 56 Activate Software Control Module (continued) 7 Verify the new software version activation is complete and it is displayed in the SW Upgrade dialog box, Current SW Ver field. Important: If there are any unexpected discrepancies here, STOP. Contact the Force10Technical Assistance Center. 8 With the standby control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box. Verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. 9 A SWMIS: Software version mismatch alarm is generated since the standby control module software version is now mismatched with the active control module. This is normal behavior. 10 If you have spare control modules to software upgrade at this time (i.e., you are not using the remote upgrade capability), remove the standby control module from the shelf and install the spare (standby) control module. Complete the Spare Control Module Software Activation, page 60 procedure. 11 Click the active control module Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. Note: You can clear the Activation Time for any module by right-clicking the module in the SW Upgrade dialog box and selecting Clear Activation Time from the shortcut menu. 12 Change the activation type Act Type (default=nsa) to SA for standby control module activation. Valid values are: NSA (non-service-affecting). Default. Indicates the activation type will not reboot (activate) an active control module. SA (service-affecting): Indicates the activation type will reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Indicates the activation type will reboot the spare (standby) control module. 13 Click Update. Important: View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Force10Technical Assistance Center if the software activation fails a second time. 58 Upgrade Guide, Release TR5.0.x

61 Table 56 Activate Software Control Module (continued) 14 Verify the new software version activation is complete and it is displayed in the SW Upgrade dialog box, Current SW Ver field. Note: Activating the active control module causes the new software to upgrade and a switchover to the protection module. 15 With the now standby (previously active) control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box. Verify the EQFAIL: equipment failure alarm caused by the reboot has cleared. 16 The SWMIS: Software version mismatch alarm generated on the previously standby control module clears as both control module software versions now match. However, this alarm is now generated for all other modules in the system as their software versions are now mismatched with the active control module. This is normal behavior. 17 The Activate Software Control Module procedure is complete. Continue to 5 of the Software Activation Process. Upgrade Guide, Release TR5.0.x 59

62 Spare Control Module Software Activation The new software is not active until the system reboots the spare (standby) control module. The reboot activates the backup partition with the newly downloaded software on the spare control module. Important: This procedure assumes you have completed upgrading the standby control module and have not yet activated the active control module. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby Traverse GCM is a GCM with OC-48 module, you can only upgrade GCM with OC-48 modules in this procedure. If the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for spare control modules. Table 59 Activate Software Spare Control Modules 1 Remove the upgraded standby control module by restarting the module through the TransNav management system, then removing the module from the shelf. 2 Insert the spare (standby) control module. 3 Once the spare control module is online and the EQRMV and EQCOMM alarms are clear, download the new software version to the module using the Download Traverse Node Software to the TransNav Server procedure. 4 Once the new software downloads to the spare control module, activate the software using the steps described for the standby control module in the Activate Software - Control Module procedure (using ActType=SPARE). 5 Repeat s 1 through 4 for each spare control module. 6 Once upgrade and activation is complete for all the spare control modules, place the original standby control module back into the standby slot and continue the procedure to activate software on the active control module. 7 The Activate Software Spare Control Modules procedure is complete. Continue to 11 of the procedure Activate Software - Control Module. 60 Upgrade Guide, Release TR5.0.x

63 Chapter 4 Replacing Existing Traverse Hardware Introduction During the course of normal operation, various conditions may arise that require network operations personnel to replace existing system equipment. This section describes Traverse card and fan equipment replacement. Cards. All cards in the Traverse system, including the General Control Modules (GCMs), are hot-swappable and can be removed and replaced while the system is in operation. During replacement procedures, service is interrupted to all connections on the removed cards. For related information about adding and removing cards using the TransNav GUI, see the TransNav Management System Provisioning Guide, Chapter 9 Creating and Deleting Equipment. The card replacement topics in this chapter are as follows: Software Compatibility Software Version Verification Electrostatic Discharge Protection Required Equipment and Tools Replacement Card Type and Software Version Preparing a Card for Removal and Replacement Remove a Card GCM Card Replacement as Standby LED Indicators For guidelines on card placement, see the Operations and Maintenance Guide, Chapter 21 Card Placement Planning and Guidelines. For information on cleaning MPX connectors and installing replacement cards, see the Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards. Fan Equipment. The fan card and fan air filter can be removed and replaced while the system is in operation. For general fan assembly information, see the Traverse Hardware Guide, Chapter 4 Fan Assemblies. The fan equipment replacement topics are as follows: Chapter 5 Upgrade to a Traverse Front Inlet Fan Tray Replace the Front Inlet Fan Tray Card Upgrade Guide, Release TR5.0.x 61

64 Replace the Traverse 600 Fan Assembly Replace the Traverse 600 Fan Assembly Fan Assembly Air Filter Installation (Traverse 600) Software Compatibility Software Version Verification For information on software compatibility of control cards, management software and replacement cards, see Chapter 1 Software Upgrades, General Software Compatibility. You can determine the software version number of a card using the TransNav GUI. The software version and serial number display in the Config tab in Shelf View. Follow these steps to verify the software version. Table 60 Card Software Version Number Verification 1 In Shelf View, click a card to select it. 2 Click the Config tab to view current software version information. Figure 61 Card Configuration Dialog Box 3 The software version displays in the Current SW Version field in the Card Configuration dialog box. Software version numbers are broken down as follows (Current SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software patch to build number 4 The Card Software Version Number Verification procedure is complete. 62 Upgrade Guide, Release TR5.0.x

65 Electrostatic Discharge Protection Required Equipment and Tools Replacement Card Type and Software Version Wear a properly grounded Electrostatic Discharge (ESD) wrist strap during the following installation and maintenance activities to avoid damaging the Traverse integrated circuits: While handling any Traverse card When connecting copper or optical cables to the PDAP, Traverse main backplane, fiber optic backplane, and fan tray card The following hardware equipment and tools are required to place cards in a Traverse shelf. General. Electrostatic Discharge (ESD) wrist strap Eye protection 1-slot wide blank faceplates for any empty slots to ensure EMI protection and proper cooling. Blank faceplates must be ordered separately. Traverse Shelf. MPX cleaning materials to clean fiber optic cable and card MPX connectors: Isopropyl alcohol of at least 91% purity Lint-free wipes Lint-free cleaning swabs with urethane foam heads Pressurized optical duster (canned air) 1 or 2 control cards, as well as any spares System interface module (SIM) cards Note: The number and combination of SIMs is based on your network requirements and physical cabling at the Traverse main and fiber optic backplanes. Card of Same Type and Software Version. When you replace a card with another of the same type and software version, the TransNav management system configures the replacement card in the same way the removed card was configured. Card of Same Type with a Earlier or Later Software Version. Replacement cards that have an earlier version of software earlier than the other cards in the Traverse node will require a software upgrade. Replacement cards that have a later version of software later than the other cards in the Traverse node will require a software downgrade. Refer to Chapter 2 Release TR5.0.x Traverse Software Upgrade for procedures on how to convert software versions on a replacement card. Upgrade Guide, Release TR5.0.x 63

66 Card of Different Type. If you replace a card with a different type of card, an Equipment Mismatch alarm is generated to indicate a failure condition. In the following Map View, the Alarm tab provides an example of an Equipment Mismatch alarm in the TransNav GUI. : Figure 62 Equipment Mismatch Alarm 64 Upgrade Guide, Release TR5.0.x

67 Preparing a Card for Removal and Replacement The following procedures provide step-by-step instructions on how to prepare a card for removal and replacement using the TransNav GUI. For instructions on how to prepare a card for removal and replacement using the CLI, see Using the CLI to Prepare a Card for Replacement. Important: GCM, Enhanced GCM (EGCM), Universal GCM (UGCM), and GCMs with integrated optics are considered different cards and must be physically removed and deleted via TransNav prior to replacement with a different GCM card type to avoid an EQMIS: Equipment Mismatch alarm. Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older GCM cards with the newer GCM cards in a redundant configuration. The following replacement rules apply: Replace: GCM with a UGCM EGCM (without optics) with a UGCM EGCM (with OC-12/STM-4) with a UGCM with 1-port OC-12/STM-4 EGCM (with OC-48/STM-16) with a UGCM with OC-48/STM-16 Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older DS3, E3, EC-1, and DS3 Transmux cards with the newer DS3, E3, EC-1, and DS3 Transmux cards with no greater than 50 ms traffic interruption for each cards in any 1:N (where N=1,2) protection group. Table 63 Preparing a Card for Removal and Replacement 1 In the TransNav GUI, go to Shelf View. 2 Click the card to be removed. 3 Click the Config tab to display the Card Configuration dialog box. 4 Click the Lock icon at the bottom left portion of the screen to change the Administrative state to locked and click Apply. Note: Force10 recommends a forced switchover if you are replacing the working card of a protection group. 5 Physically remove the card from the Traverse shelf. Refer to the procedure Remove a Card for details. You must physically remove the old card from the shelf before deleting it using the TransNav GUI or CLI. The TransNav system will continue to discover the card if it is not physically removed from the shelf. Upgrade Guide, Release TR5.0.x 65

68 Table 63 Preparing a Card for Removal and Replacement (continued) 6 In the TransNav GUI, right-click the card and select Delete Card to delete the card or Replace with Card to replace with a different type of card. 7 Place the new card in the Traverse shelf. Refer to the following sequence of topics for important details: Operations and Maintenance Guide, Chapter 21 Card Placement Planning and Guidelines GCM Card Replacement as Standby LED Indicators (Standby GCM card replacement only.) Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards, Clean Fiber Optic MPX Connectors Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards, Insert a Card 8 Click the Lock icon at the bottom left portion of the screen to change the Administrative state to unlock and click Apply. 9 The Preparing a Card for Removal and Replacement procedure is complete. Using the CLI to Prepare a Card for Replacement. Use the following step-by-step instructions to prepare a card for removal and replacement using the CLI: Table 64 Using the CLI to Prepare a Card for Replacement 1 Before removing a card, use the following node-level command to change the Administrative state of the card to locked: Type: set equipment slot slotnumber adm-state Lock<Enter> 2 Physically remove the card from the Traverse shelf. Refer to the procedure Remove a Card for details. 66 Upgrade Guide, Release TR5.0.x

69 Table 64 Using the CLI to Prepare a Card for Replacement (continued) 3 Use the following node-level command to delete the card: Type: delete equipment slot slotnumber<enter> or Use the following node-level command to replace the card with a different type of card. Type: create equipment slot slotnumber type eqtype force true<enter> Note: eqtype options are: DS3 (DS3/EC-1 Clear Channel), GBE, GCM, OC3, OC12, OC48 and OC Place the new card in the Traverse shelf. See the Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards. 5 Use the following node-level command to unlock the card. Type: set equipment slot slotnumber adm-state Unlock<Enter> 6 The Using the CLI to Prepare a Card for Replacement procedure is complete. Remove a Card Card Placement Guidelines For instructions on how to remove a card, see the Traverse Hardware Guide, Chapter 5 Inserting and Removing Cards, Remove a Card. For guidelines on card placement in specific Traverse shelves, see the Operations and Maintenance Guide, Chapter 21 Card Placement Planning and Guidelines. Upgrade Guide, Release TR5.0.x 67

70 GCM Card Replacement as Standby LED Indicators When a new GCM card is placed as the standby card, the Power and Active/Standby LED indications are as shown in the following table. Table 65 Power and Active/Standby GCM Cards LED RED Amber GREEN OFF Flashing Solid Flashing Solid Flashing Solid Power Initializing; POST is started. Hardware failure detected; replace the card. N/A N/A Node is in commissioning mode Passed initialization and is operational No power Active/ Standby N/A N/A Standby mode; synchronization with the Active card is not complete. Card type does not match the provisioned card type or the card is placed in an invalid slot. 1 Standby mode; synchronization with the active card is complete. Active and operational Initializing; POST is started. 1 Please refer to the Operations and Maintenance Guide, Chapter 21 Card Placement Planning and Guidelines for valid card placement guidelines. Insert a Replacement Card Clean the fiber optic MPX connectors, then insert the replacement module. For instructions on cleaning the fiber optic MPX connectors, see the Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards, Clean Fiber Optic MPX Connectors. For instructions on how to install a card, see the Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards, Insert a Card. 68 Upgrade Guide, Release TR5.0.x

71 Replace the Front Inlet Fan Tray Card The front inlet fan tray assembly is bundled and shipped with the Traverse 1600 and Traverse 2000 systems. For information on replacing the front inlet fan tray assembly, see the Traverse Hardware Guide, Chapter 6 Insert Fan Module and Air Filters, Insert a Traverse 1600 and Traverse 2000 Fan Air Filter. Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan card as it contains static-sensitive components. Note: This procedure is not service affecting if it is completed within 6 minutes. Typical time for completion of this procedure is 3 minutes. Note: Have all necessary materials on the work site prior to beginning this procedure. Note: Normal fan operation is indicated by the green LED being illuminated and the red LED being extinguished. An illuminated red LED indicates a fault condition on that fan card. Replace the Traverse 600 Fan Assembly The Traverse 600 fan card with integral fan tray is bundled and shipped with the Traverse 600 system. For instructions to install the fan assembly, see the Traverse Hardware Guide, Chapter 6 Insert Fan Module and Air Filters. Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan tray card as it contains static-sensitive components. Fan Assembly Air Filter Installation (Traverse 600) The Traverse 600 fan assembly (fan card with integral fan tray) requires a foam air filter that is placed to the left of the fan assembly after the fan card is installed. For instructions to replace the fan assembly for a Traverse 600 shelf, see the Traverse Hardware Guide, Chapter 6 Insert Fan Module and Air Filters, Insert a Traverse 600 Fan Air Filter. Upgrade Guide, Release TR5.0.x 69

72 70 Upgrade Guide, Release TR5.0.x

73 Chapter 5 Upgrade to a Traverse Front Inlet Fan Tray Introduction Precautions and Assumptions This chapter provides upgrade instructions for replacing separate Traverse fan tray and air ramp assemblies with a single front inlet fan tray (FIFT) assembly: Precautions and Assumptions Required Equipment and Tools FIFT Upgrade Instructions The following precautions and assumptions apply: WARNING! Plan this upgrade to avoid disruptions and keep the time to a minimum. This replacement operation should take no more than 4 to 5 minutes. A fully loaded Traverse shelf can sustain a non-service affecting temperature increase for approximately 6 minutes before it begins generating critical alarms. WARNING! Depending on the number of modules in the shelf and the room temperature, Force10 recommends the use of a regular room fan blowing on the node during this operation. If you do use a standalone room fan, carefully remove any blank faceplates in the shelf and position the fan to blow directly onto the front of the shelf. Important: A fan tray holder, with fay tray module and fan filter, must be installed directly below the Traverse 1600 or Traverse 2000 shelf so there is no gap between the shelf and fan tray holder to ensure proper air flow. Important: The existing separate fan tray holder and air ramp use 4 inches of height. This is the required minimum replacement space to allow easy insertion of the new FIFT. Upgrade Guide, Release TR5.0.x 71

74 Required Equipment and Tools The following equipment and tools are required for this upgrade: Front inlet fan tray holder Front inlet fan module Air filter 1 Large straight slot screwdriver or 5/16-inch hex socket Two technicians (to decrease the replacement time, have one in front and one in back of the rack) ladder (optional) Electrostatic Discharge (ESD) wrist strap FIFT Upgrade Instructions Follow these FIFT upgrade instructions: Table 66 Front Inlet Fan Tray Holder Upgrade Instructions Instructions 1 Check the New Fan Module, page 73 to ensure proper power up. 2 Power down the existing fan. 3 Is there an air ramp below the existing fan tray? Yes. Remove it. No. Go to the next step. 4 To avoid contamination to the equipment, carefully pull the air filter from the fan tray holder. 5 Remove the existing fan tray module. 6 Remove the power cable from the rear of the fan tray holder. 7 Remove the fan tray holder. 8 Install the new FIFT (including the fan module and air filter). Refer to the Traverse Hardware Installation and Commissioning Guide, Chapter 7 Traverse System Hardware Installation, Install the Front Inlet Fan Tray Holder. 9 The Front Inlet Fan Tray Holder Upgrade Instructions are complete. 1 Front inlet fan tray air filters are available in 63% arrestance at 300 feet per minute (91.4 meters per minute) and 80% arrestance at 300 feet per minute (91.4 meters per minute) depending on your installation requirements. 72 Upgrade Guide, Release TR5.0.x

75 Check the New Fan Module Check the new FIFT fan module as follows: Table67 New Fan Module Check 1 From the rear of the existing fan tray module, loosen the two thumbscrews on the power cable cover (located on the left-hand side). Power Cable Cover Front Figure 68 Existing Fan Tray Holder Back Panel 2 Unplug the power cable from the existing fan tray module. 3 Plug the power cable into the new FIFT fan module to verify power up. 4 Unplug the power cable from the new FIFT fan tray module. 5 Plug the power cable back into the existing fan module. 6 Did the new FIFT fan module power up? Yes. Go to 9. No. Go to 7. 7 Tighten the thumbscrews on the existing power cable cover and stop the upgrade procedure. 8 RMA the tested fan module. 9 The New Fan Module Check procedure is complete. Upgrade Guide, Release TR5.0.x 73

76 74 Upgrade Guide, Release TR5.0.x

77 Chapter 6 Upgrade a DCS-96 to a DCS-IO Shelf Introduction A Traverse single-shelf DCS application consists of a DCS-96 shelf. A Traverse multi-shelf application consists of one DCS-384 matrix shelf and one or more DCS-IO shelves. To upgrade from a single-shelf DCS application to multi-shelf DCS application, you must add the DCS-384 matrix shelf and convert the DCS-96 shelf to a DCS-IO shelf. Note: The DCS-768 requires a new shelf, therefore upgrades are not supported. This chapter includes the following topics: Install, Commission, and Create DCS Services on the DCS-384 Shelf Upgrade the Hardware in the DCS-96 Shelf Upgrade the DCS-96 Shelf to a DCS-IO Shelf Upgrade Guide, Release TR5.0.x 75

78 Install, Commission, and Create DCS Services on the DCS-384 Shelf Use this procedure as a guideline to install, commission, and create DCS services on a DCS-384 matrix shelf. Table 69 Install, Commission, and Create Services on the Matrix Shelf 1 Install and commission a DCS-384 matrix shelf. See the Traverse Hardware Installation and Commissioning Guide for detailed procedures. 2 Create the DCS services from the DCS-96 shelf to the DCS-384 matrix shelf. For a script to copy all the DCS services, contact the Force10 Networks Technical Assistance Center (TAC) 3 Activate all the DCS services on the DCS-384 matrix shelf. See the TransNav Management System Provisioning Guide, Chapter 40 Creating a Multi-Shelf Application, Activate DCS-384 or DCS-768 Services. 4 The Install, Commission, and Create Services on the Matrix Shelf procedure is complete. Continue to the procedure: Upgrade the Hardware in the DCS-96 Shelf. 76 Upgrade Guide, Release TR5.0.x

79 Upgrade the Hardware in the DCS-96 Shelf Use this procedure to upgrade the hardware in a DCS-96 shelf. Table 70 Upgrade the Hardware in the DCS-96 Shelf 1 Complete the procedure: Install, Commission, and Create Services on the Matrix Shelf. 2 In the DCS-96 shelf, insert the 2-port OC-48 cards in slots 17 and 18 (these slots must be reserved for this expansion). See the Traverse Hardware Installation and Commissioning Guide, Chapter 5 Inserting and Removing Cards. 3 Connect the fibers between the DCS-IO shelf and the DCS-384 matrix shelf. There are preprovisioned 1+1 APS protection groups configured on the DCS-384. Connect the working ports on the DCS-IO shelf to the working ports on the DCS-384 matrix shelf. Connect the protecting ports on the DCS-IO shelf to the protecting ports on the DCS-384 matrix shelf. Force10 recommends to connect the fibers in the following order: DCS-96/slot-17/port-1 to DCS-384/slot-11/port-1 DCS-96/slot-17/port-2 to DCS-384/slot-12/port-2 DCS-96/slot-18/port-1 to DCS-384/slot-12/port-1 DCS-96/slot-18/port-2 to DCS-384/slot-11/port-2 4 The Upgrade the Hardware in the DCS-96 Shelf procedure is complete. Continue with 3 in Upgrade the DCS-96 Shelf to a DCS-IO Shelf. Upgrade Guide, Release TR5.0.x 77

80 Upgrade the DCS-96 Shelf to a DCS-IO Shelf Use this procedure to upgrade the DCS-96 shelf to a DCS-IO shelf. Important: If you are converting a DCS-96 shelf to a DCS-384-IO shelf, Force10 strongly recommends that you contact Force10 Technical Assistance for help with the conversion. Table 71 Upgrade the DCS-96 Shelf to a DCS-IO Shelf 1 Complete the procedure: Install, Commission, and Create Services on the Matrix Shelf. 2 Complete the procedure: Upgrade the Hardware in the DCS-96 Shelf. 3 Create the bi-directional 1+1 APS protection groups on the DCS-IO shelf. See the TransNav Management System Provisioning Guide, Chapter 20 Creating a 1+1 APS/MSP Protection Group. Ensure the 1+1 APS protection groups are created on this node. The working ports are port 1 of each OC-48 card. The protecting port for port 1 is port 2 of the adjacent card. Figure 72 New 1+1 APS Protection Groups on DCS-96 Shelf 4 Open a telnet session to the management server. See the procedure in the TransNav Management System CLI Guide, Chapter 1 CLI Overview, Connect to the Domain-Level CLI. 78 Upgrade Guide, Release TR5.0.x