2_5_Commissioning__Integration_MOP__BBU_(FSIH)__RRU_(FZHJ)_D512241255_Rev8.pdf

8/10/2019 2_5_Commissioning__Integration_MOP__BBU_(FSIH)__RRU_(FZHJ)_D512241255_Rev8.pdf

http://slidepdf.com/reader/full/25commissioningintegrationmopbbufsihrrufzhjd512241255rev8pdf 1/34

Type ofDocument

Guidelines -Number Revision - Number

Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014

Title2.5 Commissioning & Integration MOP - BBU (FSIH) & RRU (FZHJ)

2.5 Commissioning & Integration MOP - BBU (FSIH)& RRU (FZHJ)

Project Name: Sprint 2.5 TD-LTE

Customer Name: SprintDocument No. D512241255Version 0.8

Document Type: Method of Procedure

Document Number: D512241255



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014


Copyright © Nokia Solutions and Networks 2014 SITE ENGINEERING Page 2 (34)D512241255 0.8

Document Revision History

Date Rev. Originator Summary of Change

3/17/2014 1 Pete Mork / Steve Elliston First draft

4/10/14 2 Jason Mackel Language added for SCOP docs and ATP

7/15 3 Pete Mork RL45 Updates

8/15/14 4 James Vu Factory SW to PCD4 steps Updates

08/20/14 5 Fahad Faridi Updates for commissioning and post commissioning

activities.

Included escalation matrix.

8/20/14 6 Jason Mackel Updated ART requirements in section 4 and added ART document in appendix

09/02/14 7 James Vu/ Fahad Faridi Step 11: Added removing IPsec policy during 1st

commissioning

Step 42,48, 49: Include reference for Site

Master sheet for RET angles

