XTM Series

XTM Series Upgrade Instruction

Release 36.0.1
Operation & Maintenance
R36.0.1_XTMSeries_Upgrade_Instruction

Rev A | 2021-06-24
Copyright

© Copyright 2021 Infinera Corporation. All rights reserved.

This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for
any purposes or transmitted in any form to any third party without the express written consent of Infinera.

Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any
portion thereof contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind,
including, but not limited to, indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies
contained in the information or (2) arising from the adaptation or use of the information or any portion thereof
including any application of software referenced or utilized in the Manual. The information in this Manual is subject to
change without notice.

Trademarks

Infinera, Infinera Intelligent Transport Networks, I-PIC, IQ NOS, FlexILS, DTN-X, DTN, ATN, FastSMP and logos that
contain Infinera are trademarks or registered trademarks of Infinera Corporation in the United States and other
countries. All other trademarks in this Manual are the property of their respective owners.

Infinera DTN-X, DTN, FlexILS, Cloud Xpress, XT and ATN Regulatory Compliance

FCC Class A

This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation. Modifying the equipment without Infinera's written authorization
may result in the equipment no longer complying with FCC requirements for Class A digital devices. In that event,
your right to use the equipment may be limited by FCC regulations, and you may be required to correct any
interference to radio or television communications at your own expense.

DOC Class A

This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus as set out in
the interference-causing equipment standard titled “Digital Apparatus," ICES-003 of the Department of
Communications.

Cet appareil numérique respecte les limites de bruits radioélectriques applicables aux appareils numériques de
Classe A prescrites dans la norme sur le matériel brouilleur: "Appareils Numériques," NMB-003 édictée par le
Ministère des Communications.

Class A ITE

This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic
environment, radio interference may occur, in which case, the user may be required to take corrective actions.

Warning

This is a class A product. In a domestic environment this product may cause radio interference in which case the user
may be required to take adequate measures.

FDA

This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser
Notice No. 50,dated June 24, 2007.
 CONTENTS

Contents
1 GENERAL ..........................................................................................................................1
1.1 Document Revision History.........................................................................................1
1.2 Versions....................................................................................................................1
2 IMPORTANT INFORMATION TO READ BEFORE UPGRADING............................................2
2.1 DNA-M Compatibility..................................................................................................2
2.2 Supported versions to upgrade from............................................................................2
2.3 Postpone Firmware Activation function ........................................................................3
2.3.1 General ...........................................................................................................3
2.3.2 Before an upgrade............................................................................................3
2.3.3 After an upgrade...............................................................................................5
2.4 Special Considerations...............................................................................................6
2.4.1 MS-MXP10G....................................................................................................8
2.4.2 FXP400GOTN .................................................................................................8
2.4.3 TRX100267/TC ...............................................................................................8
2.4.4 Ethernet Muxponder (EMXP).............................................................................8
2.4.5 MDU40 or VOA8CHII........................................................................................9
2.5 Notice .....................................................................................................................10
2.5.1 Upgrading FHAU/1, TM-FHAU1U–DC/1 and RFU-AC/1 to R36.0.1 ....................10
2.5.2 Upgrading to R35.0.1 or above changes SSH keys ...........................................10
2.5.3 Upgrading TM-EMXP-XH800/DC to R35.0.1 may raise minor alarm ...................10
2.5.4 Upgrading 1x2 ROADM to R36.0.1 may give warning........................................10
2.5.5 Upgrading a system with a NID........................................................................10
2.5.6 TPDDGBE and TPD10GBE with amplifiers....................................................... 11
2.5.7 TPQMR ......................................................................................................... 11
2.5.8 OA17C or OA2 17/17C ................................................................................... 11
2.5.9 CU/CUOSC/CU-SFP replacement with CU-SFPII/CU-SFPIII ............................. 11
3 UPGRADE INSTRUCTIONS..............................................................................................12
3.1 New units/products in this release .............................................................................12
3.2 Software upgrade using DNA-M (multiple nodes) .......................................................13
3.2.1 Preparations DNA-M ......................................................................................13
3.2.2 Upgrade instructions DNA-M (multiple nodes) ..................................................15
3.2.3 Upgrade issues – DNA-M................................................................................18
3.3 Software upgrade using ENM (individual node) ..........................................................20
3.3.1 Preparations ENM ..........................................................................................21
3.3.2 Upgrade instructions ENM (individual node) .....................................................22
3.3.3 Upgrade issues – ENM ...................................................................................24
3.4 Software upgrade using CLI (individual node) ............................................................26
3.4.1 Preparations CLI ............................................................................................27
3.4.2 Upgrade instructions CLI (individual node) .......................................................28
3.4.3 Upgrade issues - CLI ......................................................................................32
4 SOFTWARE VERSIONS ...................................................................................................33
4.1 Software versions for first generation of Control Units .................................................33
4.2 Software versions for second generation of Control Unit .............................................33
4.3 Software versions for third generation of Control Unit..................................................33
4.4 Software versions for fourth generation of Control Unit................................................34
4.5 Software versions for first generation of Traffic Units...................................................35
4.6 Software versions for second generation of Traffic Units .............................................36
4.7 Software versions for third generation of Traffic Units..................................................37
4.8 Software versions for fourth generation of Traffic Units................................................38
4.9 Software versions for fifth generation of Traffic Units...................................................38
4.10 Software versions for sixth generation of Traffic Units ...............................................39
4.11 Software versions for seventh generation of Traffic Units...........................................40
4.12 Software versions for eighth generation of Traffic Units .............................................40
4.13 Software versions for ninth generation of Traffic Units ...............................................40
4.14 Software versions for tenth generation of Traffic Units...............................................41
4.15 Software versions for eleventh generation of Traffic Units..........................................41
5 FALL BACK ......................................................................................................................42
5.1 Fall back Considerations ..........................................................................................42

R36.0.1_XTMSeries_Upgrade_Instruction Rev A III © Infinera 2021

Infinera Proprietary and Confidential
 CONTENTS

5.1.1 Fall back from R36.0.1 and “Postpone Firmware Activation” function ..................42
5.1.2 ENM with ‘Server’ set to ‘local’.........................................................................42
5.2 Fall back procedure using ENM ................................................................................43
5.3 Fall back procedure using CLI — Alternative 1 ...........................................................45
5.4 Fall back procedure using CLI — Alternative 2 ...........................................................47
6 APPENDIX .......................................................................................................................49
6.1 FPGA revision history for boards supporting the ‘Postpone Firmware Activation’
function ...........................................................................................................49
6.2 Boards at End of Software Support (ESS)..................................................................50
6.2.1 End of Software Support (ESS) – R33.1 ...........................................................50
6.2.2 End of Software Support (ESS) – R32.1 ...........................................................50
6.2.3 End of Software Support (ESS) – R31.1 ...........................................................50
6.2.4 End of Software Support (ESS) – R31.0 ...........................................................51
6.3 Upgrade Analysis Tool..............................................................................................52
7 CONTACT INFORMATION ................................................................................................53

R36.0.1_XTMSeries_Upgrade_Instruction Rev A IV © Infinera 2021

Infinera Proprietary and Confidential
 GENERAL

1 GENERAL
The purpose of this document is to provide step-by-step instructions of how to upgrade the In-
finera XTM Series software from R32.0.1, R32.1.1, R33.1.1, R34.0.2 and R35.0.1 to R36.0.1.
If an older software version than R32.0.1 is in use, a first upgrade to R32.0.1 is needed before
performing the steps to upgrade to R36.0.1 in this instruction. For information of how to up-
grade to R32.0.1, read the upgrade instructions for the relevant release.
Table 1 Upgrade towards R36.0.1 using CU-SFP/II, CU-SFP/III and CU-less systems in sec-
tion 2.2 Supported versions to upgrade from shows the number of upgrade steps that are
needed to be performed for different releases before upgrading to R36.0.1.
There are three possible ways of upgrading the software on a node: using DNA-M, ENM GUI
or CLI. If using the DNA-M you can upgrade the whole network with a few simple steps.
This instruction contains many upgrade steps. Please make sure to follow them in chronologi-
cal order. Command examples should be written exactly the way they are described in this
document. For example, if a command contains parameters in capital letters (e.g “swu +FS
upgrade……”) then they should be written in capital etc.

1.1 Document Revision History

Revision Date Description of changes

A 2021-06-24 1st released R36.0.1 version

1.2 Versions
The new ENM-specification file is: enm001a-r36a-1.spec. Depending on board type different
files are used. For a list of all software files, see chapter 4 SOFTWARE VERSIONS in this
document.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 1 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2 IMPORTANT INFORMATION TO READ BEFORE

UPGRADING
2.1 DNA-M Compatibility
For full compatibility between XTM and DNA-M it is strongly recommended to upgrade both
XTM and DNA-M to functionality matching releases. A network running nodes with a not
matching DNA-M release will have the risk of displaying faulty information regarding traffic
services in the DNA-M (showing services as "grey" or "incomplete"). For XTM release R36.0.1
the matching DNA-M release is R36.0 or later.

2.2 Supported versions to upgrade from

Upgrade is supported from previous R32, R33, R34 and R35 releases.
When a system is required to be upgraded from earlier releases than R32.0.1 to R36.0.1, it is
important to first upgrade the node to R32.0.1 before continuing to R36.0.1.
Table 1 Upgrade towards R36.0.1 using CU-SFP/II, CU-SFP/III and CU-less systems shows
the number of upgrade steps that are needed before upgrading to R36.0.1 for CU-SFP/II, CU-
SFP/III or CU-less systems.
If there are any questions please contact Infinera support for additional information.

Table 1 Upgrade towards R36.0.1 using CU-SFP/II, CU-SFP/III and CU-less systems

Upgrade procedure for CU-SFP/II, CU-SFP/III and CU-less systems

Release 1st upgrade to Upgrade to R36.0.1
R31.1.x and older Two releases at a time From 32.0.1/ R32.1.1/
R33.1.1/ R34.0.2 /35.0.1
R32.0.0 - Directly
R32.0.1 - Directly
R32.1.0 - Directly
R32.1.1 - Directly
R33.1.0 - Directly
R33.1.1 - Directly
R34.0.0 - Directly
R34.0.1 - Directly
R34.0.2 - Directly
R35.0.0 - Directly
R35.0.1 - Directly
R36.0.0 - Directly

Please read the release notes and upgrade instructions on how to upgrade to R36.0.1 from
earlier releases described in this document.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 2 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.3 Postpone Firmware Activation function

2.3.1 General
A new function was introduced in R21.0 called ‘Postpone Firmware Activation’. With this new
function it is possible to inhibit an FPGA update before an upgrade, or activate a new FPGA
after an upgrade.
The boards that support this function in R36.0.1 are: MS-MXP, MS-MXP10G, TPD10GBE,
GBE9/MXP10GFEC, MS-TP/40G, MS-MXP/40G, TPQMS, TPQ10GFEC and TPQ10GFEC/I.
The ‘Postpone Firmware Activation’ function can be found in ENM by entering the ’Software
Control’ link. It is also possible to ’enable/disable’ this function per board by entering the
‘Equipment’ link and click on board of choice.
• Before an Upgrade:
Use the 'Inhibit activations' button and choose board(s) that should keep the current FPGA
to avoid a traffic disturbance.
• After an Upgrade:
For boards where the firmware activation has been postponed the alarm ‘"Firmware activa-
tion is pending” with severity “Warning” will exist. Use the 'Manage pending firmware activa-
tion' button and choose board(s) for activating the new FPGA. A traffic disturbance is
expected.

By choosing not to update to new firmware, new released functions may not be available or
supported. A cold boot of a board will always activate the latest firmware.

