Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 1 (32)

ARTC 4G/5G Remote Integration MOP

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Contents

1 Introduction.................................................................................................................................
1.1 Scope........................................................................................................................................
2 Revision Information.................................................................................................................
3 Pre-requisites...............................................................................................................................
4 Solution Architecture.................................................................................................................
4.1.1 Solution 76 (2217 B28 L700 radio + 2212 B5 W850/N850 mixedmode
radio + DUW30 + BB6630)...............................................................................................
4.1.2 Solution 70 (4480 B28 + B26 L700 + N850/W850 Up The Pole +
DUW30 + BB6630)..............................................................................................................
4.1.3 Solution 71 (4480 B28 + B26 L700 + N850/W850 Down The Pole +
TMA’s+ DUW30 + BB6630)..............................................................................................
5 Software........................................................................................................................................
6 Preparation..................................................................................................................................
6.1 Use PCI tool to generate Script........................................................................................
6.2 Import the LKF into ENM...................................................................................................
7 Remote Procedure......................................................................................................................
7.1 Perform Remote Integration of the Baseband...........................................................
7.1.1 CMART Validation................................................................................................................
7.2 Zero Touch Integration......................................................................................................
7.2.1 Import the LKF in ENM....................................................................................................
7.2.2 Import the End Entity (EE) in ENM (ZT automates this process)......................
7.2.3 Update the hardwareSerialNumber in the NodeInfo.xml in the
Auto_Provisioning_Standard zip file...........................................................................
7.2.4 Drag and Drop the Updated Auto_Provisioning_Standard zip file into
workspace area..................................................................................................................
7.2.5 Order the node integration using the ap order command....................................
7.2.6 Use the provided ap status command to ensure the order = completed.........
7.2.7 Bind the node (Late Binding).........................................................................................
7.2.8 Unlock the Router Port.....................................................................................................
7.2.9 Switch on the node to start integration......................................................................
7.2.10 Confirm node integration................................................................................................
7.3 Remote Integration Script..............................................................................................
7.3.1 Create CV backup..............................................................................................................
7.3.2 Continue loading the PCI Configuration_Files.........................................................
7.3.3 Configure the Qos..............................................................................................................
7.3.4 Execute NSD alignment script.......................................................................................
7.3.5 Set SyncRiPortCandidate................................................................................................
7.3.6 Lock Unused/Disabled Riport & Unlock the Used/Enabled Riport....................
7.3.7 Set nbiot cellrange.............................................................................................................
7.3.8 Create CV Backup..............................................................................................................
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 2 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.3.9 Restart EnodeB..................................................................................................................

7.3.10 Check Node Status............................................................................................................
7.3.11 Load LKF...............................................................................................................................
7.3.12 Execute the Post Upgrade Script on the Baseband................................................
7.3.13 Configure TimeSettings...................................................................................................
7.3.14 [Solution 70 & 71] Configure VSWR Supervision for each band.......................
7.3.15 Run G2_NTP_Configuration.mos.................................................................................
7.3.16 Set DNCTYPE for MME’s..................................................................................................
7.3.17 Block IDL links....................................................................................................................
7.3.18 Create CV Backup..............................................................................................................
7.3.19 Check Node Sync in ENM................................................................................................
7.4 Continue Remote Integration........................................................................................
7.4.1 Unlock the radios...............................................................................................................
7.4.2 Check IMF 6025 is Correctly Defined & Enabled.....................................................
7.4.3 [Solution 71] Check TMA KA-1033 is Correctly Defined & Enabled.................
7.4.4 Check RET is Correctly Defined & Enabled................................................................
7.4.5 Check PTP configuration.................................................................................................
7.4.6 Check CPRI Rx level..........................................................................................................
7.4.7 Check ASM...........................................................................................................................
7.4.8 Check Interference level per branch on LTE cells....................................................
7.4.9 Check SNMP3 configuration..........................................................................................
7.4.10 Check PM counters activation & PM files received.................................................
7.4.11 Obtain post-integration tilt status & save logs........................................................
7.5 Perform Post PA.................................................................................................................
7.6 Create Final CV...................................................................................................................
7.6.1 Unlock L700 & NR850 cells/sectors to see cells are enabled..............................
7.6.2 Lock NR850 cells due to no high band LTE anchor................................................
7.6.3 save a CV..............................................................................................................................
7.6.4 Check System Constant...................................................................................................
7.7 Define External Alarms....................................................................................................
7.8 Call Test................................................................................................................................
7.8.1 Lock W850 to allow successful Inter-site L700 Handover..................................
7.9 Post-Check...........................................................................................................................
7.10 Go through Configuration Check List..........................................................................
7.11 Create CV backup to ENM...............................................................................................
7.12 Raise CT or Open Issue....................................................................................................
7.13 Send Partial RFU................................................................................................................
7.14 DRAKE Update...................................................................................................................
7.15 24 Hours Alarm Check......................................................................................................
7.16 Send Full RFU email..........................................................................................................
7.17 Whisper Update.................................................................................................................
7.17.1 Site Handler Update..........................................................................................................
8 Reference:...................................................................................................................................
8.1 Emergency Call Handling................................................................................................
8.2 Manual Restore of BB6630 or BB5216......................................................................
8.3 Monitor the progress of ZT.............................................................................................
8.4 Troubleshooting.................................................................................................................
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 3 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

