Upgrade Path And Strategy

Marconi MHL 3000 Release 6.1 CP6

UPGRADE INSTRUCTIONS

2/153 72-CSA 113 62/61 Uen K

Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

Ericsson and the Ericsson logo

are trademarks of Telefonaktiebolaget LM Ericsson.

Acrobat(R) Reader copyright (C) 1987-1996 Adobe Systems Incorporated,

- All rights reserved.
Adobe and Acrobat are trademarks of Adobe Systems
Incorporated.

All trademarks and registered trademarks mentioned in a document of this

collection are the property of their respective holders.

Document History

Table 1 Issue Record

Issue Date System Release
2/153 72-CSA 113 62/61 Uen A 2013-01-28 6.1.0
2/153 72-CSA 113 62/61 Uen B 2013-03-12 6.1.0
2/153 72-CSA 113 62/61 Uen C 2013-06-17 6.1
2/153 72-CSA 113 62/61 Uen D 2013-10-30 6.1
2/153 72-CSA 113 62/61 Uen E 2013-12-13 6.1
2/153 72-CSA 113 62/61 Uen F 2014-09-11 6.1
2/153 72-CSA 113 62/61 Uen G 2014-12-15 6.1
2/153 72-CSA 113 62/61 Uen H 2015-06-03 6.1
2/153 72-CSA 113 62/61 Uen J 2016-01-18 6.1
2/153 72-CSA 113 62/61 Uen K 2016-07-04 6.1

Reason for Updating 2/153 72-CSA 113 62/61 Uen K

• Upgrade paths to R6.1 R9A

2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Reason for Updating 2/153 72-CSA 113 62/61 Uen J

• Upgrade paths to R6.1 R8A

Reason for Updating 2/153 72-CSA 113 62/61 Uen H

• Upgrade paths to R6.1 R7A

Reason for Updating 2/153 72-CSA 113 62/61 Uen G

• Upgrade paths to R6.1 R6A

Reason for Updating 2/153 72-CSA 113 62/61 Uen F

• Upgrade paths to R6.1 R5A

Reason for Updating 2/153 72-CSA 113 62/61 Uen E

• Upgrade paths to R6.1 R4A

Reason for Updating 2/153 72-CSA 113 62/61 Uen D

• Upgrade paths to R6.1 R3A

Reason for Updating 2/153 72-CSA 113 62/61 Uen C

• System Release rebranding

• Upgrade paths to R6.1 R2A

Reason for Updating 2/153 72-CSA 113 62/61 Uen B

• Upgrade paths to R6.1.0 R1B

Reason for Updating 2/153 72-CSA 113 62/61 Uen A

• Upgrade paths to R6.1.0 R1A

2/153 72-CSA 113 62/61 Uen K | 2016-07-04

2/153 72-CSA 113 62/61 Uen K | 2016-07-04
 Contents

Contents

1 Introduction 1
1.1 Purpose 1
1.2 Terminology 1

2 MHL 3000 Release History 3

3 Upgrade Paths Recommended 5

3.1 Upgrades To R6.1 5

4 Upgrade Strategy 7

5 Traffic Disruption 9

Glossary 11

Reference List 13

2/153 72-CSA 113 62/61 Uen K | 2016-07-04

Upgrade Path And Strategy

2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Introduction

1 Introduction

This is an Upgrade Path And Strategy document that details any key issues
when moving between Network Element (NE) software revisions for the
Marconi MHL 3000 family of products.

This document covers Marconi MHL 3000 Release R6.1 (including R6.1
updates).

Caution!
Different path strategy is foreseen according to the Network Element Controller
(NEC) type installed on the node.

1.1 Purpose
The following descriptions apply to all configurations of the MHL 3000 product.

The MHL 3000 product family supports backward compatibility that enables
MHL 3000 platforms (hardware) to be upgraded to the latest software release
revision. This compatibility is the key to the ability to migrate the MHL 3000.

1.2 Terminology
The following terminology is used within this document.

An Upgrade is defined as moving from one release revision of NE software to

another (for example, R6.0 to R6.1), where all software entities are upgraded,
along with the introduction of new hardware units with associated software.
‘Data Migration’ of the NE Controller configuration database occurs during an
upgrade and a different JCT and management version is normally required.

An Update is defined as a revision to an existing NE software release, where

only some of the individual software entities are updated. ‘Data Migration’
does not occur.

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 1

 Upgrade Path And Strategy

2 2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 MHL 3000 Release History

2 MHL 3000 Release History

For the Marconi MHL 3000 product family, the overall release history of the
Network Element (NE) since R4.2.2 is:

R4.2.2 > R4.3.0 > R4.3.1 > R4.3.2 > R5.0 > R5.1 > R5.1.1 > R5.2 > R6.0 > R6.1

The Marconi MHL 3000 product family can be managed from ServiceOn
Element Manager (SO EM) or the Java Craft Terminal (JCT).

The following sections detail the specific upgrade and update paths that are
supported.

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 3

 Upgrade Path And Strategy

4 2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Upgrade Paths Recommended