2.3.2 Before an upgrade

Before upgrading to the R36.0.1 release some of the “Postpone Firmware Activation”
supported boards requires an active choice to be taken to avoid firmware activation.
In ENM click the ’Software Control’ link followed by the ‘Inhibit activations’ button.

Fig. 1 Marked boards will keep the old firmware after the upgrade.

Above is an example from ENM where an active choice has been taken to postpone activation
of firmware before an upgrade.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 3 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.3.2.1 Summary when upgrading to R36.0.1

Table 2 Upgrade to R36.0.1

Upgrade to R36.0.1
SW level at R32.0.0, Traffic Combination Active choice needed before upgrading?
R32.0.1, R33.1.0,
R33.1.1, R34.0.0,
R34.0.1, R34.0.2,
R35.0.0, R35.0.1
MS-MXP gbex3stm4Oc12x1stm1Oc3x3Basic YES, if new FPGA in R23.1 has not been activated
gbex3stm4Oc12x1stm1Oc3x3 YES, if new FPGA in R23.1 has not been activated
gbex1stm16Oc48x1stm1Oc3x3 YES, if new FPGA in R23.1 has not been activated
gbeSyncEx3stm4Oc12x1stm1Oc3x1 NO. No new FPGA
gbeSyncEx3stm4Oc12x1stm1Oc3x1Basic NO. No new FPGA
MS-MXP10G gbEx4Stm16Oc48x2 YES, if new FPGA in R19.0.5 has not been activated
stm16Oc48x4 YES, if new FPGA in R19.0.5 has not been activated
syncEx14GLinex2 YES, if new FPGA in R32.1 has not been activated
MS-MXP40G N/A YES, if new FPGA in R22.0 has not been activated
MS-TP40G N/A NO. No new FPGA
TPD10GBE N/A YES, if new FPGA in R17.0.3 has not been activated
GBE9/MXP10GFEC N/A YES, if new FPGA in R21.0 has not been activated
TPQ10GFEC N/A NO. No new FPGA
TPQ10GFEC/I N/A NO. No new FPGA
TPQMS N/A YES, if new FPGA in R22.0 has not been activated

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 4 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.3.3 After an upgrade

In the ENM GUI click the ’Software Control’ link, then in the ’SW Status’ tab click on the
‘Manage pending firmware activation’ button.

Fig. 2 Activation of new firmware. Traffic disturbance to follow for the marked boards.

In the new dialog window, the boards that should be activated with the latest firmware, mark
them in the check boxes and press the ’Apply’ button. The firmware upgrade procedure may
take up to 3 minutes to conclude.

Above is an example from the ENM GUI where activation of firmware is performed after an up-
grade. Activation of new firmware will cause a traffic disturbance.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 5 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.4 Special Considerations

A new release may contain both Software (SW) and Firmware (FW) upgrades. SW upgrades
are non service affecting. FW upgrades will be service affecting, but only on those units that
are targeted for a FW upgrade. After a FW upgrade the traffic will be recovered automatically
after a short traffic hit during reboot. Prior to an 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.

Table 3 Summary of upgrade disturbances

SUMMARY OF UPGRADE DISTURBANCES

Yes = Traffic disturbance

No = No traffic disturbance
TC = Traffic Combination Software Upgrade Path to R36.0.1
N/A = Not Applicable
HSU = Hitless SW Upgrade

Board Type
New R32.0.0 R32.1.0 R33.1.0 R34.0.0 R35.0.0
FPGA in- R32.0.1 R32.1.1 R33.1.1 R34.0.1 R35.0.1
troduced R34.0.2
in:

GBE10-EMXP10G/II No
N/A Yes Yes Yes Yes (HSU)
GBE22-EMXP10G/II

No
EMXP80G/II N/A Yes Yes Yes Yes (HSU)

EMXP48/IIE

EMXP62/IIE
No
EMXP120/IIE N/A Yes Yes Yes Yes (HSU)
EMXP220/IIE

EMXP240/IIE

No
TM-EMXP-1U-DC N/A Yes Yes Yes Yes (HSU)

No
EMXP/III N/A Yes Yes Yes Yes (HSU)

EMXP440/III No
N/A Yes Yes Yes Yes (HSU)
EMXP440-Q/III

TM-HDEA1600G/DC N/A Yes Yes Yes Yes Yes

TM-EMXP-XH800/DC N/A N/A N/A N/A N/A Yes

1
TPQMS Yes Yes 1
Yes 1
Yes 1
Yes 1
R22.0
1 1 1 1 1
MS-MXP/40G R22.0 Yes Yes Yes Yes Yes
1 1 1 1 1
GBE9/MXP10GFEC R21.0 Yes Yes Yes Yes Yes

MS-MXP
R23.1 1 1 1 1 1
TC: gbex3stm4Oc12x1st- Yes Yes Yes Yes Yes
R21.0
m1Oc3x3Basic

MS-MXP
TC: R23.1 1 1 1 1 1
Yes Yes Yes Yes Yes
gbex3stm4Oc12x1stm1Oc3x3 R21.0

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 6 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

Table 3 Summary of upgrade disturbances (cont’d.)

SUMMARY OF UPGRADE DISTURBANCES

Yes = Traffic disturbance

No = No traffic disturbance
TC = Traffic Combination Software Upgrade Path to R36.0.1
N/A = Not Applicable
HSU = Hitless SW Upgrade

Board Type
New R32.0.0 R32.1.0 R33.1.0 R34.0.0 R35.0.0
FPGA in- R32.0.1 R32.1.1 R33.1.1 R34.0.1 R35.0.1
troduced R34.0.2
in:

MS-MXP
TC: R23.1 1 1 1 1 1
Yes Yes Yes Yes Yes
gbex1stm16Oc48x1stm1Oc3x3 R21.0

MS-MXP10G 1 1 1 1 1
TC: gbEx4Stm16Oc48x2 R19.0 Yes Yes Yes Yes Yes

MS-MXP10G 1 1 1 1 1
R19.0 Yes Yes Yes Yes Yes
TC: stm16Oc48x4

MS-MXP10G 1 1 1 1 1
TC: syncEx14GLinex2 R32.1.1 Yes Yes Yes Yes Yes

1 1 1 1 1
TPD10GBE R17.0.3 Yes Yes Yes Yes Yes

NOTE: Board types not listed above do not have reported disturbances.
1. If new FPGA is activated

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 7 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.4.1 MS-MXP10G
2.4.1.1 Upgrade of MS-MXP10G

A new traffic FPGA was introduced in R32.1.1 for the board MS-MXP10G and the traffic com-
bination “syncEx14GLinex2”.
Upgrading from earlier releases to R36.0.1 an active choice needs to be taken before the up-
grade to avoid a firmware upgrade. This can be done by using the ‘Postpone Firmware Activa-
tion’ function. If no active choice is taken the firmware will be upgraded, which will cause a
traffic disturbance.
Performed tests indicates that the traffic disturbance will last less than one minute.

2.4.2 FXP400GOTN
2.4.2.1 Using the FXP400GOTN board with OCM/2p

If the FXP400GOTN board is intended to be used with the OCM/2p board, then the firmware
in the OCM/2p needs to be upgraded to revision 3.85 with a script that can be received from
the Infinera TAC support.

2.4.3 TRX100267/TC
2.4.3.1 Upgrading traffic units equipped with TRX100267/TC

Traffic units equipped with certain versions of TRX100267/TC may be causing a traffic disturb-
ance. Potentially affected traffic units are EMXP220/IIE, TP100GOTN, TP100GOTN/II and
MXP100GOTN. See product change notification 100025-PCN00224 for details.

2.4.4 Ethernet Muxponder (EMXP)

2.4.4.1 Upgrade of TM-HDEA1600G/DC and TM-EMXP-XH800/DC

Upgrade of boards will cause a traffic disturbance when the boards are restarted.
The downtime during a reboot is roughly 45 seconds, it is however strongly dependent on the
amount of configuration and can differ significantly from this value.

2.4.4.2 Upgrade of EMXP/III, EMXP440/III and EMXP440-Q/III

Upgrade of boards from release R35.0 to R36.0.1 are disturbance free (HSU).
Upgrade of boards from older releases than R35.0 will cause a traffic disturbance when the
boards are restarted
The downtime during a reboot is roughly 45 seconds, it is however strongly dependent on the
amount of configuration and can differ significantly from this value.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 8 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.4.4.3 Upgrade of GBE10-EMXP10G/II, GBE22-EMXP10G/II, EMXP80G/II,

EMXP48/IIE, EMXP62/IIE, EMXP120/IIE, EMXP220/IIE, EMXP240/IIE and
TM-EMXP-1U-DC

Upgrade of boards from release R35.0 to R36.0.1 are disturbance free (HSU).
Upgrade of boards from older releases than R35.0 will cause a traffic disturbance when the
boards are restarted.
The downtime during a reboot is roughly 45 seconds, it is however strongly dependent on the
amount of configuration and can differ significantly from this value.
Please see the Technical Description for the Ethernet Muxponders/II and NID for more infor-
mation about traffic disturbances.

2.4.5 MDU40 or VOA8CHII

2.4.5.1 Upgrading MDU40 or VOA8CHII from previous releases to R36.0.1

If you are using optical control loops (OCL) together with MDU40 or VOA8CHII it is important
that the configuration is saved before an upgrade from previous releases to R36.0.1. If the
configuration is not saved before the upgrade there might be problems with the control loops if
a "fall back" of SW is executed.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 9 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.5 Notice
2.5.1 Upgrading FHAU/1, TM-FHAU1U–DC/1 and RFU-AC/1 to
R36.0.1
Upgrading the boards FHAU/1, TM-FHA1U-DC/1 and RFU-AC/1 from older releases to
R36.0.1 will not be allowed. The last software release to use with old functionality (e.g CPRI/
OBSAI/GBE) is R35.0. If any of these boards are used in a network node it will no longer be
possible to upgrade the node to newer releases (e.g. R36.0.1) until the boards are deleted
from the configuration and a new backup has been saved. After the configuration change it will
be possible to upgrade the nodes to R36.0.1 and re-create these boards for use with new
functionality (LAN10GBE).

2.5.2 Upgrading to R35.0.1 or above changes SSH keys

After upgrading from older releases than R35.0.1 to R35.0.1 or above ssh keys are changed
on the hosts. If re-generation of new ssh keys are wanted, please follow instructions in the
document "XTM Series Installation & Commissioning Configuration Guide" at chapter "Gener-
ating SSH Key Pair".

2.5.3 Upgrading TM-EMXP-XH800/DC to R35.0.1 may raise minor

alarm

Upgrading the board TM-EMXP-XH800/DC to release R35.0.1 may raise the alarm “Manage-
ment ports blocking overridden due to loss of management connectivity” with severity “Minor”.
If the minor alarm is received, this is likely the cause of pre R35.0.1 software which has the
"Local Craft access" parameter set to "disabled" as default value. This alarm can be cleared
by setting the parameter "Local craft ETH access" to "enabled". In ENM browser this parame-
ter resides at path ”Configuration/System/Access Control/Security”.

2.5.4 Upgrading 1x2 ROADM to R36.0.1 may give warning

When upgrading the boards 1x2ROADM/50G and 1x2ROADM/100G to release R36.0.1 the
alarm “Firmware Upgrade Available” with severity “Warning” may be raised. This warning indi-
cates that new firmware is available. If the warning is received, then a module on the ROADM
unit is using old firmware. It is recommended to proceed with the firmware upgrade to avoid
signal quality variations. Detailed information on how to obtain the firmware upgrade and re-
lated instructions can be found at Infinera Customer Support Portal. Upgrading the ROADM
firmware before upgrading to release R36.0.1 will avoid the warning.

