Baseband Integration Remote Procedure For OSS-RC

https://nrocms.ericsson.
net
Baseband Integration – Remote Procedure for OSS-RC

Revision - C
ERICSSON
For Software Release(s): 17.Q1,16B,17.Q3,17A,17.Q2,17.Q4
Published: Feb 07, 2018
IPR
NRO Deployment Document (NDD)
7/1543-1/LZA 905 5680
Copyright Statement: This NDD is developed by Ericsson for Ericsson's use in the Installation, Configuration and
Implementation of Ericsson network elements. This work product represents Intellectual Property belonging to
Ericsson and is only to be used pursuant to contracts between Ericsson and the customer.
7/1543-1/LZA 905 5680

2020© Ericsson AB kamel.afilales@ericsson.com
Table of Contents
General Information.....................................................................................................................................................3
Purpose ....................................................................................................................................................................3
Intended Audience ...................................................................................................................................................3
ERICSSON
Change Request Process ..........................................................................................................................................3
Overview ......................................................................................................................................................................3
Overview of Activity .................................................................................................................................................3
Initial Conditions ......................................................................................................................................................3
Post Conditions ........................................................................................................................................................4
Services Inclusions, Exclusions, and Assumptions....................................................................................................4
Inclusions..............................................................................................................................................................4
IPR
Assumptions.........................................................................................................................................................4
Service Impacts ........................................................................................................................................................4
Coordination ............................................................................................................................................................4
Terminology .............................................................................................................................................................5
Usernames and Passwords.......................................................................................................................................5
Prechecks .....................................................................................................................................................................5
Verify Templates exist in OSS Common Explorer.....................................................................................................6
Verify Baseband Software and License exist in SHM .............................................................................................15
LMT Integration..........................................................................................................................................................22
Integration Files .....................................................................................................................................................23
Preparing BSIM for Baseband Integration..............................................................................................................24
LMT Integration Onsite Configuration .......................................................................................................................39
Integration Files .....................................................................................................................................................39
Verify Connectivity to Baseband from OSS-RC.......................................................................................................40
Apply ARNE script on the OSS-RC...........................................................................................................................42
ARNE Import file options....................................................................................................................................44
Synchronize the Baseband node to the OSS-RC.....................................................................................................45
Application of TN/RN and post installation scripts in moshell or netconf format .................................................49
Baseband Integration Postchecks ..............................................................................................................................62
7/1543-1/LZA 905 5680
© Ericsson AB 2020 kamel.afilales@ericsson.com 1
Apply Configuration File on RNC for WCDMA nodes .............................................................................................63
Requesting BSC configuration updates for GSM nodes .........................................................................................64
Backup the Baseband to the OSS-RC using SHM....................................................................................................64
Integration Postchecks...........................................................................................................................................68
Inform Field Technician that the site is ready for call testing ................................................................................68
ERICSSON
Appendices.................................................................................................................................................................69
Application of Bulk CM scripts using Planned Configuration Administration (PCA) ..............................................69
Importing of a Bulk CM script into a PCA ...............................................................................................................69
Activation of a Bulk CM script using a PCA.............................................................................................................79
Additional Bulk CM Files for Mixed Mode Deployments .......................................................................................86
Digital Unit Backup to the OSS-RC..........................................................................................................................87
Appendix - Intellectual Property Rights (IPR) .........................................................................................................87
IPR
Glossary......................................................................................................................................................................88
7/1543-1/LZA 905 5680

General Information
Purpose
This document provides the information and procedures needed to perform Baseband node
ERICSSON
integration on the OSS-RC. It applies to Baseband 5216/5212, Baseband 6620/6630, and
Baseband C608 nodes. It covers "LMT Integration"and "LMT Integration Onsite Configuration"
scenarios. Zero Touch Integration is covered in a separate NDD called Baseband Integration –
Zero Touch Remote Procedure for OSS-RC.
Intended Audience
 Remote Integration Engineer with access to OSS-RC
Change Request Process
IPR
If you have comments or corrections for this document, please click the Suggest a Change
button below the section you wish to update.
Overview
Overview of Activity
Before the integration is initiated, configuration files need to be obtained from engineering and
stored on the OSS-RC server. Please contact your site lead or project manager to obtain the
latest configuration files for your site.
In case of migration, the remote integration engineer will backup the configuration from the
existing DUx to the OSS-RC, prior to the shutdown of traffic and replacement of the node by the
onsite technician.
The onsite technician needs to complete the onsite portion of the Baseband integration
procedure in coordination with executing the procedures in this document by the remote
Integration engineer. The onsite technician could also provide a copy of the onsite
AutoIntegration log for reference of the activity done onsite.
Initial Conditions
A new greenfield integration or a site migration (DUx to Baseband) is scheduled.
7/1543-1/LZA 905 5680

