METHOD OF PROCEDURE FOR LTE G2-OSS L17A Upgrade

METHOD OF PROCEDURE 1 (18)
Prepared (Subject resp) No.
EZZZSSS Jason Zhang S BUGS-16:031498 Uen

Approved (Document resp) Checked Date Rev Reference
2016-12-14 A
METHOD OF PROCEDURE FOR LTE G2 BASEBAND L17A

UPGRADE BY OSS/SHM
Contents
1 Purpose.................................................................................................................. 2
2 Document history....................................................................................................2
3 Details..................................................................................................................... 2
4 Reporting................................................................................................................ 3
4.1 Description of fields in the template........................................................................3
5 Disturbances during Upgrade.................................................................................3
5.1 Restrictions for the Upgrade...................................................................................3
5.2 Summary of Disturbances.......................................................................................3
6 Prerequisites........................................................................................................... 4
7 Implementation Plan...............................................................................................7
7.1 Requirement before FI............................................................................................7
7.2 DCGM & KGET FOR PRE-UPGRADE...................................................................8
7.3 FI for LTE G2 BASEBAND – Preparation, Software Installation and Conversion....9
8 Fallback Plan........................................................................................................15
8.1 Criteria.................................................................................................................. 15
8.2 Procedures........................................................................................................... 16
9 References........................................................................................................... 18

2016-12-14 A
1 Purpose
[MoP Purpose]
The purpose of this Method of Procedure (MOP) is to identify and communicate the key steps
and actions required as part of the LTE RAN G2 Baseband L17A Software
installation/upgrade procedure with SHM in OSS.
All parties must sign the MOP for the installation/upgrade to commence if satisfied that all
roles, responsibilities & actions are clearly understood and in place.
2 Document history
[Documents release list for each version]
Rev. Date Responsible Comments
PA1 2016/12/14 EZZZSSS First Draft
3 Details
[Project information, SW upgrade path, HW and any information you want to put in here]
Customer Name Customer: Country:

Site name
Products Baseband 521X
Project LTE G2 BASEBAND:
Description
L1**  L17A
Activities LTE G2 BASEBAND upgrade by SHM in OSS
Planned FI dates

2016-12-14 A
4 Reporting
[BENT report is requested for RAN and SIU/TCU can follow your own reporting method]
A failed upgrade is defined as follows:
 Rollback occurs during upgrade
BENT tool shall be used to register LTE G2 BASEBAND upgrade/updates, both successful
and failed.
4.1 Description of fields in the template
Contact person: Person to contact if more information is needed

Date: When the Upgrade/Update took place
SW-level, from: E.g. L16B.2
SW-level, to: E.g. L17A.1
Summary of Activity: Reason for failure and/or alarm
Follow Up/Open Issues: If a failure, always write a CSR and attach relevant log files and
traces. Write CSR number in this field.
Timeline of Activity: If a failure, give as detailed information as possible.
5 Disturbances during Upgrade
5.1 Restrictions for the Upgrade
During the LTE G2 BASEBAND upgrade no other maintenance activities are allowed in the
G2 BASEBAND or in the related IP network.
5.2 Summary of Disturbances
The table below shows a summary of the expected disturbances during the LTE G2
BASEBAND upgrade. The time of the disturbance vary depending on the size of the G2
BASEBAND configuration.

2016-12-14 A
Type of disturbance Impact on the system Time duration
LTE G2 BASEBAND Disturbances One Restart will take place per G2 2-10 minutes depending on
BASEBAND in the network. configuration
Subscriber disturbances Calls in progress will be disconnected at

the G2 BASEBAND Restart. 2-10 minutes depending on
configuration
Call setup is not possible during the LTE
G2 BASEBAND Restart.
Operator disturbances All operator O&M activities towards the ~5 hours

LTE G2 BASEBAND are prohibited
during the entire implementation.
6 Prerequisites
[Any prerequisites or limitation for the new SW or upgrade]
 Local procedures and CPI should be available.
 The LTE G2 BASEBAND upgrade must be performed by experienced personnel.
 The main upgrade activities will be performed with SHM in OSS_16.2.8. The minimum
