6000 Integration Onsite

AT&T Mobility Network

Ericsson UMTS RBS6000 NodeB Field Integration MOP

Mobility Integration Center

Version: 1.1Last Updated: 5/6/2013Risk Assessment #:6568Risk Assessment Score:8

Author Contact Info:Nick [email protected] 214-507-4128

Objective Background: Market request for field integration support.


Table of Contents1. Document History........................................................................................................................... 4

2. Versions.......................................................................................................................................... 4

3. Integrated Solution Approach v1 (ISA v1).......................................................................................4

4. MOP Impact Scope/ General Information.......................................................................................5

4.1 Description................................................................................................................................. 5

4.2 Site Specific Description............................................................................................................5

4.3 Service Impact........................................................................................................................... 5

4.4 Coordination............................................................................................................................... 5

5. Prerequisite/Dependencies/Entrance Criteria of MOP....................................................................6

6. Assumptions................................................................................................................................... 6

7. Material Requirements....................................................................................................................6

7.1 Required Documents.................................................................................................................6

7.2 Tools.......................................................................................................................................... 6

8. Pre Maintenance Check, Precautions, and Preparations................................................................7

8.1 Pre Maintenance Check Tools/System......................................................................................7

8.2 Pre-Maintenance Check Manual (Non-Automated Requirements)............................................7

8.5 MOP Certification Environment..................................................................................................8

8.7 ATS Bulletins............................................................................................................................. 9

8.8 Emergency Contacts..................................................................................................................9

9. Implementation............................................................................................................................. 10

9.1 Preliminary Implementation......................................................................................................10

9.2 Implementation......................................................................................................................... 10

9.3 Test Plan.................................................................................................................................. 10

9.4 Backout Procedure................................................................................................................... 11

9.5 POST Activities........................................................................................................................ 11

9.6 During Maintenance Window...................................................................................................11

9.7 Post Maintenance Check.........................................................................................................11

9.8 Post Maintenance Check (Automated and Non-Automated From Above)...............................11

10. Risk Assessment Score................................................................................................................12

11. Execute MOP clean up if required................................................................................................12

12. End Of Document MOP................................................................................................................12

13. Service Assurance/Monitoring......................................................................................................12

14. Appendix and Tables (IF REQUIRED)..........................................................................................12

AT&T CONFIDENTIAL & PROPRIETARY Page 2 of 63Use pursuant to Company instructions

The use of this MOP without the expressed consent of the AT&T Mobility Integration Center (MIC) is strictly forbidden. The Mobility Integration Center accepts no responsibility for the outcome of any activity consequential of the use of this MOP except by MIC personnel.





1. Document History

Issue Issue Date Author(s) Identification of Changes1.0 04/01/13 Nick Huynh

(nh8299)Initial Draft

1.1 04/24/13 Nick Huynh (nh8299)

Update section 9.2

1.2 05/08/13 Nick Huynh (nh8299)

Update snapshot to latest SW

2. VersionsVersion # Editor Comments

Draft 1.0

Nick Huynh (nh829

9)

Same as Document History and front page less the date

1.3Wayne Spiers

(ws3557)Added Risk Assessment score.

3. Integrated Solution Approach v1 (ISA v1)Version # Editor Comments

Draft 1.0The version and editor of the Implementation Guide (IG) or Deployment Guide (DG)




4. MOP Impact Scope/ General Information

4.1 Description

This procedure provides the field integration method for the Node-b. This MOP is specific to the Ericsson UMTS RBS6000 equipments.

4.2 Site Specific Description

4.3

Service Impact

This is a new turn-up, no impact is expected.

4.4 Coordination

Field will co-ordinate with the MIC for Integration.

5. Prerequisite/Dependencies/Entrance Criteria of MOP

Field Engineer should has the base software and configuration software.

6. Assumptions

List any assumptions for your MOP Field Engineer will load all scripts.

7. Material Requirements

7.1 Required Documents

Document Location

Site OAM script OAM Wizard

Site External Hardware script Site Equipment Wizard

SiteComplete script Run Command tool



Originator Date Time

Nod eCLLI(s)

Description Enter short description of what activity will take place.


7.2 Tools

Tools

Tool Description Quantity

WinFiol, PuTTy, HyperTerminal

Connect a cable from your serial or USB port on your PC to the rbs serial console port (LMT A)

1

LAN Connect a Ethernet cable from your PC to the rbs local Ethernet port (LMT B).

1

FTP ftp client application displaying your PC’s hard drive highlight the /d and /c2 folders

1

