H3I CR MOP Format V2.

H3I SPECIFIC MOP

NOK_RAN_3G WCDMA
SW19 UPGRADE

PREPARED BY ANDRI HUMALA DATE 07 FEB 2020

REVIEWED BY GANI KUSTAMAN DATE 07 FEB 2020

APPROVED BY EKO RUSLANTO DATE 07 FEB 2020

This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, storing,
adapting or translating, any or all of this material requires the prior written consent of Nokia.
This material also contains confidential information, which may not be disclosed to others
without the prior written consent of Nokia.
1. Description of Change 3G WCDMA SW19 Upgrade

1.1. Purposes

The main purpose of this document is to describe the actions needed for
installing and or upgrading this Release Delivery into the customer's network
on 3G WBTS Level.

1.2. Overview and Pre Requisites

This document can be used in software installation for WBTS on 3G

Networks. No specific requirement for WBTS HW.

2. Preparation for Change

2.1. Change Period

Proposed change period is Thursday,26th Mar 2020 00.00 – 04.00 a.m.

2.2. Composition of Change Team and Responsibility of Team Members

Name Responsibility Contact No.

Eko Ruslanto Care Program Manager +628990000555
Gani Kustaman Leader +62895322274609
Muslikh Anshari RAN Engineer +6289684000772
Andri Humala RAN Engineer +6281553000628

2.3. Checking of Running Equipment

Potential
No Risk Description PIC
Impact
MS & RAN
1 Configuration backup Medium
Engineer
Collecting log for pre- execution , during MS & RAN
2 Low
execution, and after execution Engineer

2.4. Check Before Activity

1. Collect RNC Logcol and WBTS Alarm History

2. Collect and save both active and passive SW versions info from network.
3. Save BTS Configuration

2.5. Check After Activity

1. Collect WBTS Log fast as possible.

2. Alarm history 2 weeks backwards to be collected.
3. Change Steps

The included screenshots in the following chapters are representations and should
only be considered as examples. The current release of the WBTS software might
slightly differ from the screenshots depicted.

3.1. Download Required SW to NetAct

3.2. Transfer Site SW from NetAct to Target Site (NEs)
3.3. New SW Activation
3.4. Site Restart (Automatically)

4. Observation

Observation Observation Expected

No Observation Methods Owner
Items Time Result
SW Upgrade
Check Site Go to Netact and run CLI script 02.00 -
1 OSS Team applied as
Config LST CELL 04.00
expected
Check Alarms on Go to Netact and open Alarm No new alarms
02.00 -
2 all Monitoring Browser; compare OSS Team occurs after
04.00
BSC/RNC/eNB before and after status. activity
Go to Netact and retrieved KPI
04.00 - No degradation
3 KPI Monitoring report from Reporting Suite; NPM Team
13.00 after activity.
compare before and after status.

5. Rollback
Step of Rollback: Activated the old SW which saved in 3G WBTS, then Site restart
will be performed.
 H3I CR MOP Format V2.0

H3I SPECIFIC MOP

NOK_RAN_2G BTS SW19

UPGRADE

PREPARED BY ANDRI HUMALA DATE 07 FEB 2020

REVIEWED BY GANI KUSTAMAN DATE 07 FEB 2020

APPROVED BY EKO RUSLANTO DATE 07 FEB 2020

This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, storing,
adapting or translating, any or all of this material requires the prior written consent of Nokia.
This material also contains confidential information, which may not be disclosed to others
without the prior written consent of Nokia.
1. Description of Change 2G BTS SW19 Upgrade

1.1. Purposes

The main purpose of this document is to describe the actions needed for
installing and or upgrading this Release Delivery into the customer's network
on 2G BTS Level.

1.2. Overview and Pre Requisites

This document can be used in software installation for BTS on 2G Networks.

No specific requirement for BTS HW.

2. Preparation for Change

2.1. Change Period

Proposed change period is Thursday,26th Mar 2020 00.00 – 04.00 a.m.

2.2. Composition of Change Team and Responsibility of Team Members

Name Responsibility Contact No.

Eko Ruslanto Care Program Manager +628990000555
Gani Kustaman Leader +62895322274609
Muslikh Anshari RAN Engineer +6289684000772
Andri Humala RAN Engineer +6281553000628

2.3. Checking of Running Equipment

Potential
No Risk Description PIC
Impact
MS & RAN
1 Configuration backup Medium
Engineer
Collecting log for pre- execution , during MS & RAN
2 Low
execution, and after execution Engineer