required OSS need to check “Compatibility Matrix” for details
 Extract from ALEX OSS 16.2.8 library - SHM, Software Hardware Manager, User Guide
1/1553-CNA 403 2428 Uen L7. Below table shows the current maximum batch sizes for
some operation. Therefore, to provide some “head room” for all users it is best to limit
simultaneous G2 upgrades, backup etc. to approx. 100-150.
Subject Requirement Description
SHM Parallel Operations SHM supports 200 parallel operations.
Concurrent SHM sessions It shall be possible to support at least 10 concurrent client instances of the SHM application.
Number of concurrent SHM application shall be able to maintain at least 30 upgrade packages (with the assumption that
upgrade packages the average size of an upgrade package is 800MB).
Number of topology nodes SHM application handles at least 5000 topology nodes (including subnetworks and groups) in a
single topology (ONRM or site).
Export Hardware Inventory It shall be possible to export the 200 nodes H/W inventory from the SHM GUI application within 3
minutes.
Export Software Inventory It shall be possible to export the 200 nodes S/W inventory from the SHM GUI application within 3
minutes.
SW Upgrade duration The SW upgrade (prepare+activate together) duration shall not exceed 55 minutes on single node.
Backup time It shall be possible to create the backup of 200 nodes from the SHM GUI application within 5
minutes.

2016-12-14 A
 A Health Check must be performed before the SW upgrade to verify that all prerequisites for
a successful upgrade are met.
 Before upgrade to 16B GA (or later) SW, make sure that positionRef attribute in Support
System FieldReplaceableUnit MOs is configured. It refers to the cabinet where the actual
Baseband Unit FRU is located. If not configured it could have impact on power regulation
and battery charging in different cabinets. Thus all valid configurations are required to have
the “FieldReplaceableUnit:PositionRef” set, and cannot be left empty. If not set properly
alarm “Inconsistent Configuration FieldReplaceableUnit=5 (Attribute positionRef is empty, or
not valid)” will be issued. [2]
 LTE G2 BASEBAND available hard drive space and Backup amount requirements.
The disk full alarm must not be ignored (when disk usage is above 80%), it’s important
to remove unnecessary files from the disk before upgrade. [2]
Node Hard Disk Volume Backup amount
LTE G2
More than 20% Space Less than 15
BASEBAND
 All LTE G2 BASEBAND must have Key Files (KFs) installed to activate the license
controlled functionality and node capabilities. The Installation of the LKF should be done
before upgrading the node. The activation state of, and capacity configured for licenses
present in the LRAN product to be upgraded is retained after the upgrade.
New Licenses
Codes (HWAC) for baseband capacity is introduced in Baseband Radio Nodes. As the need
for additional resources grow over time, the HWAC can be upgraded to grant additional
capacity.
Each Radio Access Technology (RAT) in the Baseband unit uses a separate HWAC,
meaning that the baseband capacity can be adjusted individually per RAT. HWACs are
coupled to the hardware unit it's activated on, and cannot be moved to other units.
In LTE, the MO class ENodeBFunction reflects granted and maximum capacity in throughput
levels, in the following MO attributes:
 ulBbCapacityNet
 ulBbCapacityMaxLimit
 dlBbCapacityNet
 dlBbCapacityMaxLimit

2016-12-14 A
The alarm Resource Allocation Failure is raised when the node is unable to allocate
baseband hardware resources to a cell due to an insufficient HWAC level.
The following is the list of the new HWAC:
Feature Name License Key License MO Instance Name

(CXC) product
number (FAK)
Initial HWAC Baseband 5212 Utility CXC 401 1956 FAK 101 0059 InitialHwacBb5212UtiltiyMod
Module
Expansion HWAC Baseband 5212 CXC 401 1957 FAK 101 0060 ExpansionHwacBb5212UtilityMod
Utility Module
Initial HWAC Baseband 5216 Utility CXC 401 1961 FAK 101 0069 InitialHwacBb5216UtiltiyMod
Module
Expansion HWAC Baseband 5216 CXC 401 1962 FAK 101 0068 ExpansionHwacBb5216UtilityMod
Utility Module
Note: Incorrect setting of the system clocks of the nodes in which License Keys (LKs) are
installed may lead to failure to install the KFs. Failure to install the LKF prior to the upgrade
can result in deactivating of features or reduction of capacity after the upgrade. An alarm is
issued when the LKF is not installed. For more details, please refer the [1] “License check
procedure for LTE Upgrade”.
 A successful system upgrade requires that a valid network time is applied for LTE G2
