Manage Integration

User Guide

45/1553-LZA 701 6014/1-V1 Uen V

Copyright

© Ericsson AB 2016-2018. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Contents

Contents

1 Introduction 1

2 Node Integration Scenarios 2

2.1 LMT Integration 2
2.2 LMT Integration On-Site Configuration 5
2.3 Zero Touch Integration 8
2.4 Zero Touch Integration Off-Site Pre-Configuration 12

3 Configuration Files 16

4 Additional Information 17
4.1 Progress Information 17
4.2 Fault Handling 17
4.3 Autointegration Configuration Levels 18

5 Baseband Radio Node Post-Integration Activities 19

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

Manage Integration

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Introduction

1 Introduction

This instruction describes the Node Integration procedure, that is, how to initiate
and monitor the integration of a Baseband node.

The integration procedure includes the following:

— Network Provisioning

— Node Provisioning

— Node Commissioning

— Node Integration

The node integration progress can be monitored by observing the operational

optical indicator. For more information, see Indicators, Buttons, and Switches.

The Network Loader version on the node determines the supported Node
Integration scenarios. For more information on Network Loader versions and
update procedure, see Upgrade Network Loader.

Following Node Integration scenarios are supported:

— LMT integration

— LMT integration on-site configuration

— Zero Touch Integration

— Zero Touch integration off-site pre-configuration

For more information about the nodes and integration scenarios, an overview of
the full procedure, and document references, see Autointegration Deployment
Guidelines.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 1

 Manage Integration

2 Node Integration Scenarios

Do!
If the node does not respond to actions as described in this document, contact the next
level of support for assistance.

2.1 LMT Integration

In this case the Site Installation File for trusted or untrusted network is on
computer and all other files and Upgrade Package are on a SMRS server.

Note: It is recommended to use unpacked Upgrade Package.

2.1.1 Documents
For all on-site activities, ensure to have knowledge and take precautions as
described in the documents Personal Health and Safety Information and System
Safety Information.

2.1.2 Tools for LMT Integration

A computer, on site, that fulfills the following conditions must be used:

— An IP address must be configured on the computer interface on the same

subnet as the node LMT port.

Default address for the node LMT port is 169.254.2.2, netmask 255.255.0.0.
The computer IP address can be configured manually or automatically by
APIPA (only for computers running Windows OS).

— The computer must be updated with the correct current date and time.

The node uses the computer date and time until it has established contact
with the NTP server.

2.1.3 Supported Browsers and Browser Versions for Node Integration

Table 1 describes the supported browsers and the recommended versions for the
following integration scenarios:

2 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

— LMT integration

— LMT integration on-site configuration

— Zero Touch integration off-site pre-configuration

In case of Zero Touch Integration, supported browsers and the recommended

versions are not applicable.

Table 1 Supported Browser and Versions

Browser Version
Internet Explorer 11
Mozilla Firefox, 32 bit and 64 bit 35.0
Google Chrome 50.0

2.1.4 Conditions for LMT Integration

LMT integration works both for IPv4 and IPv6 on trusted networks. On untrusted
networks only IPv4 is supported.

To start the integration on-site, the following conditions must be met:

— The configuration files are prepared.

— The node hardware and power supply are installed according to the
instructions in Install RBS or Install Baseband.

The operational optical indicator is flashing slowly, at 0.5 Hz.

— Connection to at least two NTP servers with correct time of day

synchronization is available.

— The transport network is available for O&M traffic.

— OSS PKI services are available in accordance with the instructions from OSS.

— For the Auto Integration procedure, a network infrastructure must exist to set
up a private network connection to the OSS site.

— The SMRS server and credentials (username and password) are available.

— The Site Installation File is stored on the computer.

— The following files are available on the SMRS server:

— RBS Summary File

— Site Equipment File

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 3

 Manage Integration

— Site Basic File

— Upgrade Package

— License Key File