FTP ftpserver application navigate to the rbs upgrade software package folder where it is only displaying the name of the upgrade package

1

Element Manager Ericsson Element Manger GUI 1

8. Pre Maintenance Check, Precautions, and Preparations

8.1 Pre Maintenance Check Tools/System

Procedure -1 Pre Maintenance Check Tools.System

StepAction Results/Descriptions Chk

1. Site is installed and powered-up.

2. Engineer has Ericsson Base software.

3.Engineer has configuration scripts.

4.

5.

8.2 Pre-Maintenance Check Manual (Non-Automated Requirements)

Procedure -2 Preliminary

StepAction Results/Descriptions Chk

1. NA- This is a new cabinet turn-up.

2.

8.3 ATS Bulletins




Procedure -3 ATS Bulletins

Step Action Results/Descriptions Time Line

1.Access the ATS Bulletin site at the following URL: ATS Bulletin

2. Click on the List/Search button (At the top of page)

3. Click on the -Search Menu>

4.Determine a Key word associated with the activity that you are performing and type it in to the Keyword: (Hint)field

You may have to try several key words

5. Click on the Submit Query button

6.

Review each search result bulletin by clicking on the bulletin number to determine any are of the bulletins have warnings/actions associated with the activity that you are implementing

7.List if an associated bulletin is found; list it in the following table. If no associated bulletin is found place NA in the following table

Bulletin Number Description Engineer Check

ATS2012-0278BulletinEricsson-RNC, Provisioning, 12-05-2012

Rx Diversity Utilization in DAS Sites

ATS2012-0274BulletinEricsson-RNC, Hardware, 11-29-2012

CBU R5 is recommended for high capacity RBS3000 sites

ATS2012-0269BulletinEricsson-RNC, Software, 11-12-2012

High RSSI values if TMA gain is incorrectly defined

ATS2012-0268

BulletinEricsson-RNC, Upgrade, 11-05-2012 RNC W12B: During re-homes on W12B, sites are being allocated to one single module

ATS2012-0247

BulletinEricsson-RNC, Software, 10-31-2012 Secure Shell (SSH) Application Restart

ATS2012-0244

BulletinEricsson-LTE-RAN, Hardware, 10-25-2012 Put ON HOLD of any SOURCEPHOTONICS SFP usage in LTE deployment

ATS2012-0239

BulletinEricsson-RNC, Features, 10-17-2012 Prevention of negative and hanging counters in UEH

ATS2012-0235BulletinEricsson-RNC, Features, 10-15-2012

frequent DC SP crashes due to Measurement result recording for WCDMA (MRR-W)

ATS2012-0234.1

BulletinEricsson-LTE-RAN, Software, 10-15-2012 Ericsson eNode-B CV Management

ATS2012-0220

BulletinEricsson-RNC, Hardware, 10-04-2012 SW Upgrade to W12B IP1 fails on Dual DUW nodes configured with external RX branch sectors



http://atspub.nssw.att.com/bulletins/index.html


ATS2012-0219

BulletinEricsson-RNC, Provisioning, 10-03-2012 Slogan: Attribute lowCurrentSupervision should not be changed on W12B IP1

ATS2012-0201

BulletinEricsson-RNC, Other, 09-12-2012 RNC3820 R2 with SPB4, RNC Usage of certain ping commands causes KPI degredation

ATS2012-0096 BulletinEricsson-RNC, Software, 04-29-2012 Ericsson RNC and Node-B CV Management

ATS2012-0061 BulletinEricsson-RNC, Software, 03-22-2012 Sector might not come up after NodeB cold restart

ATS2012-0060 BulletinEricsson-RNC, Transport, 03-16-2012 Increased AAL2 failures on ET-MF4/2 (version 2)

ATS2012-0047 BulletinEricsson-LTE-RAN, Environmental, 02-27-2012 Maintenance 2012-02-22.09:LTE RAN RBS: Purcell Cabinet Operating Temperature

ATS2012-0017 BulletinEricsson-LTE-RAN, Other, 02-01-2012 LTE RAN - Mandatory Actions Required Prior to Node Restart

ATS2011-0281.1 BulletinEricsson-RNC, Software, 06-11-2012 Exercise Caution When Locking IubLink MO from Node Status Analyzer

ATS2011-0247 Mobility RAN BulletinEricsson-RNC, Software, 11-17-2011Ericsson Node-B - Sector May Not Recover After Cold Restart

ATS2011-0224 Mobility RAN BulletinEricsson-RNC, Software, 10-20-2011Degraded VSWR Measurement for 1900MHz 2nd Carrier