8.4.1 ZT............................................................................................................................................
8.4.2 BB has ptp sync issue.......................................................................................................

1 Introduction
This document describes the steps involved in the remote integration of ARTC 4G/5G
Baseband node.

1.1 Scope

This MOP will cover the remote integration of ARTC sites where a 4G/5G Baseband (BB)
will be scratch installed using Zero Touch (ZT).

2 Revision Information
Revision Comment Author Date
PA1 First Draft Steven Weng 20/03/23
PA2 NSD script updated to PA2 Steven Weng 29/03/23
PA3 Add 7.37 to set cellrange to nbiot Steven Weng 05/04/23
PA4 Add 7.3.4.1 to 7.3.4.3 for NSD alignment Steven Weng 06/04/23
PA5 Add 8.3 to monitor ZT progress using EM Steven Weng 12/04/23
Add 7.3.4.4 & 7.3.4.5 for 5G_SA_NSD and 5Gqi loading
PA6 Steven Weng 28/04/23
Add 8.4 Troubleshooting
Update link in the 7.3.4.4
5G_SA_NSDv3_ENIC_PA1.mos,
PA7 Steven Weng 09/05/23
Update 7.3.16 to set dcntype before post PA
Update 7.3.4.1 to ARTC_delta_alignment_PA3.mos
Update 7.3.4.3 to run
4G_5G_Delta_S1S3_NSD_PA2.mos
Add 7.4.8 mfi command to measure interference
PA8 Steven Weng 15/05/23
Add 7.8.1 to lock W850 while doing L700 intersite HO
tests. Also mention FE should band lock UE to L700 and
select 4G only.
Update 7.3.4.3 to 4G_5G_Delta_S1S3S4_NSD_PA3.mos
PA9 Steven Weng 17/05/23
This can be used for all solution types.
Update 7.4.4 to check iuantsectorid, installersid and
PA10 Steven Weng 24/5/23
basestationid in RET

3 Pre-requisites
 Onsite and Remote Integration of DRAN Router 6471 has been completed.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 4 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

4 Solution Architecture

4.1.1 Solution 76 (2217 B28 L700 radio + 2212 B5 W850/N850 mixedmode radio + DUW30 +
BB6630)

Tower/pole
top 2 Port Antenna 2 Port Antenna NOTES
+
LOW
- I O +
LOW
- I O
2 Port antenna (T1000L3R011 SRET)

Quad IMF The KA-6025 will use Port 2 to Control the

KA-6025 future Band change, via ANT B of 2212 B5

Ant A Ant B Ant A Ant B

AISG

AISG

Tx/Rx Tx/Rx Tx/Rx Tx/Rx

NR850/W850 LTE700
2212 2217
B5 B28

Data1 Data2 Data1 Data2

(S3) LTE700
(S2) LTE700

(S2) NR850

(S3) NR850
(S2) W850

(S3) W850

A B C D E F A B C D E F
DUW 30/31 IDL GPS BB6630 (LTE Site) IDL GPS

Design Drawing 76
ARTC NTCS Project

Issue Date Comment

ϭ – ST 27/07/22 Initial Drawing
2 - ST 05/08/22 Connect Filter to L700
Note
Only one Sector is shown.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 5 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

4.1.2 Solution 70 (4480 B28 + B26 L700 + N850/W850 Up The Pole + DUW30 + BB6630)

NOTES
Tower/pole New LTE700 omni configuration to
2 Port Antenna 2 Port Antenna
top allow the tail lengths to be the same
LOW LOW
+ - I O + - I O for the correct operation of 4x4
MIMO.

For the case of LTE700 with omni͛s,

the minimum horizontal diversity
spacing between the omni antenna͛s
within the same height aperture
should also be 2m. While 2m is the
specified minimum, 3 to 4m spacing is
optimum for RF performance.
Twin IMF Twin IMF IMF
BSF0020 BSF0020 KA-6025
A minimum 0.5m vertical gap is
required between antenna͛s mounted
above or below each other on a
structure (i.e. at least a 0.5m ͞air gap͟
between the bottom of the upper
antenna and the top of the lower
Ant A Ant B Ant C Ant D antenna).
AISG

Tx/Rx Tx/Rx Tx/Rx Tx/Rx

For each of these cases, if spacing
LTE700 / WCDMA / NR850 needs to be closer due to practical
Note: W850 Tx will be from Ant A RADIO4480
for Single Carrier and Ant A & Ant B constraints with the structure, the civil
B28 / B26
for Dual Carrier design contractor should discuss with
the RNE RF designer.
Data1 Data2

Design Drawing 70

Note: CPRI config indicative only – refer to LCR0120 for CPRI L700 + NR850 (4Rx) + W850

Issue Date Comment

configurations ϭ – ST 19/07/22 Initial Drawing
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 6 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

4.1.3 Solution 71 (4480 B28 + B26 L700 + N850/W850 Down The Pole + TMA’s+ DUW30 +
BB6630)