The Baseband Integration – Onsite Procedure has been or is being performed in coordination
with the activities outlined in this document.
Post Conditions
RBS is ready for service traffic testing.
ERICSSON
Services Inclusions, Exclusions, and Assumptions
Inclusions
The local Ericsson Engineering team will provide the network configuration scripts
to be loaded for each site. A list of these files can be found in the procedures
sections of this document.
The remote network integrator must have access to the following software/hardware and be
familiar with it’s use.
IPR
 Access to the OSS-RC server GUI
 Access to the OSS-RC server command line terminal
Assumptions
This document assumes all equipment is currently in proper working order and is either
alarm free or the customer is aware of any known issues and has made Ericsson and all
stakeholders associated with the execution of this document aware of the known
alarms/issues.
Service Impacts
In case of a DUx migration to Baseband, all traffic on the DUx will be down approximately 2
hours before the new Baseband module can take new calls. This downtime includes time for the
physical removal of DUx and the installation of the Baseband node. The integration portion of the
activity takes 35 to 45 minutes. This NDD is to be performed during a low traffic period as a
precautionary measure. All service impacting work should be completed 30 minutes prior to end
of maintenance window.
Note: Cell downtime is 2 hours or less if the time is counted between lock cell to unlock cell, and not
between first script to last script. Lock cell is the time when the last DUx node EUtranCellFDD is locked.
And unlock is the time when the first Baseband EUtranCellFDD is unlocked.
Coordination
The following users are involved in the integration process.
7/1543-1/LZA 905 5680
Warehouse Technician (if applicable)
 Performs all preparation activities at the warehouse prior to node being deployed to
site.
Field Technician
ERICSSON
 Performs all activities on-site
Remote Integration Engineer
 Plans the node integration and prepares configuration data and involved servers and
services.
OMC Technician
 Monitors the network from an Operation and Maintenance Center (OMC)
IPR
Terminology
The table below shows a list of some of the old integration methods and their corresponding new
names starting in release 16B and onward.
Old Name New Name

Auto integration without laptop Zero Touch Integration
Warehouse integration/installation Zero Touch Integration, off-site pre-configuration
Auto integration with laptop LMT Integration
Semi-automatic/automated integration LMT Integration, on-site configuration
Usernames and Passwords

rbs/rbs is the Baseband local maintenance username and password that is used in this
document. Check with you project lead if your region, market, or customer is using a different
local maintenance username and password for the Baseband.
Prechecks
The Ericsson Radio Systems – Go To Market (ERS-GTM) document contains a section for
System level prechecks that need to performed on the OSS-RC in preparation for Baseband
Integration. These system level checks require root access to the INFRA and OMSAS servers on
the OSS-RC and they are usually performed by the customer or the OSS-RC administrators.
7/1543-1/LZA 905 5680
In addition, the Baseband Radio Node End To End Integration Guide 25/1553-CNA 403 1646
Uen BB, which can be found in CPI, contains procedures that can be used by the OSS-RC
administrators to prepare the server for Baseband integration.
Please note that Zero Touch integration for Baseband nodes with GSM Radio Access
Technology is supported starting release 17A and above.
ERICSSON
Perform the procedures below to verify that the needed Node templates, software, and licenses
exist on the OSS-RC before starting the node integration.
Verify Templates exist in OSS Common Explorer

Use the following procedure to verify that the ARNE, Site Installation File, and OSS Node
Protocol templates exist in the Utilities tab in OSS Common Explorer.
Verifying Templates in OSS Common Explorer
Step Task/Observation
IPR
Connect to the OSS-RC server and open the OSS Common Explorer GUI window.
Note: OSS Common Explorer GUI is not the same as OSS Explorer. Make sure you select OSS
Common Explorer from the launch menu on the OSS-RC.
2 Click on "View" from the top window menu and select "Utilities".
7/1543-1/LZA 905 5680

ERICSSON
IPR
The OSS-RC comes with default templates which are owned by "nmsadm". You can sort the
template list by owner to see the standard ones available. It is also possible to have custom
templates imported into the utility list for your specific market. Those templates can be
generated by the PCI scripting tool which also generates node configuration scripts.
4 Look for the ARNE template name that will be used with Baseband integration in your market.
7/1543-1/LZA 905 5680

You can use the search function in this window to help you find the template you need.
Check with your next level of support if you are not sure which ARNE template you need to
use.
ERICSSON
IPR
If you are provided the template xml file that you wish to use for your market, you can import
it into the Utilities tab by clicking on the "Add new Template" icon.
7/1543-1/LZA 905 5680

Click "Import..." button in the pop-up window.
ERICSSON
6
IPR
Browse through the filesystem folders to where the template xml file is stored.
7
Note: You need to sftp the template xml file(s) to the OSS-RC prior to importing.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Select the filename and click "OK".
9 Give the new template a name and select the appropriate "Domain" and "Type" fields. For
7/1543-1/LZA 905 5680

ARNE templates, select "ARNE" for the domain and type "LRANRadio".
ERICSSON
IPR
Click the "Schema..." button and select the appropriate .xsd schema file for your template.
For ARNE template, the schema filename can be found in the "xsi:schemaLocation=" field
10
The needed schema filename for the template can be found in the "xsi:schemaLocation="
11
field in the template xml file content. You can view the content of the xml file on your PC or in
7/1543-1/LZA 905 5680
Solaris OS by using "cat" or "more" commands. For Baseband ARNE templates, we typically
use the "dg2NodeTemplate.xsd" schema file.
ERICSSON
IPR
Browse through the filesystem folders to where the schema xsd file is stored.
12
13 Select the filename and click "OK".
7/1543-1/LZA 905 5680