ATS2011-0152Mobility RAN BulletinEricsson-RNC, Provisioning, 07-07-2011High 2011-06-20.02:WCDMA RBS: VSWR Antenna supervision formula and guiding values

ATS2010-0212.1 Mobility RAN BulletinEricsson-RNC, Translations, 08-29-2010WcdmaCarriers & UARFCNs on the Ericsson RAN

ATS2009-0170.2 Mobility RAN BulletinEricsson-RNC, Hardware, 10-01-2009Node Restart Needed When Adding or upgrading any hardware

ATS2009-0059 Mobility RAN BulletinEricsson-RNC, Software, 02-11-2009Remove Old CV's Preventing Automatic CV Backup Creation

8.4Emergency Contacts

The following emergency contact numbers are to be used in the event provisioning support is required.

In the event a service interruption is encountered, the AT&T MIC Engineers will:

1. Cease all work immediately.2. Notify the AT&T MNRC



The stop sign indicate a critical step that may cause and ourtage.


Organization Contact Name Contact Number

MNRC 1-800-638-2822 option 4

Mobility Integration Center (MIC) 888-864-3998

8.5 Precautions

Ask Yourself

Place initials and date to acknowledge that you have read and understand

Step E911 Ask Yourself Descriptions Check

1. Do I know how this work could impact 911/e911? See note 12. Do I know what 911/e911 phase is required? See note 2

3.Have I identified potential risks to 911/e911 and taken all measures to minimize them?

See note 3

4. Does this work affect 15+ sites? See note 4

5.Can I prevent or control service interruptions to 911/e911?

See note 5

6. Is this the right time to do the work? See note 6

7.Is the individual performing the work trained and qualified to do this work?

See note 7

8.Are MOPs and supporting documents current and error free?

See note 8

9. Does the MOP include a 911/e911 test plan? See note 8

StepGeneral Ask Yourself Descriptions Check

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? See note 1

3.Have I identified and notified everybody – customers and internal groups – who will be directly affected by this work?

See note 2

4. Can I prevent or control service interruption? See note 35. Is this the right time to do this work? See note 46. Am I trained and qualified to do this work? See note 5

7.Are the work orders, MOPs, and supporting documentation current and error free?

See note 6



https://mobility-consumer.web.att.com/sites/MPC/MPC%20SME/SME%20SUPPOrt%20Documents/MPC%20Smart%20MOP_Template%202011_v1.0.doc#Notes
















8.Do I have everything I need to quickly and safely restore service if something goes wrong?

See note 7

9. Have I walked through the procedure? See note 8

10.Have I made sure the procedure includes proper closure including obtaining clearance and release for the appropriate work center?

Ask Yourself Notes

8.6 MOP Certifcation Environment

9. Implementation

9.1 Preliminary Implementation Step

PRE-CHECK OF THE SYSTEM

Step Step DescriptionResponsible

MIC FECompleted

initialPre-Check of the System .

NOTE: The Pre-Check can be performed by either AT&T personnel or by a Contractor. This step is to verify the system status before starting any kind of work.

NOTE: When working in LIVE POWER cabinets the pre-check must be performed for all in-service nodes which are connected to the common power system.

THE NODES MUST BE FAULT FREE FOR AT LEAST 24 HOURS.1. Contents of MOP and referenced documents reviewed and available. X X

2. If applicable permission for local site access is granted. X X

3.Verify all necessary remote access to all nodes including OSS access is confirmed.

X X

4. All involved nodes are verified working normally. X X

5. Verify / identify with customer the target nodes. X X

6.

If applicable, market test calls are to be completed

Common Call Types to be tested are: UE Originate and UE Terminate

X X






9.1 SITE SPECIFIC STEP-BY-STEP


MIC FECompleted

initialNOTE: If you have any problems with any steps of this MOP, DO NOT PROCEED, Contact your PM immediately.

The Steps below need to be executed in the specified sequence on all impacted nodes.

X

----NodeB Integration

---- ----------- ----------

1.Start work.

NOTE: If any In-Service Performance (ISP) problems are encountered while working follow the escalation procedure in section 8.4.

X X

2.

Plug the transmission cables into the appropriate connection points between the NodeB and the external equipment (Site Router).

Verify RU cables are plugged into the appropriate connection points in the DUW.

TN A Ethernet - Site Router S1 CP/UP/OAM/X2

OR

TN B Fiber - Site Router S1 CP/UP/OAM/X2

RI A - Sector A, Radio 1 RU/RRU

RI D - Sector A, Radio 2 RU/RRU

RI B - Sector B, Radio 1 RU/RRU