3 Upgrade Paths Recommended

This section identifies the recommended software revision at each release and
the supported upgrade paths.

In situations where the upgrade path is not possible, then a multiple step
upgrade is required.

In situations where the upgrade path is possible but has not been verified, a
single step upgrade may work successfully, but it cannot be guaranteed.

Note: An Upgrade from one software release to another assumes the same
hardware setup; any new hardware units introduced at the new release
would be configured after the upgrade.

All the Upgrades and Updates listed below were performed using the
ServiceOn Element Manager (details of the version used are listed).

Details of all possible upgrade steps are summarized at the end of this section.

When planning multiple step upgrades, it is recommended to update first to

the latest correction package of the current release then upgrade to the next
release.

The reasons for this are:

• Upgrades typically involve more special procedures to prevent traffic

disruption than do Updates.

• Updates often include fixes or improvements to the Upgrade process.

3.1 Upgrades To R6.1

Recommended version: R6.1 R9A (CP6).

Upgrades from the following MHL 3000 Releases have been verified:

• 6.1 R6D (EP5)

• 6.1 R6E (EP7)

• 6.1 R7A (CP4)

The Upgrades were verified with the following ServiceOn (SO) Build level:

• IPT NMS 16A R1D

• ServiceOn Element Manager 16A R1D

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 5

 Upgrade Path And Strategy

• EM-PMH 20.3.1.A-1

6 2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Upgrade Strategy

4 Upgrade Strategy

Full details relating to the actual implementation of an update or upgrade can

be found in the relevant upgrade Instruction documents (Refer to Reference
List on page 13). These documents provide details and workarounds for any
issues that may occur when performing an update or upgrade.

Some Release features have dependencies on system hardware (such as the

Enhanced Controller card LU11HA introduced in MHL R4.3.2). Details of such
dependencies can be found in Reference [9].

It is recommended that any updates and upgrades are performed from

ServiceOn EM remotely - refer to the relevant upgrade Instructions document.
Alternatively, it is possible to upgrade using the JCT.

Before performing any update or upgrade, suitable preliminary checks should

be undertaken.

Full details of the update and upgrade procedure can be found in the relevant
upgrade instructions document, where topics covered include:

• Upgrade Procedure (ServiceOn EM)

• ServiceOn EM Build Level Check

• Install Software on ServiceOn EM

• Configuration Back-up

• Download Software to Network Elements

• Activate Software in Network Elements

• Upgrade Procedure (JCT)

• Configuration Backup

• Software Download and Activation

• Replacing NE Controller Card (optional)

• Field Programmable Gate Array (FPGA) Upgrade

• Programming Compact Flash Devices

The duration of an NE update and upgrade will typically be less than 1 hour,
from the point of initiating the update or upgrade to the point of verification of the
software memory banks (excluding any set-up time that is required on the NE).

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 7

 Upgrade Path And Strategy

8 2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Traffic Disruption

5 Traffic Disruption

Traffic disruptions do not normally occur when an update or upgrade is

performed. However, some upgrades require special steps to be taken to
prevent a traffic disruption. Full details can be found in the relevant Upgrade
Instructions document (See Reference List on page 13).

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 9

 Upgrade Path And Strategy

10 2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Glossary

Glossary

EM
Element Manager

FPGA
Field Programmable Gate Array

JCT
Java Craft Terminal

LCT
Local Craft Terminal

NE
Network Element

NEC
Network Element Controller

SO
ServiceOn

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 11

 Upgrade Path And Strategy

12 2/153 72-CSA 113 62/61 Uen K | 2016-07-04

 Reference List

Reference List

[1] Marconi MHL 3000 Release R4.2.2 Upgrade Path And Strategy, 13/153
72-CSA 113 62/1 Uen

[2] Marconi MHL 3000 Release R4.3.1 Upgrade Path And Strategy, 6/153
72-CSA 113 62/3 Uen

[3] Marconi MHL 3000 Release R4.3.2 Upgrade Path And Strategy, 2/153
72-CSA 113 62/4 Uen

[4] Marconi MHL 3000 Release R5.0 Upgrade Path And Strategy, 2/153
72-CSA 113 62/5 Uen

[5] Marconi MHL 3000 Release R5.1 Upgrade Path And Strategy, 2/153
72-CSA 113 62/6 Uen

[6] Marconi MHL 3000 Release R5.1.1 Upgrade Path And Strategy, 2/153
72-CSA 113 62/511 Uen

[7] Marconi MHL 3000 Release R5.2 Upgrade Path And Strategy, 2/153
72-CSA 113 62/52 Uen

[8] Marconi MHL 3000 Release R6.0 Upgrade Path And Strategy, 2/153
72-CSA 113 62/60 Uen

[9] Marconi MHL 3000 Release R6.1 Network Impact Report, 10948-CSA
113 62/61 Uen

[10] Marconi MHL 3000 Release R6.1 Upgrade Instruction, 1/153 72-CSA
113 62/61 Uen

2/153 72-CSA 113 62/61 Uen K | 2016-07-04 13