BASEBAND.
 Make sure that a proper and working backup of the From-state SW (UP) is available
 Make sure that a proper and working Upgrade Package (UP) with its files (load modules) is
available
 External node combinations, the minimum required external node level need to check
“Compatibility Matrix” for details
The package has been verified together with EPC (Evolved Packet Core) system versions.
[2]
System Version
EPC EPG: 16B
SASN: 15B
SGSN-MME: 1.2
R63
SAPC: 16B

2016-12-14 A
7 Implementation Plan
[step by step upgrade procedure from pre FI check to post upgrade check]
7.1 Requirement before FI

Should be done before FI date
Act/Time Activity Responsible Comments
Make sure LTE G2 CU Network freeze.

1. BASEBAND frozen since the No parameter and HW change except LKF installation
1 dump will be offered on LTE G2 BASEBAND;
CU will send activity list and change list to Ericsson if
there is any parameter need to be updated.
- Make sure that a proper CU In Upgrade view, the user can import new SW
2. and working backup of the packages to SHM.
2 From-state SW (UP) is
available. Prerequisites:
- Make sure that a proper  The software upgrade package must be
and working Upgrade in .zip file format.
Package (UP) with its files
 The nmsinfo.xml present in software
(load modules) is available
- The Target SW are upgrade package should follow some
downloaded from SW standards.
gateway and uploaded to ◾Should have version attribute with
SHM value "1.0" in UpgradePackage element.
- The Target SW are
downloaded from SW ◾The attributes productDesignation,
gateway and uploaded to productNumber and productRevision are
SHM mandatory for ProductData element.
◾If Upgrade package supports Multi-
Standard nodes then ProductData
element should have technology attribute
with value LTE or WCDMA.
The procedure for Import SW package is as
follows:
1. Click Upgrade tab to open Upgrade view.
2. Click Import.
3. In the Import new software package
dialog box, click Browse to select the file
to be imported from directory.
4. Click Import to upload the file, or Close
to stop the upload process.

2016-12-14 A
No more than 2 "upgrade CU /Ericsson Moshell command :

3. Package" exists in FI Node ->pr UpgradePackage
3 Depends on the disk space
of LTE G2 BASEBAND. This will also be double checked before the installation.
No more than 15 backup CU /Ericsson Moshell command :
4. exist in FI Node ->cvls
4
Check all existing alarms, CU /Ericsson Moshell command
5. dump files and make sure -> alt
5 the reason for any crash is -> lll
known
Get one week ROP files for Ericsson Please provide ROP files for one week before upgrade.
6. FI LTE G2 BASEBAND
8
Check Hardware Ericsson Moshell Command:
7. requirements and limitations -> cabx
9
Create selection file Ericsson/ELS 1.Click Inventory tab. The topology side bar is
8. displayed.
2.Enter name of required ME in topology search text
box and click search icon or press enter. The ME(s)
and ME(s) count are displayed in topology tree.
3. Click Export visible below the topology search box.

4. An Export-Topology-Nodes dialog box displays the
default filename. Click Save. User can also edit file
name. Export file name should not contain any special
characters except ' _ ' and ' - '. If file name already
exists it will ask to override the existing file.
5. The file is stored in
/var/opt/ericsson/nms_shm/shm_file_store/topology_se
lection. Click Ok.
6. Click Load.
7.2 DCGM & KGET FOR PRE-UPGRADE
Health Check/Preparation Activity Responsible
1. ERICSSON
Make sure MO’s are loaded with the following commands, if not able to lt all resolve the issue or

2016-12-14 A
contact the next level of support:

lt all
Start logging parameters

l+
2. kget all ERICSSON
l-
The “dcgm” command in EMCLI will by default collect ESI without DSP PMDs to limit the file size. Full
3. ESI is collected with dcgm –k 1. In addition, command “lgf –d 1” can be used to collect DSP PMDs ERICSSON
separately.
7.3 FI for LTE G2 BASEBAND – Preparation, Software Installation and