RI E - Sector B, Radio 2 RU/RRU

RI C - Sector C, Radio 1 RU/RRU

RI F - Sector C, Radio 2 RU/RRU

The below cable is connected only if using GPS forsynchronization. Other option is NTP for sync which does notrequire a cable

Note: DUW port mapping varies site to site based on the DBB/RBB used. Follow the external hardware script/RFDS/market specific instructions.

Note: The RI ports A-F may require a SFP adaptor. Depending on the type of radio this could be an electrical SFP (built into cable) or optical SFP (supplied separate).

X





MIC FECompleted

initial

3.

Establish O&M Connection to the NodeB

Establish an O&M connection to the NodeB following the instructions below. Also see DUW connections diagram.

X

4.

Connecting the Client to an RBS through the DUW

The client must be connected to the Site LAN interface.

The Site LAN interface in the DUW occupies port LMT-B and consists of an

RJ-45 connector.

X

5.Connect one end of the Ethernet cable to the Ethernet port on the client.

Set the IP address of the client to 169.254.1.2 netmask 255.255.254.0 gateway 169.254.1.1.

X





MIC FECompleted

initial

6.

Connect the other end of the Ethernet cable to the Site LAN interface (LMT B) on the DU as seen in diagram.

Note: If a Site LAN cable is connected, remove the cable and connect

the client to the same interface.

X

7.

Check the IP Configuration and the RBS Connection

Using the LAN connection LMTB (RJ 45) open the Windows command prompt (from start menu)

Type ping default IP address (169.254.1.1) at the prompt, there will be 4 replies from the node.

NOTE: This step ensures Ethernet communication with the RBS.

X

8.

Download Element Manager from the RBS if needed. Refer to Appendix A for instruction.

Open Internet Browser.

Go to: http://<node_ip_address>/em/index.html

Download and run the installer. Follow the on-screen installation instructions.

X





MIC FECompleted

initial

9. Open RBS Element Manager application for NodeB on your PC.

NOTE: This will be under Start EM Applications RBS Element Manager.X

10.

From the RBS Element Manager application log into the rbs by entering the following IP address in the “Address” field in the bottom, left corner:

169.254.1.1

Click on “Connect” button at the bottom of the window.

X





MIC FECompleted

initial

11.

View current software level of NodeB.

Note: If you cannot log into the NodeB then there is no basic software package, skip to step 16.

1. From the Element Manager Window click on the Views drop down menu and select “Software”.

2. Click on the “UP” tab on the right side.

3. In the column “Active” look for “yes”. This will be the active software package.

X

12.

From the Element Manager window click on the Views drop down menu and select “Containment (MOM based)”.

X





MIC FECompleted

initial

13.

From the MO Tree, SelectCabinet=1.

Click on MO Properties tab on the right side.

Click on “+” sign next toproductDataand expand the window so that all field is visible.

PATH:<ManagedElement=1,Equipment=1,Cabinet=1>

X

14.

Capture the screen and save it to <sitename>.jpg file.

X





MIC FECompleted

initial

15. Close the RBS Element Manager application. X

16.

Establish a serial connection between the RBS and local client.

To setup a serial connection, perform the following steps:

a. Remove any cables connected to ports LMT A, LMT B and TN A on the DUW.

b. Using the D-sub 9 to RJ-45 cable, connect the RJ-45 end to the LMT A port on the DUW and the other end to the serial port on the client.

c. Use any software for terminal emulation on the PC, ex. Putty. Apply the following parameters to the respective communication port:

NOTE: Establish the serial connection to the DUW. Once the $ prompt appears, connection is established.

X

17.

Verify the available SW on the RBS.

$cv ls

The minimum SW must be W11A.X





MIC FECompleted

initial

18.

In the HyperTerminal window, type reload -- then press enter to put the RBS into the Backup mode.

X

19.

Type volsto list all drives.

Type mount_c2to mount the hidden C2 drive.

Type formathd /c2 then press enter to format the C drive.

The RBS replies with the information as shown below, enter“y”to confirm

X





MIC FECompleted

initial

20.

Type formathd /d then press enter to format the D drive.

The RBS replies with the information as shown below, enter“y”to confirm

X

21.

Type reload -- then press enterto put the RBS into the Backup mode again.

X





MIC FECompleted

initial

22.

Set the IP Configuration by typing the following command:

ifconfig le0 169.254.1.1 netmask 255.255.254.0

Note: Use Default IP address <169.254.1.1>unless provide a different IP address, cannot be same as lh0 IP address for OaM access.

X

23.

Type ifconfig to verify the RBS IP configuration.