ERICSSON
IPR
Back in the "Add a New Template" window, click on "Validate..." button to validate the
selected template against the selected schema file. A window should up indicating that the
"Template Validated". If the template fails validation, please contact your next level of support
or the engineering team that provided you the template.
14
15 Click "OK" to acknowledge the validation window and then click "Add" to import the template
7/1543-1/LZA 905 5680
into the OSS Utilities.
ERICSSON
IPR
Repeat the same steps above for the Site Installation File (SIF) template. If template import is
required, select "FileMgr" for the Domain field and select Type "RadioSiteInstall". For
Baseband Site Installation templates, we typically use the "SiteInstallation.xsd" schema file.
16
17 Repeat the same steps above for the OSS Node Protocol template. If template import is
7/1543-1/LZA 905 5680
required, select "FileMgr" for the Domain field and select Type "OSSNodeProtocol".
ERICSSON
IPR
Note: For any release of OSS “Security Enrollment” can be inside the SiteBasic file of the
Baseband node. Starting in release 16B the “Security Enrollment” can be separated from
SiteBasic file and into an OssNodeProtocol.xml file. This separation is optional and
the OssNodeProtocol.xml file can be generated by the PCI tool. Starting in release 17A, the
BSIM tool generates the OSSNodeProtocol.xml file for Zero Touch and LMT integration
scenarios. In order to do this, BSIM requires having an OSS Node Protocol template in the
Utilities tab. This template can be generated by the PCI tool as well and imported into the
OSS Common Explorer Utilities.
Depending on the Radio Access technology being deployed, there may be additional
18 templates required for node integration. Please use the same steps above to verify or import
any other required templates for your specific deployment scenario.
Verify Baseband Software and License exist in SHM

Use the following procedure to verify the Baseband software and license have been imported
into the Software and Hardware Manager (SHM) application on the OSS-RC.
Verifying the Baseband Software and License exist in the SHM
1 Connect to the OSS-RC server and open a web browser such as FireFox
2 Put the following in the address field of the web browser:
7/1543-1/LZA 905 5680
https://mashost:51831/NSS-Client/
ERICSSON
IPR
Login to the Software Hardware Manager (SHM) using the OSS-RC username and
3
password.
4 Click on "Upgrade" tab in the Software Hardware Manager window.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Click "Upgrade Packages" button on the top right hand side of the window.
In this window you will see a list of node software packages that have been imported into the
6 Software Hardware Manager application. You can sort the Name, ME Type, Description,
Imported by, and Date imported.
7/1543-1/LZA 905 5680

ERICSSON
IPR
To get more information on a particular package, click on "More info" link on line row
associated with your package.
In the pop-up window, you can see the Product Number and Revision associated with the
8
package. Verify that the package used by your Baseband node is available in the list.
7/1543-1/LZA 905 5680

ERICSSON
IPR
You can import a software zip package into the SHM list if you have the software zip package
and you have put it on the OSS-RC. Click the "import new" button on the top right hand side
of the window and follow the prompts to import the software.
10 To check licenses, click on the "License" tab.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Use the "Managed Element" field, to filter on the node for which you are checking. Hit enter
after typing the node name to activate the filter.
11
You can select the license entry that you want, and click on "view" button to see more details
12
related to the license.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Click "close" to quit out of the LKF Details pop-up window after looking at the desired license
details.
13
You can import a license file into the SHM list if you have the .lkf or .xml file and you have put
14 it on the OSS-RC. Click the "import" button on the top right hand side of the window and
follow the prompts to import the license.
7/1543-1/LZA 905 5680

ERICSSON
IPR
LMT Integration
This option allows the onsite field technician to use a "SiteInstallation.xml" file to perform the
node integration. This site installation file contains the information that the Baseband needs to
reach the remote SMRS (Software Management Repository Services) server. The Baseband
requires a functioning backhaul connection that will allow it to reach the SMRS server and
perform the integration automatically.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Integration Files
Depending on the integration method being used, the On-site Technician and the Remote
Integration Engineer will have a different set of configuration files. Below is a list of files needed
for LMT Integration.
LMT Integration Files

Files provided to the Onsite Technician:
 Site Installation File (xml)
Files provided to the Remote Integration Engineer:
 BSIM import file (xml)

7/1543-1/LZA 905 5680
 ARNE script (xml)
 RBS Summary file (xml)
 Site Equipment file (xml)
 Site Basic file (xml)
ERICSSON
 OSS Node Protocol file (xml)
 Software Upgrade Package file (zip)
 License Key File (xml)
 Transport Network (TN) file (Bulk CM)
 Radio Network (RN) files (Bulk CM)
IPR
 Feature Activation file (Bulk CM)
 Other optional site specific files (Bulk CM)