NOTES
Tower/pole New LTE700 omni configuration to
2 Port Antenna 2 Port Antenna
top allow the tail lengths to be the same
LOW LOW
+ - I O + - I O for the correct operation of 4x4
MIMO.

For the case of LTE700 with omni͛s,

Twin TMA Twin TMA the minimum horizontal diversity
KA-1033 KA-1033 spacing between the omni antenna͛s
within the same height aperture
should also be 2m. While 2m is the
specified minimum, 3 to 4m spacing is
optimum for RF performance.
Twin IMF Twin IMF IMF
BSF0020 BSF0020 KA-6025
A minimum 0.5m vertical gap is
required between antenna͛s mounted
above or below each other on a
structure (i.e. at least a 0.5m ͞air gap͟
between the bottom of the upper
antenna and the top of the lower
Ant A Ant B Ant C Ant D antenna).
AISG

Tx/Rx Tx/Rx Tx/Rx Tx/Rx

For each of these cases, if spacing
LTE700 / WCDMA / NR850 needs to be closer due to practical
Note: W850 Tx will be from Ant A RADIO4480
constraints with the structure, the civil
for Single Carrier and Ant A & Ant B B28 / B26
for Dual Carrier design contractor should discuss with
the RNE RF designer.
Data1 Data2

Design Drawing 71

Note: CPRI config indicative only – refer to LCR0120 for CPRI L700 + NR850 (4Rx) + W850

Issue Date Comment

configurations ϭ – ST 19/07/22 Initial Drawing

5 Software
RAN SW DUW30 (WCDMA) BB 6630 (LTE+NR)
SW Product SW SW Product SW
Number Product Number Product
Revision Revision
22.Q4 CXP9023291 R29AA0 CXP9024418/15 R64D15
3

6 Preparation

6.1 Use PCI tool to generate Script

Populate the SSIS with IP data from MTAT for the BB, then upload the SSI to the PCI tool to
generate the ZT Project zip file.

4G_5G Script
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 7 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Example ZT project zip file:

The project zip file contains three sub zip files.

It is the sub-zip file AutoProvisioning_Standard.zip that is used for ZT.

Example of the AutoProvisioning_Standard.zip

Example SSIS file:

6.2 Import the LKF into ENM

Use SHM to import the LKF.

7 Remote Procedure

7.1 Perform Remote Integration of the Baseband

On the actual day of integration cutover (connecting the radios to the new baseband):

7.1.1 CMART Validation

Search for CMART number

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 8 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Verify Start/End Date and Status of CMART.

Open the CMART by clicking on the Change ID. At the bottom of the CMART verify Number
of Breaks and Duration of Breaks.

7.2 Zero Touch Integration

For ZT to proceed, the router needs to have DHCP configured. Check How to Check if a
Router is Ready for ZT Integration (Web view). This configuration should now be standard
on all routers.

If ZT integration is to be performed at a site, the following steps should be completed by

ENIC and FE. Once OAM is established proceed directly to step Error: Reference source not
found
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 9 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Note: If the BB has previously been integrated or if repeated ZT integration is required, it

is necessary to perform manual restore of the BB before attempting the ZT steps below.

The main steps to complete a Zero Touch Auto-integration are:-

1. Field Tech (FT) to confirm with ENIC, that Zero-Touch AutoIntegration (ZT) is to be
used.
2. ENIC create site specific remote integration data files required and stores them in
ENM.
3. ENIC starts the Auto-Provisioning steps in internal systems (ENM)
4. FT records and sends the BB hardware serial number to the ENIC, using the required
process.
a. Follow the same Telstra “Baseband Barcode Capture MOP for Zero Touch”
for the required process but send the email to ksd.nic@ericsson.com and
the NIC enginner handling the site.
5. ENIC binds the BB serial number provided by the FT, to the previously
created/stored site specific integration data files, to complete the Auto-Provisioning
prerequisites.
6. ENIC advises FT that all preparations for ZT-Integration have been completed.
7. FT connects the TN port of the BB, to the prepared port of the pre-commissioned
router.
8. ENIC opens the required port on the router, to enable BB to have acces to the
network.
9. When advised by the ENIC, FT then powers on the BB.
a. If BB is pre-configured, then follow the “Consecutive Zero Touch Auto-
Integration” process below, to begin a new ZT integration attempt.
10. The BB detects the network and automatically starts ZT-Integration and contacts
ENM.
a. BB Operational light will continually double-blink, to indicate that the ZT is
in progress.
b. If the ZT process does not start within 5 minutes (no double-blink of
operation light), verify that transmission and router port are correct and then
Power cycle the BB for another ZT attempt.
11. The BB present its serial number to ENM and downloads the awaiting SW and
integration files.
12. The BB will be upgraded and configured by files downloaded from ENM.
a. BB Operational light will become steady
13. ENIC remotely completes the Auto-Previsioning steps for the BB.
14. ENIC completes any remaining integration steps.
15. ENIC activates Cells for call testing.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 10 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.2.1 Import the LKF in ENM

