Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 1 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

5G RAN Integration MOP

5G Radio Node Integration for NR-NSA (LMT Integration)

Preparation
Import License Key File and 5GRadioNode Software Package in SHM in ENM

Detailed procedure described further below.

Prepare AP project for integration

The project concept represents a grouping of nodes to be integrated.

A zip file is used to create the project. This file contains the artifacts required by AP for node integration.

The project structure looks like this:

<<GNB_example_project.zip>>

File examples available in CPI:

[Link]

Go to: 5G Radio Node -> Initial Configuration -> Configuration Files

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 2 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Short file descriptions:

[Link]

Name and description of the AP project.

One project can contain one or several nodes.

[Link]

NodeInfo file details is used by ENM to add the node to ENM and to prepare the files for the integration.

Update the following parameters:

<name>%Node Name%</name> <!-- update! -->

<nodeIdentifier>18.Q4-R8A20</nodeIdentifier> <!-- update! -->

<ipAddress>%Node OAM IP address%</ipAddress> <!-- update! -->

<nodeType>5GRadioNode</nodeType>

<ossPrefix>SubNetwork=%SubNetwork%</ossPrefix> <!-- update! -->

<upgradePackageName>5GRadioNode CXP2010045/5 R11B36 18.Q4</upgradePackageName>

<!-- update! -->

Check nodeIdentifier in ENM CLI:

>> cmedit describe --netype 5GRadioNode -t

Use the value from "Model ID" column, for the Product Identity and Revision which match closest to the NR SW
Package.
The nodeIdentifier is important to get the correct version of the MOM for the SW version to be used on the
node.

Check upgradePackageName in SHM:

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 3 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Site Equiment:

Example file is for BB6630 with one AIR6488 unit connected with 3 RiLinks, to RiPort D, E, F.

Site Basic:

Example file is:

- for IPv4
- with TNB port (10G optical interface)
- with GPS synchronization.

ServiceDiscovery and ServiceDiscoveryServer MOs are included in example file. These MOs are required in NR
node.

TN Bulk Transport:

Create MOs:
• SctpProfile
• SctpEndpoint

RN Bulk GNodeBFunction

Create MOs:
• GNodeBFunction

GNodeBFunction::gnbId should match ENodeBFunction::gNodeBId in anchor LTE node

GNodeBFunction::gNBPlmnId should match ENodeBFunction::gNodeBPlmnId in anchor LTE node
GNodeBFunction::x2SctpEndPointRef and GNodeBFunction::ngcSctpEndPointRef must not reference to the
same SctpEndpoint

RN Bulk SectorCarrier
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 4 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Create MOs:
• GNodeBRpFunction
o TddRadioChannel
o GNodeBSectorCarrier
o GUtranDUCell

GUtranDUCell::cgi must match GUtranCell::cgi which is calculated from gNBPlmnId, gNBId and cellId

RN Bulk GUtranCell

Update and create MOs:

• GNodeBFunction (update)
o GUtranCell (create)
• GNodeBRpFunction (update)
o GUtranDUCell (update)
• SyncSignalDU (update)

RN Bulk PpFunction

Create MOs:
• PpFunction

Execution :
(More detailed procedure described further below)

Order the integration in ENM:

1. Open ENM CLI application in ENM

2. Drag and drop archive [Link] from Explorer window to ENM CLI workarea.

3. Order AutoProvisioning of the GNB with command:

ap order file:"[Link]"

4. Check the status with command:

ap status -n <NodeName>

5. Download the SiteInstall file with command:

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 5 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

ap download -o -n <NodeName>

6. Save the file and provide it to onsite team.

Onsite integration:
1. At the site, connect a laptop to LMT port.
Change laptop IP to [Link]
Turn off firewall

2. Open web browser (use no proxy) and open AutoIntegration GUI:

https:// [Link]/

3. Select LMT integration tab

Browse for the Site install file and fill in SMRS username and password (ENM user with
FIELD_TECHNICIAN role)

4. Click "Download files"

5. When log shows Download completed, the Integrate button will be active.
Click "Integrate"

6. After some minutes the node will reach config level "SITE_CONFIG_COMPLETE"
At this point it is possible to login to the node from remote.
The node will synchronize automatic with ENM and continue with Bulk file configuration.