2.5.5 Upgrading a system with a NID

When upgrading a node that has a NID (Network Interface Device) attached to an EMXP port,
the firmware on the NID has to be upgraded in order to support the new release. The NID can
be remotely upgraded from the EMXP by selecting the upgrade function and transferring a
new firmware to the NID. Detailed information on how to do NID firmware upgrade can be
found in the document “EMXP Installation & Commissioning Guide”. The NID firmware is in-
cluded in the XTM Series software delivery.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 10 (53) © Infinera 2021

 IMPORTANT INFORMATION TO READ BEFORE
UPGRADING

2.5.6 TPDDGBE and TPD10GBE with amplifiers

Disable APS on AMPs before upgrading.

In systems using TPDDGbE and/or TPD10GbE in combination with amplifiers with ”Automatic
Power Shutdown” (=APS) enabled, Set APS to disabled for all active amplifiers (amplifiers
with output power) in the network before upgrading and saving the configuration. Customers
that desire to use the APS-feature must manually activate APS on the amplifiers after the
upgrade.

2.5.7 TPQMR
If using a TPQMR of version R1A or R1B that is running 1G FC or 2G FC traffic, the format
may be configured to “other” with speed “850” (when using 1G FC) or “other” with speed
“1700” (when using 2G FC). 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. 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. Do not forget to save the
changes!

2.5.8 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. This means that a board of earlier release than R2B can-
not be used as a replacement to a board with the amplifier type set to ConstantGainHI.

2.5.9 CU/CUOSC/CU-SFP replacement with CU-SFPII/CU-SFPIII

The CU-SFP/II or CU-SFP/III can be used as a spare-part for CU/CUOSC/CU-SFP. However
some special procedures are needed when such a replacement should be made. Please, read
the 'Spare Part and Maintenance Guide’ document and the chapters related to ‘Replacing CU,
CUOSC, CU-SFP or CU-SFP/II’.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 11 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3 UPGRADE INSTRUCTIONS
It is recommended to reduce the number of backup files before an upgrade. With more
stored backup files the risk for time-out in DNA-M, ENM or CLI during an upgrade in-
creases. The reason for that is that the activation phase of the upgrade will take longer
time. Backup handling in ENM can be found by entering the ‘Backup Control’ link. A
system may normally have a primary and a secondary backup file.

All systems that should be upgraded to R36.0.1 must first be upgraded to R32.0.1 or lat-
er. If upgrading from older SW release then please follow the recommendations in
chapter ‘2.2 Supported versions to upgrade from’.

Please read the ‘Release Notes’, chapter ‘2.3 Postpone Firmware Activation function’
and chapter '‘2.4 Special Considerations’ before upgrading to this release.

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. If the network connection is poor, e.g. when
using ADSL modems etc you might get timeouts when downloading the software.

The allowed set of characters from which backup filenames should be constructed are the
following:
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvw
xyz0123456789._-
The last three characters are the <period>, <underscore>, and <hyphen> characters,
respectively.

3.1 New units/products in this release

New units/products in this release are:

• FXP400G-E....................400G Enhanced OTN Flexponder

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 12 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.2 Software upgrade using DNA-M (multiple nodes)

It is important that the DNA-M SW is of release R36.0 or later and with the latest patch level
when upgrading the nodes.

Fig. 3 DNA-M

3.2.1 Preparations DNA-M

Before the upgrade can begin some preparations has to be made.

Step 1 Check that your DNA-M server is of version R36.0 or later and with the lat-
est patch level. This is done by choosing ‘Help’ and then ‘About’ in DNA-
M Client or DNA-M Server.
Step 2 Copy the ‘Downloadables’ directory from the ENM Software to the tftp
subdirectory. This directory is usually located by default in:
For Windows operating systems:
‘C:\Program Files\transmode\tnm\var\tftproot\enmsw’
For Linux operating systems:
‘/var/tnm/tftproot/enmsw’

Step 3 Rename the directory from ‘Downloadables’ to something more release

related (i.e. R36A-1).

Step 4 Login to the DNA-M client with an ‘admin’ or ‘operator’ user.

Step 5 Select the subnet that you want to upgrade.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 13 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 6 Check active alarms in all nodes and save the printouts by right-clicking in
the subnet area and then choosing ‘Active Alarms->Including Alarms
from Sub-Subnets’ . Press the `Save as´ button to save the alarm list in
an optional directory on your computer. This alarm list will be used after
the upgrade to compare with the alarm list after the upgrade.

Step 7 Check that "Postpone Firmware Activation” settings are set as wanted.
This can only be performed from the ENM. See chapter '2.3 Postpone
Firmware Activation function' for details.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 14 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.2.2 Upgrade instructions DNA-M (multiple nodes)

Fig. 4 DNA-M Software Upgrade

Step 1 Start DNA-M client and login as admin or operator.

Step 2 Select the ‘subnet’ you want to upgrade in left pane.

Step 3 Verify in the subnet that none of the nodes that you want to upgrade is
grey.

Step 4 In the subnet, check the `Active Alarms´. Verify for the nodes that you
want to upgrade, that there are no alarms saying ‘Configuration not
saved’.
Step 5 Right-click in the subnet area and select `Maintenance->Software Up-
grade->Including Nodes from Sub-Subnets´.

Step 6 Enter a new task name in ‘New name’ edit field, e.g. ‘Subnet-A-check’.

Step 7 Fill in your server path e.g. ‘/enmsw/R36A-1/enm001a-r36a-1.spec’ in the

ENM Spec Path field.
Note: If you do not want to upgrade some of the nodes in the list seen in
the ‘Software Upgrade’ window, un-check those nodes in the `Selected´
field.
Step 8 Select ‘Check’ in the `Operation´ field and press the‘Apply’ button.

Step 9 Verify that all selected nodes say ‘Upgrade needed’ in the status field.

Step 10 Press ‘New Task’ button.

Step 11 Enter a ‘New Name’, e.g. ‘Subnet-A-Upgrade’.

Note: If you do not want to upgrade some of the nodes in the list seen in
the ‘Software Upgrade’ window, un-check those nodes in the `Selected´
field.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 15 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 12 Select ‘Upgrade’ in the `Operation´ field and press the ‘Apply’ button.
A confirmation box will appear with `The operation will now be started!` or
`Reboot will cause traffic disturbance!´ and the question `Do you want to
continue?´ Press the `OK´ button.
Step 13 Wait until all the nodes are upgraded. Verify that the `Status´ field shows
`OK´ for all the nodes.
NOTE:: If the upgrade of some nodes fails, identify and solve the source
of the problem and repeat steps 5 to 7 again. Possible upgrade issues that
can occur for DNA-M are listed further below.

Configuration changes made after the upgrade part (steps above) and before the node re-
starts (steps below) will not be used after the restart, even if a 'Save' is performed.

Step 14 Press the ‘New Task’ button.

Note: If you do not want to upgrade some of the nodes in the list seen in
the ‘Software Upgrade’ window, un-check those nodes in the `Selected´
field.
Step 15 In the field ‘Operation:’ choose how to restart the boards:
Alternative 1: Only restart boards that have been upgraded. Applicable
for XTM nodes at software level R31.1.0 or above.
- Select ‘Restart Pending Boards’ (Recommended)
Alternative 2: Restart all boards.
- Select ‘Restart All’
Press the ‘Apply’ button
A confirmation box will appear with `The operation will now be started!` or
`Reboot will cause traffic disturbance!´ and the question `Do you want to
continue?´ Press the `OK´ button.
Step 16 After the restart has completed confirm that the `Status´ field shows `OK´
for all the nodes.
Press the `Close´ button.
Check the active alarms in all nodes by right-clicking in the subnet area
and then choosing `Active alarms´. Compare this list with the one you
saved before the upgrade. If the alarm list differs, try to find the root
cause.
Step 17 Right-click in the subnet area and select `Maintenance->Software Up-
grade->Including Nodes from Sub-Subnets´.

Step 18 In the ‘Task field’ select the first task made in these instructions, e.g.
‘Subnet-A-Check’.
Step 19 In the ‘Task field’ select ‘New Task’.
Note: If you did not upgrade some of the nodes in the list seen in the ‘Soft-
ware Upgrade’ window, un-check those nodes in the `Selected´ field.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 16 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 20 Select ‘Check’ in the `Operation´ field and press the ‘Apply’ button.

Step 21 Verify that all the selected nodes say ‘Up to date’ in the `Status´ field.
Press the `Close´ button to finish the upgrade procedure.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 17 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.2.3 Upgrade issues – DNA-M

Upgrade issue: Timeout

If the result of an upgrade is “failed”, then double-click on the status field in the Software Up-
grade window at DNA-M Client.
If the error message is “A timeout occurred during the operation.”
DNA-M Example:
...
File transfer successful.(9:54 AM)
The upgrade operation is started(9:54 AM)
A timeout occurred during the operation.(10:09 AM)
Please perform a check operation to see the result.(10:09 AM)
Upgrade failed.(10:09 AM)
Release failed, but it might be normal if the node is supposed to restart.

When a "timeout" occurs, the upgrade is still ongoing in the background. One of the final steps
of the upgrade procedure is to ensure that the saved backup files are compatible with the new
release. To do this, a "backup conversion" process is started to go through all the current re-
lease backup files and convert these to the new release backup file structure.
The backup conversion will take longer if there are a large number of backup files or a
lot of configuration in a backup file, or a combination of both.
This requires a certain waiting time before the system will be responsive again to receive com-
mands. Control of the system is given back to the user when the backup conversion takes
more than 15 minutes.
When the control of the system is given back to the user, create a new task and perform a
check/upgrade command on the node again.

Upgrade issue: FTP

Sometimes you might get an alarm in the DNA-M saying that the FTP to one or more of the
node fails after the upgrade. This alarm will disappear within 15 minutes or when making a
‘Full refresh’ from the DNA-M.

Upgrade issue: Reserve node failed

In some rare cases when losing contact with nodes during the upgrade you might need to “un-
lock” the upgrade process in the nodes and then perform the upgrade again. You can check if
you are in this state by double-clicking on the status field for a specific node in Upgrade
window.
If the message says: ”Reserve node failed! Possible causes: Another task, or a local ENM
GUI user may have an ongoing upgrade operation. SNMP SET operations are not enabled in
the node. A previous task was abnormally terminated.”
To unlock the node you can login to CLI and make a “swu unlock” or by using the unlock but-
ton in GUI, but make sure that no one else is trying to upgrade the node at the same time!

Upgrade issue: Verification script not found

If the result of an upgrade is “failed”, then double-click on the status field in the Software Up-
grade window at DNA-M Client. If the error message is “Verification script not found” or
“Downloaded file is corrupt”, then the application has to be completely removed from the
control unit and then run the upgrade procedure again. E.g:

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 18 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Status log (in DNA-M Client):

1.1 appl cuappl01a-r31a-36 Prepare activation failed

1.1 Verification script not found (/opt/appl/cuappl01a-r31a-36/etc/init.d/
verify_startscript.sh)
Activation is NOT performed

Delete the application using CLI: (Syntax: ‘swu delete appl <chassis> <slot> <file>’)
swu delete appl 1 1 cuappl01a-r31a-36
Fault message in CLI:

1.1 Directory not found

It could be the result, when the directory never was created during the
installation (most likely if the executing SW are of release R27 or later).

Restart issue: Restart failed

If the result of a restart for a node is “failed”, then re-issue a ‘Check’ in the `Operation´ field
and press the‘Apply’ button. In some rare cases communication may have been lost and a
time-out triggered the failure even if the restart was successful.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 19 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.3 Software upgrade using ENM (individual node)

It is important that only the user that performs the upgrade is logged in to the ENM GUI.