Conversion
LTE G2 BASEBAND Preparation (daytime)
Activity time:
Act/Time Activity Responsible Comments
Before following the steps below, Ericsson Moshell Command:
1. ensure that the COMPLETE MOM is moshell -v use_complete_mom=1 <LTE G2 BASEBAND IP>
loaded. lt all
uv
Verify if the complete MOM is
loaded
Check the system constant before Ericsson Moshell Command:

2. upgrade, and confirm with customer - read : sysconread
if it needs set after upgrade - write : sysconwrite <name> <value> (eg. sysconwrite 100 1)
- reset : sysconreset <name> (eg. sysconreset 100)
Check if any Moshell Command:

3. UNLOCKED/DISABLED boards
exist st FieldReplaceableUnit
If they exist, then they should be
LOCKED prior to upgrade in the MW
PHASE (12:01) and then UNOCKED
after the upgrade
3 Check the current LTE G2 Ericsson Moshell command:
BASEBAND license -> get Lm=1,KeyFileManagement=1,KeyFileInformation=1
-> get . featurestate 1

-> get . servicestate 1
-> get . licensestate 1
4 Check existing alarms and analyze Ericsson Moshell command:

-> alt
5 Synchronization check Ericsson Moshell command
-> synccentral info tu
-> lget ,radioeq
Check backup status and make sure Ericsson Moshell command:

7. that the number of backups is less -> cvls
than 15

2016-12-14 A
Check the hard disk free space: at Ericsson Moshell command:

8. least 25% space left discspace -p (display disk space)
discspace -c (free up disk space)
Print PM scanner status and Ericsson Moshell command:
9. counters. -> pst
-> pgetsn
Check hardware requirements and Ericsson Moshell command:
10. limitations for each LTE G2 -> cabx
11 BASEBAND
Check that the LTE G2 BASEBAND Ericsson In OSS Common Explorer/SHM
11. is synchronized to OSS
22
Check that the FTP server contains Ericsson In SHM
12. software, if not request CU to
24 download SW from SW gateway
and upload to OSS SHM
LTE G2 BASEBAND License and SW Installation (daytime)
Activity time:
Act/Time Activity Responsib Comments
le
Inform users who are not involved in CU/
13. the upgrade that the SHM client Ericsson
must not be used during the entire
upgrade procedure
Check if the fingerprint of delivered Ericsson Moshell command:
14. LKF is the same as that of the LTE get Lm=1 fingerprint
G2 BASEBAND. alt
Check that no significant value
If any of the following licensing alarms appear in the alarm
decreases in new LKF comparing to
list, do not load the LKF and contact Ericsson support.
the old LKF  Emergency Unlock of Software Licensing
For LKF checking procedure, refer  License Key File Fault
to [1] “License check procedure for
LTE G2 BASEBAND node”.
If the fingerprints do not match, do
not import the LKF and contact
internal project support.
Imported license Key Files Ericsson  SHM, choose License and ’Import’
15.  Choose the corresponding key and execute import
by following the steps on the screen
Installing Licenses on the node Ericsson  SHM, choose License and ’Install’
16.  Follow the steps on the screen to finish LKF install
IL
 Need to check the validate result if there is any
different with old LKF

2016-12-14 A
Create a backup before upgrade Ericsson  SHM, choose Backup

17.  Enter the backup name “Before_17A_Installation”
and ’System/Systemdata’ then click start button
 Follow the steps on the screen to finish backup
1. SHM, select LTE G2 BASEBAND which will be

18. Installing the Upgrade Package Ericsson upgraded
LTE G2 BASEBAND: 2. Choose Upgrade
Normally 10 mins -20 mins for the 3. Select the G2 L17A GA UP:
installation CXP9024418_5-R15GK
4. Click ‘Prepare Upgrade’ and start button
Do not click ‘Prepare and Activate Upgrade’ before next

action!
Monitor the Software Installation Ericsson

19. and verify Installation results
If a problem occurs during above Ericsson

20. steps go to Fallback procedure
LTE G2 BASEBAND Upgrade Night time