X

24.If needed, set the default gateway address in the node by command:

route add default <gateway>.X





MIC FECompleted

initial

25.

Type reload to activate the RBS password and IP configuration.

NOTE: Save the product data for use later in the Cabinet Equipment Wizard, step 63 & 64.

X

26.

Type reload -- to put the RBS into the Backup mode.

X

27. Stop window firewall if it is running on the laptop. X

28. Launch WS_FTP through Ethernet connection to DUW LMTB X





MIC FECompleted

initial

29.

In the Session Properties below enter:

RBS name

RBS IP address

Use pull down menu find Auto detect

Enter User ID & Password

Click OK to connect

X

30.

Set the left pan (local) to the basic package being loaded (>CXP9014349%4_R6B01 W11B) so the C2 and D drives are visible.

Set the rightpan (remote) to root folder “/” so the C2 and D drives are visible.

Note: Confirm with PM/MIC for the correct Basic Package before proceeding.

X





MIC FECompleted

initial

31.

1. 1. Select the C2 and D drives in the left pan (local).2. 2. Check Binary transfer mode button.3. 3. Press the right arrow to transfer to the RBS.

X

32. Wait for the upload to complete successfully (15-30 minutes) X

33.

Establish a serial connection between the RBS and local client.

At the command prompt “$”, enterreloadto put the RBS in active mode.

NOTE: Wait until HyperTerm displays “security properties not found – using defaults” in the window.

X

34.

Press enter and login

Username rbs thenpress enter

Password rbs then press enter

X



1. Select c2 andd drives

2. Check Binary transfer mod

3. Press the right arrow to transfer



MIC FECompleted

initial

35.

Set clock

Type setclock YYYY-MM-DD HH:MM:SS then press enter

ex: setclock 2013-13-24 10:10:00 <enter>

Enter: readclock

To confirm your time

X

36.

Type reload and wait for it to complete (up to 4 minutes). When completion response “Login Server Ready” appears.

X

37.

Press enter and login

Username rbs thenpress enter

Password rbs then press enter

X





MIC FECompleted

initial

38.

Use the following steps to set the RBS password.

Type passwd then press enter

Type rbs (won’t show on screen) then press enter

Type rbs (won’t show on screen) then press enter

NOTE: RBS password should be – ‘rbs’ + last 4 digits of RBS ID – unless otherwise notified by market.

For example – rbs1234 for a site ABC1234

X

39.

If an upgrade is NOT required, skip to step 59. Please contact your PM/MIC support for instruction.

Note: It is important to follow a known working upgrade path to reach the desired software level. Multiple software installs may be required. Request support if the upgrade path or required software level on the node is unknown.

X

40.

From the window pane displaying your PC’s hard drive in the FTP client application navigate to the rbs upgrade software package folder where it is only displaying the name of the upgrade package.

For Ex: After unzip, if the upgrade package is named CXP9018350_R10A. Navigate to the folder containing CXP9018350_R10A

X

41. From the window pane displaying the rbs hard drive in the ftpclient application navigate to /c/tmp.

X





MIC FECompleted

initial

42.

From the window pane in the FTP client application displaying your PC’s hard drive highlight the upgrade folder name.

For ex: CXP9018350_R10A. Drag and drop the folder into an open area in the window pane displaying the rbs folders /c/tmp.

DO NOT place these folders on top of any existing folders.

This will start copying the software files to the rbs.

Depending on the ftp client application this will take between 5 to 20 minutes.

X

43. Connect a crossed Ethernet cable from your PC to the NodeB local Ethernet port (LMT B).

X

44.

From the RBS Element Manager application log into the rbs by entering the following IP address in the “Address” field in the bottom, left corner:

169.254.1.1

Click on “Connect” button at the bottom of the window.





MIC FECompleted

initial

45.

After Element Manager launches, use the drop-down list to go to the Software view.

In MO Tree click on Manged element 1

In right window click on UP tab.

Right click the Upgrade Package.

Click Create

.

46.

If an upgrade is NOT required, skip to step 59, Please contact your PM/MIC support for instruction.

Note: It is important to follow a known working upgrade path to reach the desired software level. Multiple software installs may be required. Request support if the upgrade path or required software level on the node is unknown.

X





MIC FECompleted

initial

47.

In the upFilePathOnFtpServer field, enter the complete file path with the file name of the control file (XML file) that identifies the Upgrade Package.

For example:

/c/tmp/CXP9018350_R10A%1/CXP9018350_R10A%1.xml

NOTE: Ensure the correct directory name and the path name is entered