If LKF is unavailable, ensure sitebasic xml has integration unlocked and nodeinfo xml
updated to set install license to false. (this step is already done by PCI tool)

7.2.2 Import the End Entity (EE) in ENM (ZT automates this process)

It is NOT required to manually import the EE into ENM. ZT automates this process.

7.2.3 Update the hardwareSerialNumber in the NodeInfo.xml in the

Auto_Provisioning_Standard zip file

<hardwareSerialNumber>[actual hardware serial number]</hardwareSerialNumber>

7.2.4 Drag and Drop the Updated Auto_Provisioning_Standard zip file into workspace area

Open up ENM CLI and add the project zip fie (scripts) by drag and drop

If file already exists on system, it will be overwritten.

7.2.5 Order the node integration using the ap order command

4G Gen2 (BB): run “ap order file: filename.zip” on CLI to create project in Auto-Provisioning
tool

7.2.6 Use the provided ap status command to ensure the order = completed.

It can take a couple mins to be completed

Run “ap status -p <projectName>”

Run “ap status -n <nodeName>”

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 11 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Note: if order is failed, go to “Auto-provisioning” tool and check relevant project. Under
project there will be the relevant site and here you can export logs which can provide
information on why the order failed. Generally, it is due a fault in the script which does the
pass the ENM initial parser.

7.2.7 Bind the node (Late Binding)

• If the serial number was not known during script creation then a “Late Hardware
Bind” is required. Once the serial number has been received by the field technical
you may perform late binding by the following two methods:

Note: It is critical that the correct serial number get sent to the NIC.

We must always use the serial number marked as KRK 101 05/11 for the Zero
Touch process, and the bracketed “(S)” is not part of the serial number but was
included in the attached list.

Example:

BB6630 (KDU137848/11) - B440778851

7.2.7.1 Method One

Method one in auto provisioning tool click on relevant project and relevant node and select
Bind. You will be prompted for a serial number at which point you enter the serial number
and continue
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 12 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.2.7.2 Method Two

Method two you can run the following bind command in CLI, for example:

7.2.8 Unlock the Router Port

 FT connects the TN port of the BB, to the prepared port of the pre-commissioned
router.
 ENIC opens the required port on the router, to enable BB to have acces to the
network

7.2.9 Switch on the node to start integration

Now on site the field technician just needs to (A) power on the unit and/or (B) factory reset
unit if hardware has pre-existing config on it

7.2.9.1 Power on the BB6630

Field technician should power on the BB6630

7.2.9.2 If Hardware has pre-existing config, perform a factory reset

• If pre-existing config on the node the node will need to be factory reset. There are two
methods to do this à

• Web-gui: connect LMT and configure laptop to be on same subnet

(169.254.2.1 /24). Then in chrome browser type in https://169.254.2.2/ea.html
on this page there should be a “board restore” button

• Note in 19Q4 a MO was created to enable/disable this as a security

feature. If the board restore button is missing please use the below
physical method

• Physical reset: use a small screwdriver or pin to

hold the button underneath the fan LED for 20+
seconds. Wait until blue lights flash and the green
tick LED is flashing at 0.5 hz
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 13 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.2.10 Confirm node integration

At this point the BB6630 should boot up and automatically scan for a VLAN. The DHCP will
be configured to a specific VLAN which when scanned by the BB6630 will provide an IP
allocation. The Node will then connect to the AIWS which will trigger downloading the
config and software for the node.

Observe ENM auto-provisioning tool to observe the integration procedure. It should

eventually state that it is completed.

OR

Use the ap status command to view the node integration status, for example:

ap status -n Enb610

7.3 Remote Integration Script

It is assumed that remote connectivity to the node is available before executing this step. If
a DRAN site is being integrated and there is no remote connectivity to the node, perform
following checks:

1. Ensure the BB port on the router 6471 is unlocked

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 14 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

2. If the port is unlocked and there is no remote connectivity to the node, request tech to
swap the fibres on the TN port and confirm if connectivity is established.

3. If above steps do not restore connectivity to the node, confirm with the site tech that a
correct SFP type is used in line with the distance between BB and R6471. That is, a long
range SFP may need to be used in cases where the distance between the BB and R6471
is large.

7.3.1 Create CV backup

ZT will automatically create a cv name SITE_CONFIG_COMPLETE

But to prevent the system created cv getting removed at node escalated restart, manually
create a cv backup and make it startable.

cvms SITE_CONFIG_COMPLETE_1

7.3.2 Continue loading the PCI Configuration_Files

Unzip the project zip file to extract the Configuration_Files directory.

Eg:

Use netconf command to load sequentially each of the netconf files in the directory.

netconf 03_TN_[xxx].xml

netconf 04_RN_ENBF_[xxx].xml

netconf 05_RN_CUUP_[xxx].xml

netconf PostInstall_[xxx].xml
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 15 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

If any command fails, please record the details log and seek support.

Note: After executing 09_RN xml file, a node restart will create a system cv
Escalation_default_[date_time]+0000

Note: After loading the PostInstall xml, a system cv

RadioNode_CXP9024418_15_R64D15_22_Q4_[date]_[time]_READY_FOR_SERVICE will
be created.

