Ericsson 3G

Network Audit &

Parameter Modification

Network Engineering
AUG 21, 2019
Configure Citrix Client

 Configure Citrix OSS Client and Log into OSS

 Add ICA Connection -> LAN ->
 Protocol: TCP/IP+HTTP;
 Server IP: 10.206.116.200/201
 Options
 Window Colors: True Color (24bit)
 Window Size: (1024x768)
Starting up Moshell
Upon startup, and running the command "lt all“ (load tree), moshell will go
through the following steps:

1. Download the node’s IOR (Interoperable Object Reference) file and store it
on the workstation. The IOR file contains the node’s IP address and some
specifications as to how the clients can send requests to the node.

2. Check the node’s MOM version and download from the node.

3. Parse the MOM and generate an internal table specifying all MO classes,
attributes, and actions supported by the node.

4. Initiate CORBA communication with the node by using the information

contained in the IOR file.

5. Read the FDN of the Root MO

6. Ready to receive commands from the user

Managed Object Model

Each MO class contains a number of attributes which are used to store

configuration data or performance measurement data.

Each MO class can also support a number of defined actions. These represent
certain operations which can be performed by the MO. A typical example is
the action restart which will cause the MO to restart the resource it is
responsible for (a board, a program, etc).

The Managed Object Model (MOM) is a reference document describing all the
MO Classes that can exist in a Network Element, together with their attributes
and actions.
To view the MO tree
>momt
Taking dumps on individual RNC or NodeB
 Launch -> Applications -> Utilities -> Terminal

amos [RNC name/NodeB name]

lt all
l+
kget all
l-
Taking dumps on multiple RNCs/NodeBs
 amosbatch filepath_RNC/NodeB_list filepath_command_file
 
 amosbatch /home/etfitmer/RNC_LIST.txt /home/etfitmer/RNC_CMD.txt
 RNC_CMD.txt
◦ lt all
◦ l+
◦ kget all
◦ l-
 RNC_LIST.txt
◦ RNC01_ER_ADTEL_AD_SER
◦ RNC02_ER_ADTEL_AD_SER
◦ RNC03_ER_ADTEL_AD_SER
◦ RNC04_ER_ADTEL_AD_SER
◦ RNC05_ER_SHTEL_SH_SR
◦ RNC06_ER_SHTEL_SH_SR
◦ RNC07_ER_SHTEL_SH_SR
◦ RNC08_ER_SHTEL_SH_SR
◦ RNC09_ER_JMTEL_JM_SWR
◦ RNC10_ER_JMTEL_JM_SWR
◦ RNC11_ER_JMTEL_JM_SWR
Bulk CM Export using OSS

 Launch -> Applications -> Ericsson -> OSS Common

Explorer
  

◦ In the Topology View, select WCDMA

◦ Right-click - > Export
◦ In the Export Details, note (copy) the file path where the
export will be saved so that you can navigate to the specified
folder using your FTP client
◦ Click on the Export Button at the bottom-right
◦ Launch your FTP client
◦ Navigate to the folder where the export was made
◦ Copy to you PC
◦ Use parser software to parse the dump
3G Bulk CM Parse

Use RaNP (3rd Party Software) to parse the BulkCM or Kget

dump files and export to the desired format (excel, access) for
further analysis and documentation.
 Modifying RNC parameters

 To Enable feature on RNC

 Log into the RNC : amos RNC_NAME
 Load the MO object model:
◦ lt all
◦ lset full_distinguished_name_of_feature featureState 1
 Eg.
◦ amos RNC01_ER_ADTEL_AD_SER
◦ lt all
◦ lset SystemFunctions=1,Licensing=1,RncFeature=LoadBasedHandoverToGsm featureState 1
◦ lset SystemFunctions=1,Licensing=1,RncFeature=ServiceBasedHandover featureState 1
◦ lset SystemFunctions=1,Licensing=1,RncFeature=LoadBasedHandoverToGsm featureState 1

◦ lset ManagedElement=1,RncFunction=1 loadSharingDirRetryEnabled 1

◦ lset ManagedElement=1,RncFunction=1 loadSharingRrcEnabled 0

◦ lset ManagedElement=1,RncFunction=1,Handover=1 releaseConnOffset 120

◦ lset ManagedElement=1,RncFunction=1,Handover=1 maxActiveSet 3

◦ Extreme care when changing RNC parameters!!

