Ericsson UMTS RBS6000 NodeB Integration

AT&T Mobility Network
Ericsson UMTS RBS6000

NodeB Field Integration MOP
Author Contact Info:
Nick Huynh
NH8299@att.com
Cell 214-507-4128
Mobility Integration Center

Objective Background: Market request for field integration
support.
Version: 1.1
Last Updated: 5/6/2013
Risk Assessment #:6568
Risk Assessment Score:8
Ericsson UMTS RBS6000 NodeB Field Integration MOP
Table of Contents
1.
2.
3.
4.
Document History...................................................................................................4
Versions..................................................................................................................4
Integrated Solution Approach v1 (ISA v1)...............................................................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 63
Use 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.
Document History
Issue
1.0
Issue Date
04/01/13
1.1
04/24/13
1.2
05/08/13
Author(s)
Nick Huynh
(nh8299)
Nick Huynh
(nh8299)
Nick Huynh
(nh8299)
Identification of Changes
Initial Draft
Update section 9.2
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 #
Draft 1.0
Editor
Comments
The version and editor of the Implementation Guide (IG) or
Deployment Guide (DG)

Page 3 of 63
MOP Impact Scope/ General Information

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

Originator
Date
Time
Nod eCLLI(s)
Description
Enter short description of what activity will take place.
Service Impact
This is a new turn-up, no impact is expected.
Coordination
1.
Field will co-ordinate with the MIC for Integration.
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
Site OAM script
OAM Wizard
Site External Hardware script
Site Equipment Wizard
SiteComplete script
Run Command tool

Page 4 of 63
Tools
Tools
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)
LAN
Connect a Ethernet cable from your PC to the rbs local

Ethernet port (LMT B).
FTP
ftp client application displaying your PCs hard drive

highlight the /d and /c2 folders
FTP
ftp server application navigate to the rbs upgrade software

package folder where it is only displaying the name of the
upgrade package
Element Manager
Ericsson Element Manger GUI
Pre Maintenance Check, Precautions, and Preparations

Pre Maintenance Check Tools/System
Procedure -1 Pre Maintenance Check Tools.System
Action
Step
1.
Site is installed and powered-up.
2.
Engineer has Ericsson Base software.
3.
Engineer has configuration scripts.
Results/Descriptions
Chk
4.
5.
Pre-Maintenance Check Manual (Non-Automated Requirements)

Procedure -2 Preliminary
Action
Step
1.
Chk
NA- This is a new cabinet turn-up.
2.
ATS Bulletins

Page 5 of 63
Procedure -1 ATS Bulletins

Step
1.
2.
3.
4.
5.
6.
7.
Action
Access the ATS Bulletin site at the following URL:

ATS Bulletin
Click on the List/Search button
(At the top of page)
Time Line
Click on the -Search Menu>

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
Click on the Submit Query button

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
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
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
ATS20120268
ATS20120247
ATS20120244
ATS20120239
ATS2012-0235
ATS20120234.1
ATS20120220
ATS2012-
Engineer
Check
Bulletin Ericsson-RNC, Upgrade, 11-05-2012

RNC W12B: During re-homes on W12B, sites are being allocated to one single
module
Secure Shell (SSH) Application Restart
Bulletin Ericsson-LTE-RAN, Hardware, 10-25-2012
Put ON HOLD of any SOURCEPHOTONICS SFP usage in LTE deployment
Bulletin Ericsson-RNC, Features, 10-17-2012
Prevention of negative and hanging counters in UEH
Bulletin Ericsson-RNC, Features, 10-15-2012
frequent DC SP crashes due to Measurement result recording for WCDMA (MRR-W)
Bulletin Ericsson-LTE-RAN, Software, 10-15-2012
Ericsson eNode-B CV Management
Bulletin Ericsson-RNC, Hardware, 10-04-2012
SW Upgrade to W12B IP1 fails on Dual DUW nodes configured with external RX
branch sectors
Bulletin Ericsson-RNC, Provisioning, 10-03-2012

Page 6 of 63

Slogan: Attribute lowCurrentSupervision should not be changed on W12B IP1
0219
ATS20120201
Bulletin Ericsson-RNC, Other, 09-12-2012

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 Ericsson-RNC, Provisioning, 07-07-2011

High 2011-06-20.02:WCDMA RBS: VSWR Antenna supervision formula and guiding
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

