Académique Documents
Professionnel Documents
Culture Documents
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.
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.
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.
####################################################################
# 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>
Checking the MO with the required action. Required action missing due to
incomplete MOM
T6530_LTE_B3> acl RbsConfiguration=1
========================================================================
=
Proxy MO Action Nr of Params
========================================================================
=
563 RbsConfiguration=1 changeIpForOamSetting 5
========================================================================
=
===============================================================================
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.
===============================================================================
Proxy MO Action Nr of Params
===============================================================================
563 RbsConfiguration=1 setUniqueLogicalName 1
===============================================================================
Total: 1 MOs attempted, 1 MOs actioned
As you can see, the fingerprint has been set. As I mentioned earlier, once LKF update is
done, the fingerprint remains permanent.