— The Network Loader version must be R5BX or later.

Note: For more information about Network Loader versions and the
update procedure, see Upgrade Network Loader.

— If a public network is used for integration, a secure gateway is needed.

RELATED INFORMATION

3. Configuration Files on page 16

2.1.5 Procedures
This section describes the LMT integration node integration procedures.

Note: If the node does not respond to actions as described in this document,
contact the next level of support for assistance.

2.1.5.1 Load Files with LMT Integration

1. Connect the computer to the LMT port.

See Connect Client for more information.

2. Start a web browser.

3. Disable any proxies in the web browser.

4. Enter the https://169.254.2.2/ address to the Auto Integration web GUI.

5. Select the LMT integration tab

6. Enter the SMRS server Username.

7. Enter the SMRS server Password .

8. Click Browse and select the Site Installation File

9. Click Download files

Result: The download starts. On site, the operational optical indicator on the
node double-flashes off.

4 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

2.1.5.2 Integrate Node with LMT Integration

1. Click Integrate in the Auto Integration web GUI.

The continuous steps of the integration process can be monitored from the
AutoIntegration log window. For more information, see Progress Information
on page 17.

Result: After the UP is installed, the node is restarted.

2. Wait until the operational optical indicator is on.

This indicates that the on-site part of the integration is finished, the node is
in-service and ready for operation.
If the operational optical indicator is not on or flashing, do the following:

3. Check the integration status in the Emergency Access (EA) interface.

See Fault Handling on page 17 for more information.

2.2 LMT Integration On-Site Configuration

In this case all configuration files and Upgrade Package are on the SFTP server
of the computer.

Note: It is recommended to use unpacked Upgrade Package.

2.2.1 Documents

For all on-site activities, ensure to have knowledge and take precautions as
described in the documents Personal Health and Safety Information and System
Safety Information.

2.2.2 Tools for LMT Integration On-Site Configuration

A computer, on site, that fulfills the following conditions must be used:

— An IP address must be configured on the computer interface on the same

subnet as the node LMT port.

Default address for the node LMT port is 169.254.2.2, netmask 255.255.0.0.
The computer IP address can be configured manually or automatically by
APIPA (only for computers running Windows OS).

— SSH File Transfer Protocol (SFTP) server is installed.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 5

 Manage Integration

The SFTP server is used for storage and transfer of configuration files to the
node through the LMT port.

— The firewall is configured to allow access to the SFTP server.

— The computer must be updated with the correct current date and time.

The node uses the computer date and time until it has established contact
with the NTP server.

2.2.3 Supported Browsers and Browser Versions

Table 2 describes the supported browsers and the recommended versions.

Table 2 Supported Browser and Versions

Browser Version
Internet Explorer 11
Mozilla Firefox, 32 bit and 64 bit 35.0
Google Chrome 50.0

2.2.4 Conditions for LMT Integration On-Site Configuration

To start the integration on-site the following conditions must be met:

— The configuration files are prepared.

— The node hardware and power supply are installed according to the
instructions in Install RBS or Install Baseband.

The operational optical indicator is flashing slowly, at 0.5 Hz.

— Connection to at least two NTP servers with correct time of day

synchronization is available.

— The transport network is available for O&M traffic.

— OSS PKI services are available in accordance with the instructions from OSS.

— For the Auto Integration procedure, a network infrastructure must exist to set
up a private network connection to the OSS site.

— The username, password, and IP address of the SFTP server of the computer
are available.

— The configuration files are stored on the computer.

6 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

RELATED INFORMATION

3. Configuration Files on page 16

2.2.5 Procedures

This section describes the LMT integration on-site configuration node integration
procedures.

Note: If the node does not respond to actions as described in this document,
contact the next level of support for assistance.

2.2.5.1 Load Files with LMT Integration On-Site Configuration

1. Connect the computer to the LMT port.

See Connect Client for more information.

