0% found this document useful (0 votes)
203 views9 pages

Huawei 3G Site Integration Manual

This document provides instructions for integrating a new 3G site using Huawei equipment. It is a 3 step process: 1) Download and activate software and configuration files. 2) Configure transmission layer settings like IP, clock link, and SCTP. 3) Configure RF layer settings including RRU/antenna configuration and defining sectors. The summary outlines the key 3 steps in the integration process and what each step involves at a high level without including detailed command examples or configuration parameters.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
203 views9 pages

Huawei 3G Site Integration Manual

This document provides instructions for integrating a new 3G site using Huawei equipment. It is a 3 step process: 1) Download and activate software and configuration files. 2) Configure transmission layer settings like IP, clock link, and SCTP. 3) Configure RF layer settings including RRU/antenna configuration and defining sectors. The summary outlines the key 3 steps in the integration process and what each step involves at a high level without including detailed command examples or configuration parameters.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Huawei 3G

NEW SITE
Integration /
Expansion Manual
1st Edition, Version
1.1

Sherif Mahmoud El-Shalawy


Mobile Access Engineer/Etisalat UAE

Everybody is a genius. But, if you judge a fish by its ability to climb a tree, it'll spend its whole life believing that it is stupid. Albe

To do Before Starting:
1. Neighbor list: Call to the Planning/OMC, ask for neighbor list for your site, this list contains
NodeB IP, Subnet Mask, Gateway IP, RNC IPs (Default and standby).
2. Cell details: call to the OMC Ask for local cell IDs, site configuration(number of sectors, power)
3. Link check: to confirm that the transmission between the NodeB and the RNC is established
this can be MW link or optical fiber according to the site.
a. Set your computer IP, subnet mask and Gateway to the NodeB IPs from neighbor list.
b. Connect your LAN cable to the transmission port in the link.
c. Try to ping the Gateway IP given from the planning team if you received response then the
link is OK if not call to the transmission to check as you cannot integrate the site without
working link.
4. Create a new folder with the site ID (Optional) and put old script file inside it to be used.
Now you have checked and have all the data needed to start the integration.
Requirements for the integration:
1. Working Laptop with Web LMT R015V260 software, internet explorer 9 or older version and
Java compatible platform.
2. Straight LAN cable RJ45 (if BBU have UMPT board you will need also USB to LAN cable).
3. Old scripts file to upload it and edit through it to the new site configuration.
STEP ONE : Software and configuration download and activation :
1. Software loading :
a. Change LAN IP to [Link] (for the new BBU because this is the default IP).
b. Change program IP from office management setting to [Link].
c. Change working directory from SFTP server to the folder you have created for the site
d. Open the WLMT and login with Username: admin and password hwbs@com (for UMPT
boards)(for WMPT username:admin and password: NodeB)
e. In the MML window you can start downloading your old script file by:
Command
Details
DLD
Fill the fields as shown in Fig.1 note that:
1. For user password: hwbs@com (for WMPT password:
SOFTWARE
NodeB)
2. FTP server directory: is the directory for the script file in
the folder you have created before starting.
3. New window will appear put the same directory for the
script file and same password
LST
Copy the software version to be used for the activation
SOFTWARE
(V100R008C00SPC260)
2. Software activation:
Command
Details
ACT
Use the software version for the activation copied from previous
SOFTWARE
command (V100R008C00SPC260) as shown in fig.2

1
Sherif Mahmoud Mohamedsherif@[Link]

3. Configuration file download:


Command
Details
LST CFGFILE To see if there is previous configuration from old data.
DLD
Fill the fields as shown in Fig.3 note that:
1. FTP server IP is the same as program IP.
CFGFILE
2. fTP server username: admin.
3. For user password: hwbs@com (for WMPT password:
NodeB)
4. FTP server directory: is the directory for the configuration
file.
5. Source file name is the configuration file [Link]
4. Configuration file activation :
Command
Details
ACT CFGFILE Use the XML mode and after_reset effect type.
Now you have downloaded and activated the software and the configuration for the NodeB this is
common procedure for all new 3G sites. The NodeB may restart 2 or three time during the
activation.
STEP TWO : Transmission layer (IP configuration):
1. IP configuration :
a. Change LAN IP to [Link]/16.
b. Change program IP from office management setting to [Link].
c. Open the WLMT and login with Username: admin and password hwbs@com (for UMPT
boards)(for WMPT username: admin and password: NodeB)
d. In the MML window start setting the NodeB IP by:
Command
LST DEVIP
ADD DEVIP
LST DEVIP

LST

I
P
C
L
K
L
I
N
K