FI Time:
Act/Time Activity Responsib Comments
le
21. 23:30 Team on site CU/
Ericsson

2016-12-14 A
22. 23:30 Quick health check for the LTE Ericsson Moshell Command:
G2 BASEBAND again to make -> st cell/ FieldReplaceableUnit
sure there is no new alarm and -> lll
disabled cell/sector/ru/RET, and -> cvls
-> cabx
also below checking list
-> alt
Abnormal Restarts
....
Alarm list
Cell availability
Disabled unlocked
FieldReplaceableUnit
Disk Space
Error
Hardware
Upgrade package
23. 23:40 Collect 24 hours KPI statistics Ericsson Moshell Command:
before upgrade ->pmr -m 24 -r 3
24. 00:02 Check new Licensing works well. Ericsson Moshell command:
-> get Lm=1,KeyFileManagement=1,KeyFileInformation=1
-> invl
The following capacity licenses are mandatory and must be

installed prior to system upgrade:
Connected users CXC4010608 FAJ2210992
Down Link Capacity CXC4010623 FAJ1210544
Up Link Capacity CXC4010624 FAJ1210545
Output power up to 40W CXC4010625 FAJ1210546
Channel BandWith 5MHz CXC4010627 FAJ1210548
LTE HW Connected Users CXC4010864 FAJ1210762
Downlink PRB Capacity CXC4011039 FAJ1210927
Uplink PRB Capacity CXC4011040 FAJ1210928
Output Power 60W to 80W CXC4011161 FAK1010020
LTE Output Power 120W to 140W CXC4011620 FAK1010041
Capacity 5MHz Sector Carriers CXC4011622 FAJ2213071


2016-12-14 A
25. 00:35 1- Analysis KPI for previous 2 Ericsson 1-. Moshell command
hour > pmr -m 2
2- disable all unnecessary trace 2-. Moshell command
(enable and saved) on all board. > lh all fte s
3- turn off target monitor > lh all te default *
4- Check UE registration > lh all te default -restart
> lh all te save *
> lh all fte s
3-. Moshell command
>mon-
>mon?
4-. Moshell command
>ue print -admitted
26. 01:15 Software Upgrade – reboot Ericsson In SHM: Same procedure as Installation but
node upgrade only select ‘Activate Upgrade’ (Verify, Activate and
Normally 10 mins for the upgrade Confirm) and then start
- ~ 4 minutes later, all O&M will be lost due to JVM restart.

the O&M connection will be recovered 90 seconds later.
- Another about 3 minute later, Node will be restarted and

all O&M lost during the rebootagain. The O&M will be
recovered about 3-5 minutes depends on the side of node
configurationlater.
27. 02:15 Check that the “Final_backup” Ericsson Moshell Commands:

has been created -> cvls
28. 02:50 Basic health check by moshell Ericsson Moshell Command:

command after upgrade. -> alt
-> st cell/FieldReplaceableUnit
-> ue print -admitted
-> cvls

2016-12-14 A
29. 03:20 Confirm the preliminary drive CU/ If some problems occurred, collect dcgm before rollback
testing result is OK. Ericsson for further analysis
If any serious alarm or

disturbances exist in the LTE G2
BASEBAND NODE that indicates
that the upgrade has failed, go to
Fallback 2
30. 03:45 Check PM raw file can be parsed CU/ Double check the scanners status
in OSS-RC. Ericsson moshell command:
Check PM file works well. -> pst
Check KPI status.
Define new PM profile by CU if
needed.
31. 04:05 Check License works well Ericsson Moshell command:
-> get Lm=1,KeyFileManagement=1,KeyFileInformation=1
-> invl
The following capacity licenses are mandatory and must be

installed prior to system upgrade:
Connected users CXC4010608 FAJ2210992
Down Link Capacity CXC4010623 FAJ1210544
Up Link Capacity CXC4010624 FAJ1210545
LTE HW Connected Users CXC4010864 FAJ1210762
Downlink PRB Capacity CXC4011039 FAJ1210927
Uplink PRB Capacity CXC4011040 FAJ1210928
5+5 MHz Sector Carrier CXC4011622 FAJ2213071

