Generic Method of Procedure

LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

Integration/Migration of 2xDUS to 2xBB5216 (no IDL) + XMU

_____________________________________________________________________________________

SCOPE OF WORK

Version 17.31

Creation history

Author/s Version SW Description/Update

Jennifer Carino 17.31 L17Q3 Added pmVoipQualityUeUlOk stat
Added ANR deactivation and activation
Jennifer Carino 17.0 L17Q2 Initial release
Noel Lacson 17.0 L17Q2 Initial release
James Jalandoni 17.0 L17Q2 Initial release

Contacts

Jennifer Carino 714-875-4507 [email protected]

Noel Lacson 469-236-4132 [email protected]
James Jalandoni 469-583-3185 [email protected]

Page 1 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

ASK YOURSELF

It is AT&T’s mandatory requirement to review and acknowledge that you have applied their Ask Yourself
Principles before touching the network to ensure flawless customer execution and network reliability. It
is also important that you have completed AT&T’s training course (51247894) before you begin any kind
of work in AT&T’s network. If you answer NO to any of the first 10 questions below, stop and resolve the
issues prior to resuming your work.

Ask Yourself Questions YE NO N/A

S
1. Do I have the proper ID and appropriate building access permissions for
the environment I am about to enter?
2. Do I know why I’m doing this work?
3. Have I identified and notified everybody, customers and internal groups,
who will be directly affected by this work?
4. Can I prevent or control service interruption?
5. Is this the right time to do this work?  
6. Am I trained and qualified to do this work?
7. Are the work orders, MOPs, and supporting documentation current and
error-free?  
8. Do I have everything I need to quickly and safely restore service if
something does go wrong?  
9. Have I walked through the procedure?
10. Have I made sure the procedure includes proper closure, including
obtaining clearance and release from the appropriate work center?  

E911 Ask Yourself Questions YE NO N/A

S
1. Does this work have a direct impact on Mobility E911? (Note: Turning
down a cell site is not a direct impact to Mobility E911 per AT&T.)
2. Is E911 testing required? If yes, is the individual performing the testing
familiar with the E911 test requirements of AT&T?

Page 2 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

1. Get a head start and gather all files you need; Scripts, CIQ, EDP, LKF, NBR dump as needed.

2. Check Scope of Work. Compare existing config of the node/s with the desired config in RF-validated
CIQ. Validate scripts if correct. Verify EDP. If we are migrating sectors, make sure RF had sent the
NBR dump of the current existing nodes. No NBR dump means no integration.

3. Check the latest SW packages currently in use in Ericsson Network Manager (ENM). Confirm with FE
that he has an official copy of the SW packages needed as contingency measure in case of rollback
or fallback. (The information on official release and integration readiness of the SW packages must
come from the customer (e.g. AT&T) through the Nexius Integration Manager. This information
must be acquired prior to the day of integration.)

4. When working with live nodes, e. g. 2 nodes with DUS-to-BB5216 conversion and sector migration,
make sure that both nodes have the same SW Package version prior to activity. If DUS SW version is
the same at precheck, the equivalent BB5216 SW version must also be the same for both nodes
after integration. If not the same prior to activity, inform your FE and OSS Supervisor. Customer will
need to upgrade the node with the lower SW version and inform Integration Manager when the site
is ready for integration.

5. Verify with FE the NFSD and EIM work tickets. No work tickets mean we cannot start integration.
Include this info in your Integration Report.

6. Confirm site readiness with FE. Verify if all the required hardware is available onsite, including
power connection of new equipment, fibers, and other ancillary materials, as well as the SS Kit.

7. Run your precheck macro and save the logfiles. You will need to run precheck on all the live nodes
that exist at site, including the ones you are not touching. Fetch pre-KGET and pre-KPI.

 kget all
 pmr -r 106

8. From the logs generated by your precheck macro, save in a separate file the RSSI, VSWR, and RET
information of the live node/s as well as alarm history and current node alarms. You will need this
information later to compare with your post checks. In the case of STX market, this separate file
containing RSSI/VSWR/RET is required to be attached in the Integration Report.
Page 3 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