Details
To check old device data loaded with configuration file
download
To Add IP As shown in Fig.4: for the IP address set the NodeB IP
and the Mask as given from the planning.
With LST command again you will find two IPs old one and the
new one you added now keep the old one and dont remove
now.
You have to remove the IP clock, OM channel, IP route, IP Path
and SCTP link before removing the old device IP because all of
this depends on it.
For removing the IPCLK set link number to 0 to remove the
active IP.
For adding the IP clock link set the server IPv4 (RNC active as
shown in fig.5.
For removing the IPCLK set link number to 1 to remove the
standby IP.
Repeat the addition and change only the Server IPv4 to RNC
standby IP as shown in fig.6.

RMV
I
P
2
Sherif Mahmoud Mohamedsherif@[Link]

C
L
K
L
I
N
K
ADD
I
P
C
L
K
L
I
N
K
LST
I
P
C
L
K
L
I
N
K
RMV
I
P
C
L
K
L
I
N
K
ADD
I
P
C
L
K
L
I
N
K
LST OMCH
LST to see the exsiting OM cnannel so no need to remove just
MOD OMCH
edit.
LST OMCH
In the MOD mode set the local IP to the NodeB IP+1, local mask
as given from planning, and peer IP to [Link] this peer IP
3
Sherif Mahmoud Mohamedsherif@[Link]

LST IPRT
RMV IPRT

ADD IPRT

LST IPPATH
MOD IPPATH

LST

S
C
T
P
L
I
N
K

fixed allover UAE and peer mask [Link] then bearer type
IPV4. As shown in fig.7
For listing the IPRT check how many routes you have then
delete all by repeating RMV command for each route index.
Almost from 0 to 4.
Repeat 5 times for route index from 0 to 4 changing the
destination IP and its mask as follow (repeat as shown in
fig.8)
1. Index zero : Destination IP : [Link] fixed for all UAE
and Mask : [Link].
2. Index 1 : Destination IP : [Link] fixed for all UAE and
Mask : [Link].
3. Index 2 : Destination IP : given RNC IP-1 and Mask :
[Link].
4. Index 3 : Destination IP : RNC active IP and Mask :
[Link].
5. Index 4 : Destination IP : RNC standby IP and Mask :
[Link].
6. All the remaining fields still the same no change and for
the next hop IP is the Gateway IP.
List all existing IP paths then you can directly edit it by editing
the NodeB IP and the RNC IP then repeat 4 times for path ID
from 1 to 4 and change the DSCP as follow: (ID 1 DSCP =
46,ID 2 DSCP = 18,ID 3 DSCP = 10,ID 4 DSCP = 38
List the SCTP link parameters the you can modify the first local
IP to the NodeB IP and first peer IP to the RNC IP.
Repeat 3 times for link number 1,2 and 3 without changing
anything as shown in fig.10.

MOD
S
C
T
P
L
I
N
K
RMV DEVIP Now you can remove the old device IP.
LST IUBCP
List old IUBCP if 3 existing (0,1,2) then no change if not add new
ADD IUBCP
3 by only changing the CBBear ID 0,1,2 and port number 0,1
onlu for ID 1,2 as shown in fig.11.
STEP THREE : RF layer ( Site configuration):
1) RRU/WRFU configuration :
a. Change LAN IP to [Link]/16.
b. Change program IP to [Link].
4
Sherif Mahmoud Mohamedsherif@[Link]

c. Open the WLMT and login with Username: admin and password hwbs@com (for UMPT
boards)(for WMPT username: admin and password: NodeB)
d. In the MML window start configuration by ( For RRU sites) :
Command
LST RRU
RMV RRU
LST

R
R
U
C
H
A
I
N

Details
To check previous RRU setting (how many RRUs you have) if
exist remove it by repeating for all existing RRU.
To check previous RRU chain setting (how many fiber cables
connected to the WBBP board) if exist remove it by repeating
for all existing RRU chains.

RMV
R
R
U
C
H
A
I
N
ADD RRU
Repeat RRU addition for your all RRUs number with its
configuration (Cascaded or single RRU) as shown in fig.12
For single RRU for example 3RRUs repeat 3 times and change
only the subrack number 80, 81, 82 and RRU chain number 0,
1, 2 (fiber cables) and the position is 0 for all.
For cascaded RRUs for example 6 RRUs for 3 sectors (2 for each
sector) repeat 6 times for the 6 RRUs and change only
subrack number, RRU chain number and the position as
following :
1. Sector 1: (1st RRU - Subrack 80, position 0)( 2nd RRU Subrack 81, position 1) (RRU chain number 0 for both)
2. Sector 2: (1st RRU - Subrack 82, position 0)( 2nd RRU Subrack 83, position 1) (RRU chain number 1 for both)
3. Sector 3: (1st RRU - Subrack 84, position 0)( 2nd RRU Subrack 85, position 1) (RRU chain number 2 for both)
ADD
Repeat changing the chain number for all main CPRI cables
R
connected to the WBBP board for example (3 RRUs connected
R
to WBBP repeat 3 times)(6 RRUs cascaded 2/sector repeat
U
also 3 times for the 3 CPRI cables from WBBP board) as shown
C
in fig.13
H
A
I
N
For WRFU configuration change the subrack number will be 4 and slot from 0 to
5 as WRFU installed inside the cabinet.
2) Sectors configuration :
5
Sherif Mahmoud Mohamedsherif@[Link]