Remove Old CV's Preventing Automatic CV Backup Creation
8.4
Emergency 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:
2.
1. Cease all work immediately.

Notify the AT&T MNRC

Page 7 of 63
Organization
Contact Name
Contact Number
MNRC
1-800-638-2822 option 4
Mobility Integration Center (MIC)
888-864-3998
1 Precautions
The stop sign indicate a critical step that may cause and ourtage.
Ask Yourself
Place initials and date to acknowledge that you have read and understand
Step
E911 Ask Yourself
Descriptions
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?
Does this work affect 15+ sites?
See note 3
Can I prevent or control service interruptions to

911/e911?
Is this the right time to do the work?
See note 5
Is the individual performing the work trained and

qualified to do this work?
Are MOPs and supporting documents current and error
free?
Does the MOP include a 911/e911 test plan?
See note 7
4.
5.
6.
7.
8.
9.
Step
1.
2.
3.
4.
General Ask Yourself

Do I have the proper ID and appropriate building
access permissions for the environment I am about to
enter?
Do I know why Im doing this work?
Have I identified and notified everybody customers
and internal groups who will be directly affected by
this work?
Can I prevent or control service interruption?
Check
See note 4
See note 6
See note 8
See note 8
Descriptions
Check
See note 1
See note 2
See note 3

Page 8 of 63

5.
Is this the right time to do this work?
See note 4
6.
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?
Do I have everything I need to quickly and safely
restore service if something goes wrong?
Have I walked through the procedure?
See note 6
8.
9.
10.
See note 7
See note 8
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
911 and E911
Ask Yourself checklist.doc
Explanations (1 1).docx
1.1
MOP Certifcation Environment
Implementation
Preliminary Implementation Step
PRE-CHECK OF THE SYSTEM
Responsible
Step
Step Description
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.
THE NODES MUST BE FAULT FREE FOR AT LEAST 24 HOURS.
Contents of MOP and referenced documents reviewed and available.
MIC
FE
If applicable permission for local site access is granted.

Verify all necessary remote access to all nodes including OSS access is
confirmed.
All involved nodes are verified working normally.
Verify / identify with customer the target nodes.
2
3

Page 9 of 63
Completed
initial
Responsible
Step
Step Description
If applicable, market test calls are to be completed
Common Call Types to be tested are:
UE Originate and UE Terminate
MIC
FE

Page 10 of 63
Completed
initial
SITE SPECIFIC STEP-BY-STEP

Responsible
Step
Step Description
MIC
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.
----
FE
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.
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
- Site Router
S1 CP/UP/OAM/X2
TN B Fiber
RI A - Sector A, Radio 1
2.
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
Completed
initial
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).

Page 11 of 63
----------
Responsible
Step
Step Description
MIC
FE
Establish O&M Connection to the NodeB

Establish an O&M connection to the NodeB following the instructions below. Also
see DUW connections diagram.
3.
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.
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.

Page 12 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
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.
6.
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.
7.
NOTE: This step ensures Ethernet communication with the RBS.
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.

Page 13 of 63
Completed
initial
Responsible
Step
9.
Step Description
Open RBS Element Manager application for NodeB on your PC.
NOTE: This will be under Start EM Applications RBS Element Manager.
MIC
FE
X
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.
10.
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.

Page 14 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
From the Element Manager window click on the Views drop down menu and
select Containment (MOM based).
12.
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>
13.

Page 15 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Capture the screen and save it to <sitename>.jpg file.
14.
15.
Close the RBS Element Manager application.

Page 16 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
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:
16.
NOTE: Establish the serial connection to the DUW. Once the $ prompt
appears, connection is established.
17.
Verify the available SW on the RBS.

$cv ls
The minimum SW must be W11A.

Page 17 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
In the HyperTerminal window, type reload -- then press enter to put the
RBS into the Backup mode.
18.
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

Page 18 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Type formathd /d then press enter to format the D drive.

The RBS replies with the information as shown below, enter y to confirm
20.
Type reload -- then press enter to put the RBS into the Backup mode
again.
21.

Page 19 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Set the IP Configuration by typing the following command:

ifconfig le0 169.254.1.1 netmask 255.255.254.0
22.
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.
Type ifconfig to verify the RBS IP configuration.
23.
24.
If needed, set the default gateway address in the node by command:

route add default <gateway>.

Page 20 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Type reload to activate the RBS password and IP configuration.
25.
NOTE: Save the product data for use later in the Cabinet Equipment
Wizard, step 63 & 64.
Type reload -- to put the RBS into the Backup mode.
26.
27.
Stop window firewall if it is running on the laptop.
28.
Launch WS_FTP through Ethernet connection to DUW LMTB

Page 21 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
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
29.
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.
30.
Note: Confirm with PM/MIC for the correct Basic Package before
proceeding.

Page 22 of 63
Completed
initial
Responsible
Step
1.
2.
3.
31.
Step Description
MIC
FE
1. Select the C2 and D drives in the left pan (local).

2. Check Binary transfer mode button.
3. Press the right arrow to transfer to the RBS.
1. Select c2 and
d drives
3. Press the right

arrow to transfer
2. Check Binary
transfer mod
32.
Wait for the upload to complete successfully (15-30 minutes)
Establish a serial connection between the RBS and local client.

At the command prompt $, enter reload to put the RBS in active mode.
33.
NOTE: Wait until HyperTerm displays security properties not found

using defaults in the window.
Press enter and login
34.
Username rbs then press enter
Password rbs then press enter

Page 23 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Set clock
Type setclock YYYY-MM-DD HH:MM:SS then press enter
ex: setclock 2013-13-24 10:10:00 <enter>
35.
X
Enter: readclock
To confirm your time
Type reload and wait for it to complete (up to 4 minutes). When completion
response Login Server Ready appears.
36.
Press enter and login
37.
Username rbs then press enter
Password rbs then press enter