Preparing BSIM for Baseband Integration

The following procedure shows how to prepare for Baseband integration using the BSIM tool in
the OSS Common Explorer. The BSIM tool generates the SiteInstallation.xml file that is used
onsite with the Network Loader Web UI.
Setup BSIM for LMT Integration
1
7/1543-1/LZA 905 5680

ERICSSON
IPR
2 Click on "View" from the top window menu and select "BSIM"
7/1543-1/LZA 905 5680

ERICSSON
IPR
3 Click on Add RadioNode tab
7/1543-1/LZA 905 5680

ERICSSON
IPR
4 Click on the add icon in the Nodes area of the window
7/1543-1/LZA 905 5680

ERICSSON
IPR
5 Navigate to where the BSIM xml file is located and click on the file to select it.
7/1543-1/LZA 905 5680

ERICSSON
IPR
6 Click ok to import the BSIM xml file.
7 Give a name to the Planned Configuration Name field
8 Click on "Validate Nodes" button
7/1543-1/LZA 905 5680

ERICSSON
IPR
9 Verify that all selected RadioNodes validate ok.
7/1543-1/LZA 905 5680

ERICSSON
IPR
10 Click "Add Nodes" button
7/1543-1/LZA 905 5680

ERICSSON
IPR
11 Click "OK" at the "Confirm Add Nodes" pop-up message.
7/1543-1/LZA 905 5680

ERICSSON
IPR
12 Verify the "Add nodes" command is successful
7/1543-1/LZA 905 5680

ERICSSON
IPR
13 Select Node Integration tab
7/1543-1/LZA 905 5680

ERICSSON
IPR
14 Right click on the newly added node and select "No Hardware Bind"
7/1543-1/LZA 905 5680

ERICSSON
IPR
Select the Site Installation Template that is appropriate for your market. In the example
15
below, we choose "SiteInstall_RadioExample_WithoutIPSec".
7/1543-1/LZA 905 5680

ERICSSON
IPR
Input the template variables specific to the site.Depending on the template, there may be
16
additional or different variables then what is in the capture below.
7/1543-1/LZA 905 5680

ERICSSON
IPR
17 Note the filename and path of where the site_installation file is going to be saved.
18 Click "OK" to acknowledge the "No Hardware Bind" window.

Fetch the SiteInstallation.xml file from the OSS-RC and arrange for it to be delivered to the
19
Onsite Field Technician.
The Site Installation File (SIF) that is generated in the procedure above, is sent to the onsite field
technician to apply to the Baseband node and perform the node integration. Once that is
complete, the remote integration engineer on the OSS-RC will need to do the following:
 Verify node connectivity from the OSS-RC and check synchronization. Procedures "Verify Connectivity to
Baseband from OSS-RC" and "Synchronize the Baseband node to the OSS-RC" can be referenced to
perform these tasks.
 Perform the "Baseband Integration Postchecks" section of this NDD.
7/1543-1/LZA 905 5680

LMT Integration Onsite Configuration
This option allows the onsite field technician to download the Site_Basic, Site_Equipment,
License file (LKF), and software Upgrade Package from his laptop to the Baseband node onsite.
The rest of the integration, which involves the application of TN/RN and post installation scripts,
is performed remotely from the OSS-RC.
Integration Files ERICSSON

IPR
Depending on the integration method being used, the On-site Technician and the Remote
Integration Engineer will have a different set of configuration files. Below is a list of files needed
for LMT Integration On-site configuration.
LMT Integration On-site Configuration Files

Files provided to the Onsite Technician:
7/1543-1/LZA 905 5680

 RBS Summary file (xml)
 Site Equipment file (xml)
 Site Basic file (xml)
 OSS Node Protocol file (xml)
ERICSSON
 Software Upgrade Package file (zip)
 License Key File (xml)
Files provided to the Remote Integration Engineer:
 ARNE script (xml)
 Transport Network (TN) file (Netconf, Moshell, or Bluk CM)
IPR
 Radio Network (RN) files (Netconf, Moshell, or Bluk CM)
 Feature Activation file (Netconf, Moshell, or Bluk CM)
 Other optional site specific files (Netconf, Moshell, or Bluk CM)
Verify Connectivity to Baseband from OSS-RC

This section provides the basic instructions to ping and amos to the Baseband unit from the
OSS-RC.
Verify that you can moshell to the Baseband from the OSS-RC
Connect to the OSS-RC server and open a terminal window by right clicking on the desktop
1 and selecting "Open Terminal".
7/1543-1/LZA 905 5680

ERICSSON
IPR
From the terminal window, ping the Baseband OAM IP address:
ping xxx.xxx.xxx.xxx
Note: Replace the xxx.xxx.xxx.xxx with the actual OAM IP address of the Baseband.
If the ping test fails, then contact the onsite technician and the transport team if necessary to
3
help troubleshoot connectivity to the Baseband node.
7/1543-1/LZA 905 5680
If the ping test is successful, then proceed to amos to the Baseband unit from the OSS-RC
terminal window.
amos xxx.xxx.xxx.xxx
ERICSSON
4
IPR
5 Type q to exit from amos shell.
Apply ARNE script on the OSS-RC