To modify Ucell/NodeB parameters
 Log into the RNC : amos RNC_NAME
 Load the MO object model: lt all
 lset RncFunction=1,UtranCell=Ucell_Name Parameter_Name Value
  
 Eg

◦ amos RNC01_ER_ADTEL_AD_SER
◦ lt all
◦ lset RncFunction=1,UtranCell=U1037B1 pwrAdm 84
◦ lset RncFunction=1,UtranCell=U1073A1 loadSharingGsmThreshold 75
◦ lset RncFunction=1,UtranCell=U1061A4 sf128Adm 50

 Log into the NodeB : amos RBS_ID

 Load the MO object model: lt all
 lset NodeBFunction=1 dlLicFractBbPool 50 0 50 0
To modify RbsLocalCell parameter

 Log into the NodeB :

 amos RBS_ID
 lt all
 lset NodeBFunction=1,RbsLocalCell=S1C1 maxNumEulUsers 96
 lset NodeBFunction=1,RbsLocalCell=S1C2 maxNumEulUsers 96
 lset NodeBFunction=1,RbsLocalCell=S1C3 maxNumEulUsers 96
Running Script to make changes on multiple ucells
 Prepare the script and save it as text file
 Eg 1037_pwrAdm.txt
 lset RncFunction=1,UtranCell=U1037B1 pwrAdm 84
 lset RncFunction=1,UtranCell=U1037B2 pwrAdm 84
 lset RncFunction=1,UtranCell=U1037B3 pwrAdm 84
  
 Save the file to your home directory in OSS using FTP client
 /home/etfitmer/1037_pwrAdm.txt
  
 Open command line terminal in OSS [ Right click in desktop->Open Terminal]
  
 Issue the command at the prompt:
 run file_path_command_script
 run /home/etfitmer/1037_pwrAdm.txt
Using amosbatch to make changes on multiple NodeB’s

 
 mobatch [options] sitefile command(s)|commandfile|commanddir [logdirectory]
  
 The first argument is the sitefile. The sitefile contains the list of sites to connect to.
 Each line in the sitefile contains:
 The IP/ or site names whose IP address are definedin the IP database file.
  
 Options may also be specified to the mobatch command these are:
 -t (minutes) - This allows the user to specify the number of minutes before the mobatch
command times out. If this value is set to 0 the command will never time out. A default time
out of 20 minutes is configured in AMOS.
◦ -p (processes) - This specifies the maximum number of AMOS sessions that will run in
parallel, by default a maximum number of 10 processes can be started.
  
 If a directory is given, then a different commandfile will be used for each Network Element,
the name of each commandfile should be network-element-name.cmd or network-element-
name.mos, the Network Element-name should be the same as given in the sitefile.
  
 If the Network Element-name is rbs602 then the commandfile should be rbs602.cmd or
rbs602.mos and it will be run exclusively against that Network Element.
Using amosbatch to make changes on multiple NodeB’s
  Save the command file in txt format to your home directory in OSS
 Eg
 maxNumEulUsers_96_Aug19.txt
 lt all
 lset NodeBFunction=1,RbsLocalCell=S1C1 maxNumEulUsers 96
 lset NodeBFunction=1,RbsLocalCell=S1C2 maxNumEulUsers 96
 lset NodeBFunction=1,RbsLocalCell=S1C3 maxNumEulUsers 96
 q
 Save the site file in txt format where the above command is to be executed to your home
directory in OSS 
 maxNumEulUsers_site_list_Aug19.txt
 211027
 211028
 211029
 211035
 211042
 211044
 Open command terminal in OSS
 amosbatch /home/etfitmer/ maxNumEulUsers_site_list_Aug19.txt /home/etfitmer/
maxNumEulUsers_site_list_Aug19.txt
Abort an MO command

 To abort an MO command (like get/st/set/acc...), two steps are needed:

 First type Ctrl-Z, to suspend moshell.

 Then, at the unix prompt, create an empty file /tmp/xxxx (where xxxx is the process
number indicated in moshell menu and in the window’s title bar) and resume moshell. This is
done with the following command:

 touch /tmp/xxxx ;
Using OSS Element Manager to make parameter changes

 OSS Common Explorer (CEX)

 Right-click in the Topology view-> Launch-> RNC Element Manager
 From the drop down list, select Radio Network
 Browse to the Utracell MO
 MO Properties View on the right side; Attributes Tab lists parameter and values
 Change the desired parameter
 Apply
 Confirm using command line interface
  
 get utrancell=u1091a5 loadsharing*

 get utrancel sinter !10

Thank you