MOP for Controller 6610 Integration

Contents

1 Purpose ............................................................................................................................. 2
2 Revision ............................................................................................................................. 7
3 General Information .......................................................................................................... 8
4 Naming Convention........................................................................................................... 8
5 Summary Time Plan .......................................................................................................... 9
6 Detailed Time Plan – Zero Touch Integration Preparation............................................... 10
7 Detailed Time Plan - Zero Touch Integration Implementation ........................................ 15
8 Fallback Procedure .......................................................................................................... 29
9 Restore Procedure........................................................................................................... 29
10 Baby Sitter Responsibility................................................................................................ 33
11 Escalation Procedures after Implementation .................................................................. 33
12 MOP Checklist ................................................................................................................. 34
13 Roles & Responsibilities Checklist ................................................................................... 36
14 Commencement Signoff .................................................................................................. 37

1 |3 9
1 Purpose
The Ericsson Smart Connected Site (SCS) solution with Controller 6610 aims to intelligently
integrate the management of all site elements in a unified system. The Controller 6610 Node
controls the support system and external alarms for a cabinet or a managed site. The
advantage with Controller 6610 is that the software is aligned with Baseband and the
management of the node is like how we handle a baseband node.

The purpose of this document is to describe the autointegration process for a Controller 6610
using ENM. With autointegration, the onsite engineer only needs to install Controller 6610 and
make sure that all the connection cables are connected. The ASP also should make sure that
the transport cable between the 6610 and Router6672 are connected, and the Baseband is
powered ON. Once it is powered ON, 6610 will automatically fetch the script from ENM and
do the auto configuration.

Autointegration flow:

AutoIntegration needs a DHCP server to provide IP to the 6610. The DHCP Server is located in
ENM and Router 6672 will act as DHCP relay. We need to configure DHCP server and DHCP
relay prior to the 6610 Integration.

2 | 39
Controller 6610 Nodes provide the following functions and resources:

 The transport network termination based on IP, allowing to configure O&M

 Mechanical environment for Baseband units and radios
 Power supply and distribution
 Climate control
 Interfaces for external alarms

The separation of functions between the Baseband and Controller 6610 node in RBS 6000
Cabinet and ERS Enclosure deployment is shown below.

Following is the front panel view of the Controller 6610. The foot print is same
as the existing ESC in the network.

Controller 6610 can be installed in Enclosures as shown below

3 | 39
Controller 6610 can be installed in RBS6K as shown below

The connections to be followed in case of Enclosures and RBS 6K are given below

4 | 39
Enclosures

RBS6K

5 | 39
MO structure comparison between Enclosures and RBS6K

6 | 39
 The following section shows the comparison between Controller 6610 and ESC

2 Revision

Revision Date Reason of Issue

A First draft
19-July-2022
B Updated for Enclosure configurations
21-July-2022
C Updated for RBS6K configurations
19-Aug-2022

7 | 39
3 General Information
Implementation Package: 22.Q1 GA

Implementation Place:

Implementation Date:

Implementation Time:

NA
Implementation Downtime:
-
Preparation Work Checked By:
Ashwin Ramachandran
MOP Prepared By:
-
DT/ Procedures Verified By:
Hikmat Nugraha
MOP verified By:
Ie Ivan Suguanto
MOP Approved By:

4 Naming Convention
The naming convention for the Smart Connected Site is as follows

SCS_<OD/IB Indictor><3G SITE ID><1>_<SITENAME>_<TYPE>_<CABINETNO>

 OD/IB Indicator – 7 for OD, 9 for IB

 TYPE – ENC for Enclosure, 6K for RBS6000
 Cabinet Number – Indicates the number of the cabinet

Let us see the example below

SITE ID – 3002
Type – Outdoor OD

Example for an Enclosure 6130, first cabinet

Naming for the Controller 6610 in Enclosure 6130 – SCS_730021_Shaw_Center_ENC6130_01

Example for an RBS 6102, second cabinet

Naming for the Controller 6610 - SCS_730021_Shaw_Center_6K6102_02