2. Start a web browser.

3. Disable any proxies in the web browser.

4. Enter the https://169.254.2.2/ address to the Auto Integration web GUI.

5. Select the LMT integration on-site configuration tab.

6. Enter the SFTP server IP address.

The SFTP server IP address must be the same as the IP address of the
computer.

7. Enter the SFTP server Username.

8. Enter the SFTP server Password .

9. Enter the SFTP server file path for the Site Installation File in the Site
Installation File text field.
The Site Installation File points to the RBS Summary File, which points to the
Upgrade Package (UP), LKF, Site Basic File, and Site Equipment File.

10. Click Download files.

Result: The download starts. On site, the operational optical indicator on the
node double-flashes off.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 7

 Manage Integration

2.2.5.2 Integrate Node with LMT Integration On-Site Configuration

1. Click Integrate in the Auto Integration web GUI.

The continuous steps of the integration process can be monitored from the
AutoIntegration log window. For more information, see Progress Information
on page 17.

Result: After the UP is installed, the node is restarted.

2. Wait until the operational optical indicator is on.

This indicates that the on-site part of the integration is finished, the node is
in-service and ready for operation.
If the operational optical indicator is not on or flashing, do the following:

3. Check the integration status in the Emergency Access (EA) interface.

See Fault Handling on page 17 for more information.

2.3 Zero Touch Integration

In this case Site Installation File is on AIWS Server and all other configuration
files and Upgrade Package are on a SMRS server.

2.3.1 Documents

For all on-site activities, ensure to have knowledge and take precautions as
described in the documents Personal Health and Safety Information and System
Safety Information.

2.3.2 Tools for Zero Touch Integration

Zero Touch integration does not require any additional tools.

2.3.3 Supported Browsers and Browser Versions

Not applicable.

2.3.4 Conditions for Zero Touch Integration

Zero Touch integration works both for IPv4 and IPv6 on trusted networks. On
untrusted networks only IPv4 is supported.

To start the integration on-site, the following conditions must be met:

8 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

— The configuration files are prepared.

— The node hardware and power supply are installed according to the
instructions in Install RBS or Install Baseband.

The operational optical indicator is flashing slowly, at 0.5 Hz.

— Connection to at least two NTP servers with correct time of day

synchronization is available.

— The transport network is available for O&M traffic.

— OSS PKI services are available in accordance with the instructions from OSS.

— For the Auto Integration procedure, a network infrastructure must exist to set
up a private network connection to the OSS site.

— The DHCP server is available.

Depending on DHCP configuration, DNS is required.

The DHCP server should provide the trusted network configuration to the
node and it can provide the AIWS and security gateway IP addresses to a
different server.

In case of Zero Touch integration over untrusted networks, the DHCP can
provide the IP address of the security gateway.

For Baseband nodes, the NTP server configuration needs to be in the DHCP
configuration.

Note: Due to prioritization towards trusted networks, the AIWS IP address

is taken from a DHCP server in case any is present.

— The SMRS server is available.

— The AIWS server is available.

— The Site Installation file is available on the AIWS server.

— The following files are available on the SMRS server:

— RBS Summary File

— Site Equipment File

— Site Basic File

— Upgrade Package

— License Key File

— The Network Loader version must be R5BX or later on trusted networks.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 9

 Manage Integration

Note: For more information about Network Loader versions and the
update procedure, see Upgrade Network Loader.

RELATED INFORMATION

3. Configuration Files on page 16

2.3.4.1 Network Loader Upgrade with EGIS

In case available, the Network Loader tries to reach the EGIS server to find a
newer Network Loader version and to find the IP of a security gateway and
AIWS server. The Network Loader upgrades and restarts to the new Network
Loader version automatically when one is available.

Note: In case the node finds the EGIS server with a newer Network Loader
version, it upgrades in both untrusted and trusted cases.