Once the name is entered the “Create Package” button is enabled. X

48.

Click Create Package. The Upgrade Control File (UCF) path is verified, and the FTP server is contacted. When the UCF (XML file) has been found in the FTP server, it is downloaded to the node. No other files are downloaded at this point.

Note: Wait for the package to be created

X

49.

Click Install Package when it highlights





MIC FECompleted

initial

50.

Click Full Install and wait for the installation to complete successfully

51.

After the installation completes successfully click Upgrade Node.

52.

Click Hard Upgrade.

53.

Monitor the upgrade progress with the window maximized and wait for successful completion

Note: The system will reset twice, connection to EMAS will be lost, once restarts complete EMAS should re-connect, if not proceed with next step, if EMAS re-connects automatically skip next sep.





MIC FECompleted

initial

54.

Reconnect to the RBS with Element Manager

55.

Open Software view.

56.

Select Upgrade Tab.

Right click on upgrade package and select properties





MIC FECompleted

initial

57.

From Properties window select Confirm Upgrade and click Yes

58.

Click yes on pop up to make the upgrade permanent.

NOTE: You may have to change views and go back to confirm the upgrade.

Upgrade is complete. Click Yes





MIC FECompleted

initial

59.

Run the Cabinet Equipment Configuration tool

From the main EMAS window, select Tools and then Cabinet Equipment Configuration. The Cabinet Equipment Configuration window will appear. Follow the instructions in the tool to configure the node’s hardware.

For RBS 6000 you need to specify the hardware below:

Rbs type

Number of sectors

Radio building block & CPRI line rate

Number of power supply available on site

Number of PDU available on site

Select the battery back up only in case if it exist on site

Climate system put it standard

For RBS 6000, it is mandatory to configure the Cabinet product data otherwise you will have an alarm Enclosure product data mismatch

This data is available on a stickers label inside the cabinet and it is called enclosure

Note: In case if we don’t have a battery backup, disconnect the control cable of the BFU, otherwise you will have the alarm "NumberOfHwEntitiesMismatch".

X





MIC FECompletedinitial

Use the following steps to configure the cabinet and equipment. X

60.

In Element Manager click Tools and select Cabinet Equipment Configuration..

Read the information on the page, and check that the preconditions are met, and click Next

X




Step Step Description

Responsible


61.

Cabinet Equipment Configuration

DO NOTcheck “Use Configuration file” box.

Click “Next”. The system will auto-detect the cabinet equipment.

X




62.

The system will auto-detect the cabinet equipment. Wait for successful completion and click NEXT.

X




63.

Enter cabinet product information retrieved from cabinet or subrack, for RBS 6601 subrack skip to step 64.

For 6102, 6101, 6202 an 6201continue.

Retrieve cabinet label on frame front left side of lower frame corner near door hinge.

Enter Radio Building block for each sector, “RBB12_1A”

Enter Line Rate, “Ex2”

Click “Next”

Then skip to step 65RBS 6102, 6101, 6201, 6202

Note: RBB and Line rate can be retrieved from information supplied by PM/MIC

X




64.

Enter cabinet product information retrieved from RBS cabinet label on top of subrack near back.

Click NEXT.

RBS 6301 and 6601

NOTE: product data should NOT contain any blank space. The product data can also be acquired by the “reload” command in step 25. Example below:




65.

For cabinets 6102, 6101, 6201 AC or +24VDC enter the number of PSUs and click next

For 6601, 6202 or any -48VDC equipment cabinets leave blank and Click Next.

X




66.

Click Next.

X




67.

Confirmthe Default IP address “169.254.1.1” and Subnet mask “255.255.254.0”

Click “Next”.

X




68.

Click Finish

Click Yeson the Pop up window to confirm

Verify successful completion third Pop up window.

X





Responsible


69.

To finish the configuration, do the following:

1. Check that the displayed settings are correct.

2. To edit the settings, click Previous to go backwards in the wizard and modify the appropriate options.

3. When all settings are correct, click Finish to start the installation of the configuration.

Note:

At the beginning of the installation a "Cancel CV" is automatically created. This CV reflects the state of the node prior to the start of the wizard. If you click Cancel during the installation, the configuration is interrupted, and the node is restarted using the Cancel CV. If something goes wrong during the installation, you can select whether to restart the node using the Cancel CV or not.

Note:

At the end of a successful installation, a new CV is automatically created.

4. In some cases, for example if the IP address was changed, a dialog box will be displayed, stating that it is necessary to restart the RBS (using the new CV) to activate the settings.

Note:

