SETTING THE FINGERPRINT OF AN ENODEB

BACKGROUND

Oftentimes eNodeBs vis-à-vis DUL comes from factory without any fingerprint unlike
CBUs and DUWs which come with fingerprints from the factory.

In view of this, fingerprint for DULs have to be set. We must note that the fingerprint can
only be set for as long as no LKF update has been done on that eNodeB. Once an LKF
update has been done, the fingerprint becomes permanent.

Below is a procedure of securing this change.

COMPLETE/INCOMPLETE MOM

Usually most CPP nodes, if not all, usually come with incomplete MOM. Basically, this
is to ensure that certain parameters are restricted. This protects unwarranted tampering
with the “dangerous” parameters of the Node.

One of such is the setting of uniquelogicalname under the MO: RbsConfiguration=1

Basically, in order to set the fingerprint of an enodeB, the complete MOM has to be used.

Place the complete MOM which is a zipped file in the following path:
/cygwin/home/your_username/moshell/jarxml. This is the same path where all other
MOMs are placed after been downloaded from the Node.

SETTING THE FINGERPRINT OF THE ENODEB

1. Connect and log unto the node as usual

[~]$ moshell 169.254.1.10

####################################################################
# Welcome to MoShell 9.0j (LPA108514/1_R9J) #
# Finn Magnusson, Jan Pettersson #
# http://utran01.au.ao.ericsson.se/moshell #
# Contact: Finn.Magnusson@ericsson.com #
# Joakim.xo.Ostlund@ericsson.com #
####################################################################
Checking ip contact...OK

HELP MENU : h
BASIC MO COMMANDS : m
OTHER MO COMMANDS : n
OTHER COMMANDS : o
PM COMMANDS : p
QUIT : q

10.0.3.236> lt all
 Parsing MOM (cached):
/home/etemson/moshell/jarxml/ERBS_NODE_MODEL_B_1_53.xml.cache.gz .......
..........................................Done.
Using paramfile /home/etemson/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt
Parsing file
/home/etemson/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt ...............
...............................................................Done.
Connected to 169.254.1.10 (ManagedElement=1).
.
.
T6530_LTE_B3>

2. Force the node to parse the complete MOM

Checking the MO with the required action. Required action missing due to
incomplete MOM
T6530_LTE_B3> acl RbsConfiguration=1

121229-23:15:20 169.254.1.10 9.0j ERBS_NODE_MODEL_B_1_53

stopfile=/tmp/6532

========================================================================
=
Proxy MO Action Nr of Params
========================================================================
=
563 RbsConfiguration=1 changeIpForOamSetting 5
========================================================================
=

Node parsing the complete MOM

T6530_LTE_B3> parsemom ERBS_NODE_MODEL_B_1_53_COMPLETE.xml

Parsing MOM (cached):

ERBS_NODE_MODEL_B_1_53_COMPLETE.xml.cache.gz ...........................
..........................Done.
Using paramfile /home/etemson/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt
Parsing file
/home/etemson/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt ...............
...............................................................Done.

Checking to confirm that the MO now has the required action

T6530_LTE_B3> acl RbsConfiguration=1

121229-23:18:47 169.254.1.109.0j ERBS_NODE_MODEL_B_1_53_COMPLETE

stopfile=/tmp/6532

===============================================================================
Proxy MO Action Nr of Params
===============================================================================
563 RbsConfiguration=1 cancelRbsIntegration 0
563 RbsConfiguration=1 changeIpForOamSetting 5
563 RbsConfiguration=1 modifyConfiguration 1
563 RbsConfiguration=1 setUniqueLogicalName 1
563 RbsConfiguration=1 startProductionTestConfiguration 4
563 RbsConfiguration=1 startRbsAutoIntegration 18
563 RbsConfiguration=1 startRbsIntegration 1
563 RbsConfiguration=1 storeConfigurationReport 4
563 RbsConfiguration=1 updateRbsIntegrationParameters 1
NOTE: You can see that more actions have been displayed, as compared to the
previous output because we are now using the complete MOM.

3. Set the fingerprint as follows:

T6530_LTE_B3> acc RbsConfiguration=1 setUniqueLogicalName

121229-23:22:44 169.254.1.109.0j ERBS_NODE_MODEL_B_1_53_COMPLETE

stopfile=/tmp/6532
Call Action setuniquelogicalname on following 1 MOs ?
===============================================================================
563 ENodeBFunction=1,RbsConfiguration=1
===============================================================================
Call action setuniquelogicalname on 1 MOs. Are you Sure [y/n] ? y

===============================================================================
Proxy MO Action Nr of Params
===============================================================================
563 RbsConfiguration=1 setUniqueLogicalName 1

Parameter 1 of 1, uniqueLogicalName (string): dayo

>>> Return value = null

===============================================================================
Total: 1 MOs attempted, 1 MOs actioned

T6530_LTE_B3> get . fingerprint

121229-23:22:56 169.254.1.109.0j ERBS_NODE_MODEL_B_1_53_COMPLETE

stopfile=/tmp/6532
===============================================================================
MO Attribute Value
===============================================================================
Licensing=1 fingerprint dayo
===============================================================================
Total: 1 MO

T6530_LTE_B3> get Licensing=1

121229-23:25:11 169.254.1.109.0j ERBS_NODE_MODEL_B_1_53_COMPLETE

stopfile=/tmp/6532
===============================================================================
6 SystemFunctions=1,Licensing=1
===============================================================================
LicensingId 1
emergencyStateInfo Struct{2}
>>> 1.state = 0 (NEVER_USED)
>>> 2.time = 0
fingerprint dayo
lastLicensingPiChange 101214-173951
licenseFileUrl
userLabel
===============================================================================
Total: 1 MOs

As you can see, the fingerprint has been set. As I mentioned earlier, once LKF update is
done, the fingerprint remains permanent.