7.3.3 Configure the Qos

Define the queues, traffic shaper and dscp to pcp mapping

netconf Delta_NetConf_[Node_Name].xml

lpr qos

7.3.4 Execute NSD alignment script

7.3.4.1 Use runx command to execute ARTC_delta_alignment_PA3.mos

amos> runx ARTC_delta_alignment_PA3.mos

7.3.4.2 Use diff command to generate a delta load file and load it

amos> diff . 4G_5G_NSD_ref.txt

amos> l cat $diffcmdfile

Copy the output and run the command lines

7.3.4.3 Run the 4G_5G_Delta_S1S3S4_NSD_PA3.mos

The above script should align the node as if Post PA has been loaded. This will allow post
PA to be done at a later time (< 3 business day from integration)

7.3.4.4 Execute 5G_SA_NSD script

run 5G_SA_NSDv3_ENIC_PA1.mos

7.3.4.5 Execute Create_5qi_full.mos

 Download the Create_5qi_full.zip

 Unzip the file to a directory named Create_5qi_full
 Edit the file Create_5qi_full.mos to replace d630505 with your login id & save it
 ftp the directory and files to your enm account
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 16 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

 change directory to Create_5qi_full on enm then amos to the node

 run Create_5qi_full.mos

7.3.5 Set SyncRiPortCandidate

If S1 & S3 (port D & F)

set Transport=1,Synchronization=1,RadioEquipmentClock=1,NodeGroupSyncMember=1
syncRiPortCandidate Equipment=1,FieldReplaceableUnit=DU-1,RiPort=D
Equipment=1,FieldReplaceableUnit=DU-1,RiPort=F

If S1 & S2 (port D & E)

set Transport=1,Synchronization=1,RadioEquipmentClock=1,NodeGroupSyncMember=1
syncRiPortCandidate Equipment=1,FieldReplaceableUnit=DU-1,RiPort=D
Equipment=1,FieldReplaceableUnit=DU-1,RiPort=E

7.3.6 Lock Unused/Disabled Riport & Unlock the Used/Enabled Riport

st riport

Example for S1 & S3:

bl riport=[B,E]

deb riport=[A,C,D,F]

7.3.7 Set nbiot cellrange

If RRU is 2217,

set NbIotCell cellRange 40

If RRU is 4480

set NbIotCell cellRange 120

7.3.8 Create CV Backup

cvms Post_delta_alignment

7.3.9 Restart EnodeB

acc FieldReplaceableUnit=DU-1 restartUnit

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 17 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.3.10 Check Node Status

st cell

st sector

st field – check the radios are locked and enabled

alt

st ret

st tma

st gnb

st sctp

st mme

st ru-

hget ret uniqueId|electricalAntennaTilt| mechanicalAntennaTilt|

iuantAntennaBearing|iuantBaseStationId|iuantSectorId|userLabel

cvls

get . syncRiPortCandidate

7.3.11 Load LKF

Use the below step to step method to load license in node

7.3.12 Execute the Post Upgrade Script on the Baseband

Use run command to execute the 22Q4 Post Upgrade Script

7.3.13 Configure TimeSettings

This is important as failure to set this will cause PA activation to fail

For G2:

For QLD: set timesettings=1 timeOffset +10:00

For WA: set timesettings=1 timeOffset +08:00

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 18 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

For NT: set timesettings=1 timeOffset +09:30

No daylight saving for QLD/WA/NT.

For VIC/NSW/ACT/TAS, G2:

set timesettings=1 timeOffset +10:00

set timesettings=1 daylightSavingTimeOffset 1:00

set timesettings=1 daylightSavingTimestartDate

month=OCTOBER,dayrule=SUN>=1,time=02:00

set timesettings=1 daylightSavingTimeEndDate

month=APRIL,dayrule=SUN>=1,time=03:00

For SA, G2

set timesettings=1 timeOffset +09:30

set timesettings=1 daylightSavingTimeOffset 1:00
set timesettings=1 daylightSavingTimestartDate
month=OCTOBER,dayrule=SUN>=1,time=02:00
set timesettings=1 daylightSavingTimeEndDate
month=APRIL,dayrule=SUN>=1,time=03:00

7.3.14 [Solution 70 & 71] Configure VSWR Supervision for each band
set FreqBandData= vswrsupervisionactive true

set FreqBandData= vswrSupervisionSensitivity 70

7.3.15 Run G2_NTP_Configuration.mos

Due to over subscription(again) of the NTP servers in NSW and VIC, we have deployed a
second set of references in these regions.

We have used a script with an inbuilt algorithm to balance the load between these servers
and would like Ericsson to use the same script to ensure consistency across the network.

Going forward can you please run the following script from enm1/3 on all G2 LTE nodes to
ensure you are pointing to the latest set of ‘correct’ servers:

run /home/shared/common/TNIC/G2_NTP_Configuration.mos
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 19 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.3.16 Set DNCTYPE for MME’s

DON’T FORGET THIS STEP: As part of the 5G network build the DÉCOR feature has been
GAR’d and we now have XXX 5G MME’s online. These are defined on the DNS and the
termPointToMme links from the eNodeB are automatically configured with default
parameter settings. To control how traffic is assigned within the network we need to ensure
that the dcnType attribute on these XXX MO’s are set to SPECIFIC (1).

