Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 1 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Overview

Hi all, this guide is designed to whole NIC people due to the upcoming exorbitant load of Anchor sites which we could receive without any knowledge
about how to work with them. We are not experts, but we have decided to share our experience with you: our partners.

“All for one and one for all, united we stand divided we fall.”
-Alexandre Dumas, The Three Musketeers.
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 2 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Phase 1:

UMTS and GSM could be in mixed mode with L19 1st or 2nd carrier. If UMTS is in mixed mode with the 1st Carrier, we’re going to use AIR32; otherwise,
we’re going to use Radios 4415/4424. Every time that you have UMTS in Mixed Mode with LTE, UMTS will use Data 1 and LTE will use Data 2.
GSM as well as UMTS could use any carrier with any of the Hardware mentioned above. The only difference will be Data Ports usage, LTE will be Data 1
and GSM will handle Data 2.
Radio 4415 AIR32

D1 D2 D1 D2

DUW BB6630 DUG

Mixed Mode Port configuration

Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 3 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Table 1.1 Table 1.2

You need to check the following things before starting the activity:
• Software in UMTS: You need to check that we have W16 (CXP9023291/6_R4DB01) in the node.
ULA03248A2> cvcu
200602-20:01:36 11.245.5.228 17.0m RBS_NODE_MODEL_U_4_343_COMPLETE stopfile=/tmp/27963
==============================================================================================================
200602-20:01 CV Name Upgrade Package Release
==============================================================================================================
Startable: 4_ULA03248A2_Set_bandwidth CXP9023291/6_R4DB01 W16B (C16.2-EP25-2)
Loaded: INITIAL_CXP9023291_6_R4DB01 CXP9023291/6_R4DB01 W16B (C16.2-EP25-2)
Executing: 4_ULA03248A2_Set_bandwidth CXP9023291/6_R4DB01 W16B (C16.2-EP25-2)
Last created: 4_ULA03248A2_Set_bandwidth CXP9023291/6_R4DB01 W16B (C16.2-EP25-2)
-------------------------------------------------------------------------------------------------------------------
Current UpgradePkg: UpgradePackage=CXP9023291/6_R4DB01 CXP9023291/6_R4DB01 W16B (C16.2-EP25-2)
AutoCreatedCV: Enabled. Daily backup at 04:00
Ongoing CV activity: 0 (IDLE)
Rollback status: Rollback is off
==============================================================================================================
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 4 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

If you don’t have this SW, please proceed to upgrade it, meanwhile, the FE could modify IDB on site.
• In your scripts you will have a folder labeled “GSM”, into it you must see a script to run in Winfiol e.g. below:

IEBSC901_VY028_DT.
txt

You need to confirm which SW will be used:

!*********************************!
!** UPDATE THE SOFTWARE *!
!*********************************!
RXMOC:MO=RXOTG-41,SWVER=B1316R087D;
RXMOP:MO=RXOTG-41;

In the case above - please refer to Table 1.2 - we can see GSM will handle AIR 32, so it will be in mixed mode with the 1st Carrier.

After completing the Software Upgrade in UMTS we need to send External_hw to FE and ask him to load it into DUW and check if he has already
modified the IDB.

• Please make sure that Software Versions are the same: RXMOP:MO=RXOTG-[YourTG];
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 5 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Next step will be

• Start integrating the L19 2nd Carrier in Legacy Node.

You only need scripts contained in folder LTE/L[SITEID], they would look like the next ones:

Picture 1. L19 2nd Carrier Scripts

Once finished with all scripts, proceed to run the Baseline for L19 2nd Carrier located in
/home/shared/EJAMBZD/Baseline/Baseband_CarrierAdd_Baseline/2nd_Carrier/Tmobile_L1900_2ndCarrier_anchor_01_L20Q1_BBU_baseline_pa5.mos

Please take on consideration that we have one script to run in the RNC that you must run after all the scripts are completed.

Once Baseline has finished don’t forget to run L[SITEID]_LTE_NGS.mos in Legacy node (which is in the 2nd visit folder of the scripts package), it will
create more NGS references on it.

We can throw next command: get member=

Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 6 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Picture 2. Node Group Sync Member after L19 2nd Carrier

After FE told you that export and delete is completed -And you have connectivity with UMTS node- you need to perform the next steps:
• Run DUW Baseline, it is in /home/ejambzd/Baseline/
• TMO_BASELINE_W16B_DUW_RBS_rev13-0-70_PA1.mos (until 06/03/2020)
• You will have scripts like next ones