The ARNE script will add the Baseband Network Element to the OSS-RC database. ARNE
stands for Add Remove Network Element. In case of DUx to Baseband migration, there may be
2 ARNE scripts provided; one to remove the DUx, and another to add the Baseband to the OSS-
RC database. For greenfield nodes, it is possible to run the ARNE script prior to node integration
being performed onsite.
Apply ARNE script on the OSS-RC
1
and selecting "Open Terminal".
7/1543-1/LZA 905 5680

ERICSSON
IPR
From the terminal window, ssh to the master host on the OSS-RC server:
ssh mashost
Note: Enter your OSS-RC server password when prompted
Change directories to where the ARNE script is stored on the OSS-RC.

3
7/1543-1/LZA 905 5680

cd /"path"
Note: Replace "path" with the actual file path to the ARNE script.
Use the ls *.xml command to list the xml files in the current directory
3
ls *.xml
ERICSSON
Note: Look for the import file name in the output list.
Import the ARNE file into the OSS-RC database using the following command:
/opt/ericsson/arne/bin/import.sh -import -f "XML file name.xml"
Note: Replace "XML file name" with the actual ARNE script file name.
IPR
4
ARNE Import file options

The following table shows the various options associated with the import command. It is
provided here as a reference only.
7/1543-1/LZA 905 5680
Import.sh Option reference
Option Description
-f "xml file
ERICSSON
File to import. The XML file to parse
name.xml"
-i_nau (Node Already Used) Ignore errors about the attributes SubNetwork
userLabel, Site userLabel, ManagedElementID, ipaddress, group userLabel or
-i_nau
ftpService userLabel name already in use, reported as warning instead, does
not affect exit code.
-import Imports the file specified by -f.
Used only to validate all Network Elements.
r1: This stops the import after the first error.
rall: report all errors.
IPR
Validation of delete XML files checks for syntax errors and the following
-val:[r1|rall] semantic errors/warnings:
• the import version in the XML file must match the DTD version (error)
• the object being deleted does not exist (warning)
However, the import itself will restrict changes that could lead to an
inconsistent model.
Disable the Model upgrade operation. This option should not be used in normal
-notrans
operation.
This option is used to get the ARNE Rules Engine tracing in the import log file.
-traceon This option should not be used in normal operation unless Rules Engine
tracing is required.
Synchronize the Baseband node to the OSS-RC

This section provides the basic instructions to Synchronize the Baseband unit to the OSS-RC
database.
Synchronize the Baseband node to the OSS-RC
1
7/1543-1/LZA 905 5680
ERICSSON
IPR
In the "Topology" panel, click on the down arrow right underneath the word "Label"
3 Select "LTE" or "WCDMA" depending on the type of node you are integrating.
7/1543-1/LZA 905 5680
ERICSSON
IPR
Still in the "Topology" panel, click on the right pointing triangle to expand the child elements.
7/1543-1/LZA 905 5680

5 Look for your node name in the list of Managed Elements and right click on it.
Select "Synchronize Node" from the menu that pops up.
ERICSSON
6
IPR
7 Wait about 2 minutes for the Synchronization to take place.
Check the Synchronization status of the element by looking in the "Properties" panel and in
8 the "Configuration" tab. You may need to scroll down a little bit to see element's
"connectionStatus" and "mirrorMIBsynchStatus".
7/1543-1/LZA 905 5680

ERICSSON
IPR
Application of TN/RN and post installation scripts in
moshell or netconf format
TN/RN and post Integration scripts such as feature activation and cell relations scripts can be
delivered in one of the following 3 formats:
 Netconf format
 Moshell format
 Bulk CM format
The following procedure shows the steps for applying scripts in netconf or moshell format.
Please use the Appendix entitled "Application of TN/RN scripts using Bulk CM" to apply scripts
that are delivered in Bulk CM format.
7/1543-1/LZA 905 5680

Note: The first 2 digits at the start of the file name indicate the order in which the files are
applied. Always run the Transport Network (TN) script first, before the Radio Network (RN)
script.
Application of moshell or netconf scripts using amos
ERICSSON
IPR
1
In the terminal window, change directory to the where the site scripts are located.
2
cd /"path"
Note: Replace "path" with the actual file path to the scripts
7/1543-1/LZA 905 5680

amos to the RBS using the Baseband OAM IP address:
amos xxx.xxx.xxx.xxx
ERICSSON
3
IPR
Once connected to the Baseband, type: lt all
4 When prompted, type the Baseband's local maintenance username and password.
Note: "lt all" command loads the MO tree and builds the proxy table.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Execute the Transport Network (TN) script that is provided for the node.
For scripts in moshell format, use the "run" command below:

>run TN.mos
5
For scripts in netconf format, use the "netconf" command below:
>netconf TN.xml
Note: Contact your next level of support if you encounter any errors during the execution of this
procedure.
Save an image on the Baseband after the execution of each script.
6
7/1543-1/LZA 905 5680