For WA/SA:

lset ENodeBFunction=1,TermPointToMme=MME_173119000042$ dcnType 1

lset ENodeBFunction=1,TermPointToMme=MME_173106003209$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173105002224$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173104129144$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173104004144$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173104000176$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173103129208$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173103002002$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173103000160$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173102129104$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173102002012$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173102000176$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173101006008$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173101002004$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173101000022$ dcnType 1
lset ENodeBFunction=1,TermPointToMme=MME_173101000017$ dcnType 1

Note: Dibbler post PA will set the dcntype automatically but these should be set prior to
PA.

7.3.17 Block IDL links

Block IDL ports as they are not used.

uv use_nolock=0

bl idl_A

uv use_nolock=1

mcc lldp=1 show lldp neighbors

7.3.18 Create CV Backup

cvms Post_UpgradeScript_time_ntp

7.3.19 Check Node Sync in ENM

The node should be synchronized in ENM.

cmedit action NetworkElement=<node name>,CmFunction=1 sync

cmedit get NetworkElement=<node name>,CmFunction=1

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 20 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.4 Continue Remote Integration

On the actual day of integration cutover (connecting the radios to the new baseband
triplets):

7.4.1 Unlock the radios

deb rru

st rru

7.4.2 Check IMF 6025 is Correctly Defined & Enabled

st imf

get imf rfport

7.4.3 [Solution 71] Check TMA KA-1033 is Correctly Defined & Enabled

7.4.3.1 TMA KA-1033 is shared by L700/N+W850

4(four) tmasubunits have to be defined under TMA-LRDC-0708-[1,2]. N850 rfbranch tmaref

needs to set to tmasubunit 3 and 4.

get rfb tmaref

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 21 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.4.4 Check RET is Correctly Defined & Enabled

RET should have already been configured by the PCI scripts. Note the Ret naming
convention where AntennaUnit_Number in RET must match the AntennaUnitNumber of the
associated MO AntennaUnit.

AntennaNearUnit = RET-<LRD>-<AntennaUnit_Number>[-<AntennaSubunit_Number>]

Where

 <LRD> is the node code

 < AntennaUnit_Number> is the AntennaUnit number of its associated RET unit.

[<AntennaSubunit_Number>] is the associated subunit number of the Antenna Unit

controlling the RET. Only applicable for SRET antenna configurations.
st ret

get ret rfport

get ret iuantsector à check it is correctly defined

get ret basestationid -> check antenna number is correct, no duplidate

get ret iuantinstallersid -> check there is an underscore prefix

7.4.5 Check PTP configuration

7.4.5.1 Check ptp sync is locked

get Transport=1,Synchronization=1,RadioEquipmentClock=1 radioClockState

Result: radioClockState 6 (RNT_TIME_LOCKED)

IMPORTANT: If NOT (RNT_TIME_LOCKED), then run the following commands:

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 22 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

set SystemFunctions=1,Lm=1,FeatureState=CXC4040018 featureState 1

set SystemFunctions=1,Lm=1,FeatureState=CXC4040008 featureState 1

If still NOT NOT (RNT_TIME_LOCKED) after running the above commands, log in to the
router and check the ptp sync status:
show synchronization tod input
show synchronization equipment-clock
show synchronization ptp-port

If you see Signal fail, 1pps (Major) or Equipment Clock Loss Reference 1 (Major), raise a CT
to build team to install the missing GPS/TOD cables.

Check ptp counters on each port:

pget bcoc ptpPackets

If ptpPacketsRx or ptpPacketsTx are not pegged, then try to re-run the above mos file to
delete and redefine, then check the counters again. Also try blocking the remote TN port
and check the local TN port is disabled to confirm the plumbing is correct.

7.4.6 Check CPRI Rx level

sdir or invxr

 For local links over Hybrid feeder (ie R503 to Radio up pole or BB6630 DRAN to
radio 2212/2217/4480):

DlLoss and UlLoss should be no more than 3dB

 For local links within hut (ie BB6630 DRAN to Radio4480 inside the hut):

DlLoss and UlLoss should be no more than 2dB

7.4.7 Check ASM

mfagr -m 0.25

7.4.8 Check Interference level per branch on LTE cells

It should be -120 dbm for L700 and the delta should be < 3db
mfi

7.4.9 Check SNMP3 configuration

st snmp

Result: SystemFunctions=1,SysM=1,Snmp=1,SnmpTargetV3=ENMFM

Use amos to remove snmpv2 if exists.

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 23 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

del SnmpTargetV2C

7.4.10 Check PM counters activation & PM files received

7.4.10.1 Activate counter profile

Activate counter profile (this should have happened automatically while loading scripts)

Check counter are Enabled

pst

7.4.10.2 Check stats files are received on ENM1 or ENM3

Check on ENM directory /ericsson/pmic1/XML to see if stats file appear

 [d625449@scp-1-scripting(enm1) ~]$ cd /ericsson/pmic1/XML

 [d625449@scp-1-scripting(enm1) XML]$ ls | grep -i [LRD]