Page 24 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Use the following steps to set the RBS password.
Type passwd then press enter
Type rbs (wont show on screen) then press enter
Type rbs (wont 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
38.
If an upgrade is NOT required, skip to step 59. Please contact

your PM/MIC support for instruction.
39.
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.
From the window pane displaying your PCs 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.
40.
X
For Ex: After unzip, if the upgrade
CXP9018350_R10A.
Navigate
to
the
CXP9018350_R10A
41.
package
folder
is named
containing
From the window pane displaying the rbs hard drive in the ftp client
application navigate to /c/tmp.

Page 25 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
From the window pane in the FTP client application displaying your PCs
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.
42.
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.
43.
Connect a crossed Ethernet cable from your PC to the NodeB local

Ethernet port (LMT B).
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.
44.

Page 26 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
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
45.
If an upgrade is NOT required, skip to step 59, Please contact

your PM/MIC support for instruction.
46.
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.

Page 27 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
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
47.
NOTE: Ensure the correct directory name and the path name is entered
Once the name is entered the Create Package button is enabled.
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
Click Install Package when it highlights
49.

Page 28 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Click Full Install and wait for the installation to complete successfully
50.
After the installation completes successfully click Upgrade Node.
51.
Click Hard Upgrade.
52.
Monitor the upgrade progress with the window maximized and wait for
successful completion
53.
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.

Page 29 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Reconnect to the RBS with Element Manager
54.
Open Software view.
55.
Select Upgrade Tab.

Right click on upgrade package and select properties
56.

Page 30 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
From Properties window select Confirm Upgrade and click Yes
57.
Click yes on pop up to make the upgrade permanent.

NOTE: You may have to change views and go back to confirm the
upgrade.
58.
Upgrade is complete. Click Yes

Page 31 of 63
Completed
initial
Responsible
Step
Step Description
MIC
FE
Run the Cabinet Equipment Configuration tool
59.
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 nodes 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 dont have a battery backup, disconnect the control cable of the
BFU, otherwise you will have the alarm "NumberOfHwEntitiesMismatch".

Page 32 of 63
Completed
initial
Step
Step Description
Use the following steps to configure the cabinet and equipment.
MIC
Responsible
Completed
FE
initial
X
In Element Manager click Tools and select Cabinet Equipment

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

Page 33 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
Cabinet Equipment Configuration
61.
DO NOT check Use Configuration file box.
Click Next. The system will auto-detect the cabinet equipment.

Page 34 of 63

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

Page 35 of 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 65

RBS 6102, 6101, 6201, 6202
63.
Note: RBB and Line rate can be retrieved from information supplied
by PM/MIC

Page 36 of 63
Enter cabinet product information retrieved from RBS cabinet label on

top of subrack near back.
Click NEXT.
RBS 6301 and 6601
64.
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:

Page 37 of 63
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.
65.
Click Next.
66.

Page 38 of 63
67.
Confirm the Default IP address 169.254.1.1 and Subnet mask

255.255.254.0
Click Next.

Page 39 of 63
68.
Click Finish
Click Yes on the Pop up window to confirm
Verify successful completion third Pop up window.

Page 40 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
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.
69.
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.

Page 41 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
Example of Restart Requirement Message
70.
Use the following steps to run the O&M Access script.
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
71.
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

Page 42 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
Restart Element Manager.

Click Tools and select OAM Access.
72.
73.
Click Next

Page 43 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
OaM access Configuration File Input Page
74.
Check Use Configuration File
Check Automatic (No Wizard)
Click Browse.

Page 44 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
Navigate Client computer and select the xxxx_OAM_Access.xml file and

click Open.
75.
76.
Verify that the the correct OAM script was selected.
Click Next.

Page 45 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
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.
77.
NOTE: If the wizard displays an error message, take a snapshot of the

error and contact your MIC support.

Page 46 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
Display shows the Chosen RBS Configuration page, which summarizes

the settings you have specified for the configuration.
78.
Click Finish to start the installation.
On the popup window. Click OK to confirm.

Page 47 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
The Current Action page is displayed.
79.
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.
80.
Wait until the following message is displayed in the Result box:

Configuration Completed Successfully
81.
Click OK. The RBS EM will be closed immediately.
82.
Restart the RBS EM.

Page 48 of 63
Step
Step Description
In the RBS EM View selector, select Software.
Click on Managed Element 1
Click the CV tab.
83.
MIC
Responsible
Completed
FE
initial
Verify that a Configuration Version (CV) is automatically created with the name
OAM_....
Verifying Network Synchronization Status
In the RBS EM View selector, select ATM.
84.
Select the Synchronization object and verify that nodeSystemClock is in

LOCKED_MODE mode.

Page 49 of 63

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.
85.
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.
86.

Page 50 of 63
Step
87.
Step Description
MIC
Responsible
Completed
FE
initial
Configuring External Hardware
In the RBS EM, from the Tools menu, click Site Equipment
Configuration... to start the Site Equipment Configuration wizard.
In the Preconditions page, which displays basic information about the wizard,
click Next.
88.

Page 51 of 63
Step
Step Description
89.
MIC
Responsible
Completed
FE
initial
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.

Page 52 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
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.
90.
Click Next.

Page 53 of 63

The Chosen RBS Configuration page will now be displayed.
91.
Click Finish to start installation and display the Current Action page.

Page 54 of 63
Step
Step Description
MIC
Responsible
Completed
FE
initial
Wait until the following message is displayed in the Result dialog box:
92.
Configuration Completed Successfully

Click OK.
In the RBS EM View selector, select Software.
Click the CV tab.
93.
Verify that a CV is automatically created with the name SITE_....

Page 55 of 63
Step
Step Description
Verifying the LED Status
MIC
Responsible
Completed
FE
initial
X
This activity verifies all units are working properly by verifying the Light Emitting
Diode (LED) status.
Verify that:
94.
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.
Verifying the RbsLocalCell
This activity verifies the local RBS cell connection.

In the RBS EM View selector, select Radio Network.
95.
Verify that all RbsLocalCell have the operational state Enabled.

Page 56 of 63
Step
Step Description
Completing the Integration
MIC
Responsible
Completed
FE
initial
X
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.
96.

Page 57 of 63
Step
97.
Step Description
MIC
Responsible
Completed
FE
initial
Concluding Routines
Inform MIC support that the On-Site Integration is completed.

Page 58 of 63
9.3 POST CHECK OF THE SYSTEM

Responsible
Step
Step Description
Check Alarm Status.
MIC
FE
2 Check For hardware Faults. EX: Red LEDS

3 Save any Logfiles and screen capture for your reference.
Completed
initial
X
X
Before you leave the site, ensure that the following actions have been performed:
Close the RBS EM.
4 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.
9.4
FALL BACK
Responsible
Step
Step Description
Not Applicable. If integration failed a Scratch load is needed to reintegrate the site.
MIC
FE
Completed
initial
9.5 Exit CRITERIA

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

better performance state than before the activity started.
Activity completion report (along with the status / KPIs from pre and
2 post checks) has been sent to all concerned personnel from AT&T and
the customer.
3 All logs from the activity have been stored in the designated AT&T
Shared Drive.
MIC
Responsible
FE
X
X
X

Page 59 of 63
Time
2. Risk Assessment Score

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

5. Service Assurance/Monitoring

Page 60 of 63
14. Appendix and Tables (IF REQUIRED)
14.1
Step
APPENDIX A
How to Download and Install RBS Element Manager
Download and Install Element Manager and Integrate RBS for Windows
1
1
2
Must have Java 1.5 or higher installed on PC.
Connect a crossed Ethernet cable from your PC to the eNodeB local Ethernet port (LMT B).
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.
Open Internet Explorer (IE). Type in the following url address:

http://169.254.1.1/em/index.html
Click on Windows Download, then click Run. Follow the install instructions as they are displayed.

Page 61 of 63
14.2 APPENDIX B
Note: Please confirm with your PM if 911 call is to be performed.
Call Test Scenarios
Step
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
Mobile Terminating (MT) from Circuit Switch (SC)
6
1
Receive a call from a landline number on the UE
Release the call
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
411 Call
From the UE dial 411
Confirm call is connected to information
Release the call
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
SMS Call
10
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
Combination RAB Packet Switch (PS) plus Circuit Switch (CS) Call
11
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

Page 62 of 63
Call Test Scenarios
Step
HS Data Call
Note: Either a mobile supporting HSPA or Data Card Required
12
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

Page 63 of 63

Ericsson UMTS RBS6000 NodeB Integration

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ericsson UMTS RBS6000 NodeB Integration

Caricato da

Copyright:

Formati disponibili

AT&T Mobility Network

Ericsson UMTS RBS6000

Mobility Integration Center

Ericsson UMTS RBS6000 NodeB Field Integration MOP

AT&T CONFIDENTIAL & PROPRIETARY

Ericsson UMTS RBS6000 NodeB Field Integration MOP

Same as Document History and front page less the date

Added Risk Assessment score.

Integrated Solution Approach v1 (ISA v1)

AT&T CONFIDENTIAL & PROPRIETARY

Ericsson UMTS RBS6000 NodeB Field Integration MOP

MOP Impact Scope/ General Information

Site Specific Description

Enter short description of what activity will take place.

Field will co-ordinate with the MIC for Integration.

Prerequisite/Dependencies/Entrance Criteria of MOP

Site OAM script

Site External Hardware script

Site Equipment Wizard

Run Command tool

AT&T CONFIDENTIAL & PROPRIETARY

Ericsson UMTS RBS6000 NodeB Field Integration MOP

Connect a cable from your serial or USB port on your PC

Connect a Ethernet cable from your PC to the rbs local

ftp client application displaying your PCs hard drive

ftp server application navigate to the rbs upgrade software

Ericsson Element Manger GUI

Pre Maintenance Check, Precautions, and Preparations

Site is installed and powered-up.

Engineer has Ericsson Base software.

Engineer has configuration scripts.

Pre-Maintenance Check Manual (Non-Automated Requirements)

NA- This is a new cabinet turn-up.

AT&T CONFIDENTIAL & PROPRIETARY

Ericsson UMTS RBS6000 NodeB Field Integration MOP

Procedure -1 ATS Bulletins

Access the ATS Bulletin site at the following URL:

(At the top of page)

Click on the -Search Menu>

You may have to try several key

Click on the Submit Query button

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

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

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

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

AT&T CONFIDENTIAL & PROPRIETARY

Ericsson UMTS RBS6000 NodeB Field Integration MOP

Bulletin Ericsson-RNC, Other, 09-12-2012

Bulletin Ericsson-RNC, Software, 04-29-2012

Bulletin Ericsson-RNC, Software, 03-22-2012

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

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

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

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

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

Mobility RAN Bulletin Ericsson-RNC, Software, 10-20-2011

Mobility RAN Bulletin Ericsson-RNC, Provisioning, 07-07-2011

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

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

Mobility RAN Bulletin Ericsson-RNC, Software, 02-11-2009

1. Cease all work immediately.

AT&T CONFIDENTIAL & PROPRIETARY

Ericsson UMTS RBS6000 NodeB Field Integration MOP