7. After some more minutes the node will reach "READY_FOR_SERVICE"

At this point the integration is completed.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 6 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

9. Check status in ENM:

ap status -n <NodeName>

The printout should show state Integration Completed

10. Note: If in the AI log the config level shows "OSS_CONFIGURATION_FAILED" and the ENM ap status
command printout shows failure, then check in ENM what failed and then perform ap upload and ap
resume.
More details provided further down.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 7 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

11. Connect to the node by AMOS

Check configuration for uplink (MCG or SCG):

Check GNodeBSectorCarrier and GUtranCell MOs are unlocked and enabled:

LTE configuration for NR-NSA

To use LTE node for NR-NSA the ENDC configuration must be added.
Below are examples of scripts for configuration.

netconf_FeatureState_5G.xml

<ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
<managedElementId>1</managedElementId>
<SystemFunctions>
<systemFunctionsId>1</systemFunctionsId>
<Lm>
<lmId>1</lmId>
<FeatureState> <featureStateId>CXC4012218</featureStateId>
<featureState>ACTIVATED</featureState> </FeatureState> <!-- Basic Intelligent Connectivity -->
</Lm>
</SystemFunctions>
</ManagedElement>
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 8 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

NOTES:
Only Basic Intelligent Connectivity feature is mandatory to get 5G functionality working in eNB. Any case
double check which other features might add values for you customer to get 5G network working optimal
way

netconf_GUtranNetwork.xml
<ManagedElement>
<managedElementId>1</managedElementId>
<ENodeBFunction>
<eNodeBFunctionId>1</eNodeBFunctionId>
<intraRanIpAddressRef>Router=UP,InterfaceIPv4=1,AddressIPv4=1</intraRanIpAddressRef>
<GUtraNetwork>
<gUtraNetworkId>1</gUtraNetworkId>
<ExternalGNodeBFunction>
<externalGNodeBFunctionId>1</externalGNodeBFunctionId>
<gNodeBId>21</gNodeBId> <!-- Must match gNBId in the gNB node -->
<gNodeBPlmnId struct="PlmnIdentity">
<mcc>262</mcc>
<mnc>800</mnc>
<mncLength>3</mncLength>
</gNodeBPlmnId>
<TermPointToGNB>
<termPointToGNBId>1</termPointToGNBId>
<ipAddress>[Link]</ipAddress> <!-- gNB traffic IP -->
<administrativeState>UNLOCKED</administrativeState>
</TermPointToGNB>
</ExternalGNodeBFunction>
</GUtraNetwork>
</ENodeBFunction>
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 9 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

</ManagedElement>

[Link]

<ManagedElement> <managedElementId>1</managedElementId> <ENodeBFunction>

<eNodeBFunctionId>1</eNodeBFunctionId>
<Rcs>
<rcsId>1</rcsId>
<tInactivityTimer>61</tInactivityTimer>
</Rcs>
<EndcProfile>
<endcProfileId>1</endcProfileId>
<meNbS1TermReqArpLev>1</meNbS1TermReqArpLev>
</EndcProfile>
<QciTable>
<qciTableId>default</qciTableId>
<QciProfilePredefined>
<qciProfilePredefinedId>qci9</qciProfilePredefinedId>
<endcProfileRef>ManagedElement=1,ENodeBFunction=1,EndcProfile=1</endcProfileRef>
<dualConnInitUlConf>SCG</dualConnInitUlConf>
</QciProfilePredefined>
</QciTable>
<EUtranCellFDD>
<eUtranCellFDDId>FDD-1</eUtranCellFDDId>
<endcAllowedPlmnList struct="PlmnIdentity">
<mcc>262</mcc>
<mnc>800</mnc>
<mncLength>3</mncLength>
</endcAllowedPlmnList>
</EUtranCellFDD>
</ENodeBFunction> </ManagedElement>
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 10 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Example file from CPI, Bulk format:

<<RN_Bulk_Cm_gNB_in_eNB.xml>>
(Missing eNodeBFunction::intraRanIpAddressRef and QciProfilePredefined::dualConnInitUlConf parameters.)

Auto Provisioning

The flowchart below highlights the main steps involved in Auto Provisioning.

1.1 Auto Provisioning

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 11 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Auto
Provisionin
g