Picture 3. UMTS Scripts

To this procedure we need to deactivate the safe feature (safe-) activated in UMTS for a while; please follow the order marked in the scripts.
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 7 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Please, before running the UMTS scripts, uninitialize your sectors, find the procedure below:
• Throw hget sector band|numberOfTxBranches, this command gives information needed to init sectors once we are done

ULA03546E> hget sector band|numberOfTxBranches

200614-17:49:33 11.246.77.67 17.0m RBS_NODE_MODEL_U_4_343_COMPLETE stopfile=/tmp/16481

.
=================================================================================================================
MO band numberOfTxBranches
=================================================================================================================
Sector=1 2 2
Sector=2 2 2
Sector=3 2 2
=================================================================================================================
Total: 3 MOs

• Acl NodeBFunction=1,Sector=

========================================================================================================
Proxy MO Action Nr of Params
=========================================================================================================
1238 Sector=1 initSector 2
1238 Sector=1 unInitSector 0
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 8 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

• Acc NodeBFunction=1,Sector=1 unInitsector -> You need to throw this one for each sector

After Script 5 we can check the changes with get . maxtot

Example for radios 4424 is below
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 9 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

• For script 7 we can throw next command: get member=

In which we can check the next (to confirm that it was successfully set):
In syncRiPortCandidate we have 3 defined: Ri_Port_A, Ri_Port_B and Ri_Port_C

Picture N. Node Group Sync Member defined on UMTS

As last step for UMTS we need to run a script on RNC

Picture N. Script example

It will change power to cells on RNC and we can proceed -if radios are connected- to bring our UMTS up and check for alarms.
 Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 10 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Phase 2:

As a first recommendation, once you have a site where you need to perform this phase please ask IC/IM available to provide you SCU IP. This info
needs to be sent to FE to configure SCU and after this we can proceed to configure it by our end.

SiteID corenet_subnet nmnet_vlan nmnet_subnet market_nm OAM gateway CSR Port SCU IP address SCU Subnet Mask SCU VLAN tag SCU NTP IP
LA03368B 51.76.28.224 4001 11.204.28.224 LA 11.204.28.225 1/1/24 11.204.28.247 255.255.255.224 null 51.204.28.228

Picture N. SCU Info provided by Market

We need to look up for scripts to know how many Anchor nodes we are going to have. In your scripts folder you will find “01_LTE_B25_L41_Add” folder
and there you can see Anchor Nodes:

After this we can check if we have available ECI Files in ESI Portal -If not, please request for them to ECI Team
MANA NTW TMO CVF [email protected] – Send these ones to your FE.
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 11 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Once you have connectivity in the L41 and N41 BBs proceed to do the enrollment, URI alarms, supervisions, time zone setting and management state
to normal in all of them; after that, please run the baselines below (even if they are loaded with the ECI file):

• Basebands L41:

/home/shared/EJAMBZD/Baseline/LTE_NSB/Tmobile_01_L20Q1_B41_baseline_BBU_pa7.mos); Restart each Baseband after it.

• Basebands N41:

For these ones we need to perform more steps such as the ENDC process but by now -thinking that Tower Crew is working on radios- we only need to
run the Baseline (located in /home/shared/EJAMBZD/Baseline/5G/N41_Baseline_Rev_I.mos) on them; after these restart basebands.

• SCU

Do you remember the first recommendation about requesting the SCU IP? Well, once t it has connectivity -FE needs to tell you about it- so, you need to
perform the steps below:

1- Confirm info provided by FE with a new tab on SecureCRT, you need to throw next command: ping -c 3 SCU_IP
See an example belo

Picture N. Check contact with SCU

Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 12 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Once we have reached communication with the SCU we can proceed to change generic SCU name -usually is SCU serial number- to SITEID that it
belongs, the process could be find below, just take in consideration that it needs to be performed on SSH (amos terminal) ENM GUI.

Throw ssh -q oss@SCU_IP to log in

ssh -q [email protected]
password: default
gettransactionId
getMOAttribute SDN=0 name
startTransaction T1
setMOAttribute t1 SDN=0 name="LA03368B"
commit T1
endTransaction T1

Picture N. SCU Name Definition (SSH)

Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 13 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Here you can find a bug, when someone has been trying to configure it and you see the information highlighted below in the first command:

LA13098E> gettransactionID
json
OperationSucceeded

In that case, it does not allow you to change the name, so you need to do the following:

1- Open your OSS with Citrix and go to your filezilla browser and enter: https://[SCUIP] as you can see in picture below

Picture N. SCU Login in Firefox Browser (Citrix)

2- Here it requests a user and password: user is oss and password is default. After this, we can see the SCU environment
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 14 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Picture N. SCU Environment

3- In SCU environment you must go to “Advanced configuration”; next, you will find “Transaction control” when it has the issue mentioned
previously, in Transaction ID you will see “json” and the only available button will be End, you need to click on End and you will see all as
picture below and you can return to SSH ENM GUI to continue with SCU name change.
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 15 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Picture N. SCU Advanced Options

After changing the name, we can proceed to create SCU on ENM GUI

• Go to Network Discovery>Create Discovery Activity and you need to put the next info:

Activity Name Probe port

<SCU name from CIQ>_SCU (SITE ID_SCU) 161
Description Read community
<SCU name from CIQ>_Discovery (SITE ID_Discovery) public
Network Address Range Discover NE Type(s)
IP of the SCU SCU
Connection Profile Add NE Options
Name of connection profile created/found above Enable Management for FM and PM
SNMP Connection Type Device Naming String
SNMPv2c SCU Name from CIQ (SITEID)
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 16 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Picture N. Info Required to define Discover SCU on ENM

Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 17 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

• Next, we save it and check that Discovery Activity be successfully created as you can see below.

Picture N. SCU Successfully Created

Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 18 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

N41 ENDC Process

First, we need to check what scripts we have available, you must have one folder with scripts like the ones below

We need to run scripts at next way:

1- Run Rilinks script and after it check that they get enabled
2- Run IDLE_Script
3- Run 02_NSITEID2_PTP_Slave_Configuration
4- Run eNB_ENDC_Creation_LTE_Multisite_NSITEID2_endc in all LTE nodes -AAS/L25/LTE Legacy-
5- Run gnb_ENDC_Creation_NSITEID2, only in N anchor node
6- Run LTE_PmFlexCounterFilter_LSITEID[N]_endc only in site labeled on script
7- After this you need to restart all nodes, NR600 first, then legacy LTE, LTE second nodes, finally the remaining nodes
8- When BBs return run 02_NSITEID2_Intrafreq-intragnb-relation in N Anchor node with Cells Unlocked
9- Run Node_GutranCellRelation_LSITEID in legacy with cells unlocked
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 19 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

Apendix A
URI Sets once you are done with enrollment for each ENM:

POL2:

• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 uri sftp://mm-

[email protected]/smrsroot/software/radionode/RadioNode_CXP9024418_12_R57C74_20.Q1
• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 password
cleartext=false,password=1:Y+zTwuENMXR9TW5ZaipuaI3MRItTpYb0

POL8:

• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 uri sftp://mm-

[email protected]/smrsroot/software/radionode/RadioNode_CXP9024418_12_R57C74_20.Q1
• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 password
cleartext=false,password=1:B0UlmtYYO+/GOrwI8OWmshJNAHW5hgw=

SYL6:

• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 uri sftp://mm-

[email protected]/smrsroot/software/radionode/RadioNode_CXP9024418_12_R57C74_20.Q1
• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 password
cleartext=false,password=1:woOsvUhP+XBAe7rNtrKG4cWMcBnSP51E
• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 password
cleartext=false,password=1:6G8tsw4+jzThnhywtN8bo636Bztwf/kJ
• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 password
cleartext=false,password=1:VbIDX0LZXY1/NN1+Uge0drpWV9vo0bX3
Confidentiality Class External Confidentiality Label Document Type Sheet

Ericsson Internal Public Guideline 20 (20)

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

EUVLLAI Luis Antonio Alvarez Bautista; EONOMON Mónica Itzayana Onofre

Serviño
Document Number Revision Date Reference

Uen PA1 2020-06-02

POL3:

• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 uri sftp://mm-

[email protected]/smrsroot/software/radionode/RadioNode_CXP9024418_12_R57C74_20.Q1
• set SystemFunctions=1,SwM=1,UpgradePackage=CXP9024418/12-R57C74 password
cleartext=false,password=1:5nlySmCEv33iDTTBkNmdLk38DB7FuqY=