1521-TMSeries_R19.0.1_A

IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION© Transmode Date: 2010-06-02 Doc. number: 1521-TM_15_0 Rev: A Page 1 (42) TM-Series UPGRADE INSTRUCTION Release 19.0.1 Rev A, 2012-06-19 IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. number: 1521-TM_R19.0.1 Rev: A Page 2 (42) 1 GENERAL The purpose of this document is to provide step-by-step instructions of how to upgrade the Transmode TM-series SW from R17.0.3 and R18.0.1 to R19.0.1. If an older software version than R17.0 is in use, a first upgrade to 17.0.3 is needed before performing the steps to upgrade to R19.0.1 in this instruction. For information of how to upgrade to 17.0.3, read upgrade instructions for the relevant release. Table 1 in chapter ‘2.2 Supported versions to upgrade from’ show the number of upgrade steps that are needed to be performed for different releases before upgrading to R19.0.1. All commands must be written exactly in the way they are written in this document e.g. some parameters in the string must be written using capitals “swu +FS upgrade……”. Make sure to follow the numbered steps below in chronological order. There are three possible ways of upgrading the SW on a node: using TNM, ENM GUI or CLI. If using the TNM you can upgrade the whole network with a few simple steps. The specifications and information within this manual are subject to change without further notice. All statements, information and recommendations are believed to be accurate but are presented without warranty of any kind. Users must take full responsibility for their application of any products. In no event shall Transmode Systems AB be liable for any indirect, special, consequential or incidental damages, including, without limitation, lost profits or loss or damage to data arising from the use or inability to use this manual, even if Transmode or its suppliers have been advised of the possibility of such damages. 1.1 In commercial confidence The manual is provided in commercial confidence and shall be treated as such. 1.2 Document Revision History Revision A Date 2012-06-19 Description of changes First released R19.0.1 version 1.3 Versions The new ENM-specification file is: enm001a-r19a-2. Depending on board type different files are used. For a list of all Software files, see Software versions at chapter 4 in this document. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. No part of this document may be reproduced without written permission of the copyright holder Home page: www.transmode.com IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. number: 1521-TM_R19.0.1 Rev: A Page 3 (42) 1.4 1 1.1 1.2 1.3 1.4 Table of content General.....................................................................................................2 In commercial confidence .........................................................................................2 Document Revision History .......................................................................................2 Versions ..................................................................................................................2 Table of content ......................................................................................................3 TNM Compatibility....................................................................................................4 Supported versions to upgrade from .........................................................................4 Special Considerations..............................................................................................5 Multiservice Muxponder 10G (MS-MXP10G)................................................................6 Ethernet Muxponder (EMXP).....................................................................................7 Multi Service Access Hub (MXP-MBH/1) .....................................................................7 Quad 10Gb/s FEC Transponder (TPQ10GFEC)............................................................7 10G Tunable OTN Transponder (TP10GOTN/TC)........................................................7 MDU40 or VOA8CHII ................................................................................................8 Notice .....................................................................................................................9 TPDDGBE and TPD10GBE with amplifiers ..................................................................9 TPQMR....................................................................................................................9 OA17C or OA2 17/17C..............................................................................................9 Spare-part in slave subracks .....................................................................................9 CU/CU2OSC replacement with CU-SFP.......................................................................9 2 2.1 2.2 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 Important Information to read Before upgrading ..........................................4 3 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.3 3.3.1 3.3.2 Upgrade instructions ................................................................................10 Software upgrade using TNM (multiple nodes)......................................................... 11 Preparations TNM .................................................................................................. 11 Upgrade instructions TNM (multiple nodes) ............................................................. 12 Software upgrade using ENM (individual node) ........................................................ 15 Preparations ENM .................................................................................................. 16 Upgrade instructions ENM (individual node)............................................................. 17 Software upgrade using CLI (individual node).......................................................... 20 Preparations CLI .................................................................................................... 21 Upgrade instructions CLI (individual node)............................................................... 22 The correct Software versions................................................................................. 26 Software versions for first generation of Control Units .............................................. 26 Software versions for second generation of Control Unit........................................... 26 Software versions for third generation of Control Unit .............................................. 26 Software versions for first generation of Traffic Units ............................................... 27 Software versions for second generation of Traffic Units........................................... 28 Software versions for third generation of Traffic Unit................................................ 29 Software versions for fourth generation of Traffic Unit ............................................. 30 Fall back procedure using ENM ............................................................................... 31 Fall back procedure using CLI (alternative 1) ........................................................... 33 Fall back procedure using CLI (alternative 2) ........................................................... 35 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 Software versions ....................................................................................26 5 5.1 5.2 5.3 Fall back .................................................................................................31 6 Contact information .................................................................................42 Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. No part of this document may be reproduced without written permission of the copyright holder Home page: www.transmode.com IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. number: 1521-TM_R19.0.1 Rev: A Page 4 (42) 2 2.1 IMPORTANT INFORMATION TO READ BEFORE UPGRADING TNM Compatibility For full compatibility between ENM and TNM it is strongly recommended to upgrade both TNM and ENM to the same release (e.g. R19.0). A network running nodes on a later release than the TNM (e.g. TNM not upgraded to R19.0) will have the risk of displaying faulty information regarding traffic services in the TNM (showing services as "grey" or "incomplete") 2.2 Supported versions to upgrade from Upgrade is supported from previous R17 and R18 releases. When a system is required to be upgraded from earlier releases than R17.0 to R19.0.1, it is important to first upgrade the node to R17.0.3 before continuing to R19.0.1. Table 1 below shows the number of upgrade steps that are needed before upgrading to R19.0.1 for CUSFP, CUOSC or CU systems. If there are any questions please contact Transmode support [email protected] for additional information. Upgrade procedure for CU-SFP, CUOSC and CU systems Release 1st upgrade to Upgrade to R19.0.1 R16.0.x and older Two releases at a time From R17.0.3/R18.0.1 R17.0 Directly R17.0.1 Directly R17.0.2 Directly R17.0.3 Directly R18.0 Directly R18.0.1 Directly R19.0 Directly Table 1: Upgrade towards R19.0.1 using CU-SFP, CUOSC and CU Please read the release notes and upgrade instructions on how to upgrade to 19.0.1 from earlier releases described in this document. If you have a system of an earlier release, you need to upgrade the system to at least 19.0.1 release in order to be able to use the new released boards such as VOA-8CH/SFP, please read the release notes and upgrade the system first and then insert the new boards afterwards. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. No part of this document may be reproduced without written permission of the copyright holder Home page: www.transmode.com 1 Yes Yes N/A Yes Yes Yes Yes Yes. Prior to an upgrade. SW upgrades are non service affecting.1 Rev: A Page 5 (42) 2.0. Traffic FW upgrades will be service affecting. if new fpga is activated R17.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.0.1) NOTE: Board types not listed above does not have reported disturbances. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.3 Yes Yes N/A Yes Yes Yes Yes Yes. number: 1521-TM_R19. After a FW upgrade the traffic will be recovered automatically after a short traffic hit during reboot.3 Special Considerations A new release may contain both Software (SW) and Firmware (FW) upgrades.0 Yes Yes Yes Yes Yes Yes Yes Yes. if new fpga is activated.com . SUMMARY OF UPGRADE DISTURBANCES Yes = traffic disturbance No = no traffic disturbance N/A= board not released Software Upgrade Path to R19. if new fpga is activated R18. if new fpga is activated R19.0 Yes Yes N/A Yes Yes Yes Yes Yes.transmode. read the chapter for this board type (2.0. No part of this document may be reproduced without written permission of the copyright holder Home page: www. if new fpga is activated R18.1 R17. if new fpga is activated For detailed information.1 Yes Yes Yes Yes Yes Yes Yes Yes.3. but only on those units that are targeted for a FW upgrade. please check if the network that is to be upgraded contains any of the below listed units since traffic carried on these units will be affected. if new fpga is activated R17.0.2 Yes Yes N/A Yes Yes Yes Yes Yes. Board Type GBE10-EMXP10G/II GBE22-EMXP10G/II EMXP40G/II EMXP80G/II MXP-MBH/1 TPQ10GFEC TP10GOTN/TC MS-MSXP10G Traffic combination: -gbEx4Stm16Oc48x2 -stm16Oc48x4 R17.0 Yes Yes Yes Yes Yes No No Yes.0.0. 0. After the CU restart has finished. Click on ‘Maintenance’ tab and choose ‘Restart main CU’ and ‘Apply’. save a backup of the current configuration.1 to R19.3. The R19. Method 2: Another way to activate the new traffic FPGA is to reconfigure the board in ENM to another traffic combination and then returning to the previous combination. The traffic FPGA version has now changed to the new R19. In ENM.g.1 traffic FPGA will cause a traffic disturbance. the saved backup in step ‘1.0. then ‘Apply’ the change. This information can be found below the ‘board’ tab in the “Additional Information” field. pull the board out and re-insert it. Important: Do NOT save this configuration.3 or R18. take note of which traffic combination that currently is active (e. 3.g.’ is reloaded. Method 1: The fastest method to change the traffic FPGA is to cold start the board. No part of this document may be reproduced without written permission of the copyright holder Home page: www. (E. Stm16Oc48x4). otherwise previous configuration data may be overwritten with default settings.xml’) 2.1 version. Do you still want to reboot?’ Click ‘OK’ button. Click ‘Change’ button and choose a different traffic combination (e. e. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 version.0. Traffic Combination gbEx4Stm16Oc48x2 Stm16Oc48x4 Old FPGA version P1N P1G New FPGA version (R19) P1O P1H Loading and activating the new R19. In ENM it is possible to view information of which traffic FPGA that is currently in use. gbEx4Stm16Oc48x2).3.0.0. This can be verified in the “Additional Information” field.0. A user of the MS-MXP10G board can choose to stay with the old FPGA version and avoid a traffic disturbance in the network.g.transmode.0.g. with the name ‘Config_backup.1 traffic FPGA is loaded and active. Follow the procedure below: 1. The traffic FPGA has now changed to the new R19.1 Multiservice Muxponder 10G (MS-MXP10G) 2.1. 4. There are two ways to load and activate the new FPGA version. Click ‘Change’ button again and return to the previous combination.0.1 Upgrade instructions when using MS-MXP10G After an upgrade from R17.1 Rev: A Page 6 (42) 2.com . In MS-MXP10G board ‘Line’ tab. The new traffic FPGA’s are compatible with the previous versions.1 new traffic FPGA’s are introduced for the traffic combinations ‘gbEx4Stm16Oc48x2’ and ‘Stm16Oc48x4’. number: 1521-TM_R19. A message box appears saying ‘Configuration is not saved.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. but are not loaded. 0.3 to R18.1 a cold start of the board is required to guarantee that all new features are initialised and functional.3 and R18.0.1 Upgrading MXP-MBH/1 from R17. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.3.2 Upgrading MXP-MBH/1 from R17.1 Upgrading TPQ10GFEC from R17.0. GBE22-EMXP10G/II.1 of the boards GBE10-EMXP10G/II.3 and R18.0.1 to R19.0.3.0. EMXP40G/II and EMXP80G/II will cause a traffic disturbance when the boards are restarted.3.0. GBE22EMXP10G/II.0. The downtime during a reboot is roughly 45 seconds. The problem does not occur every time. The SDH/SONET and Ethernet setting in MBA is lost in 1-2 sec resulting in lost traffic.0.3.3 or R18.3.0. 2. number: 1521-TM_R19.3 Multi Service Access Hub (MXP-MBH/1) 2.1 to R19.3.3 and R18. 2.1 Rev: A Page 7 (42) 2.1 to R19.0. 2. it occurs 1 out of 50 times.5 10G Tunable OTN Transponder (TP10GOTN/TC) 2.3.com .2 Ethernet Muxponder (EMXP) 2.0.4 Quad 10Gb/s FEC Transponder (TPQ10GFEC) 2.1 of the board TPQ10GFEC will cause a traffic disturbance when the board is restarted.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.0.3.0. The SDH/SONET and Ethernet setting in MBA is lost in 10-60 sec resulting in lost traffic.0.1 Upgrading TP10GOTN/TC from R17. it is however strongly dependent on the amount of configuration and can differ significantly from this value.4. The problem does not occur every time.0.3.2.1 Upgrade from R17. No part of this document may be reproduced without written permission of the copyright holder Home page: www.1 to R19. it occurs 1 out of 3 times.0.3.3 and R18.0.1 When rebooting MXP-MBH/1 a traffic hit might occur. EMXP40G/II and EMXP80G/II Upgrade from R17.transmode.1 When rebooting MXP-MBH/1 a traffic hit might occur. The downtime during a reboot is roughly 45 seconds. 2.1 After upgrading the TP10GOTN/TC to R19.5.3.1 to R19.0.1 Upgrade of GBE10-EMXP10G/II. 0.0.1.1 Rev: A Page 8 (42) 2. If configuration is not saved before the upgrade there might be problems with the control loops if a "fallback" of SW is executed.com .3 or R18.transmode.6.3.3.1 from R17.1 to R19.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.0.6 MDU40 or VOA8CHII 2. number: 1521-TM_R19.3 and R18.0.0.0. No part of this document may be reproduced without written permission of the copyright holder Home page: www.1 Upgrading MDU40 or VOA8CHII from R17. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 If you are using optical control loops (OCL) together with MDU40 or VOA8CHII it is important that the configuration is saved before upgrade to R19.0. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. If SW in sparepart is of older release.1 Rev: A Page 9 (42) 2. Afterwards the board must be moved to the slot where the original board was located (in slave subrack) or the board have to be configured again in master subrack.4 2. read the ‘Spare-part handling Guide’ within System Manual Volume C (Operations & Maintenance).2 TPQMR If using a TPQMR of version R1A or R1B that is running 1 G FC or 2 G FC traffic.4.0 on the spare-part you can also put that spare-part into a free slot in master subrack then the upgrade will be made automatically. Please.4.0 or later. 2. If you know that you have an older SW version than R8. However some special procedures are needed when such a replacement should be made. No part of this document may be reproduced without written permission of the copyright holder Home page: www.transmode. Set APS to disabled for all active amplifiers (amplifiers with output power) in the network before upgrading and saving the configuration.0. Customers that desire to use the APS-feature must manually activate APS on the amplifiers after the upgrade. 2. The CU-SFP/II can be used as a spare-part for CU-SFP. In systems using TPDDGbE and/or TPD10GbE in combination with amplifiers with ”Automatic Power Shutdown” (=APS) enabled. the SW in the spare-part board must be of release R8. This means that a board of earlier release than R2B cannot be used as a replacement to a board with the amplifier type set to ConstantGainHI. Do not forget to save the changes! 2. number: 1521-TM_R19.1 Notice TPDDGBE and TPD10GBE with amplifiers Disable APS on AMPs before upgrading. the upgrade to R8.4. the format may be configured to “other” with speed “850” (when using 1G FC) or “other” with speed “1700” (when using 2G FC).0 is inserted first into slave-subrack and then into master subrack this solution WILL NOT work.3 OA17C or OA2 17/17C An OA17C or OA2 17/17C with an earlier revision than R2B cannot be used with parameter amplifier type set to constantGainHI.5 CU/CU2OSC replacement with CU-SFP The CU-SFP can be used as a spare-part for CU/CU2OSC.0 must be done manually.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. The change of traffic format from “other/850” to “1GFC” or “other/1700” to 2GFC will not cause any traffic disturbances on TPQMR’s of revision R1A. This format should in such case be changed to “1GFC” or “2GFC” before the upgrade to avoid future problems with board replacements of TPQMR to revision R2A. 2. If the spare-part with older SW than R8.com .4.4 Spare-part in slave subracks If having more than one subrack in one node and replacing a board in any of the slave subracks.4. New units/products in this release are   VOA-8CH/SFP VOA-SFP/01 8ch SFP-based VOA unit VOA SFP 20dB range SM no PD Always upgrade the system to R19.1 Rev: A Page 10 (42) 3 UPGRADE INSTRUCTIONS Please read the release notes and chapter ‘2.g.0. when using ADSL modems etc you might get timeouts when downloading the software.com .0. number: 1521-TM_R19. e.1 must be first upgraded to R17.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc._The last three characters are the <period>. The allowed set of characters from which backup filenames should be constructed are the following: ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789.3 or later. All systems that should be upgraded to R19.2 Supported versions to upgrade from’.0. respectively. and <hyphen> characters. If the network connection is poor. <underscore>. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.0.3 Special Considerations’ before upgrading to this release.1 before inserting new boards. Since the node uses ftp to download the software it is important that the network connection between the ftp-server and node is not too poor.transmode. If upgrading from older SW release then please follow the recommendations in chapter ‘2. No part of this document may be reproduced without written permission of the copyright holder Home page: www. This is done by choosing Help and then About in TNM Client or TNM Server. No part of this document may be reproduced without written permission of the copyright holder Home page: www. This alarm list will be used after the upgrade to compare with the alarm list after the upgrade. This directory is usually located by default in: For Windows operating systems: ‘C:\Program Files\Transmode TNM\tftproot\enmsw’ For Solaris operating systems: ‘/opt/Transmode_TNM/tftproot/enmsw’ Step 3 Step 4 Step 5 Step 6 Rename the directory from ‘Downloadables’ to something more release-related (i. Step 1 Step 2 Check that your TNM server is of version R19.e.transmode.1 Preparations TNM Before the upgrade can begin some preparations has to be made. Check active alarms in all nodes and save the printouts by right-clicking in the subnet area and then choosing Alarm list.0 or later. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 Rev: A Page 11 (42) 3.1.0. Then press Save as button to save the alarm list in optional directory in your computer. Select the subnet that you want to upgrade.1 Software upgrade using TNM (multiple nodes) It is important that the TNM SW is of release 19.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. 3. Copy the ‘Downloadables’ directory from the ENM Software disc to the tftp subdirectory.0 or later when upgrading the nodes.com . R19A-2). number: 1521-TM_R19. Login to the TNM client with an admin or operator user. Press New Task button.transmode. © 2012 Transmode Systems AB All rights reserved. If you do not want to upgrade some of the nodes in the list seen in the ‘Software Upgrade’ window.g. Enter a new task name in New name edit field.0. ‘/enmsw/R19A-2/enm001a-r19a-2. Enter a New Name. No part of this document may be reproduced without written permission of the copyright holder Home page: www.1. ‘Subnet-A-check’.g.1 Rev: A Page 12 (42) 3.spec’ in the ENM Spec Path field.g. Verify that you do not have any alarms on the nodes that you want to upgrade that say ‘Configuration not saved’.com . e. Step 9 Step 10 Step 11 Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN Verify that all selected nodes say Upgrade needed in the status field. ‘Subnet-A-Upgrade’. Select the subnet you want to upgrade in left pane.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.2 Upgrade instructions TNM (multiple nodes) Figure 1: TNM Software Upgrade Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Start TNM client and login as admin or operator. Fill in your server path e. Right-click in the subnet area and select Maintenance  Software Upgrade. Select ‘Check’ in the Operation field and press Apply button. e. uncheck those nodes in the list. Verify that none of the nodes that you want to upgrade is grey. number: 1521-TM_R19. transmode. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. If upgrade of some nodes fails. Wait until all nodes are upgraded. In the Task field select the first task made in these instructions. Select ‘Restart All’ in Operation field and press Apply button to restart all upgraded nodes. Step 20 Step 21 Select Check in the Operation field and press Apply button. Verify that all selected nodes say Up to date in the Status field. After the restart. check the active alarms in all nodes by right-clicking in the subnet area and then choosing Active alarms. Right-click in the subnet area and select Maintenance  Software Upgrade. Step 14 Step 15 Step 16 Press New Task button. Step 17 Step 18 Step 19 If you did not upgrade some of the nodes in the list seen in the ‘Software Upgrade’ window. number: 1521-TM_R19. identify and solve the source of the problem and repeat again steps 5 to 7.com . ‘Subnet-ACheck’. try to find the root cause. e. Compare this list with the one you saved before the upgrade.g. If the alarm list differs. In the Task field select ‘New Task’. No part of this document may be reproduced without written permission of the copyright holder Home page: www. uncheck those nodes in the list.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.1 Rev: A Page 13 (42) Step 12 Step 13 Select ‘Upgrade’ in Operation field and press Apply button.0. g. then double-click on the status field in the Software Upgrade window at TNM Client.1 Rev: A Page 14 (42) Sometimes you might get an alarm in the TNM saying that the FTP to one or more of the node fails after the upgrade. then the application has to be completely removed from the control unit and then run the upgrade procedure again.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.sh) Activation is NOT performed Delete the application using CLI: Syntax: ‘swu delete appl <chassis> <slot> <file>’ swu delete appl 1 1 cuappl01a-r19a-4 Fault message in CLI: 1.transmode.d/verify_startscript.1 Directory not found It could be the result. or a local ENM GUI user may have an ongoing upgrade operation.0. when the directory never was created during the installation (most likely if the executing SW are of release R19 or later).” To unlock the node you can login to CLI and make a “swu unlock” or by using the unlock button in GUI. If the message says: ”Reserve node failed! Possible causes: Another task. You can check if you are in this state by double-clicking on the status field for a specific node in Upgrade window. This alarm will disappear within 15 minutes or when making a ‘Full refresh’ from the TNM. Status log (in TNM Client): 1.com . If the error message is “Verification script not found” or “Downloaded file is corrupt”.1 Verification script not found (/opt/appl/cuappl01a-r19a4/etc/init. SNMP SET operations are not enabled in the node. No part of this document may be reproduced without written permission of the copyright holder Home page: www. number: 1521-TM_R19.1 appl cuappl01a-r19a-4 Prepare activation failed 1. A previous task was abnormally terminated. In some rare cases when loosing contact with nodes during the upgrade you might need to “unlock” the upgrade process in the nodes and then perform the upgrade again. but make sure that no one else is trying to upgrade the node at the same time! If the result of an upgrade is “failed”. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. E. number: 1521-TM_R19. The nodes can be upgraded in any order. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.com .transmode. Figure 2 ENM GUI main window      Go through the numbered items below for all the nodes that need to be upgraded. However.0. Be aware that the IP address used below is just an example and that it of course should be changed to the IP address for the tftp server computer.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.2 Software upgrade using ENM (individual node) It is important that only the user that performs the upgrade is logged in to the ENM GUI. Transmode recommends that you start with the far end nodes and work towards the node where the tftp server computer is connected to minimize the risk of losing the connectivity to whole network in the worst case. as long as you work with one node at a time. Work with one node at a time and finish the upgrade for that node before starting with the next node. The show command responses are examples as well.1 Rev: A Page 15 (42) 3. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Put all 19.transmode. No part of this document may be reproduced without written permission of the copyright holder Home page: www.exe. Change Server Configuration timeout seconds to 8 in tftp-server. Select ‘Edit’ in the menu of Notepad or Wordpad. Change ‘Max retransmit’ to 9 in tftp-server. Press OK to apply the settings. Choose Copy. 6. by clicking on the file named tftpd32. Save the file. Make sure that you choose a computer that can be reached from all the nodes that you want to upgrade.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. 2. This is done in the following way on a PC: 1. 7. 3. Select Active Alarms in left pane of the ENM GUI. 5.1 software files and the tftp program called tftpd32.0.1 Preparations ENM Before the upgrade can begin some preparations have to be made.0. Check active alarms in all nodes and save the printouts. Open ‘Notepad’ or ‘Wordpad’.com .1 Rev: A Page 16 (42) 3. Mark all the alarm text. number: 1521-TM_R19. The files and the program can be found under directory “/downloadables” on the ENM CD you have got from Transmode or downloaded from our customers support pages: http://www.exe in that folder. Uncheck ‘Option negotiation’. Select ‘paste’. Click on the right button. 4.transmode.com/support Start the tftp server. 8. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Figure 3 Marking of Active Alarms Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.2. Press ‘Settings’ button in tftp-server window. Step 1 Create a new folder and name it “tftp” on your “tftp server computer”. 3 release or later. number: 1521-TM_R19.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.2 Upgrade instructions ENM (individual node) Step 1 Step 2 Login to the node as an oper user. using the web-browser (ENM GUI). Then refresh the page. Close down all tabs that are not used at the moment. If not then follow instructions at chapter 2. Check that you have a 17.g.transmode. E. To have only one session is strongly recommended. Save the configuration before continuing. see Figure 2.2.com .2 (supported versions to upgrade from). Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 Rev: A Page 17 (42) 3. this is done by pressing the Diskette icon in ENM GUI. Then enter a file name in the dialogue that appears and press the Save button. (includes r17a-4 or later).0.0. No part of this document may be reproduced without written permission of the copyright holder Home page: www. The information about software version could be read at the upper right corner of the ENM GUI. see Figure 4. for Internet Explorer: Tools -> internet options -> delete files -> delete all offline content -> OK. Step 3 Figure 4 Save dialog In order to eliminate problems during the upgrade one should empty the cache and remove temporary information from the used web browser before starting the upgrade. com .transmode. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. On some rare occasions you might need to press the refresh button in browser before you can press on the “Apply” button. Fill in your server path e. Step 8 Step 9 Step 10 Verify that ENM state field says: UpgradeNeeded. then repeat the upgrade step 9. If the ENM state is not correct. Now the software will be downloaded and installed. No part of this document may be reproduced without written permission of the copyright holder Home page: www. issue a second check. When the upgrade procedure is done. Figure 5 ENM GUI Maintenance dialog Step 5 Step 6 Step 7 Enter the IP address to your TFTP server in the IP edit field. Select ’Check’ in the Action field and press Apply button. ‘/enm001a-r19a-2. Select ’Upgrade’ in the Action field and press Apply.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Step 11 Verify that ENM state field says: RebootNeeded.spec’ in the Path field.0. Select ’Check’ in the Action field and press Apply button.g. number: 1521-TM_R19.1 Rev: A Page 18 (42) Step 4 Select Maintenance in left panel of ENM GUI. Step 18 Go back to step 1 and start with the next node in the network. Insert the correct Server and the Path to the just loaded SW again. Login as user ‘oper’ or ‘root’. No part of this document may be reproduced without written permission of the copyright holder Home page: www. this could take 1-2 minutes.1 Rev: A Page 19 (42) Step 12 When the correctness of the ENM state is verified then a reboot of all boards are needed in order to set the new software in use.1 appl cuappl01a-r19a-4 Prepare activation failed 1. Select Maintenance in left panel of ENM GUI. Step 13 Step 14 Step 15 Step 16 Step 17 Login to the node again using ENM GUI. Then repeat the steps in this description.0. It will be impossible to log in to the node before it has started again. If there are alarms saying “Interwork failed” then probably the SW is not correctly installed. Check the active alarms. 1. E. compare with the active alarms before the SW upgrade by choosing Active Alarms in left pane of the ENM GUI.sh) Activation is NOT performed Deletion of the application is done in the CLI for the failed node. with the above error message would be: swu delete appl 1 1 cuappl01a-r19a-4 Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. Select Action Check and press Apply button. If the result of an upgrade in the Maintenance tab is “failed”. try to find the root cause. then run the upgrade procedure again.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Check that ENM state says: Uptodate. then the application has to be completely removed from the control unit. Now all boards will be rebooted.com . number: 1521-TM_R19. then check the text printout. E.1 Verification script not found (/opt/appl/cuappl01a-r19a4/etc/init. If the alarms differs. If the error message is “Verification script not found” or “Downloaded file is corrupt”.transmode.g. Select ’Restart All Boards’ in the Action field and press Apply.g.d/verify_startscript.  Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. Work with one node at a time and finish the upgrade for that node before starting with the next node. The actual printouts depend on the node configuration. as long as you work with one node at a time. The printouts below correspond to a basic configuration containing one control unit (CU) and only one traffic unit (TU). However.0.com . The show command responses are examples as well.transmode. the type and amount of boards can vary. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Transmode recommends you to start with the far end nodes and work towards the node where the tftp server computer is connected.3 Software upgrade using CLI (individual node) Figure 6 CLI Maintenance interface     Go through the numbered items below for all the nodes that need to be upgraded.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. The nodes can be upgraded in any order. Be aware that the IP address used below is just as an example and that it should of course be changed to the IP address for the tftp server computer.1 Rev: A Page 20 (42) 3. number: 1521-TM_R19. Press OK to apply the settings.com/support Start the tftp server. Put all 19. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Uncheck ‘Option negotiation’.1 Rev: A Page 21 (42) 3. Step 1 Create a new folder and name it “tftp” on your “tftp server computer”. Change ‘Max retransmit’ to 9 in tftp-server. Use the command: Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 activeAlarms Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.0.exe. by clicking on the file named tftpd32.1 software files and the tftp program called tftpd32.0. number: 1521-TM_R19. Press Settings button in tftp-server window. The files and the program can be found under “//downloadables” on the ENM CD you have got from Transmode or downloaded from our customers support pages: http://www. Check active alarms in all nodes and save the printouts.transmode.exe in that folder.1 Preparations CLI Before the upgrade can begin some preparations have to be made. These printouts should be compared with the alarm printouts after the upgrade.transmode.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Change Server Configuration timeout seconds to 8 in tftp-server. Make sure that you choose a computer that can be reached from all the nodes you want to upgrade.3.com . . If not then follow instructions at chapter 2........xml File exists.2 (supported versions to upgrade from)........3 release. Slot 5: done Slot 3: done Transferring backup to traffic units... This is done by verifying that all the softwares in the ‘Application’ column when performing ‘swu show executing’ includes r17a-4 or later... No part of this document may be reproduced without written permission of the copyright holder Home page: www. Slot 5: snmpd.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc..2 Upgrade instructions CLI (individual node) Step 1 Step 2 Login to the node as an oper user. Invalidating backup copies on traffic units. Saving backup on central unit.conf passwd done Slot 3: snmpd. overwrite? (yes or no) (no) yes .1 Rev: A Page 22 (42) 3...... Slot 5: done Slot 3: done Transferring additional persistent files to traffic units..transmode..com ...... Use the command: save Expected printout: Transmode::> save saving to config.1 cuboot02a-r17a-3 oskernel02a-r17a-1 1. Check that you have at least a 17.5 tuboot02a-r17a-2 oskernel02a-r17a-1 Application cuappl02a-r17a-7 tuappl01a-r17a-4 tuappl02a-r17a-5 Step 3 Save the node configuration... number: 1521-TM_R19.0...... Use the command: swu show executing Expected printout (for CU systems): Board Boot Kernel 1..conf passwd done Transmode::> Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved..3......0...3 tuboot01a-r14a-1 oskernel01a-r8a-1 1...... using the Command Line Interface (CLI).. 5 tuappl02a-r19a-5 is expected … Downloading 172. then one should repeat Step 4 and Step 5 again. Step 5 Upgrade application.12. boot.5 appl tuappl02a-r17a-5 Needs upgrading 1.Download complete.3 tuappl01a-r19a-2 is expected … 1. kernel and file system SW.ppc_8xx.rpm.1 kernel 1.59/enm001a-r19a-2.1 boot 1. Use the command: swu +FS upgrade all all 172. Cleaned Cleaned Deleted Cleaned Cleaned Cleaned Deleted Cleaned Cleaned Cleaned Cleaned Cleaned Cleaned 04:35:37 04:35:37 04:35:40 04:35:40 04:35:40 04:35:40 04:35:43 04:35:43 04:35:43 04:35:43 04:35:43 04:35:43 04:35:45 Make sure that folder /tftpboot/download/ is cleaned and empty.59/tuappl01a-r19a-2.1 appl cuappl02a-r16a-11 1.5 kernel 1.1 downloaded We are done.transmode..1 appl 1.5 appl 1. 6375506 bytes downloaded in 68.16.com . number: 1521-TM_R19.0.016 seconds 1.1 Rev: A Page 23 (42) Step 4 Remove all old previous software. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.3 boot 1. before starting the upgrade (command: swu show downloaded).3 appl tuappl01a-r16a-5 1.spec Expected printout: Downloading from host to node: Download complete.5 appl 1.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Use the command: swu –F clean all all Expected printout: 1.624 seconds … Wait until all software is activated on each board.12.16. 584 bytes downloaded in 0.3 appl 1.3 appl tuappl01a-r17a-4 Needs upgrading 1. Notice: If the upgrade fails for any reason at this stage. No part of this document may be reproduced without written permission of the copyright holder Home page: www.5 boot 1.3 kernel 1. 1 1.transmode. number: 1521-TM_R19.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. If not all of the above expected-links are correct. Use the command: swu reboot all Expected printouts: 1.. Use the command swu show filesystem all Expected printout: 1. Check that both CU and TUs have the same software release) before rebooting the node.0. The system is going down NOW! Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.. No part of this document may be reproduced without written permission of the copyright holder Home page: www.1 Reboot ordered Reboot ordered Reboot ordered We are done Transmode::> Rebooting.5 Boot cuboot02a-r19a-1 fs=r19a-2 tuboot01a-r14a-1 fs=r16a-2 tuboot01a-r19a-1 fs=r19a-2 Kernel oskernel02a-r19a-1 oskernel01a-r8a-1 oskernel02a-r19a-1 Application cuappl02a-r19a-7 tuappl01a-r19a-2 tuappl02a-r19a-5 Step 7 Check that all boards have the right file system installed. Make sure that all the software’s are correctly installed and activated for each board (i.e.1 1. go back and perform the upgrade procedure again.5 1.5 fs fs fs r19a-2 r16a-2 r19a-2 15:18:11 15:18:11 15:18:11 We are done.0.com .3 1. Use the commands: swu show next Expected printout (for CU systems): Board 1. Step 9 If all software corresponds to release R19. Step 8 Compare the software information in step 6 and step 7 with Table 2 to Table 7 at Chapter 4.1 reboot all boards.3 1.3 1.1 Rev: A Page 24 (42) Step 6 Check that all boards have the expected software. Use the command swu show filesystem all Expected printout: 1.3 Boot cuboot02a-r19a-1 fs=r19a-2 tuboot01a-r14a-1 fs=r16a-2 tuboot02a-r19a-1 fs=r19a-2 Kernel Application oskernel02a-r19a-1 cuappl02a-r19a-7 oskernel01a-r18a-1 tuappl01a-r19a-2 1. If all installed software corresponds to R19. Use the command: swu show executing Expected printout (for CU systems): Board 1. Use the command: activeAlarms If there are alarms saying “Interwork failed” then probably the SW is not correctly installed.5 oskernel02a-r19a-1 tuappl02a-r19a-5 We are done. Step 13 Check that all boards have the right file system installed. See Step 6 for information about what the software should be.transmode. Then repeat the steps in this description. No part of this document may be reproduced without written permission of the copyright holder Home page: www.1 Rev: A Page 25 (42) Step 10 Log in to the node again as oper user. Step 11 Check the active alarms.1 you are finished.1 fs r19a-2 1.0. this could take 1-2 minutes. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 1.0.0.5 fs r19a-2 15:46:40 15:46:40 15:46:40 See Step 6 for information about what the software should be.com .IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.1 software installed. Step 12 Check that all boards have the right R19. compare with the active alarms before the SW upgrade.3 fs r16a-2 1. number: 1521-TM_R19. go back to item 1 and start with the next node in the network. It will be impossible to log in to the node before it has started again. No part of this document may be reproduced without written permission of the copyright holder 1 Home page: www.Control board that has older CPU which is recognized by number 01 in the SW file name and suffix .powerpc.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.Control board that has new CPU which is recognized by number 02 in the SW file name.3 Board type CU3 3 CU-SFP/II Software versions for third generation of Control Unit Application Software Boot Kernel File system osappl02ar19a-2 Released in 18.1.ppc _8xx.1 cuappl01a-r19a-4 cuboot01ar14a-1 cuboot01ar14a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 CUOSC cuappl01a-r19a-4 4. 2 CU2.1 software versions are shown in this chapter. 4.transmode.pkg). Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 Rev: A Page 26 (42) 4 4.1 SOFTWARE VERSIONS The correct Software versions The correct R19.1 Board type CU1 1 CU Software versions for first generation of Control Units Application Software Boot Kernel File system osappl01ar16a-2 osappl01ar16a-2 Released in 1.0.0 cuappl03a-r19a-6 cuboot02ar19a-1 oskernel02 a-r19a-1 Table 4: SW for Control unit (CU3) CU1 .rpm).0 cuappl02a-r19a-7 cuboot02ar19a-1 oskernel02 a-r19a-1 Table 3: SW for Control unit (CU2) 4.1.powerpc.Control board that has new CPU which is recognized by number 03 in the SW file name.2 Board type CU2 2 CU-SFP Software versions for second generation of Control Unit Application Software Boot Kernel File system osappl02ar19a-2 Released in 8. number: 1521-TM_R19.1.rpm (xxxx01a-xxxx. 3 CU3.com .pkg).0.1 Table 2: SW for Control Unit (CU1) 4. see below (xxxx02a-xxxx. see below (xxxx03a-xxxx.0.1. 2 TPDGBE 2.1. No part of this document may be reproduced without written permission of the copyright holder 4 Home page: www. 5 CU-less Application SW is always used for boards that should be spare-parts and most of the boards can also be run in “stand-alone” CU-less mode.rpm cugxpappl01a-r19a3.1 TPDFC 2. 10. MDU40/50G-EVEN-L.2. 4.0 MDU40/50G-EVEN. MDU40/50G-ODD-L MXP8.rpm tuboot01 a-r14a-1 tuboot01 a-r14a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 osappl01 a-r16a-2 osappl01 a-r16a-2 2.rpm cu9gbeappl01ar19a-3. 6. OA2x15.ppc_8xx. 2.ppc _8xx. 2.rpm (xxxx01a-xxxx.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.0.0.rpm Boot Kernel File system Released in 4x2G5-MXP10G tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 10. OA2x17.3.ppc_8xx. 2.1. 6.1.rpm cuqxpappl01a-r19a3.rpm cu10gtcappl01ar19a-3. MXP28 10.3.0.rpm).rpm cumduappl01ar19a-3.rpm cud10glappl01ar19a-3. 4.ppc_8xx. 4. OA15.ppc_8xx.0 17.1.0 TPDDGBE 3.2 TU1. TP10G-LAN TP10GCLX/xxxx R1B TP10GCLX/TC 3.Traffic board that has older CPU that could be easily recognized by number 01 in the SW file name and suffix .1 tuappl01ar19a-2 tuappl01ar19a-2 tuappl01ar19a-2 tuappl01ar19a-2 tuappl01ar19a-2 tuappl01ar19a-2 tuappl01ar19a-2 cu10gappl01a-r19a3. OA20C/VG.0.com .0.2.ppc_8xx. OA210/10C.1. OA2x20.1 Rev: A Page 27 (42) 4.ppc_8xx.3.1. OA2-20/20/CC/VG TP10G.1. see Release note for information about which boards that can be used in CUless configurations.0. 3.ppc_8xx.0 17.ppc_8xx.2. OA20.0 GXP10/2500-SFP 3.2. OA17. OA10C/FG.1 9.ppc_8xx.0 tuappl01ar19a-2 tuappl01ar19a-2 cumxpappl01ar19a-3.rpm tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 tuboot01 a-r14a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 osappl01 a-r16a-2 TPD10GBE-BU 8.0 4. MDU40/50G-ODD.rpm cuoaappl01a-r19a3. number: 1521-TM_R19.transmode.0 GBE9-MXP10G 6.rpm cudtgappl01a-r19a3.rpm cudfcappl01a-r19a3.ppc_8xx.2.ppc_8xx.0 TPD10G-L-BU 4. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.rpm cudgbeappl01ar19a-3. 10.ppc_8xx. OA20C/LG.4 Board type TU1 4 Software versions for first generation of Traffic Units Application Software in CU systems tuappl01ar19a-2 tuappl01ar19a-2 tuappl01ar19a-2 tuapp01ar19a-2 CU-less Application Software 5 cusomappl01ar19a-3.ppc_8xx.3 OA10.0 17. 0 14.pkg tuboot02 a-r19a-1 tuboot02 a-r19a-1 tuboot02 a-r19a-1 oskernel02ar19a-1 oskernel02ar19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 osappl02 a-r19a-2 osappl02 a-r19a-2 PCU/2P 13.pkg Boot Kernel File system Released in 1x2ROADM/100G 1x2ROADM/50G 1x4ROADM/100G tuboot02 a-r19a-1 tuboot02 a-r19a-1 tuboot02 a-r19a-1 tuboot02 a-r19a-1 tuboot02 a-r19a-1 tuboot02 a-r19a-1 oskernel02ar19a-1 oskernel02ar19a-1 oskernel02ar19a-1 oskernel02ar19a-1 oskernel02ar19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 osappl02 a-r19a-2 osappl02 a-r19a-2 osappl02 a-r19a-2 osappl02 a-r19a-2 osappl02 a-r19a-2 17.rpm cuqmrappl01a-r19a3.0.2.pkg cur4x1appl01a-r19a3.0 tuappl02ar19a-5 cuqmsappl01a-r19a5.5 Software versions for second generation of Traffic Units Board type TU2 6 Application Software in CU systems tuappl02ar19a-5 Tuappl02ar19a-5 Tuappl02ar19a-5 Tuappl02ar19a-5 tuappl02ar19a-5 tuappl02ar19a-5 CU-less Application Software 7 cur4x1appl01a-r19a3.powerpc.pkg cu10g2appl01a-r19a3.0 12.0 GBE9/MXP10GFEC 12.Traffic board that has new CPU unit with SW that could be easily recognized by number 02 in the SW file name (xxxx02a-xxxx.powerpc.1.powerpc.powerpc. TPQMRi tuboot01 a-r14a-1 tuboot01 a-r14a-1 oskernel01 a-r18a-1 oskernel01 a-r18a-1 osappl01 a-r16a-2 osappl01 a-r16a-2 1.ppc_8xx.transmode.0 GBE10-EMXP10 GBE22-EMXP10 MS-MXP.powerpc.0 11.0 14.powerpc.0 12.0 13. TP10GCLX/xxxx R1C TP10GOTN/TC TPQMS 12. TPMR25-V2 TPQMR.rpm Boot Kernel File system Released in TPMR2500.pkg tuboot02 a-r19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 6 TU2. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. MSMXPDQGBE MSMXPQMS2G5 OCM/2P 12.powerpc.0 tuappl02ar19a-5 tuappl02ar19a-5 tuappl02ar19a-5 cuocmappl01a-r19a3.pkg cumxfecappl01ar19a-3. 7 CU-less Application SW is always used for boards that should be spare-parts and most of the boards can also be run in “stand-alone” CU-less mode. 7.1.0 Table 5: SW for different TU1 boards 4. No part of this document may be reproduced without written permission of the copyright holder Home page: www.pkg) except for CU-less application (01).powerpc.ppc_8xx.0 1x8ROADM/50G 15.0 2.pkg cuemxpappl01ar19a-3.pkg cumsmappl01a-r19a5.powerpc.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.1.1 Rev: A Page 28 (42) Board type TU1 4 Application Software in CU systems tuappl01ar19a-2 tuappl01ar19a-2 CU-less Application Software 5 cumrappl01a-r19a3.0.0 11.0 13.powerpc.pkg cupcuappl01a-r19a3.pkg cur4x1appl01a-r19a3.0 TP10G/TC-ER.powerpc.com . number: 1521-TM_R19. 8. see Release note for information about which boards that can be used in CUless configurations. 6 Board type TU3 8 Software versions for third generation of Traffic Unit Application Software in CU systems tuappl03ar19a-6 CU-less Application Software 9 cuemxp2appl01ar19a-7.powerpc.0 VOA-8CH/SFP 19.pkg tuboot02 a-r19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 17.0 Table 6: SW for different TU2 boards 4.com . Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.0.0 15. TM-MBA/2E - cumbaappl01a-r19a3.powerpc.0 tuappl03ar19a-6 tuappl03ar19a-6 cumxp2appl01a-r19a3.pkg cuvoa8sappl01ar19a-3.pkg Boot Kernel File system Released in VOA-8CH/II tuboot02 a-r19a-1 tuboot02 a-r19a-1 oskernel02ar19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 osappl02 a-r19a-2 11.Traffic board that has new CPU unit with SW that could be easily recognized by number 03 in the SW file name (tuappl03a-xxxx.1.pkg) except for CU-less application (01).0 16.pkg cumbhappl01a-r19a3.powerpc.0 TM-MBA/2.0 MXP-MBH/1 17. see Release note for information about which boards that can be used in CUless configurations.transmode.powerpc.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.pkg tuboot02 a-r19a-1 tuboot02 a-r19a-1 oskernel02ar19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 osappl02 a-r19a-2 18. No part of this document may be reproduced without written permission of the copyright holder Home page: www.powerpc.1 Rev: A Page 29 (42) Board type TU2 6 Application Software in CU systems tuappl02ar19a-5 tuappl02ar19a-5 CU-less Application Software 7 cuvoa2appl01a-r19a3. number: 1521-TM_R19.pkg cumsm10appl01ar19a-5.pkg Boot Kernel File system Released in GBE10-EMXP10G/II GBE22-EMXP10G/II EMXP80G/II tuboot02 a-r19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 15. 9 CU-less Application SW is always used for boards that should be spare-parts and most of the boards can also be run in “stand-alone” CU-less mode.pkg tuboot02 a-r19a-1 tuboot02 a-r19a-1 oskernel02ar19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 osappl02 a-r19a-2 16.0 EMXP40G/II - cuemxp2appl01ar19a-7.powerpc.powerpc.powerpc.0 Table 7: SW for different TU3 boards 8 TU3.powerpc.0 MSMXP10G MSMXP10G/TC-ER MXP8/II tuappl03ar19a-6 14. number: 1521-TM_R19.0 MDU16-CL/50G tuappl04ar19a-3 cumdu16appl01ar19a-3.pkg tuboot02 a-r19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 18.0.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.pkg tuboot02 a-r19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 18.transmode. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.com . see Release note for information about which boards that can be used in CU-less configurations.7 Board type TU4 10 Software versions for fourth generation of Traffic Unit Application Software in CU systems tuappl04ar19a-3 CU-less Application Software 11 cutpqappl01a-r19a3. No part of this document may be reproduced without written permission of the copyright holder 10 Home page: www.powerpc.1 Rev: A Page 30 (42) 4.pkg Boot Kernel File system Released in TPQ10GFEC tuboot02 a-r19a-1 oskernel02ar19a-1 osappl02 a-r19a-2 17.powerpc.pkg) except for CU-less application (01).powerpc.powerpc.1.0 Table 8: SW for different TU4 boards TU4.0 TPQMP tuappl04ar19a-3 cuqmpappl01a-r19a3. 11 CU-less Application SW is always used for boards that should be spare-parts and most of the boards can also be run in “stand-alone” CU-less mode.Traffic board that has new CPU unit with SW that could be easily recognized by number 04 in the SW file name (tuappl04a-xxxx. 1. boot and kernel SW.0.0. R18. No part of this document may be reproduced without written permission of the copyright holder Home page: www.1 software.com .0 or R19.0.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Speed: both10and100.1 Rev: A Page 31 (42) 5 FALL BACK If for any reason the upgrade failed and one wants to revert to the old SW. If not.0.0. R19. then they should be set back to standard values (Auto negotiation mode: On. 5. Figure 7 ENM GUI Maintenance Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. a cold start of the CUSFP or CU-less board will be needed to restore the standard settings. R17. If the Ethernet settings for the DCN port/s has been modified from the standard settings when using the R17. The file system is backward compatible and will work with an earlier version of the SW.transmode. Duplex Capability: both) before proceeding with a fall back.0. number: 1521-TM_R19. Step 1 Select Maintenance in left panel of ENM GUI.3.2.0. use ENM or CLI to perform a downgrade of application. R18. Fallback procedure using ENM with ‘Server’ set to ‘local’ is currently not supported. It is very important that you never downgrade the boot and kernel SW on CU/CU2OSC to a release before 8.1 Fall back procedure using ENM Follow the steps below to revert to the previous node SW. Insert the correct Server and the Path to the just loaded SW again. this could take 1-2 minutes. Step 8 Step 9 Step 10 Step 11 Step 12 Login to the node again using ENM GUI.1 Rev: A Page 32 (42) Step 2 Step 3 Step 4 Enter the IP address to your TFTP server in the IP edit field. If the R17. If there are alarms saying “Interwork failed” then probably the SW is not correctly installed. compare with the active alarms before the SW upgrade by choosing Active Alarms in left pane of the ENM GUI. ‘/enm001a-r17a-4.0.spec’ in the Path field. In this case repeat steps Step 1 to Step 12. then repeat the upgrade Step 4.g. Select ’Check’ in the Action field and press the Apply button. number: 1521-TM_R19. Check that ENM state says: Uptodate. Login as user ‘oper’ or ‘root’.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. issue a check. Select Maintenance in left panel of ENM GUI. Select Action Check and press Apply button.com . Step 5 Step 6 Verify that ENM state field says: RebootNeeded.0. Step 13 Go back to Step 1 and start with the next node in the network. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Check the active alarms. It will be impossible to log in to the node before it has started again. Select ’Upgrade’ in the Action field and press Apply. boot and kernel software will be downloaded and installed. Fill in your server path e. If the ENM state is not correct.3 application software is still available on board then it will be activated directly otherwise the application. Now all boards will be rebooted. Select ’Restart all boards’ in the Action field and press Apply. Step 7 When the correctness of the ENM state is verified then a reboot of all boards are needed in order to set the new software in use.transmode. When the upgrade procedure is done. Clean temporary files from CU by using following command: swu clean downloaded Step 3 Downgrade application.16.1 '/etc/lumentis/cuappl02a-r17a-7' is not empty .. is expected Needs activation of .spec Expected printout: 1. Step 1 Step 2 Login to the node as an oper user. No part of this document may be reproduced without written permission of the copyright holder Home page: www.3.rpm…………. using the Command Line Interface (CLI).59.5 1..1 appl cuappl02a-r17a-7 Activate done 14:32:41 1.com .12.1 Rev: A Page 33 (42) 5.5 … 1. is expected Needs upgrading to . In this case R17.5 appl tuappl02a-r17a-5 Activate done 14:31:45 1.16. is expected Needs upgrading to ... is expected 14:22:48 14:22:48 14:22:48 14:22:48 14:22:48 14:22:48 14:22:48 14:22:48 14:22:48 14:22:48 Downloading 172.12.176 seconds … … 1.3 1.1 appl appl boot kernel appl tuappl01a-r19a-2 tuappl01a-r17a-4 tuappl02a-r19a-5 tuappl02a-r17a-5 cuboot02a-r19a-1 cuboot02a-r17a-3 oskernel02a-r19a-1 oskernel02a-r17a-1 cuappl02a-r19a-7 cuappl02a-r17a-7 Needs upgrading to . number: 1521-TM_R19.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.transmode.1 kernel oskernel02a-r17a-1 Activate done 14:32:40 1.ppc_8xx.1 1.1 1. 6330983 bytes downloaded in 67.no files copied (this version might have been active before?) We are done Wait until all software is activated on each board.0..1 boot cuboot02a-r17a-3 Activate done 14:32:18 1.2 Fall back procedure using CLI (alternative 1) Follow the steps below to revert to the previous node SW. Download complete.1 1.1 1.... is expected Needs activation of . boot and kernel to original SW release.3 1./tuappl01a-r17a-4.59/enm001a-r17a-4.1 1. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.0.. Use the command: swu upgrade all all 172.. contact Transmode support before doing the second upgrade. Make sure that the correct software is installed and activated by using following commands at CLI: swu show next Board Boot 1.0. Then make a ‘swu reboot cu’ and the alarm will disappear. Use the command: ActiveAlarms If using OAR-450C a ‘Configuration’ error might appear after the ‘fall back’. Note that it will be impossible to log in to the node before it has started again.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. this could take 1-2 minutes. If performing a ‘fall back’ to older release and using FC traffic on GXP10/2500-SFP boards the traffic might be interrupted after the ‘fall back’ until administrative state is toggled between down/up on the FC client ports.spec) then a reboot of all boards are needed in order to set the new software in use. Use the command: swu reboot all It will be impossible to log in to the node before it has started again. number: 1521-TM_R19.5 tuboot02a-r17a-2 fs=r17a-1 We are done Kernel oskernel02a-r17a-1 oskernel01a-r8a-1 oskernel02a-r17a-1 Application cuappl02a-r17a-7 tuappl01a-r17a-4 tuappl02a-r17a-5 Step 5 Step 6 If the software is not correctly installed or activated for any board then repeat the upgrade Step 2 and Step 3. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. If there are alarms saying “Interwork failed” then probably the SW is not correctly installed.com . the backup that was used before the ‘fall back’ will be used again.transmode. this could take 1-2 minutes.1 Rev: A Page 34 (42) Step 4 When the upgrade procedure is done. Compare with the active alarms before the SW upgrade. When the correctness of activated application software is verified (compare to enm001a-r17a-4. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Step 7 Log in to the node and check the active alarms.1 cuboot02a-r17a-3 fs=r17a-1 1. If you have done a ‘fall back’ and then upgrades to the same version of CUapplication that was used before the ‘fall back’. In this case repeat steps Step 1 to Step 6. Please.3 tuboot01a-r14a-1 fs=r16a-2 1. Step 1 Printout the executing application SW for the controller unit.previous If using a system without CU you will see the executing and previous versions in a similar way. No part of this document may be reproduced without written permission of the copyright holder Home page: www.0.1 '/etc/lumentis/cuappl02a-r17a-7' is not empty .1 The selected version (cuappl01a-r17a-4) is not installed properly under /opt/appl Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.1 '/etc/lumentis/cuappl02a-r17a-7' is not empty .no files copied (this version might have been active before!) We are done If using a system that has several subracks (Master-Slave) with different CU type.1 Rev: A Page 35 (42) 5. Use the command: swu show appl cu Expected printout (for CU systems): 1. Step 2 Revert to the previous version of the application SW. Expected printout (if using a CU-SFP): 1.1 appl cuappl02a-r17a-7 Activate done 14:04:35 1.1 The selected version (cuappl01a-r17a-4) is not installed properly under /opt/appl 1. <--.1 appl cuappl01a-r17a-4 Activate failed 13:13:50 2.transmode. Naturally a warning message will be displayed where the CU type doesn’t match the software and therefore it will ask if the application should be activate for those that it match.1 appl cuappl01a-r17a-4 Prepare activation failed 13:13:31 2.com . Use the command: swu activate appl cu XXX where XXX is the previous application software in Step 1 above.1 '/etc/lumentis/cuappl02a-r17a-7' is not empty . swu activate appl cu cuappl02a-r17a-7 2. CU/CUosc(CU1) and CUsfp(CU2) then one had to repeat step 2 for each type.no files copied (this version might have been active before?) The operation seems to fail on some boards. number: 1521-TM_R19.e.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.no files copied (this version might have been active before?) 1.3 Fall back procedure using CLI (alternative 2) Follow the steps below to revert to the previous node SW. Do you want to proceed with activation anyway? [no] yes 2.1 appl cuappl02a-r19a-7 cuappl02a-r17a-7 We are done.executing <--. i. The correct answer is Yes which result to activation of correct application for right CU type. Example below shows application activation of CUsfp when there is a CUosc in second subrack. Expected printout: Transmode::$ swu activate appl tu tuappl01a-r17a-4 1.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. activate the application software for those types as well: Transmode::$ swu activate appl tu tuappl02a-r17a-5 1.3 The selected version (tuappl02a-r17a-5) is not installed properly under /opt/appl The operation seems to fail on some boards. Use the command: swu show appl tu Expected printout: 1. number: 1521-TM_R19.no files copied (this version might have been active before?) We are done Step 3 If using a CU.3 The selected version (tuappl02a-r17a-5) is not installed properly under /opt/appl 1.3 appl tuappl02a-r17a-5 Prepare activation failed 15:01:28 1. if needed.transmode.3 appl 1.3 appl tuappl02a-r17a-5 Activate failed 15:01:38 1.5 appl tuappl01a-r17a-4 Prepare activation failed 15:00:06 1.1 Rev: A Page 36 (42) 1.5 appl tuappl01a-r17a-4 Activate failed 15:00:15 1.5 The selected version (tuappl01a-r17a-4) is not installed properly under /opt/appl The operation seems to fail on some boards.com .3 appl tuappl01a-r17a-4 Activate done 15:00:15 1. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Use the command: swu activate appl tu XXX where XXX is the previous application software in Step 3 above.5 The selected version (tuappl01a-r17a-4) is not installed properly under /opt/appl We are done Transmode::$ If other TU board types exists (for example: 02 or 03). printout the executing application SW for the traffic units.5 appl tuappl02a-r17a-5 Activate done 15:01:39 We are done Transmode::$ Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.5 appl tuappl01a-r19a-2 tuappl01a-r17a-4 tuappl02a-r19a-5 tuappl02a-r17a-5 <--<--<--<--executing previous executing previous Step 4 If using a CU/CUOSC or CU-SFP revert to the previous version of the TU application SW.1 appl cuappl02a-r17a-7 Activate done 13:13:51 1.0. Do you want to proceed with activation anyway? [no] yes 1.1 '/etc/lumentis/cuappl02a-r17a-7' is not empty . Do you want to proceed with activation anyway? [no] yes 1. TU1(old CPU) and TU2(new CPU) then one have to repeat step 4 for each type.no files copied (this version might have been active before?) The operation seems to fail on some boards.next <--.3 appl 1. Naturally a warning message will be displayed where the TU type doesn’t match the software and therefore it will ask if the application should be activated.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. number: 1521-TM_R19.1 appl 1.executing <--.1 Rev: A Page 37 (42) If using a system that has different TU type. Use the command: swu show appl all Expected printout (if using a CU-SFP): 1.5 '/etc/lumentis/tuappl02a-r17a-5' is not empty .e. <--.4 The selected version (tuappl01a-r17a-5) is not installed properly under /opt/appl 1.next Step 6 Printout the executing kernel SW for the controller unit.next <--.com . The correct answer is Yes which result to activation of correct application for right TU type.transmode.executing <--.previous If using a system without CU you will see the executing and previous versions in a similar way. swu activate appl tu tuappl02a-r17a-5 1. Example below shows activation of application for TU2(slot 5) when there is a TU1(slot 4). Use the command: swu show kernel cu Expected printout (for CU systems): 1.4 appl tuappl01a-r17a-5 Prepare activation failed 14:10:31 1.1 kernel oskernel02a-r19a-1 oskernel02a-r17a-1 We are done.5 appl tuappl02a-r17a-5 Activate done 14:10:51 1.no files copied (this version might have been active before?) We are done Step 5 Check that all ‘next’ links corresponds to the previous application SW.4 appl tuappl01a-r17a-5 Activate failed 14:10:50 1. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.executing <--. Do you want to proceed with activation anyway? [no] yes 1.5 appl We are done cuappl02a-r19a-7 cuappl02a-r17a-7 tuappl01a-r19a-2 tuappl01a-r17a-4 tuappl02a-r19a-5 tuappl02a-r17a-5 <--.5 '/etc/lumentis/tuappl02a-r17a-5' is not empty .0. No part of this document may be reproduced without written permission of the copyright holder Home page: www. The ‘next’ links should read the same as the ‘previous’ SW in Step 1 and Step 3.4 The selected version (tuappl01a-r17a-5) is not installed properly under /opt/appl 1. i.executing <--. transmode.3 kernel 1. Expected printout (if using a CU-SFP): 1.uboot) not found We are done Transmode::> If other TU board types exists (for example: 02). Transmode::> swu activate kernel tu oskernel02a-r17a-1 1.0.executing <--.3 kernel oskernel02a-r17a-1 Activate failed 07:52:59 1.uboot) not found The operation seems to fail on some boards.5 File (/opt/kernel/oskernel01a-r8a-1/boot/vmlinux.5 kernel oskernel02a-r17a-1 Activate done 07:53:23 Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. if needed. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Do you want to proceed with activation anyway? [no] yes 1.3 File (/opt/kernel/oskernel02a-r17a-1/boot/vmlinux. Expected printout: Transmode::> swu activate kernel tu oskernel01a-r8a-1 1. activate the kernel software for those types as well.3 File (/opt/kernel/oskernel02a-r17a-1/boot/vmlinux. Use the command: swu show kernel tu Expected printout: 1.3 kernel oskernel02a-r17a-1 Prepare activation failed 07:52:56 1. printout the executing kernel SW for the traffic units.previous <--.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.3 kernel oskernel01a-r8a-1 Activate done 07:49:52 1.ppcboot) not found The operation seems to fail on some boards. Use the command: swu activate kernel tu XXX where XXX is the previous kernel software in Step 8 above. Use the command: swu activate kernel cu XXX where XXX is the previous kernel software in Step 6 above. Do you want to proceed with activation anyway? [no] yes 1.1 kernel We are done oskernel02a-r17a-1 Activate done 07:40:25 Step 8 If using a CU.com .executing <--.5 kernel oskernel01a-r18a-1 oskernel01a-r8a-1 oskernel02a-r19a-1 oskernel02a-r17a-1 <--.5 File (/opt/kernel/oskernel01a-r8a-1/boot/vmlinux.1 Rev: A Page 38 (42) Step 7 Revert to the previous version of the kernel SW.previous Step 9 If using a CU/CUOSC or CU-SFP revert to the previous version of the TU application SW.5 kernel oskernel01a-r8a-1 Activate failed 07:49:52 1.5 kernel oskernel01a-r8a-1 Prepare activation failed 07:49:32 1. number: 1521-TM_R19.ppcboot) not found 1. Use the command: swu activate boot cu XXX where XXX is the previous boot software in Step 11 above.executing <--. number: 1521-TM_R19.5 kernel We are done oskernel02a-r19a-1 oskernel02a-r17a-1 oskernel01a-r18a-1 oskernel01a-r8a-1 oskernel02a-r19a-1 oskernel02a-r17a-1 <--. No part of this document may be reproduced without written permission of the copyright holder Home page: www.transmode.executing <--.1 boot cuboot02a-r19a-1 cuboot02a-r17a-3 We are done. Use the command: swu show boot cu Expected printout (for CU systems): 1.1 boot cuboot02a-r17a-3 We are done Activate done 08:15:24 Step 13 If using a CU. Step 12 Revert to the previous version of the boot SW.5 boot tuboot01a-r14a-1 tuboot01a-r14a-1 tuboot02a-r19a-1 tuboot02a-r17a-2 <--<--<--<--executing previous executing previous Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved. Use the command: swu show boot tu Expected printout: 1.executing <--.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.3 kernel 1. The ‘next’ links should read the same as the ‘previous’ SW in Step 6 and Step 8.1 kernel 1.next <--.3 boot 1.next Step 11 Printout the executing boot SW for the controller unit.0. <--. Expected printout (if using a CU-SFP): 1.executing <--.next <--.1 Rev: A Page 39 (42) We are done Transmode::> Step 10 Check that all ‘next’ links corresponds to the previous kernel SW.com . Use the command: swu show kernel all Expected printout (if using a CU-SFP): 1.previous If using a system without CU you will see the executing and previous versions in a similar way. printout the executing boot SW for the traffic units. com .bin) not found 1.executing <--. Use the command: swu reboot all If performing a ‘fall back’ to older release and using FC traffic on GXP10/2500-SFP boards the traffic might be interrupted after the ‘fall back’ until administrative state is toggled between down/up on the FC client ports. activate the kernel software for those types as well. if needed. In our case above it is not needed. number: 1521-TM_R19.3 boot tuboot02a-r17a-2 Prepare activation failed 08:22:32 1.5 boot We are done cuboot02a-r19a-1 cuboot02a-r17a-3 tuboot01a-r14a-1 tuboot01a-r14a-1 tuboot02a-r19a-1 tuboot02a-r17a-2 <--.executing <--. Do you want to proceed with activation anyway? [no] yes 1. Use the command: swu activate boot tu XXX where XXX is the previous kernel software in Step 13 above.1 Rev: A Page 40 (42) Step 14 If using a CU/CUOSC or CU-SFP revert to the previous version of the TU boot SW.3 File (/opt/boot/tuboot02a-r17a-2/boot/ppcboot.transmode.next <--.bin) not found The operation seems to fail on some boards. The ‘next’ links should read the same as the ‘previous’ SW in Step 11 and Step 13. Expected printout: Transmode::$ swu activate boot tu tuboot02a-r17a-2 1.next Step 16 Reboot the node. Step 15 Check that all ‘next’ links corresponds to the previous boot SW.0. Use the command: swu show boot all Expected printout (if using a CU-SFP): 1. No part of this document may be reproduced without written permission of the copyright holder Home page: www. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.3 boot 1.3 boot tuboot02a-r17a-2 Activate failed 08:22:39 1.1 boot 1.executing <--. the boot software for TU 01 is already an older or same version (tuboot01a-r14a-1) than what we intend to ‘fall back’ to (r17).5 boot tuboot02a-r17a-2 Activate done 08:22:42 We are done Transmode::$ If other TU board types exists (for example: 01).3 File (/opt/boot/tuboot02a-r17a-2/boot/ppcboot.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.previous <--. the backup that was used before the ‘fall back’ will be used again. for Internet Explorer: Tools -> internet options -> delete files -> delete all offline content -> OK Then refresh the page.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc. Then make a ‘swu reboot cu’ and the alarm will disappear. To fix this problem delete all offline temporary internet files. Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.transmode. Note that it will be impossible to log in to the node before it has started again. E. contact Transmode support before doing the second upgrade. If you have done a ‘fall back’ and then upgrades to the same version of CUapplication that was used before the ‘fall back’. Please.1 Rev: A Page 41 (42) Step 17 Log in to the node and check the active alarms. number: 1521-TM_R19. Use the command: ActiveAlarms If using OAR-450C a ‘Configuration’ error might appear after the ‘fall back’. Compare with the active alarms before the SW upgrade. No part of this document may be reproduced without written permission of the copyright holder Home page: www. this could take 1-2 minutes.com .g.0. Due to problems in some Internet Browsers the graphical view is not updated with all new features or the view might look corrupt when using the ENM GUI after an upgrade. transmode.IN COMMERCIAL CONFIDENCE UPGRADE INSTRUCTION © Transmode Date: 2012-06-19 Doc.1 Rev: A Page 42 (42) 6 CONTACT INFORMATION To get in contact with support personal at Transmode regarding upgrade.com Table 9: Contact information Transmode Systems AB Box 42114 SE-126 14 Stockholm SWEDEN © 2012 Transmode Systems AB All rights reserved.0.transmode.com/support E-mail tac@transmode. please use the contact information below: Name TAC Web www.com . No part of this document may be reproduced without written permission of the copyright holder Home page: www. number: 1521-TM_R19.