Step Task/Observation

1 Login to the ENM using your username and password.

2 Click on your username in the top right corner of the ENM GUI and select View User Profile
from the drop down menu.

Verify that the user has the following roles required to complete this procedure:
• Operator
• SHM Operator or Administrator
• AMOS Operator or Administrator
• Shell Terminal (SSH) Access
• Topology Browser
• Alarm Monitoring (FM)
• Autoprovisioning Operator or Administrator
• Cmedit_Operator or Cmedit_Administrator
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 12 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

3 Import License Key Files

At the ENM Application Launcher, click on Software and Hardware Manager > License
Administration > View Imported Key Files
Check if the License Key File (LKF) exists for the site.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 13 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

If the LKF is not listed, click on Import Key Files and upload the LKF to ENM.

4 Import Software Package

At the ENM homepage, click on Software and Hardware Manager > Software Administration >
View Software Packages
Check if the required Upgrade Package (UP) is available.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 14 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

If the UP is not listed, click on Import Software Package and upload the UP to the ENM.

5 Open ENM CLI

At the ENM homepage, under Tools, click on Command Line Interface (CLI).
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 15 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

6 Start AutoProvisioning

Locate the AP project zip file on the PC from which you are accessing the ENM
Then drag and drop the project zip file into the ENM CLI workspace.
This will copy the project zip file from the PC into the ENM.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 16 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

7 In the ENM CLI, order the project file to add the new node into the ENM and generate the site
install file.

>> ap order file:<FileName>

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 17 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

8 In the ENM CLI, check the status for the project and the node to be integrated.
At this point it will show the integration status before the node is integrated on site.

The node state should be: Order Completed

The last task at this stage should be: Node Up Notification with a status of Waiting

>> ap view

>> ap status -p <ProjectName>

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 18 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

>> ap view -n <NodeName>

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 19 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

>> ap status -n <NodeName>

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 20 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

9 Download the site install file generated on the ENM.

Then provide the [Link] file to the on site engineer, to use for LMT Integration.

>> ap download -o -n <NodeName>

10 The node is now defined on the ENM as part of the AP

Now the onsite team may proceed with the onsite activities.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 21 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Once the onsite team has completed the onsite activities and called the NIC, proceed with this
procedure to complete the remote integration.

Onsite Onsite activities

activities
Connect laptop to LMT port
Change IP settings of the laptop and turn off firewall

Open web browser and connect to AI GUI:

[Link]

Onsite LMT integration - Download files

activities
Click LMT integration tab
Fill in username and password for SMRS user (ENM user with role FIELD_TECHNICIAN)
Browse for SiteInstall file

Click Download files

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 22 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Onsite Start integration

activities
When log shows Download Completed, the Integrate button will become active.

Click Integrate

Onsite Integration completed

activities
Wait for READY_FOR_SERVICE.

Once integration reached level SITE_CONFIG_COMPLETE it is possible to remotely connect to

the node from ENM / AMOS.
If OSS_CONFIGURATION_FAILED is seen, then go back to ENM CLI and troubleshoot.
It is possible to fix a fault in Bulk file, perform ap upload and then ap resume.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 23 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Once the onsite team has completed the onsite activities, proceed with this procedure to
complete the remote integration.

11 In the ENM CLI, check the status of the node

This will show the integration status after the completion of the onsite activities.

The integration status and last task in the list should both be: Integration Completed

>> ap status -n <NodeName>

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 24 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

12 In the ENM CLI, verify that the CM syncStatus for the node is SYNCHRONIZED.

>> cmedit get <NodeName> [Link] -t

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 25 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Note: If the CM syncStatus for the node is UNSYNCHRONIZED, perform the following command
to sync the node.
Repeat the command above to verify the node is now SYNCHRONIZED.

>> cmedit action NetworkElement=<NodeName>,CmFunction=1 sync

13 In the ENM CLI, verify that CM supervision is set to true for the node.

>> cmedit get <NodeName> [Link] -t

Note: If CM supervision is not set to true, perform the following command to set the
attribute(s) to true.
Repeat the command above to verify the parameter has been changed.

>> cmedit set NetworkElement=<NodeName>,CmNodeHeartbeatSupervision=1

active=true

