Ericsson Internal 1 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Madhusudhanan.M
Checked
Date
Rev
2017-08-19
B
Reference
CONFIGURATION MOP FOR ADDING LTE ON BBU BASED UMTS SITES This instruction set is valid for adding LTE configuration on already live BBU based UMTS sites. This document is based on running the delta or additional scripts (LTE) to already configured and working UMTS site. For adding LTE on UMTS, referred as L+W, configuration changes need to be carried out in the following domains.
Transport Network BBU 5216 OSS On Field
Current configuration at the site is as depicted by following diagrams.
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
The current configuration of the site includes separate BBU for UMTS and DUS31/41 for LTE DUS 31/41 might have TDD+FDD .
FIG 1 : RRUS12 B1 connected directly to the BBU.
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Madhusudhanan.M
Checked
Date
Rev
2017-08-19
PA2
Reference
FIG 2 : Separate DUS31/41 for LTE FDD+TDD.
This needs to be changed as per the following: ONLY ONE BBU will be used for UMTS and LTE (FDD+TDD) Port A-B-C and so on are currently connected to RRUS12 and RRUS14 will in return must be cascaded to these RRUS12. The number of Cascaded cable needed will be 1 per FDD sector. TDD Radios must be connected directly to the BBU RI ports (D-E-F).
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
WITH GSM 1800 RRU MIXED MODE Sites where GSM 1800 is in mixed mode radio with LTE we must define the NGS in BBU.
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
CONFIGURATION CHANGES REQUIRED IN TRANSPORT NETWORK
1. The existing port of TN equipment, connected to UMTS BBU port – TNA or TNB , will now be used to carry the new LTE traffic hence it should have the new LTE VLAN and IP configurations as a prerequisite to this activity.
CONFIGURATION CHANGES REQUIRED IN OSS
1.
The existing UMTS site must be re-configured as a MIXED (L+W) mode site in the OSS and relevant PM profiles should be attached to it.
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M S.No 1 2 3 4 5
Date
Rev
2017-08-19
PA2
Reference
Actions Need to be change site ID 3G to 4G(Site name should be LTE) 3G and 4G site need to be deleted in OSS Site Should be define as LTE subnetwork as a Mixed mode(L+W) in the OSS After Definition, should be re-enrolled After Enrolment, Mix Mode counter (3G+4G) Profiles activation
Team Resp RAN OSS OSS RAN OSS
ON FIELD CHANGES: 1. Field technician should inform about starting the activity. 2. Proper safety measures should be adopted before the start of any filed activity. 3. Field technician must remove CPRI cables connected to Port 1 of RRUS14 B3 at the radios and connect cascading cable from this port to Port 2 of RRUS12B1. 4. Please follow the connection diagram for FDD as shown below.
5. Further, Sector 1 of TDD on Radio 1 (RRUS4412 B40) ,Sector 2 of TDD on Radio 2 (RRUS4412 B40) Sector 3 of TDD on Radio 3 (RRUS4412 B40) should be directly connected to the BBU.
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
6. Disconnect the GPS and from DUS and connect to the BBU.
7. Disconnect the RJ45 Media cable from TN_A port of DUS else MME connectivity will not be stable in BBU.
8. Please follow the connectivity diagram for TDD as shown below.
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
CONFIGURATION CHANGES REQUIRED IN BBU 1. Install the mixed mode License file and activate the features recommended by RF. 2. Take logs of existing alarms and create a pre-activity CV. 3. UMTS BBU should be configured with additional RRU(s) and sectors for e.g. If there are 3 sectors already up and running with UMTS and we must add more sectors for LTE FDD and TDD as per site configuration and then new RI links and RI ports should be configured along with new RRU(s) and sectors. 4. This can be done of by running the delta “SITE EQUIPMENT SCRIPT”. 5. This needs to be done via OSS or Cygwin as this file is has .xml format. Transfer the Site Equipment Script to the OSS and input the following command at the OSS prompt – and NOT in Moshell prompt. ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830 “maintenanceUser”@”IP” -s netconf < “filename”.xml maintenanceUser=RBS User ID IP=RBS ONM IP Example: ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830
[email protected] -s netconf < SiteEquipment_ UMTS1.xml
6. Alternatively, the following script can be used up to 3 sectors 3G/FDD.
BBU_3_RRU_ADD_F DD+TDD.mos
7. For sites where there are existing 4 UMTS and 3 FDD sectors the use the followings script.
BBU_4_3G_RRU_AD D_FDD+TDD.mos
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
8. For sites where there are existing 5 UMTS and 3 FDD sectors the use the followings script
BBU_5_3G_RRU_AD D_FDD+TDD.mos
9. For sites where there are existing 6 UMTS and 3 FDD sectors the use the followings script
BBU_6_3G_RRU_AD D_FDD+TDD.mos
10. This L+W site should also have VLAN and IP configuration of LTE site that is being added to the existing BBU. For this delta “site basic file” also needs to be run. Since this file is also in .xml format, above procedure must be adopted. Transfer the “Site Basic file” to the OSS and input the following command at the OSS prompt – and NOT in Moshell prompt . ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830 “maintenanceUser”@”IP” -s netconf < “filename”.xml maintenanceUser=RBS User ID IP=RBS ONM IP
Example: ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830
[email protected] -s netconf < SiteBasic_ UMTS1.xml
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
11. After all the above configurations are done. It is time to define the other provided scripts. Since these are in. mos format they will be run in Moshell prompt. Transfer these files to the OSS and create moshell session with the node and run using “run TN_FILE.mos” and “run RN_FILE”. Mos
12. Load the new mixed mode license in the BBU and activate the recommended features.
FDD+TDD FEATURES.txt
13. Change the dnPrefix, networkManagedElementId and userlable of the node as per the LTE MO NAME. ####### CRITICAL STEP ###### set 0 dnPrefix SubNetwork=ONRM_ROOT_MO_R,SubNetwork=LTE,MeContext=”LTEMONAME” set 0 managedElementId set 0 userLabel
“LTEMONAME”
“LTEMONAME”
14. Run following the X2_MME_SGW_OSS script.
X2_OSS_SGW_OQS_ OSS.txt
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
15. Run the GPS SYNC definition script.
GPS SYNC BBU.txt
Node will take a refresh.
16. In case of mixed mode GSM RRU, NGS must be defined using the following script
NGS SCRIPT BBU.txt
Node will take a refresh.
17. Run the following RF parameters script.
LTE_RF_BBU_FDD_T DD_2C Script_1.txt
18. Make sure there are no new alarms.
19. Make a cv “AFTER_DUS_BBU_SWAP”
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Checked
Madhusudhanan.M
Date
Rev
2017-08-19
PA2
Reference
POST CHECK LIST :
Following commands must be run to check the status of definition.
1. alt (to check alarms. There must be no new alarms) 2. st ru ( To check the status of RRUs) . All should be unlocked and enabled. 3. lbl AntennaNearUnit=2 (To lock the AntennaNearUnit=2) 4. get . radioclock ( to check synchronization status . It must me RNT_TIME_LOCKED) 5. st mme (To check the status of term point to MME. There must be 4 MME defined and all of them should be enabled ). 6. pr sgw (To check SGW definition . There must be 7 SGW defined). 7. get gnssinfo (To check the status of GPS clock. It must display “synchronized” 8. st cell ( To check the status of UMTS and LTE cells . They must be unlocked and enabled. If some cells were already locked prior this activity they must be kept in locked state only ) 9. ue print -admitted ( to check LTE traffic) 10. get . noofra ( to check UMTS traffic) 11. get . nodeg (To check the status of NodeGroupSync MO. The output of this command must have two mo or proxies) 12. get . configuredMaxTxPower ( All LTE cells should have its value as 40000) 13. If after the activity RRUS 13-14 and 15 are down along with their RiLinks run the following.
SWAP_RRU13-14-15 ISSUE FIX.txt
Ericsson Internal 10 (12) Prepared (Subject resp)
No.
SHANKAR THAKUR Approved (Document resp)
Madhusudhanan.M
Checked
Date
Rev
2017-08-19
PA2
Reference