>cvms TN_Applied
ERICSSON
IPR
Verify the image is saved by listing all the saved image names on the Baseband using the
command:
7
>cvls
7/1543-1/LZA 905 5680

ERICSSON
IPR
Execute all Radio Network (RN) scripts that are provided for the node.

>run RN.mos
8
>netconf RN.xml
procedure.
9
>cvms RN_Applied
7/1543-1/LZA 905 5680

ERICSSON
IPR
command:
>cvls
10
Execute the Feature Activation script.

11
7/1543-1/LZA 905 5680

>run FeatureActivation.mos

>netconf FeatureActivation.xml
ERICSSON
procedure.
>cvms FeatureActivation_Applied
IPR
12
command:
13
>cvls
7/1543-1/LZA 905 5680

ERICSSON
IPR
Restart the node manually after the Feature Activation completed
>acc FieldReplaceableUnit=1 restartunit
14
The reboot process will prompt for several variables. Type "y" when prompted to confirm the
restart. Then type "1" to indicate "RESTART_COLD", type "0" for
"PLANNED_RECONFIGURATION", and finally type a text string indicative of the reason for
the restart; for example, "updates".
7/1543-1/LZA 905 5680

ERICSSON
IPR
Once connected to the Baseband, type: lt all
When prompted, type the Baseband's local maintenance username and password.
15
Execute any post integration scripts provided for the node.
16
>run PostIntegration.mos
7/1543-1/LZA 905 5680

>netconf PostIntegration.xml
procedure.
ERICSSON
>cvms PostIntegartion_Applied
17
IPR
command:
18
>cvls
7/1543-1/LZA 905 5680

ERICSSON
IPR
Execute any cell relations scripts provided for the node.

>run CellRelations.mos
19
>netconf CellRelations.xml
procedure.
20
>cvms CellRelation_Applied
7/1543-1/LZA 905 5680

ERICSSON
IPR
command:
21
>cvls
7/1543-1/LZA 905 5680

ERICSSON
IPR
Note: There will be multiple Radio Network (RN) files and multiple post installation scripts in
Mixed Mode deployments. The first 2 digits at the start of the file name indicate the order in
which the files are applied. Use the same procedure above to apply any additional moshell or
netconf files provided for Mixed Mode node Integration.
Baseband Integration Postchecks

Once the Baseband is integrated using either the "LMT Integration" or "LMT Integration Onsite
Configuration" methods, the remote integration engineer should perform the following:
 Apply RNC scripts in case the Baseband is providing WCDMA radio access service.
 Request or perform BSC changes in case the Baseband is providing GSM radio access service.
 Create a configuration backup on the Baseband node and transfer it to the OSS-RC.
 Perform any market or customer specific post integration activities.
7/1543-1/LZA 905 5680

 Inform onsite field technician that the site is ready for service call testing.
Apply Configuration File on RNC for WCDMA nodes

The integration of WCDMA node requires the application of IUB configuration scripts to the
corresponding RNCs. The configuration scripts can be delivered in one of 2 formats:
ERICSSON
 Bulk CM RNC configuration file
 Moshell RNC configuration file
If the RNC(s) configuration files are delivered in Bulk CM format, please refer to the procedure
entitled "Application of Bulk CM scripts using Planned Configuration Administration (PCA)".
If the RNC(s) configuration files are delivered in Moshell format, please use the procedure below.
Note: The application of RNC scripts is only applicable for WCDMA nodes.
IPR
Configuration on RNC for WCDMA nodes via moshell commands/script
1
In the terminal window, change directory to the where the site scripts are located.
2 >cd /"path"
Note: Replace "path" with the actual file path to the scripts
amos to the RNC using the OAM IP address:
3 >amos xxx.xxx.xxx.xxx
Note: Replace the xxx.xxx.xxx.xxx with the actual OAM IP address of the RNC.
Once connected to the RNC, type: lt all
4
Execute the RNC configuration Script

5
>run RNCxxxxx.mos
7/1543-1/LZA 905 5680

procedure.
6 Repeat the step above for all RNC scripts associated with you node.
7 Type "exit" to quit out of moshell.
ERICSSON
Requesting BSC configuration updates for GSM nodes
The integration of a GSM node may require configuration changes on the associated BSC(s).
The integration engineer should check with the customer or project leads to make sure those
changes have been completed for the GSM node being added to the network. For more
information on BSC changes please refer to Baseband Integration - GSM BSC Procedure.
Backup the Baseband to the OSS-RC using SHM
IPR
This section provides the basic instructions to backup the Baseband unit to the OSS-RC server.
Backup the Baseband node to the OSS-RC
1 Connect to the OSS-RC server and open a web browser such as FireFox
Put the following in the address field of the web browser:
2
https://mashost:51831/NSS-Client/
7/1543-1/LZA 905 5680

ERICSSON
IPR
Login to the Software Hardware Manager (SHM) using the OSS-RC username and
3
password.
Click on "Inventory" tab
5 Expand the Element Tree and Select the Node you wish to backup to the OSS-RC
7/1543-1/LZA 905 5680