To get the Network Loader automatically downloaded from EGIS, NL must have
the following protocols and interfaces available:

— DHCP to obtain IP address, Gateway IP address, and DNS address for the IP
network. This IP address data can be used for the inner or outer network.

— HTTPS is used for communication with EGIS to get the basic data, like
security gateway IP address. This is done on the IP address obtained from
DHCP.

— SFTP is used to get a new Network Loader from a fileserver connected to

EGIS, if the operator so has ordered. FTPS is considered for future releases.

— IPsec is used to open a secure transport connection to the security gateway

and the internal network where the AIWS and SMRS is. The available ciphers
are the default IPsec ciphers. For information on default IPsec ciphers, see
Manage IPsec.

— RBS must use HTTPS to transfer Network Loader.

In case the IP address of the security gateway or the AIWS is missing on the
EGIS server, the node uses the IP address received from the DHCP server or the
DNS server. The node searches for the AIWS and security gateway IP addresses
on EGIS first. In case one of them is missing, it searches in the DHCP server and
proceeds as follows:
— The DHCP server provides the IP address of the security gateway. The node
runs untrusted case.

— The DHCP server cannot provide the IP address of the security gateway but
provides the AIWS IP address. The node runs trusted case.

10 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

Both IP addresses are still missing after searching in the DHCP server. The node
proceeds to search in the DNS server for the missing IP addresses as follows:
— The DNS server provides the IP address of the security gateway. The node
runs untrusted case.

— The DNS server cannot provide the IP address of the security gateway but
provides the AIWS IP address. The node runs trusted case.

In case both addresses are still missing after searching the DHCP and DNS
servers, the node proceeds to the next VLAN.

Figure 1 shows how the node decides to run untrusted or trusted case depending
on the availability of the AIWS and security gateway IP addresses.

SecGW and AIWS

address from EGIS

No Untrusted scenario

SecGW addresses Yes

from DHCP

No

AIWS addresses Yes

Trusted scenario
from DHCP

No

SecGW addresses Yes

from DNS

No

AIWS addresses Yes

from DNS

L0001750B

Figure 1 Selection Process of Untrusted and Trusted Cases

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 11

 Manage Integration

2.3.5 Procedures

This section describes the Zero Touch node integration procedures.

Note: If the node does not respond to actions as described in this document,
contact the next level of support for assistance.

2.3.5.1 Load Files and Integrate Node with Zero Touch Integration

1. Power on the node.

Result: Zero Touch integration process starts automatically.

If all required conditions are met no further actions are needed.

2. Wait until the operational optical indicator is on.

This indicates that the on-site part of the integration is finished, the node is
in-service and ready for operation.
If the operational optical indicator is not on or flashing, do the following:

3. Check the integration status in the Emergency Access (EA) interface.

See Fault Handling on page 17 for more information.

2.4 Zero Touch Integration Off-Site Pre-Configuration

In this case all configuration files and Upgrade Package are on the SFTP server
of the computer.

Note: It is recommended to use unpacked Upgrade Package.

2.4.1 Documents

For all on-site activities, ensure to have knowledge and take precautions as
described in the documents Personal Health and Safety Information and System
Safety Information.

2.4.2 Tools for Zero Touch Integration Off-Site Pre-Configuration

A computer that fulfills the following conditions must be used:

— An IP address must be configured on the computer interface on the same

subnet as the node LMT port.

12 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

Default address for the node LMT port is 169.254.2.2, netmask 255.255.0.0.
The computer IP address can be configured manually or automatically by
APIPA (only for computers running Windows OS).

— SSH File Transfer Protocol (SFTP) server is installed.

The SFTP server is used for storage and transfer of configuration files to the
node through the LMT port.

— The firewall is configured to allow access to the SFTP server.

— The computer must be updated with the correct current date and time.

The node uses the computer date and time until it has established contact
with the NTP server.

2.4.3 Supported Browsers and Browser Versions