32. 04:10 Check CV status Ericsson Moshell command:
-> cvls
33. 04:55 Check if LTE G2 BASEBAND Ericsson Change the parameter according to customer requirement.
parameter set to previous value
and new feature is deactivated.
34. 05:00 Get upgrade log and cell status Ericsson Moshell command:
-> lgur -m 2

2016-12-14 A
35. 05:20 Collect LTE G2 BASEBAND dcgk Ericsson Moshell Command:

data and have a comparison with ->dcgk
the one before upgrade if
needed.
36. 05:30 Compare LTE G2 BASEBAND Ericsson Diff the dcgk in offline mode to generate scripts
NODE parameter to previous ->ldiff before_dcgk after_dcgk
value and active related features.
If needed.
37. 05:30 Create a backup Ericsson In SHM, backup Name: After_L17A_Upgrade
38. 05:45- KPI monitoring Ericsson KPI monitoring until the end of MW
06:00
39. 06:00 Whole driving testing and CU/
functionality testing finished. Ericsson
40. 06:00 Send BENT report about the Ericsson
upgrade activity
After above steps the upgrade is considered completed
8 Fallback Plan
[Roll back procedure]
8.1 Criteria
The agreed FI fallback criteria decision is:
1. The upgrading to SW level encounters problems and cannot be

completed within the maintenance window.
2. Basic function (CSFB, PS call, HSDPA/EUL call, handover) not working,

which cannot be fixed by trouble shooting/emergency handling within
maintenance window.
3. OSS lost sync with LTE G2 BASEBAND after upgrading, which can’t be
fixed by troubleshooting/emergency-handling within maintenance window.
IMPORTANT COMMENTS:
1. Multiple upgrading attempts are allowed, and it will be regarded as a

successful FI if the upgrading succeeds within the maintenance window.
For example, 1st upgrading was rolled back to Rollback backup, and we
find the reason/remedy promptly, so we will do 2nd upgrade attempts if
the time can be controlled within maintenance window.
2. When basic function has a problem, or node lost sync with OSS, the first
action is troubleshooting, instead of fallback directly.

2016-12-14 A
8.2 Procedures
If the LTE G2 BASEBAND NODE Upgrade fails, a set of fallback procedures are described in
this chapter.
Caution!
The Fallback has to be performed in cooperation with Ericsson Local Support and with customer
Following fallback procedure exist:

Fallback procedure Fallback situation
Fallback 1 This fallback is applicable if a fault occurs during, or
after, the LTE G2 BASEBAND Software Installation,
but before the LTE G2 BASEBAND Software Upgrade
has been started.
Fallback 2 This fallback is applicable if a fault occurs during, or
after, the LTE G2 BASEBAND Software Upgrade.
8.2.1 Fallback 1
Some possible reasons for a failed installation:
 Not enough disk space in the LTE G2 BASEBAND
 The LTE G2 BASEBAND restarted during installation
 FTP server access problems
 Wrong path name to the upgrade package XML-file
Reinstall the Upgrade Software

1. Reinstall the Upgrade Package using the full installation method and
continue with the rest of the upgrade procedure
If installation fails again, check Health Check result file for disc space, if
disc space is too low continue with next step, otherwise contact Ericsson
local support.
Remove an installed package

2. Remove the installed software with SHM. In the SHM window, click on
Inventory tab and select the Upgrade Package you want to delete. Click
Delete Upgrade Packages.

2016-12-14 A
In the SHM window, click on Jobs to verify the process completed

successfully.
3. Run the Health Check.
Fallback 1 completed!
Upgrade should be re-performed after this.
8.2.2 Fallback 2
1. If the status in SHM is not Awaiting confirm, login LTE G2 BASEBAND
and check which CV is currently loaded. If the CV is SU_rev_date_time, the
upgrade is almost finished. Try to confirm the upgrade manually.
Moshell command: acc <upgrade package> confirmUpgrade
If the backup is confirmed at this step and a Final backup is created, then
perform the applicable steps after Verify the Upgrade status and create a
new Final backup if any configuration changes are done.
For a complete fallback restart on the backup that was startable before the
upgrade. Remove the failed upgrade package, see Fallback 1. It is then
possible to retry the whole procedure, starting with SW installation, using
SHM.