Fig. 5 ENM GUI Main window

• Go through the numbered items below for all the nodes that need to be upgraded.
• Work with one node at a time and finish the upgrade for that node before starting with the
next node.
• Be aware that the IP address used below is just an example and that it should be changed
to the IP address of the ‘TFTP’ server computer.
• The ‘show’ command responses are examples as well.
• The nodes can be upgraded in any order, as long as you work with one node at a time.
However, Infinera 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 con-
nectivity to the whole network.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 20 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.3.1 Preparations ENM

Before the upgrade can begin some preparations have to be made.

Step 1 Create a new folder and name it ‘tftp’ on your tftp server computer. Make
sure that you choose a computer that can be reached from all the nodes
that you want to upgrade.

Step 2 Put all R36.0.1 software files and the tftp program called ‘tftpd32.exe’ in
that folder. The files and the program can be found under the directory
‘downloadables’ in the ENM software package.

Step 3 Start the tftp server, by clicking on the file named ‘tftpd32.exe’.

Step 4 Press the ‘Settings’ button in tftp server window.

Step 5 Un-check ‘Option negotiation’.

Step 6 Change Server Configuration time-out seconds to 8 in tftp server.

Step 7 Change ‘Max retransmit’ to 9 in tftp-server.

Step 8 Press the ‘OK’ button to apply the settings.

Step 9 Check active alarms in all nodes and save the printouts. This is done in
the following way on a PC:
1. Select ‘Alarms and events’ then ‘Current’ in left pane of the ENM
GUI.
2. Mark all the alarm text.
3. Click on the right mouse button.
4. Choose ‘Copy’.
5. Open ‘Notepad’ or ‘Wordpad’.
6. Select ‘Edit’ in the menu of Notepad or Wordpad.
7. Select ‘Paste’. Save the file

Fig. 6 Select ‘Active Alarms’

Step 10 Check that "Postpone Firmware Activation” settings are set as wanted.
This can only be performed from the ENM. See chapter '2.3 Postpone
Firmware Activation function' for details.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 21 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.3.2 Upgrade instructions ENM (individual node)

Step 1 Login to the node as user “oper”, using the web-browser (ENM GUI).

Step 2 Check that you have a R32.0.1 release or later. If not, then follow instruc-
tions at chapter 2.2 (supported versions to upgrade from). The information
about software version could be read at the lower left corner of the ENM
GUI, see Figure 5. (includes r29a).

Step 3 Save the configuration before continuing, this is done by pressing the
“Save” button in the ENM GUI, see Figure 7. Then enter a file name in
the dialogue that appears and press the “Save” button.

Fig. 7 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. Then refresh
the page. Close down all tabs that are not used at the moment. To have only one session is
strongly recommended. After the upgrade similar measures may be needed.

Step 4 Select ‘Software control’ in left panel of ENM GUI.

Fig. 8 ENM GUI Maintenance dialog

Step 5 Click on the button ’Select ENM Spec’.

Step 6 In the ’Select ENM spec’ pop-up window, select ’Remote’ in the Server
field.
Step 7 Enter the IP address to your TFTP server in the IP edit field.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 22 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 8 Fill in your server path e.g. ‘/enm001a-r36a-1.spec’ in the Path edit field
and press the Apply button.

Step 9 Select ’Check’ in the last row of the Action field and press the Apply but-
ton at the bottom of the ENM GUI.
Step 10 In the ‘Confirm action’ pop-up window, press the ’Execute’ button.

Step 11 Verify in the tab SW Status that it shows lines of: “Needs upgrading to...”

Step 12 Select ’Upgrade’ in the last row of the Action field and press Apply but-
ton at the bottom of the ENM GUI.
Step 13 In the ‘Confirm action’ pop-up window, press the ’Execute’ button. Now
the software will be downloaded and installed.
Step 14 When the upgrade procedure is done, verify that SW status field says:
Software update on reboot
If the SW status is not correct, then repeat the upgrade steps from step 5.
Possible upgrade issues that can occur for ENM are listed further below.

Step 15 When the correctness of the SW status is verified then a reboot of all
boards are needed in order to set the new software in use.
Select ’Reboot ’ in the last row of the Action field and press Apply button
at the bottom of the ENM GUI.
In the ‘Confirm action’ pop-up window, press the ’Execute’ button. Now all
boards will be rebooted.

It will be impossible to log in to the node before it has started again, this could take 1-2
minutes.

Step 16 Login to the node again using ENM GUI. Login as user ‘oper’ or ‘root’.

Step 17 Select Software control in left panel of ENM GUI.

Step 18 Check in the SW status field that it says: Ok.

Check the active alarms, compare with the active alarms before the SW
upgrade by choosing ‘Alarms and events’ in left pane of the ENM GUI
and then ’Current’. If the alarms differs, try to find the root cause.
If there are alarms saying “Interwork failed” then probably the SW is not
correctly installed. Then repeat the steps in this description.

Step 19 Go back to ‘Step 1’ and start with the next node in the network.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 23 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.3.3 Upgrade issues – ENM

Upgrade issue: Timeout

If the result of an upgrade in the ‘Software control’ tab is “failed”, then check the text printout.
If the error message is “Command timed out...”
ENM Example:
...
1.1 boot cuboot02a-r35a-1 Downloading to local board 17:04:42
1.1 boot cuboot02a-r35a-1 Installing on board 17:04:42
1.1 boot cuboot02a-r35a-1 Install done 17:04:47
1.1 kernel oskernel02a-r36a-1 Downloading to local board 17:04:48
1.1 kernel oskernel02a-r36a-1 Installing on board 17:04:48
1.1 kernel oskernel02a-r36a-1 Install done 17:05:00
1.1 appl cuappl03a-r36a-32 Downloading to local board 17:05:14
1.1 appl cuappl03a-r36a-32 Installing on board 17:05:14
1.1 appl cuappl03a-r36a-32 Install done 17:06:37
Command timed out....
When a "timeout" occurs, the upgrade is still ongoing in the background. One of the final steps
of the upgrade procedure is to ensure that the saved backup files are compatible with the new
release. To do this, a "backup conversion" process is started to go through all the current re-
lease backup files and convert these to the new release backup file structure.
The backup conversion will take longer if there are a large number of backup files or a
lot of configuration in a backup file, or a combination of both.
This requires a certain waiting time before the system will be responsive again to receive com-
mands. Control of the system is given back to the user when the backup conversion takes
more than 15 minutes.
When the control of the system is given back to the user, repeat the upgrade steps from step
5 on the node again.

Upgrade issue: Backup conversion

If the result of an upgrade in the ‘Software control’ tab is “Failed to convert backup”, then
check the text printout.
If the error message is “Conversion failed”
ENM Example:
...
1.1 appl cuappl03a-r36a-32 Failed to convert backup 10:33:10
1.1 /opt/appl/cuappl03a-r36a-32/bin/convert_backup: Conversion failed:
check '/var/log/lumentis/convert_backup.log.0' for detail

Activation is NOT performed.

The recommended remedy is to remove older unused backup files. Using ENM browser the
location of backup files can be found at path “Configuration/Backup Control/ Backup Files”.
After removal of old backup files, re-try the upgrade procedure.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 24 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Upgrade issue: Verification script not found

If the result of an upgrade in the ‘Software control’ tab is “failed”, then check the text printout.
If the error message is “Verification script not found” or “Downloaded file is corrupt”,
then the application has to be completely removed from the control unit, then run the upgrade
procedure again..
E.g.
1.1 appl cuappl01a-r31a-36 Prepare activation failed
1.1 Verification script not found (/opt/appl/cuappl01a-r31a-36/etc/init.d/
verify_startscript.sh)
Activation is NOT performed

Deletion of the application is done in the CLI for the failed node. E.g. with the above error mes-
sage would be:
swu delete appl 1 1 cuappl01a-r31a-36

Upgrade issue:
Lack of CU memory can result in a failed upgrade state with no additional information
If the upgrade procedure fails on a multiple subrack node with CU-SFP/II as master CU with
no additional information, it could be due to lack of available memory on the main CU causing
the CU to perform a reboot before the upgrade is complete. If this happens, the upgrade pro-
cedure will most likely fail and continue to fail on consecutive upgrade attempts.
Please contact Infinera TAC support for further information.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 25 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.4 Software upgrade using CLI (individual node)

Fig. 9 CLI Maintenance interface

• Go through the numbered items below for all the nodes that need to be upgraded.
• Work with one node at a time and finish the upgrade for that node before starting with the
next node.
• 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.
• The show command responses are examples as well. The actual printouts depend on the
node configuration, the type and amount of boards can vary. The printouts below corre-
spond to a basic configuration containing one control unit (CU) and only one traffic unit
(TU).
• The nodes can be upgraded in any order, as long as you work with one node at a time.
However, Infinera recommends you to start with the far end nodes and work towards the
node where the tftp server computer is connected.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 26 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.4.1 Preparations CLI

Before the upgrade can begin some preparations have to be made.

Step 1 Create a new folder and name it “tftp” on your “tftp server computer”. Make
sure that you choose a computer that can be reached from all the nodes
you want to upgrade.

Step 2 Put all R36.0.1 software files and the tftp program called tftpd32.exe in
that folder. The files and the program can be found under the directory
“downloadables” in the ENM software package.

Step 3 Start the tftp server, by clicking on the file named tftpd32.exe.

Step 4 Press Settings button in tftp-server window.

Step 5 Uncheck ‘Option negotiation’.

Step 6 Change Server Configuration timeout seconds to 8 in tftp-server.

Step 7 Change ‘Max retransmit’ to 9 in tftp-server.

Step 8 Press OK to apply the settings.

Step 9 Check active alarms in all nodes and save the printouts. These printouts
should be compared with the alarm printouts after the upgrade. Use the
command:
activeAlarms
Step 10 Check that "Postpone Firmware Activation” settings are set as wanted.
For example:
show ::eq::board::<boardtype>:<subrack>:<slot>::postponeFwUpgrade
or:
show ::eq::board::*::postponeFwUpgrade

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 27 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.4.2 Upgrade instructions CLI (individual node)

Step 1 Login to the node as an oper user, using the Command Line Interface (CLI).

Step 2 Check that you have at least a R32.0.1 release. This is done by verifying that all the
softwares in the ‘Application’ column when performing ‘swu show executing’
includes r31a or later. If not then follow instructions at chapter 2.2 (supported
versions to upgrade from).
Use the command:
swu show executing
Expected printout (for CU systems):

Board Boot Kernel Application

1.1 cuboot02a-r32a-3 oskernel02a-r32a-2 cuappl03a-r32a-32
1.3 tuboot01a-r14a-1 oskernel01a-r19a-2 tuappl01a-r32a-31
1.5 tuboot02a-r32a-2 oskernel02a-r32a-2 tuappl02a-r32a-31

Step 3 Save the node configuration. Use the command:

save
Expected printout:

Infinera::> save
saving to config.xml
File exists, overwrite? (yes or no) (no) yes
.......................................................
Saving backup on central unit.
Invalidating backup copies on traffic units.
Slot 5: done
Slot 3: done
Transferring backup to traffic units.
Slot 5: done
Slot 3: done
Transferring additional persistent files to traffic units.
Slot 5: snmpd.conf passwd done
Slot 3: snmpd.conf passwd done
Infinera::>

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 28 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 4 Remove all old previous software. Use the command:

swu –F clean all all
Expected printout:

1.1 boot Cleaned 04:35:37