Eg: ls | grep -I LAXJ
And the following printout appear
SubNetwork=Telstra,SubNetwork=NSW_COUNTRY,MeContext=NSW_LAXJ15_Larmer_Silver_Ave
_520754,ManagedElement=NSW_LAXJ15_Larmer_Silver_Ave_520754

 [d625449@scp-1-scripting(enm1) XML]$ cd [copy the print out from previous

command]
Eg:
cd
SubNetwork=Telstra,SubNetwork=NSW_COUNTRY,MeContext=NSW_LAXJ15_Larmer_Silver_Ave
_520754,ManagedElement=NSW_LAXJ15_Larmer_Silver_Ave_520754
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 24 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

 Check the stats files appear with ls -l

Eg: [d625449@scp-1-scripting(enm1)
SubNetwork=Telstra,SubNetwork=NSW_COUNTRY,MeContext=NSW_LAXJ15_Larmer_Silver_Ave_520754,
ManagedElement=NSW_LAXJ15_Larmer_Silver_Ave_520754]$ ls -l

You should see xml files listed:

If NOT, replace [MeContext], with the node value (eg: eg:

NSW_THLD15_THOMPSONS_HILL_520323 ) and apply the following commands on ENM
CLI and check again using the steps above:
secadm credentials create --secureusername expert --secureuserpassword expert -
n [MeContext]
cmedit set NetworkElement=[MeContext],CmNodeHeartbeatSupervision=1 active=true
alarm enable [MeContext]
cmedit set NetworkElement=[MeContext],InventorySupervision=1 active=True
cmedit set NetworkElement=[MeContext],PmFunction=1 pmEnabled=false
cmedit set NetworkElement=[MeContext],PmFunction=1 pmEnabled=True
alarm status [MeContext]

If xml files still do not appear, please delete and recreate the NE in ENM as per node
creation step in the MOP, then check again.

7.4.11 Obtain post-integration tilt status & save logs

 Get tilt status in Moshell:

>lt all

>hget ret label|prod|serial|iuantSectorId|elec

 Save the output to a text file: <LRD>_Post_Tilt.txt

Keep this file, you will need to upload it (and the pre-tilt snapshot taken in earlier in) to
DRAKE after integration is completed.
hget ret label|prod|serial|iuantSectorId|elec
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 25 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.5 Perform Post PA

For Ericsson RF designed, ENIC sites:

Use single site refresh to select the correct inter-working reftype.

Please follow the Squall PA guideline to assign the reftype.

7.6 Create Final CV

7.6.1 Unlock L700 & NR850 cells/sectors to see cells are enabled
deb sector

Deb cell

st cell

7.6.2 Lock NR850 cells due to no high band LTE anchor

bl nrcelldu

7.6.3 save a CV
cvms Cells_L700_Unlocked

7.6.4 Check System Constant

Check system constants is properly defined per Software level and node type (LTE anchor,
non-anchor)
scg

7.7 Define External Alarms

Check if any external alarms have been created on kget. If yes, load the external alarm mos
file. Many sites would have external alarms defined on ESC already.

7.8 Call Test

Perform call test for LTE cells only. Keep NR850 cells locked after call test.

7.8.1 Lock W850 to allow successful Inter-site L700 Handover

Event B2 = PCell becomes worse than threshold1 and inter RAT neighbour becomes better
than threshold2
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 26 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Due to b2Threshold1Rsrp at -130 dbm and b2Threshold2RscpUtra at -108 dbm, the volte
call will be handed over to 3G if the LTE is worse than -130 dbm and the 3G RSCP is better
than -108. For solution 76, this SRVCC (volte to CSFB) release is often observed at between
9 to 12 km from the site if both 3G and 4G are on air.

Therefore, to allow L700 intersite handover to occur, we have to lock W850 to allow the FE
to travel more than 9 to 12 km without SRVCC, so he can reach the cell border (around
20km) to detect the neighbour L700 for handover to occur.

Unlock W850 after a successful intersite HO.

Alternatively, if the FE can band lock the UE to B28 and select 4G only, then he should be
able to avoid a SRVCC to reach the cell border for handover to occur.

7.9 Post-Check

IMPORTANT : Go through the Check List to audit configuration after remote integration/call
test is completed.
st cell

alt

st ret

st tma

st gnb

st ru-

hget ret uniqueId|electricalAntennaTilt|iuantAntennaBearing|iuantBaseStationId|

iuantSectorId|userLabel

ue print -admitted

cvls

invxr

mfagr -m 0.25

VSWR check with commands (RL > 11.6 dB, see VSWR In Telstra network):

Connect to the Baseband using the OOB IP address (get

Router=OAM,InterfaceIPv4=AltOAM,AddressIPv4=1 usedAddress), if NOK, we need to
check router config and raise it to national team

7.10 Go through Configuration Check List

To ensure quality, please ensure we go through the configuration check list

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 27 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

7.11 Create CV backup to ENM

Use SHM in ENM to back up the CV, name it "Integration_Complete_<date>".

7.12 Raise CT or Open Issue