ERICSSON
6 Click on "Backup" in the right Panel of the browser window
Select the Node and the Backup name that you wish to export to the OSS-RC
IPR
7
8 Click on "Export to OSS"
7/1543-1/LZA 905 5680

ERICSSON
Click on "Export"
IPR
9
10 Watch the Export Backup Progress until it reaches 100%
7/1543-1/LZA 905 5680

ERICSSON
IPR
Integration Postchecks
Integration postchecks need to be performed on each Baseband node before it can be called
Integration complete. These postchecks vary depending on the region, market, and customer.
During project planning, the project leads, and the customer agree on a list of postchecks that
the Integration Engineer would need to perform on the node. Postchecks could be prepared in
the form of scripts. Please check with you project leads if you are not sure which postchecks are
required for your site.
Inform Field Technician that the site is ready for call testing
Once all postchecks have completed successfully, the remote integration engineer should inform
the onsite field technician that the site is ready for call testing.
7/1543-1/LZA 905 5680

Appendices
Application of Bulk CM scripts using Planned
Configuration Administration (PCA)
ERICSSON
Use the two procedures below to apply Bulk CM scripts to a node using a Planned Configuration
Area (PCA) on the OSS-RC. These two procedures can be used to apply Bulk CM scripts to G2
nodes and to the WCDMA RNC.
Importing of a Bulk CM script into a PCA

The screen captures in the procedure show the application of the Transport Network (TN) script.
The same steps in this procedure can be used to import any post install scripts in Bulk CM
format.
IPR
Import Bulk CM scripts into a Planned Configuration
7/1543-1/LZA 905 5680

Click on "View" from the top window menu and select "Planned Configuration Administration"
ERICSSON
2
IPR
3 Click on the New Planned Configuration icon to create a new PCA
7/1543-1/LZA 905 5680

ERICSSON
IPR
Enter a Planned Configuration Name and Description then click OK button
4
Note: Always run the Transport Network (TN) script first, before the Radio Network (RN) script.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Click on "General" in the "Properties" tab in the lower panel of the display and change the
5
"ActivationScheme" to "NetworkElement"
7/1543-1/LZA 905 5680

ERICSSON
IPR
6 Save the PCA change by clicking on the save icon in the properties tab.
7/1543-1/LZA 905 5680

ERICSSON
IPR
From the PCA tab, Right click on the new Planned Configuration Name you just created, then
7
select import
7/1543-1/LZA 905 5680

ERICSSON
IPR
Click on the Browse icon to navigate to the directory and script location in the OSS-RC file
8
system.
7/1543-1/LZA 905 5680

ERICSSON
IPR
9 Select the script you wish to import and click OK.
7/1543-1/LZA 905 5680

ERICSSON
IPR
10 Click on "import" to proceed.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Verify that the Bulk CM import Status is Successful.
11
procedure.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Activation of a Bulk CM script using a PCA
The screen captures in the procedure show the application of the Transport Network (TN) script.
The same steps in this procedure can be used to activate any post install scripts in Bulk CM
format.
Th previous procedure had the steps to import the Bulk CM script into a Bulk CM Planned
Configuration Administration (PCA); this procedure shows how to activate that PCA.
Activate Bulk CM scripts using a Planned Configuration
1
7/1543-1/LZA 905 5680

ERICSSON
IPR
Click on "View" from the top window menu and select "Planned Configuration Administration"
7/1543-1/LZA 905 5680

Right click on the Planned Configuration name that you created in the previous procedure
and select "Activate".
Note: Always run the Transport Network (TN) script first, before the Radio Network (RN) script.
ERICSSON
3
IPR
A new window will pop up. Leave "Create Rollback File" unchecked and click on the "Next" to
4
continue.
7/1543-1/LZA 905 5680

ERICSSON
IPR
5 Verify that "Activate now" is selected and click on "Pre-check" to continue.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Verify that the Pre-check is successful and click on "Activate"
6
procedure.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Verify that the Activation is successful and the Status shows "Complete" and Click on "Next"
7
procedure.
7/1543-1/LZA 905 5680

ERICSSON
IPR
8 Click on "Close" to close the "Activation Summary" window.
7/1543-1/LZA 905 5680

ERICSSON
IPR
Repeat the Import Bulk CM procedure and Activate Bulk CM procedure for the Radio
9
Network (RN) script.
Note: The same steps can be used to apply any post install Bulk CM script provided for this site.
The previous two procedures can be used to applu Bulk CM scripts to a WCDMA RNC. Please
check with your next level of support if you are not sure about the format or procedure you need
to use to apply any of the provided site scripts.
Additional Bulk CM Files for Mixed Mode Deployments

There will be multiple Radio Network (RN) files and multiple post Install scripts in Mixed Mode
deployments. The first 2 digits at the start of the file name indicate the order in which the files are
applied. Use the same Bulk CM procedures above to import and activate any additional Bulk CM
(.xml) files provided for Mixed Mode node Integration.
7/1543-1/LZA 905 5680

