Ericsson UMTS RBS6000 NodeB Integration

(1)

Ericsson UMTS RBS6000

NodeB Field Integration MOP

Mobility Integration Center

Nick Huynh

NH8299@att.com

Cell 214-507-4128

Author Contact Info:

Objective Background:

Market request for field integration

support.

(2)

1. 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

(3)

Issue

Issue Date

Author(s)

Identification of Changes

1.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

Versions

Version #

Editor

Comments

Draft 1.0

Nick

Huynh

(nh829

9)

Same as Document History and front page less the date

1.3 Wayne

Spiers

(ws3557)

Added Risk Assessment score.

Integrated Solution Approach v1 (ISA v1)

Version #

Editor

Comments

(4)

Description



This procedure provides the field integration method for the Node-b.



This MOP is specific to the Ericsson UMTS RBS6000 equipments.

Site Specific Description

Service Impact



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

Coordination



Field will co-ordinate with the MIC for Integration.

1. Prerequisite/Dependencies/Entrance Criteria of MOP



Field Engineer should has the base software and configuration software.

Assumptions

List any assumptions for your MOP



Field Engineer will load all scripts.

Material Requirements

Required Documents

Document

Location

Originator

Date

Time

Nod eCLLI(s)

(5)

Tool

Description

Quantit

y

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

ftp server 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 Pre Maintenance Check, Precautions, and Preparations

Pre Maintenance Check Tools/System

Procedure -1 Pre Maintenance Check Tools.System

Step

Action

Results/Descriptions

Chk

1. Site is installed and powered-up.

2. Engineer has Ericsson Base software.

3. Engineer has configuration scripts.

4.

5. Pre-Maintenance Check Manual (Non-Automated Requirements)

(6)

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-0278

Bulletin Ericsson-RNC, Provisioning, 12-05-2012

Rx Diversity Utilization in DAS Sites

ATS2012-0274

Bulletin Ericsson-RNC, Hardware, 11-29-2012

CBU R5 is recommended for high capacity RBS3000 sites

ATS2012-0269

Bulletin Ericsson-RNC, Software, 11-12-2012

High RSSI values if TMA gain is incorrectly defined

ATS2012-0268

Bulletin Ericsson-RNC, Upgrade, 11-05-2012

RNC W12B: During re-homes on W12B, sites are being allocated to one single module

ATS2012-0247

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

ATS2012-0244

Bulletin Ericsson-LTE-RAN, Hardware, 10-25-2012

Put ON HOLD of any SOURCEPHOTONICS SFP usage in LTE deployment

(7)

ATS2012-0201

RNC3820 R2 with SPB4, RNC Usage of certain ping commands causes KPI degredation

ATS2012-0096

Ericsson RNC and Node-B CV Management

ATS2012-0061

Sector might not come up after NodeB cold restart

ATS2012-0060

Bulletin Ericsson-RNC, Transport, 03-16-2012

Increased AAL2 failures on ET-MF4/2 (version 2)

ATS2012-0047

Bulletin Ericsson-LTE-RAN, Environmental, 02-27-2012

Maintenance 2012-02-22.09:LTE RAN RBS: Purcell Cabinet Operating Temperature

ATS2012-0017

Bulletin Ericsson-LTE-RAN, Other, 02-01-2012

LTE RAN - Mandatory Actions Required Prior to Node Restart

ATS2011-0281.1

Exercise Caution When Locking IubLink MO from Node Status Analyzer

ATS2011-0247

Mobility RAN Bulletin Ericsson-RNC, Software, 11-17-2011

Ericsson Node-B - Sector May Not Recover After Cold Restart

ATS2011-0224

Degraded VSWR Measurement for 1900MHz 2nd Carrier

ATS2011-0152

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

ATS2010-0212.1

Mobility RAN Bulletin Ericsson-RNC, Translations, 08-29-2010

WcdmaCarriers & UARFCNs on the Ericsson RAN

ATS2009-0170.2

Mobility RAN Bulletin Ericsson-RNC, Hardware, 10-01-2009

Node Restart Needed When Adding or upgrading any hardware

ATS2009-0059

(8)

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

MNRC

1-800-638-2822 option 4

Mobility Integration Center (MIC)

888-864-3998

1 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 1

2. 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

(9)

7.

Are the work orders, MOPs, and supporting

documentation current and error free?

See note 6

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

General and 911

Ask Yourself checklist.docExplanations (1 1).docx911 and E911

1.1 MOP Certifcation Environment

Implementation

Preliminary Implementation Step

PRE-CHECK OF THE SYSTEM

Step

Step Description

Responsible

MIC

FE

Completed

_initial

Pre-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.

(10)

initial

6

If applicable, market test calls are to be completed Common Call Types to be tested are:

(11)

Step

Step Description

Responsible

MIC

FE

Completed

_initial

NOTE: 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

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 for

synchronization. Other option is NTP for sync which does not require 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).

(12)

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.

(13)

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.

(14)

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

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.

(15)

initial

12.

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

X