During restart, the connection to the RBS is lost. Please wait for the RBS connection restored. And Click Continue.

X





Responsible


70.

Example of Restart Requirement Message

X

Use the following steps to run the O&M Access script. X

71.

Run the O&M Access Configuration tool

From the main EMAS window, select Tools and then O&M Access Configuration tool. The O&M Access Configuration window will appear. Click next.

On the second screen, click the option to “Use configuration file”. Then click on the browse button and go to the location of the <Utrancell>_OAM_Access.xml file for the node, on the thin client. Select it and verify that the path appears in the text area to the left of the browse button

Next click on the radio button for “Automatic (No Wizard)” and then click on next.

The tool will then proceed to configure the O&M settings for the node. On the last screen before committing the changes, instructions will be available to indicate the new IP address of the node and how to regain access to the node once the changes are made.

Take note of the instructions and then proceed to commit the changes. Implement the required changes on the thin client, and then proceed to re-establish a connection to the node on its new IP address.

Note:in order to access the site again via moshell after you loaded the O&M scripts you need to Set the IP address of the client to RBS_IP_ADDR+1 with the same subnet as the RBS, since the O&M changed the default IP address that was used in the DUW

X





Responsible


72.

Restart Element Manager.

Click Tools and select OAM Access.

X

73.

Click Next

X





Responsible


74.

OaM access Configuration File Input Page

Check“Use Configuration File”

Check “Automatic (No Wizard)”

Click “Browse”.

X





Responsible


75.

Navigate Client computer and select the xxxx_OAM_Access.xml file and click Open.

X

76.

Verify that the the correct OAM script was selected.

Click “Next”.

X





Responsible


77.

The wizard now downloads the current configuration data from the RBS.

When the download is complete, the Current Configurationpage displays a message stating that the configuration data is successfully loaded.

If the download fails, the wizard displays an error message.

Click Next.

NOTE: If the wizard displays an error message, take a snapshot of the error and contact your MIC support.

X





Responsible


78.

Display shows theChosen RBS Configuration page, which summarizes the settings you have specified for the configuration.

Click “Finish”to start the installation.

On the popup window. Click OK to confirm.

X





Responsible


79.

The Current Action page is displayed.

If the IP address to the RBS is changed during the O&M Access Configuration phase, the connection is temporarily lost. When a message about lost connection is displayed, wait for the connection to be restored automatically. If you click Close All, the progress window is closed and the configuration report is not displayed.

X

80.Wait until the following message is displayed in the Result box:

“Configuration Completed Successfully”X

81. Click OK. The RBS EM will be closed immediately. X

82. Restart the RBS EM. X





Responsible


83.

In the RBS EM View selector, select “Software”.

Click on “Managed Element 1”

Click the “CV”tab.

Verify that a Configuration Version (CV) is automatically created with the nameOAM_....

X

84.

Verifying Network Synchronization StatusIn the RBS EM View selector, select ATM.

Select the Synchronization object and verify that nodeSystemClock is in

LOCKED_MODE mode.

X




85.

Verify IP connectivity In the RBS EM View selector, select IP. Select IpOam=1 MO. Select MO Properties tab. Select Actions tab. From the Actions memu, select ping action.

86.

Enter the OSS IP address <10.175.144.4> in the host field. Click Execute. Verify the Resultreturns with an aliveresponse.

NOTE: for CDNB integration, please inform your MIC support of the ping status and wait for further instruction.





Responsible


Configuring External Hardware X

87.In the RBS EM, from the Tools menu, clickSite Equipment

Configuration... to start the Site Equipment Configuration wizard. X

88.

In thePreconditions page, which displays basic information about the wizard, clickNext.

X





Responsible


89.

In theFile Input page, select theUse configuration file check box. Select Automatic (No Wazard). ClickBrowse to find the location of the configuration files on the Client,

select<nodename>_RBS_ExtHardward.xml, and then clickOpen.

X





Responsible


90.

The current configuration data from the RBS is now downloaded. When the download is complete, theCurrent Configuration page displays a message stating that the configuration data is successfully loaded.

If the download fails, an error message will be displayed.

ClickNext.

X




91.

TheChosen RBS Configuration page will now be displayed.

Click Finish to start installation and display the Current Action page.

X





Responsible


92.

Wait until the following message is displayed in the Result dialog box:

Configuration Completed Successfully

Click OK.

X

93.

In the RBS EMView selector, selectSoftware.

Click theCV tab.

Verify that a CV is automatically created with the nameSITE_....

X





Responsible


Verifying the LED Status X

94.

This activity verifies all units are working properly by verifying the Light Emitting Diode (LED) status.