8 | 39
5 Summary Time Plan

Activity Activity Description Start Finish Duration

ID (minutes)

6 Preparation

6.1 Script Preparation 09:00 10:00 60

6.2 Add DHCP Entry in ENM DHCP Service 10:00 10:15 15

6.3 Configure Router 6672 with DHCP Relay and Transport configuration 10:15 10:30 15

6.4 ENM Preparation: Script loading 10:30 10:45 15

7 Implementation

7.1 ENM Binding 11:00 11:15 15

7.2 Turn on 6610 and start ZT integration 11:15 12:15 60

7.3 Activate SNMPv3 12:15 12:20 5

7.4 Defining External Alarms (For Enclosures) 12:20 12:30 10

7.5 Defining External Alarms, SAU, PDU, PSU, SCU and BFU (For RBS 6K) 12:20 12:30 10

7.6 Activate Scanner for the node 12:30 12:35 5

7.7 Define the geographic coordinates in ENM 12:35 12:40 5

7.8 Perform Battery Test 12:40 13:15 35

7.9 Post Integration Activity 13:15 13:45 30

7.10 Remove Project from ENM 13:45 13:55 5

9 | 39
6 Detailed Time Plan – Zero Touch Integration Preparation

ID Activity Start Finish Duration Comments

Time Time (minutes)

6.1 Script Preparation 09:00 10:00 60 

Please prepare the script using PCI templates and ask

the ASP for the label containing the Enclosure
Product detail.

The product number will start with BMK for

Enclosures.

6.2 Add DHCP Entry in ENM DHCP Service 10:00 10:15 15

 Login to ENM
 Open Command Line Interface

 Check if the subnet already added to the dhcp.

> dhcp network view --subnet | -s <subnet>

 If it does not exist, then add subnet using the

following command:

# For /30 Subnet

dhcp network add --subnet 100.89.88.116 --
netmask 255.255.255.252 --defaultrouter
100.89.88.118 --broadcast 100.89.88.119 --ntp
10.252.179.12, 10.252.179.13 --aiws
10.252.179.43
dhcp client add E96A00KT9D --host
SCS_727311_The_Agape_ENC6130_01 --ip
100.89.88.117 --subnet 100.89.88.116 --ntp
10.252.179.12, 10.252.179.13

## -- Broadcast = gateway ip + 1
## -- Subnet = gateway ip - 2

10 | 39
 # For /31 Subnet
dhcp network add --subnet 100.89.70.193 --
netmask 255.255.255.254 --defaultrouter
100.89.70.194 --broadcast 100.89.70.194 --ntp
10.252.179.12, 10.252.179.13 --aiws
10.252.179.43
dhcp client add E96A00KT9D --host
SCS_727311_The_Agape_ENC6130_01 --ip
100.89.70.193 --subnet 100.89.70.193 --ntp
10.252.179.12, 10.252.179.13

Broadcast = Default Router IP

Subnet = Node IP

 To update the subnet used the following command:

11 | 39
 To delete the subnet use the following command:

dhcp network delete --subnet | -s <subnet> [ --noreload ]

6.3 Configure Router 6672 with DHCP Relay and 10:15 10:30 15
Transport configuration

Make sure that the DHCP relay service is configured

in the OAM context. If configured you can ignore
the following

configure
!
context RAN_OAM
!

dhcp relay server 10.252.179.12

!
dhcp relay server 10.252.179.13

commit
end

Now configure the OAM interface for 6610

Controller with DHCP relay
12 | 39
 configure

### OAM Interface ###

context RAN_OAM
interface to-SCSPort20_OAM
ip address 100.89.88.118/30
dhcp relay 65535
propagate qos from ip class-map ein-default-dscp-
to-dp

## Ethernet Port configuration

port ethernet 1/20

description to-SCS
no shutdown
encapsulation dot1q
dot1q pvc 210
bind interface to-SCSPort20_OAM RAN_OAM

commit
end

save configuration

6.4 ENM Preparation: Script loading 10:30 10:45 15