Table 3 describes the supported browsers and the recommended versions.

Table 3 Supported Browser and Versions

Browser Version
Internet Explorer 11
Mozilla Firefox, 32 bit and 64 bit 35.0
Google Chrome 50.0

2.4.4 Conditions for Zero Touch integration off-site pre-configuration

To start the integration off-site, the following conditions must be met:

— The configuration files are prepared.

— The node hardware and power supply are installed according to the
instructions in Install RBS or Install Baseband.

The operational optical indicator is flashing slowly, at 0.5 Hz.

— Connection to at least two NTP servers with correct time of day

synchronization is available.

— The transport network is available for O&M traffic.

— OSS PKI services are available in accordance with the instructions from OSS.

— For the Auto Integration procedure, a network infrastructure must exist to set
up a private network connection to the OSS site.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 13

 Manage Integration

— The username, password, and IP address of the SFTP server of the computer
are available.

— The configuration files are stored on the computer SFTP server.

— The Network Loader version must be R4AJ or later.

Note: For more information about Network Loader versions and the
update procedure, see Upgrade Network Loader.

RELATED INFORMATION

3. Configuration Files on page 16

2.4.5 Procedures

This section describes the Zero Touch off-site pre-configuration node integration
procedures.

Note: If the node does not respond to actions as described in this document,
contact the next level of support for assistance.

2.4.5.1 Load Files with Zero Touch Integration Off-Site Pre-Configuration

1. Connect the computer to the LMT port.

See Connect Client for more information.

2. Start a web browser.

3. Disable any proxies in the web browser.

4. Enter the https://169.254.2.2/ address to the Auto Integration web GUI.

5. Select the Zero touch off-site pre-configuration tab

6. Enter the SFTP server IP address.

The SFTP server IP address must be the same as the computer IP address.

7. Enter the SFTP server Username.

8. Enter the SFTP server Password .

9. Enter the SFTP server file path for the Site Installation File in the Site
Installation File text field.
The Site Installation File points to the RBS Summary File, which points to the
Upgrade Package (UP), LKF, Site Basic File, and Site Equipment File.

14 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Node Integration Scenarios

10. Click Download files.

Result: The download starts. On site, the operational optical indicator on the
node double-flashes off.

11. Wait until download is finished.

12. Check the Download Completed message in AutoIntegration log field.

13. Power off the node.

2.4.5.2 Integrate Node with Zero Touch Integration Off-Site Pre-Configuration

1. Power on the node.

2. Wait until the operational optical indicator is on.

This indicates that the on-site part of the integration is finished, the node is
in-service and ready for operation.
If the operational optical indicator is not on or flashing, do the following:

3. Connect the computer to the LMT port.

4. Check the integration status in the Emergency Access (EA) interface.

See Fault Handling on page 17 for more information.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 15

 Manage Integration

3 Configuration Files

The integration is based on configuration files, containing the configuration

parameters, license keys, and software upgrade package.

The configuration files are stored locally on the laptop. The following
configuration files in Table 4 must be prepared:
— Site Installation File

— RBS Summary File

— Site Equipment File

— Site Basic File

Manage Configuration Files contains instructions on how to prepare the files,

links to example files, and a description of the files and configuration parameters.
The upgrade package and license key file are provided by Ericsson.

Note: At least one maintenance user must be added during integration. A

maintenance user cannot be configured after the completion of
integration.

The maintenance user configuration is part of the Site Basic File. For
information on how to configure the maintenance user role, see Manage
Security.

It is recommended to use unpacked Upgrade Package for all integration

methods.

Table 4 Configuration Files

Configuration Filename File Content

Site Installation File Path to the RBS Summary File used for the
integration
RBS Summary File Paths to the files used for the integration
Site Equipment File Equipment configuration
Site Basic File Security management, system management,
and transport network configuration
Upgrade Package (UP) Software installation
License Key File (LKF) License keys for node features (1)
(1) The License Key File is required when licensed features need to be installed and activated. To start the cell of the
node, a License Key File for the feature 5+5 MHz Sector Carrier is mandatory.