2.4. Check Before Activity

1. Collect BSC Logcol and BTS Alarm History

2. Collect and save both active and passive SW versions info from network.
3. Save BTS Configuration

2.5. Check After Activity

1. Collect BTS Log fast as possible.

2. Alarm history 2 weeks backwards to be collected.
3. Change Steps

The included screenshots in the following chapters are representations and should
only be considered as examples. The current release of the BTS software might
slightly differ from the screenshots depicted.

3.1. Download Required SW to NetAct

3.2. Transfer Site SW from NetAct to Target Site (NEs)
3.3. New SW Activation
3.4. Site Restart (Automatically)

4. Observation

Observation Observation Expected

No Observation Methods Owner
Items Time Result
SW Upgrade
Check Site Go to Netact and run CLI script 02.00 -
1 OSS Team applied as
Config LST CELL 04.00
expected
Check Alarms on Go to Netact and open Alarm No new alarms
02.00 -
2 all Monitoring Browser; compare OSS Team occurs after
04.00
BSC/RNC/eNB before and after status. activity
Go to Netact and retrieved KPI
04.00 - No degradation
3 KPI Monitoring report from Reporting Suite; NPM Team
13.00 after activity.
compare before and after status.

5. Rollback
Step of Rollback: Activated the old SW which saved in 2G BTS, then Site restart will
be performed.
 H3I CR MOP Format V2.0

H3I SPECIFIC MOP

NOK_RAN_4G ENODEB
SW19 UPGRADE

PREPARED BY ANDRI HUMALA DATE 07 FEB 2020

REVIEWED BY GANI KUSTAMAN DATE 07 FEB 2020

APPROVED BY EKO RUSLANTO DATE 07 FEB 2020

This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, storing,
adapting or translating, any or all of this material requires the prior written consent of Nokia.
This material also contains confidential information, which may not be disclosed to others
without the prior written consent of Nokia.
1. Description of Change 4G ENODEB SW19 Upgrade

1.1. Purposes

The main purpose of this document is to describe the actions needed for
installing and or upgrading this Release Delivery into the customer's network
on 4G ENODEB Level.

1.2. Overview and Pre Requisites

This document can be used in software installation for BTS on 4G Networks.

No specific requirement for ENODEB HW.

2. Preparation for Change

2.1. Change Period

Proposed change period is Thursday,26th Mar 2020 00.00 – 04.00 a.m.

2.2. Composition of Change Team and Responsibility of Team Members

Name Responsibility Contact No.

Eko Ruslanto Care Program Manager +628990000555
Gani Kustaman Leader +62895322274609
Muslikh Anshari RAN Engineer +6289684000772
Andri Humala RAN Engineer +6281553000628

2.3. Checking of Running Equipment

Potential
No Risk Description PIC
Impact
MS & RAN
1 Configuration backup Medium
Engineer
Collecting log for pre- execution , during MS & RAN
2 Low
execution, and after execution Engineer

2.4. Check Before Activity

1. Collect BTSMED/IOMS TS Log and ENODEB Alarm History

2. Collect and save both active and passive SW versions info from network.
3. Save ENODEB Configuration

2.5. Check After Activity

1. Collect ENODEB Log fast as possible.

2. Alarm history 2 weeks backwards to be collected.
3. Change Steps

The included screenshots in the following chapters are representations and should
only be considered as examples. The current release of the ENODEB software might
slightly differ from the screenshots depicted.

3.1. Download Required SW to NetAct

3.2. Transfer Site SW from NetAct to Target Site (NEs)
3.3. New SW Activation
3.4. Site Restart (Automatically)

4. Observation
Observation Observation Expected
No Observation Methods Owner
Items Time Result
SW Upgrade
Check Site Go to Netact and run CLI script 02.00 -
1 OSS Team applied as
Config LST CELL 04.00
expected
Check Alarms on Go to Netact and open Alarm No new alarms
02.00 -
2 all Monitoring Browser; compare OSS Team occurs after
04.00
BSC/RNC/eNB before and after status. activity
Go to Netact and retrieved KPI
04.00 - No degradation
3 KPI Monitoring report from Reporting Suite; NPM Team
13.00 after activity.
compare before and after status.

5. Rollback
Step of Rollback: Activated the old SW which saved in 4G ENODEB, then Site restart
will be performed.