a. This section to define the sectors and sector equipment settings, In the MML window start
configuration by:
Command
Details
LST SECTOR To check previous sectors setting if exist remove it by
RMV SECTOR
repeating for all existing sectors.
LST
Also check for all existing sector equipment if existing remove
S
all (supposed to be removed automatically with removing the
E
sectors)
C
T
O
R
E
Q
M
RMV
S
E
C
T
O
R
E
Q
M
ADD SECTOR Repeat changing the sector ID equal to your sectors number.
For single RRU set antenna number to be 2 and the subrack
number for antenna 1 and 2 to be 80 for first sector and 81
for second sector and so on and channel number for 1 st
antenna to R0A and second antenna R0B.
For cascaded RRUs set antenna number to be 2 and the
subrack number for antenna 1 to 80 and antenna number 2
to be 81 for first sector same as subrack numbers for RRU
addition and so on and channel number for 1 st antenna to
R0A and second antenna R0A as 2 RRUs. As shown in fig.14
ADD
Assign the RRUs for the sectors as shown in fig.15, 16 (repeat
S
sector equipment ID equal to RRUs numbers).
E Repeat 2 times for each sector ID by changing the RX/TX
C
mode for both antennas to be Rx/Tx, Rx and Rx, Rx/Tx for
T
the second time.
O Change the subrack number for each sector ID.(sector1R
80,81/ sector2- 82,83 and so on for cascaded RRUs)
E
Q
M
b. Local Cells configuration :
a. This section to define the sectors and sector equipment settings, In the MML window start
configuration by:
Command
LST ULOCELL

Details
To check previous local cells setting if exist remove
6

Sherif Mahmoud Mohamedsherif@[Link]

RMV ULOCELL
ADD ULOCELL

ADD

NODEBMULT
ICELLGRP

ADD

NODEBMULT
ICELLGRPIT
EM

it by repeating for all existing cells.


Assign frequency channels for the sectors as
shown in fig17,18,19
We have two groups (0, 1) each group can carry up
to 6 local cells.
Each 3 local cells assigned to one frequency
default frequencies are 4:
1. F1 UL : 9812, DL : 10762
2. F2 UL : 9837, DL : 10787
3. F3 UL : 9862, DL : 10812
4. F4 UL : 9887, DL : 10337
Assign for first 3 local cell IDs sector equipment 0,
2, 4 assigned to same frequency F1
Assign for second 3 local cell IDs sector equipment
0, 2, 4 assigned to same frequency F2 and now
you have 6 cells in sector equipment 0, 2, 4 as
group 0
Assign for third 3 local cell IDs sector equipment 1,
3, 5 assigned to same frequency F3
Assign for forth 3 local cell IDs sector equipment 1,
3, 5 assigned to same frequency F4 and now you
have 6 cells in sector equipment 1, 3, 5 as group
1
Frequency assignment to the sector equipment
may vary.
Repeat local cell addition by changing the cell ID
(almost site ID, 1), sector equipment1, UL, DL
frequencies, and the MAX power.
Repeat multi-group addition for same sectors
numbers.
Sect carrier cell ID 0, 1, 2 and so one equal to site
sectors as shown in fig.17
Repeat for local cells numbers and assign all to cell
IDs you have created in previous step
For cell ID 0 : local cell 1,2,3 Sector A
For cell ID 1 : local cell 4,5,6 Sector B
For cell ID 2 : local cell 7,8,9 Sector C

STEP FOUR: Board configuration:


a. Check for the boards installed in your site and compare with the boards configured in the
software from device maintenance tap, if there is board change start adding or removing
with what existing in the site. For example for removing/adding WBBP board.
Command
LST

Details
To see what already installed in your BBU.
BAS
EBA
NDE
QM

RMV BRD

To remove a board by setting slot number for this board in


the BBU.

7
Sherif Mahmoud Mohamedsherif@[Link]

