Sie sind auf Seite 1von 19

PPLTE16AMP4 Installation Instructions

Product Family: Base Stations


Product: Flexi Multiradio BTS LTE
Release: FL16A 6.0

Approval date: 26-Apr-2017

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 1/19 © Nokia 2017


Version 1.0
Confidential
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified
herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom
you have entered into the Agreement (as defined below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the
agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used,
copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not
entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility
when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the
documentation.

This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability,
capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document,
and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to
ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You
identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia
does not warrant that the use of the software in the Product will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA, BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without
the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners.

Copyright © 2017 Nokia. All rights reserved.

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having
carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information”
part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow
the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at
Nokia for any additional information.

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 2/19 © Nokia 2017


Version 1.0
Confidential
Table of Contents
1.Purpose..................................................................................................................................... 4
2.Summary................................................................................................................................... 4
3.Configuration Information .......................................................................................................... 4
4.Test Results .............................................................................................................................. 5
5.Installation Instructions .............................................................................................................. 5
5.1 Copying software to Administration Server ..................................................................... 5
5.2 Filling in commissioning workflow variables .................................................................... 6
5.3 Restoring files................................................................................................................. 7
5.4 Updating the parameters ................................................................................................ 7
5.5 Executing system configurations .................................................................................... 8
5.6 Running the Preparing_Upgrade workflow...................................................................... 8
5.7 Disabling scheduled backups ......................................................................................... 9
5.8 Upgrading Product Software ........................................................................................... 9
5.8.1 Creating the NetAct online upgrade stack .................................................................. 9
5.8.2 Executing the NetAct online upgrade stack ................................................................ 9
5.8.3 Creating the NetAct offline upgrade stack ................................................................ 10
5.8.4 Executing the NetAct offline upgrade stack .............................................................. 10
5.9 Completing the upgrade ............................................................................................... 11
5.10 Deploying NetAct fast pass FM/PM compatible metadata............................................ 11
5.11 Verifying the system after installation............................................................................ 12
6.Completing Post upgrade actions ............................................................................................ 13
6.1 Running the NetAct post-upgrade actions with the Workflow tool ................................. 14
6.2 Deleting passwords of Workflow variables .................................................................... 14
6.3 Removing Workflow tool PRG files ............................................................................... 14
6.4 Taking the VDP backup for Administration Server ........................................................ 14
6.5 Enabling the scheduled backup .................................................................................... 15
6.6 Powering off the Administration Server ......................................................................... 15
7.Troubleshooting ...................................................................................................................... 15
7.1 Cleaning the Administration Server............................................................................... 15
7.2 Continuing a failed upgrade stack execution................................................................. 15
7.3 Continuing a failed Workflow execution ........................................................................ 16
7.4 Continuing a failed online/offline stack creation ............................................................ 16
7.5 Failed to deploy NetAct fast pass(formerly INES) compatible metadata ....................... 16
8.Testing instructions ................................................................................................................. 19
9.Rollback instructions ............................................................................................................... 19

Contact: Contact your local Nokia support.

Summary of changes:

Date Version Summary of changes


26-Apr-2017 1.0 Approved version

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 3/19 © Nokia 2017


Version 1.0
Confidential
1. PURPOSE

This document contains installation instructions and other information for a Priority Package
(PP) or Service Package (SP) delivery for the Nokia NetAct product. Priority Package
provides software corrections for major faults. Service Package provides new or enhanced
functionality and possibly also major fault corrections. Changes delivered in this delivery will
be merged in the later Release or Maintenance Package (MP) of the product.

2. SUMMARY

Corrected problems: None


New functionality: This delivery brings PM, FM and CM support for LTE16A MP4 on top of
NetAct 16.8.
Other effects: None

3. CONFIGURATION INFORMATION

This delivery pre-requires Release / MP / SP / PP installed: NetAct 16.8


Changes to be merged in Release / MP: NetAct 17.2
Related problem IDs: None
Is anything restarted during installation? Yes, WAS restart.
Does this delivery bring any database changes? Yes
Installation time in R&D test lab: < 2 hours
Other information: None
Software package name: netact-PPLTE16AMP4-5-disc1.iso
Modified rpm files and versions included in this delivery:
NSN-BTSSiteElementManager-base-17.001775-1.i686.rpm
NSN-BTSSiteElementManager-FLF-16-16.0000_000144_000000.2147-1.noarch.rpm
NSN-BTSSiteElementManager-FL-16-16.0000_000207_000000.2245-1.noarch.rpm
NSN-BTSSiteElementManager-FLC-16-16.000000_000138_000000.2270-1.noarch.rpm
NSN-BTSSiteElementManager-TLC-16A-16A.0000_000134_000000.2272-1.noarch.rpm
NSN-BTSSiteElementManager-FL-16A-16A.0000_000267_000000.2065-1.noarch.rpm
NSN-BTSSiteElementManager-TLF-16A-16A.0000_000196_000000.2030-1.noarch.rpm
NSN-BTSSiteElementManager-TL-16A-16A.0000_000268_000000.2050-1.noarch.rpm
NSN-BTSSiteElementManager-FLF-16A-16A.0000_000200_000000.2030-1.noarch.rpm
NSN-BTSSiteElementManager-TL-15A-15A.0000_000163_000000.2612-1.noarch.rpm
NSN-BTSSiteElementManager-TL-16-16.0000_000184_000000.2104-1.noarch.rpm
NSN-BTSSiteElementManager-FLC-16A-16A.0000_000134_000000.2027-1.noarch.rpm
nokianetworks-NOKLTE.pmb-LTE16A-20161019.013830.70-1.noarch.rpm
nokianetworks-NOKLTE.man-FL16A-20161014.071127.103-1.noarch.rpm
nokianetworks-NOKLTE.man-TL16A-20161018.072030.89-1.noarch.rpm
nokianetworks-NOKLTE.man-TLF16A-20161018.072045.95-1.noarch.rpm
nokianetworks-NOKLTE.man-FLF16A-20161014.071100.91-1.noarch.rpm
nokianetworks-NOKLTE.man-FLC16A-20161019.063136.82-1.noarch.rpm
nokianetworks-NOKLTE.man-TLC16A-20161019.063201.78-1.noarch.rpm
nokianetworks-NOKLTE-integrationmetadatatemplate-20161123.113218.341-1.noarch.rpm

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 4/19 © Nokia 2017


Version 1.0
Confidential
Modified artifacts included in this delivery:
Artifact type Artifact name Artifact version

d3b2 CMDLTE 16.5.2.16500.586

d3b2 CMHLTE 16.5.2.16500.586

confmeta CMDLTE 16.5.2.16500.586

confmeta CMHLTE 16.5.2.16500.586

4. TEST RESULTS

Installation has been successfully verified by using the Installation Instructions presented in
the chapter 5.

5. INSTALLATION INSTRUCTIONS

This delivery is installed by using the Administration Server and NetAct Deployment
Configuration Automation (DCA). Steps before the chapter “Upgrade Product Software” can
be executed before the actual software upgrade.
Verify system before installation by running Preventive Health Check, see instructions in
NetAct Operating Documentation – Troubleshooting – Troubleshooting Tools –
Preventive Health Check – Running Preventive Health Check. Take full system backup
in case rollback option is needed for this delivery.
Adding new optional nodes is not supported during the installation.
Make sure that the sys user password is identical with the system user password when
upgrading on top of NetAct 16.5. The characters; " ' { } [ ] cannot be used in the sys or
system password during the upgrade.
If this delivery is going to be installed in the system equipped with Disaster Recovery, then
follow the “DR equipped NetAct Minor Version Upgrade Guide” document available in TPS
under the “Disaster Recovery” folder.
This document is for both standard NetAct (not Cloud) and NetAct Cloud environments.
Note that some installation workflow commands are only for standard NetAct, followed by
the corresponding command to be executed only in NetAct Cloud environment.

5.1 Copying software to Administration Server

The software (iso) image files of this delivery include the software assets (rpm files) and
the configuration assets (xml files and templates) which will be copied to the
Administration Server by executing the following steps:
1. Power on the Administration Server if it is powered-off:
a. Log in as the root user to the Vcenter by using vSphere Client.
b. Select the Administration Server from navigation tree.
FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 5/19 © Nokia 2017
Version 1.0
Confidential
c. Select Inventory - Virtual Machine - Power - Power On from menu.
If you do not have access to vCenter, powering on the Administration Server
must be requested beforehand from the data center administrator.
Use the following steps in case of NetAct Cloud 16.5 OS (OpenStack):
a. Log in to Horizon as NetAct tenant user.
b. Select Project - Compute - Instances.
c. Select “Start Instance” from the Actions menu for Admin server.
2. Check the Administration Server Tools version by executing the below command:
root@<admin_server># cat /etc/admin_server-release
Expected Administration Server Tools version for NetAct 16.8 release is:
99.0.0.1436.324 (or higher)
3. Download and copy software image (iso) files from NOLS Software Supply Tool to
Administration Server to /var/ directory. After downloading the software, check that
the checksum of the downloaded software matches with the ones shown in NOLS.
4. Execute the system software copying script product_copy.sh, enter:
/opt/misserver/scripts/product_copy.sh -i /var/netact-
PPLTE16AMP4-5-disc*.iso
5. Remove the software image (iso) files after the successful copy operation:
root@<admin_server># rm -vf /var/netact-PPLTE16AMP4-5-
disc*.iso

5.2 Filling in commissioning workflow variables

As preparation for the upgrade, fill in the appropriate values for the variables in the
commissioning_variables.txt file.
1. Copy upgrade_variables.txt template file to the correct place to be used for
commissioningManager.sh with the below command:
root@<admin_server># cp -pv
/opt/commissioning/workflow/xmls/upgrade/upgrade_variables.txt
/opt/commissioning/bin/commissioning_variables.txt
2. Open the file /opt/commissioning/bin/commissioning_variables.txt for
editing.
3. Check and update the values of the following parameters (detailed information on the
parameters can be found in the file). Note especially the BUILD variable:

Variable Description
SYSTEMNAME System name
NETACT_DB_VM_IP IP address of the database VM
OMC_PASSWD The password of the omc user
ROOT_PASSWD The password of the root user
CONF_FILES_ZIP Enter the exact name of the zip file using the
format
configuration_files_<systemname>.z
ip
FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 6/19 © Nokia 2017
Version 1.0
Confidential
Variable Description
Ex:configuration_files_srnbm.zip
CONF_FILES_ZIP_PASSWD The password of the ZIP file (decrypted in the
beginning of upgrade)
NEW_CONF_FILES_ZIP_PASSWD The new password of the ZIP file (encrypted
at the end of upgrade)
BUILD PPLTE16AMP4_5
BUILD_PATH NetAct product build path, usually
/var/builds/NetAct/product
UPGRADE_TYPE Type of upgrade.
For normal upgrade, leave the value as
empty, e.g. UPGRADE_TYPE=
For cloned upgrade, enter the value as -
cloning, e.g. UPGRADE_TYPE=-cloning

5.3 Restoring files

In this step all mandatory files are restored from Unify database node to the Administration
Server. The files restored are:
• backup.tgz
• tsn.tgz (if it exists)
• configuration_files_<systemname>.zip
1. Log in to the Administration Server as the root user.
2. Restore the mandatory files:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Restoring_Files_WF
.xml

5.4 Updating the parameters

The upgrade may bring some changes to parameters used in the previous
installation/upgrade. The parameters from the last installation and the new/updated ones
need to be merged and exported with the NIPE tool.
The parameter files to be imported with the NIPE tool in the next phase are:
/var/netact/${SYSTEMNAME}_vmware_vconf.yml
/var/netact/${SYSTEMNAME}_cluster_info.txt
/var/netact/${SYSTEMNAME}_installation_attr.txt
/var/builds/NetAct/product/PPLTE16AMP4_5/nipe-conf/NetAct8_ini.xml
/var/builds/NetAct/product/PPLTE16AMP4_5/nipe-
conf/NetAct8_upgrade_attrs.txt
Download the latest version of NIPE tools.
1. Extract the nipe.zip file to the appropriate location on your laptop.
2. In the extracted file folder, find and run the nipe.bat file.

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 7/19 © Nokia 2017


Version 1.0
Confidential
NIPE GUI opens.
3. Select File → New Configuration → Virtual machine config and select the correct
virtual machine configuration.
4. Select File → Import Product → Browse and open NetAct8_ini.xml.
5. Select File → Import → VMware Configuration → Browse and open
<systemname>_vmware_vconf.yml.
6. Select File → Import →Cluster Info → Browse and open
<systemname>_cluster_info.txt.
7. Select File → Import →Installation Attributes → Browse and open
<systemname>_installation_attr.txt.
8. Select File → Import →Installation Attributes → Browse and open
NetAct8_upgrade_attrs.txt.
9. In NIPE GUI, go to the NetAct 16 tab → Installation Attributes. Check if there is
any Attribute name without a value defined. Add the value if needed based on the
info / description fields.
If the customer has changed any of the passwords listed in the Installation
Attributes tab, you need to set those to correct ones in NIPE.
10. After parameter values, have been filled, export the files. Select File → Export →
All... and select a temporary directory (e.g c:\temp) directory to save the files
and press Export.
11. After the export, transfer the exported files to /tmp directory on the Administration
Server.

5.5 Executing system configurations

Execute the below command to enable root login to the target nodes and to create the
system configurations files in the standard NetAct (not Cloud) system:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/System_Configuration
s_WF.xml
Run this command in the NetAct Cloud system. The command is the same regardless of
the Cloud infrastructure, whether it is VMware or OpenStack (also in the later chapters):
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/openstack/upgrade/System_Con
figurations_swonly_WF.xml

5.6 Running the Preparing_Upgrade workflow

Run the Preparing_Upgrade workflow in the standard NetAct (not Cloud) system:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Preparing_Upgrade_WF
.xml
Run this command in the NetAct Cloud system:

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 8/19 © Nokia 2017


Version 1.0
Confidential
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/openstack/upgrade/Preparing_
Upgrade_swonly_WF.xml

5.7 Disabling scheduled backups

During the upgrade it is mandatory to disable all the scheduled backups (VDP and Online
backup). See instructions in NetAct Operating Documentation  NetAct
Administration  NetAct Administration Operating Procedures  Administering
Backups  Taking and Restoring Disk-based Backups  Disabling scheduled
backups. Backups are enabled again after the successful upgrade (chapter 6.5).

5.8 Upgrading Product Software

This section provides instructions for the actual software upgrade. During the upgrade,
restarts may occur depending on what is upgraded. Executing the NetAct offline stack
brings downtime.

5.8.1 Creating the NetAct online upgrade stack

In this section, running the commissioningManager.sh script executes the following actions
which are needed for upgrading with the DCA:
• Creates the online upgrade stack
• Stores the XML file name of online upgrade stack to
/var/tmp/online_stack_done.txt for offline upgrade stack creation purposes
1. Log in to the Administration Server as the root user.
2. Create online upgrade stack:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Create_And_Execute
_Online_Upgrade.xml operation=create_online_upgrade_stack
If the online upgrade stack creation fails, see the chapter 7.4 Continuing a failed
online/offline stack creation.

5.8.2 Executing the NetAct online upgrade stack

In this section, running the commissioningManager.sh script executes the following actions
which are needed for upgrading with the DCA:
• Checks the status of the services in the cluster by using smanager.pl
• Executes the online upgrade stack
1. Run the following command:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Create_And_Execute
_Online_Upgrade.xml operation=execute_online_upgrade_stack
Expected outcome:
Online upgrade triggered successfully. Monitor logs in:
/var/log/dca/
Any errors during the online upgrade needs to be handled manually.
FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 9/19 © Nokia 2017
Version 1.0
Confidential
2. Monitor the upgrade progress from the log files in the Administration Server.
root@<admin_server># tailf
/var/log/dca/dca_stack_<systemname>_root.log
The installation is ready when the following message is visible in DCA log:
Installation ready.
If the online upgrade fails, see the chapter 7.2 Continuing a failed upgrade stack
execution.

5.8.3 Creating the NetAct offline upgrade stack

Running the commissioningManager.sh script executes the following actions which are
needed for upgrading with the DCA:
• Creates the offline upgrade stack.
• Stores the XML file name of the offline upgrade stack to
/var/tmp/offline_stack_done.txt for future stack creation purposes.
1. Run the following command:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Create_And_Execute
_Offline_Upgrade.xml operation=create_offline_upgrade_stack
If the offline upgrade stack creation fails, see chapter 7.4 Continuing a failed
online/offline stack creation.

5.8.4 Executing the NetAct offline upgrade stack

In this section, running the commissioningManager.sh script executes the following actions
which are needed for upgrading with the DCA:
• Checks the status of the services in the cluster by using smanager.pl.
• Executes the offline upgrade stack.
• Run the following command:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Create_And_Execute
_Offline_Upgrade.xml operation=execute_offline_upgrade_stack
Expected outcome:
Offline upgrade triggered successfully. Monitor logs in:
/var/log/dca/
Any errors during the offline upgrade needs to be handled manually.
• Monitor the upgrade progress from the log files in the Administration Server with the
command:
root@<admin_server># tailf
/var/log/dca/dca_stack_<systemname>_root.log
There are also VM specific log files in the same folder.
The Installation is ready, when the following message is visible in the DCA log:
Installation ready.
FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 10/19 © Nokia 2017
Version 1.0
Confidential
If the upgrade fails, see chapter 7.2 Continuing a failed upgrade stack execution.

5.9 Completing the upgrade

In this section the Workflow tool (commissioningManager.sh) is executed to finalize the


upgrade. Run this command in the standard NetAct (not Cloud) system:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Finalize_Upgrade_WF.
xml
Run this command in the NetAct Cloud system:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/openstack/upgrade/Finalize_U
pgrade_swonly_WF.xml
This workflow may continue restarting services in the background. Before moving to the
next chapter ensure that all services are in the started state by running the command:
root@<NetAct_VM># smanager.pl status | grep -v started
If there is a need to reboot any servers, it is shown in the workflow output. For instructions
on rebooting NetAct, see NetAct Operating Documentation → NetAct Administration
→ NetAct Administration Operating Procedures → Starting Up and Shutting Down
NetAct → Rebooting NetAct virtual machines.

5.10 Deploying NetAct fast pass FM/PM compatible metadata

1. Log in to any NetAct VM where the generic_mediations service is running as the omc
user.

2. Navigate to the /opt/oss/NOKIA-integrationmanager/bin/ directory by


entering:
omc@<generic_mediations node>$ cd /opt/oss/NOKIA-
integrationmanager/bin/

3. Deploy NetAct fast pass (formerly INES) compatible metadata for Flexi Multiradio BTS
LTE by entering:
omc@<generic_mediations node>$ sh ads_client.sh -nt NOKLTE -v
LTE16A

Expected outcome

An example output:

2015-12-09 08:34:27,287 - [Deploying Adaptation NOKLTE +


LTE16A ...]

2015-12-09 08:34:28,552 - [Adaptation Deployment started for


[NOKLTE + LTE16A]]

2015-12-09 08:34:29,703 - [Deployment Status:STARTED]


FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 11/19 © Nokia 2017
Version 1.0
Confidential
2015-12-09 08:34:29,703 - [Adaptation [NOKLTE + LTE16A] deployment
is up and running background. You could check status via: " sh
ads_client.sh -nt NOKLTE -v LTE16A -q"]

Note:

For Flexi Multiradio BTS LTE, the duration of the deployment is about 1 hour.
4. Check the deployment status by entering:
omc@< generic_mediations node>$ sh ads_client.sh -nt NOKLTE -v
LTE16A -q

Expected outcome

The following is part of an example output:

<DeploymentStatus>

<status neRelease="LTE16A" neType="NOKLTE" ... status="done">


<FragmentStatus

...

...

</status>

</DeploymentStatus>

In the output, check the deployment status under <DeploymentStatus>.

o If it indicates status="done", the deployment is completed.

o If it indicates status="started", the deployment is ongoing. In this case, wait and


check the deployment status again. The duration of the deployment varies according
to the adaptation package size of the network element. Before the deployment is
completed, do not start the deployment for another network element. Otherwise, the
newly started deployment will not be executed by ADS.
o If it indicates status="failed", the deployment is failed. In this case, record the
name of the failed fragment, go to 7.5 Failed to deploy NetAct fast pass(formerly
INES) compatible metadata for possible causes and solutions.

5.11 Verifying the system after installation

Verify the system after the upgrade by running Preventive Health Check workflow.
FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 12/19 © Nokia 2017
Version 1.0
Confidential
1. Log in to the Administration Server as the root user.
2. Run the Preventive Health Check workflow.
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Preventive_Health_
Check_WF.xml

6. COMPLETING POST UPGRADE ACTIONS

After the upgrade, the Workflow tool completes the following tasks:
• Runs customization checker tool.
• Disables SSH root access.
• Encrypts upgrade configuration files in the Administration Server.
A script creates an encrypted ZIP archive of the cluster configuration files. The archive
is stored in the Administration Server, dns master, db and nfs cluster nodes.
The files include, for example:
DCA XML and CSV files under /opt/skynet/dca/dca-install/
Static and dynamic attributes from
/var/builds/hosts/<systemname>/attributes/
The encrypted archive is created to the Administration Server in:
/var/builds/hosts/<systemname>/
configuration_files_<systemname>.zip
The encrypted archive is stored in dns master, db and nfs cluster nodes in:
/opt/oss/install/conf/configuration_files_<systemname>.zip
• Makes and copies the following backup file(s) to the /opt/oss/install/conf/
directory in the database node:
- backup.tgz which includes data of the following directories in the Administration
Server:
 /etc/ssh/
 /root/.ssh/
 /etc/hosts
 /etc/sysconfig/clock
 /etc/localtime
 /var/www/html/ssh/authorized_keys
- tsn.tgz (if needed). Script checks if any Technical Support Notes (TSNs) have
been applied to the system by checking and compressing the content of
/var/builds/hosts/<systemname>/tsn/ directory.
• Deletes passwords of Workflow tool variables.

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 13/19 © Nokia 2017


Version 1.0
Confidential
6.1 Running the NetAct post-upgrade actions with the Workflow tool

1. Log in to the Administration Server as the root user.


2. Run the following command:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Post_Upgrade_Actio
ns_WF.xml

6.2 Deleting passwords of Workflow variables

Before deleting passwords from password file, store the encryption password of upgrade
configuration ZIP file for future use.
1. Print out and store the password for future use.
root@<admin_server># grep ^NEW_CONF_FILES_ZIP_PASSWD
/opt/commissioning/bin/commissioning_variables.txt
2. Run the below command to delete all workflow clear-text passwords from the
commissioning_variables.txt file.
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Cleanup_WF_Passwor
ds_WF.xml

6.3 Removing Workflow tool PRG files

Workflow tool (commissioningManager.sh) makes *.prg files during the upgrade.


Such files need to be removed from the /opt/commissioning/progress directory and
transferred to the /var/log/upgradewfprg directory.
Run the following command:
root@<admin_server>#
/opt/commissioning/workflow/scripts/upgrade/clean_wf_prg_files.sh
-e

6.4 Taking the VDP backup for Administration Server

In case of NetAct Cloud system consult the data center administrator for taking the
Administration Server backup and skip the rest of this chapter.
In case of standard NetAct (not Cloud) take the VDP backup for Administration Server:
1. Execute the instructions in the chapter Creating a backup job in NetAct Operating
documentation → NetAct Administration → NetAct Administration Operating
Procedures → Administering Backups → Taking and Restoring Disk-based Backups →
Taking and restoring backups of virtual machines.
Note: In the creating a backup job chapter, it is mentioned to exclude the backup disk
before creating backup jobs. Do not exclude the backup disk as the Administration Server
VM resides under the backup disk. Ignore the statement and follow the instructions to
create a backup job only for the Administration Server VM.
2. Execute the instructions in the chapter Backing up a virtual machine in NetAct
Operating documentation → NetAct Administration → NetAct Administration Operating

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 14/19 © Nokia 2017


Version 1.0
Confidential
Procedures → Administering Backups → Taking and Restoring Disk-based Backups →
Taking and restoring backups of virtual machines → Triggering backup jobs manually.
Note: Ensure that you select the backup job created in the step 1 to trigger the
Administration Server VM backup job.

6.5 Enabling the scheduled backup

After the successful upgrade enable the scheduled backup (VDP and Online backup)
which was disabled during the upgrade (chapter 5.7) by following the instructions in
NetAct Operating Documentation → NetAct Administration → NetAct Administration
Operating Procedures → Administering Backups → Taking and Restoring Disk-
based Backups → Scheduling an online backup.

6.6 Powering off the Administration Server

Power off the Administration Server:


1. Log in as the root user to the Administration Server.
2. To shut down the Administration Server, enter:
poweroff
If you do not have access to vCenter, powering off the Administration Server must be
requested from the data center administrator.

7. TROUBLESHOOTING

This section provides instructions for troubleshooting the upgrade.

7.1 Cleaning the Administration Server

If the Administration Server is used for several installation or upgrades it may be


necessary to remove old NetAct software products first in order to free disk space so that
product_copy.sh is able to extract the new product from media.
Products are extracted under the /var/builds/ directory.
NetAct products are in /var/builds/NetAct/product/<version>
To free disk space, remove the products which are no longer needed. Also remove the
corresponding NetAct repository (.repo) file from the /etc/yum.repos.d/ directory.

7.2 Continuing a failed upgrade stack execution

If the upgrade stack execution fails, an error is visible in the logs. The problem must be
investigated and if the error is solved and there is no need to create the stack again, you
can restart the stack execution.
Before starting a new stack execution, make sure that the old instance is finished.
1. Log in to the Administration Server as the root user.
2. To find out if the stack execution is finished, enter:
root@<admin_server># ps -ef |grep <stack_filename.csv>
3. If the given <stack_filename.csv> is not listed, start a new instance.

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 15/19 © Nokia 2017


Version 1.0
Confidential
3.1. If the upgrade fails either in stack verification phase or stack execution phase,
investigate and solve the problem and then restart the failing stack with the following
command:
root@<admin_server># /opt/misserver/scripts/execute_stacks.sh
-stacks <stack_filename.csv>

7.3 Continuing a failed Workflow execution

If the Workflow execution fails, an error is visible on the screen and in the logs of the
scripts which were executed by commissioningManager.sh. When the problem is
resolved, you can restart Workflow execution continuing from the previous with the same
commissioning manager command that has failed.

7.4 Continuing a failed online/offline stack creation

If the upgrade stack creation fails, an error is visible in the logs. The problem must be
investigated and if the error is solved, re-execute the stack creation as follows:
• If online stack creation fails, execute the following command:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Create_And_Execute
_Online_Upgrade.xml operation=create_online_upgrade_stack
• If offline stack creation fails, execute the following command:
root@<admin_server># commissioningManager.sh
file=/opt/commissioning/workflow/xmls/upgrade/Create_And_Execute
_Offline_Upgrade.xml operation=create_offline_upgrade_stack

7.5 Failed to deploy NetAct fast pass(formerly INES) compatible metadata

The Adaptation Deployment Suite (ADS) command line indicates that the deployment of
NetAct fast pass (formerly INES) compatible metadata fails.

status="failed"

Solution

1. Check the status of ADS service.


a. Log in as the omc user to any NetAct VM where the was service is running.

To locate the right virtual machine (VM) on which a specific service is running.
b. Check the status by entering:
/opt/cpf/bin/cpfwas_listClusterApplications.sh | grep -i
integration_manager-ear

An example output:

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 16/19 © Nokia 2017


Version 1.0
Confidential
integration_manager-ear netact0025vm27/server1 (STARTED)
netact0025vm25/server1 (STARTED) netact0025vm26/server1 (STARTED)

In the output, ensure that the status is STARTED.

2. Check whether NetAct fast pass (formerly INES) compatible metadata for the network
element release is published in Adaptation Storage.
a. Log in as the omc user to any NetAct VM where the nfs service is running.

b. Go to the directory of Adaptation Storage by entering:


cd /var/opt/oss/global/NSN-
integrationmanager/adaptationStorage

c. Check whether the <NE_type> folder for the network element exists.

o If it exists, go to step 2d.

o If it does not exist, NetAct fast pass (formerly INES) compatible metadata for the
network element is not published in Adaptation Storage. In this case, skip the
following steps in this section and contact the system administrator for further
investigation.

Note:

The <NE_type> and <NE_release> information is provided in the integration


document of the corresponding network element.
d. In the <NE_type> folder, check whether the <NE_release> folder for the network
element release exists.

o If it exists, check all the files and subfolders in the <NE_type> folder by using the
ls -rlt command, and ensure the following:

• The permissions of the files and subfolders are sufficient (-rw-r--r-- for files
and drwxr-xr-x for subfolders).

• For all the files and subfolders, the owner is system and the group is sysop.

o If it does not exist, NetAct fast pass (formerly INES) compatible metadata for the
network element release is not published in Adaptation Storage. In this case, skip
the following steps in this section and contact the system administrator for further
investigation.

3. Check the client log of Adaptation Deployment Suite.


a. Log in as the omc user to any NetAct VM where the generic_mediations service
is running.

b. Check the /var/opt/oss/log/NOKIA-integrationmanager/*.log file.

4. Check the server log of Adaptation Deployment Suite.

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 17/19 © Nokia 2017


Version 1.0
Confidential
a. Log in as the omc user to any NetAct VM where the was service is running.

b. Check the /var/opt/oss/log/NSN-integrationmanager/oss_*.log file.

The following table provides the log errors and their descriptions.

TABLE 1 ADS server errors

Log content Descriptions

Failed to deploy Adaptation deployment fails for a fragment. For more


adaptation, return value:3 information, check the AM log in step 5.

Metadata can not be The parameters for ADS are incorrect, and ADS fails to find
found, please check your metadata in Adaptation Storage.
input

Timeout while deploy Adaptations are not deployed successfully within a certain
adaptation period of time (timeout threshold). ADS marks the deployment
as timeout.

New Request is not ADS accepts only one deployment request at a time. The
accepted since previous previous deployment is not finished. Wait and check the
deployment is not deployment status later. After the previous deployment is
finished... completed, start the new deployment manually.

5. Check the AM log of Adaptation Deployment Suite.


a. Log in as the omc user to any NetAct VM where the was service is running.

b. Check the /var/opt/oss/log/am/oss_*.log file.


o To check PM Warehouse (PMWH) fragment deployment, search pmwh in the file.

o To check PMB fragment deployment, search pmb in the file.

Note:

For more information on PMWH and PMB fragment deployment, check the PDDS
and PMDC logs.

o To check CMUI fragment deployment, search cmui in the file.

o To check AOMCAP fragment deployment, search aomcap in the file.

o To check FMB fragment deployment, search fmb in the file.

o To check NADA fragment deployment, search nada in the file.


FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 18/19 © Nokia 2017
Version 1.0
Confidential
o To check MAN fragment deployment, search man in the file.

o To check FMC fragment deployment, search fmc in the file.

o To check FileIC fragment deployment, search fileic in the file.

o To check Common fragment deployment, search common in the file.

6. Check the PM Dynamic Deploy Suite (PDDS) log of Adaptation Deployment Suite.
a. Log in as the omc user to any NetAct VM where the generic_mediations service
is running.

b. Check the /var/opt/oss/log/ne3sws_dynamicadaptation/oss_*.log file.

7. Check the PM deployment controller (PMDC) log of Adaptation Deployment Suite.


a. Log in as the omc user to any NetAct VM where the was service is running.

b. Check the /var/opt/oss/log/pmdc/oss_*.log file.

8. TESTING INSTRUCTIONS

PPLTE16AMP4 functionality can be verified by executing the basic operations of


FM/PM/CM applications for LTE16A MP5 eNBs.

9. ROLLBACK INSTRUCTIONS

There is no delivery specific rollback for this delivery. Restore full system backup if needed.

FL16A 6.0 PPLTE16AMP4 Installation Instructions - Page 19/19 © Nokia 2017


Version 1.0
Confidential