Raise separate CTs for any new open Issues.

7.13 Send Partial RFU

If call test is successful, partial RFU email can be sent. Proceed to update DRAKE.

7.14 DRAKE Update

Update the DRAKE to set the NSD PA completed date

IMPORTANT (on same day) : Update DRAKE and set "Cells On Air" date. Ericsson will
perform a Post PA within 3 business day of the cells are put on air & SOA in Ericsson tool
Site Handler will trigger Ericsson RF team to update the QUOLL to put "cells in service not
accepted".

7.15 24 Hours Alarm Check

Perform 24 Hrs once all the pending issues are cleared and upload the results in SH.

7.16 Send Full RFU email

If site passes 24 hr alarm check with no outstanding issues, send the Full RFU email.

7.17 Whisper Update

Update Whisper once the node has passed 24 Hrs, including the full RFU email.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 28 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

Update BOTH Transmission Integrated Date” and “ENodeB completion date”.

Debor Team [lungile.ncube@ericsson.com, TBD] requests SAO Mobility

(MobilityNetworkAssurance@team.telstra.com) to create a new RODS Alert OR DeBor team
updates RODS directly, to be entered against the site, to indicate it is running BB5216 in a
1GOA scenario.

7.17.1 Site Handler Update

 Update CMS425 and upload post logs, tick off "Site Alarm Free" and "SOA"
Remote Integration log is stored on OSS under
/ossrc/upgrade/project/Integration/Post_Integration_Logs/[node_name]/
 VSWR check with commands (RL > 11.6 dB, see VSWR In Telstra network):
 Please tick alarm free boxes if applicable
 Please tick Site on air for all technologies if applicable
 Ensure CMS425 is actualized
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 29 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

8 Reference:

8.1 Emergency Call Handling

For 3G:

https://hangar.in.telstra.com.au/mobiles_in/triple0/result.php

For 4G:

https://hangar.in.telstra.com.au/page/network#f=CIMSE000Cube/
Calls_In_Progress.xml;m=17-1-0;ct=xml;

With these tools, we can check 3G 000 call on LAC level, so we need to make sure the cells
we are to soft lock do not fall into one of these LAC.

For 4G, the tools give us 000 on cell level, so we can check if our cell is one of the listed 000
cells. If not, hard lock the cell is the current Telstra procedure.

8.2 Manual Restore of BB6630 or BB5216

Perform the steps below then return to ZT integration again

Manual Restore of a BB6630 or BB5216 (Web view)

8.3 Monitor the progress of ZT

1. If ZT fails to complete (TN port down/no OAM to BB), request FE to obtain the AI
WEBGUI log
2. During ZT AI, login to the router and issue command: show arp-cache all to find the
DHCP IP address allocated to the BB
3. Select another NE already integrated in ENM, right click and select "Launch Element
Manager"
4. A browser will pop up.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 30 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

5. Modify the url by typing https://[enter the dhcp address] to open the following page
then select Autointegration tab to check the failure reason

6. Investigate the logs to find out the failure reason

7. If the above is not able to be obtained, and RANOPS login locally is not possible, it is
necessary to redo the ZT integration (follow the MOP here)
a. Get FE to factory reset the board, follow these steps here
b. Delete existing AP node - ap delete -n [FDN]
c. Delete the NE from ENM
d. Go to SP to find the ZT zip file for the node from here. Open the nodeinfo.xml
and check the <upgradePackageName>RadioNode CXP2010171/1 R9G11
20.Q3</upgradePackageName> exists on the ENM
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 31 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

e. Drag and Drop the Project zip file into workspace area (follow the MOP 8.2.1)
f. 5G Gen3 (BB 6648) + AIR 1281: run “ap order -nv file: filename.zip” on CLI to
create project in Auto-Provisioning tool. Note: due to limitation with current
ENM use of option ‘-nv’ required to disable validation
g. Run “ap status -n <nodeName>” to check status complete
h. Do late binding ap bind -n <nodename> -s <serial number>
i. Power on the BB

8.4 Troubleshooting

8.4.1 ZT

 Node OSPF private IP was incorrectly set to .97 instead of .98

 Router (show config dhcp) shows incorrect DNS server (ie. Ntp) .21 used instead
of .6
 FE sends the serial number on the side panel of the BB instead of the one on the
front panel resulting in missing SIF files in the ZT logs sent by FE.

8.4.2 BB has ptp sync issue

 pget bcoc ptpPackets show rx is not stepping but tx is stepping on the enb
 Missing config on tod-a on the router, apply the following changes:

configure
synchronization
equipment-clock
wait-to-restore 0
ql-enabled
input-source 1 external tod-a
priority 100
force quality-level ql-prc
commit
end

configure
synchronization
ptp-clock g8275-1 t-bc
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal Implementation Instruction 32 (32)

Prepared By (Subject Responsible) Approved By (Document Responsible) Checked

EPAWENG Steven Weng

Document Number Revision Date Reference

PA10 2023-05-24

local-priority 32
holdover-time-error-budget 10000
ptp-port 16 virtual
description GPS clock reference
local-priority 32
no shutdown
attach tod-a
commit
end

save config
y