Digital Unit Backup to the OSS-RC
This section provides the basic instructions to Backup the Digital Unit (DU) to the OSS-RC
server.
ERICSSON
Backup the DU node to the OSS-RC
1 Connect to the OSS-RC server and open the Software Management Organizer GUI
Select Network from left panel of the window and search for your node name in the middle
2
panel of the window
Select the node you want to backup and click on the "config" tab in the right panel of the
3
window.
Scroll down through the list of CVs on the node and select the one you want to upload to the
IPR
4
OSS-RC
5 Right click on the CV name you want to backup and clock "Upload CVs"
6 Click on the "Jobs" option in the left panel to verify that the upload is successful.
Appendix - Intellectual Property Rights (IPR)

This document contains Ericsson Intellectual Property (IP) also known as Intellectual Property
Rights (IPR). This document was created using modified/selective content from the Telcordia
GR-1275 Central Office/Network Environment Equipment Installation/Removal Generic
Requirements Issue 12.
This document is not intended for use by external customers or any customer delegate, including
Third Party vendors and/or sub-contractors. Review of this document with customers should only
occur with the knowledge, consent and control of Ericsson personnel in a manner where content
is not distributed to the customer.
The following Table of IPR examples is provided as reference information and examples to
identify Ericsson Intellectual Property (IP). This information is provided for use by Ericsson
Customer Unit interfacing functions.
 Detailed Acceptance Plans/Test Cases  Ericsson Developed Tools
 Detailed Assembly  Installation Instructions

Instructions/Diagrams  Commissioning Instructions
7/1543-1/LZA 905 5680

 Cable Diagrams  Integration Instructions
 Connections  Integration files/scripts
 Software upgrade command lines  Copyright material
 Processes  Patent material
ERICSSON
 Configuration files/scripts  Trademark material
 Ericsson Developed Applications (Apps)  Ericsson Radio Frequency Specs
 Industrial design  Debug logs
 Session logs  Detailed Patch Procedures
 Restricted User Level Passwords  Any capture of Ericsson messaging traffic

(i.e. Wireshark)
IPR
 IOT (Inter-Operability Test) and
Integration Processes
Glossary
The Glossary is used to define the Terms and Acronyms used throughout the document.
Term/Acronym Definition
AIWS Auto Integration Web Service
AP Auto Provisioning
ARNE Add Remove Network Element
BSIM Base Station Integration Manager
CA Certificate Authority
CLI Command Line Interface
DU Digital Unit
DUR Document Update Request
ENM Ericsson Network Manager
FTP File Transfer Protocol
G1 Generation 1 node (i.e. DUL / DUS / DUG)
7/1543-1/LZA 905 5680
G2 Generation 2 node (i.e. Baseband 5212/5216, 6620/6630, & C608)
GUI Graphical User Interface
IPR Intellectual Property Rights
L/G LTE / GSM
L/W LTE / WCDMA
ERICSSON
LKF License Key File
LMT Local Maintenance Terminal
NDD NRO Deployment Document
NIC Network Integration Center
NMA Netconf Manager Adapter
OMC Operations and Maintenance Center
OMSAS Operation and Maintenance Security Administration Server
OSS-RC Operations Support System - Radio and Core
IPR
RA Registration Authority
RBS Radio Base Station
RN Radio Network
RRU Remote Radio Unit
SFTP Secure FTP
SIF Site Installation File
SMRS Software Management Repository Services
TN Transport Network
UP Upgrade Package
USB Universal Serial Bus
VC Vendor Credentials
ZT Zero Touch
7/1543-1/LZA 905 5680


Baseband Integration Remote Procedure For OSS-RC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Baseband Integration Remote Procedure For OSS-RC

Uploaded by

Copyright:

Available Formats

https://nrocms.ericsson.

Baseband Integration – Remote Procedure for OSS-RC

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

Change Request Process

7/1543-1/LZA 905 5680

 Access to the OSS-RC server command line terminal

Remote Integration Engineer

 Monitors the network from an Operation and Maintenance Center (OMC)

Old Name New Name

Usernames and Passwords

Verify Templates exist in OSS Common Explorer

Verifying Templates in OSS Common Explorer

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

13 Select the filename and click "OK".

7/1543-1/LZA 905 5680

Verify Baseband Software and License exist in SHM

Verifying the Baseband Software and License exist in the SHM

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

10 To check licenses, click on the "License" tab.

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

LMT Integration Files

 Site Installation File (xml)

Files provided to the Remote Integration Engineer:

 BSIM import file (xml)

 RBS Summary file (xml)

 Site Equipment file (xml)

 Site Basic file (xml)

 Software Upgrade Package file (zip)

 License Key File (xml)

 Transport Network (TN) file (Bulk CM)

 Radio Network (RN) files (Bulk CM)

 Other optional site specific files (Bulk CM)

Preparing BSIM for Baseband Integration

Setup BSIM for LMT Integration

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

7/1543-1/LZA 905 5680

18 Click "OK" to acknowledge the "No Hardware Bind" window.

 Perform the "Baseband Integration Postchecks" section of this NDD.

7/1543-1/LZA 905 5680

Integration Files ERICSSON