13.

 From the MO Tree, Select Cabinet=1.

 Click on MO Properties tab on the right side.

 Click on “+” sign next to productData and expand the window so that all field is visible.

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

(16)

initial

14.

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

X

(17)

initial

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

(18)

initial

18.

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

X

19.

 Type vols to list all drives.

 Type mount_c2 to 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

(19)

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 enter to put the RBS into the Backup mode again.

(20)

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:

(21)

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

(22)

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 right pan (remote) to root folder “/” so the C2 and D drives are visible.

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

(23)

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 “$”, enter reload to 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 then press enter

X

3. Press the right arrow to transfer 2. Check Binary

transfer mod 1. Select c2 and d drives

(24)

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 then press enter Password rbs then press enter

(25)

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

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

(26)

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

(27)

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.

(28)

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.

(29)

initial

50.

Click Full Install and wait for the installation to complete successfully

51.

After the installation completes successfully click Upgrade Node.

52.

(30)

initial

54.

Reconnect to the RBS with Element Manager

55.

Open Software view.

Select Upgrade Tab.

(31)

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.

(32)

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".

(33)

initial

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

(34)

MIC

FE

initial

61. Cabinet Equipment Configuration



DO NOT check “Use Configuration file” box.

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

(35)

(36)

63.

 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 65

RBS 6102, 6101, 6201, 6202

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

(37)

64.

 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:

(38)

65.

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

X

66.

Click Next.

(39)

67.

 Click “Next”.

(40)

68.

 Verify successful completion third Pop up window.

(41)

Step

Step Description

Responsible

MIC

FE

Completed

_initial

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.

(42)

MIC

FE

initial

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

(43)

MIC

FE

initial

72.

Restart Element Manager.

Click Tools and select OAM Access.

X

73.

 Click Next

(44)

MIC

FE

initial

74.

OaM access Configuration File Input Page  Check “Use Configuration File”  Check “Automatic (No Wizard)”  Click “Browse”.

(45)

MIC

FE

initial

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”.

(46)

MIC

FE

initial

77.

The wizard now downloads the current configuration data from the RBS. When the download is complete, the Current Configuration page 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.

(47)

MIC

FE

initial

78.

Display shows the Chosen 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.

(48)

MIC

FE

initial

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

(49)

MIC

FE

initial

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 name

OAM_....

X

84.

Verifying Network Synchronization Status

In the RBS EM View selector, select ATM.

(50)

85.

 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 Result returns with an alive response.

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

(51)

MIC

FE

initial

Configuring External Hardware

X

87.

In the RBS EM, from the Tools menu, click Site Equipment

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

X

88.

In the Preconditions page, which displays basic information about the wizard, click Next.

(52)

MIC

FE

initial

89.

 In the File Input page, select the Use configuration file check box.

 Select Automatic (No Wazard).

 Click Browse to find the location of the configuration files on the Client, select <nodename>_RBS_ExtHardward.xml, and then click Open.

(53)

MIC

FE

initial

90.

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

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

Click Next.

(54)

91.

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

(55)

MIC

FE

initial

92.

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

Configuration Completed Successfully Click OK.

X

93.

In the RBS EM View selector, select Software. Click the CV tab.

Verify that a CV is automatically created with the name SITE_....

(56)

MIC

FE

initial

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, see Interpreting 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.

(57)

Step

Step Description

MIC

FE

Completed

_initial

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.

(58)

MIC

FE

initial

Concluding Routines

X

(59)

Step

Step Description

Responsible

MIC

FE

Completed

_initial

1

Check Alarm Status.

_X

2

Check For hardware Faults. EX: Red LEDS

_X

3

Save any Logfiles and screen capture for your reference.

_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

Step

Step Description

Responsible

MIC

FE

Completed

_initial

Not Applicable. If integration failed a Scratch load is needed to

re-integrate the site.

X

9.5 Exit CRITERIA

Step

Step Description

Responsible

MIC

FE

Time

1 Post check completed satisfactorily (Node / Network is in as good or

better performance state than before the activity started.

X

2 Activity 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

(60)

Risk Factor:

3. Execute MOP clean up if required

[Specify timeframe to execute and identify whether work to be completed within

maintenance window or some later date.]

4. End Of Document MOP

(61)

14. Appendix and Tables (

IF REQUIRED

)

14.1 APPENDIX A

Step

How to Download and Install RBS Element Manager

Download and Install Element Manager and Integrate RBS for Windows

1

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

(62)

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

1

Mobile Terminating (MT) from Circuit Switch (SC)

 Verify via the UE that the scrambling code matches the scrambling for the sector under test  Receive a call from a landline number on the UE

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

8

411 Call

 Verify via the UE that the scrambling code matches the scrambling for the sector under test  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

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

 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

 Verify via the UE that the scrambling code matches the scrambling for the sector under test  From UE initiate a MO call

(63)

12

HS Data Call

Note: Either a mobile supporting HSPA or Data Card Required

 Verify via the UE that the scrambling code matches the scrambling for the sector under test  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