16 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Additional Information

4 Additional Information

This section describes details about the progress information and actions to take
during deviations from the procedures.

4.1 Progress Information

The integration progress data is stored in the AutoIntegration Log. During
download of the configuration files, the progress data can be followed in the
AutoIntegration Log area in the Autointegration web GUI. During this time, the
AutoIntegration log can also be exported from the web GUI by clicking the
Export Autointegration log button.

After the restart, the log can be exported and viewed. Use a node management
tool. For more information, see Manage Software.

4.2 Fault Handling

If there is a configuration file error and 2 hours has passed without a successful
logon, the node is reset to initial start state and an ESI package is generated. To
determine why the integration has failed, the ESI can be sent to Ericsson for
analysis.

The EA interface can be used to generate and export the ESI. For information on
how to generate and export the ESI from EA, see Data Collection Guideline.

The EA interface can also be used to manually set the node to the initial start
state before 2 hours has passed.

Note: If several Restore Board actions are triggered in a row, the logs are
deleted.

To set the node to state initial start from EA:

Steps

1. Connect the computer to the LMT port.

See Connect Client for more information.

2. Start a web browser.

3. Disable any proxies in the web browser.

4. Enter the https://169.254.2.2/ea.html address of the EA.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 17

 Manage Integration

a. Approve the security certificate for this node local web site.
The IP address of the LMT port is by default 169.254.2.2.

5. Click the Restore Board button in the Emergency Access window.

6. Click the Restore Board button in the Restore Board window.

Result: The node is reset to state initial start.

The integration procedure can now be restarted.

Note: Faults are monitored in the Autointegration Log window.

4.3 Autointegration Configuration Levels

The OSS_CONFIGURATION_FAILED and RAN_INTEGRATION_WAS_CANCELLED levels
cause the node to restore the backup that was created once
SITE_CONFIG_COMPLETE was reached during autointegration and this results in a
restart. The READY_FOR_SERVICE level causes the backup to be deleted.

Note: Autointegration configuration levels are only to be set through OSS-RC

or ENM and not directly by an operator.

18 45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07

 Baseband Radio Node Post-Integration Activities

5 Baseband Radio Node Post-Integration

Activities

Ensure that the node is added to OSS and OSS-RC MIB Synchronization, a node
backup is created, the planned area is activated, and confirmation that the node
is integrated and activated is made.

— Add Node to OSS and OSS-RC MIB Synchronization

The Integration Engineer adds the node to OSS-RC through the ARNE tool,
see the OSS-RC documents ARNE User Guide, and ARNE, Import Export
User Guide. The OSS-RC MIB is synchronized to the node MIB.

— Activate Planned Area

Note: This step is valid for the OSS-RC support system.

RBS configuration data for radio network and transport network can be
imported to OSS-RC with bulk CM files.

The Integration Engineer activates the planned area through OSS Common
Explorer. For more information, see the OSS-RC documents CEX, OSS
Common Explorer, User Guide, and PCA, Planned Configuration
Administration. The transport network is configured.

— Configuration Backup

The Integration Engineer enters a request to create a node backup using the
OSS-SHM tool. OSS stores the backup on an OSS server. For more
information, see the OSS-RC document SHM, Software Hardware Manager,
User Guide and the document Manage Software.

— Node Integrated and Activated

The Integration Engineer sets AI Configuration level to

INTEGRATION_COMPLETE in OSS Common Explorer. The node confirms that
integration is complete, and sets the AI Configuration level to
READY_FOR_SERVICE and the operational optical indicator is On. For more
information, see the OSS-RC document CEX, OSS Common Explorer, User
Guide.

45/1553-LZA 701 6014/1-V1 Uen V | 2018-08-07 19