Command
LST

Details
To see what already installed in your BBU.
BAS
EBA
NDE
QM

ADD BRD

To add a board by setting slot number for this board in the


BBU and selecting the board type as WBBP as shown in
fig.21.

STEP FIVE: External Alarms setting:


a. You have to check for the external alarms if not connected to your BBU (connected to the
2G equipment) so you must disable it by:
Command
SET ALMPORT

Details
To set the alarms off, repeat 8 times for all external alarms
by changing the port number from 0 to 7 as shown in
fig.22 and set the switch to OFF.

There is no copy rights in the world, feel free to steal my effort.

8
Sherif Mahmoud Mohamedsherif@[Link]

Common questions

Powered by AI

Using specific peer IPs and masks when configuring the transmission layer is necessary to ensure correct data routing and communication integrity between network components such as NodeB and RNC. The peer IPs and masks, such as 10.24.0.216 with mask 255.255.0.0, are fixed values chosen to facilitate consistent and reliable connections across the network infrastructure throughout the UAE. These configurations guarantee that data is transmitted through authorized and recognized channels, minimizing communication errors and potential data loss .

Reliable IP synchronization during the transmission layer setup is ensured by meticulously aligning IP configurations, such as setting up NodeB IPs, modifying IP clock links, and establishing SCTP links, as outlined in the integration manual. It is vital to adhere to prescribed sequences, such as removing old device IPs and systematically adding new IPs while ensuring all related settings, like IP paths and routes, are correctly updated. This process establishes reliable and consistent connectivity with RNC and other components .

Setting the LAN IP to specific values, such as 192.168.0.50 for the BBU or 17.21.2.14 for NodeB IP, is crucial for establishing consistent communication between the integration equipment and the NodeB. This ensures that configurations and commands are properly directed to the correct network component and that they are able to communicate effectively with the RNC and other network elements. This IP assignment is a foundational step to ensure proper integration and subsequent operations .

Previous configurations can interfere with new integrations by introducing conflicting settings or outdated parameters that are not compatible with current network architectures. During the integration process, it is essential to list and understand existing configurations using commands such as LST CFGFILE, and remove or modify old configurations accordingly. This includes removing existing device IPs, OM channels, IP paths, and sector settings, ensuring that the integration proceeds without unnecessary disruptions .

Configuring the RF layer and setting up RRU chains enhances network performance by optimizing the distribution of resources and coverage. By systematically organizing RRUs in either cascaded or single configurations, and by modifying operational parameters such as subrack numbers and chain positions, the network can better manage and direct signal flows to meet capacity demands. This structured approach ensures efficient spectrum use, maximizes coverage area per sector, and minimizes interference .

Disabling unused external alarms during NodeB setup is crucial to prevent false alarms and reduce noise in network monitoring systems. If these alarms, often connected to outdated systems like 2G equipment, remain active without serving any functional purpose, they may create unnecessary alerts and obfuscate genuine network issues. Setting alarms off by changing the port number helps in aligning the setup with current operational requirements and maintaining a clear monitoring framework .

The ADD IPRT command must be performed repeatedly to establish multiple routes within the network, each translating to a unique path that data packets can follow. This redundancy ensures that if one route encounters an issue, alternative paths are available to maintain data flows. Configuring with specific pairings of destination IPs and masks for indexes (e.g., Index 0: 10.237.210.70) creates a comprehensive routing table that enhances network resilience and scalability .

Conducting a thorough review and potential reset of configuration files ensures that any legacy settings do not interfere with new site requirements. Commands like LST CFGFILE and DLD CFGFILE are used to inspect and download existing configurations, after which ACT CFGFILE applies the updated settings in a controlled environment. This process guarantees that the NodeB operates with parameters aligned to the latest network standards, preventing incompatibilities that may affect site functionality .

Assessing compatibility and necessity during the NodeB board configuration involves checking the boards installed using commands like LST BASEBAND EQM, and comparing them with the existing board needs for effective network function. Decisions to add or remove boards are made based on this assessment, ensuring that only essential hardware is utilized, maintaining operational efficiency, and avoiding resource wastage. This phase is critical for aligning hardware capabilities with network performance objectives .

Critical considerations include ensuring optimal frequency assignment to minimize interference, as well as aligning local cells with specific sector equipment IDs to maintain seamless connectivity. For example, assigning frequencies using specific uplink and downlink channels (e.g., F1 UL: 9812, DL: 10762) and organizing cells into groups ensures that spectral resources are effectively utilized and that cells adhere to the spatial distribution within the sector. These configurations prevent signal overlap and enhance network efficiency .

You might also like