1.1 kernel Cleaned 04:35:37
1.1 appl Cleaned 04:35:40
1.1 appl Cleaned 04:35:40
1.3 boot Cleaned 04:35:40
1.3 kernel Cleaned 04:35:40
1.3 appl tuappl01a-r30a-40 Deleted 04:35:43
1.3 appl Cleaned 04:35:43
1.5 boot Cleaned 04:35:43
1.5 kernel Cleaned 04:35:43
1.5 appl Cleaned 04:35:43
1.5 appl Cleaned 04:35:43
1.1 downloaded Cleaned 04:35:45
We are done.
Make sure that folder /tftpboot/download/ is cleaned and empty, before starting the
upgrade (command: swu show downloaded).

Step 5 Upgrade application, boot, kernel and file system SW. Use the command:
swu +FS upgrade all all 172.16.15.80/enm001a-r36a-1.spec
Expected printout:

Downloading from host to node: Download complete.

4577 bytes downloaded in 0.65 seconds
1.3 appl tuappl01a-r32a-31 Needs upgrading
1.3 tuappl01a-r36a-30 is expected
…
1.5 appl tuappl02a-r32a-31 Needs upgrading
1.5 tuappl02a-r36a-30 is expected
…
Downloading 172.16.15.80/tuappl01a-r36a-30.ppc_8xx.rpm..
Download complete. 6375768 bytes downloaded in 16.365 seconds
…
Wait until all software are activated on each board.

If the upgrade fails for any reason at this stage, then one should repeat
‘Step 4’ and ‘Step 5’ again. Possible upgrade issues that can occur
for CLI are listed further below.

Step 6 Check that all boards have the expected software. Use the commands:
swu show next
Expected printout (for CU systems):

Board Boot Kernel Application

1.1 cuboot02a-r32b-2 oskernel02a-r36a-1 cuappl03a-r36a-32
fs=r35a-3
1.3 tuboot01a-r14a-1 oskernel01a-r35a-1 tuappl01a-r36a-30
fs=r22a-1
1.5 tuboot02a-r36a-2 oskernel02a-r36a-1 tuappl02a-r36a-30
fs=r35a-3

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 29 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 7 Check that all boards have the right file system installed. Use the command
swu show filesystem all
Expected printout:

1.1 fs r35a-2 15:18:11

1.3 fs r22a-1 15:18:11
1.5 fs r35a-2 15:18:11
We are done.

Step 8 Compare the software information in ‘Step 6’ and ‘Step 7’ with ‘Table 2’ to ‘Table 7’
at ‘Chapter 4’.

Make sure that all the software’s are correctly installed and acti-
vated for each board (i.e. Check that both CU and TUs have the
same software release) before rebooting the node.
If not all of the above expected software are correct, go back and per-
form the upgrade procedure again.
NOTE: Configuration changes made after the upgrade part (steps
above) and before the node reboots (steps below) will not be used
after the reboot, even if a 'Save' is performed.

Step 9 If all software corresponds to release R36.0.1 reboot all boards.

Use the command: (recommended)
swu reboot all
An alternative reboot command is available starting from release R31.1.0 and on-
wards. The command only reboots boards which needs to be re-started. Boards
that have the activated software already running are not re-started.
swu -pending reboot all
A third alternative reboot command which power cycle boards and is only supported
by specific HW is:
swu -cold reboot all

Using reboot option ‘cold’ will cause traffic disturbance.

Expected printout:

1.3 Reboot ordered

1.5 Reboot ordered
1.1 Reboot ordered

We are done
Infinera::> Rebooting...
The system is going down NOW!

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 30 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

Step 10 Log in to the node again as ‘oper’ user.

It will be impossible to log in to the node before it has started again,

this could take 1-2 minutes.

Step 11 Check the active alarms, compare with the active alarms before the SW upgrade.
Use the command:
activeAlarms
If there are alarms saying “Interwork failed” then probably the SW is not correctly in-
stalled. Then repeat the steps in this description.

Step 12 Check that all boards have the right R36.0.1 software installed. Use the command:
swu show executing
Expected printout (for CU systems):

Board Boot Kernel Application

1.1 cuboot02a-r32b-2 oskernel02a-r36a-1 cuappl03a-r36a-32
fs=r35a-3
1.3 tuboot01a-r14a-1 oskernel01a-r35a-1 tuappl01a-r36a-30
fs=r22a-1
1.5 tuboot02a-r36a-2 oskernel02a-r36a-1 tuappl02a-r36a-30
fs=r35a-3

We are done.
See ‘Step 6’ for information about what the software should be.

Step 13 Check that all boards have the right file system installed. Use the command
swu show filesystem all
Expected printout:

1.1 fs r35a-2 15:46:40

1.3 fs r22a-1 15:46:40
1.5 fs r35a-2 15:46:40
See ‘Step 6’ for information about what the software should be.
If all installed software corresponds to R36.0.1 you are finished, go back to ‘Step1’ and start
with the next node in the network.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 31 (53) © Infinera 2021

 UPGRADE INSTRUCTIONS

3.4.3 Upgrade issues - CLI

Upgrade issue: Timeout

If the result of an upgrade is “failed”, then check the text printout.
If the error message is “Command timed out...”
CLI Example:
...
1.1 boot cuboot02a-r35a-1 Downloading to local board 17:04:42
1.1 boot cuboot02a-r35a-1 Installing on board 17:04:42
1.1 boot cuboot02a-r35a-1 Install done 17:04:47
1.1 kernel oskernel02a-r36a-1 Downloading to local board 17:04:48
1.1 kernel oskernel02a-r36a-1 Installing on board 17:04:48
1.1 kernel oskernel02a-r36a-1 Install done 17:05:00
1.1 appl cuappl03a-r36a-32 Downloading to local board 17:05:14
1.1 appl cuappl03a-r36a-32 Installing on board 17:05:14
1.1 appl cuappl03a-r36a-32 Install done 17:06:37
Command timed out....
When a "timeout" occurs, the upgrade is still ongoing in the background. One of the final steps
of the upgrade procedure is to ensure that the saved backup files are compatible with the new
release. To do this, a "backup conversion" process is started to go through all the current re-
lease backup files and convert these to the new release backup file structure.
The backup conversion will take longer if there are a large number of backup files or a
lot of configuration in a backup file, or a combination of both.
This requires a certain waiting time before the system will be responsive again to receive com-
mands. Control of the system is given back to the user when the backup conversion takes
more than 15 minutes.
When the control of the system is given back to the user, repeat the same SWU upgrade com-
mand that was entered previously before the time out.

Upgrade issue: Backup conversion

If the result of an upgrade is “Failed to convert backup”, then check the text printout.
If the error message is “Conversion failed”
CLI Example:
...
1.1 appl cuappl03a-r36a-32 Failed to convert backup 10:33:10
1.1 /opt/appl/cuappl03a-r36a-32/bin/convert_backup: Conversion failed:
check '/var/log/lumentis/convert_backup.log.0' for detail

Activation is NOT performed.

The recommended remedy is to remove older unused backup files. Using CLI the location of
backup files can be found using command “::backup::file::”. After removal of old backup files,
re-try the upgrade procedure.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 32 (53) © Infinera 2021

 SOFTWARE VERSIONS

4 SOFTWARE VERSIONS
The software versions for R36.0.1 are shown in this chapter.

4.1 Software versions for first generation of Control Units

Table 4 SW for Control Unit (CU1)

Board Type Application Boot Kernel File System Released in

CU1 1 Software

CU cuappl01a-r31a-36 cuboot01a-r14a-1 oskernel01a- osappl01a-r22a-1 1.0.1 (ESS)

r19a-2

CUOSC cuappl01a-r31a-36 cuboot01a-r14a-1 oskernel01a- osappl01a-r22a-1 4.1.1 (ESS)

r19a-2
1. CU1 - Control board that has older CPU which is recognized by number 01 in the SW file name and suffix .rpm (xxxx01a-xxxx.
ppc _8xx.rpm).

4.2 Software versions for second generation of Control

Unit
Table 5 SW for Control Unit (CU2)

Board Type Application Boot Kernel File System Released in

CU2 1 Software

CU-SFP cuappl02a-r33b-43 cuboot02a-r32b-2 oskernel02a- osappl02a-r33a-1 8.0 (ESS)

r33a-1
1. Control board that has new CPU which is recognized by number 02 in the SW file name, see below (xxxx02a-xxxx.powerpc.
pkg).test

4.3 Software versions for third generation of Control Unit

Table 6 SW for Control Unit (CU3)

Board Type Application Boot Kernel File System Released in

CU3 1 Software

CU-SFP/II cuappl03a-r36a-32 cuboot02a-r32b-2 oskernel02a- osappl02a-r35a-6 18.0

r36a-1
1. Control board that has new CPU which is recognized by number 03 in the SW file name, see below (xxxx03a-xxxx.powerpc.
pkg).

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 33 (53) © Infinera 2021

 SOFTWARE VERSIONS

4.4 Software versions for fourth generation of Control

Unit
Table 7 SW for Control Unit (CU4)

Board Type Application Boot Kernel File System Released in

CU4 1 Software

CU-SFP/III cuappl04a-r36a-32 cuboot04a-r36a-2 oskernel04a- osappl04a-r35a-2 27.0

r36a-1
1. Control board that has new CPU which is recognized by number 04 in the SW file name, see below (xxxx04a-xxxx.powerpc.
pkg).

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 34 (53) © Infinera 2021

 SOFTWARE VERSIONS

4.5 Software versions for first generation of Traffic Units

Table 8 SW for different TU1 boards

Application CU-less
Board Type TU1 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

4x2G5-MXP10G tuappl01a- cusomappl01a- tuboot01a- oskernel01a- osappl01a- 10.0

r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm

GBE9-MXP10G tuappl01a- cu9gbeap- tuboot01a- oskernel01a- osappl01a- 6.0

r36a-30 pl01a-r27a-30. r14a-1 r35a-1 r22a-1
ppc_8xx.rpm

GXP10/2500-SFP tuappl01a- cugxpappl01a- tuboot01a- oskernel01a- osappl01a- 3.0

r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm

MDU40/50G-EVEN, tuappl01a- cumduappl01a- tuboot01a- oskernel01a- osappl01a- 10.0

MDU40/50G-ODD, r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
MDU40/50G-EVEN-L, 8xx.rpm 17.0
MDU40/50G-ODD-L

MXP028 tuappl01a- cumxpappl01a- tuboot01a- oskernel01a- osappl01a- 1.0 (ESS)

r31b-22 r27a-30.ppc_ r14a-1 r19a-2 r22a-1
8xx.rpm

MXP8 tuappl01a- cumxpappl01a- tuboot01a- oskernel01a- osappl01a- 2.3

r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm

OA10, OA210/10C, tuappl01a- cuoaappl01a- tuboot01a- oskernel01a- osappl01a- 3.2, 3.2,

OA15, OA2x15, OA17, r36a-30 r31a-36.ppc_ r14a-1 r35a-1 r22a-1 2.3.2,
OA2x17, OA20, 8xx.rpm 2.3.2,4.0,
OA2x20, OA20C/LG, 4.0,6.0,
OA10C/FG, OA20C/ 6.0,10.0,
VG, OA2-20/20/CC/VG 10.0 17.0
17.0

TP10G, TP10G-LAN tuappl01a- cu10gappl01a- tuboot01a- oskernel01a- osappl01a- 4.1.1, 2.3.2

r31b-22 r27a-30.ppc_ r14a-1 r19a-2 r22a-1 (ESS)
8xx.rpm

TP10GCLX /xxxx R1B tuappl01a- cu10gappl01a- tuboot01a- oskernel01a- osappl01a- 4.1.1 (ESS)
r33b-43 r27a-30.ppc_ r14a-1 r19a-2 r22a-1
8xx.rpm

TP10GCLX/TC tuappl01a- cu10gtcap- tuboot01a- oskernel01a- osappl01a- 9.1.1 (ESS)

