Miscellaneous Projects » Ericsson RBS 6xxx

h1. DUL 20 Configuration

The DUL can be configured via

* OSS-RC (Ericsson operations support system-radio and core - a centralized server)

* EMA (Element Manager - a Windows WebUI utility)

* moshell (a javabased command line utility - runs on linux)

* ncli (a command line utility which runs on the DUL itself)

h2. Configuration tools

h3. EMA - Element Manager

There are different versions of this tool. An ancient version can be downloaded from the DUL itself:

http://169.254.1.10/em/index.html

h3. ncli

With the ncli basic operations can be performed. However the ncli usually doesn't have a ManagedObject tree loaded which means it doesn't know which attributes an ManagedObject can have.

h3. moshell

The most powerful tool to configure the DUL. It loads the ManagedObject on startup. But can also operate offline on backups.

See [[moshell]] for further information how to install and use it.

h2. Backup & Recover

A backup of the DUL can be created via ftp and serial.

The serial is required to boot into the recovery mode.

h3. Boot DUL into recovery

Configure the serial connection to **9600** baud (alternative **115200**).

Restart the DUL by removing the power for 5 seconds.

If the connection is working a boot message is shown:

<pre>

OSE Delta PowerPC/BL410660

Start of @(#)CXC1729957 R80L37 2013-02-01 10:34:51 GMT

Plug-in Unit Product Name:   DUL2001

Plug-in Unit Product No:     KDU137533/4

Plug-in Unit Product rev:    R1F

Plug-in Unit Product Date:   20120402

Plug-in Unit Product Serial: XXXXXXXXXX

Ethernet MAC_address 0:      0x3CCAFFEE2342

RAM size:                    1024 Mbytes

</pre>

Press enter to show the login prompt `username`.

Login using username "rbs" and password "rbs".

<pre>

username: rbs

password:

Welcome to OSE Shell OSE5.5.

$

</pre>

Enter the recovery state:

<pre>

$ reload --

[..]

Stop due to remain in basic/backup set

</pre>

Verify the address of the LMT B interface.

<pre>

$ ifconfig

le0: inet 169.254.1.10 netmask 255.255.0.0 broadcast 169.254.255.255

</pre>

If the address is not correct, the address can be set by:

<pre>

$ ifconfig le0 169.254.1.10 netmask 255.255.0.0

</pre>

The DUL should be reachable by icmp/ping and ftp.

h3. Backup

Backup the "partitions" /c and /d from the DUL to be safe.

/c and /d contains configuration and system files, application and firmwares.

The DUL supports a ftp service.

Mount the volume of c2 on the DUL first.

<pre>

$ mount_c2

$

</pre>

Use your local ftp terminal to get all data. Either graphical client or text.

As an example **gftp** (text version) is used in a terminal on the laptop.

<pre>

linux ~> mkdir backup ; cd backup

linux ~> gftp rbs:rbs@169.254.1.10

</pre>

<pre>

linux ~> gftp 169.254.1.10

gFTP 2.0.19, Copyright (C) 1998-2008 Brian Masney <masneyb@gftp.org>. If you have any questions, comments, or suggestions about this program, please feel free to email them to me. You can always find out the latest news about gFTP from

my website at http://www.gftp.org/

gFTP comes with ABSOLUTELY NO WARRANTY; for details, see the COPYING file. This is free software, and you are welcome to redistribute it under certain conditions; for details, see the COPYING file

Looking up 169.254.1.10

Trying 169.254.1.10:21

Connected to 169.254.1.10:21

220 Welcome to OSE FTP server (Version ose5.3).

USER rbs

230 User logged in.

SYST

215 UNIX system type.

TYPE I

200 Command OK.

PWD

257 "/" is current directory.

ftp>

</pre>

Copy /c2 and /d recursive.

<pre>

ftp> mget c2

[..]

ftp> mget d

[..]

</pre>

Depending on the software version and configuration the size can vary. E.g. 300 MB - 800 MB.

Restart the node into normal operation.

<pre>

$ reload

</pre>

h2. Recovery

Ensure the DUL is booted into recovery.

<pre>

$ reload --

$ mount_c2

$ formathd /c2

> y

$ formathd /d

> y

$ reload --

$ ifconfig le0 169.254.1.10 netmask 255.255.0.0

</pre>

Use ftp to copy files towards the DUL

<pre>

linux ~> gftp 169.254.1.10

gFTP 2.0.19, Copyright (C) 1998-2008 Brian Masney <masneyb@gftp.org>. If you have any questions, comments, or suggestions about this program, please feel free to email them to me. You can always find out the latest news about gFTP from

my website at http://www.gftp.org/

gFTP comes with ABSOLUTELY NO WARRANTY; for details, see the COPYING file. This is free software, and you are welcome to redistribute it under certain conditions; for details, see the COPYING file

Looking up 169.254.1.10

Trying 169.254.1.10:21

Connected to 169.254.1.10:21

220 Welcome to OSE FTP server (Version ose5.3).

USER rbs

230 User logged in.

SYST

215 UNIX system type.

TYPE I

200 Command OK.

PWD

257 "/" is current directory.

ftp>

</pre>

Copy /c2 and /d recursive.

<pre>

ftp> mput c2

[..]

ftp> mput d

[..]

</pre>

Restart the DUL into normal operation.

<pre>

reload

</pre>

h2. Understanding ManagedObjects

**TODO**

h2. Step-by-Step Configuration Howto using the moshell.

h2. Configure a DUL from the scratch [L13A]

Ericsson created the so-called moshell (managed object shell). It

is a utility using java, bash, awk, perl, ssh.

This howto is for L13A release. You can check the release of the DUL with the moshell.

<pre>

moshell> cvls

[...]

===================================================================================================================

201111-16:36            CV Name                                   Upgrade Package       Release

===================================================================================================================

Startable:              selfconfig_autocreated1                   CXP102051/18_R23BM    L13A (C13.0-EP7)

Loaded:                 selfconfig_autocreated1                   CXP102051/18_R23BM    L13A (C13.0-EP7)

Executing:              selfconfig_autocreated1                   CXP102051/18_R23BM    L13A (C13.0-EP7)

Last created:           selfconfig_autocreated1                   CXP102051/18_R23BM    L13A (C13.0-EP7)

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

[...]

</pre>

h2. Cleanup old states

The DUL doesn't support a factory reset method other than installing the software from the scratch using the Recovery method.

The following howto cleans up most of the old state.

<pre>

# load full mom tree

lt all

# do not ask for confirmation

uv del_confirmation=0

uv bldebset_confirmation=0

bl IpSystem=1,IpSec

del IpSystem=1,IpSec

# returns errors if no ntp is defined

acc ManagedElementData=1 deleteNtpThird

acc ManagedElementData=1 deleteNtpSecondary

acc ManagedElementData=1 deleteNtpPrimary

# remove all cells

rdel ENodeBFunction=1,EUtranCellFDD

rdel ENodeBFunction=1,Cdma2000Network

rdel ENodeBFunction=1,GeraNetwork

rdel ENodeBFunction=1,UtraNetwork

# clear old MO from EnodeBFunction to recreate the refMos

set ENodeBFunction=1 upIpAccessHostRef

set ENodeBFunction=1 sctpRef

del TransportNetwork=1,Sctp=1

# clean up synchronizsation

set TimingUnit gpsOutEnabled false

# get a list of activated synchronisations

get Synchronization=1

# remove all entries with `syncReference =`

accn Synchronization=1 removeSyncRefResource IpSystem=1,IpAccessHostEt=1,IpSyncRef=1

accn Synchronization=1 removeSyncRefResource Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=1

del TuSyncRef

del IpSyncRef

# remove remaining Ip Mo

del IpSystem=1,IpAccessSctp

del IpSystem=1,IpAccessHostEt

# ensure the NodeIp is set to 169.254.1.10

get IpOam=1,Ip=1,EthernetLink=1

# check ipv4Addresses => 169.254.1.10 prefix = 16

# if not, set it

# ensure the nodeInterfaceName is set to le0

get IpOam=1,Ip=1 nodeInterfaceName

set IpOam=1,Ip=1 nodeInterfaceName le0

# The IP now changing. exit moshell and reconnect.

del IpOam=1,Ip=1,IpHostLink

del Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface

del Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1

# clean up the equipment

del ENodeBFunction=1,SectorCarrier

bl SectorEquipmentFunction

del SectorEquipmentFunction

rdel Equipment=1,AntennaUnitGroup

# remove all connection of the DUL CPRI ports

get Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,RiPort remoteRiPortRef

set Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,RiPort remoteRiPortRef

# check for RRUS

lpr Equipment=1,AuxPlugInUnit

# if only RUS/RRUS appear, remove them

rdel Equipment=1,AuxPlugInUnit

# check for RUS

lpr Equipment=1

# remove other old RUS

</pre>

h3. setup an empty node

**It's unsure to what the license is bound. It's expected to bound to a uniqueName or the logicalName.

  License issues will show up in the alarm list `al`.**

<pre>

    set ManagedElement=1 userLabel somesite-01

    # create network interface. PortNo defines SFP or Ethernet

    cr Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1

        Attribute 1 of 3, dscpPbitMap (sequence:structRef-DscpPbit): d

        Attribute 2 of 3, linkType (enumRef:LinkType):

        Enter one of the following integers: 0:FRONT_PORTS, 1:BACKPLANE_PORTS: 0

        Attribute 3 of 3, portNo (long): 2

    cr Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=1

        Attribute 1 of 2, networkPrefixLength (long): 24

        Attribute 2 of 2, defaultRouter0 (string): 10.23.0.1

        Following attributes are optional. Enter attribute value or "d" for default.

        Once the MO is created, these attributes cannot be changed (they are restricted).

        Attribute 1 of 5, ownIpAddressActive (string): d

        Attribute 2 of 5, ownIpAddressPassive (string): d

        Attribute 3 of 5, rps (boolean): false

        Attribute 4 of 5, vlanRef (moRef:ManagedObject):

            Enter mo LDN:

        Attribute 5 of 5, mtu (long): 1500

    # set OAM IP

    cr Ip=1,IpHostLink=1

        Attribute 1 of 1, ipInterfaceMoRef (moRef:ManagedObject):

        Enter mo LDN: Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=1

    set Ip=1,IpHostLink=1 ipv4Addresses 10.23.0.199

    # set eNodeB IP

    cr IpSystem=1,IpAccessHostEt=1

        Attribute 1 of 2, ipAddress (string): 10.23.0.198

        Attribute 2 of 2, ipInterfaceMoRef (moRef:ManagedObject):

           Enter mo LDN: Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=1

        Following attributes are optional. Enter attribute value or "d" for default.

        Once the MO is created, these attributes cannot be changed (they are restricted).

        Attribute 1 of 1, networkPrefixLength (long): 24

    cr IpSystem=1,IpAccessSctp=1

        Attribute 1 of 1, ipAccessHostEtRef1 (moRef:IpAccessHostEt):

           Enter mo LDN: IpSystem=1,IpAccessHostEt=1

    # ntp settings

    accn ManagedElementData createNtpPrimary 10.23.0.2 16 1024 true true

    accn ManagedElementData createNtpSecondary 10.23.0.3 16 1024 true true

    # optional allow ntp sync for clock ref

    cr IpSystem=1,IpAccessHostEt=1,IpSyncRef=1

        Following attributes are optional. Enter attribute value or "d" for default.

        Once the MO is created, these attributes cannot be changed (they are restricted).

        Attribute 1 of 1, ntpServerIpAddress (string): 10.23.0.2

    cr IpSystem=1,IpAccessHostEt=1,IpSyncRef=2

        Following attributes are optional. Enter attribute value or "d" for default.

        Once the MO is created, these attributes cannot be changed (they are restricted).

        Attribute 1 of 1, ntpServerIpAddress (string): 10.23.0.3

    accn Synchronization=1 addSyncRefResource IpSystem=1,IpAccessHostEt=1,IpSyncRef=1 3

    accn Synchronization=1 addSyncRefResource IpSystem=1,IpAccessHostEt=1,IpSyncRef=2 4

    deb IpSystem=1,IpAccessHostEt=1,IpSyncRef=1

    deb IpSystem=1,IpAccessHostEt=1,IpSyncRef=2

    # only GPS or external clock can be used.

    ## external clock sync (untested). See `mom TuSyncRef` for more info about Tu

    # cr Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=1

    # accn Synchronization=1 addSyncRefResource Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=1 1

    # deb Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=2

    # gps sync

    cr Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=2

    accn Synchronization=1 addSyncRefResource Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=2 2

    deb Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=2

    # create sctp nodes

    cr TransportNetwork=1,Sctp=1

        Attribute 1 of 2, numberOfAssociations (long): 10

        Attribute 2 of 2, rpuId (moRef:ReliableProgramUniter):

           Enter mo LDN: ReliableProgramUniter=sctp_host

    set TransportNetwork=1,Sctp=1 ipAccessSctpRef IpSystem=1,IpAccessSctp=1

    # setup ENodeBFunction

    # there might be old values

    get ENodeBFunction

    # part of Cell Global Identity

    set ENodeBFunction=1 eNBId 2342

    set ENodeBFunction=1 sctpRef TransportNetwork=1,Sctp=1

    set ENodeBFunction=1 eNodeBPlmnId mcc=901,mnc=70,mncLength=2

    set ENodeBFunction=1 upIpAccessHostRef IpSystem=1,IpAccessHostEt=1

    # s1 link

    cr ENodeBFunction=1,TermPointToMme=1

    # a second ip can be also set or an domainName

    set ENodeBFunction=1,TermPointToMme=1 ipAddress1 10.23.0.2

    deb ENodeBFunction=1,TermPointToMme=1

    # setup the hardware equipment

    # create a subrack

    cr Equipment=1,RbsSubrack=1

        Following attributes are optional. Enter attribute value or "d" for default.

        Once the MO is created, these attributes cannot be changed (they are restricted).

        Attribute 1 of 1, noOfSlots (long): d

    # should not be needed, this SwAllocation should be already present

    get SwManagement=1,SwAllocation=RBS_RU

    # cr SwManagement=1,SwAllocation=RBS_RU

    # accn SwManagement=1,SwAllocation=RBS_RU addRepertoire SwManagement=1,Repertoire=LTE_RBS_RU

    # the dul needs to support this specific RUS/RRUS. Take a look on the installed RUS/RRUS productNumber

    # in this case KRC11875

    # check if this RUS is supported

    lpr KRC11875

    # SwManagement=1,PiuType=KRC11875/1_*

    # should return a MO, this MO is required when adding a new antenna setup

    cr Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=1

        Attribute 1 of 1, piuType (moRef:PiuType):

        Enter mo LDN: PiuType=KRC11875/1_*

    # connect the RUS Data 1 port to the DUL RiPort A

    set Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=1,RiPort=DATA_1 remoteRiPortRef Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,RiPort=A

    # create antennagroup

    cr Equipment=1,AntennaUnitGroup=1

    cr Equipment=1,AntennaUnitGroup=1,RfBranch=1

        Attribute 1 of 2, dlAttenuation (sequence:long):

        Enter value or sequence of values, separated by ,: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

        Attribute 2 of 2, ulAttenuation (sequence:long):

        Enter value or sequence of values, separated by ,: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

    cr Equipment=1,AntennaUnitGroup=1,RfBranch=2

        Attribute 1 of 2, dlAttenuation (sequence:long):

        Enter value or sequence of values, separated by ,: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

        Attribute 2 of 2, ulAttenuation (sequence:long):

        Enter value or sequence of values, separated by ,: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

    cr Equipment=1,AntennaUnitGroup=1,AntennaUnit=1

    # connect the Antenna with the RUS

    set Equipment=1,AntennaUnitGroup=1,RfBranch=1 rfPortRef Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=1,DeviceGroup=ru,RfPort=A

    set Equipment=1,AntennaUnitGroup=1,RfBranch=2 rfPortRef Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=1,DeviceGroup=ru,RfPort=b

    # unblock the RUS

    deb Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=1,DeviceGroup=ru,RfPort=A

    # create sectorequipment function

    cr SectorEquipmentFunction=1

    # on older setup this is in W, on newer this is in mW ###

    # use mom SectorEquipmentFunction configuredOutputPower to know it#

    set SectorEquipmentFunction=1 confOutputPower 20

    # connect Sector Function to the antenna

    set SectorEquipmentFunction rfBranchRef Equipment=1,AntennaUnitGroup=1,RfBranch=1

    cr ENodeBFunction=1,SectorCarrier=1

        Attribute 1 of 1, sectorFunctionRef (moRef:SectorEquipmentFunction):

        Enter mo LDN: SectorEquipmentFunction=1

    set ENodeBFunction=1,SectorCarrier=1 noOfRxAntennas 1

    set ENodeBFunction=1,SectorCarrier=1 noOfTxAntennas 1

    # create cell

    cr ENodeBFunction=1,EUtranCellFDD=1

        Attribute 1 of 6, earfcndl (long): 300

        Attribute 2 of 6, earfcnul (long): 18300

        Attribute 3 of 6, cellId (long): 1

        Attribute 4 of 6, physicalLayerCellIdGroup (long): 1

        Attribute 5 of 6, physicalLayerSubCellId (long): 1

        Attribute 6 of 6, tac (long): 1

        Following attributes are optional. Enter attribute value or "d" for default.

        Once the MO is created, these attributes cannot be changed (they are restricted).

        Attribute 1 of 5, sectorCarrierRef (sequence:moRef-SectorCarrier):

           Enter LDN, or sequence of LDNs (separated by spaces): ENodeBFunction=1,SectorCarrier=1

        Attribute 2 of 5, dlChannelBandwidth (long): d

        Attribute 3 of 5, ulChannelBandwidth (long): d

        Attribute 4 of 5, additionalPlmnList (sequence:structRef-PlmnIdentity): d

        Attribute 5 of 5, additionalPlmnReservedList (sequence:boolean):

           Enter value or sequence of values, separated by ,: d

    # Check the status of all nodes

    st

    # most of the MO should be unlocked and enabled.

    # ensure all important nodes are unlocked

    ldeb ENodeBFunction=1,EUtranCellFDD=1

    ldeb ENodeBFunction=1,TermPointToMme=1

    ldeb SectorEquipmentFunction=1

    ldeb Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1

    ldeb Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=2

    ldeb Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=1

    # finally create a new configuration version otherwise everything is lost after a restart

    cvms singlecell moshell

</pre>