At this step, we will load the prepared script into

ENM CLI.

For Enclosure following is a sample script.

SCS_727311_The_Ag
ape_ENC6130_01.zip

For RBS6K cabinets, following is a sample script

22Q1_C6610_74152
1_RBS6K_ENM_0T_Script_RevA.zip

13 | 39
Login to ENM
Open Command Line Interface

Open folder where the script is located.

Put all the file into Zip file.

Drag and drop the zipped file into the ENM CLI.

On CLI run the following command:

ap order file:"SCS_727311_The_Agape_ENC6130_01.zip"

Check the ap status

Project Status:
ap status -p <project name>
ap status -p SCS_727311_The_Agape_ENC6130_01

Check the node status with the following command

ap status -n SCS_727311_The_Agape_ENC6130_01

14 | 39
 Check the node

7 Detailed Time Plan - Zero Touch Integration Implementation

ID Activity Start Finish Duration Comments

Time Time (minutes)

15 | 39
 7.1 ENM Binding 11:00 11:15 60 

Next step is to binding of the prepared

configuration in ENM with the node serial
number. Only if the serial number matches the
physical serial number of the Controller 6610,
configuration files can be fetched from ENM for
ZT integration

Request the ASP for the Serial Number of the the

Controller 6610

 Login to ENM
 Open Command Line Interface

Bind the node with its serial number

ap bind -n <node name> -s <serial number>

ap bind -n SCS_727311_The_Agape_ENC6130_01 -s E96A00KT9D

Check the node status with the following command. The Hardware Bind Completed status should be seen

ap status -n <node name>

ap status -n SCS_727311_The_Agape_ENC6130_01 -s E96A00KT9D

16 | 39
 At this point, please ask the ASP to turn on the Baseband

7.2 Turn on 6610 11:15 12:15 60

ASP need to ensure the following:

- Transmission Link conneted to the
correct port in Router 6672
- All HW has been connected to the
Baseband

Once the node up, it will get IP from DHCP server and it will try to reach ENM.
We can see from the AP node status:

ap status -n SCS_727311_The_Agape_ENC6130_01

Wait until Integration AP process completed.

17 | 39
Once Integration is completed, check for the status of all FieldReplaceableUnit

st field

Also make sure that the rectifiers are created automatically and enabled

st rectifier

18 | 39
Also make sure other MO’s are auto created as shown

If all FieldReplaceableUnits are enabled execute the following commands. If not please check with ASP on the physical connection

acc PowerDomain=1,BatteryBackup=1 copyConfigFrom

acc PowerDomain=1,BatteryBackup=1 copyConfigTo
acc PowerDomain=1,BatteryBackup=1 setReferenceBatteryCapacity
200

Note: Please check with ASP on the battery capacity

19 | 39
7.3 Activate SNMPv3 12:15 12:20 5

Run the following command on the ENM CLI to

activate SNMP v3 for the node

Note: Please change the node name accordingly

cmedit set
NetworkElement=SCS_727311_The_Agape_ENC
6130_01,FmAlarmSupervision=1 active=false
cmedit set
NetworkElement=SCS_727311_The_Agape_ENC
6130_01,ComConnectivityInformation=1
snmpVersion=SNMP_V3,snmpSecurityLevel=AU
TH_PRIV,snmpSecurityName=snmpuser

secadm snmp authpriv --auth_algo SHA1 --

auth_password v3Password --priv_algo AES128
--priv_password v3Password --nodelist
SCS_727311_The_Agape_ENC6130_01

cmedit set
NetworkElement=SCS_727311_The_Agape_ENC
6130_01,FmAlarmSupervision=1 active=true

cmedit action
NetworkElement=SCS_727311_The_Agape_ENC
6130_01,CmFunction=1 sync

cmedit get
SCS_727311_The_Agape_ENC6130_01
CmFunction.syncStatus -t

cmedit get
SCS_727311_The_Agape_ENC6130_01
20 | 39
 ComConnectivityInformation.snmpVersion -t