Verify that:

There are no red LED indicators for any unit.

All units have a green LED indicator steady on.

All units have a yellow LED indicator flashing or off.

For more information on the meaning of LED indicators, seeInterpreting Optical Indicators.

X

Verifying the RbsLocalCell X

95.

This activity verifies the local RBS cell connection.

In the RBS EM View selector, select Radio Network.

Verify that all RbsLocalCell have the operational state Enabled.

X





Responsible


Completing the Integration X

96.

Run the Site Complete script

From the main EMAS window, select tools and then Run Command File from the menu options. Once the Run Command File window appears, ensure File location: is selected to be client. Then click on Browse and find the file <Utrancell>_Site_Complete.mo. Enable (check) the Halt on Errors and Verbose Logging check boxes. Then click on Start. The script file will run. View the Logging: window to ensure no errors were reported. If errors are encountered, troubleshoot on site, or forward the issue to the scripting team. See the screen capture below for additional details.

X





Responsible


Concluding Routines X

97. InformMIC support that the On-Site Integration is completed. X




9.3 POST CHECK OF THE SYSTEM


MIC FECompleted

initial

1. Check Alarm Status. X X

2. Check For hardware Faults. EX: Red LEDS X

3. Save any Logfiles and screen capture for your reference. X X

4.

Before you leave the site, ensure that the following actions have been performed:

Close the RBS EM.

• Tidy the site and leave it in the same condition as you found it.

• Update the site documentation, if there have been any changes during the integration.

• Give the updated site documentation to the person responsible for the site.

• Lock all the doors to the site.

X

9.4 FALL BACK


MIC FECompleted

initialNot Applicable. If integration failed a Scratch load is needed to re-integrate the site.

X X

9.5 Exit CRITERIA


MIC FE Time

1 Post check completed satisfactorily (Node / Network is in as good or better performance state than before the activity started.

X

2Activity completion report (along with the status / KPIs from pre and post checks) has been sent to all concerned personnel from AT&T and the customer.

X

3 All logs from the activity have been stored in the designated AT&T Shared Drive.

X




10. Risk Assessment Score

Risk Factor:

11. Execute MOP clean up if required[Specify timeframe to execute and identify whether work to be completed within maintenance window or some later date.]

12. End Of Document MOP

13. Service Assurance/Monitoring




14.Appendix and Tables (IF REQUIRED)

1.1 APPENDIX A

Step How to Download and Install RBS Element Manager

Download and Install Element Manager and Integrate RBS for Windows

1. Must have Java 1.5 or higher installed on PC.

2. Connect a crossed Ethernet cable from your PC to the eNodeB local Ethernet port (LMT B).

3.Set the IP address of your PC in network settings to 169.254.1.2, netmask to 255.255.0.0, and default router to 169.254.1.1.

4.Open Internet Explorer (IE). Type in the following url address:http://169.254.1.1/em/index.html

5. Click on Windows Download, then click Run. Follow the install instructions as they are displayed.



http://169.254.1.1/em/index.html


1.2 APPENDIX B

Note: Please confirm with your PM if 911 call is to be performed.

Step Call Test Scenarios

1

Mobile Originating (MO) to Circuit Switch (SC)

Verify via the UE that the scrambling code matches the scrambling for the sector under test

From the UE place a call to a landline number

Once connection is established verify both way audio

Release the call

6.

Mobile Terminating (MT) from Circuit Switch (SC)


Receive a call from a landline number on the UE


Release the call

7.

Mobile to Mobile

Verify via the UE that the scrambling code matches the scrambling f for the sector under test

From the UE place a call to a mobile subscriber


Release the call

8.

411 Call


From the UE dial 411

Confirm call is connected to information

Release the call

9.

611 Call

Verify via the UE that the scrambling code matches the scrambling f for the sector under test

From the UE dial 611

Confirm call is connected to AT&T Customer Care

Release the call

10.

SMS Call


From the UE send a SMS message to a mobile subscriber and request a reply conformation that the SMS message was received

Receive conformation SMS from mobile subscriber

11.

Combination RAB Packet Switch (PS) plus Circuit Switch (CS) Call


From UE initiate a MO call

Once call is established with UE browse to a web site

Confirm that CS call is still established while web browsing

Release the call

12.

HS Data Call

Note: Either a mobile supporting HSPA or Data Card Required


With UE or PC (if data card used) browse to: http://www.speakeasy.net/speedtest/ (or similar);

select the nearest cist to begin the test

Take and save a screen shoot capturing the test results



http://www.speakeasy.net/speedtest/