RBS Audit with Mobatch

Introduction
In this project, one of the tasks is to audit both utrancell, RNC and RBS parameters.

Both Utrancell and RNC parameters audit are done using Nexplorer with data generated from Kget, which is a straight forward process.
However, for RBS parameter audit, Ranos dump was not available and hence Nexplorer cannot be used to run the RBS parameter audit.

To extract RBS parameter, one need to run moshell to each RBS at a time
On average it will take around 10 minutes (depending on the remote connection speed) to run Moshell, extract the parameters and verify the values for about 20 parameters. This way of auditing the parameter is also prone to error especially when this process is repeated in a large number of RBS.

It was found that Moshell support a script called Mobatch which can be used to automatically access all RBS specify in a text file

Steps to using Mobatch

1. Create one text file (and save this file as e.g rbsname.mos) containing the RBS name/ip address of all the RBS which you want to extract the data from. One line can only contain one RBS name as follows: CA151U CA156U CA157U CA158U CA167U Create another log file (and save this file as rbscommand.mos) which will contain all the command you want to execute Format of the file is as follows: lt all get .cqiAdjustmentOn get . maxhsrate get . flexibleSchedulerOn get . supportof16qam get . maxNumHsdpaUsers get . minDlPowerCapability

2.

3. Copy the two files to the moshell directory

Steps to using Mobatch

4. 5. 6. 7. In the moshell directory, issue the command mobatch rbsname.mos command.mos At the end of the execution, it will display the location where the logs are stored. Go to the output directory There is one log file per RBS

8. Opening each individual file to go through the parameter is time consuming as well Hence, it is recommended to concatenate all the logs into a file with this command cat *.* > output_all.log 9. Alternative, we can grep one parameter at a time and pipe it to a file. E.g. grep minDlPowerCapability *.log >minpwr_all.log CA151U.log:CAS151U> get . minDlPowerCapability CA151U.log:RbsLocalCell=S2C1 minDlPowerCapability 163 CA151U.log:RbsLocalCell=S3C1 minDlPowerCapability 168 CA151U.log:RbsLocalCell=S1C1 minDlPowerCapability 172 CA196U.log:CAS196U> get . minDlPowerCapability CA196U.log:RbsLocalCell=S2C1 minDlPowerCapability 173 CA196U.log:RbsLocalCell=S3C1 minDlPowerCapability 170 CA196U.log:RbsLocalCell=S1C1 minDlPowerCapability 170 10. Open the output file with Excel for further post-procesing

Conclusion
This is a very useful tool which is beneficial in two ways
Reduce the time needed to extract RBS parameters Reduce room for error when checking parameter values as the output file can be opened with Excel for simple analysis and filtering

It is an excellent tool whenever one need to access a big number of RBS for e.g, parameter audit and parameter unification