Delete the following SNMP configuration

del Snmp=1,SnmpTargetV3=1

7.4 Define External Alarms in the node (For 12:20 12:30 10

Enclosures)

External alarm definion needs to be done at this

point. The Controller is connnected to an SAU
which is capable of handling 32 external alarms.
Check with the ASP on the external alarms on site
and define them according to project plan.

A sample script for defining external alarm is

given below

crn Equipment=1,FieldReplaceableUnit=SAU-
1,AlarmPort=1
administrativeState 1
alarmInExternalMe false
alarmSlogan Enclosure B154 Door Open
filterAlgorithm 0
filterDelay 60
filterTime 0
normallyOpen true
perceivedSeverity 4
userLabel
end

crn Equipment=1,FieldReplaceableUnit=SAU-
1,AlarmPort=2
administrativeState 1
alarmInExternalMe false
alarmSlogan Enclosure B154 CB Down
filterAlgorithm 0
filterDelay 60
filterTime 0
normallyOpen false
perceivedSeverity 4
userLabel
end

7.5 Defining External Alarms, SAU, PDU, PSU, SCU 12:20 12:30 10
and BFU (For RBS 6K)

The external alarms and adjunct units such as

PDU, PSU, SCU etc which were previously
handled by DUW need to be migrated to the
Controller 6610. This can be easily prepared by
the u+s/u-s method in the DUW. It can also be
21 | 39
prepared manually depending on the
configuration of the adjunct units. The sample
scripts for creation are mentioned below

Note: Before running this script make sure that

the Ec Port in the Controller 6610 is disconnected
from SHU as it may automatically create the MO’s

1. Creation of SAU and alarm ports

The SAU and alarm ports are created by

executing the following command.

run 1_SAU_Alarmport.mos

1_SAU_Alarmport.mo
s
2. For the creation of BFU, the following
command is executed

run 2_BFU.mos

2_BFU.mos

3. For the creation of PSU, the following

command is executed

run 3_PSU.mos

3_PSU.mos

4. For the creation of PDU, the following

command is executed

run 4_PDU.mos

4_PDU.mos

5. For the creation of SCU, the following

command is executed

5_SCU.mos

Once all MO’s are created do “lt all” . Make sure

that the create MO’s batch the actual number of
22 | 39
 hardware installed.

7.6 Activate Scanner for the node 12:30 12:35 5

Add the newly integrated 6610 to the scanner.

The scanner name for 6610 is “6610_Counters”

Right Click and Edit

Click Add topology data

Search for the newly added 6610 and click Add

Click Save

23 | 39
7.7 Define the geographic coordinates in ENM 12:35 12:40 5 Please get the coordinates from
the co-located ESS/GNB/ENB
We can now define the geographical coordinates node
for the Controller 6610 through the CLI. Please
issue the following commands.

cmedit create
NetworkElement=SCS_727311_The_Agape_ENC6
130_01,GeographicLocation=1
geographicLocationId=1 -ns=OSS_GEO -v=2.0.0

cmedit create
NetworkElement=SCS_727311_The_Agape_ENC6
130_01,GeographicLocation=1,GeometricPoint=1
geometricPointId=1, latitude="1.326888",
longitude="103.724606" -ns=OSS_GEO -v=2.0.1

Open Network Viewer Application in ENM and

seach for the node. Make sure that the node is
visible in the map.

24 | 39
 7.8 Perform Battery Test 12:40 13:15 35

To start the battery test

acc PowerDomain=1,BatteryBackup=1
startBatteryTest

Wait for the Battery test result to be completed.

To start Battery Test :

Locate the node in Topology explorer and launch AMOS

25 | 39
Once the AMOS is launched type the following command to start the battery test

acc PowerDomain=1,BatteryBackup=1 startBatteryTest

The parameter option for forced should be set as true

To check if the battery test is running, type the command

get . batteryTestIsRunning

26 | 39
To check if the battery test has been completed

get . batteryTestIsRunning

To Check the Battery Test result, go to