14 In the ENM CLI, verify that SHM supervision is true for the node.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 26 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

>> cmedit get <NodeName> [Link] -t

Note: If CM supervision is not set to true, perform the following command to set the
attribute(s) to true.
Repeat the command above to verify the parameter has been changed.

>> cmedit set NetworkElement=<NodeName>,CmNodeHeartbeatSupervision=1

active=true

15 In the ENM CLI, verify that Alarm supervision is true for the node.

>> cmedit get <NodeName> [Link] -t

Note: If Alarm supervision is not set to true, perform the following command to set the
attribute to true.
Repeat the command above to verify the parameter has been changed.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 27 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

>> alarm enable <NodeName>

16 In the ENM CLI, verify that PM supervision is set to true for the node if PM supervision is
required.

>> cmedit get <NodeName> [Link] -t

Note: If PM supervision is not set to true, perform the following command to set the attribute(s)
to true if required.
Repeat the command above to verify the parameter has been changed.

>> cmedit set NetworkElement=<NodeName>,PmFunction=1 pmEnabled=true

17 At the ENM homepage, click on Software and Hardware Manager > Backup Administration
Then click on the Add Topology Data button to select the node you want to add under Network
Elements.

Verify that the latest backup of the node has been uploaded to the ENM.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 28 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

18 At the ENM Application Launcher, click on Alarm Monitor

Then click on the Add Topology Data button to select the node you want to add under Network
Elements.
The node will now appear in the Topology, click on Apply and this will display the alarms for the
node.

Verify that there is not a "Heartbeat Alarm" for the node.

Acknowledge any minor and major alarms by right clicking on the alarm and selecting
Acknowledge.
This will change the status of the alarm from ACTIVE_UNACKNOWLEDGED to
ACTIVE_ACKNOWLEDGED.

19 At the ENM homepage, click on Command Line Interface (CLI), once the AP of the node has
been completed and everything has been verified. The project file that was added at the
beginning of the AP will need to be manually deleted from the ENM.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 29 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Verify that the integration has completed for all nodes in the project before you delete the
project from the ENM.

>> ap status -p <Project Name>

20 In the ENM CLI, delete the project from the ENM.

>> ap delete -p <Project Name>

AP resume - If Import Configurations failed

Step Task/Observation

If AI log shows "OSS_CONFIGURATION_FAILED" and ENM ap status shows Import Configurations Failed

»ap status -n <NodeName>

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 30 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Click Wrap/Unwrap Contents to read Additional Information

Check errors in import verbose job status:

»cmedit import --status --job 1250 -v

Identify the error in the Bulk file in the project and correct it. The file must be unzipped from the
project.
Drag and drop the fixed file to the ENM CLI workarea

»ap upload -n <NodeName> file:"[Link]"

This will replace the faulty file in the ordered project with the corrected file.

Perform Resume, to resume the project and Import Configurations will be started again (with the
corrected file)

»ap resume -n <NodeName>

Note. The ap status must be in Waiting for Resume or Cancel before trigger Resume.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 31 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Check ap status that Integration Completed is reached.

»ap status -n <NodeName>

Manual Provisioning
This section provides the steps required to use the ENM to manually complete the integration of a new node.

Manual
Provisionin
g

Step Task/Observation

1 Login to the ENM using your username and password.

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 32 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

2 Click on your username in the top right corner of the ENM GUI and select View User Profile
from the drop down menu. Verify that the user has the following roles required to complete
this procedure:
• Administrator
• Operator
• SHM Operator
• SHM Administrator
• AMOS Administrator
• Shell Terminal (SSH) Access
• Topology Browser
• Alarm Monitoring (FM)
• Node CLI
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 33 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

3 At the ENM homepage, under Tools, click on Command Line Interface (CLI).
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 34 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

4 Drag and drop the add node batch file into the ENM CLI and run the batch file.

>> batch execute file:<filename>

Note: The batch file will perform all CLI commands required to add the node into the ENM.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 35 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

5 Drag and drop the OneNodeEntity XML file from your PC into the ENM CLI and create the
OneNodeEntity entity on the ENM.

>> pkiadm etm -c -xf file:<filename>

Verify that the new entity has been created on the ENM.

>> pkiadm entitymgmt --list --entitytype ee

