19
1 2xDUW integration through EMAS ///Rabih El-Najjar 14 feb 2011
1
2xDUW integration through EMAS
///Rabih El-Najjar
14 feb 2011
2
Table of Content Physical Cabling ................................................................................................................. 3 Scratch load the node .......................................................................................................... 4 Cabinet Equipment configuration wizard ........................................................................... 7 Site equipment configuration wizard ................................................................................ 11 O&M access configuration: .............................................................................................. 16 Tips and tricks:.................................................................................................................. 19
3
In the following document we will discuss how to integrate 2 DUWs connected together and where one acts as a primary and the second one as a secondary.
Physical Cabling
Installing Cables
1
Information on where to connect the cables can be found in Antenna and RF Connections or RBS Configurations. To install DUW cables, perform the following procedure: Make sure that the new, secondary DUW has the secondary (SEC) end of the IDL cable inserted (see figure above number 3). Make sure that the primary, already installed, DUW has power on: 1. Insert the primary (PRIM) end of the IDL cable in the primary, already installed, DUW. 2. Insert the Common Public Radio Interface (CPRI) cable in both the primary DUW and the secondary DUW(see figure above number 4). 3. Connect the power cable (-48 V DC) to the secondary DUW. 4. Turn on power to the secondary DUW. 5. Check the result of the automatic restore procedure. If this is performed on site, connect the client to the Ethernet port of the primary DUW and use the Element Manager to check the state of faultTolerantCoreStates on MO ManagedElement. The already configured DUW has state Active. The new DUW has state PassiveNotReady during the restore procedure. The new DUW has state PassiveReady when the restore procedure is finished. • If the automatic restore procedure fails, restore the dual DUW configuration as described in Restoring Digital Units. 6. Change RUs or RRUs and cabling, if necessary for the expansion. We have different types of configuration which we will discuss later on in this document.
1 The physical cabling installation was taken from CPI
4
Scratch load the node
To set up a serial connection, perform the following procedure:
1. Connect the RJ-45 connector on the serial cable to the serial port (LMT A) of the primary DUW. 2. Use any software for terminal emulation for example Putty and put the following parameters:
• baud rate = 9600 bits per second
• parity = none
• stop bits = 1 bit
• data bits = 8 bits
• flow control = none
The $ prompt is shown indicating that a serial connection to the primary DUW is established. Then scratch load the node by doing the following commands: reload -- // to go in backup mode formathd /d // drive d will be formatted y reload // go out of backup mode reload -- // enter backup mode formathd /c2 // diver c is formatted y vols // check that c and d are formatted reload // go out of backup mode
To set the IP address of the node do the following: ifconfig le0 <node_ip_address> netmask <netmask_node_ip_address> broadcast <broascast_node_ip_address>
Afterwards add +1 to the IP address of the node and insert it in the laptop IP address. Go to network and sharing center click on manage network connections Right click on local area connection � properties
5
Uncheck the box as shown in the figure above, then select IPv4 then click on properties
Choose “use the following IP “and put the appropriate IP address of the laptop: <node_ip_address+1> Also put in the subnet mask 255.255.0.0, afterwards click OK Then connect to the LMT B with the Ethernet cable so you can ftp the basic package onto the node by using for example “windows total commander”. After copying drivers c2 and d from the basic CV package connect in serial mode and do the following: reload // to restart the node. passwd // to change password rbs rbs ifconfig // to check IP address
6
Go back to Ethernet connection, and download and install the EMAS from the following website: http://<node_ip_address>/em/index.html
Then Open EMAS and connect to the node:
Insert the IP address of the node (10.120.21.35 in this case) and click Connect. Please note that everytime you scratch load the node the finger print will change and you will need to request a new license.
7
Cabinet Equipment configuration wizard
Go to Cabinet Equipment Configuration and follow the steps. You can find all the info needed by logging into AMos and putting the product data.
8
Afterwards all that is left is to put the IP address of the node with the default router.
After click Finish and the EMAS will close on its own.
9
Now connect in serial mode and wait until the synchronize finishes. You will see the following window:
In Amos: RBS456> get . faulttol 101106-11:41:15 10.120.21.35 8.0n RBS_NODE_MODEL_M_1_43_COMPLETE stopfile=/tmp/7788 =============================================================================================== MO Attribute Value =============================================================================================== ManagedElement=1 faultTolerantCoreStates s[2] = ManagedElement=1,Equipment=1,Subrack=1,Slot=1,PlugInUnit=1;Active ManagedElement=1,Equipment=1,Subrack=1,Slot=2,PlugInUnit=1;PassiveNotReady =============================================================================================== Total: 1 MOs
10
In Amos
RBS456> get . faulttol 101106-11:48:15 10.120.21.35 8.0n RBS_NODE_MODEL_M_1_43_COMPLETE stopfile=/tmp/7788 =============================================================================================== MO Attribute Value =============================================================================================== ManagedElement=1 faultTolerantCoreStates s[2] = ManagedElement=1,Equipment=1,Subrack=1,Slot=1,PlugInUnit=1;Active ManagedElement=1,Equipment=1,Subrack=1,Slot=2,PlugInUnit=1;PassiveReady =============================================================================================== Total: 1 MOs
If the DUW is Active that means that DUW is the primary one, if its Passive not Ready means the secondary DUW is not synched with the primary, and if the DUW is PassiveReady means that the secondary DUW is synchronized with the primary.
11
Site equipment configuration wizard
We have different types of configurations, for example 3x2 configurations which stands for 3 sectors 2 carriers per sector hence 6 cells. Here are the different configurations we can have with 2 DUWs: RBB12 1a used for 6x2 RBB12 1a used for 3x2 + 3x2
As you will notice in the 6x2 mode, we have f1 and f2 hence 2 carriers on the same band ( e.g. 1900 MHz) and 6 sectors. In the 3x2+3x2 we have 2 carriers on each sector but 3 of them are on a different band, hence we have 2 bands. RBB22 1a used for 3x3 ->3x4
In the mode 3x3 or 3x4, we have 3 sectors and in each sectors we have 3 or 4 carriers (f1, f2, f3 and f4) depending which mode it is in.
DU
W A
B
C
D
E
F
D
UW A
B
C
D
E
F
S1-S6
f2
S1-S6f1
RUxData 1
Data 2S1
f1-f2
TXA/
RXA
RXB
RUxData 1
Data 2
TXA/RXA
RXB
RUxData 1
Data 2
TXA/
RXA
RXB
RUxData 1
Data 2
TXA/RXA
RXB
RUxData 1
Data 2
TXA/
RXA
RXB
S4
f1-f2
S2
f1-f2
S5
f1-f2
S3
f1-f2
RUxData 1
Data 2
TXA/
RXA
RXB
S6f1-f2
DU
W A
B
C
D
E
F
D
UW A
B
C
D
E
F
S1-S3 B1
f2
S1-S3 B2(S4-S6)
f2
RUxData 1
Data 2S1 B1
f1-f2
TXA/
RXA
RXB
RUxData 1
Data 2
TXA/RXA
RXB
RUxData 1
Data 2
TXA/
RXA
RXB
RUxData 1
Data 2
TXA/RXA
RXB
RUxData 1
Data 2
TXA/
RXA
RXB
S1 B2 (S4)f1-f2
S2 B1
f1-f2
S2 B2 (S5)f1-f2
S3 B1
f1-f2
RUxData 1
Data 2
TXA/
RXA
RXB
S3 B2 (S6)f1-f2
S1-S3 B1
f1
S1-S3 B2
(S4-S6)f1
D
U
W A
B
C
D
E
F
RUxData 1
Data 2S1
f1 & f3
RUxData 1
Data 2
S1
f2 & f4
TXA/
RXA
TXB/
RXB
RUxData 1
Data 2
RUxData 1
Data 2
TXA/
RXA
TXB/
RXB
RUxData 1
Data 2
RUxData 1
Data 2
TXA/
RXA
TXB/
RXB
DU
W A
B
C
D
E
F
S1-S3
f2 & f4
S1-S3
f1 & f3
S2
f1 & f3
S2
f2 & f4
S3
f1 & f3
S3
f2 & f4
12
In this document we will discuss the 3x3 configuration, in other words we have 3 sectors and each sector has 3 cells.
Click Next
If you have the script then check the box in the “use configuration file” and browse to that file, if not just click “Next”. In the second window you will see the progress green bar getting full and at the end you will see the result: current configuration successfully loaded from RBS. Click Next to proceed to page 3.
13
On page 3 you just need to fill out the site and logic name which should be the RBS-Id. On page 4 click “Next” unless the SAU unit is connected to the DUW.
On page 5, you have to choose the Radio building block, in our case it will be RBB22_1A, as for the line rate Ox2 (1.2 Gb/s link) which Specifies the capacity on an optical or electrical link. And in the port Id we have BU1_A and BU1_B which is for the primary DUW where the sectors are connected to slot RI A and RI B, as for the third one BU2_C it’s where the third sector is connected to slot RI C but on the secondary DUW. Sector sequence it should be 1. Click Next. On page 6 you can insert the location information for each sector. After all this is done, click Next and you will see the following window.
14
In page 7, you define the cell Ids and the cell range, now in the example above we have Number of TX branches 2, this means that all the RRUW have all 3 carriers. But if you want them to be separated the Number of TX branches should be set to 1. By doing so we will have the following:
RBS456> get SectorAntenna=1,AuxPlugInUnit=RRUW-2,RruDeviceGroup=1,TpaDeviceSet=1,TpaDevice=1
101117-15:29:43 10.120.21.35 8.0n RBS_NODE_MODEL_M_1_43_COMPLETE stopfile=/tmp/15068
=================================================================================================================
487 Equipment=1,SectorAntenna=1,AuxPlugInUnit=RRUW-2,RruDeviceGroup=1,TpaDeviceSet=1,TpaDevice=1
=================================================================================================================
TpaDeviceId 1
alarmStatus 0 (NO_ALARM)
availabilityStatus 0 (NO_STATUS)
maxTotalOutputPower -1
operationalState 1 (ENABLED)
reservedBy [1] =
>>> reservedBy = NodeBFunction=1,Sector=1,Carrier=2
usageState 2 (BUSY)
userLabel
=================================================================================================================
Total: 1 MOs
RBS456> get SectorAntenna=1,AuxPlugInUnit=RRUW-1,RruDeviceGroup=1,TpaDeviceSet=1,TpaDevice=1
101117-15:29:55 10.120.21.35 8.0n RBS_NODE_MODEL_M_1_43_COMPLETE stopfile=/tmp/15068
=================================================================================================================
457 Equipment=1,SectorAntenna=1,AuxPlugInUnit=RRUW-1,RruDeviceGroup=1,TpaDeviceSet=1,TpaDevice=1
=================================================================================================================
TpaDeviceId 1
alarmStatus 0 (NO_ALARM)
availabilityStatus 0 (NO_STATUS)
maxTotalOutputPower -1
operationalState 1 (ENABLED)
reservedBy [2] =
>>> reservedBy = NodeBFunction=1,Sector=1,Carrier=1
>>> reservedBy = NodeBFunction=1,Sector=1,Carrier=3
usageState 2 (BUSY)
userLabel
=================================================================================================================
Total: 1 MOs
After clicking “Next” we get to page 8 here we get to choose the band, here we have band 2 = 1900 MHz.
Band 1 (2100 MHz)
Band 0 (900 MHz)
Band 2 (1900 MHz)
Band 3 (1800 MHz)
Band 5 (850 MHz)
Band 8 (900 MHz)
15
Page 9, you insert the values for frequency band low edge and high edge; those values should be in accordance to “uarfcn” value in the RNC. In this case we have 19300 and 19450 which means it’s uarcfndl 412 and uarfcnul 12.Click “Next” and go to the next page. Page 10 all the attenuation is set to 0 unless requested otherwise. Click “Next” when done.
In page 11 we can notice we have 2 baseband pools, one on slot 1 meaning the primary DUW and the second baseband pool on slot 2 which is the secondary DUW. We can allocate 3 num Hs codes for each sector but for the num EUL resources we can only have one baseband pool with EUL this means that a maximum of 6 cells can have EUL channel enabled. However there is a feature on the DUW called EulForLargeRbsConfig if activated we can have a second baseband pool with EUL enabled and in this case we will have 9 cells EUL enabled. Click “Next” Then on page 12 click on “Finish”.
16
O&M access configuration:
Now go to tools�O&M Access configuration If you don’t have the configuration file just click “Next”. Then on page 2 wait until the bar is complete then click “Next”.
On page 3 you need to insert the IP address of the node, with the subnet mask and the Transport option is IPV4. On page 4 for the “GigaBitEthernet” select TNA, here also you need to put the IP and Subnet mask. As for VID you need to put the O&M VLAN ID.
17
On page 5 similar to page 4 but you also need to insert IP sync reference as shown in the figure below. On page 6 you need to put the information for the static routing.
Page 7, no changes are required here. Page 8, insert the NTP server address.
18
On Page 9 you will see 2 DUWs, the changes required will be only on the DUW in slot 1, since the second DUW is only for expansion so it doesn’t have O&M connectivity. Hence in slot 1 DUW you can select 5, if Network Synchronization is done through a GPS signal or select 7, if Network Synchronization is done through IP Interface.
On page 10 click “Finish”. Then the window below will appear click “OK”, then “Close all”.
19
Tips and tricks:
1) If you want to change the configuration of the sectors in the DUWs, here is a quick way to do it, without having to scratch load the node again.
After doing the O&M Access configuration, save a CV and make startable by doing “cvms” in AMos Go to EMAS �Tools�Export and Delete. Afterward check the box “delete cabinet equipment and site equipment configuration” and click “OK”. A new CV will be created in AMos automatically, when this is done, you just have to redo the cabinet equipment and site equipment configuration wizard. That way you will be able to try as many configurations as you want without having neither to scratch load the node nor to do the O&M Access configuration everytime.