2016-12-14 A
*In COM node, backup is handled by BrmBackup MO

- cvset not supported and replaced by cvre, cvre will reboot the node with
Cold restart rank
2. If upgrade failed due to other issue, for example, cell disabled after
upgrade, KPI drop a lot after upgrade, take whole DCGM and restore in the
Backup before upgrade.
Note: Fall back decision will be decided by Ericsson and CUSTOMER
Some possible reasons for a failed upgrade:
 Not enough disk space in the LTE G2 BASEBAND
 Exhaustion of heap or pool memory. Note that every load module on

disk also consumes database heap memory, which is another reason
to keep as few upgrade packages as possible on disk.
 Checksum failure. Before the upgrade begins, all checksums are

verified. Because a delta installation downloads only updated load
modules (new revisions), it is possible (but very unusual) to get a
checksum failure at the upgrade. A complete install should correct the
problem.
 HW/SW issue
9 References
[Any reference you want to put into here]
[1] License check procedure for LTE Upgrade , 1/000 23- FCP 121 4455 Uen
[2] Baseband Radio Node 17A GA Release Note, BUGS-16:031498 Uen
7/1543- CRX 102 01/1 Uen A

METHOD OF PROCEDURE FOR LTE G2-OSS L17A Upgrade

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

METHOD OF PROCEDURE FOR LTE G2-OSS L17A Upgrade

Caricato da

Copyright:

Formati disponibili

METHOD OF PROCEDURE 1 (18)

Prepared (Subject resp) No.

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

METHOD OF PROCEDURE FOR LTE G2 BASEBAND L17A

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

Rev. Date Responsible Comments

PA1 2016/12/14 EZZZSSS First Draft

Customer Name Customer: Country:

Activities LTE G2 BASEBAND upgrade by SHM in OSS

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

A failed upgrade is defined as follows:

 Rollback occurs during upgrade

4.1 Description of fields in the template

Contact person: Person to contact if more information is needed

5 Disturbances during Upgrade

5.1 Restrictions for the Upgrade

5.2 Summary of Disturbances

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

Type of disturbance Impact on the system Time duration

Subscriber disturbances Calls in progress will be disconnected at

Operator disturbances All operator O&M activities towards the ~5 hours

 Local procedures and CPI should be available.

 The LTE G2 BASEBAND upgrade must be performed by experienced personnel.

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

The following is the list of the new HWAC:

Feature Name License Key License MO Instance Name

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

7.1 Requirement before FI

Act/Time Activity Responsible Comments

Make sure LTE G2 CU Network freeze.

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

No more than 2 "upgrade CU /Ericsson Moshell command :

3. Click Export visible below the topology search box.

7.2 DCGM & KGET FOR PRE-UPGRADE

Health Check/Preparation Activity Responsible

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

contact the next level of support:

Start logging parameters

7.3 FI for LTE G2 BASEBAND – Preparation, Software Installation and

Check the system constant before Ericsson Moshell Command:

Check if any Moshell Command:

-> get . featurestate 1

4 Check existing alarms and analyze Ericsson Moshell command:

Check backup status and make sure Ericsson Moshell command:

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

Check the hard disk free space: at Ericsson Moshell command:

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

Create a backup before upgrade Ericsson  SHM, choose Backup

1. SHM, select LTE G2 BASEBAND which will be

Do not click ‘Prepare and Activate Upgrade’ before next

Monitor the Software Installation Ericsson

If a problem occurs during above Ericsson

LTE G2 BASEBAND Upgrade Night time

EZZZSSS Jason Zhang S BUGS-16:031498 Uen

The following capacity licenses are mandatory and must be

Connected users CXC4010608 FAJ2210992

Down Link Capacity CXC4010623 FAJ1210544

Up Link Capacity CXC4010624 FAJ1210545

Output power up to 40W CXC4010625 FAJ1210546

Output power up to 60W CXC4010626 FAJ1210547

Channel BandWith 5MHz CXC4010627 FAJ1210548

Channel BandWith 10MHz CXC4010718 FAJ1210668