9. Verify alarm status with FE. With any critical or major alarms, if unsure whether to cancel integration
or continue, seek advice from OSS Supervisor. Confirm from FE if he had completed his pre-photo
essays, backup CVs, and other prechecks.

10. Perform pre-CV backups. Prior to creating the CV, make sure ManagedElementData=1
autoConfigurationAllowed is set to true.

set ManagedElementData=1 autoConfigurationAllowed true

cvms CV_SXL05514_20170425_ORIG

cvset CV_SXL05514_20170425_ORIG

cvget CV_SXL05514_20170425_ORIG

Save files in your home folder. You will need to attach these files in your final report (Prelogs,
Pre-KGETs, Pre-CV backups, pre-KPIs/PMRs, alarm history.

/home/shared/v03076/Ericsson/BB5216/SXL05514_SXL05014_BB5216

KGET_SXL05514_20170425_orig.zip

PMR_SXL05514_20170425_pre.zip

SXL05514_CV_SXL05514_20170425_ORIG.zip

SXL05514_PreLog_20170425.zip

SXL05514_AlmHist_20170425.zip

11. Check TN port with FE. Have the FE troubleshoot with MNRC for any transport issue.

12. Provide port assignment details as per market/CIQ. Verify existing ports and the new port
connections with FE.

13. Check and load LKF in ENM. These 2 must be present. (applicable with BB5216 only)

IPv6 Backhaul Support

Page 4 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

VirtualRouters

14. FOR SITES WITH 2xBB5216 migration where 2 DUS’s are existing,

before deleting the node in ENM do a screenshot of this info in case of rollback:

cmedit get NetworkElement=SXL00031

cmedit get NetworkElement=SXL00031,CppConnectivityInformation=1

15. Lock down all MO’s, FDDs, sectors, RRUs, termpoints, MMEs. Save CV. Inform FE he can bring the
DUSs down.

16. DELETE the 2 DUS nodes.

cmedit set NetworkElement=SXL00031,CmNodeHeartbeatSupervision=1 active=false

cmedit set NetworkElement=SXL00031,InventorySupervision=1 active=false

fmedit set NetworkElement=SXL00031,FmAlarmSupervision=1 alarmSupervisionState=false

cmedit set NetworkElement=SXL00031,PmFunction=1 pmEnabled=false

cmedit action NetworkElement=SXL00031,CmFunction=1 deleteNrmDataFromEnm

cmedit delete NetworkElement=SXL00031 -ALL –force

17. Once BB is board-restored, load AP files.

ap order file:SXL05014.zip

ap status -p SXL05014

ap status -n SXL05014

18. Download site install script, zip it, and mail to FE. FE will commission the node/s.

ap download -o -n SXL05014

Page 5 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

19. Check AP status and activate supervision.

cmedit set NetworkElement=SXL04202,CmNodeHeartbeatSupervision=1 active=true

fmedit set NetworkElement=SXL04202,FmAlarmSupervision=1 alarmSupervisionState=true

cmedit set NetworkElement=SXL04202,InventorySupervision=1 active=true

cmedit set NetworkElement=SXL04202,PmFunction=1 pmEnabled=true

alarm enable SXL04202

cmedit get SXL04202 CmFunction.syncStatus

cmedit action NetworkElement=SXL04202,CmFunction=1 sync

20. When logging in for the first time, you may need to type in user/password of the node.

For DUS

user = rbs

password = Ltecho!4G

For BB5216

user=rbs

password = Er1css0n#BBU

21. Amos to node and check licenses.

get Lm=1

invl

hget CXC4011161|CXC4011162|CXC4011182|CXC4011620|CXC4011621|CXC4010625|CXC4010626

get KeyFileManagement=1

get . fingerprint 

get SystemFunctions=1,Lm=1 

get SystemFunctions=1,Lm=1,KeyFileManagement=1,KeyFileInformation=1 

get CXC4011823

Page 6 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

get CXC4040006 

22. Run the rest of the integrations scripts once you establish stable connection to node.

23. Run TN MME and Feature activation script. SRVCC feature must be the same in Pre-KGET.

cmedit import -f file:SXL05014_TN_MME.xml -ft 3GPP -t Live

cmedit import -f file:Feature_Activation_L17A_SXL04202.xml -ft 3GPP -t Live !!!ATENTION!!! This

step does not apply anymore. Now scripting team has provided a mos script instead.

BBU_Feature_state_elastic_Activation_.mos

cmedit import -st -j 1133 -v

24. Run the RBS scripts folder according to sequence. This step includes running RiLinks and
AirIfLoadProfiles before proceeding to load the FDD scripts.

25. In NTX, if radios are not 4478 and have 4 ports on 1900 and 2100, we add a second fiber depending
on the RFDS/CIQ config and BW. In STX, we do not add a second fiber but use 10G SFP instead. For
both markets, we use 10G SFPs if the radios are of type 4478.

26. These 4 antenna parameters must be the same original values from your KGET for live sectors. If
not, you need to update the scripts.

dlAttenuation

ulAttenuation

dlTrafficDelay

ulTrafficDelay

27. For STX, WCS RF ports or any other radios with 4 ports must be ACBD. For NTX and DSW, 4-port
definition must be ABCD. Note: this definition is only for new sectors. Existing port definitions must
remain the same regardless of whether they were ABCD or ACBD before.

Page 7 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

28. If your radios for 1900 or 2100 are RRUS12, do not forget to check your RRU scripts. They must have
RXA_IO and RXB_IO rfports. Also, check pre-KGET for RRUS12 radios. If they have RXA_IO/RXB_IO
ports, then you need to redefine back to the new BB.

29. For new node, run the scripts for the new sectors first up to relations. Then run the NSB baselines. If
new node does not have new sectors as in the case of the first of two BB5216s, run the first live
sector carrier script, run the NSB baselines, then delete the sector. After this, load all the live FDD
scripts including the one you deleted. The objective is to NOT LOAD the NSB baselines after all live
sector carrier scripts were ran to prevent overwriting the cloned parameters inside the live FDDs.

30. After loading the NSB baselines, please correct the values of the following parameters for new
sectors according to CIQ. The GS values are commonSrPeriodicity =10 and cellrange=15 but the CIQ
of STX has values higher than GS in STX. The values of these parameters must have the CIQ values.

- cellRange

- commonSrPeriodicity

31. Check the earfcndl/ul and BW according to the latest CIQ by COUNTY (for STX only). The Excel file
name is [STX UMTS & LTE Frequencies by County].xlsx. Latest file is sent to team when available.

32. LOADING LIVE SECTOR CARRIER scripts. Before loading, define the necessary AILG scripts based on
what's existing on the live sectors. Check Pre-KGET.

33. Run the Relation scripts folder. At this point, run EUTRAN and UTRAN folders to define Frequency
relations only. Check the value of the relation frequencies of live sectors from the existing node and
the new sectors in CIQ. Update frequency template as necessary.

34. Make sure to DEACTIVATE ANR function before proceeding to the next step. This is implemented to
avoid relations loading issues.

35. When all your frequency relations are loaded completely, including the new sectors, and your ANR
confirmed deactivated, save a CV and restart the node.

36. Unlock all your sectors for call testing. Make sure the stats are pegging traffic.

Page 8 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

pget . pmVoipQualityUeUlOk
pmxh . pmVoipQualityUeUlOk
lh mp ue print -admitted
hpget . pmRrcConnEstabSucc$|pmRrcConnEstabAtt$
37. While call testing, load the rest of the neighbor cell relations (EUTRANCELL,
ExTernal_EutranCellRelation).

38. For nodes that have AWS3 sectors, load B66 baseline after all cell relations are loaded, soft lock all
sectors and restart the node (only if it’s not past MW, if past MW – get approval from Nexius, for DT
– perform restart if EIM is still open).

39. Perform the neighbor relation cleanup of migrated cells. Use the NBR list provided by RF team.

40. REACTIVATE the ANR function. This is very, very important!

41. Define ULCOMP if new sectors are more than one in each carrier. Update the existing groups as
necessary.

set ENodeBFunction=1,UlCompGroup=1 sectorCarrierRef

ENodeBFunction=1,SectorCarrier=4;ENodeBFunction=1,SectorCarrier=6

cr ENodeBFunction=1,UlCompGroup=3

ENodeBFunction=1,SectorCarrier=7 ENodeBFunction=1,SectorCarrier=9

42. Redefine the existing RETs and new RETs of new sectors if RET sheet is available. If new RETs are
pending, put it on your report that new RETs for new sectors need to be defined by NCC daytime
crew when RET sheet is available.

43. Redefine the external alarms punch list in SAU and the RBS LTE RRU SQUID DC SPD in the radio/s
assigned to it.

44. Capture rillink alarms. Lock down disabled rilinks of new sectors so the FE can log out. Rememnber
to attach the rilink alarm printout to your email report. NCC and tower crew will reference the port
assignment in the printout.

Page 9 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

St sfp

45. For DUS, if the new RILINKs for new sectors are disabled, capture and save the hget rilink= in text file
before you delete the disabled RILINKS. You will need to attach this to your final integration report.
NCC daytime crew will redefine back the rilinks when the fibers are ready.

46. After call testing, make the sure the new sectors are locked/barred/reserved. But before locking
down the new sectors, fetch the VSWRs and RSSIs and include in the report if the values pass or fail
market standards. Current passing values as follows (subject to change):

UL RSSI -114 dBm and VSWR 16dB for LTE all bands

47. Mention in your report if WCS new sectors require filter. Check AFTRCC sheet.

48. Run your macro post checks (logs/CV backups/KGETs/PMRs) and check values against prelogs.
Resolve RRU swaps, VSWR and RSSI issues if any.
Pmr -r 206

49. Please ensure FirstNet PLMNs are defined and MMEs are enabled.
St mme

50. Please make sure TermPointToENBs are unlocked/enabled.

Lst TermPointToENB

51. Run stats and make sure they are normal and have traffic. Notify team of sleeping cells.
pget . pmVoipQualityUeUlOk
pmxh . pmVoipQualityUeUlOk
lh mp ue print -admitted
hpget . pmRrcConnEstabSucc$|pmRrcConnEstabAtt$

52. If there’s no traffic seen on pmVoipQualityUeUlOk (sleeping cells an exception), please soft-lock
sectors, create CV, and restart node (only if it’s not past MW, if past MW – get approval from
Nexius, for DT – perform restart if EIM is still open). Run stats again.

53. When everything is running normal on both nodes; sectors taking traffic and no new alarms, have
your FE log out of NFSD. Include the NFSD ticket in your final report.

Page 10 of 11
Nexius Confidential and Proprietary
 Generic Method of Procedure
LTE L17Q2/L17B 2xDUS to 2xBB5216 (no IDL) + XMU

ROLLBACK PROCEDURE

1. Lock all MOs and shut down the BB5216s.

2. Send the CV backup to your FE.

3. Recreate the DUS nodes in OSS.

4. Unlock all MOs and check stats after 15 minutes.

Pmr -r 106

5. Please ensure FirstNet PLMNs are defined and MMEs are enabled.
St mme

6. Please make sure TermPointToENBs are unlocked/enabled.

Lst TermPointToENB

7. Run stats and make sure they are normal and have traffic. Notify team of sleeping cells,.
pget . pmVoipQualityUeUlOk
pmxh . pmVoipQualityUeUlOk
lh mp ue print -admitted
hpget . pmRrcConnEstabSucc$|pmRrcConnEstabAtt$

8. When everything is running normal on both nodes; sectors taking traffic and no new alarms,
have your FE log out of NFSD. Include the NFSD ticket in your final report.

Page 11 of 11
Nexius Confidential and Proprietary