Page 31 [#4] : Added details for picture uploadfields in NOLS

9/3/14 8 James Vu/ Fahad Faridi Step 19: Added new route in routing table to

support Traffica

Step 20 - 25: Added steps for configuring RFparameters during 2

nd commissioning.

Step 5 - 8: Added steps to check for CPRIinterface using script.

Sprint Document Approval

Rev. Role Name Signature Date

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document isintended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may beused, reproduced, modified, or transmitted in any form or means without the prior wri tten permission of Nokia Solutions and Networks. The document has been prepared tobe used by professional and properly trained personnel, and the customer assumes full responsibili ty when using it. Nokia Solutions and Networks welcomes customercomments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is”and all liability arising in connection with such hardware or software products shall be defined conclusively in a separate agreement between Nokia Solutions and Networksand the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and freeof material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by thedocument.

Nokia Solutions and Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FORERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR

ANY MONETARY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THATMAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the appli cable laws.

Wave logo is a trademark of Nokia Solutions and Networks Oy. Nokia is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identifi cation purposes only.Copyright © Nokia Solutions and Networks 2014. All rights reserved.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Table of Contents

1. Introduction ......................................................................................................................................... 4

1.1 MOP Contacts .......................................................................................................................... 4

1.2 NSN Project Escalation Contacts ........................................ .......................... ........................... . 4

2. MOP Work Tasks Summary, Responsibilities & Assumptions ................................ ......................... 6

2.1 C&I Pre-requisites .......................... .......................... ........................ ......................... ................ 6

2.2 Commissioning and Integration Tasks .......................................... ......................... .................... 6

2.3 Training & Insurance Requirements ................................ ........................... ........................ ....... 7

3. Work Task Execution .......................................................................................................................... 7

3.1 Required Tool & Test Equipment Check List......................... .......................... ......................... .. 7

3.2 Detailed Work Task Instructions .......................... ......................... .......................... ................... 7

Table 3: NSN project contact list .......................... ......................... ......................... ......................... ..... 26 4. Post C&I checklist and SCOP UPLOAD........... ......................... ........................... ......................... .... 28

5. Appendix a: C&I Troubleshooting Guide ..................................... ........................... ......................... 33

6. Appendix B: ENB LOCK UNLOCK PROCEDURE ............................................... ......................... ..... 33

7. Appendix C: TCP/IP Settings ....................................... .......................... .......................... ................. 33

8. Appendix D: FSIH Port Diagram ........................... ......................... ......................... ......................... . 34

9. Appendix E: ART Overview ........................... ........................ .......................... ......................... ......... 34

10. Appendix F: SITE MASTER SHEET (For RET Angles) ........................... ......................... ................. 34



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



1. INTRODUCTION

This document details the Method of Procedure (MOP), including work tasks and checks required tosuccessfully commission and integrate the NSN TD-LTE BBU (FSIH) and RRUs (FZHJ), collectively knownas eNodeB (eNB).

This document is generated by NSN and shared with Sprint for consultation and Sprint approval. Thisdocument and information contained within shall not be shared or distributed outside of Sprint without NokiaSolutions and Networks prior written consent.

Nokia Solutions & Networks (NSN) shall not be responsible or accountable for any information taken fromthis document which is subsequently used by any other party other than Sprint and NSN directly.

If there are any concerns or changes required to this MOP, this should be raised to the identified contacts inthis document within 2 working days of identifying.

1.1 MOP Contacts

Contact the following when there are any concerns, queries or corrections required to this MOP. In allcorrespondence, reference the MOP document and version # and the applicable page(s).

Table 1: MOP contact list.

Company Name Contact Email

Sprint

Nokia Fahad Faridi [email protected]

Note: Above is for documentation purposes, responses may take 2-5 working days. For training andtechnical support, please contact your relevant support organizations.

1.2 NSN Project Escalation Contacts

If there are issues, problems or concerns that are not being addressed by installation engineers, the Nokiaproject manager should be contacted immediately.

In the unlikely event that the NSN project manager is not addressing issues, problems or concerns, anescalation should be made to one of the regional project directors.

For all technical issues (C&I / ATP failures) Nokia Tier 2 Support should be contacted according tocorresponding markets listed in Table 3: NSN project contact list.

If Nokia Tier 2/OSS Support is not addressing issues, problems or concerns, an escalation should be madeto one of the following Technical project managers.

Table 2: Technical escalation contact list.

Company Name Title Contact Phone

Nokia Fahad Faridi National Technical Manager 847-531-3137

Nokia Frederick Mckinlay RAN Technical Manager 425-205-7818

http://xmpp:[email protected]/

http://xmpp:[email protected]/



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Table 3: NSN project contact list.

Market Nokia Market PMNokia Regional

DirectorNokia Tier 2 Support OSS Support

South West

FloridaJoe Meilinger

Cell: 407-284-7812

Jason Mackel

Cell: 954-214-2960

Siraj Sindhi

Cell: 2149148768

Jeffery San-Luis

ROC Central Number :

972-374-0871

Tampa

Jacksonville

Orlando

NashvilleDave Romagnia

Cell: 615-335-6815

James Vu

Cell: 469 879 3692

West Kentucky

Memphis

Atlanta /

Athens

Carla Pratcher

Cell: 770-337-1686

Miami / West

Palm

Steve Emberlin

Cell: 954-439-5353

Arkansas

Rick Reveley

Cell: 313-408-7350

Steve Holden

Cell: 571-201-2139

Mississippi

Manohar Gotgi

Cell: 214 912 2154

Anthony Chavez/Ramiro Alaniz

ROC Central Number :

972-374-0871

New Orleans

Kansas

Missouri

AlbuquerqueRafe Schenouda

Cell: 972-693-6324

Austin

South Texas

San Antonio

HoustonBrandon Zobisch

Cell: 405-762-3737

DFW Mike Moser

Cell: 972-693-8482West Texas



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



2. MOP WORK TASKS SUMMARY, RESPONSIBILITIES & ASSUMPTIONS

2.1 C&I Pre-requisitesCommissioning and Integration (C&I) of the 2.5 BBU/RRUs shall not commence until all 2.5 hardwarepreparations and installation has been successfully completed, and the site is ready for C & I to commence.

In addition to work Sprint or Ericsson may need to carry out (preparation), there is an NSN installationMethod of Procedure (MoP) for each of the following site types, which should be referenced concerningwhat is required to make the site ready for 2.5 C&I.

1. Ericsson Outdoor cabinet (RBS 6102)

2. Ericsson Indoor cabinet (Sprint shelter site)

3. NSN Outdoor Growth Cabinet (sites that required an expansion cabinet)

The C&I Engineer must have access to the site specific SCF file required for commissioning the site

(Downloaded to PC) before C&I can start.The C&I Engineer must have a copy of the Sprint RFDS.

2.2 Commissioning and Integration Tasks

The tasks indicated in the table below represent the items to be conducted by the BTS engineer/technicianand will result in the commissioning and integration of the site.

# Work task Responsible forcompleting work

Work carriedout during

1Take before photos inside the Ericsson 6102 cabinet clearlydisplaying the left side, right side, and CSR.

NSN D

2 Verify fiber connectivity to ports 1-6 on FSIH NSN D

3 Power on FSIH (BBU), FYGE (GPS box), and FZHJ (RRU) units NSN D

4 Successfully log into the FSIH NSN D

5Commission TRS and wait until all FZHJ are detected and FYGEself survey is completed

NSN D

6 Commission BTS NSN D

7Complete software upgrade of FSIH and FZHJ units using thelatest project approved software release

NSN D

8Move optical cables to the required ports per approved software

release

NSN D

9Commission all ALDs (Antenna Line Device) including RET ACUs(Antenna Control Unit)

NSN D

10 Save a copy of the Site Commissioning File NSN D

11 Save a copy of the Backup Commissioning File NSN D

12Save a copy of the BTS Site Manager Snapshot (Current DataOnly)

NSN D



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



13Call ROC (OSS Support) for pushing eCSFB Parameters before

ATP testingNSN D

14 Execute ATP and upload logs NSN D

M = Maintenance window (service effecting work activity)

D = Done at any time, including during normal business hours or priorto maintenance window

2.3 Training & Insurance Requirements

Suitable training shall be completed and passed (certified to use this MOP) by all C&I engineers executingthis MoP. All persons carrying out works on site shall be suitability insured.

3. WORK TASK EXECUTION

3.1 Required Tool & Test Equipment Check List

# Tool or test equipmentCheck status

(OK, NOK, N/A or note)

1 Laptop with current project approved eNB software and BTS Site Manager

2 Ethernet cable

3 Fiber Cleaner (Cletop or similar)

3.2 Detailed Work Task Instructions

Upon arrival at site, follow these instructions step by step.

Step Step Description Task Status

Arrival On-site

1Call the Sprint NOC at 1-866-400-6040 Options 2 + 6

- Identify site ID & inform NOC of planned activities- Request NOC engineer to identify status of CDMA & LTE equipment for alarms- Record any alarms observed by the NOC engineer- Sign in on the site log book- Locate the hybrid & fiber test results left by the GC (Tower Crew) - Locate the Antenna and RET Serial Number information left by the GC (TowerCrew)



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Hardware Detection

5Copy and unzip AutoScriptForCustomerUsing (0.0.11).7z to your laptop.AutoScriptForCustomerUsing (0.0.11).7z is included in the C&I Document Pack

zip file.

6

Double click file CheckLoadIndication4OBSAI.bat following output will displaywhen script execution will complete

7

Once CheckLoadIndication4OBSAI.bat is completed check the output.txt file.The output.txt file of the script can be found in same folder as the script.

There will be one of two messages in the output.txt file.

OBSAI unit, no need to change!

CPRI unit, change to OBSAI now!

8If the message in the output.txt is CPRI Unit, change to OBSAI now!,

please return the serial and version number to [email protected].

9Make sure that all 6 fiber connections from FZHJs (RRHs) are connected to ports 1to 6 on FSIH (System Module)

mailto:[email protected]






Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



10

Commission TRS by selecting “Commissioning “, select “Template”, unchecked“BTS”, Click “Browse” and go to where the SCF file is st ored, click on the file to

load.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



11

Click Next until you reach IP Security page.

If there is a IP Security Policy listed under Policies, Select Policy and Click DeletePolicy

12

Click “next” to “Send Parameters” page then click “ Send Parameters”

13 Wait for GPS self survey to complete (This step may take around 30 minutes)

14

Check BTS status and RRU status after auto reset. After auto reset the GPS will come up and site goes to synchronized status. Wait forup to 10 min, RFM will be detected but there is fault 23 reported due to

incompatible version.

The BTS status should be integrated.

If all hardware is not detected, do not begin software upgrade orcommissioning. (Refer to Appendix A: C&I Troubleshooting Guide)



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Commissioning

15

From the main menu on the left click on “Commissioning”.

16

Select the following and browse to your site specific SCF (Site Configuration File)

17

Select the SCF file that was created for the site you are commissioning. Verify thesite information on the right side “File Details” is correct and click “open”.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



18

Click Next until you reach IP Security page.If there is a IP Security Policy listed under Policies, Select Policy and Click DeletePolicy



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



19

Click Next until you reach IPv4 Routing page. Add a new route based on following settings:

Destination: Lookup IP address in Table A according to your marketNetmask : 255.255.254.0Gateway: Same as management plane CSR gateway (see figure below)

Market IP Address

South West Florida 10.88.43.0

Tampa 10.88.43.0

Jacksonville 10.88.43.0Orlando 10.88.43.0

Nashville 10.88.43.0

West Kentucky 10.88.43.0

Memphis 10.88.43.0

Atlanta / Athens 10.88.43.0

Miami / West Palm 10.88.43.0

Arkansas 10.88.43.0

Mississippi 10.88.46.0

New Orleans 10.88.46.0

Kansas 10.88.46.0

Missouri 10.88.46.0

Albuquerque 10.88.46.0Austin 10.88.46.0

South Texas 10.88.46.0

San Antonio 10.88.46.0

Houston 10.88.46.0

DFW 10.88.46.0

West Texas 10.88.46.0

Table A



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



20

Click Next until you reach the Cell Resources page.- Check and fill in antennas (FZHJ 1.7.1) data for Alpha Sector (49) as

below:

- Check MIMO settings and select Dynamic Open loop MIMO.

- Check Carrier Power and select 5W as below:

21

Repeat step 15 for Beta sector (50), FZHJ 1.9.1 antennas

22Repeat step 15 for Gamma Sector (51), FZHJ 1.11.1 antennas

23Click Next to reach the LTE Carriers Page enter Frequency Band, Bandwidth,and EARFCN for each sector as below:



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



24

Click Next until you reach the Antenna line management menu and verify that“3GPP/AISG Communication” is enabled on antenna line 1 for each RRH. This will

allow the RET ACU to be detected after the site is commissioned.DC Voltage should be unchecked.

25Click Next until you reach Antenna Line Settings page enter data as below for all

antennas:



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



26

Click Next until following page with all Parameters will be reached

27

Modify following parameters under each LNCEL:

Object Name



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Parameter Name

Select R81xCsfbEnforced

Select false

Select false

28

Click Next until you reach the page that allows you to send parameters and click the“Send Parameters” button.

29 Once commissioning is complete, you will have the option to save a copy of thecommissioning report. Select the “Save As” option and save this report to your PC



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



as part of the site acceptance close out package.

30

Click on the object FYGA and verify GPS is receiving signal from satellites. Verify aminimum of 5 satelites are required with minimum signal strength of 6. If minimumsatellite requirements are not met, check the hardware installation. If hardwareinstallation is correct, check the position of the GPS antenna – and that it has aclear view to the sky. Contact PM if GPS postion is a concern.

Software Upgrade

31

From the main menu click “Software”, then “Update Software to BTS”. Update thesoftware to the project approved software release (LNT4.0_BTSSM_1311_536_03).

Note: Wait 10 minutes after software upgrade is 100% COMPLETE beforeproceeding to next step.

32Verify there is no “Software Incompatibility” alarms post software upgrade. If thisalarm is encountered, first move the fibers according to step 22 and then follow thesteps to clear this alarm.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



33

Verify no other alarms are present before proceeding to the next step.

34

Move optical cables from ports 1,2 ( alpha sector) to 7,8; 3,4 (beta sector) to 9,10and 5,6 ( gamma sector) to 11,12 as shown in following diagram:

NOTE: If you encounter Software incompatibility alarm repeat step 19. A

second software upgrade is required to clear this alarm.

35 After FZHJs are detected, re-commission site using Reconfiguration option.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



36

After commissioning is completed verify that correct ports are being shown in BTSSite Manager after clicking each FZHJ.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



37

Verify “OAM connected” is displayed in lower right corner of BTS Site Manager . IfOAM connected does not display within 10 minutes refer to troubleshooting

appendix.

38

Verify “TRS Commissioned” is displayed in lower right corner of BTS Site Manager

39

Verify “On Air” is displayed in lower right corner of BTS Site Manager

40

Click on each hardware object FSIH, FBIH, and FZHJ and verify working state is“working”. Example FZHJ displayed below.

41

Verify all sectors are “On Air” and the site has no alarms other than ALD (AntennaLine Device). ALD alarms will be resolved in the next steps during RETcommissioning. If you encounter any other alarms do not proceed. Pleaserefer to Appendix A: C&I Troubleshooting Guide for issue resolution details.

RET Commissioning

42

Commission all RET ACU (Antenna Control Units). From the main menu on the leftclick on “Commissioning”.

Note: Electrical tilts for RETs are set in the warehouse before the antennas areshipped to market. If no new RET information is provided please commission RETswith the current settings. If your site is listed in the “Site Master sheet” pleasecommission the RETs and then reset the angles to the new angels

43

Select the following option to reconfigure the BTS. This allows you to commissionthe RETs only. It is highly recommended to save a Backup Commissioning fileby clicking the “Backup Commissioning Files” button before proceeding.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



44

Click “Next” until you reach the RET Settings page. Assign each RET to the

corresponding antenna

45

After each RET has been assigned to its corresponding antenna click “Next” untilyou reach the send parameters page. Click “Send Parameters” (Only Changes isdefault).



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



46

Once the RETs are commissioned they need to be calibrated and the electrical tiltneeds to be set per the Site Information Package. To calibrate each RET ACU, goto the main menu Antenna and click on “RET Settings”

47 Select the RET you wish to calibrate by clicking the check box and then click send.NOTE: You can select all RETs for calibration at the same time.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



48

After the RETs are calibrated you will be able to set the desired electrical down tilt.Double click inside the “Angle” box, enter the desired angle value according to SiteMaster Sheet [APPENDIX F] and then click send.

49

After the RETs are commissioned, calibrated, and electrical tilts are set according tothe Site Master Sheet, verify the eNodeB is alarm free. Example below.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Post Commissioning Activities

50

From the main menu, click on the Snapshot button and save a current snapshot ofthe BTS (Current Data Only option is OK). This will be required for site acceptanceand close out package.

51

Notify OSS Support to initiate eNB Object Creation and eCSFB Parameter Push inNetAct OSS (EMS).

OSS Support numbers are listed in following section of this MOP

1.2 NSN Project Escalation ContactsTable 3: NSN project contact list



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



52

Verify if eCSFB push is successful by confirming that values for following

parameter under each LNCEL object are non zero:

Note:If above parameters are zero wait for 10 minutes and re-check.If they are still zero call OSS support numbers.

53

Proceed to the NSN TD-LTE ATP MOP and perform Site Acceptance testing usingTAPAS.

Important:

ATP will fail if previous step is not performed (eCSFB Parameter push andverification)

54

After ATP completion and before leaving site lock all 3 sectors by changingAdministrative State = Locked, under Commissioning LNCEL parameters.

For more detail see MOP titled Nokia_ENB_Lock_Unlock_MOP – Section 1.2[Ref: Appendix B]

55 Enable DRX by following step 16 and selecting true

56

ENB final state (before leaving site) should be:OAM Connected /Integrated /TRS Commissioned



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



4. POST C&I CHECKLIST AND SCOP UPLOAD

Use this checklist to verify C&I was successfully completed.Table 3: Post checks installation steps.

Step Step Description

Task Statu

Complete [C

Not Complet

[NC]

1

Prior to leaving the Site the ENB engineer will verify the following items have been comlpletedand the status of each the status of all the deliverables has been forwarded to the market PM.

2 Upon completion of the Installtion of the NSN components, as well as the Integration andcommissioning the EnB enginner will collect closeout pictures and upload them to ART. ART isa program that is utilized by Sprint to collect closeout documents and a subscription will berequired to access the system. If you need an account set-up, please contact your marketproject manager;



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Picture size will be a minimum of 1280 x 720. Camera to have 8megapixel capability.

Link to ART:

https://nvart.sprint.com/

Art overview can be found in Appendix (#)






Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Description of Photos to be collected and uploaded to ART

3 Pictures will be labeled, compressed to a zip file and uploaded to the documents folder for thatparticular site. It is expected tat the photos will be uploaded the same day that they taken. Anotification e-mail will be sent to the CPO organization and the market PM.



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



Open site and clickdocumentation



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



4

Choose following options when uploading pictures to Site folder

5Upon leaving the site Call the Sprint NOC at 1-866-400-6040 and informed them you leaving the site.

Load pictures to C&I fo



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014



5. APPENDIX A: C&I TROUBLESHOOTING GUIDE

Sprint_C&I_Troubleshooting_Guide_v2.xls

6. APPENDIX B: ENB LOCK UNLOCK PROCEDURE

Nokia_ENB_Lock_Unlock_MOP_ver2.pdf

7. APPENDIX C: TCP/IP SETTINGS



Type ofDocument


Method ofProcedure

D512241255 0.8

of 34 Date: 9/4/2014


8. APPENDIX D: FSIH PORT DIAGRAM

9. APPENDIX E: ART OVERVIEW

ART Template forOEM ICI CCFA_Draft

10. APPENDIX F: SITE MASTER SHEET (FOR RET ANGLES)

SPRINT-MasterList-2.5GHz.xlsx

2_5_Commissioning__Integration_MOP__BBU_(FSIH)__RRU_(FZHJ)_D512241255_Rev8.pdf

Documents

Transcript of 2_5_Commissioning__Integration_MOP__BBU_(FSIH)__RRU_(FZHJ)_D512241255_Rev8.pdf