>> pkiadm entitymgmt --list --entitytype ee --name <filename>
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 36 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Example Command: pkiadm entitymgmt --list --entitytype ee --name LIENB4180-oam

6 In the ENM CLI, verify that CM, SHM, Alarm and PM supervision are active or enabled for the
node.

>> cmedit get NetworkElement=<NodeName>,CmNodeHeartbeatSupervision=1

>> cmedit get NetworkElement=<NodeName>,InventorySupervision=1
>> cmedit get NetworkElement=<NodeName>,FmAlarmSupervision=1
>> cmedit get NetworkElement=<NodeName>,PmFunction=1
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 37 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 38 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Note: If CM, SHM, Alarm or PM supervision are not set to true, perform the following
command(s) to set the attribute(s) to true. Repeat the command above to verify the parameter
has been changed.

CM:
>> cmedit set NetworkElement=<Node>,CmNodeHeartbeatSupervision=1 active=true
SHM:
>> cmedit set NetworkElement=<Node>,InventorySupervision=1 active=true
Alarm:
>> alarm enable <node>
PM:
>> cmedit set NetworkElement=<Node>,PmFunction=1 pmEnabled=true

7 In the ENM CLI, verify that the CM syncStatus for the node is SYNCHRONIZED.

Note: The node must be synchronized in order to perform any remote integration activities on
the node. The node will not be able to synchronize until the onsite integration activities have
been completed.

>> cmedit get NetworkElement=<NodeName>,CmFunction=1

Note: If the CM syncStatus for the node is UNSYNCHRONIZED, perform the following command
to sync the node. Repeat the command above to verify the node is now SYNCHRONIZED.

>> cmedit action NetworkElement=<NodeName>,CmFunction=1 sync

8 Perform this step to apply TN, RN and feature activation 3GPP bulk CM files only if these
configuration files were not applied to the node during a warehouse configuration.

Note: Refer to the Appendices if the Customer wishes to apply moshell or Netconf files.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 39 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Note: When integrating a WCDMA node, separate TN and RN scripts will be generated for the
RNC.

Drag and drop the [Link] file into the ENM CLI and import the TN file.

Always apply the TN file first and then the RN and Feature Activation file(s).

>> cmedit import -f file:<filename> -ft 3GPP -t Live

Take note of the job ID # assigned to the import and check the status of the job.

>> cmedit import -st -j <job #> -v

After applying a Bulk CM file, you will need to save a backup on the node. Open a new window
in the ENM and start a Shell Terminal, then AMOS to the node from the Shell Terminal.

[eryamcm@scp-2-amos ~]$ amos <node ip>

Once you are connected to the node:

Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 40 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

>lt all

Save an image on the node.

>cvms <File_Applied_Name>

Verify that the image has been saved on the node.

>cvls
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 41 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Note: Repeat for all RN and Feature Activation bulk CM files that you wish to import.

9 At the ENM homepage, click on Software and Hardware Manager > Backup Administration and
then click on the Add Topology Data button to select the node you want to add under Network
Elements.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 42 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19

Select the latest backup available on the node from the list and click on Manage Backup.

Enter a Job Name and check the Upload to ENM box and then click on Create.

Verify that the upload of the backup completes and shows a job status of 100%.

10 At the ENM homepage, click on Alarm Monitor and then click on the Add Topology Data button
and select Search for Network Objects from the drop down menu. Enter the name of the node
you want to find and click on Search. Select the node from the search results and then click on
the Return Selected Managed Objects button. The node will now appear in the Topology, click
on Apply and this will display the alarms for the node.

Verify that there is not a "Heartbeat Alarm" for the node.

Verify that there is not an alarm for a missing LKF, in the case the LKF was not installed during
the onsite activities for the node, refer to the Appendices to apply the LKF using the ENM.

Acknowledge any minor and major alarms by right clicking on the alarm and selecting
Acknowledge. This will change the status of the alarm from ACTIVE_UNACKNOWLEDGED to
ACTIVE_ACKNOWLEDGED.
Confidentiality Class External Confidentiality Label Document Type Page

Ericsson Internal 43 (43)

Prepared By (Subject Responsible) Approved By (Document Responsibile) Checked

Clifford Imaguezegie
Document Number Revision Date Reference

PA1 2019-08-19