r33b-43 pl01a-r27a-30. r14a-1 r19a-2 r22a-1
ppc_8xx.rpm

TPD10GBE-BU tuappl01a- cudtgappl01a- tuboot01a- oskernel01a- osappl01a- 8.0

r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm

TPD10G-L-BU tuappl01a- cud10glap- tuboot01a- oskernel01a- osappl01a- 4.0

r36a-30 pl01a-r27a-30. r14a-1 r35a-1 r22a-1
ppc_8xx.rpm

TPDDGBE tuappl01a- cuqxpappl01a- tuboot01a- oskernel01a- osappl01a- 3.1

r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm

TPMR2500 tuappl01a- cumrappl01a- tuboot01a- oskernel01a- osappl01a- 1.0.1 (ESS)

r32b-37 r27a-30.ppc_ r14a-1 r19a-2 r22a-1
8xx.rpm

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 35 (53) © Infinera 2021

 SOFTWARE VERSIONS

Table 8 SW for different TU1 boards (cont’d.)

TPMR25-V2 tuappl01a- cumrappl01a- tuboot01a- oskernel01a- osappl01a- 8.0

r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm

TPQMR tuappl01a- cuqmrappl01a- tuboot01a- oskernel01a- osappl01a- 2.1.2

TPQMRi r36a-30 r27a-30.ppc_ r14a-1 r35a-1 r22a-1 7.0
8xx.rpm

OA2-21SEED tuappl01a- cuoaappl01a- tuboot01a- oskernel01a- osappl01a- 20.0

r36a-30 r31a-36.ppc_ r14a-1 r35a-1 r22a-1
8xx.rpm
1. Traffic board that has older CPU that could be easily recognized by number 01 in the SW file name and suffix .rpm (xxxx01a-
xxxx.ppc _8xx.rpm).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.6 Software versions for second generation of Traffic

Units
Table 9 SW for different TU2 boards

Application CU-less
Board Type TU2 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

1x2ROADM/100G tuappl02a- cur4x1appl01a- tuboot02a- oskernel02a- osappl02a- 17.0

1x2ROADM/50G r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

1x4ROADM/100G tuappl02a- cur4x1appl01a- tuboot02a- oskernel02a- osappl02a- 12.0

r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
1X4ROADM-F powerpc.pkg 28.0

1x4ROADM–F/II 34.0

1x8ROADM/50G tuappl02a- cur4x1appl01a- tuboot02a- oskernel02a- osappl02a- 15.0

r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

1X9ROADM-F tuappl02a- cur4x1appl01a- tuboot02a- oskernel02a- osappl02a- 30.0.0

r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

GBE9/MXP10GFEC tuappl02a- cumxfecap- tuboot02a- oskernel02a- osappl02a- 12.0

r36a-30 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

GBE10-EMXP10 tuappl02a- cuemxpap- tuboot02a- oskernel02a- osappl02a- 12.0 (ESS)

GBE22-EMXP10 r32b-37 pl01a-r27a-32. r32b-2 r32b-2 r32a-1
powerpc.pkg

MS-MXP, tuappl02a- cumsmap- tuboot02a- oskernel02a- osappl02a- 11.0

MSMXPDQGBE r36a-30 pl01a-r36a-32. r36a-2 r36a-1 r35a-6 13.0
MSMXPQMS2G5 powerpc.pkg 14.0

OCM/2P tuappl02a- cuocmappl01a- tuboot02a- oskernel02a- osappl02a- 11.0

r36a-30 r31a-33. r36a-2 r36a-1 r35a-6
powerpc.pkg

OCM/8P tuappl02a- cuocm8pap- tuboot02a- oskernel02a- osappl02a- 31.1.0

r36a-30 pl01a-r32b-37. r36a-2 r36a-1 r35a-6
powerpc.pkg

PCU/2P tuappl02a- cupcuappl01a- tuboot02a- oskernel02a- osappl02a- 13.0

r36a-30 r27a-30. r36a-2 r36a-1 r35a-6
powerpc.pkg

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 36 (53) © Infinera 2021

 SOFTWARE VERSIONS

Table 9 SW for different TU2 boards (cont’d.)

TP10G/TC-ER tuappl02a- cu10g2ap- tuboot02a- oskernel02a- osappl02a- 12.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

TP10GCLX/TC R2B tuappl02a- cu10g2ap- tuboot02a- oskernel02a- osappl02a- 12.0 (ESS)

r33b-43 pl01a-r33b-43. r33a-1 r33a-1 r33a-1
powerpc.pkg

TP10GOTN/TC tuappl02a- cu10g2ap- tuboot02a- oskernel02a- osappl02a- 14.0 (ESS)

r28b-1 pl01a-r28b-1. r28a-2 r28a-3 r28a-2
powerpc.pkg

TPQMS tuappl02a- cuqmsappl01a- tuboot02a- oskernel02a- osappl02a- 13.0

r36a-30 r31a-36. r36a-2 r36a-1 r35a-6
powerpc.pkg

VOA-8CH/II tuappl02a- cuvoa2ap- tuboot02a- oskernel02a- osappl02a- 11.0

r36a-30 pl01a-r27a-30. r36a-2 r36a-1 r35a-6
powerpc.pkg

VOA-8CH/SFP tuappl02a- cuvoa8sap- tuboot02a- oskernel02a- osappl02a- 19.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

Newer HW revisions tuappl02a- cuoar2appl01a- tuboot02a- oskernel02a- osappl02a- TBD

of R2A and later: r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
OA20C/LG (R2A_L), powerpc.pkg
OA20C/VG (R2A_I),
OA2-20/20/CC/LG
(R2A_L),
OA2-20/20/CC/VG
(R2A_K)

OTDR8P tuappl02a- cuotdrappl01a- tuboot02a- oskernel02a- osappl02a- 32.0.0

r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg
1. 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.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.7 Software versions for third generation of Traffic Units

Table 10 SW for different TU3 boards

Application CU-less
Board Type TU3 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

GBE10-EMXP10G/II tuappl03a- cuemxp2ap- tuboot02a- oskernel02a- osappl02a- 15.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
GBE22-EMXP10G/II powerpc.pkg 15.0

EMXP80G/II 16.0

EMXP40G/II - cuemxp2ap- tuboot02a- oskernel02a- osappl02a- 18.0 (ESS)

pl01a-r32b-37. r32b-2 r32b-2 r32a-1
powerpc.pkg

MSMXP10G tuappl03a- cumsm10ap- tuboot02a- oskernel02a- osappl02a- 14.0

r36a-30 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
MSMXP10G/TC-ER powerpc.pkg

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 37 (53) © Infinera 2021

 SOFTWARE VERSIONS

Table 10 SW for different TU3 boards (cont’d.)

MXP8/II tuappl03a- cumxp2ap- tuboot02a- oskernel02a- osappl02a- 16.0

r36a-30 pl01a-r31a-36. r36a-2 r36a-1 r35a-6
powerpc.pkg

TM-MBA/2 - cumbaappl01a- tuboot02a- oskernel02a- osappl02a- 17.0