get . latestBatteryTestResult

7.9 Post Integration Activity 13:15 13:45 30

 Check alarm and HW Status

alt
st fieldreplacement
set rectifier
cabx
inv

 Create Backup and transfer to ENM

- Open SHM in ENM

Create Backup:

27 | 39
28 | 39
Backup will be stored in /ericsson/tor/smrs/smrsroot/backup/controller6610/SCS_959921

7.9 Remove Project from ENM 13:45 13:55

Once integration done, remove project from EM

using CLI.

Check the ap status:

ap status -p
SCS_727311_The_Agape_ENC6130_01

Delete ap
ap delete -p
SCS_727311_The_Agape_ENC6130_01

8Fallback Procedure
N/A

9Restore Procedure
The restore procedure can be done using ZT or manual methods. Both methods are described
below

Restore using ZT

1. Install New Controller 6610, connect all the cabling except the power
2. Make sure to create a zip project for replacing the Controller 6610.

29 | 39
3. Transfer the Replace.zip into the ENM CLI work space by dragging the file

4. To create the AP project, the following command should be given

ap order file:”Replace.zip”

5. Now switch on the new controller 6610 and monitor the status of integration using the following
command

ap status -n SCS_959921

6. Wait till the Hardware Replacement Completed is seen on the ENM

ap status -n SCS_959921

30 | 39
 A sample replace file is given below

Replace.zip

Restore using LMT procedure

1. Install New Controller 6610, connect all the cabling except the power
2. Power ON the 6610
3. Connect PC to the 6610 directly
6610 IP : 169.254.2.2 Mask 255.255.255.0
PC IP : 169.254.2.3 Mask 255.255.255.0 Gateway : 169.254.2.2
4. Open browser and go to  https://169.254.2.2
5. Go to LMT Onsite and key in the SFTP server details as follows

Transfer the working backup of Controller 6610 from the following folder
/ericsson/tor/smrs/smrsroot/backup/controller6610/

31 | 39
In the SFTP server folder inside the test laptop, put the RBSSummarySiteRestore, the backup as well as
the software as shown below.

Click Download on the LMT window in the 6610 controller and wait till download is completed. Once
download is completed, the Integrate button will be enabled. Then click Integrate and wait for the
Restore to be completed as shown.

32 | 39
10 Baby Sitter Responsibility
NA

11 Escalation Procedures after Implementation

At the completion of the implementation, there will be 24-hour “soaking period”.

Any emergency escalations during this period should be directed to the Ericsson Call
Centre number +65 9687 9012.

The Ericsson Call Centre will have contact information for all resources associated with the
implementation and will direct emergency calls accordingly.

33 | 39
MOP Checklist

Checks (Yes, No,

s/n Description
N/A)

1 Objectives and reasons for performing task must be clearly stated Yes No N/A

Expected outcome and improvement after the change must be clearly

2 stated. E.g. Reduction in CPU load by x %, traffic load balance between Yes No N/A
links etc)

3 Detailed Activity Flowchart & Summary Time Plan shall be provided Yes No N/A

All services and network impacts (including adjacent nodes, if applicable)

4 Yes No N/A
shall be assessed and clearly described

All pre and post implementation checks shall be detailed in the MOP,
5 Yes No N/A
including the parties to conduct these health checks

Detailed procedures (including scripts, low level commands), expected

6 Yes No N/A
outcomes and time required for each execution must be provided.

Impact of change to System must be verified

(a) Any new O&M-related counters and alarms introduced or removed?

Yes No N/A
(b) Any new performance-related counters introduced or removed?
Yes No N/A
(c) Any billing implications (e.g. change in CDR format or perceived volume
7 Yes No N/A
of CDRs)
Yes No N/A
(d) Any degradation in node capacity/throughput as far as dimensioning is
concerned. (signaling & payload)

(e) Any follow-up action required at adjunct nodes before or during the
Yes No N/A
MOP

8 Fallback plan and escalation procedures must be included in the MOP Yes No N/A