r36a-32. r36a-2 r36a-1 r35a-6
TM-MBA/2E powerpc.pkg
1. TU3- Traffic board that has new CPU unit with SW that could be easily recognized by number 03 in the SW file name (tuappl03a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.8 Software versions for fourth generation of Traffic

Units
Table 11 SW for different TU4 boards

Application CU-less
Board Type TU4 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

TPQ10GFEC tuappl04a- cutpqappl01a- tuboot02a- oskernel02a- osappl02a- 17.0

r36a-30 r36a-31. r36a-2 r36a-1 r35a-6
TPQ10GFEC/I powerpc.pkg 21.0

TPQMP tuappl04a- cuqmpappl01a- tuboot02a- oskernel02a- osappl02a- 18.0

r36a-30 r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

MDU16-CL/50G tuappl04a- cumdu16ap- tuboot02a- oskernel02a- osappl02a- 18.0 (ESS)

r33b-43 pl01a-r27a-30. r33a-1 r33a-1 r33a-1
powerpc.pkg
1. TU4- Traffic board that has new CPU unit with SW that could be easily recognized by number 04 in the SW file name (tuappl04a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.9 Software versions for fifth generation of Traffic Units

Table 12 SW for different TU5 boards

Application CU-less
Board Type TU5 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

MS-TP/40G tuappl05a- cu40gtpap- tuboot02a- oskernel02a- osappl02a- 20.0

r36a-31 pl01a-r27a-30. r36a-2 r36a-1 r35a-6
powerpc.pkg

MS-MXP/40G tuappl05a- cu40gmxap- tuboot02a- oskernel02a- osappl02a- 20.0

r36a-31 pl01a-r27a-30. r36a-2 r36a-1 r35a-6
powerpc.pkg

MXP10GOTN tuappl05a- cumtomap- tuboot02a- oskernel02a- osappl02a- 21.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

TPHEX10GOTN tuappl05a- cut10goap- tuboot02a- oskernel02a- osappl02a- 23.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 38 (53) © Infinera 2021

 SOFTWARE VERSIONS

Table 12 SW for different TU5 boards (cont’d.)

TP100GOTN tuappl05a- cut100oap- tuboot02a- oskernel02a- osappl02a- 23.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

TP100GOTN/II tuappl05a- cutcoiiappl01a- tuboot02a- oskernel02a- osappl02a- 28.0

r36a-31 r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

MXP100GOTN tuappl05a- cum100oap- tuboot02a- oskernel02a- osappl02a- 23.1

r36a-31 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

MXP-MBH/1 tuappl05a- cumbhap- tuboot02a- oskernel02a- osappl02a- 17.0 (ESS)

r28b-3 pl01a-r27a-30. r28a-2 r28a-3 r28a-2
powerpc.pkg

FH-MXP10G tuappl05a- cufhmappl01a- tuboot02a- oskernel02a- osappl02a- 23.0 (ESS)

r33b-43 r31a-36. r33a-1 r33a-1 r33a-1
powerpc.pkg

TPMRHEX-L/16G tuappl05a- cuhexlappl01a- tuboot02a- oskernel02a- osappl02a- 23.1

r36a-31 r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

FPU/1 tuappl05a- cufpu1ap- tuboot02a- oskernel02a- osappl02a- 26.0

r36a-31 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

OARAED21/HG tuappl05a- curaedap- tuboot02a- oskernel02a- osappl02a- 26.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

OA-RAED-20LG tuappl05a- curaedap- tuboot02a- oskernel02a- osappl02a- 30.0.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

OA20C/VG/II tuappl05a- curaedap- tuboot02a- oskernel02a- osappl02a- 27.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
OA2–20C/VG/II powerpc.pkg

OA21EC/VG tuappl05a- curaedap- tuboot02a- oskernel02a- osappl02a- R33.0.0

r36a-31 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
OA2-21EC/VG powerpc.pkg
1. TU5- Traffic board that has new CPU unit with SW that could be easily recognized by number 05 in the SW file name (tuappl05a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.10 Software versions for sixth generation of Traffic Units

Table 13 SW for different TU6 boards

Application CU-less
Board Type TU6 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

EMXP48/IIE tuappl06a- cuemxpeap- tuboot03a- oskernel03a- osappl02a- 22.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
EMXP62/IIE powerpc.pkg 21.0

EMXP120/IIE 21.0

EMXP220/IIE 23.0

EMXP240/IIE 25.0

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 39 (53) © Infinera 2021

 SOFTWARE VERSIONS

Table 13 SW for different TU6 boards (cont’d.)

1. TU6- Traffic board that has new CPU unit with SW that could be easily recognized by number 06 in the SW file name (tuappl06a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.11 Software versions for seventh generation of Traffic

Units
Table 14 SW for different TU7 boards

Application CU-less
Board Type TU7 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

EMXP/III tuappl07a- cuemxp3ap- tuboot03a- oskernel03a- osappl02a- 26.1

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

TM-EMXP-1U-DC - cuemxpuap- tuboot03a- oskernel03a- osappl02a- 29.0.0

pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg
1. TU7- Traffic board that has new CPU unit with SW that could be easily recognized by number 07 in the SW file name (tuappl07a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.12 Software versions for eighth generation of Traffic

Units
Table 15 SW for different TU8 boards

Application CU-less
Board Type TU8 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

PTIO-10G tuappl08a- cuptio1ap- tuboot02a- oskernel02a- osappl02a- 27.0

r36a-30 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg

PTIO-100G tuappl08a- cuptio1ap- tuboot02a- oskernel02a- osappl02a- 29.0.0

r36a-30 pl01a-r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg
1. TU8- Traffic board that has new CPU unit with SW that could be easily recognized by number 08 in the SW file name (tuappl08a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.13 Software versions for ninth generation of Traffic Units

Table 16 SW for different TU9 boards

Application CU-less
Board Type TU9 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

FHAU/1 tuappl09a- cufhau1ap- tuboot02a- oskernel02a- osappl02a- 28.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 40 (53) © Infinera 2021

 SOFTWARE VERSIONS

Table 16 SW for different TU9 boards (cont’d.)

TM-FHA1U-DC/1 - cufha1uap- tuboot02a- oskernel02a- osappl02a- 28.0

pl01a-r36a-31. r36a-2 r36a-1 r35a-6
powerpc.pkg

RFU-AC/1 - curfu1appl01a- tuboot02a- oskernel02a- osappl02a- 29.0.0

r36a-32. r36a-2 r36a-1 r35a-6
powerpc.pkg
1. TU9- Traffic board that has new CPU unit with SW that could be easily recognized by number 09 in the SW file name (tuappl09a-
xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.14 Software versions for tenth generation of Traffic Units

Table 17 SW for different TU10 boards

Application CU-less
Board Type TU10 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

FXP400GOTN tuappl10a- cuf400oap- tuboot04a- oskernel04a- osappl04a- 29.1.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-2
powerpc.pkg

EMXP440/III tuappl10a- cuem440ap- tuboot04a- oskernel04a- osappl04a- 30.0.0

r36a-30 pl01a-r36a-31. r36a-2 r36a-1 r35a-2
EMXP440-Q/III powerpc.pkg 32.1.0

MXP200GOTN tuappl10a- cum200oap- tuboot04a- oskernel04a- osappl04a- 31.0.0

r36a-30 pl01a-r36a-32. r36a-2 r36a-1 r35a-2
powerpc.pkg

TM-HDEA1600G/DC - cuhdeaap- tuboot04a- oskernel04a- osappl04a- 31.1.0

pl01a-r36a-31. r36a-2 r36a-1 r35a-2
powerpc.pkg

TM-EMXP-XH800/DC - cuem800ap- tuboot04a- oskernel04a- osappl04a- 34.1.0

pl01a-r36a-31. r36a-2 r36a-1 r35a-2
powerpc.pkg
1. TU10- Traffic board that has new CPU unit with SW that could be easily recognized by number 10 in the SW file name (tuap-
pl10a-xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

4.15 Software versions for eleventh generation of Traffic

Units
Table 18 SW for different TU11 boards

Application CU-less
Board Type TU11 1 Software in Application Boot Kernel File System Released
CU systems Software 2 in

FXP400G-E tuappl11a- cuf400eap- tuboot04a- oskernel04a- osappl04a- 36.0.0

r36a-33 pl01a-r36a-30. r36a-2 r36a-1 r35a-2
powerpc.pkg
1. TU11- Traffic board that has new CPU unit with SW that could be easily recognized by number 11 in the SW file name (tuap-
pl11a-xxxx.powerpc.pkg) except for CU-less application (01).
2. 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, see Release note for information about which boards that can be used in CU-less configurations.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 41 (53) © Infinera 2021

 FALL BACK

5 FALL BACK
If for any reason the upgrade failed and one wants to revert to the old SW, use ENM or CLI to
perform a downgrade of application, boot and kernel SW. The file system is backward compat-
ible and will work with an earlier version of the SW.

5.1 Fall back Considerations

5.1.1 Fall back from R36.0.1 and “Postpone Firmware Activation”
function

Boards with the function “Postpone Firmware Activation” set to ”disabled” during an upgrade
and with a traffic disturbance, will also have a traffic disturbance at fall back.

5.1.2 ENM with ‘Server’ set to ‘local’

Fall back procedure using ENM with ‘Server’ set to ‘local’ is currently not supported.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 42 (53) © Infinera 2021

 FALL BACK

5.2 Fall back procedure using ENM

Follow the steps below to revert to the previous node SW.

Step 1 Select “Software control” in left panel of ENM GUI.

Fig. 10 ENM GUI Maintenance

Step 2 In the ‘SW Status’ tab, press the button ’Select ENM spec’.

Step 3 In the dialog window, select ’Remote’ in the ‘Server’ field.

Step 4 Enter the IP address to your TFTP server in the ‘IP’ edit field.

Step 5 Fill in your server path e.g. ‘/enm001a-r32a-1.spec’ in the ‘Path’ edit field.

Step 6 Press the ‘Apply’ button.

Step 7 In the ‘SW Status’ tab at the field ‘Name’, click the top square box at the
left once or mark all boxes under the ‘Name’’ field next to the boards one
by one.

Step 8 In the ‘SW Status’ tab under the field ‘Action’, select ’Upgrade’ for all
boards.
Step 9 At the top of the page press the button ‘Apply’. In the dialog window, con-
firm the action by pressing the ‘Execute’ button. If the R32.0.1 application
software is still available on the board then it will be activated directly oth-
erwise the application, boot and kernel software will be downloaded and
installed.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 43 (53) © Infinera 2021

 FALL BACK

Step 10 When the upgrade procedure is done, the ‘SW Status’ field says ‘Soft-
ware update on reboot’.
If the ‘SW Status’ state is not correct, then repeat the upgrade from ‘Step
2’.
Step 11 In the field ‘Action’, select ’Reboot’ for all boards.
At the top of the page press the button ‘Apply’
In the dialog window, confirm the action by pressing the ‘Execute’ button.
Now all boards will be rebooted.

It will be impossible to log in to the node before it has started again, this could take 1-2
minutes.

Step 12 Login to the node again using ENM GUI. Login as user ‘oper’ or ‘root’.

Step 13 Select ‘Software control’ in left panel of ENM GUI.

Step 14 Check that ‘SW status’ field says: Ok

Check the active alarms, compare with the active alarms before the SW
upgrade by choosing ‘Alarms and events’ in left pane of the ENM GUI
and then ’Current’.

If there are alarms saying “Interwork failed” then probably the SW is not correctly installed. In
this case repeat ‘Step 1’ to ‘Step 14’.

Step 15 Go back to ‘Step 1’ and start with the next node in the network.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 44 (53) © Infinera 2021

 FALL BACK

5.3 Fall back procedure using CLI — Alternative 1

Follow the steps below to revert to the previous node SW.

Step 1 Login to the node as an oper user, using the Command Line Interface (CLI).

Step 2 Clean temporary files from CU by using following command:

swu clean downloaded

Step 3 Downgrade application, boot and kernel to original SW release, In this case
R32.0.1. Use the command:
swu upgrade all all 172.16.15.80/enm001a-r32a-1.spec
Expected printout:

1.3 appl tuappl01a-r36a-30 Needs activation of ... 15:31:19

1.3 tuappl01a-r32a-31 is expected 15:31:19
1.5 boot tuboot02a-r36a-2 Needs activation of ... 15:31:19
1.5 tuboot02a-r32a-2 is expected 15:31:19
1.5 kernel oskernel02a-r36a-1 Needs activation of ... 15:31:19
1.5 oskernel02a-r32a-2 is expected 15:31:19
1.5 appl tuappl02a-r36a-30 Needs activation of ... 15:31:19
1.5 tuappl02a-r32a-31 is expected 15:31:19
1.1 boot cuboot02a-r32b-2 Needs activation of ... 15:31:19
1.1 cuboot02a-r32a-3 is expected 15:31:19
1.1 kernel oskernel02a-r36a-1 Needs activation of ... 15:31:19
1.1 oskernel02a-r32a-2 is expected 15:31:19
1.1 appl cuappl03a-r36a-32 Needs activation of ... 15:31:19
1.1 cuappl03a-r32a-32 is expected 15:31:19
Downloading 172.16.15.80/cuappl01a-r31a-36.ppc_8xx.rpm....Download
complete. 7028622 bytes downloaded in 21.545 seconds
..
..
1.1 '/etc/lumentis/cuappl03a-r32a-32' is not empty - no files copied
(this version might have been active before?)
1.3 appl tuappl01a-r32a-31 Activate done 15:34:56
1.5 boot tuboot02a-r32a-2 Activate done 15:34:59
1.5 kernel oskernel02a-r32a-2 Activate done 15:35:24
1.5 appl tuappl02a-r32a-31 Activate done 15:35:26
1.1 boot cuboot02a-r32a-3 Activate done 15:35:28
1.1 kernel oskernel02a-r32a-2 Activate done 15:35:41
1.1 appl cuappl03a-r32a-32 Activate done 15:35:42
1.1 '/etc/lumentis/cuappl03a-r32a-32' is not empty - no files copied
(this version might have been active before?)

We are done
Wait until all software are activated for each board.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 45 (53) © Infinera 2021

 FALL BACK

Step 4 When the upgrade procedure is done. Make sure that the correct software is
installed and activated by using following commands at CLI:
swu show next
Expected printout:

Board Boot Kernel Application

1.1 cuboot02a-r32a-3 oskernel02a-r32a-2 cuappl03a-r32a-32
fs=r33a-1
1.3 tuboot01a-r14a-1 oskernel01a-r19a-2 tuappl01a-r32a-31
fs=r22a-1
1.5 tuboot02a-r32a-2 oskernel02a-r32a-2 tuappl02a-r32a-31
fs=r33a-1
We are done

Step 5 If the software is not correctly installed or activated for any board then repeat the
upgrade 'Step 2' and 'Step 3'.

Step 6 When the correctness of the activated application software is verified (compare to
enm001a-r32a-1.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,

this could take 1-2 minutes.

If there are alarms saying 'Interwork failed' then probably the SW is not
correctly installed. In this case repeat steps 'Step 1' to 'Step 6'.

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.

Step 7 Log in to the node and check the active alarms. Note that it will be impossible to log
in to the node before it has started again, this could take 1-2 minutes. Compare with
the active alarms before the SW upgrade. Use the command:
activeAlarms
If using OAR-450C a 'Configuration' error might appear after the 'fall back'. Then
make a 'swu reboot cu' and the alarm will disappear.

If you have done a 'fall back' and then upgrades to the same version of CU-application that
was used before the 'fall back', the backup that was used before the 'fall back' will be used
again. Please, contact Infinera support before doing the second upgrade.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 46 (53) © Infinera 2021

 FALL BACK

5.4 Fall back procedure using CLI — Alternative 2

A new fallback function was introduced in the release R34.0. This new function can only be
applied if the following criteria’s have been fulfilled:
• The upgrade started from release R34.0 or later.
• The upgrade was performed from DNA-M, ENM or CLI with the command structure like
’swu upgrade all all’.
Follow the steps below to revert to the previous node SW.

Step 1 Login to the node as an oper user, using the Command Line Interface (CLI).

Step 2 Check if a valid fallback check point exists. Use the command:
swu show fallback
If the reply printout is “No fallback check point exists” this fallback method can-
not be used. Please use other fallback methods.
Expected printout:

Fallback check point created Tue May 29 09:42:50 CEST 2020 at upgrade
from enm001a-r34a-1 to enm001a-r35a-0
Run 'swu -n fallback all all' to see effect of fallback.
We are done

Step 3 Check which software parts that will be affected by the fallback. Use the command:
swu -n fallback all all
Expected printout:

Fallback check point created Tue May 29 09:42:50 CEST 2020 at upgrade
from enm001a-r34a-1 to enm001a-r35a-0
1.3 appl tuappl01a-r36a-30 Needs activation of ... 10:29:24
1.3 tuappl01a-r34a-39 is expected 10:29:24
1.5 boot tuboot02a-r36a-2 Needs activation of ... 10:29:24
1.5 tuboot02a-r34a-1 is expected 10:29:24
1.5 kernel oskernel02a-r36a-1 Needs activation of ... 10:29:24
1.5 oskernel02a-r34a-1 is expected 10:29:24
1.5 appl tuappl02a-r36a-30 Needs activation of ... 10:29:24
1.5 tuappl02a-r34a-39 is expected 10:29:24
1.1 boot cuboot02a-r35a-1 Needs activation of ... 10:29:24
1.1 cuboot02a-r32b-2 is expected 10:29:24
1.1 kernel oskernel02a-r36a-1 Needs activation of ... 10:29:24
1.1 oskernel02a-r34a-1 is expected 10:29:24
1.1 appl cuappl03a-r36a-32 Needs activation of ... 10:29:24
1.1 cuappl03a-r34a-40 is expected 10:29:24
We are done
If all affected software to fallback are the same as what was upgraded, proceed to
the next step.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 47 (53) © Infinera 2021

 FALL BACK

Step 4 Perform the fallback to the previous installed software version. Use the command:
swu fallback all all
Expected printout:

Fallback check point created Tue May 29 09:42:50 CEST 2020 at upgrade
from enm001a-r34a-1 to enm001a-r35a-0
1.3 appl tuappl01a-r36a-30 Needs activation of ... 10:57:07
1.3 tuappl01a-r34a-39 is expected 10:57:07
1.5 boot tuboot02a-r36a-2 Needs activation of ... 10:57:07
1.5 tuboot02a-r34a-1 is expected 10:57:07
1.5 kernel oskernel02a-r36a-1 Needs activation of ... 10:57:07
1.5 oskernel02a-r34a-1 is expected 10:57:07
1.5 appl tuappl02a-r36a-30 Needs activation of ... 10:57:07
1.5 tuappl02a-r34a-39 is expected 10:57:07
1.1 boot cuboot02a-r35a-1 Needs activation of ... 10:57:08
1.1 cuboot02a-r32b-2 is expected 10:57:08
1.1 kernel oskernel02a-r36a-1 Needs activation of ... 10:57:08
1.1 oskernel02a-r34a-1 is expected 10:57:08
1.1 appl cuappl03a-r36a-32 Needs activation of ... 10:57:08
1.1 cuappl03a-r34a-40 is expected 10:57:08
1.1 '/etc/lumentis/cuappl03a-r34a-40' is not empty - no files copied
(this version might have been active before?)
1.3 appl tuappl01a-r34a-39 Activate done 10:57:27
1.5 boot tuboot02a-r34a-1 Activate done 10:57:31
1.5 kernel oskernel02a-r34a-1 Activate done 10:57:59
1.5 appl tuappl02a-r34a-39 Activate done 10:58:02
1.1 boot cuboot02a-r32b-2 Activate done 10:59:46
1.1 kernel oskernel02a-r34a-1 Activate done 11:00:01
1.1 appl cuappl03a-r34a-40 Activate done 11:00:03
1.1 '/etc/lumentis/cuappl03a-r34a-40' is not empty - no files copied
(this version might have been active before?)
We are done
Wait until all software are activated for each board.

Step 5 When the correctness of the activated application software is verified (compare to
the previous ‘.spec’ file) 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,

this could take 1-2 minutes.

If there are alarms saying 'Interwork failed' then probably the SW is not
correctly installed. In this case please contact Infinera support.

Step 6 Log in to the node and check the active alarms. Note that it will be impossible to log
in to the node before it has started again, this could take 1-2 minutes. Compare with
the active alarms before the SW upgrade. Use the command:
activeAlarms
NOTE: After this fallback procedure has been executed, it cannot be used again to
return back to the newer SW release. A new upgrade procedure will be needed.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 48 (53) © Infinera 2021

 APPENDIX

6 APPENDIX
6.1 FPGA revision history for boards supporting the
‘Postpone Firmware Activation’ function
Table 19 FPGA revision history for ‘Postpone Firmware Activation’ supported boards

Firmware revision history

Board FPGA ID Traffic Combination R19.0.5 R20.0.3 R21.0.1 R22.0 R23.1 R29.0.0 R32.1.x
R21.0.2 R23.0 R23.1.x R29.1.x R33.1.x
R23.0.1 R24.0 R30.0.x R34.0.x
R24.0.x R30.1.x R35.0.x
R25.0 R31.0.x R36.0.x
R25.0.x R32.0.x
R25.0.2
R25.0.3
R26.0
R26.0.x
R26.1
R27.0
R27.0.x
R28.0
R28.0.x
MS-MXP SWP300029 gbex3stm4Oc12x1st- P1P P1P R1A R1A R1C R1C R1C
m1Oc3x3
SWP300033 gbex1st- P3E P3E R1C R1C R1G R1G R1G
m16Oc48x1st-
m1Oc3x3
SWP300056 gbESyncEx3St- R1E R1E R1E R1E R1G R1G R1G
m4Oc12Stm1Oc3x1
SWP300085 gbex3stm4Oc12x1st- R1B R1B R1C R1C R1E R1E R1E
m1Oc3x3Basic
SWP300086 gbESyncEx3St- R1C R1C R1C R1C R1E R1E R1E
m4Oc12Stm1Oc3x1-
Basic
MS-MXP10G SWP300045 gbEx4Stm16Oc48x2 P1O P1O P1O P1O P1O P1O P1O
SWP300050 Stm16OC48x4 P1H P1H P1H P1H P1H P1H P1H
SWP300060 syncEx14GLinex2 R1B R1B R1B R1B R1B R1B R1C
SWP300063 syncEx10 P1F P1F P1F P1F P1F P1F P1F
MS-MXP40G SWP300075 client - R1C R1C R1J R1J R1J R1J
SWP300074 line - R1P R1P R1P R1P R1P R1P
MS-TP40G SWP300081 client - R1J R1J R1N R1N R1N R1N
SWP300082 line - R1S R1S R1U R1U R1U R1U
TPD10GBE SWP300004 traffic R2A R2A R2A R2A R2A R2A R2A
GBE9/MXP10GFEC SWP300022 traffic R1G R1G R1H R1H R1H R1H R1H
TPQ10GFEC SWP300070 traffic P2D P2D P2D P2D P2D P2D P2D
TPQ10GFEC/I SWP300070 traffic - - P2D P2D P2D P2D P2D
TPQMS SWP300031 traffic P1I P1I P1I R1A R1A R1A R1A

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 49 (53) © Infinera 2021

 APPENDIX

6.2 Boards at End of Software Support (ESS)

Software support have ended for the below boards. Last software release to use is listed.

To be able to upgrade to the latest software release the boards that are no longer supported
need to be deleted from the configuration before upgrading and a new backup saved. If the
node has several backup files, the unused backup files need to be deleted as well.

Table 20 Boards at End of Software Support (ESS)

Boards at End of Software Support (ESS)

Boards Last software
release to use
CUSFP R33.1
MDU16-CL/50G
FH-MXP10G
TP10GCLX
TP10GCLX/TC
GBE10-EMXP10 R32.1
GBE22-EMXP10
EMXP40G/II
VOA8CH
TPMR2500
TPLMR2500
TPMRLR
TPMR25CIR
TPLMR25CIR
TP10G R31.1
TP10G-LAN
MXP028
CU R31.0
CUOSC
MXP-MBH/1 R28.1
TP10GOTN/TC

6.2.1 End of Software Support (ESS) – R33.1

The boards TP10GCLX, TP10GCLX/TC, FH-MXP10G, MDU16–CL/50G and CUSFP have
been set to “End of Software Support”. The last software release to use is R33.1. This means
that upgrade to R36.0.1 are not allowed for these boards. If any of these boards are used in a
network node it will no longer be possible to upgrade the node to newer releases (e.g.
R36.0.1) until the boards are replaced or removed.

6.2.2 End of Software Support (ESS) – R32.1

The boards GBE10-EMXP10, GBE22-EMXP10, EMXP40G/II, VOA8CH, TPMR2500,
TPLMR2500, TPMRLR, TPMR25CIR and TPLMR25CIR have been set to “End of Software
Support”. The last software release to use is R32.1. This means that upgrade to R33.1.1 or
above are not allowed for these boards. If any of these boards are used in a network node it
will no longer be possible to upgrade the node to newer releases (e.g. R36.0.1) until the
boards are replaced or removed.

6.2.3 End of Software Support (ESS) – R31.1

The boards TP10G, TP10G-LAN and MXP028 have been set to “End of Software Support”.
The last software release to use is R31.1. This means that upgrade to R32.0 or above are not
allowed for these boards. The upgrade will normally be prohibited. However if you upgrade
from R31.0.0, R31.1.0 or R31.1.2 the upgrade will not be prohibited and that may result in

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 50 (53) © Infinera 2021

 APPENDIX

undefined behavior. Therefore it is important to remove those boards before upgrading a sys-
tem from R31.0.0, R31.1.0 or R31.1.2 to a higher release.

6.2.4 End of Software Support (ESS) – R31.0

The last software release to use for the CU and CUOSC boards are R31.0 since they have
been “frozen”. If any of these boards are used in a network node it will no longer be possible
to upgrade the node to newer releases (e.g. R36.0.1) until these cu boards are replaced by
newer cu boards (e.g CU-SFP/II or CU-SFP/III). The upgrade will fail in DNA-M when trying to
upgrade a CU or a CUOSC to release R31.1 or higher.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 51 (53) © Infinera 2021

 APPENDIX

6.3 Upgrade Analysis Tool

From release R28.0 for XTM and DNA-M a new tool named ‘Upgrade analysis tool’ is avail-
able. With the help of this tool it is possible to graphically predict the outcome of an upgrade
before performing the actual upgrade.
The ‘Upgrade analysis tool’ resides within the DNA-M web browser interface.
Before using the ‘Upgrade analysis tool’ it is important to read the deviations for the tool.
These deviations can be checked inside the tool by a click on the information icon in the upper
right corner and then a click on the ’deviations’ link.
It is also important to make sure to use the latest impact files for the release in DNA-M. The
impact files are found in your DNA-M server directory:
For Windows operating systems:
‘C:\Program Files\transmode\tnm\conf\upgrade_impact_resources\json\release’
For Linux operating systems:
‘/etc/tnm/upgrade_impact_resources/json/release’
The latest impact files can be downloaded from the Infinera customer web portal:
https://support.infinera.com
Remove all files in the ‘upgrade_impact_resources/json/release’ directory of the installed
DNA-M and replace them with the latest ones before using the tool.

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 52 (53) © Infinera 2021

 CONTACT INFORMATION

7 CONTACT INFORMATION
To get in contact with support personal at Infinera regarding upgrade, please use the contact
information below:

Table 21 Contact information

Name Web E-mail

TAC support.infinera.com techsupport@infinera.com

R36.0.1_XTMSeries_Upgrade_Instruction Rev A 53 (53) © Infinera 2021