34 | 39
 Comprehensive service verification test cases after implementation must
9 Yes No N/A
be identified

All configuration changes shall be documented in MOP, checked, reviewed

10 and agreed by all stakeholders before proceeding with the live Yes No N/A
implementation

All personnel (internal or external) involved in the execution of MOP,

11 Yes No N/A
including their contact numbers shall be listed in the MOP

Responsibilities matrix shall be clearly defined and all stakeholders of

12 interconnecting nodes are informed and prepared to support the Yes No N/A
implementation

All procedures, improvement/software correction provided by the patch

13 Yes No N/A
shall be verified in the OLP

14 The license key needed for upgrade is checked and verified Yes No NA

For any activities that involve restart/reboot of nodes, team to access and
to ensure that all adjacent and end to end nodes have sufficient capacity
15 Yes No N/A
to handle the sudden surge in signaling and bearer traffic during the
restart/reboot.

Does the reconfiguration (e.g APN IP Pool modification) requires the

16 Yes No N/A
blocking and termination of existing APNs?

Does the activity impact the roaming Corporate customer (e-ideas,

17 Yes No N/A
Internet or Blackberry APN)?

Overall risk assessment shall be provided for the execution

High
Medium
18 (a) 1st implementation of a new patch is considered High Risk
Low
(b) An old patch that has been widely deployed is considered Low risk

35 | 39
13 Roles & Responsibilities Checklist

Role Name Organization Contact Number

36 | 39
14 Commencement Signoff
After completing the previous pages, the Customer representative agrees that the detailed
procedures provided are adequate to complete the work, a signature below; indicating acceptance
will enable work to commence.

Changes shall be made without the prior approval of the Customer and Ericsson representatives.

Ericsson Representative:
Title:
Date:
Signature:

Customer Representative:
Title:
Date:
Signature:

37 | 39
Appendix A – Definition of Skill Level
Assessed

1. Deliver services within site engineering, integration and/or configuration and/or support of products and
networks in accordance with clearly defined specification in the customer contract.

2. Identify and isolate malfunctioning systems/nodes and if possible apply resolving processes.

3. Execute programming on parts of IT-tools to enable that the tools can be used to deliver services in the
day to day operations.

4. Plan and design networks within a given framework and in accordance to contract specification.
Participate in network optimization.

5. Conduct limited customized configuration, integration and some software adaptation of

products/networks, including 3rd party products.

6. Carry out appropriate site design and layout, after a site has been approved.

Experienced

1. Deliver services within one or many of the following services (site engineering, configuration, integration,
customized software adaptation and support of products and networks in accordance with a customer
service contract. Services are predominantly delivered in live customer networks.

2. Create software packages for specific customers to stabilize and optimize their networks, including
customizations of interfaces between Ericsson and third party products.

3. Identify faults and troubleshoot these, according to a set of defined alternatives, and apply standard
resolving processes in the network.

4. Develop and design customized solutions, end user application, methods, tools and scripts/features
within a defined framework and in accordance to customer requirements.

5. Plan, design, configure, integrate, and optimize the network based on the customers’ requirements on
the technical functionality.

6. Identify appropriate site locations and gain approval for the planning phase of the acquisition.

After approval:

- Organize and coordinate site engineering activities

- Carry out appropriate site design and layout and order materials

- Engage subcontractors

all at an optimal level to secure the completion of the acquisition.

7. Provide training courses to Ericsson employees and customers in a predefined IT-environment;

sometimes including developing of new courses and/or customization of existing standard courses to meet
customers’ requirement.

38 | 39
Senior

1. Deliver several services of the following services (Network design, optimization, integration,
configuration, customized software adaptation) and support of multiple technologies/platforms, including
products from other vendors than Ericsson.

2. Conduct major upgrades/updates of live networks.

3. Conduct end user solution/ application to the network

4. Troubleshoot with creativity and different approaches for severe, undefined problems in networks and
propose suitable resolving solutions.

5. Provide training courses to Ericsson employees and customers in a non predefined IT-environment.

39 | 39