Installation and Upgrade Guide - Nokia Documentation

Alcatel-Lucent 5620SERVICE AWARE MANAGER

Alcatel-Lucent 5650CONTROL PLANE ASSURANCE MANAGERI N S T A L L A T I O N A N D U P G R A D E G U I D E

Alcatel-Lucent ProprietaryThis document contains proprietary information of Alcatel-Lucent and is not to be disclosedor used except in accordance with applicable agreements.Copyright 2016 © Alcatel-Lucent. All rights reserved.

I N S T A L L A T I O N A N D U P G R A D E G U I D E

Release 13.0 R8 | May 2016 | 3HE 09796 AAAH TQZZA Issue 1

When printed by Alcatel-Lucent, this document is printed on recycled paper.

All specifications, procedures, and information in this document are subject to change and revision at any time without notice. The information contained herein is believed to be accurate as of the date of publication. Alcatel-Lucent provides no warranty, express or implied, regarding its contents. Users are fully responsible for application or use of the documentation.

Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, lightRadio, and TiMetra are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

Copyright 2016 Alcatel-Lucent.All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.

However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.



Contents

Getting started

1 — Before you begin 1-11.1 Overview ................................................................................. 1-2

Guide conventions ................................................................... 1-2Platform support ..................................................................... 1-3samadmin user........................................................................ 1-3System migration from obsolete platforms ...................................... 1-4

1.2 Special upgrade requirements ........................................................ 1-4Disk space requirements ............................................................ 1-5

1.3 Virtualization support .................................................................. 1-65620 SAM server and database requirements and restrictions ................ 1-6Client requirements and restrictions.............................................. 1-6Additional element manager requirements and restrictions .................. 1-6

1.4 Deployment restrictions................................................................ 1-7Network restrictions ................................................................. 1-7Platform restrictions................................................................. 1-8Security restrictions ................................................................. 1-8Software restrictions ................................................................ 1-8

1.5 Deployment requirements ............................................................ 1-10Network requirements.............................................................. 1-10Platform requirements ............................................................. 1-12Security requirements .............................................................. 1-12Software requirements ............................................................. 1-13Procedure 1-1 To obtain the system ID of a station for 5620 SAM or

5650 CPAM license acquisition .............................................. 1-141.6 5620 SAM management network configuration .................................... 1-15

Management network configuration example .................................. 1-16

Alcatel-Lucent 5620 SAM | 5650 CPAM iii5620 SAM | 5650 CPAMInstallation and Upgrade Guide

Contents


1.7 Automated client installation, upgrade, and configuration ..................... 1-18Client software upgrades .......................................................... 1-18Client configuration changes ...................................................... 1-18Considerations and restrictions ................................................... 1-19

2 — RHEL OS configuration 2-12.1 Overview ................................................................................. 2-22.2 OS configuration restrictions .......................................................... 2-22.3 OS configuration requirements ....................................................... 2-2

Firewall requirements ............................................................... 2-3Procedure 2-1 To prepare disk partitions for 5620 SAM installation ........ 2-3Procedure 2-2 To reset the disk partition reserved block counts............ 2-4

2.4 RHEL OS package groups and packages .............................................. 2-6Package installation method ....................................................... 2-6Server and database packages ..................................................... 2-7Client and client delegate server packages...................................... 2-9

3 — RHEL disk configuration 3-13.1 Overview ................................................................................. 3-2

Procedure 3-1 To configure a 5620 SAM disk partition createdafter the RHEL OS installation ............................................... 3-2

3.2 Using RAID with the 5620 SAM......................................................... 3-33.3 Logical disk management .............................................................. 3-43.4 Disk partitioning for trial deployments .............................................. 3-53.5 Disk partitioning for live deployments.............................................. 3-10

4 — Configuring SSL security 4-14.1 Overview ................................................................................. 4-2

GUI client and main server communication...................................... 4-3Managing SSL certificate expiry.................................................... 4-4

4.2 Workflow to configure SSL............................................................. 4-54.3 SSL security configuration ............................................................. 4-6

Procedure 4-1 To prepare a 5620 SAM system for SSL......................... 4-6Procedure 4-2 To enable SSL on a main server ................................. 4-9Procedure 4-3 To enable SSL on an auxiliary server .......................... 4-11Procedure 4-4 To disable SSL on a RHEL single-user client or

client delegate server ........................................................ 4-13Procedure 4-5 To disable SSL on a Windows single-user client or

client delegate server ........................................................ 4-15Procedure 4-6 To enable SSL and HTTPS for an OSS client .................. 4-17Procedure 4-7 To enable SSL and HTTPS on a Cflowd auxiliary

server ........................................................................... 4-18

5 — Configuring Small Cell management 5-15.1 Overview ................................................................................. 5-25.2 Migration from SCMS.................................................................... 5-25.3 HDM installation and configuration................................................... 5-2

iv Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM

Installation and Upgrade Guide

Contents


5.4 Small Cell management configuration ............................................... 5-3Procedure 5-1 To enable Small Cell management ............................. 5-3

5620 SAM system deployment

6 — 5620 SAM installation 6-16.1 Overview ................................................................................. 6-26.2 5620 SAM installation procedures list ................................................ 6-26.3 Standalone system installation workflow............................................ 6-46.4 Standalone system installation........................................................ 6-5

Procedure 6-1 To install a standalone 5620 SAM system ...................... 6-56.5 Redundant system installation workflow ........................................... 6-436.6 Redundant system installation ....................................................... 6-44

Procedure 6-2 To install a redundant 5620 SAM system...................... 6-446.7 Auxiliary server installation ........................................................ 6-135

Procedure 6-3 To install a 5620 SAM auxiliary server....................... 6-135Procedure 6-4 To add an auxiliary server to a 5620 SAM system ......... 6-149

6.8 Cflowd auxiliary server installation ............................................... 6-156Procedure 6-5 To install a 5620 SAM Cflowd auxiliary server ............. 6-156Procedure 6-6 To configure Cflowd auxiliary server communication .... 6-158

6.9 Auxiliary database installation..................................................... 6-161Procedure 6-7 To install a 5620 SAM auxiliary database ................... 6-161Procedure 6-8 To enable an auxiliary database in a 5620 SAM

system......................................................................... 6-1646.10 Analytics server installation ........................................................ 6-167

Procedure 6-9 To install and enable a 5620 SAM analytics server ........ 6-167

7 — 5620 SAM upgrade 7-17.1 Overview ................................................................................. 7-27.2 5620 SAM upgrade procedures list.................................................... 7-27.3 5620 SAM system upgrade preparation .............................................. 7-3

Procedure 7-1 To perform the pre-upgrade tasks .............................. 7-37.4 Standalone system upgrade workflow .............................................. 7-127.5 Standalone system upgrade .......................................................... 7-13

Procedure 7-2 To upgrade a standalone 5620 SAM system................... 7-137.6 Redundant system upgrade workflow............................................... 7-567.7 Redundant system upgrade........................................................... 7-60

Procedure 7-3 To upgrade a redundant 5620 SAM system ................... 7-607.8 Auxiliary server upgrade ............................................................ 7-166

Procedure 7-4 To upgrade a 5620 SAM auxiliary server .................... 7-1667.9 Cflowd auxiliary server upgrade ................................................... 7-181

Procedure 7-5 To upgrade a 5620 SAM Cflowd auxiliary server ........... 7-181

8 — 5620 SAM conversion to redundancy 8-18.1 Overview ................................................................................. 8-28.2 Conversion to redundancy procedures list .......................................... 8-2

Alcatel-Lucent 5620 SAM | 5650 CPAM v5620 SAM | 5650 CPAMInstallation and Upgrade Guide

Contents


8.3 Conversion to redundancy workflow ................................................. 8-38.4 Conversion to redundancy ............................................................. 8-4

Procedure 8-1 To convert a standalone 5620 SAM system to aredundant system .............................................................. 8-5

9 — 5620 SAM conversion to IPv6 9-19.1 Overview ................................................................................. 9-29.2 Conversion to IPv6 procedures list ................................................... 9-29.3 Conversion to IPv6 workflow .......................................................... 9-39.4 Conversion to IPv6 preparation ....................................................... 9-4

Procedure 9-1 To perform the pre-conversion tasks........................... 9-49.5 Standalone system conversion to IPv6 ............................................... 9-8

Procedure 9-2 To convert a standalone 5620 SAM system to IPv6 ........... 9-89.6 Redundant system conversion to IPv6 .............................................. 9-17

Procedure 9-3 To convert a redundant 5620 SAM system to IPV6 .......... 9-17

10 — 5620 SAM uninstallation 10-110.1 Overview ................................................................................ 10-210.2 System uninstallation procedures list............................................... 10-210.3 System uninstallation workflow...................................................... 10-310.4 System uninstallation.................................................................. 10-3

Procedure 10-1 To uninstall the 5620 SAM analytics server software...... 10-3Procedure 10-2 To uninstall the 5620 SAM auxiliary database

software ........................................................................ 10-4Procedure 10-3 To uninstall the 5620 SAM auxiliary server software ...... 10-6Procedure 10-4 To uninstall the Cflowd auxiliary server software ....... 10-10Procedure 10-5 To uninstall the 5620 SAM main server software......... 10-11Procedure 10-6 To uninstall the 5620 SAM database software ............ 10-15

5650 CPAM system deployment

11 — 5650 CPAM installation 11-111.1 Overview ................................................................................ 11-211.2 5650 CPAM installation procedures list ............................................. 11-211.3 5650 CPAM installation ................................................................ 11-3

Procedure 11-1 To install a standalone 5650 CPAM system.................. 11-3Procedure 11-2 To install a redundant 5650 CPAM system ................ 11-23

12 — 5650 CPAM upgrade 12-112.1 Overview ................................................................................ 12-212.2 5650 CPAM upgrade procedures list ................................................. 12-212.3 5650 CPAM upgrade .................................................................... 12-3

Procedure 12-1 To upgrade a standalone 5650 CPAM system ............... 12-4Procedure 12-2 To upgrade a redundant 5650 CPAM system .............. 12-25

vi Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


Contents


13 — 5650 CPAM uninstallation 13-113.1 Overview ................................................................................ 13-213.2 5650 CPAM uninstallation procedures list .......................................... 13-213.3 5650 CPAM uninstallation ............................................................. 13-2

Procedure 13-1 To uninstall the 5650 CPAM software ........................ 13-3

5620 SAM | 5650 CPAM client deployment

14 — Single-user GUI client deployment 14-114.1 Overview ................................................................................ 14-2

Platform requirements ............................................................. 14-2Security requirements .............................................................. 14-3Procedure 14-1 To install the Oracle JRE on a RHEL client station ........ 14-4

14.2 Single-user client deployment procedures list .................................... 14-614.3 Single-user client installation ........................................................ 14-7

Procedure 14-2 To install a single-user client on RHEL using aweb browser ................................................................... 14-7

Procedure 14-3 To install a single-user client on RHEL using theclient installer ............................................................... 14-12

Procedure 14-4 To install a single-user client on Windows using aweb browser ................................................................. 14-19

Procedure 14-5 To install a single-user client on Windows usingthe client installer .......................................................... 14-25

14.4 Single-user client upgrade .......................................................... 14-32Procedure 14-6 To upgrade a single-user client on RHEL .................. 14-32Procedure 14-7 To upgrade a single-user client on Windows.............. 14-35

14.5 Single-user client uninstallation ................................................... 14-38Procedure 14-8 To uninstall a RHEL single-user client using a web

browser ....................................................................... 14-38Procedure 14-9 To uninstall a RHEL single-user client using the

client uninstaller ............................................................ 14-42Procedure 14-10 To uninstall a Windows single-user client using a

web browser ................................................................. 14-45Procedure 14-11 To uninstall a Windows single-user client using

an OS utility .................................................................. 14-49

15 — Client delegate server deployment 15-115.1 Overview ................................................................................ 15-2

Platform requirements ............................................................. 15-2Security requirements .............................................................. 15-2

15.2 Client delegate server deployment procedures list............................... 15-415.3 Client delegate server installation .................................................. 15-5

Procedure 15-1 To install a client delegate server on RHEL................. 15-5Procedure 15-2 To install a client delegate server on Windows .......... 15-13Procedure 15-3 To add a client delegate server to an existing

system......................................................................... 15-21

Alcatel-Lucent 5620 SAM | 5650 CPAM vii5620 SAM | 5650 CPAMInstallation and Upgrade Guide

Contents


15.4 Client delegate server upgrade .................................................... 15-26Procedure 15-4 To upgrade a client delegate server on RHEL ............ 15-26Procedure 15-5 To upgrade a client delegate server on Windows........ 15-29

15.5 Client delegate server uninstallation ............................................. 15-32Procedure 15-6 To uninstall a RHEL client delegate server ............... 15-32Procedure 15-7 To uninstall a Windows client delegate server ........... 15-36

Appendices

A. 5620 SAM installation parameters A-1A.1 Standalone database and main server installation parameters.................. A-2A.2 Redundant database and main server installation parameters .................A-10A.3 Auxiliary server installation parameters............................................A-30A.4 Single-user client and client delegate server installation parameters ........A-33

B. 5620 SAM upgrade parameters B-1B.1 Standalone database and main server upgrade parameters...................... B-2B.2 Redundant database and main server upgrade parameters ...................... B-8B.3 Auxiliary server upgrade parameters ...............................................B-22

C. 5620 SAM conversion to redundancy parameters C-1C.1 5620 SAM conversion to redundancy parameters .................................. C-2

D. 5650 CPAM installation parameters D-1D.1 5650 CPAM installation parameters .................................................. D-2

E. 5650 CPAM upgrade parameters E-1E.1 5650 CPAM upgrade parameters ...................................................... E-2

viii Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


Alcatel-Lucent 5620 SAM | 5650 CPAM 5620 SAM | 5650 CPAMInstallation and Upgrade Guide

Getting started

1 — Before you begin

2 — RHEL OS configuration

3 — RHEL disk configuration

4 — Configuring SSL security

5 — Configuring Small Cell management


Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM



Alcatel-Lucent 5620 SAM | 5650 CPAM 1-15620 SAM | 5650 CPAMInstallation and Upgrade Guide


1.1 Overview 1-2

1.2 Special upgrade requirements 1-4

1.3 Virtualization support 1-6

1.4 Deployment restrictions 1-7

1.5 Deployment requirements 1-10

1.6 5620 SAM management network configuration 1-15

1.7 Automated client installation, upgrade, and configuration 1-18



1-2 Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


1.1 Overview

This chapter defines the general conditions that apply to 5620 SAM deployment. Before you attempt to deploy or configure a 5620 SAM component, you must comply with the conditions in this chapter and ensure that the 5620 SAM platform is configured as described in the other chapters of the “Getting started” volume.

The “5620 SAM | 5650 CPAM client deployment” volume contains OS-specific information about single-user GUI client and client delegate server deployment.

Guide conventions

This guide uses the following terminology:

• station—a discrete processing entity, such as a physical or virtual computer• peer—an equivalent component in the same 5620 SAM system. For example, the

peer main server of the primary main server in a redundant deployment is the standby main server. The term peer is irrespective of the primary or standby role.

The figures and associated text in the guide display a typical or default parameter value when appropriate. A default value is acceptable in most deployment environments, but must be validated against specific requirements, for example, firewall constraints. See the 5620 SAM Planning Guide and the current 5620 SAM Release Notice for more information, or contact Alcatel-Lucent technical support.

An installer panel field that has a yellow background is a mandatory field that requires a valid entry before you proceed to the next panel.

The 5620 SAM installer prompts the operator before it creates a directory in the file system. The prompts are not described in procedure steps.

Warning — A 5620 SAM system upgrade from a release earlier than 12.0 R5 has special requirements. To ensure the upgrade success, you must prepare for the upgrade as directed in section 1.2.

Caution 1 — Alcatel-Lucent supports 5620 SAM software deployment only under the conditions described in this guide, the 5620 SAM Planning Guide, and the 5620 SAM Release Notice.

Caution 2 — A 5620 SAM upgrade, conversion to redundancy, or conversion to IPv6 requires a thorough understanding of 5620 SAM system administration and OS requirements. The operation must be planned, documented, and tested in advance on a lab system that is representative of the target live network.

Contact Alcatel-Lucent technical support to assess the requirements of your 5620 SAM deployment, and for information about the Alcatel-Lucent upgrade service, which Alcatel-Lucent strongly recommends that you engage for any type of deployment.




Platform supportThe following components described in this guide comprise a 5620 SAM system:

• one standalone main server, or two in a redundant deployment• one standalone 5620 SAM database, or two in a redundant deployment• one or more auxiliary servers (optional)• one auxiliary database (required for 5620 SAM analytics, optional otherwise)• one or more Cflowd auxiliary servers (optional)• one analytics server (required for 5620 SAM analytics)• one or more single-user GUI clients or client delegate servers

Table 1-1 lists the supported platforms for each 5620 SAM component type.

Table 1-1 5620 SAM platform support by component

Hardware virtualization

You can deploy any 5620 SAM component in a virtual machine, or VM. See the 5620 SAM Planning Guide for VM system requirements, and section 1.3 for VM deployment requirements and restrictions.

samadmin userA 5620 SAM or 5650 CPAM server installation creates a RHEL user called samadmin that is required for 5620 SAM operation and administration.

• The account is created on each main, auxiliary, 5650 CPAM, and RHEL client delegate server station.

• The samadmin user owns all 5620 SAM and 5650 CPAM server processes.• The samadmin home directory is the server installation directory, which

samadmin owns. The root user owns few files below the directory.• The root user assigns the initial samadmin user password.• Only the samadmin user can start or stop a server, run server scripts, or modify

the server configuration.• Server uninstallation does not remove the samadmin account or home directory.• Root user privileges are required only for a few low-level functions.

5620 SAM component RHEL Microsoft Windows

Main server ✓

Auxiliary server ✓

Cflowd auxiliary server ✓

5620 SAM database ✓

Auxiliary database ✓

Analytics server ✓

Client delegate server ✓ ✓

Single-user client ✓ ✓





System migration from obsolete platformsTo move a 5620 SAM system from an obsolete platform to RHEL, you must use a migration procedure from the 5620 SAM | 5650 CPAM Installation and Upgrade Guide for the 5620 SAM release that is installed on the obsolete platform. You can then upgrade the 5620 SAM system, directly or indirectly, depending on the release, to the current 5620 SAM release.

For example, the migration of a Release 9.0 R5 5620 SAM system on Solaris SPARC to RHEL must be performed in the following stages:

• migration from the Solaris SPARC to Solaris x86, using the Release 9.0 R5 5620 SAM | 5650 CPAM Installation and Upgrade Guide migration procedure

• Solaris x86 system upgrade to a target release that supports RHEL• Solaris x86 migration to RHEL, using the migration procedure in the

target-release 5620 SAM | 5650 CPAM Installation and Upgrade Guide• upgrade of the RHEL system to the current 5620 SAM release

1.2 Special upgrade requirements

A 5620 SAM system upgrade from a release earlier than 12.0 R5 involves the migration of all NE configuration backups from the 5620 SAM database to the main-server file system. Depending on factors that are not limited to the following, the migration may take considerable time to complete:

• number of managed NEs• average configuration backup size• number of retained backups per NE• 5620 SAM deployment type—standalone or redundant• network latency

The migration begins automatically during the standalone or primary main server initialization that follows an upgrade. In a redundant deployment, the migration includes the synchronization of the migrated files between the main servers, which may require hours or days to complete.

Note — Main server uninstallation does not delete or otherwise affect the NE configuration backup files.




Disk space requirementsThe NE backup migration requires a separate, mounted disk partition called opt/5620sam/nebackup. The partition size is derived, based on the size of the managed network and the types of NEs in the network. To assist with the partition sizing, use the following formula to calculate the space required per NE type; see Table 1-2 for the size factor values:

data capacity = backup size × number of NEs × backups per NE × 2.5

Table 1-2 Configuration backup file sizes by NE type

Note — The formula is a guideline for planning purposes only; the actual size may require adjustment. Alcatel-Lucent recommends that you use the size of the largest backup per NE type in your network as the backup size, and multiply the final number by 2.5, as shown in the formula. This calculation accounts for network and NE backup growth, and accommodates the storage of compressed archive files.

NE type Backup size

1830 PSS 400 kbytes

7210 SAS 200 kbytes

7450 ESS, 7710 SR, 7750 SR MG, 7750 SR, 7950 XRS

1.5 Mbytes

7705 SAR 250 kbytes

9500 MPR 1.5 Mbytes

eNodeB 250 kbytes

OmniSwitch 30 kbytes





1.3 Virtualization support

This section describes the requirements and restrictions for 5620 SAM deployment in a VM. 5620 SAM deployment is supported in the following virtual environments:

• KVM• VMware

See the 5620 SAM Planning Guide for the hardware virtualization requirements, and for the specific configuration requirements of each supported environment.

5620 SAM server and database requirements and restrictionsThe following conditions apply to 5620 SAM main server, auxiliary server, client delegate server, and database deployment in a VM.

• The guest OS must be a 5620 SAM-supported version of RHEL 6 Server x86-64.• A RHEL deployment on VMware requires VMXNET 3 NIC adapters. See the

VMware documentation for information about the NIC adapters.

Client requirements and restrictionsThe following conditions apply to 5620 SAM client deployment in a VM.

• You can deploy a 5620 SAM VM client in a live network environment only if the client resources are dedicated to the guest OS and not shared or oversubscribed.

• The guest OS must be a supported version of RHEL or Windows, as defined in the 5620 SAM Planning Guide.

• The supported connection application for a VMware ESXi Windows platform is Windows Remote Desktop.

Additional element manager requirements and restrictionsThe following conditions apply to a 5620 SAM single-user GUI client or client delegate server in a VM that requires the installation of an additional element manager on the same platform, or is to use an additional NE management interface.

• You can use two or more NICs to isolate network traffic between the client VM and the managed NEs. Such a configuration may be required when an additional element manager, for example, NEtO, must share the client resources, or when web-based NE management is to be performed from the client station.

• Additional RAM, disk space, and CPU resources are required to accommodate an element manager that shares a client platform.

Note 1 — Before you deploy a 5620 SAM component in a VM, you must also install the latest VMware Tools software. See the VMware documentation for information about VMware Tools.

Note 2 — The requirements and restrictions in sections 1.4 and 1.5 apply also to 5620 SAM deployment in a VM.




1.4 Deployment restrictions

This section describes the general conditions and constraints under which 5620 SAM deployment is supported.

Network restrictions• Alcatel-Lucent does not support DNS or NIS name resolution on a main or

auxiliary server, and a pre-existing name service must not conflict with 5620 SAM server address resolution. Alcatel-Lucent does support DNS or NIS name resolution on a 5620 SAM GUI or OSS client.

• You cannot specify “localhost” or an alias IP address to identify a component.• A 5620 SAM main server listens for GUI and OSS client communication on only

one interface unless you specify a hostname for the main server during an installation or upgrade.

• You cannot use a hostname to identify a database station; other 5620 SAM components use only an IP address to reach a database.

• All IP communication from a 5620 SAM auxiliary server to a 5620 SAM main server must originate from one IP address, which is the auxiliary server address specified during the main server configuration. A main server rejects communication from an auxiliary server if the auxiliary server uses a source address other than the configured address.

• During a single-user client installation, you can specify a hostname instead of an IP address to identify a main server. A client upgrade occurs automatically through a connection to a server named in the client configuration.

IPv4 and IPv6

• All 5620 SAM components must communicate with all other 5620 SAM components using exclusively IPv4 or IPv6.

• Before you can specify an IPv6 address for a 5620 SAM component, the IPv6 interface must be plumbed and operational. See the OS documentation for information about enabling and configuring an IPv6 interface.

• A main server can perform network management using both IPv4 and IPv6.• Before you use a procedure in chapter 9 to convert a 5620 SAM system from IPv4

to IPv6, the system must be at the software release described in this guide.

Caution — The use of NAT between 5620 SAM servers and databases is not supported.

The 5620 SAM supports NAT only between the following:

• main server and single-user client or client delegate server• main or auxiliary server and OSS client• main or auxiliary server and managed network

Caution — Alcatel-Lucent does not support 5620 SAM system conversion from IPv4 to IPv6 during an upgrade or conversion to redundancy.





Platform restrictions• A 5620 SAM single-user client or client delegate server cannot be installed on the

same station as a 5620 SAM server or database.• A 5620 SAM single-user client and client delegate server cannot be installed on

the same station.• An auxiliary server or client delegate server requires a dedicated station.

Alcatel-Lucent does not support the sharing of an auxiliary or client delegate server station with another 5620 SAM component.

• If you plan to convert a standalone 5620 SAM system to a redundant system and plan to upgrade the system, you must perform the upgrade before the conversion.

Security restrictions• The user that starts a 5620 SAM client must be the user that installs the client

software, or another user that has read, write, and execute privileges on the client files and directories.

• A 5620 SAM domain name defines the network-management domain to which a 5620 SAM component belongs and must be unique to a network. A 5620 SAM component can interact only with other 5620 SAM components in the same 5620 SAM domain. During 5620 SAM installation, you must specify the same domain name for all components in a 5620 SAM system.

Software restrictions• The 5620 SAM server and database installers are available in English only.• The prompts and descriptive text displayed during a client installation are in

English; subsequent client upgrades use the language associated with the locale configured for the client on the server.

• The 5620 SAM supports the upgrade of a 5620 SAM component that is no more than two major releases older than the current release. For example, you can upgrade a 5620 SAM Release 11.0 system to Release 13.0, but you cannot upgrade a Release 10.0 system directly to Release 13.0; you must first perform an intermediate upgrade to at least Release 11.0.

• You cannot upgrade the 5620 SAM to a release that is chronologically older than the currently installed release. For example, you cannot upgrade from Release 10.0 R8 to 11.0 R1, because Release 11.0 R1 predates Release 10.0 R8.

Note 1 — A redundant 5620 SAM system upgrade requires a network-management outage and must be performed only during a scheduled maintenance period of sufficient duration for the upgrade.

Note 2 — The upgrade of a 5650 CPAM server, or a 5620 SAM main server that is integrated with a 5650 CPAM server, requires additional time if the 5650 CPAM checkpoints are retained. The additional time varies, depending on the platform resources, managed network size, and checkpoint schedule. To minimize the upgrade time, you must remove the 5650 CPAM checkpoints before the upgrade.

Note 3 — After an upgrade to an intermediate release, for example, an upgrade from Release 10.0 to Release 11.0 before a final upgrade to Release 13.0, you must allow each 5620 SAM main server to initialize fully before the final upgrade, or the final upgrade fails.




• You cannot share an existing Oracle installation with the 5620 SAM, and no other application can use the 5620 SAM Oracle software.

• The following 5620 SAM and 5650 CPAM components are installed in the following directories, which cannot be changed:

• main or 5650 CPAM server—/opt/5620sam/server• auxiliary server—/opt/5620sam/auxserver• 5620 SAM database—/opt/5620sam/samdb• Oracle software for 5620 SAM database—/opt/5620sam/oracle12r1

• You can complete a server installation, upgrade, or conversion without specifying a license file. However, if you do not specify a license file, you cannot start a 5620 SAM main server or 5650 CPAM server until you import a license. See the “Software and license configuration procedures” section in the 5620 SAM System Administrator Guide for information about importing a license.

Release-specific restrictions

• The 5620 SAM Release Notice contains important release-specific information. Ensure that you read the Release Notice for the current release before you attempt a 5620 SAM installation or upgrade.

Caution 1 — A 5620 SAM upgrade does not preserve non-default settings in configuration files such as nms-server.xml. If a 5620 SAM configuration file contains non-default settings that you want to retain after an upgrade, contact Alcatel-Lucent technical support for assistance before the upgrade.

Caution 2 — At the beginning of a 5620 SAM server upgrade, the 5620 SAM installation utility backs up specific configuration and log files to a timestamped directory under the installation directory. The utility then deletes specific directories under the installation directory.

If you create or modify a file under the server installation directory, you risk losing the file during a 5620 SAM upgrade unless you first back up the file to a location that is unaffected by the upgrade activity.

Caution 3 — A 5620 SAM server upgrade applies a default set of file permissions to each directory below the server installation directory. If you change the file permissions of a directory below the server installation directory and want the permissions to be in effect after an upgrade, you must re-apply the permissions after the upgrade.





1.5 Deployment requirements

You must satisfy the requirements in this section before you attempt to perform a procedure in this guide.

Network requirements

The 5620 SAM network requirements apply to the following:

• management network—the network over which the 5620 SAM components communicate with each other

• managed network and external systems—the managed NEs, and the systems that are integrated with the 5620 SAM, for example, the 5780 DSC

Management network

The following requirements apply to the 5620 SAM management network.

• During a main server installation or upgrade, you must use hostnames to identify the main server interfaces under the following conditions:

• when the OSS and GUI clients communicate with a main server using multiple IP addresses for the main server

• when the OSS and GUI clients use different addresses to communicate with a main server through one interface on the main server

• An auxiliary server must be accessible to each main server and database in a redundant 5620 SAM deployment. Optimally, all components in a deployment are in the same LAN and have high-quality network interconnection.

• Each auxiliary database in an auxiliary database cluster must be on the same side of the management LAN, and not geographically dispersed.

Note 1 — If you use SSH X forwarding to perform a procedure in this guide, the “su - oracle” command fails. In such a scenario, you must log in directly as the Oracle management user to perform the required actions.

Note 2 — You must record all information that you specify when you perform a procedure in this guide, and store the information in a secure location for use during subsequent operations.

Caution — Alcatel-Lucent strongly recommends the use of hostname resolution for GUI and OSS client communication with a 5620 SAM main server in a NAT environment.

When IP addresses are used in a NAT environment, the following conditions apply:

• All client communication with the main server must use the public IP address of the server.

• The NAT firewall must be configured to allow the main server to communicate with itself using the public IP address.




• When two components use hostnames to communicate, the /etc/hosts file on each component station must contain the following local entries; see section 1.6 for more information and a configuration example:

• an entry that maps the hostname assigned to the interface on the other component to the IP address used to reach the other component

• an entry that maps the hostname of the other component station to each IP address used to reach the other component

• Using NAT adds an extra level of complexity to a 5620 SAM network. The /etc/hosts file on each component station must contain the correct public and private address entries for reaching other components at the following times:

• during normal operation• after a 5620 SAM component or network component failure

• Specifying a TCP or UDP port other than the default during an installation or upgrade can affect a firewall configuration. Ensure that you record any changes to default port numbers and make the ports available through the firewalls.

• When you use a hostname to identify a 5620 SAM component, you must use local hostname resolution.

Managed network and external systems

The following requirements apply to the network of 5620 SAM- managed devices and to the external systems with which the 5620 SAM is integrated.

• Before you upgrade a 5620 SAM system, you must confirm that the new 5620 SAM software release supports the release of each 5620 SAM-managed device. If this is not true, you must perform one of the following before you attempt the upgrade, or service disruption may occur.

• Upgrade the device to a release that the new 5620 SAM release supports.• Use a 5620 SAM client to unmanage the device, remove the device from the

managed network, and remove the discovery rule element for the device.• Before you upgrade a 5620 SAM system, you must ensure that the new

5620 SAM software is compatible with the software release of each connected external system, for example, the 5620 NM. Contact Alcatel-Lucent technical support about 5620 SAM and external system compatibility.

• A 5620 SAM system that manages eNodeB devices has special disk partitioning requirements. See chapter 3 for information.

• Before the 5620 SAM can manage an eNodeB, functions such as PM statistics transfers and network snapshots require configuration. See the 5620 SAM LTE RAN User Guide for specific eNodeB management information.

Caution 1 — If a 5620 SAM system that is to be upgraded manages a device as a GNE, and the new 5620 SAM release supports native management of the device, you must unmanage the device and delete it from the 5620 SAM database before the upgrade.

After the upgrade, you can use the 5620 SAM to discover and manage the device natively, rather than as a GNE.

Caution 2 — The 5620 SAM and eNodeB devices require a common time-synchronization server that runs a protocol such as NTP. 5620 SAM eNodeB PM statistics collection fails when the eNodeB and 5620 SAM real-time clocks are not synchronized.





• Before you can use the 5620 SAM to manage Small Cell NEs, you must perform specific configuration steps on each main and auxiliary server. See chapter 5 for the configuration information.

Platform requirements• The 5620 SAM platform must meet the minimum requirements described in the

5620 SAM Planning Guide for the current release.• The OS release and patch level of all main server, auxiliary server, and database

stations in a 5620 SAM deployment must be identical.• 5620 SAM deployment in a live network requires a station that has at least two

hard disks. Alcatel-Lucent supports a one-disk layout only for lab trials or for demonstration purposes.

• In a redundant 5620 SAM deployment, the main server time zones must match.• The hostname of a 5620 SAM component must meet the following criteria.

• It contains only ASCII alphanumeric and hyphen characters.• It does not begin or end with a hyphen.• If the hostname is an FQDN, period characters delimit the FQDN components.• The FQDN of the hostname does not exceed 63 characters.

• The 5620 SAM platform must be dedicated to the 5620 SAM only. 5620 SAM operation may be adversely affected by the activity of other software on the same platform. Alcatel-Lucent does not support the sharing of the 5620 SAM platform.

• Before you install or upgrade a redundant 5620 SAM system, you must enable SSH on each main server, auxiliary server, and database station in the system.

• If the 5620 SAM is to collect statistics on a large scale, as defined in the 5620 SAM Planning Guide, Alcatel-Lucent requires the use of a disk array with the 5620 SAM database to increase performance. See chapter 3 for information.

• The 5620 SAM OSS and GUI client real-time clocks must always be synchronized with the main server real-time clock. Alcatel-Lucent strongly recommends using NTP or an equivalent time protocol for synchronization.

Security requirements• The Oracle management user requires full read and write permissions to the

5620 SAM database installation directory and any specifically created partitions, for example, /opt/5620sam/dbbackup.

• The user that installs a 5620 SAM single-user client requires local user privileges only, but must have full access permissions on the client installation directory. The user that opens the client installer must have sufficient file permissions to create the installation directory, or the installation fails.

• The use of sudo for root user privileges is supported for 5620 SAM installation, and for any other action in this guide that requires root user privileges.

Caution — Enabling Small Cell management on an existing 5620 SAM system involves a server restart, which can be service-affecting.

Alternatively, you can configure the function during a server installation or upgrade, before the initial server startup. If you choose to do this, you must ensure that the associated maintenance period includes time for the Small Cell configuration.




Software requirements• A 5620 SAM or 5650 CPAM deployment requires a license file in compressed

format with a .zip extension. A license file has the following characteristics.• The Alcatel-Lucent Software License Manager, or ASLM, generates the file using

the system ID of the host station, which is the station UUID. Procedure 1-1 describes how to obtain a station UUID.

• The file can accommodate two system IDs, which allows the use of the same file on redundant servers; Alcatel-Lucent recommends using one license file in such a case.

• Renaming the compressed file has no effect on the validity of the contained license file, but renaming the contained XML license file renders it invalid.

• The 5620 SAM/5650 CPAM server installation utility copies the license file content to a backup location; a change to the license file content or location after an installation or upgrade does not affect server operation.

• Before you install or upgrade a 5620 SAM system, you must confirm that your 5620 SAM license enables the functions that you require and contains the correct licensed quantity for each type of network object that you intend to manage.

• The database installer and Oracle installation files must be in the same directory.• You must ensure that you have sufficient time to complete a 5620 SAM database

upgrade. The time required for a database upgrade depends on the platform resources, database complexity, and tablespace configuration. See the 5620 SAM Planning Guide for database upgrade time estimates.

• You can opt to purge the current statistics data during a 5620 SAM database upgrade. Purging the statistics data may reduce or increase the upgrade duration, depending on the 5620 SAM release and the database contents. Alcatel-Lucent recommends that you stage an upgrade before you attempt a live upgrade, if the upgrade duration is a concern.

• To enable or disable SSL on a single-user GUI client or delegate client, you must uninstall the single-user client or client delegate server software, and then select the appropriate SSL option during the client or client delegate server re-installation. A client cannot connect to a main server that has a different SSL configuration, and so the main server cannot update the client SSL configuration.

Note — The 5620 SAM installation utility uses Oracle parallel processing to speed a database upgrade only when the 5620 SAM database station has multiple CPUs.





Procedure 1-1 To obtain the system ID of a station for 5620 SAM or 5650 CPAM license acquisition

Perform this procedure to obtain the system ID of a station that is to host a 5620 SAM main server or a 5650 CPAM server. The ASLM requires the system ID to generate a license file.

1 Log in to the station as the root user.

2 Open a console window.

3 Enter the following:

# lshal | grep system.hardware.uuid | tr '[A-Z]' '[a-z]' ↵

The UUID is displayed; for example:

system.hardware.uuid = 'ef5eb0a2-c816-e111-bbda-38aba9872c41' (string)

4 Record the value for use when you request a 5620 SAM or 5650 CPAM license.

Caution — If you are using an Integrated Lights Out Management system, ensure that you obtain the UUID of the intended blade and not the UUID of the ILO module.

Note 1 — You must perform this procedure on each station that requires a license file.

Note 2 — The command line uses the # symbol to represent the root user prompt. Do not type the # symbol when you enter the command.




1.6 5620 SAM management network configuration

The topology of a 5620 SAM management network may be sufficiently complex to benefit from or require the use of hostnames, rather than fixed IP addresses, for communication between 5620 SAM components. Hostname resolution is of even greater benefit when NAT is used between 5620 SAM clients and a main server that communicates over multiple networks.

This section provides a configuration example for hostname resolution in a moderately complex 5620 SAM management network. For simplicity, the example does not include NAT configuration.

To enable hostname resolution in a 5620 SAM management network, you must do the following:

• Configure the local /etc/hosts file on each component to ensure that each hostname is translated to the correct IP address.

• During component installation or upgrade, enable the Use Hostname for Communication parameter.

When two server components use hostnames to communicate, the /etc/hosts file on each component station must contain the following:

• on a main server:• an entry that maps the main server hostname to an IP address of a main server

interface• an entry for each auxiliary server that maps the auxiliary server hostname to the IP

address of the auxiliary server interface that is used for main server communication• an entry for each database that maps the database hostname to the IP address of the

database interface that is used for main server to database communication• on an auxiliary server:

• an entry for each main server that maps the main server hostname to the IP address of the main server interface that is used for auxiliary server communication

• an entry for each auxiliary server that maps the auxiliary server hostname to the IP address of the auxiliary server interface that is used for main server communication

• an entry for each database that maps the database hostname to the IP address of the database interface that is used for database communication

Note 1 — Only local hostname resolution is supported in a 5620 SAM management network. The use of a DNS server for 5620 SAM component hostname resolution is not supported.

Note 2 — When the 5620 SAM clients and auxiliary servers use different main server interfaces to communicate with a main server, the 5620 SAM clients must use a hostname to reach the main server.

Note 1 — Each main server must use the same IP address for the mapping of an auxiliary server hostname to an IP address.

Note 2 — The hostname of a main server may map to different IP addresses on different components to ensure that the appropriate interface on the main server is reached.





Management network configuration exampleThe following example provides guidance about configuring local hostname resolution for 5620 SAM components in a relatively complex management network. In the example, each main server communicates with multiple networks using separate interfaces, as shown in Figure 1-1.

Figure 1-1 Management network topology

The client IP addresses are in the 192.168.1.n network, and the internal management IP addresses are in the 192.168.2.n network.

25451

5620 SAM mainserver “main_a”

5620 SAM database“db_a”

NIC 4

5620 SAM auxiliaryserver “aux_a”

5620 SAM mainserver “main_b”

5620 SAM database“db_b”

NIC 4

5620 SAM auxiliaryserver “aux_b”

NIC 1 NIC 1

NIC 1 NIC 1

NIC 1 NIC 1

NIC 2

NIC 3

Switch/ Router

Switch/ Router

NIC 4

NIC 2

IPv4 Managed Network

NIC 3

Switch/ Router

Switch/ Router

NIC 3

Switch/ Router

Switch/ Router

IPv6 Managed Network

NIC 4 NIC 4

NIC 2

NIC 4

NIC 3

NIC 2

5620 SAM Clients

...2.1

...2.3

...2.5

...2.2

...2.4

...2.6

192.168.4.1 192.168.4.2

2001:0DB8::0001 2001:0DB8::0002

192.168.1.1 192.168.1.2




The component hostnames in the example are the following:

• main servers—main_a and main_b• 5620 SAM databases—db_a and db_b• auxiliary servers—aux_a and aux_b

The same configuration methodology must be applied to all components in the internal management network; for simplicity, the following configuration examples show only the components on one side of the 5620 SAM complex.

The /etc/hosts file on station main_a requires the following entries:

192.168.1.1 main_a

192.168.2.2 main_b

192.168.2.5 aux_a

192.168.2.6 aux_b

192.168.2.3 db_a

192.168.2.4 db_b

127.0.0.1 localhost

The /etc/hosts file on station aux_a requires the following entries:

192.168.2.5 aux_a

192.168.2.6 aux_b

192.168.2.1 main_a

192.168.2.2 main_b

192.168.2.3 db_a

192.168.2.4 db_b

127.0.0.1 localhost

The /etc/hosts file on station db_a requires the following entries:

192.168.2.3 db_a

192.168.2.4 db_b

127.0.0.1 localhost





1.7 Automated client installation, upgrade, and configuration

The following 5620 SAM client software installation methods are available:

• using the client installer utility• using a web browser that connects to a 5620 SAM main server

Each method sets up a basic client environment that includes the 5620 SAM auto-client update utility. The auto-client update utility then downloads the client software from a 5620 SAM main server and installs it.

The 5620 SAM main server must be installed and initialized before you can use a web browser to install the auto-client update utility and client software. You can use the file-based client installer to install the auto-client update utility, regardless of the main server state, but the main server must be fully initialized before the auto-client update utility can install the client software.

See the following chapters for client installation and upgrade information:

• 14—single-user client deployment• 15—client delegate server deployment

The auto-client update utility can also be used for the central management and automatic distribution of client software upgrades and configuration changes.

During startup, the client software checks for available updates on a 5620 SAM main server. If a configuration change is available, the client automatically applies it. If a client software upgrade is available, the client applies the upgrade in response to a user prompt.

Client software upgradesAfter a 5620 SAM main server is upgraded, a GUI client that connects to the server automatically detects the release mismatch and attempts an upgrade to the server release level.

During a software upgrade, a 5620 SAM client downloads and installs only the files required for the upgrade. The upgrade process removes previously downloaded local 5620 SAM files that are not required by the updated client software.

Client configuration changesWhen the GUI clients that connect to a main server require a configuration change, an administrator updates the global client configuration stored on a main server. Each client detects the update at the start of the next client session and applies the required configuration changes. See the “System components configuration procedures” section in the 5620 SAM System Administrator Guide for information about updating client configurations.




By default, the client configuration after an automatic update matches the server configuration, but this behavior is configurable using client startup options. To retain a customized configuration on a client, you can specify that the client does not apply any configuration changes from the server. If a client configuration change is mandatory and affects the customized configuration, you must allow the update and then manually reapply the custom configuration entries. See the “Procedures for opening and closing the GUI” section in the 5620 SAM User Guide for a description of each 5620 SAM client startup option.

Considerations and restrictionsConsider the following before you attempt to use the client auto-update function.

• When a client detects an error during an auto-update attempt, for example, when the client is unable to connect to the server, it displays a message about the error.

• An auto-client update proceeds only when there is sufficient disk space on the client station. Otherwise, the client displays a message and exits.

• When a GUI client tries to connect to a server that is at an earlier 5620 SAM release than the download server, the client displays a message to this effect, restarts, and tries to connect to the other server in the cluster.

• A client backs up the existing configuration files before it performs a configuration change.








2.1 Overview 2-2

2.2 OS configuration restrictions 2-2

2.3 OS configuration requirements 2-2

2.4 RHEL OS package groups and packages 2-6





2.1 Overview

This chapter describes the RHEL OS configuration requirements and restrictions for 5620 SAM and 5650 CPAM deployment. You must comply with the conditions in chapter 1 and the specific requirements in this chapter before you attempt to perform a procedure in this guide on a RHEL station.

2.2 OS configuration restrictions

The following are the RHEL OS configuration restrictions for 5620 SAM and 5650 CPAM system components.

• The 5620 SAM supports the use of RHEL IP bonding only when IP bonding is deployed in an active/backup configuration. See the RHEL documentation for information about configuring IP bonding.

• The 5620 SAM does not support the RHEL SELinux function. You must disable the function after the OS installation and before you install the 5620 SAM.

• The RHEL TFTP server conflicts with the 5620 SAM TFTP server, and must be disabled on a 5620 SAM main or auxiliary server station.

2.3 OS configuration requirements

The following are the RHEL OS configuration requirements for 5620 SAM and 5650 CPAM system components.

• The system locale must be POSIX.• The file system type must be ext4.• You must choose English (English) as the RHEL OS installation language.

Note 1 — See the current 5620 SAM Release Notice for the required RHEL version and patch information.

Note 2 — Alcatel-Lucent recommends that you install any OS, driver, or firmware update that your hardware vendor advises for RHEL.

Note — The use of IP bonding is not supported on a 5620 SAM Cflowd auxiliary server.

Note — Alcatel-Lucent recommends that you create the 5620 SAM disk partitions during the RHEL OS installation. Each partition created after the OS installation requires additional configuration, as described in Procedure 3-1.

Note — Before you deploy a 5620 SAM component on RHEL in a VM, you must also install the latest VMware Tools software. See the VMware documentation for information about VMware Tools.




• You must select the “Create custom layout” disk configuration option, and must then create the file system partitions as specified in chapter 3.

• You must specify the required RHEL packages and package groups listed in section 2.4 during the RHEL OS installation.

• After the OS installation, you must do the following.• Configure each ext4 disk partition with the required options for 5620 SAM software

deployment; see Procedure 2-1.• Reset the reserved block count on each 5620 SAM disk partition; see Procedure 2-2.

• The /etc/hosts entry that maps a main or auxiliary server hostname to an external IP address must be listed above the loopback address entry, and optimally is the first line of the file.

• If OSS clients are to use the registerLogToFile method, you must enable the RHEL FTP, SCP, or SFTP services, as required, and configure each firewall to allow the associated file-transfer traffic between the clients and main servers.

Firewall requirementsAlcatel-Lucent supports the following firewall types in a 5620 SAM deployment:

• external firewall• native RHEL firewall implemented using iptables and ip6tables

Procedure 2-1 To prepare disk partitions for 5620 SAM installation

Perform this procedure to configure each ext4 disk partition on a station after the RHEL OS installation and before you attempt to install a 5620 SAM component on the station.



3 Open the /etc/fstab file using a plain-text editor such as vi. You must modify the entry for each partition that has an ext4 file system. The following is an example ext4 partition entry, which may optionally include the file system UUID:

/dev/device mount_point ext4 defaults 1 2

wheredevice is the name of the device associated with the partitionmount_point is the partition mount point, for example, /opt/5620sam

Caution — Before you install a 5620 SAM system, you must disable the iptables and ip6tables firewall on each RHEL station. Also, if you plan to implement RHEL iptables as part of a 5620 SAM system upgrade, you must ensure that the iptables and ip6tables firewall on each station is disabled before the upgrade.

Note — A RHEL kernel firewall must be configured according to the rules in the 5620 SAM Planning Guide, which describes the use of 5620 SAM templates to create RHEL iptables and ip6tables rules.





4 Perform the following steps for each ext4 partition entry.

i If the “defaults” option is shown, remove the option.

ii For a partition in a physical hardware deployment, insert “barrier=0,noatime”, as shown in the following:

/dev/device mount_point ext4 barrier=0,noatime 1 2

iii For a partition in a VM deployment, insert “noatime”, as shown in the following:

/dev/device mount_point ext4 noatime 1 2

5 Close the console window.

Procedure 2-2 To reset the disk partition reserved block counts

Perform this procedure to ensure that the number of reserved blocks for the root user on each 5620 SAM disk partition is zero.




# mount | grep 5620sam ↵

The 5620 SAM disk partitions are listed; for example:

/dev/sda2 on /opt/5620sam type ext4 (rw,noatime,barrier=0)

/dev/sda3 on /opt/5620sam/dbbackup type ext4 (rw,noatime,barrier=0)

/dev/sdb1 on /opt/5620sam/samdb/archivelog type ext4 (rw,noatime,barrier=0)

Note 1 — Only the partition options shown are supported.

Note 2 — An entry may include the file system UUID, which is optional. Excluding the UUID does not affect 5620 SAM operation.

Note — You must perform this procedure on each station that hosts one of the following 5620 SAM system components:

• main server• auxiliary server• 5620 SAM database

Note — The example lists physical disk partitions, which are named sdan; a logical partition is named vdan.




4 Enter the following once for each 5620 SAM partition:

# tune2fs -m 0 /dev/partition ↵

where partition is the partition name






2.4 RHEL OS package groups and packages

This section lists the RHEL package groups and packages, in addition to a Minimal OS installation, that are required for 5620 SAM deployment. If a required group or package is not installed, a 5620 SAM component deployment fails.

Some packages provide basic functions, for example, man and Telnet, but are not required by the 5620 SAM. These optional packages are listed separately.

The required package groups for each component type are the following:

• Desktop• Desktop Platform• Legacy X Window System Compatibility• X Window System

Package installation methodFor ease of administration, Alcatel-Lucent recommends using the RHEL yum utility to install the required packages. The yum syntax is the following:

yum -y install package_1 package_2 ... package_n

Note 1 — During a RHEL OS installation, you must select the Minimal installation option, and then specify the required package groups and packages listed in this section.

Note 2 — The RHEL rpm utility requires hardware driver files in binary format. If the RHEL driver files provided by your server hardware vendor are in source rpm format, you may need to install additional packages in order to compile the files into binary format. See the server hardware documentation for more information.

Note 1 — To install packages using yum, you require a yum repository. The following repository types are available:

• local repository, which you can create using the RHEL OS installation DVD

• Internet-based repository, which you can access after you register with the Red Hat Network

See the RHEL documentation for information about setting up a yum repository.

Note 2 — If a package has dependencies on one or more additional packages that are not listed in a table, the yum utility installs the additional packages.




Server and database packagesTable 2-1 lists the packages that are required, in addition to the package groups, for a main server, auxiliary server, analytics server, 5620 SAM database, or auxiliary database. To facilitate the installation, copy the command block in Code 2-1 and paste it in a CLI.

Code 2-1: Required package installation command block, server and databaseyum -y install bc.x86_64 binutils.x86_64 compat-libcap1.x86_64yum -y install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64yum -y install dbus-glib-devel.i686 elfutils-libelf-devel.x86_64 elfutils.x86_64yum -y install firefox.x86_64 gcc-c++.x86_64 gcc.x86_64 glibc-devel.i686yum -y install glibc-devel.x86_64 gtk2.i686 hal-devel.i686 irqbalance.x86_64yum -y install ksh.x86_64 libaio-devel.i686 libaio-devel.x86_64 libaio.i686yum -y install libaio.x86_64 libgcc.x86_64 libibverbs.x86_64 libstdc++-devel.x86_64yum -y install libXau.x86_64 libXau.i686 libxcb.x86_64 libxcb.i686 libXtst.i686yum -y install libXtst.x86_64 make.x86_64 numactl-devel.i686 numactl-devel.x86_64yum -y install openmotif.i686 openssh.x86_64 openssh-askpass.x86_64yum -y install openssh-clients.x86_64 openssh-server.x86_64 rsync.x86_64yum -y install sysstat.x86_64 tcpdump.x86_64 unzip.x86_64yum -y install xorg-x11-proto-devel.noarch zip.x86_64

Table 2-1 Required packages, server and database

Package name Description

bc.x86_64 GNU's bc (a numeric processing language) and dc (a calculator)

binutils.x86_64 A GNU collection of binary utilities

compat-libcap1.x86_64 Library for getting and setting POSIX.1e capabilities

compat-libstdc++-33.i686 Compatibility standard C++ libraries

compat-libstdc++-33.x86_64 Compatibility standard C++ libraries

dbus-glib-devel.i686 Libraries and headers for the D-Bus GLib bindings

elfutils-libelf-devel.x86_64 Development support for libelf

elfutils.x86_64 A collection of utilities and DSOs to handle compiled objects

firefox.x86_64 Mozilla Firefox Web browser

gcc-c++.x86_64 C++ support for GCC

gcc.x86_64 Various compilers, for example, C, C++, Objective-C, and Java

glibc-devel.i686 Object files for development using standard C libraries

glibc-devel.x86_64 Object files for development using standard C libraries

gtk2.i686 The GIMP ToolKit (GTK+), a library for creating GUIs for X

hal-devel.i686 Libraries and headers for HAL

irqbalance.x86_64 (1) Daemon that evenly distributes IRQ load across multiple CPUs

ksh.x86_64 The Original ATT Korn Shell

libaio-devel.i686 Development files for Linux-native asynchronous I/O access

libaio-devel.x86_64 Development files for Linux-native asynchronous I/O access

(1 of 2)





Notes(1) New in Release 13.0(2) Required as of Release 13.0 R7; formerly optional

Table 2-2 lists optional packages for a main server, auxiliary server, or database. To facilitate the installation, copy the command block in Code 2-2 and paste it in a CLI.

Code 2-2: Optional package installation command block, server and databaseyum -y install ftp.x86_64 man.x86_64 net-snmp.x86_64 net-snmp-utils.x86_64yum -y install nfs-utils.x86_64 telnet.x86_64 vsftpd.x86_64

libaio.i686 Linux-native asynchronous I/O access library

libaio.x86_64 Linux-native asynchronous I/O access library

libgcc.x86_64 GCC version 4.4 shared support library

libibverbs.x86_64 Core user space library that implements hardware abstracted verbs protocol

libstdc++-devel.x86_64 Header files and libraries for C++ development

libXau.x86_64 (1) X authorization file management libary

libXau.i686 (1) X authorization file management libary

libxcb.x86_64 (1) X protocol C-language binding library

libxcb.i686 (1) X protocol C-language binding library

libXtst.i686 X.Org X11 libXtst runtime library

libXtst.x86_64 X.Org X11 libXtst runtime library

make.x86_64 GNU tool which simplifies the build process for users

numactl-devel.i686 Development package for building Applications that use numa

numactl-devel.x86_64 Development package for building Applications that use numa

openmotif.i686 Open Motif runtime libraries and executables

openssh.x86_64 Open source implementation of SSH protocol versions 1 and 2

openssh-askpass.x86_64 Passphrase dialog for OpenSSH and X

openssh-clients.x86_64 Open-source SSH client application

openssh-server.x86_64 Open source SSH server daemon

rsync.x86_64 A program for synchronizing files over a network

sysstat.x86_64 The sar and iostat system monitoring commands

tcpdump.x86_64 (2) Command-line packet analyzer and network traffic capture; used by Alcatel-Lucent support for debugging

unzip.x86_64 A utility for unpacking zip files

xorg-x11-proto-devel.noarch X.Org X11 Protocol headers

zip.x86_64 A file compression utility


(2 of 2)




Table 2-2 Optional packages, server and database

Client and client delegate server packagesTable 2-3 lists the individual RHEL packages, in addition to the required package groups, that a single-user client requires on a 32-bit OS installation.

To facilitate the installation, copy the command block in Code 2-3 and paste it in a CLI.

Code 2-3: Required package installation command block, 32-bit clientyum -y install compat-libstdc++-33.i686 dbus-glib-devel.i686 firefox.i686 glibc.i686yum -y install hal-devel.i686 libXtst.i686 openmotif.i686yum -y install xorg-x11-proto-devel.noarch

Table 2-3 Required packages, 32-bit single-user client

Table 2-4 lists the individual RHEL packages, in addition to the required package groups, for the following:

• single-user client on 64-bit OS installation• client delegate server

To facilitate the installation, copy the command block in Code 2-4 and paste it in a CLI.


ftp.x86_64 The standard UNIX FTP (File Transfer Protocol) client

man.x86_64 A set of documentation tools: man, apropos and whatis

net-snmp.x86_64 The SNMP Agent Daemon and documentation

net-snmp-utils.x86_64 SNMP clients such as snmpget and snmpwalk

nfs-utils.x86_64 NFS utilities and supporting clients and daemons for the kernel

telnet.x86_64 The client program for the Telnet remote login protocol

vsftpd.x86_64 Very Secure Ftp Daemon




firefox.i686 Mozilla Firefox Web browser

glibc.i686 Object files for development using standard C libraries









Code 2-4: Required package installation command block, 64-bit single-user client and client delegate serveryum -y install compat-libstdc++-33.i686 dbus-glib-devel.i686 firefox.x86_64yum -y install glibc.i686 hal-devel.i686 irqbalance.x86_64 libXtst.i686yum -y install openmotif.i686 xorg-x11-proto-devel.noarch

Table 2-4 Required packages, 64-bit single-user client and client delegate server

Note(1) New in Release 13.0




firefox.x86_64 Mozilla Firefox Web browser

glibc.i686 Object files for development using standard C libraries


irqbalance.x86_64 (1) Daemon that evenly distributes IRQ load across multiple CPUs







3.1 Overview 3-2

3.2 Using RAID with the 5620 SAM 3-3

3.3 Logical disk management 3-4

3.4 Disk partitioning for trial deployments 3-5

3.5 Disk partitioning for live deployments 3-10





3.1 Overview

This chapter describes the disk configuration and partitioning requirements for 5620 SAM components in trial and live deployments.

If the 5620 SAM is to perform large-scale statistics collection, Alcatel-Lucent requires that you implement high-performance disk throughput using one of the following:

• internal disks in a hardware RAID 0 configuration• external disks in a hardware RAID 0 or RAID 1+0 configuration• SAN storage

You can determine the number of disks required for high-performance throughput by submitting a 5620 SAM Platform Sizing Request to Alcatel-Lucent.

See section 3.2 for general information about using RAID with the 5620 SAM, and the 5620 SAM Planning Guide for scaling guidelines related to statistics collection. Contact Alcatel-Lucent technical support for information about using a disk array.

Procedure 3-1 To configure a 5620 SAM disk partition created after the RHEL OS installation

Perform this procedure on each 5620 SAM disk partition that you create after the RHEL OS installation.

1 Log in to the 5620 SAM station as the root user.


3 Mount the partition; see the RHEL OS documentation for information.


# tune2fs -m 0 -o +acl /dev/device ↵

where device is the name of the device associated with the partition

5 Open the /etc/fstab file using a plain-text editor such as vi.

Note 1 — A 5620 SAM disk subsystem requires read and write caching with fault protection.

Note 2 — Alcatel-Lucent recommends that you create the 5620 SAM disk partitions during the RHEL OS installation. A partition created after the OS installation requires additional configuration, as described in Procedure 3-1.

Caution — This procedure requires a restart of the station that hosts the partition. If a 5620 SAM component is installed on the station, perform the procedure only during a scheduled maintenance period.




6 Perform one of the following.

a For a partition in a physical hardware deployment, add the following entry:

/dev/device mount_point ext4 barrier=0,noatime 1 2

b For a partition in a VM deployment, add the following entry:

/dev/device mount_point ext4 noatime 1 2

wheredevice is the name of the device associated with the partitionmount_point is the partition mount point, for example, /opt/5620sam

7 Save and close the /etc/fstab file.

8 Enter the following to reboot the station:

# init 6 ↵

3.2 Using RAID with the 5620 SAM

A RAID implementation for the 5620 SAM requires a hardware RAID controller that can create and manage the required number of volumes.

For optimal performance, a 5620 SAM station requires the recommended number of disks configured in a striping, or RAID 0, volume. A single RAID 0 disk failure can cause a complete file system failure, so for live deployments, Alcatel-Lucent recommends disk mirroring using a RAID 1+0 configuration for greater resiliency and to reduce the recovery time after a disk failure.

Caution — Alcatel-Lucent supports a 5620 SAM deployment that includes RAID only when RAID is implemented as described here and in the 5620 SAM Planning Guide.

You must strictly follow the RAID specifications in the 5620 SAM Planning Guide for the current release before you attempt to install, upgrade, or convert a 5620 SAM system that uses RAID. Contact Alcatel-Lucent technical support for more information.

Note 1 — Alcatel-Lucent does not support the use of software RAID.

Note 2 — Alcatel-Lucent is not responsible for the installation, administration, or recovery of RAID in a 5620 SAM system.





3.3 Logical disk management

Alcatel-Lucent supports logical disk implementation using the LVM function according to the 5620 SAM Planning Guide specifications.

Before you use LVM to resize a partition, you must ensure that the throughput and latency of the new configuration are within the allowed 5620 SAM tolerances. See the “To test 5620 SAM disk performance” procedure in the 5620 SAM System Administrator Guide for information about performing the required check.

Note — Alcatel-Lucent supports LVM only for resizing disk partitions, and not for creating software RAID volumes. See the 5620 SAM Planning Guide for information about the LVM features that are supported in a 5620 SAM deployment.




3.4 Disk partitioning for trial deployments

The disk partitioning schemes in this section are supported only for trial 5620 SAM deployments in a lab environment or for demonstration purposes.

Table 3-1 lists the partitions required for the trial deployment of a collocated 5620 SAM database and main server.

Table 3-1 Trial partitioning scheme, collocated 5620 SAM database and main server

Notes(1) Derived using the formula in section 1.2(2) Required only for Small Cell NE management(3) Based on 15-minute statistics collection interval, 7-day retention period

Caution — Each disk partition described in this section must be a mounted partition and not a symbolic link. The 5620 SAM does not support the use of symbolic links to represent partitions.

Note 1 — See the 5620 SAM Planning Guide or the response to your 5620 SAM Platform Sizing Request for information about the supported disk types.

Note 2 — For each database partitioning scheme, the Oracle management user home directory specified by the ORACLE_HOME environment variable is /opt/5620sam/oracle12r1.

Disks required: two 146-Gbyte or two 300-Gbyte

Partition Content Size (Gbytes)

/ Root, including /usr and /var 25

— Swap Equal to RAM, up to 16

/opt/5620sam 5620 SAM software, operating data 50

/opt/5620sam/dbbackup Database backups 35

/opt/5620sam/nebackup NE configuration backups Network-specific (1)

/opt/5620sam/samdb Database tablespaces 90

/opt/5620sam/samdb/archivelog Database archive logs 35

/opt/5620sam/server/nms/log 5620 SAM server log files 15

/opt/5620sam/server/xml_output Output of OSSI file export operations 10

/smallcell (2) Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC

16 per 1000 NEs without statistics-collection auxiliary server; 1 per 1000 NEs otherwise (3)

At operator discretion Customer data; can be partitioned according to customer requirements

Remainder





Table 3-2 lists the partitions required for the trial deployment of a main server in a distributed 5620 SAM system.

Table 3-2 Trial partitioning scheme, main server, distributed system


Table 3-3 lists the partitions required for the trial deployment of a 5620 SAM database in a distributed 5620 SAM system.

Table 3-3 Trial partitioning scheme, 5620 SAM database, distributed system

Disks required: one 146-Gbyte




/opt/5620sam 5620 SAM server software, operating data 70


/opt/5620sam/server/nms/log 5620 SAM server log files 15

/opt/5620sam/server/xml_output Output of OSSI file export operations 10




Remainder

Disks required: two 146-Gbyte




/opt/5620sam 5620 SAM database software, operating data 40

/opt/5620sam/dbbackup Database backups 40

/opt/5620sam/samdb Database tablespaces 100

/opt/5620sam/samdb/archivelog Database archive logs 40

/opt/5620sam/samdb/redolog Database redo logs 8


Remainder




Table 3-4 lists the partitions required for the trial deployment of an auxiliary server that is to collect statistics.

Table 3-4 Trial partitioning scheme, statistics-collection auxiliary server

Notes(1) Required only if eNodeB statistics are to be collected(2) Required only for Small Cell NE management(3) Based on 15-minute statistics collection interval, 7-day retention period

Table 3-5 lists the partitions required for the trial deployment of an auxiliary server that is to collect call-trace data.

Table 3-5 Trial partitioning scheme, call-trace auxiliary server

Disks required: one 146-Gbyte minimum, two 146-Gbyte recommended Size (Gbytes)

Partition Content One disk Two disks

/ Root, including /usr and /var 25 40


/opt/5620sam 5620 SAM server software, operating data 40 90

/opt/5620sam/auxserver/nms/log 5620 SAM server log files 20 30

/opt/5620sam/auxserver/xml_output Output of OSSI file export operations 10 20

/opt/5620sam/lte (1) Collected eNodeB statistics 20 60


15 per 1000 NEs (3)


Remainder

Disks required: four 146-Gbyte or four 300-Gbyte Size (Gbytes)

Partition Content 146 300

Disks 1 and 2, RAID 0 recommended






Remainder

Disks 3 and above, RAID 0 mandatory

/opt/5620sam/calltrace Call-trace output 80% of disk

/opt/5620sam/debugtrace Call-trace debug output 20% of disk





Table 3-6 lists the partitions required for the trial deployment of a Cflowd auxiliary server.

Table 3-6 Trial partitioning scheme, Cflowd auxiliary server

Table 3-7 lists the partitions required on each auxiliary database station for the trial deployment of an auxiliary database.

Table 3-7 Trial partitioning scheme, auxiliary database

Table 3-8 lists the partitions required for the trial deployment of an analytics server.

Table 3-8 Trial partitioning scheme, analytics server

Disk required: one 146-Gbyte or larger




/opt/5620sam 5620 SAM Cflowd auxiliary server softwareCollected statistics data files

Remainder

Disk required: two 300-Gbyte plus a minimum of six 600-Gbyte


Disks 1 and 2, RAID 1



/opt 5620 SAM auxiliary database software Remainder


/opt/5620sam/auxdb/data Auxiliary database data All









Table 3-9 lists the partitions required for the trial deployment of a single-user client or client delegate server on RHEL.

Table 3-9 Trial partitioning scheme, single-user client or client delegate server

Disk required: one 146-Gbyte or larger Size (Gbytes)

Partition Content 146 >146



/opt/5620sam 5620 SAM client software 5 20


Remainder





3.5 Disk partitioning for live deployments

The disk partitioning schemes in this section are supported for 5620 SAM deployments in a live network environment.

Table 3-10 lists the partitions required for the live deployment of a collocated 5620 SAM database and main server.

Table 3-10 Live partitioning scheme, collocated 5620 SAM database and main server


Caution — Each disk partition described in this section must be a mounted partition and not a symbolic link. The 5620 SAM does not support the use of symbolic links to represent partitions.

Note 1 — See the 5620 SAM Planning Guide or the response to your 5620 SAM Platform Sizing Request for information about the supported disk types.

Note 2 — For each database partitioning scheme, the Oracle management user home directory specified by the ORACLE_HOME environment variable is /opt/5620sam/oracle12r1.


Partition Content 4 × 146 (RAID 0)

4 × 300 (RAID 0)



/opt/5620sam 5620 SAM software, operating data 100 240

/opt/5620sam/dbbackup Database backups 70 120


/opt/5620sam/samdb Database tablespaces 200 360

/opt/5620sam/samdb/archivelog Database archive logs 70 120

/opt/5620sam/server/nms/log 5620 SAM server log files 35 50

/opt/5620sam/server/xml_output Output of OSSI file export operations 10 20




Remainder




Table 3-11 lists the partitions required for the live deployment of a main server in a distributed 5620 SAM system.

Table 3-11 Live partitioning scheme, main server, distributed system


Table 3-12 lists the partitions required for the live deployment of a 5620 SAM database in a distributed 5620 SAM system.

Table 3-12 Live partitioning scheme, 5620 SAM database, distributed system

Disks required: two 146-Gbyte, or four 146-Gbyte or 300-Gbyte Size (Gbytes)


4 × 146 or 300 (RAID 0)





/opt/5620sam/server/nms/log 5620 SAM server log files 50 50

/opt/5620sam/server/xml_output Output of OSSI file export operations 20 20




Remainder



4 × 300 (RAID 0)

6 × 300 or greater (RAID 0)

/ Root, including /usr and /var 40 40 40


/opt/5620sam 5620 SAM software, operating data 120 120 120

/opt/5620sam/dbbackup Database backups 60 120 250

/opt/5620sam/samdb Database tablespaces 180 360 625

/opt/5620sam/samdb/archivelog Database archive logs 60 120 556

/opt/5620sam/samdb/redolog Database redo logs 30 30 30

(1 of 2)





Table 3-13 lists the partitions required for the live deployment of an auxiliary server that is to collect statistics.

Table 3-13 Live partitioning scheme, statistics-collection auxiliary server

Notes(1) Required only if eNodeB statistics are to be collected(2) Required only for Small Cell NE management(3) Based on 15-minute statistics collection interval, 7-day retention period

Table 3-14 lists the partitions required for the live deployment of an auxiliary server that is to collect call-trace data.

Table 3-14 Live partitioning scheme, call-trace auxiliary server


Remainder



4 × 300 (RAID 0)

6 × 300 or greater (RAID 0)

(2 of 2)

Disks required: four 146-Gbyte or four 300-Gbyte, RAID 0




/opt/5620sam 5620 SAM server software, operating data 180

/opt/5620sam/auxserver/nms/log 5620 SAM server log files 50

/opt/5620sam/auxserver/xml_output Output of OSSI file export operations Remainder (150 minimum; 180 minimum if 5620 SAM system includes auxiliary database)

/opt/5620sam/lte (1) Collected eNodeB statistics 100


15 per 1000 NEs (3)



Disks 1 and 2, RAID 0 recommended



(1 of 2)




Table 3-15 lists the partitions required for the live deployment of a Cflowd auxiliary server.

Table 3-15 Live partitioning scheme, Cflowd auxiliary server

Note(1) A larger disk allows for longer data file retention in the event that the IPDR FTP destination is not available.

Table 3-16 lists the partitions required on each auxiliary database station for the live deployment of an auxiliary database.

Table 3-16 Live partitioning scheme, auxiliary database




Remainder


/opt/5620sam/calltrace Call-trace output 80% of disk

/opt/5620sam/debugtrace Call-trace debug output 20% of disk



(2 of 2)

Disk required: two 300-Gbyte in RAID 0 configuration




/opt/5620sam 5620 SAM Cflowd auxiliary server software 50

/opt/5620sam/dcp_data Collected statistics data files Remainder (1)

Disk required: two 300-Gbyte, plus a minimum of twelve 600-Gbyte


Disks 1 and 2, RAID 1



/opt 5620 SAM auxiliary database software Remainder

Disks 3 and above, RAID 1+0

/opt/5620sam/auxdb/data Auxiliary database data All





Table 3-17 lists the partitions required for the live deployment of an analytics server.

Table 3-17 Live partitioning scheme, analytics server

Table 3-18 lists the partitions required for the live deployment of a single-user client or client delegate server on RHEL.

Table 3-18 Live partitioning scheme, single-user client or client delegate server






Disk required: one 146-Gbyte or larger Size (Gbytes)

Partition Content 146 >146



/opt/5620sam 5620 SAM client software 5 20


Remainder




4.1 Overview 4-2

4.2 Workflow to configure SSL 4-5

4.3 SSL security configuration 4-6





4.1 Overview

Secure Sockets Layer, or SSL, is a security mechanism for data encryption, client authentication, and message integrity. You can configure SSL for secure communication between 5620 SAM main servers and other 5620 SAM components.

SSL secures the EJB, JMS, and HTTP interfaces of 5620 SAM single-user GUI clients and client delegate servers, and the JMS and HTTP interfaces of OSS clients. When SSL is enabled on a 5620 SAM GUI or OSS client, the client uses HTTPS instead of HTTP. Figure 4-1 shows the SSL channels of 5620 SAM components.

Figure 4-1 5620 SAM communication channels and security

SSL requires a security certificate that is shared among members of a network domain. A certificate from a certification authority, or CA, is used for live 5620 SAM deployments, but you can locally generate a self-signed certificate for internal lab use.

Note 1 — You cannot selectively enable SSL on the components of a 5620 SAM system. If you enable SSL on a main server, you must enable SSL on all other servers and clients in the 5620 SAM system.

Note 2 — The 5620 SAM LI function requires SSL.

Caution — Alcatel-Lucent strongly recommends that you do not use a self-signed SSL security certificate in a live 5620 SAM deployment.

OSS application

JMS/SSL HTTPSHTTPUser ID/password

5620 SAMclient GUI

User ID/password

SNMPv3 USM/VACMSNMPv1, v2 community string

SSH1/2 or TelnetUser ID/password

FTP/SCP User ID/password

FirewallFirewall

JMS/SSL

EJB/SSL

User ID/password

User ID/passwordSSL

Databasesession

authentication

User authorization andauthentication

requests

RADIUS, TACACS+,SAM-L, or CSA

Databasesif redundant

Managednetwork

18083

5620 SAMserver

Localsecurity

data

5620 SAM serverif redundant




An SSL truststore file contains SSL security certificates from trusted entities. An SSL security certificate must be imported to a truststore file on the following:

• each main server station• each OSS client station• each Cflowd auxiliary server station

A main server distributes the truststore file to each GUI client and client delegate server. A keystore file is manually copied to each auxiliary server station.

You use the 5620 SAM installation utility to enable SSL by specifying the keystore and truststore files. If SSL is configured and enabled on a 5620 SAM system, the SSL configuration persists through subsequent upgrades.

A 5620 SAM server acts as an SSL client of another 5620 SAM server. For example, in a redundant system, the standby main server is a client of the primary main server.

GUI client and main server communicationIf a non-SSL single-user GUI client or delegate client connects to a main server on which SSL is enabled, SSL is automatically enabled on the client or delegate client; no additional user action is required.

To disable SSL on a single-user GUI client or delegate client, you must either reconfigure the client software using the client configuration utility, or uninstall and reinstall the client software, specifying that SSL is disabled during the reinstallation. See Procedures 4-4 and 4-5 for information.

When SSL is enabled, the GUI status bar displays a padlock icon in the bottom left corner, as shown in Figure 4-2. The icon is also displayed on the following:

• client GUI login form• information form opened using Help→About 5620 SAM / 5650 CPAM

Figure 4-2 SSL security icon

Note — The 5620 SAM does not support the use of multiple private encryption keys. A 5620 SAM main or auxiliary server uses only the first encryption key in a keystore, and ignores additional keys.

Note 1 — When SSO is enabled, each main server keystore must contain the SSL certificate of the remote server.

Note 2 — You must use the Java Key Store, or JKS, keystore format in a 5620 SAM system. If you have a keystore in a different format, for example, PKCS12, you can use the Java keytool utility to convert the keystore to JKS format.





Managing SSL certificate expiryWhen SSL is configured on a main or auxiliary server, the server checks the expiry date of the SSL certificate in the local keystore during server initialization and once every 24 hours thereafter. If the certificate is to expire within a predefined period, the 5620 SAM raises a warning alarm. If the certificate is expired, the 5620 SAM clears the warning alarm and raises a critical alarm.

The default warning period is 30 days from the current date. To change the warning period, contact Alcatel-Lucent technical support.

The 5620 SAM updates the Last Time Detected value of an expiry warning alarm daily, and raises a new critical alarm daily when a certificate is expired. When you replace an expiring or expired certificate with a new and valid certificate, the associated expiry alarms clear. Each type of alarm persists through events such as server switchovers.

The alarm information includes the certificate ID, and the expiry date and time.

If a keystore contains hierarchical certificates, the 5620 SAM checks the expiry date of each certificate in the hierarchy, starting with the lowest, and uses the earliest expiry date found as the reference point for raising an alarm.

SSL certificate renewal

The SSL certificate renewal process is the same as the initial configuration process. After you obtain the new keystore and truststore files, you can use the workflow in section 4.2 to update the SSL configuration on the 5620 SAM system components.

Note — The Days Remaining value in an expiry alarm is based on the number of complete 24-hour periods until the certificate expiry time. If fewer than 24 hours remain until the expiry, the Days Remaining value is zero, but the 5620 SAM does not raise an alarm about the expired certificate until the actual expiry time.




4.2 Workflow to configure SSL

The following is the sequence of high-level actions that are required to configure SSL in a 5620 SAM system.

1 Preconfigure the 5620 SAM system. See Procedure 4-1.

2 To enable SSL for an existing 5620 SAM system that is not being upgraded, go to step 4.

3 If you are performing a 5620 SAM system installation or upgrade, enable SSL and specify the keystore and truststore files for each component, as required, and then go to step 10.

4 If the 5620 SAM system is redundant, enable SSL on the standby main server. See Procedure 4-2.

5 Enable SSL on each reserved auxiliary server. See Procedure 4-3.

6 If the 5620 SAM system is redundant, open a 5620 SAM GUI client to monitor the network during the required server activity switch.

7 If the 5620 SAM system is redundant, enable SSL on the primary main server. See Procedure 4-2.

8 If the 5620 SAM system is standalone, enable SSL on the standalone main server. See Procedure 4-2.

9 Enable SSL on each preferred auxiliary server. See Procedure 4-3.

10 Enable SSL and HTTPS on each OSS client. See Procedure 4-6.

11 Enable SSL and HTTPS on each Cflowd auxiliary server. See Procedure 4-7.

12 If required, disable SSL on a single-user GUI client or client delegate server. See Procedures 4-4 and 4-5.

Caution 1 — Configuring SSL in an existing standalone 5620 SAM system requires a shutdown of the main server, which causes a network management outage. Configure SSL in a 5620 SAM system only during a scheduled maintenance period.

Caution 2 — Configuring SSL in an existing redundant 5620 SAM system requires a server activity switch, which causes a temporary network management outage. Configure SSL in a 5620 SAM system only during a scheduled maintenance period.

Note — You can use the workflow to perform the initial SSL configuration, or to renew an expired SSL certificate.





4.3 SSL security configuration

The following procedures describe how to configure SSL in a 5620 SAM system.

Procedure 4-1 To prepare a 5620 SAM system for SSL

Perform this procedure to preconfigure the 5620 SAM for SSL communication.

1 If you have an SSL certificate that you want to use, for example, a new certificate that replaces an expired certificate, go to step 3.

2 If you have a set of SSL keystore and truststore files, go to step 10.

3 Use the Java keytool utility to generate a keystore file. For information about the keytool utility, visit the Oracle website.

# keytool -genkey -alias alias -keyalg RSA -keypass password -storepass password -keystore keystore_file -storetype JKS -validity days -dname “CN=common_name, OU=org_unit, O=org_name, L=locality, S=state, C=country” ↵

wherealias is a case-insensitive alias that is required for subsequent keytool operationspassword is the password for the key and keystorekeystore_file is the name of the generated keystore filedays is the number of days before the SSL key expires; the default is 90and where the following comprise the X.500 distinguished name:common_name is the server hostname or IP addressorg_unit is a department or division nameorg_name is a company namelocality is a city namestate is a state or region namecountry is a country code, for example, US

Caution — Alcatel-Lucent strongly recommends that the person who performs the procedures in this chapter has SSL security experience. Contact Alcatel-Lucent technical support if you require assistance with SSL configuration.

Note 1 — You must use the Java Key Store, or JKS, keystore format. If your keystore has a different format, for example, PKCS12, you can use the Java keytool utility to convert the keystore to JKS format.

Note 2 — Ensure that the keystore that you use contains only one private encryption key. A 5620 SAM main or auxiliary server uses only the first encryption key in a keystore, and ignores additional keys.

Note 1 — The keytool utility that you use must be from the same Java version as the Java version that the 5620 SAM uses. See the 5620 SAM Planning Guide for Java version information.

Note 2 — The passwords that you specify in this step must be identical.




4 Record the key and keystore password.

5 If you do not require an SSL certificate that is signed by a CA, for example, in a 5620 SAM lab deployment, perform the following steps.

i Enter the following to export the certificate to a certificate file:

# keytool -export -alias alias -keystore keystore_file -storepass password -file certificate_file ↵

wherealias is the alias specified during keystore generationkeystore_file is the source keystore file, for example, /opt/samserver.keystorepassword is the keystore passwordcertificate_file is the name of the generated certificate file

ii Go to step 8.

6 Perform the following steps to generate a certificate signing request, or CSR.

i Enter the following:

# keytool -certreq -alias alias -keystore keystore_file -file CSR_file -storetype JKS

wherealias is a case-insensitive alias that is required for subsequent keytool operationskeystore_file is the keystore file generated in step 3CSR_file is the name of the generated CSR file

The following prompt is displayed:

Enter keystore password:

ii Enter the keystore password. The following prompt is displayed:

Enter key password for <alias>

iii Enter the key password. The utility generates the CSR file.

7 Send the CSR file to a CA for authentication. The CA returns a certificate file that contains a trusted root certificate in a hierarchical certificate chain.

8 Enter the following to import the certificate to a truststore file:

# keytool -import -trustcacerts -alias alias -file certificate_file -keystore truststore_file -storepass password

wherealias is the keystore aliascertificate_file is the self-signed or CA certificate filetruststore_file is the truststore file to which you want to import the certificatepassword is the truststore password

Note — If the certificate is signed by a CA, you must import the entire CA chain of certificates to the truststore file. See the CA documentation for information about importing trusted certificates.





9 If the security certificate is signed by a CA, enter the following to import the certificate from the certificate file to a keystore file:

# keytool -import -trustcacerts -alias alias -file certificate_file -keystore keystore_file -storepass password

wherealias is the keystore aliascertificate_file is the CA certificate filekeystore_file is the keystore file to which you want to import the certificatepassword is the truststore password

10 Copy the keystore and truststore files to each main server in the 5620 SAM system.

11 Copy the keystore file to each auxiliary server station in the 5620 SAM system.

Note — You must import the entire CA chain of certificates into the keystore file. See the CA documentation for information about importing trusted certificates.

Note — The keystore file must be in the same location on each main server station, for example, /opt.

Note — The keystore file location on each auxiliary server station must match the keystore file location on each main server station, for example, /opt.




Procedure 4-2 To enable SSL on a main server

Perform this procedure to enable SSL encryption on a 5620 SAM main server for communication with other 5620 SAM components.

1 Stop the 5620 SAM main server application.

i Log in to the main server station as the samadmin user.

ii Open a console window.

iii Enter the following:

bash$ cd /opt/5620sam/server/nms/bin ↵

iv Enter the following to stop the 5620 SAM main server software:

bash$ ./nmsserver.bash stop ↵

v Enter the following to display the 5620 SAM main server status:

bash$ ./nmsserver.bash appserver_status ↵

The command displays a status message.

vi The 5620 SAM main server is stopped when the command displays the following status message:

Application Server is stopped

If the command displays a different message, wait 5m and repeat step 1 v. Do not proceed to the next step until the server is stopped.

2 Enter the following to switch to the root user:

bash$ su - ↵

3 Navigate to the directory that contains the new 5620 SAM installation software.


# cd Linux ↵

Caution — Configuring SSL on a 5620 SAM main server requires a shutdown of the server software and causes a network-management outage. Ensure that you perform this procedure only during a scheduled maintenance period.

Note — You must perform this procedure on each main server In a redundant 5620 SAM deployment. See section 4.2 for information about the order in which the main servers must be configured.






# ./ServerInstall_RHEL_R_r_revision.bin ↵

whereR_r is the release identifier, in the form MAJOR_minor

revision is the revision identifier, such as R1, R3, or another descriptor

The 5620 SAM server configuration utility opens, and displays the Introduction panel.

6 Click on the Next button.

7 Accept the terms of the license agreement in the “Software License Agreement” panel.


9 Choose Main Server Configuration in the “Choose Installation Type” panel.


11 Click on the Next button in each subsequent panel until the “SSL Configuration” panel is displayed.

12 Select the “Enable Secure Communication” parameter.

13 Configure the remaining parameters:

• Keystore File• Keystore Password• Truststore File• Truststore Password


15 Click on the Next button in each subsequent panel until the “Installation Complete” panel is displayed.

16 Select the “Start the 5620 SAM Main Server” parameter.

17 Click on the Done button to close the server configuration utility.

18 Enter the following to switch back to the samadmin user:

# exit ↵





Procedure 4-3 To enable SSL on an auxiliary server

Perform this procedure to enable SSL encryption on a 5620 SAM auxiliary server for communication with other 5620 SAM components.

1 Stop the 5620 SAM auxiliary server application.

i Log in to the auxiliary server station as the samadmin user.


iii Enter the following to change to the server binary directory:

bash$ cd /opt/5620sam/auxserver/nms/bin ↵

iv Enter the following to stop the 5620 SAM auxiliary server software:

bash$ ./auxnmsserver.bash auxstop ↵

v Enter the following to display the 5620 SAM auxiliary server status:

bash$ ./auxnmsserver.bash auxappserver_status ↵


vi The auxiliary server is stopped when the command displays the following status message:


If the command displays a different message, wait 5m and repeat step 1 v. Do not proceed to the next step until the server is stopped.

2 Enter the following to switch to the root user:

bash$ su - ↵



# cd Linux ↵


# ./ServerInstall_RHEL_R_r_revision.bin ↵



The 5620 SAM server configuration utility opens, and displays the Introduction panel.








9 Choose Auxiliary Server Configuration in the “Choose Installation Type” panel.


11 Click on the Next button in each subsequent panel until the “SSL Configuration” panel is displayed.

12 Select the “Enable Secure Communication” parameter.

13 Configure the remaining parameters:

• Keystore File• Keystore Password


15 Click on the Next button in each subsequent panel until the “Installation Complete” panel is displayed.

16 Select the “Start the 5620 SAM Auxiliary Server” parameter.

17 Click on the Done button to close the server configuration utility.

18 Enter the following to switch back to the samadmin user:

# exit ↵





Procedure 4-4 To disable SSL on a RHEL single-user client or client delegate server

Perform this procedure when SSL is no longer enabled on a main server and you need to disable SSL on a 5620 SAM single-user client or client delegate server on RHEL.

1 Close each affected client GUI session by choosing Application→Exit from the 5620 SAM main menu. A dialog box appears.

2 Click on the Yes button. The client GUI closes.


a Reinstall the client software. Perform the following steps.

i Uninstall the single-user client or client delegate server software by performing the appropriate procedure in chapter 14 or 15.

ii Install the single-user client or client delegate server software by performing the appropriate procedure in chapter 14 or 15.

iii Go to step 18.

b Reconfigure the client software as described in the following steps.




# cd Linux ↵


# ./ClientInstall_RHEL_R_r_revision.bin ↵



The 5620 SAM client configuration utility opens, and displays the Introduction panel.




Note — An affected client GUI session is one of the following:

• a single-user client session on the station• a delegate client session on the station





11 Perform one of the following in the “Choose Installation Type” panel.

a Choose Client Installation and Configuration, if you are configuring a single-user client.

b Choose Client Delegate Installation and Configuration, if you are configuring a client delegate server.


13 Click on the Next button in each subsequent panel until the “Main Server Configuration” panel is displayed.

14 Deselect the “Enable Secure Communication” parameter.

15 Click on the Install button. The installation begins. When the installation is complete, the “Installation Complete” panel is displayed.

16 Select the “Start the 5620 SAM Client” parameter.

17 Click on the Done button to close the client configuration utility.

18 The 5620 SAM client GUI opens and connects to the main server. Subsequent client-server communication does not use SSL.

Log in to the client GUI to verify that the client and main server can communicate.




Procedure 4-5 To disable SSL on a Windows single-user client or client delegate server

Perform this procedure when SSL is no longer enabled on a main server and you need to disable SSL on a 5620 SAM single-user client or client delegate server on Windows.

1 Close each affected client GUI session by choosing Application→Exit from the 5620 SAM main menu. A dialog box appears.

2 Click on the Yes button. The client GUI closes.


a Reinstall the client software. Perform the following steps.

i Uninstall the single-user client or client delegate server software by performing the appropriate procedure in chapter 14 or 15.

ii Install the single-user client or client delegate server software by performing the appropriate procedure in chapter 14 or 15.

iii Go to step 16.

b Reconfigure the client software as described in the following steps.


5 Double-click on the ClientInstall_SAM__R_r_revision.exe file



The 5620 SAM client configuration utility opens with the Introduction panel displayed.




9 Perform one of the following in the “Choose Installation Type” panel.

a Choose Client Installation and Configuration, if you are configuring a single-user client.

b Choose Client Delegate Installation and Configuration, if you are configuring a client delegate server.


Note — An affected client GUI session is one of the following:

• a single-user client session on the station• a delegate client session on the station





11 Click on the Next button in each subsequent panel until the “Main Server Configuration” panel is displayed.

12 Deselect the “Enable Secure Communication” parameter.

13 Click on the Install button. The reconfiguration begins. When the installation is complete, the “Installation Complete” panel is displayed.

14 Select the “Start the 5620 SAM Client” parameter.

15 Click on the Done button to close the 5620 SAM client configuration utility.

16 The 5620 SAM client GUI opens and connects to the main server. Subsequent client-server communication does not use SSL.

Log in to the client GUI to verify that the client and main server can communicate.




Procedure 4-6 To enable SSL and HTTPS for an OSS client

Perform this procedure to enable SSL and HTTPS on an OSS client station for secure communication with a 5620 SAM main server.

1 Ensure that SSL is enabled on each main server in the 5620 SAM system.

2 Ensure that the trusted root certificates from the main server station are copied to the OSS client station, as described in Procedure 4-1.

3 Use an SSL utility to import the SSL certificate from the certificate file to an SSL truststore file on the OSS client station. See the utility documentation for information about importing an SSL certificate to a truststore.

4 Perform the following steps to modify the URL that each OSS application on the station uses to reach the main server.

i Change http: to https:.

ii Change the port value in the URL from 8080 to 8443.





Procedure 4-7 To enable SSL and HTTPS on a Cflowd auxiliary server

Perform this procedure to enable SSL and HTTPS on a Cflowd auxiliary server station for secure communication with one or more 5620 SAM main servers and web UI clients.

1 Ensure that SSL is enabled on each main server in the 5620 SAM system.

2 Copy the trusted root certificate file from the main server station to the Cflowd auxiliary server station.

3 Use an SSL utility to import the SSL certificate from the certificate file to an SSL truststore file on the Cflowd auxiliary server station. See the utility documentation for information about importing an SSL certificate to a truststore.

4 Log on to the Cflowd auxiliary server station as the root user.



# cd /opt/5620sam/dcp-R_rRn/bin

where R_rRn is the software release identifier

7 Enable SSL for communication with the 5620 SAM.

i Create a backup copy of the dcpctl.sh file and store it in a secure location.

ii Open the dcpctl.sh file using a plain-text editor such as vi.

iii Locate the section that begins with the following line:

# SSL configuration

iv Locate the following line in the section:

# J_OPTS_SSL="-Djavax.net.ssl.trustStore=<absolute path of the trust store file>"

v Remove the leading # symbol.

vi Replace <absolute path of the trust store file> with the absolute path of the truststore file.

vii Save and close the dcpctl.sh file.

8 Enable SSL for communication with web UI clients.


# cd /opt/5620sam/jboss-6.4.0/standalone/configuration

ii Create a backup copy of the standalone-5620dcp.xml file and store it in a secure location.

iii Open the standalone-5620dcp.xml file using a plain-text editor such as vi.

iv Locate the following section:






<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>

v Move the “-->” to a new line at the section end so that the section reads as follows:



vi Locate the following section:



vii Replace absolute_path_of_the_cert_key_file with the absolute path and name of the truststore file.

viii Replace the word password inside the quotation marks with the truststore password.

ix Move the “-->” line from the end of the section to a new line after the first line; the section now reads as follows:



<connector name="https" scheme="https" protocol="HTTP/1.1" socket-binding="https" enable-lookups="false" secure="true">

<ssl name="https" password="password" protocol="TLSv1,TLSv1.1,TLSv1.2" certificate-key-file="keystore_file"/>

</connector>

wherepassword is the keystore passwordkeystore_file is the absolute file path and name of the SSL truststore file

x Save and close the standalone-5620dcp.xml file.






# cd /opt/5620sam/dcp-R_rRn/bin


10 Restart the Cflowd auxiliary server.


# ./dcpctl.sh stop ↵

The server stops, and the following messages are displayed:

Stopping 5620 SAM DCP server...

5620 SAM DCP server is stopped successfully

ii Enter the following:

# ./dcpctl.sh start ↵

The server starts, and displays messages like the following:

Starting 5620 SAM DCP server...date time org.xnio.Xnio <clinit>

INFO: XNIO Version n.n.n.GA-redhat-n

date time org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version n.n.n.GA-redhat-n

date time org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version n.n.n.Final-redhat-n

5620 SAM DCP server is started successfully

11 Configure the Cflowd auxiliary server to use HTTPS and SFTP for communication with the main servers, as described in Procedure 6-6.




5.1 Overview 5-2

5.2 Migration from SCMS 5-2

5.3 HDM installation and configuration 5-2

5.4 Small Cell management configuration 5-3





5.1 Overview

You must perform the procedure in section 5.4 to enable 5620 SAM management of the following classes of Small Cell NEs:

• Small Cell access point—all 3G and 4G variants• Small Cell Gateway—all multi-standard variants

See the “Solution support information” section of the 5620 SAM Small Cells User Guide for specific device-support information.

You can choose to perform the configuration at the following times:

• after a 5620 SAM installation or upgrade, before the standalone or primary main server and the auxiliary servers start

• when the 5620 SAM system is fully initialized after an installation or upgrade

5.2 Migration from SCMS

If you plan to migrate from SCMS to 5620 SAM Small Cell management, you must first perform Procedure 5-1 to configure the 5620 SAM for Small Cell management; the SCMS and 5620 SAM must share an HDM instance during the migration. See the 5620 SAM SCMS Migration Guide for information about migrating from SCMS to 5620 SAM Small Cell management.

5.3 HDM installation and configuration

HDM installation and configuration operations are independent of 5620 SAM installation and upgrade activity. After a 5620 SAM system upgrade, however, you must apply the HDM Adaptation Kit from the new 5620 SAM software package to the HDM.

See the 5620 SAM Release Notice for information about obtaining the HDM Adaptation Kit for the release, and follow the associated installation or upgrade instructions, as required.

See the 5620 SAM Release Notice for information about HDM post-installation configuration requirements.

See the HDM documentation for HDM installation and configuration information.

Note — Before you attempt to configure Small Cell management, you must ensure that the ACL flag is enabled on the /smallcell partition, as described in Procedure 3-1.




5.4 Small Cell management configuration

Use the following procedure to enable and configure the 5620 SAM management of Small Cell NEs.

Procedure 5-1 To enable Small Cell management

1 Log on to the main or auxiliary server as the root user.



a On a main server, enter the following:

# cd /opt/5620sam/server/nms/config/femto/fsconf ↵

b On an auxiliary server, enter the following:

# cd /opt/5620sam/auxserver/nms/config/femto/fsconf ↵

4 If this is the first time that Small Cell management is being configured on the station, go to step 6.


a If you are upgrading the server, perform the following steps.


# ./fsconf.sh upgrade ↵

The script displays messages like the following, and then exits:

[ timestamp ]:SAM File Server Upgrading(sam-fileserver-1.2-linux64)

Caution — This procedure potentially involves a restart of each main server and auxiliary server in a 5620 SAM system, which is service-affecting. Ensure that you perform this procedure only during a scheduled maintenance period.

Note 1 — You must perform this procedure on each main and auxiliary server in the 5620 SAM system. In a redundant 5620 SAM system, you must perform this procedure on the standby main server station first.

Note 2 — Command lines use the following as the CLI prompts:

• #—root user prompt• $—fgwuser and ftpuser prompts• bash$—samadmin user prompt

Do not type the leading # symbol, $ symbol, or bash$ when you enter a command.





[ timestamp ]:updating nms-femto.xml file

ii Go to step 52.

b If you are replacing a previous Small Cell configuration, for example, after a server uninstallation and re-installation, perform the following steps.


# ./fsconf.sh uninstall ↵

The script displays configuration messages and the following prompt:

Are you sure to uninstall SAM File Server(sam-fileserver-1.1-linux64)[yes/no]?

ii Enter yes ↵. The script removes the Small Cell configuration and exits.

Configure SFTP parameters


# ./fsconf.sh install ↵

The script displays configuration messages, and then the following prompt:

Install Complete SAM File Server(sam-fileserver-1.1-linux64)(Main+Aux)[yes/no]?


a If the 5620 SAM system does not include an auxiliary server, enter the following to install all management components on the main server station:

yes ↵

b If the 5620 SAM system includes one or more auxiliary servers, perform the following steps.

i Enter the following to install only one management component on the station that you are configuring:

no ↵


Choose SAM File Server type [1 Main/ 2 Aux]?

ii Enter one of the following, depending on the type of server that you are configuring:

• main server:

1 ↵

• auxiliary server:

2 ↵





Enter oamNeIpAddress(This is the IP over which SAM receives FGW traps):

8 Enter the address of the server interface that connects to the FGW. You can specify an IPv4 address, an IPv6 address, or an FQDN.


Enter fileServerHostNameForFemto(This is the FQDN/IP over which Femto interacts with SAM FileServer):

9 Enter the address of the server interface that connects to the FGW. You can specify an IPv4 address, an IPv6 address, or an FQDN.


Do you have a dedicated interface for smallcell access?[yes/no]


a Enter no ↵ if the main or auxiliary server has no dedicated interface for Small Cell management.

b Enter yes ↵ if the main or auxiliary server has more than one physical network management interface, and one of the interfaces is dedicated to Small Cell NE management.

The script displays configuration messages and then exits.

The script creates the /smallcell directory and subdirectories, and the following user accounts and groups:

• fgwuser• ftpuser

11 If you answer yes in step 10, perform the following steps to configure an SSH instance for the dedicated interface.


# ./femtoInterfaceHardening.sh

The script displays the following prompt:

Note 1 — Alcatel-Lucent recommends that you specify an FQDN.

Note 2 — If you specify an IPv6 address, you must enclose the address in brackets, for example:

[2001:0DB8:0EA6:11D0::74AC]

Note 1 — Alcatel-Lucent recommends that you specify an FQDN.

Note 2 — If you specify an IPv6 address, you must enclose the address in brackets, for example:

[2001:0DB8:0EA6:11D0::74AC]





Do you want to configure security hardening feature on this server?[yes/no]

ii Enter yes ↵.


Enter the IP over which Femto interacts with SAM:

iii Enter the IPv4 address of the dedicated 5620 SAM management interface.

The script displays configuration messages and then exits.

Configure SSH for Small Cell file transfers by ftpuser user

12 Enter the following to switch to the ftpuser user:

# su - ftpuser ↵


$ cd .ssh ↵

14 Copy the public encryption key from the Small Cell NE /etc/sftpkeys/id_dsa.pub file.


a If you enter yes in step 10 to specify a dedicated 5620 SAM management interface, perform the following steps.

i Using a plain-text editor such as vi, create a file named alt_authorized_keys and paste in the encryption key copied in step 14.

Note — If the Small Cell NEs use IPv4 and IPv6 to communicate over the dedicated interface, the script configures the IPv6 SSH instance automatically.

Note — Ensure that you remove the line breaks from the pasted text.




ii Save and close the alt_authorized_keys file.


$ chmod 755 alt_authorized_keys ↵

b If you enter no in step 10 to specify the default 5620 SAM management interface, perform the following steps.

i Using a plain-text editor such as vi, create a file named authorized_keys and paste in the encryption key copied in step 14.

ii Save and close the authorized_keys file.


$ chmod 755 authorized_keys ↵


$ cd .. ↵


$ chmod 755 .ssh ↵

18 Enter the following to switch back to the root user:

$ exit ↵

Enable bulk file transfers for ftpuser user

19 Create a backup copy of the /etc/security/limits.conf file.

20 Open the /etc/security/limits.conf file using a plain-text editor such as vi.

21 Add the following lines to the end of the file:

ftpuser soft nofile 4096

ftpuser soft nproc 5000

22 Save and close the /etc/security/limits.conf file.


# su - ftpuser ↵






24 Verify the configuration update.


$ ulimit -a ↵

ii Ensure that the output includes the following lines:

open files (-n) 4096

max user processes (-u) 5000


$ exit ↵

Generate SSH key for samadmin user

26 Enter the following to switch to the samadmin user:

# su - samadmin ↵

27 Enter the following to run the SSH key-generation utility:

bash$ ssh-keygen -t rsa ↵

The script displays the following prompt on a main server:

Enter file in which to save the key (/opt/5620sam/server/.ssh/id_rsa):

The script displays the following prompt on an auxiliary server:

Enter file in which to save the key (/opt/5620sam/auxserver/.ssh/id_rsa):

28 Press ↵ to accept the default value.


Enter passphrase (empty for no passphrase):

29 Enter a passphrase.


Enter same passphrase again:

The utility displays the key fingerprint and randomart image, and then exits.




Propagate SSH key of samadmin user to FGW admin user

30 Copy the SSH public key, which is in one of the following files, to the /home/admin/.ssh/authorized_keys file on the FGW:

• on a main server:/opt/5620sam/server/.ssh/id_rsa.pub

• on an auxiliary server:/opt/5620sam/auxserver/.ssh/id_rsa.pub

Propagate SSH key of FGW admin user to samadmin user

31 Copy the SSH public key from the FGW /home/admin/.ssh/id_rsa.pub file.


bash$ cd .ssh ↵


a If you enter yes in step 10 to specify a dedicated 5620 SAM management interface, and the FGW is to use the interface, perform the following steps.

i Using a plain-text editor such as vi, create a file named alt_authorized_keys and paste in the copied encryption key.



bash$ chmod 755 alt_authorized_keys ↵


i Using a plain-text editor such as vi, create a file named authorized_keys and paste in the copied encryption key.



bash$ chmod 755 authorized_keys ↵








bash$ cd .. ↵


bash$ chmod 755 .ssh ↵


bash$ exit ↵

Propagate SSH keys for FGW file transfers by fgwuser user

37 If you are configuring an auxiliary server, go to step 52.

38 Enter the following to switch to the fgwuser user:

# su - fgwuser ↵


$ cd .ssh ↵

40 Copy the SSH public key from the FGW /root/.ssh/id_rsa.pub file.



i Using a plain-text editor such as vi, create a file named alt_authorized_keys and paste in the copied encryption key.





i Using a plain-text editor such as vi, create a file named authorized_keys and paste in the copied encryption key.










$ cd .. ↵




$ exit ↵

Propagate SSH keys for FGW file transfers by ftpuser user


# su - ftpuser ↵


$ cd .ssh ↵

47 Copy the SSH public key from the FGW /root/.ssh/id_rsa.pub file.



i Using a plain-text editor such as vi, open the alt_authorized_keys file and paste the copied encryption key on a new line.





i Using a plain-text editor such as vi, open the authorized_keys file and paste the copied encryption key on a new line.











$ cd .. ↵




$ exit ↵

Complete deployment procedure, if required

52 If you are performing this procedure as part of a 5620 SAM system installation, upgrade, or conversion to redundancy procedure in chapter 6, 7, or 8, perform the following steps.

i Return to the installation, upgrade, or conversion procedure and complete the procedure steps.

ii Perform step 55 when the 5620 SAM system is fully initialized.

Restart main or auxiliary server


# su - samadmin ↵


a On a main server, enter the following to restart the main server software:

bash$ /opt/5620sam/server/nms/bin/nmsserver.bash force_restart ↵

b On an auxiliary server, enter the following to restart the auxiliary server software:

bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxforce_restart ↵

The server restarts.




Add dedicated management interface to 5620 SAM system

55 If you enter yes in step 10 to specify a dedicated 5620 SAM management interface, use a 5620 SAM client GUI to perform the following procedures in the 5620 SAM User Guide, as required:

• “To configure an additional management interface on a main server”• “To configure an additional management interface on an auxiliary server”







5620 SAM system deployment

6 — 5620 SAM installation

7 — 5620 SAM upgrade

8 — 5620 SAM conversion to redundancy

9 — 5620 SAM conversion to IPv6

10 — 5620 SAM uninstallation







6.1 Overview 6-2

6.2 5620 SAM installation procedures list 6-2

6.3 Standalone system installation workflow 6-4

6.4 Standalone system installation 6-5

6.5 Redundant system installation workflow 6-43

6.6 Redundant system installation 6-44

6.7 Auxiliary server installation 6-135

6.8 Cflowd auxiliary server installation 6-156

6.9 Auxiliary database installation 6-161

6.10 Analytics server installation 6-167





6.1 Overview

This chapter describes the installation of the following 5620 SAM components for standalone and redundant system deployments:

• main server• auxiliary server• Cflowd auxiliary server• analytics server• 5620 SAM database• auxiliary database

Chapters 14 and 15 describe single-user client and client delegate server installation.

Before you attempt to perform a procedure in this chapter, ensure that you understand and comply with the relevant requirements, considerations, and precautions described in chapter 1 of this guide.

See Appendix A for 5620 SAM installation parameter descriptions.

6.2 5620 SAM installation procedures list

Table 6-1 lists the 5620 SAM software installation procedures.

Table 6-1 5620 SAM installation procedures list

Caution — Alcatel-Lucent supports 5620 SAM software configuration only under the conditions described in chapter 1.

Procedure Purpose

To install a standalone 5620 SAM system Install the database and server software in a standalone deployment on one or more stations.

To install a redundant 5620 SAM system Install the database and server software in a redundant deployment.

To install a 5620 SAM auxiliary server Install the auxiliary server software on a station.

To add an auxiliary server to a 5620 SAM system Add an auxiliary server to an existing 5620 SAM system.

To install a 5620 SAM Cflowd auxiliary server Install the Cflowd auxiliary server software on a station.

To configure Cflowd auxiliary server communication

Configure a Cflowd auxiliary server to communicate with 5620 SAM servers and NEs.

To install a 5620 SAM auxiliary database Install the auxiliary database software on a station.

To enable an auxiliary database in a 5620 SAM system

Enable communication among the auxiliary database stations, and between the stations and other 5620 SAM components.

(1 of 2)




To install and enable a 5620 SAM analytics server

Install the 5620 SAM analytics server software on a station.

Procedure Purpose

(2 of 2)





6.3 Standalone system installation workflow

The following is the sequence of high-level actions required to install a standalone 5620 SAM system. A reference in quotation marks is a link to a section in Procedure 6-1.

1 Install the database; see “Install standalone 5620 SAM database”.

2 Install the main server; see “Install standalone main server”.

3 Install and enable one or more auxiliary servers, if required; see Section 6.7.

4 Install and enable one or more Cflowd auxiliary servers, if required; see Section 6.8.

5 Install and enable an auxiliary database, if required; see Section 6.9.

6 Install an analytics server, if required; see Section 6.10.

7 Install one or more 5620 SAM clients; see “Install client”.




6.4 Standalone system installation

This section describes how to install the software components of a standalone 5620 SAM system.

Procedure 6-1 describes how to install the main server and database software.

Procedure 6-1 To install a standalone 5620 SAM system

Perform this procedure to install the 5620 SAM main server and database software in a standalone deployment on one or more stations. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses.

You require the following user privileges to perform this procedure:

• on the main server station• root

• on the database station:• root• Oracle management

Note 1 — Command-line examples use the following to represent the RHEL CLI prompts:

• #—represents the prompt for the root user• bash$—represents the prompt for the samadmin and Oracle

management users

Do not type the # symbol or bash$ when you enter a command.

Note 2 — If you are performing a procedure in this section from a remote terminal, you must ensure the following:

• that the DISPLAY environment variable is correctly set for display redirection

• that the remote system allows access for display terminal support

Otherwise, the 5620 SAM installer GUI does not open.

Caution — Before a 5620 SAM system installation, you must ensure that the RHEL iptables and ip6tables firewall on each station is disabled.

Note 1 — The samadmin user account is created on the main server station during this procedure.

Note 2 — The Oracle management user account is created on the database station during this procedure.





Run Oracle pre-installation script

1 Before you perform a 5620 SAM database installation, you must run a script that configures the Oracle management user account.

Log in as the root user on the station that is to be the database station.




# cd Linux ↵


# ./OracleSw_PreInstall.sh ↵


Please select between the following option:

1) NEW INSTALL, DB RESTORE, OR DB RECONFIGURATION OF 5620 SAM

2) UPGRADE OF 5620 SAM

3) EXIT

Please enter(1,2 or 3):

6 Enter 1 ↵.


Enter the Oracle dba group name [default]:

7 Enter a group name and press ↵.

The following messages are displayed:

Creating group group if it does not exist ...

done


Note — The default values displayed by the script are shown as [default]. To accept a default value, press ↵.

If you specify a value other than the default, you must record the value for use when the OracleSw_PreInstall.sh script is run during a software upgrade, or when the Oracle management user information is required by Alcatel-Lucent technical support.

Note — To reduce the complexity of subsequent software upgrades and technical support activities, Alcatel-Lucent recommends that you accept the default.




Enter the Oracle user name [default]:

8 Enter a username and press ↵.


Oracle user [username] new home directory will be [/opt/5620sam/oracle12r1].

Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1...

Checking user username...

Adding username...

Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group.

About to unlock the UNIX user [username]

Unlocking password for user username.

passwd: Success

Unlocking the UNIX user [username] completed


Please assign a password to the UNIX user username ..

New Password:

9 Type a password and press ↵. The following prompt is displayed:

Re-enter new Password:

10 Retype the password and press ↵. The following message is displayed if the password update is successful:

passwd: password successfully changed for username


Specify whether a 5620 SAM server will be installed on this workstation.

The database memory requirements will be adjusted to account for the additional load.

Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]:

11 Enter Yes or No, as required, and press ↵.






The script generates the following messages:

INFO: About to set kernel parameters in /etc/sysctl.conf...

INFO: Completed setting kernel parameters in /etc/sysctl.conf...

INFO: About to change the current values of the kernel parameters

INFO: Completed changing the current values of the kernel parameters

INFO: About to set ulimit parameters in /etc/security/limits.conf...

INFO: Completed setting ulimit parameters in /etc/security/limits.conf...

INFO: Completed running Oracle Pre-Install Tasks

12 When the script execution is complete, enter the following to reboot the database station:

# init 6 ↵

The station reboots.

The next section of the procedure describes the standalone 5620 SAM database installation.

Install standalone 5620 SAM database

13 When the reboot is complete, log in as the root user on the station that is to be the 5620 SAM database station.


15 Enter the following to switch to the Oracle management user created by the pre-installation script:

# su - Oracle_management_user_name ↵

where Oracle_management_user_name is the name of the UNIX account with Oracle management privileges, typically oracle



bash$ ./DBConfig_RHEL_SAM_R_r_revision.bin ↵






The splash screen shown in Figure 6-1 opens.

Figure 6-1 5620 SAM installer

18 The 5620 SAM database installer opens, as shown in Figure 6-2. The left pane indicates installation progress. The right pane displays release information about the software. Click on the Next button.

Figure 6-2 Introduction





19 Review and accept the terms of the license agreement shown in Figure 6-3. Click on the Next button.

Figure 6-3 Software License Agreement

20 Select Install and Configure a Standalone Database, as shown in Figure 6-4. Click on the Next button.

Figure 6-4 Choose Installation Type




21 Select Install Oracle Software, as shown in Figure 6-5. Click on the Next button.

Figure 6-5 Install Oracle Software

The installer prepares to install the database, as shown in Figure 6-6.

Figure 6-6 Installing 5620 SAM Database Configurator





22 Perform the following steps when the panel in Figure 6-7 is displayed.

Figure 6-7 Oracle Pre-Install Script

i Open a separate console window.

ii Enter the following to run the script named in the panel:

# /opt/5620sam/samdb/install/config/orainstRoot.sh ↵

The script generates messages like the following:

Creating the Oracle inventory pointer file (/etc/oraInst.loc)

Creating the Oracle inventory directory (/opt/5620sam/oracle12r1/oraInventory)

Changing groupname of /opt/5620sam/oracle12r1/oraInventory to (group).

where group is the group name of the Oracle management user, typically dba

iii When the script execution is complete, close the console window.

iv Click on the Next button.




23 You are prompted to install Oracle software, as shown in Figure 6-8. This operation can take one hour or more. Click on the Start Oracle Installation button to begin the Oracle software installation.

Figure 6-8 Install Oracle Database Management Software

24 As shown in Figure 6-9, Oracle installation details are displayed as the installation progresses. When the installation is complete, click on the Next button.







Figure 6-10 Oracle Post-Install Script


ii Enter the following to run the Oracle post-install script:

# /opt/5620sam/samdb/install/config/orapostinstRoot.sh ↵

The script displays the following message:

Check /opt/5620sam/oracle12r1/install/root_hostname_timestamp.log for output

where hostname is the hostname of this stationtimestamp is the script execution start time

iii If the script generates a message that contains the word “error”, view the script log file named in the message, and contact Alcatel-Lucent technical support for assistance, if required.

iv When the script execution is complete, close the console window.

v Click on the Next button.




26 Configure the following parameters shown in Figure 6-11, then click on the Next button:

• Public IP (accessible to servers)• Database User Password• Confirm Database User Password

The “Database User Password” value that you specify must meet the following criteria:

• The password must be between 4 and 30 characters long.• The password must contain at least three of the following:

• lower-case alphabetic character• upper-case alphabetic character• numeric character• special character, which is one of the following:

# $ _• The password must not contain four or more of the same character type in

sequence.• The password must not be the same as the user name or its reverse.• The password must not contain a space character.

Figure 6-11 General Database Configuration Info





27 Configure the following parameters shown in Figure 6-12, then click on the Next button.

• SYS Password• Confirm SYS Password

The password value that you specify must meet the following criteria:





Figure 6-12 Oracle SYS Password





If the “Enable 5620 SAM Server IP Validation” parameter is selected, only the server at the specified IP address or hostname can connect to the database.

• Enable 5620 SAM Server IP Validation• Server IP Address

Figure 6-13 Main Server IP Validation





29 The panel in Figure 6-14 is displayed If the “Enable 5620 SAM Server IP Validation” parameter in step 28 is selected. Otherwise, go to step 32.

Figure 6-14 Auxiliary Servers

Perform the following steps.

i Click on the Add button. The form shown in Figure 6-15 opens.

Figure 6-15 Auxiliary Server IP Validation

ii Enter the auxiliary server IP address or hostname.

iii Click on the OK button to save the information and close the form.

iv Repeat steps 29 i to iii to specify an additional auxiliary server, if required.





31 Configure the “Accounting Statistic Data Retention Period” parameter shown in Figure 6-16. Click on the Next button.

Figure 6-16 Accounting Statistics Database Retention Period

32 You are prompted to begin database creation, as shown in Figure 6-17. Database creation can take one hour or more, depending on the tablespace configuration. Click on the Start Process button to begin the database creation.

Figure 6-17 Database Creation





The next panel displays database creation progress, as shown in Figure 6-18.


33 When the panel in Figure 6-19 is displayed, the 5620 SAM database installation is complete, but as shown in the panel text, you must run a script to enable automatic database startup.

Figure 6-19 Installation Complete




Perform the following steps to run the script described in the panel.

i Open a separate console window as the root user.


# /opt/5620sam/samdb/install/config/samdb/SAMDb_root.sh ↵


34 Click on the Done button to close the database installer.

35 Alcatel-Lucent recommends that as a security measure, you limit the number of database user login failures that the 5620 SAM allows before the database user account is locked.

For information about how to limit the number of database user login failures, see the “5620 SAM database management procedures” section of the 5620 SAM System Administrator Guide.


bash$ exit ↵

37 Enter the following to reboot the database station:

# init 6 ↵


The next section of the procedure describes the main server installation.

Install standalone main server

38 Log in as the root user on the station that is to be the main server station.




# ./ServerInstall_RHEL_SAM_R_r_revision.bin ↵









42 The 5620 SAM server installer opens, as shown in Figure 6-21. The left pane indicates installation progress. The right pane displays release information about the software. Click on the Next button.







44 Select Main Server Installation, as shown in Figure 6-23. Click on the Next button.






45 As shown in Figure 6-24, the installer indicates which release of 5620 SAM software is to be installed. Verify the information. Click on the Next button.

Figure 6-24 Checking Build Compatibility

46 Configure the License File parameter shown in Figure 6-25 using the absolute file path of the 5620 SAM license zip file. Click on the Next button.

Figure 6-25 License Information for 5620 SAM Main Server





• Redundancy Supported• Auxiliary Server Supported• Client Delegate Server Supported

Figure 6-26 Additional Server Configuration

Note — You must leave the “Redundancy Supported” parameter unselected, as shown in Figure 6-26.





48 Configure the following parameters, shown in Figure 6-27, using the recorded values from the database installation. Click on the Next button.

• Database Server IP address• Database User Password

Figure 6-27 Database Configuration





• Online Backup Interval (Hours) (typically 24)• Online Backup Destination (typically /opt/5620sam/dbbackup)• Number Of Backup Sets (typically 3)

Figure 6-28 Online Database Backup

Note — The “Online Backup Destination” value is a path on the file system of the database station specified in step 48.





50 The panel in Figure 6-29 is displayed if you select the “Auxiliary Server Supported” parameter in step 47. Otherwise, go to step 52.

Figure 6-29 Main Server Configuration for Auxiliary Servers

Perform the following steps:

i Configure the parameters:

• Public IP (accessible to auxiliary)• Enable Stats Collection on Auxiliary Servers• Enable Call Trace Collection on Auxiliary Servers

Note — An auxiliary server can perform statistics collection or call-trace data collection, but not both.




ii Click on the Next button. The panel shown in Figure 6-30 is displayed.


iii Click on the Add button. The form shown in Figure 6-31 opens.

Figure 6-31 Auxiliary Server Configuration

iv Configure the parameters:

• IP Address• Type

v Click on the OK button to save the information and close the form.

Note — All IP communication from a 5620 SAM auxiliary server to a 5620 SAM main server must originate from one IP address, which is the address specified in this step. A main server rejects communication from the auxiliary server if the auxiliary server uses a source address other than the address specified in this step.





vi Repeat steps 50 iii to v to specify an additional auxiliary server, if required.

vii If “Enable Call Trace Collection on Auxiliary Servers” is selected in step 50 i, click on the “Configure Call Trace Auxiliary Servers” button shown in Figure 6-30. Otherwise, go to step 51.

viii The form shown in Figure 6-32 opens. Select a preferred auxiliary server in the upper left panel, optionally select the associated reserved auxiliary server in the lower left panel, and click on the “Make Pair from Selected” button. The auxiliary servers move to the list on the right side of the form.

Figure 6-32 Configure Call Trace Auxiliary Servers

ix Repeat step 50 viii to configure another call-trace auxiliary server pair, if required.


Note — A preferred auxiliary server is required; a reserved auxiliary server is optional.




52 Configure the parameters shown in Figure 6-33, then click on the Next button:

• Server Domain Name (typically 5620sam)This parameter uniquely identifies the 5620 SAM server cluster.

• Use Hostname for Communication

• NAT (network address translation) Used• Private IP (accessible only by this server)

• Public IP (accessible to clients)

• JNDI Server Port (typically 1099)• Enable AA Stats File Processing• AA Stats File Format

• Enable 3GPP OSS Interface

Figure 6-33 Main Server Configuration for Clients

Note — You must select the “Use Hostname for Communication” parameter if the main server is to use multiple interfaces for GUI and OSS client communication.

Note — The “Private IP (accessible only by this server)” parameter is configurable when the “NAT (network address translation) Used” parameter” is selected.

Note — The “Public IP (accessible to clients)” parameter is configurable when the “Use Hostname for Communication” parameter is unselected.

Note — The “AA Stats File Format” parameter is configurable when the “Enable AA Stats File Processing” parameter is selected.





53 The panel in Figure 6-34 is displayed if you do not select the “Auxiliary Server Supported” parameter in step 47. Otherwise, go to step 54.

Configure the parameters shown in Figure 6-34:

• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5620 SAM main server and the OSS clients.

• Public IP (accessible to OSS clients)

Figure 6-34 Server Configuration for OSS Clients

54 The panel in Figure 6-35 is displayed if you select the “Client Delegate Server Supported” parameter in step 47. Otherwise, go to step 55.

Figure 6-35 Client Delegate Servers




Perform the following steps for each client delegate server.

i Click on the Add button. The panel in Figure 6-36 opens.


ii Configure the parameters:

• IP Address

• Install Directory PathThis is the absolute file path of the client installation location on the client delegate server station.

iii Click on the OK button to save your changes and close the form.

Note — If NAT is used between the main server and client delegate servers, specify the public IP address.





55 Perform the following steps to enable communication security between the main server and clients, and between the main and auxiliary servers. Otherwise, click on the Next button.

i Select the “Enable Secure Communication” parameter shown in Figure 6-37.

Figure 6-37 SSL Configuration

ii Configure the following parameters:

• Keystore File• Keystore Password• Truststore File• Truststore Password• Enable WebDAV access to activation data

iii Click on the Next button. The main server copies the files and imports them into the main server configuration.

Note — See chapter 4 for information about creating SSL keystore and truststore files, and for general 5620 SAM SSL configuration information.




56 If the 5620 SAM deployment includes a 5650 CPAM server, select the check box shown in Figure 6-38 and configure the License File parameter using the absolute file path of the 5650 CPAM license zip file. Click on the Next button.

Figure 6-38 License Information for 5650 CPAM Server






• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5620 SAM main server and the managed network.

• IPv6 Address Used• SNMP Trap Receiving IPv4 Address• SNMP Trap Receiving IPv6 Address• SNMP Trap Receiving Port (typically 162)• Trap Log Id (typically 98)• Enable CORBA Notification Service• Notification Listening IP Address

Figure 6-39 Mediation Configuration

Caution — Some device types do not support an SNMP port value other than 162. Before you configure the “SNMP Trap Receiving Port” parameter to a value other than the default, you must ensure that each type of device in the managed network supports the configuration.

Note 1 — The “SNMP Trap Receiving IPv6 Address” parameter is configurable only when the “IPv6 Address Used” parameter is selected, as shown in Figure 6-39.

Note 2 — The “Notification Listening IP Address” parameter is configurable only when the “Enable CORBA Notification Service” parameter is selected, as shown in Figure 6-39.




58 If you require 5620 SAM client navigation from a 5620 NM system, select the “Enable Navigation from External Systems” parameter shown in Figure 6-40 and specify the TCP port that the client is to use for accepting navigation requests. Click on the Next button.

Figure 6-40 Navigation from External Systems

59 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 6-41. Click on the Install button to begin the server installation.

Figure 6-41 XML Output Directory





The next panel displays installation progress, as shown in Figure 6-42.

Figure 6-42 Installing 5620 SAM/5650 CPAM Server

60 The main server is installed as a UNIX daemon, as shown in Figure 6-43. Click on the Next button.

Figure 6-43 Installing the Server as a Unix Daemon




61 When the main server installation is complete, as shown in Figure 6-44, configure the “Start the 5620 SAM Main Server” parameter to specify whether you want the server to start immediately after the installation.


62 View the panel text to see whether it states that you must assign a password to samadmin, as shown in Figure 6-44. This information is required in step 65.

63 Click on the Done button to close the server installer. If you specified that the main server is to start after installation, the server starts. Initial server startup can take twenty minutes or more.

64 If you intend to enable Small Cell management, perform Procedure 5-1 on the main server station.

65 If this is the first 5620 SAM server installation on the station, the installer creates a user account called samadmin for 5620 SAM system administration.

Caution — If you intend to enable Small Cell management, you must perform additional configuration steps before you start the main server, as described in step 64.

Note — The “Start the 5620 SAM Main Server” parameter is configurable only if you specify a 5620 SAM or 5650 CPAM license file during the installation.





If you must assign a password to samadmin, as determined in step 62, perform the following steps.


# passwd samadmin ↵


New Password:

ii Enter the new password and press ↵.


Confirm New Password:

iii Enter the new password again and press ↵. The password is changed.

iv Record the new password and store it in a secure location.

66 Perform the following steps.

i Log in as the samadmin user on the main server station.



bash$ mkdir /opt/5620sam/nebackup/backup ↵

67 If you specified that the main server is to start after installation, perform the following steps to verify that the main server is started.



bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status ↵

The command returns server status information.

If the main server is not completely started, the first line of status information is the following:

Main Server is not ready...

The main server is completely started when the command returns the following line of output:

Note — The samadmin password must not contain the @ symbol, or eNodeB device management may be compromised.




-- SAM Server is UP

iii If the command output indicates that the server is not completely started, wait five minutes and then return to step 67 ii.

Do not proceed to the next step until the server is completely started.

68 If you specified not to start the main server immediately after the installation, perform the following steps to start the server manually.



iii Enter the following to navigate to the server binary directory:


iv Enter the following to start the main server application:

bash$ ./nmsserver.bash start ↵

v Enter the following:






-- SAM Server is UP

vi If the command output indicates that the server is not completely started, wait five minutes and then return to step 68 v.



Note — If you did not specify a license file during the installation, you cannot start the server until you import a license. See the “Software and license configuration procedures” section in the 5620 SAM System Administrator Guide for information about importing a license.





Install client

70 Perform one of the following to install a 5620 SAM client.

a Perform the appropriate procedure in chapter 14 to install a single-user client.

b Perform the appropriate procedure in chapter 15 to install a client delegate server.




6.5 Redundant system installation workflow

The following is the sequence of high-level actions required to install a redundant 5620 SAM system. A reference in quotation marks is a link to a section in Procedure 6-2.

1 Prepare the primary database station for the installation; see “Run Oracle pre-installation script for primary database”.

2 Install the primary database; see “Install primary database”.

3 Prepare the standby database station for the installation; see “Run Oracle pre-installation script for standby database”.

4 Install the standby database; see “Install standby database”.

5 Install the primary main server; see “Install primary main server”.

6 Install a single-user client or client delegate server; see “Install client”.

7 Reinstantiate the primary database on the standby database station; see “Reinstantiate database on standby station”.

8 Install the standby main server; see “Install standby main server”.

9 Install and enable one or more auxiliary servers, if required; see Section 6.7.

10 Install and enable one or more Cflowd auxiliary servers, if required; see Section 6.8.

11 Install and enable an auxiliary database, if required; see Section 6.9.

12 Install an analytics server, if required; see Section 6.10.

13 Install additional single-user clients or client delegate servers, as required; see “Install additional client”.





6.6 Redundant system installation

This section describes how to install the software components of a redundant 5620 SAM system. Procedure 6-2 describes how to install the primary and standby 5620 SAM database and main server software.

Procedure 6-2 To install a redundant 5620 SAM system

Perform this procedure to install the 5620 SAM primary and standby main server and database software. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses.


• on each main server station:• root

• on each database station:• root• Oracle management



management users






Caution — Before a 5620 SAM system installation, you must ensure that the RHEL iptables and ip6tables function on each station is disabled.

Note 1 — The samadmin user account is created on each main server station during this procedure.

Note 2 — The Oracle management user account is created on each database station during this procedure.




Run Oracle pre-installation script for primary database


Log in as the root user on the station that is to be the primary database station.




# cd Linux ↵







3) EXIT


6 Enter 1 ↵.






done




Note — To reduce the complexity of subsequent software upgrades and technical support activities, Alcatel-Lucent recommends that you accept the default for this parameter.











Adding username...




passwd: Success




New Password:






















12 When the script execution is complete, enter the following to reboot the primary database station:

# init 6 ↵


The next section of the procedure describes the primary 5620 SAM database installation.

Install primary database

13 When the reboot is complete, log in as the root user on the station that is to be the primary database station.


15 Enter the following to switch to the oracle user created by the pre-installation script:





bash$ cd Linux ↵


















21 Select Install & Configure Primary/Standby Database, as shown in Figure 6-48. Click on the Next button.






22 Select Primary Database Install, as shown in Figure 6-49. Click on the Next button.

Figure 6-49 Install & Configure Primary/Standby Database





























26 Oracle installation details are displayed as the installation progresses. When Oracle installation is complete, as shown in Figure 6-54, click on the Next button.




















28 Configure the following primary database installation parameters shown in Figure 6-56, then click on the Next button:

• Public IP (accessible to servers)• Instance Name (typically samdb1)• Database User Password• Confirm Database User Password

The “Database User Password” value that you specify must meet the following criteria:





Figure 6-56 Primary Database Configuration Info






• SYS Password• Confirm SYS Password

The password value that you specify must meet the following criteria:





Figure 6-57 Oracle SYS Password





If the “Enable 5620 SAM Server IP Validation” parameter is selected, only the servers at the specified IP addresses or hostnames can connect to the database.

• Enable 5620 SAM Server IP Validation• Server One IP Address• Server Two IP Address




















34 Configure the following parameters shown in Figure 6-62, record the information for use later in the procedure, then click on the Next button:

• Standby IP Address• Standby Instance Name (typically samdb2)

Figure 6-62 Standby Database Info





35 You are prompted to begin primary database creation, as shown in Figure 6-63. Database creation can take one hour or more, depending on the tablespace configuration. Click on the Start Process button to begin the database creation.
















For information about how to limit the number of database user login failures, see the “5620 SAM database management procedures” section of the 5620 SAM System Administrator Guide.


bash$ exit ↵

40 Enter the following to reboot the primary database station:

# init 6 ↵






Run Oracle pre-installation script for standby database


Log in as the root user on the station that is to be the standby database station.




# cd Linux ↵







3) EXIT


46 Enter 1 ↵.






done




Note — To reduce the complexity of subsequent software upgrades and technical support activities, Alcatel-Lucent recommends that you accept the default for this parameter.










Adding username...




passwd: Success




New Password:























52 When the script execution is complete, enter the following to reboot the standby database station:

# init 6 ↵


The next section of the procedure describes the standby 5620 SAM database installation.

Install standby database

53 When the reboot is complete, log in as the root user on the station that is to be the standby database station.


55 Enter the following to switch to the oracle user created by the pre-installation script:





bash$ cd Linux ↵























62 Select Standby Database Install, as shown in Figure 6-70. Click on the Next button.































66 Oracle installation details are displayed as the installation progresses, as shown in Figure 6-75. When installation is complete, click on the Next button.




















68 Configure the “Public IP (accessible to servers)” parameters shown in Figure 6-77, then click on the Next button.

Figure 6-77 Standby Database Configuration Info






• Enable 5620 SAM Server IP Validation• Server One IP Address

This is the “Server One IP Address” value from step 30.• Server Two IP Address

This is the “Server Two IP Address” value from step 30.


















72 Configure the following parameters, shown in Figure 6-81, using the recorded values from the primary database installation. Click on the Next button.

• Primary IP Address• Primary Instance Name (typically samdb1)• Primary SYS Password

Figure 6-81 Primary Database Info

73 You are prompted to begin standby database creation, as shown in Figure 6-82. Click on the Start Process button to begin.

Figure 6-82 Standby Database Configuration














bash$ exit ↵

77 Enter the following to reboot the new primary database station:

# init 6 ↵


The next section of the procedure describes the installation of the primary main server.

Install primary main server

78 Log in as the root user on the station that is to be the primary server station.







# cd Linux ↵











83 The 5620 SAM server installer opens, as shown in Figure 6-85. The left pane indicates the installation progress. The right pane displays release information about the software. Click on the Next button.























Note — You must select the “Redundancy Supported” parameter, as shown in Figure 6-90.





89 Configure the following parameters, shown in Figure 6-91, using the recorded values from the primary database installation. Click on the Next button.

• Primary Database Server IP Address• Primary Database Instance Name (typically samdb1)• Database User Password

Figure 6-91 Primary Database Configuration




90 Configure the following database backup parameters shown in Figure 6-92, then click on the Next button:








91 Configure the following parameters shown in Figure 6-93 using the recorded values from the standby database installation, then click on the Next button:

• Standby Database Server IP Address• Standby Database Instance Name (typically samdb2)• Enable Database Backup File Synchronization





92 The panel in Figure 6-94 is displayed if you select the “Auxiliary Server Supported” parameter in step 88. Configure the following parameters, and click on the Next button; otherwise, go to step 96:








93 Configure the “Peer Server IP Address” parameter shown in Figure 6-95 by specifying the IP address that the auxiliary servers must use to reach the other main server, and then click on the Next button.

Figure 6-95 Peer Main Server Configuration for Auxiliary Servers

94 Specify the 5620 SAM auxiliary servers using the panel shown in Figure 6-96.











Note 1 — All IP communication from a 5620 SAM auxiliary server to a 5620 SAM main server must originate from one IP address, which is the address specified in this step. A main server rejects communication from the auxiliary server if the auxiliary server uses a source address other than the address specified in this step.

Note 2 — When you assign the Preferred and Reserved auxiliary servers for this main server, there are two configurations to consider.

• The auxiliary server that you specify as the Preferred auxiliary server is the same for each main server. In this configuration, after a main server activity switch, the same auxiliary server is used.

• The auxiliary server that you specify as the Preferred auxiliary server is the Reserved auxiliary server of the other main server. In this configuration, after a main server activity switch, the other auxiliary server is used.






v If “Enable Call Trace Collection on Auxiliary Servers” is selected in step 92, click on the “Configure Call Trace Auxiliary Servers” button shown in Figure 6-96. Otherwise, go to step 95.

vi The form shown in Figure 6-98 opens. Select a preferred auxiliary server in the upper left panel, optionally select the associated reserved auxiliary server in the lower left panel, and click on the “Make Pair from Selected” button. The auxiliary servers move to the list on the right side of the form.


vii Repeat step 94 vi to configure another call-trace auxiliary server pair, if required.





96 If you select the “Enable Database Alignment” parameter shown in Figure 6-99, you must specify the preferred database of this main server, then click on the Next button.

Database alignment associates each main server with the database to which it is most directly connected in terms of network latency. This database is the preferred database of the main server. For example, in a 5620 SAM complex that is geographically dispersed, the preferred database of a main server is the database in the same physical facility; typically, the primary main server and database are in one facility, and the standby server and database are in another.

When a primary server starts, it verifies that the database to which it connects is the preferred database. If this database is not the preferred database, the server performs a database switchover to reverse the primary and standby database roles. If the switchover is successful, the main servers and databases in the 5620 SAM complex are aligned. If the switchover fails, each database reverts to the former role, and the main server raises an alarm about the failed switchover.

When database alignment is enabled and you perform a database switchover, the primary server does not attempt database realignment, because a switchover is a manual operation that is considered to be a purposeful act.

When database alignment is enabled and you perform a server activity switch, the primary main server performs an automatic database switchover to maintain alignment with the preferred database.

Figure 6-99 Database Alignment






• Enable Auto Re-Instantiation of Standby DatabaseIf this parameter is selected, the 5620 SAM main server automatically reinstantiates the standby database after a database failover.

• Delay Time After Database Failover (minutes)This parameter specifies how long, in minutes, the main server waits after database failover completion before it initiates a standby database reinstantiation.

Figure 6-100 Auto Re-Instantiation After Database Failover

Note — The “Delay Time After Database Failover (minutes)” parameter is configurable when the “Enable Auto Re-Instantiation of Standby Database” parameter is selected.




























100 Configure the “Public IP (accessible to peer server)” parameter shown in Figure 6-103 using the IP address that the other main server must use to reach this main server, and click on the Next button.

Figure 6-103 Main Server Configuration for Peer Server


• Public IP (accessible to peer server)• Peer Public IP (accessible to this server)

Figure 6-104 Synchronization of Data











• IP Address



































• Peer Server IP Address• Peer Server Trap Log Id (typically 98)• Peer Server SNMP Trap Receiving IPv4 Address• Peer Server SNMP Trap Receiving IPv6 Address• Peer Server SNMP Port Number (typically 162)

Figure 6-110 Peer Main Server Configurations

107 If the “Use Hostname for Communication” parameter in step 98 is selected, go to step 110.

Caution — Some device types do not support an SNMP port value other than 162. Before you configure the “Peer Server SNMP Trap Receiving Port” parameter to a value other than the default, you must ensure that each type of device in the managed network supports the configuration.

Note — The “Peer Server SNMP Trap Receiving IPv6 Address” parameter is configurable only if you select the “IPv6 Address Used” parameter in step 105.





• Peer Server IP Address• JNDI Peer Server Port (typically 1099)

Figure 6-111 Peer Main Server Configuration for Clients

109 Go to step 111.






• Peer Server Hostname• JNDI Peer Server Port (typically 1099)















113 As shown in Figure 6-116, the main server is installed as a UNIX daemon. Click on the Next button.








116 Click on the Done button to close the server installer. If you specified that the main server is to start after installation, the server starts. Initial server startup can take twenty minutes or more.

117 If you intend to enable Small Cell management, perform Procedure 5-1 on the primary main server station.







118 If this is the first 5620 SAM server installation on the station, the installer creates a user account called samadmin for 5620 SAM system administration.If you must assign a password to samadmin, as determined in step 115, perform the following steps.




New Password:











120 If you specified that the main server is to start after installation, perform the following steps to verify that the server is started.












-- Primary Server is UP
















vi If the command output indicates that the server is not completely started, wait five minutes and then return to step 121 iv.


Install client









Reinstantiate database on standby station

124 Log in to a 5620 SAM client as the admin user.

125 Choose Administration→System Information from the 5620 SAM main menu. The System Information form opens with the General tab displayed.

126 Click on the Re-Instantiate Standby button. A dialog box appears.

127 Click on the Yes button. The database reinstantiation begins. You can view the reinstantiation status on the client GUI status bar or on the System Information form. The Standby Re-instantiation State changes from In Progress to Success when reinstantiation is complete. The start time of the reinstantiation is shown by the Last Attempted Standby Re-instantiation Time indicator.

128 When the reinstantiation is complete, close the System Information form.

The next section of the procedure describes the installation of the standby main server.

Install standby main server

129 Log in as the root user on the station that is to be the standby main server station.




# cd Linux ↵





Note — Database reinstantiation can take a long time when there is a large amount of statistics information to transfer.


































140 Configure the following parameters, shown in Figure 6-125 using the recorded values from the primary database installation. Click on the Next button.







141 Configure the following parameters shown in Figure 6-126 using the recorded values from the standby database installation, then click on the Next button:
























































• Delay Time After Database Failover (minutes)This parameter specifies how long, in minutes, the main server waits after database failover completion before it initiates a standby database reinstantiation.













































• IP Address













Note — The parameter values must match the values specified during the primary main server installation.






















• Peer Server IP Address• Peer Server Trap Log Id (typically 98)• Peer Server SNMP Trap Receiving IPv4 Address• Peer Server SNMP Trap Receiving IPv6 Address• Peer Server SNMP Trap Receiving Port (typically 162)











159 Go to step 161.





























166 Click on the Done button to close the server installer. If you specified that the main server is to start after installation, the server starts.

167 If you intend to enable Small Cell management, perform Procedure 5-1 on the standby main server station.












New Password:











170 If you specified that the main server is to start immediately after installation, perform the following steps to verify that the server is started.












-- Standby Server is UP

iii If the command output indicates that the server is not completely started, wait five minutes and then return to step 170 iii.






















Install additional client







6.7 Auxiliary server installation

This section describes how to install a 5620 SAM auxiliary server for a standalone or redundant 5620 SAM system. Procedure 6-3 describes how to install the auxiliary server software. Procedure 6-4 describes how to add a new auxiliary server to an existing 5620 SAM system.

Procedure 6-3 To install a 5620 SAM auxiliary server

Perform this procedure to install the 5620 SAM auxiliary server software on a station. You require root user privileges on the station to perform this procedure. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses.

1 Log in as the root user on the station that is to be the auxiliary server station.




# cd Linux ↵



management users






Note 1 — An auxiliary server is dedicated to only one of the following functions:

• statistics collection• call-trace data collection

Note 2 — The installer creates the samadmin user account on the auxiliary server station during this procedure.











6 The 5620 SAM server installer opens, as shown in Figure 6-152. The left pane indicates installation progress. The right pane displays release information about the software. Click on the Next button.







8 Select Auxiliary Server Installation, as shown in Figure 6-154. Click on the Next button.











10 Configure the parameters shown in Figure 6-156:

• Server Domain Name (typically 5620sam)This parameter uniquely identifies the 5620 SAM server cluster to which the auxiliary server belongs.

• Public IP (accessible to servers)• Redundancy Supported On the 5620 SAM Main Server

Select this parameter only if the 5620 SAM main servers are deployed in a redundant configuration.

• Enable Stats ServiceSelect this parameter if the 5620 SAM auxiliary server is to be used for statistics collection.

• Enable Call Trace ServiceSelect this parameter if the 5620 SAM auxiliary server is to be used for call-trace data collection.

Figure 6-156 Auxiliary Server Address Configuration







a If the “Redundancy Supported On the 5620 SAM Main Server” parameter in step 10 is not selected, configure the “Server IP Address” parameter shown in Figure 6-157:

Figure 6-157 Main Server Configuration

b If the “Redundancy Supported On the 5620 SAM Main Server” parameter in step 10 is selected, configure the parameters shown in Figure 6-158:

• Server One IP Address• Server Two IP Address






• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5620 SAM auxiliary server and the OSS clients.







13 If “Enable Call Trace Service” in step 10 is not selected, go to step 15.

14 The panel shown in Figure 6-160 is displayed if you select the “Enable Call Trace Service” parameter in step 10. Configure the following parameters, then click on the Next button:

• IPv6 Address Used• Call Trace Receiving IPv4 Address• Call Trace Receiving IPv6 Address• Call Trace Receiving Directory (typically /opt/5620sam/calltrace)• Debug Trace Receiving Directory (typically /opt/5620sam/debugtrace)

Figure 6-160 Auxiliary Server Call Trace Configuration

Note — The “Call Trace Receiving IPv6 Address” parameter is displayed only when the “IPv6 Address Used” parameter is selected, as shown in Figure 6-160.





• Enable Synchronization of Data• Public IP (accessible to peer auxiliary)• Peer Public IP (accessible to this auxiliary)


Note — The “Public IP (accessible to peer auxiliary)” and “Peer Public IP (accessible to this auxiliary)” parameters are configurable only when the “Enable Synchronization of Data” parameter is enabled.





16 Perform the following steps to enable communication security between the auxiliary server and each main server. Otherwise, click on the Next or Install button to continue.





iii Click on the Next or Install button.





17 The panel in Figure 6-163 is displayed if the “Enable Stats Service” parameter in step 10 is selected. Specify an OSS XML output location (typically /opt/5620sam/auxserver/xml_output), and then click on the Install button to begin the auxiliary server installation.








18 As shown in Figure 6-165, the 5620 SAM auxiliary server is installed as a UNIX daemon. Click on the Next button.


19 When the auxiliary server installation is complete, as shown in Figure 6-166, configure the “Start the 5620 SAM Auxiliary Server” parameter to specify whether you want the server to start immediately after the installation.


Caution — If you intend to enable Small Cell management using the auxiliary server, you must perform additional steps before you start the auxiliary server, as described in step 23.





21 Click on the Done button to close the server installer. If you specified that the auxiliary server is to start after installation, the server starts. Initial server startup can take twenty minutes or more.






New Password:






23 If you intend to enable Small Cell management using the auxiliary server, perform Procedure 5-1 on the auxiliary server station.

24 If you specified not to start the auxiliary server immediately after the installation, you can start it later by performing the following steps.



iii Enter the following to start the auxiliary server application:

bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart ↵






The auxiliary server starts. Initial server startup can take twenty minutes or more.

Note — The order in which an auxiliary server and the primary main server initialize is unimportant. The primary main server synchronizes with an auxiliary server as soon as it is able to communicate with the auxiliary server.




Procedure 6-4 To add an auxiliary server to a 5620 SAM system

Perform this procedure to add one or more 5620 SAM auxiliary servers to a 5620 SAM system. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses.


• on each main and auxiliary server station:• root• samadmin

• on each database station that has IP validation enabled:• Oracle management

1 Perform Procedure 6-3 to install an auxiliary server.

2 If the 5620 SAM is deployed in a standalone configuration, go to step 6.

3 Perform steps 6 to 14 on the standby main server, which is called Server B in this procedure.

4 Perform steps 6 to 14 on the primary main server, which is called Server A in this procedure.

5 Go to step 16.

6 Log in to the main server station as the root user.


8 Perform the following steps to stop the main server application.

i Enter the following to switch to the samadmin user:

# su - samadmin ↵

ii Enter the following to navigate to the server binary directory:


Caution — If the 5620 SAM system uses a firewall, before you add a new component to the system you must ensure that the firewall allows the required traffic to pass. See the 5620 SAM Planning Guide for specific firewall configuration information.

Caution — This procedure requires that you add each new auxiliary server to each 5620 SAM main server configuration and restart each main server, which is service-affecting. Perform this procedure only during a scheduled maintenance period.

Note — After you stop the primary main server in step 8, a server activity switch occurs and Server B begins to manage the network.

If required, you can revert to the previous primary and standby roles of Server A and Server B by performing an activity switch in step 15.





iii Enter the following to stop the main server application:


iv Enter the following to display the main server status:



v The main server is stopped when the command displays the following status message:


If the command displays a different message, wait five minutes and then return to step 8 iv.

Do not proceed to the next step until the server is stopped.


bash$ exit ↵



# cd Linux ↵










13 Perform the following steps to add an auxiliary server to the main server configuration.

i Accept the terms of the license agreement in the “Software License Agreement” panel.

ii Click on the Next button.

iii Choose Main Server Configuration in the “Choose Installation Type” panel.


v Click on the Next button in each successive panel until the “Additional Server Configuration” panel is displayed.

vi Select the “Auxiliary Server Supported” parameter.

vii Click on the Next button in each successive panel until the “Main Server Configuration for Auxiliary Servers” panel is displayed.

viii Configure the following parameters:

• Enable Stats Collection on Auxiliary Servers• Enable Call Trace Collection on Auxiliary Servers

ix Click on the Next button. The “Auxiliary Servers” panel is displayed.

x Click on the Add button. The Auxiliary Server Configuration form opens.






xi Configure the following parameters:

• IP Address• Type (Preferred or Reserved)

xii Click on the OK button. The Auxiliary Server Configuration form closes.

xiii Repeat steps 13 x to xii to add another auxiliary server, if required.

xiv If “Enable Call Trace Collection on Auxiliary Servers” is selected in step 13 viii, click on the “Configure Call Trace Auxiliary Servers” button to open the Configure Call Trace Auxiliary Servers form. Otherwise, go to step 13 xvii.

xv Select a preferred auxiliary server in the upper left panel, optionally select the associated reserved auxiliary server in the lower left panel, and click on the “Make Pair from Selected” button. The auxiliary servers move to the list on the right side of the form.

xvi Repeat step 13 xv to configure another call-trace auxiliary server pair, if required.

xvii Click on the Next button.

xviii Click on the Next button in each successive panel until the “Installation Complete” panel is displayed.

xix Click on the Done button to close the server installer.



Note — When you assign the Preferred and Reserved auxiliary servers for this main server, there are two configurations to consider.






14 Perform the following steps to start the main server application.


# su - samadmin ↵



iii Enter the following to start the main server application:







The main server is completely started when the command returns the one of the following messages:

• For a standalone main server:-- SAM Server is Up

• For a primary main server:-- Primary Server is UP

• For a standby main server:-- Standby Server is UP

v If the command output indicates that the server is not completely started, wait five minutes and then return to step 14 iv.


15 To revert to the previous primary and standby main server roles in a redundant deployment, perform the following steps.

i Log in to Server B as the samadmin user.


iii Enter the following at the CLI prompt to initiate a server activity switch:


The server activity switch begins. Server B restarts as the standby main server. Server A switches roles and manages the network as the primary main server.

iv Log in to Server A as the samadmin user.





v Open a console window.

vi Enter the following to display the main server status:





The main server is completely started when the command returns the following message:


vii If the command output indicates that the server is not completely started, wait five minutes and then return to step 15 vi.


16 If IP validation is enabled for database access, perform the following steps on each database station to enable validation of each auxiliary server.

i Log in to the database station as the Oracle management user.


iii Enter the following to navigate to the Oracle network configuration directory:

bash$ cd /opt/5620sam/oracle12r1/network/admin ↵

iv Create a backup copy of the sqlnet.ora file.

v Open the sqlnet.ora file with a plain-text editor, for example, vi.

vi In the section labeled IP Validation, edit the TCP.VALIDNODE_CHECKING line to read:

TCP.VALIDNODE_CHECKING = yes

vii In the same section, edit the TCP.INVITED_NODES line to read:

TCP.INVITED_NODES = (server,server,...)

where server is the hostname or IP address of an auxiliary server

viii Save the file.

ix Close the file.

Caution — In a redundant 5620 SAM deployment, you must perform this step on the primary database station first, then on the standby database station.




x Enter the following command to stop the Oracle database listener:

bash$ /opt/5620sam/oracle12r1/bin/lsnrctl stop ↵

xi Enter the following command to start the Oracle database listener:

bash$ /opt/5620sam/oracle12r1/bin/lsnrctl start ↵

17 Close the open console windows, as required.





6.8 Cflowd auxiliary server installation

This section describes how to install a 5620 SAM Cflowd auxiliary server in a standalone or redundant 5620 SAM system.

You must do the following to deploy Cflowd auxiliary servers.

• Perform Procedure 6-5 on each Cflowd auxiliary server station to install the Cflowd auxiliary server software.

• If the 5620 SAM system is secured using SSL, perform Procedure 4-7 to enable SSL on each Cflowd auxiliary server.

• Perform Procedure 6-6 on each Cflowd auxiliary server station to enable communication with the main servers and the target file server that is to receive the IPDR files.

See the 5620 SAM Statistics Management Guide for information about how to specify the statistics that the Cflowd auxiliary server is to collect.

See the 5620 SAM System Administrator Guide for information about starting and stopping a Cflowd auxiliary server, enabling and disabling the statistics collection, and other control functions.

Procedure 6-5 To install a 5620 SAM Cflowd auxiliary server

Perform this procedure to install the 5620 SAM Cflowd auxiliary server software on a station. You require root user privileges on the station to perform the procedure.

1 Download the integration package for the 5620 SAM release from the Alcatel-Lucent software repository and copy the package to the Cflowd auxiliary server station.



4 Uncompress the integration package in a local directory.

5 Navigate to the directory that contains the package files.


# gunzip < DcpInstaller_linux64.tar.gz | tar xvf - ↵

The installation files and directories are extracted to the current directory.

Note — Command-line examples use the # symbol to represent the RHEL CLI prompt. Do not type the leading # symbol when you enter a command.

Caution — A 5620 SAM Cflowd auxiliary server requires a dedicated station; you cannot install the Cflowd auxiliary server software on a station if another 5620 SAM component is installed on the station.





# cd linux64/dcp/util ↵

8 Enter the following to verify and configure the system parameters:

# ./checkInstall.sh ↵

The script displays messages like the following:

Executing ./checkInstall.sh. Please check /tmp/checkInstall.log.nnnnn for more details

Check PATH setting...

Check /etc/nsswitch.conf setting...

Check OS version...

Check system info...

Check the minimum required OS packages are installed...

package_1

package_2

package_n

the minimum OS packages are installed...OK

Tune OS kernel parameters...

9 If the script displays a message that begins with ERROR, correct the error described in the message and repeat step 8. Check the log file indicated in the script output about the error, if required.

10 Enter the following to install the software:

# ./runInstaller.sh install ↵

The installer displays the following message:

Start to install 5620 SAM DCP. Please check the log in /var/opt/5620sam/logs/install for status!

The installation is complete when the CLI prompt reappears.

11 Start the Cflowd auxiliary server.


# cd /opt/5620sam/dcp-R_rRn/bin ↵




The server starts, and displays the following messages:





Starting 5620 SAM DCP server......



Procedure 6-6 To configure Cflowd auxiliary server communication

Perform this procedure to configure the parameters for Cflowd auxiliary server communication with the 5620 SAM main servers and the FTP destination.

1 Use a browser to open one of the following:

• if SSL is not enabled:http://server:8080/dcp-admin/admin

• if SSL is enabled:https://server:8443/dcp-admin/admin

where server is the Cflowd auxiliary server IP address or hostname

2 If a login form opens, enter the required user credentials and click OK.

3 The 5620 SAM Cflowd Auxiliary Server form opens. Click on the Collector Configuration link. The Configuration page is displayed.

4 Configure the Collection Port parameter to specify the TCP port that is to receive the statistics data from the NEs.

5 Click Save Configuration. A confirmation page is displayed.

6 Click Configuration View. The Configuration page is displayed.

7 Click on the 5620 SAM Configuration tab. The 5620 SAM Configuration page is displayed.

8 Configure the parameters listed in Table 6-2.

Table 6-2 Cflowd auxiliary server parameters, 5620 SAM Configuration tab

Note — The default user credentials are available from Alcatel-Lucent technical support.

Panel and parameters Description

5620 SAM-O Service

User Name The 5620 SAM username for OSS operations

Password The password of the 5620 SAM OSS user

(1 of 2)




9 Click Save 5620 SAM Configuration. A confirmation page is displayed.

10 Click Configuration View. The Configuration page is displayed.

11 Click on the IPDR Configuration tab. The IPDR Configuration page is displayed.

12 Configure the parameters listed in Table 6-2.

Table 6-3 Cflowd auxiliary server parameters, IPDR Configuration tab

Use Secure HTTP (HTTPS) Specifies whether HTTPS is used

Redundant Specifies whether the 5620 SAM system is a redundant deployment

Reconnect Specifies whether the Cflowd auxiliary server attempts to reconnect to the 5620 SAM after a connection failure

Durable Specifies whether the 5620 SAM JMS subscription is durable

Reconnect Attempts The number of times to attempt to reconnect to the 5620 SAM after a connection failure

Reconnect Delay The time, in seconds, to wait between 5620 SAM reconnection attempts

Connection Timeout The time, in seconds, to wait for a response to a 5620 SAM connection attempt

Transfer Option The method to use for file transfers from a 5620 SAM main server

5620 SAM Primary

5620 SAM Standby (required for redundant system)

IP Address/Host name The public IP address or hostname of the main server

HTTP Port The TCP port on the main server for non-secured OSS communication

HTTPS Port The TCP port on the main server for SSL-secured OSS communication

JNDI Port The TCP port on the main server for JMS communication

SFTP Port The TCP port on the main server for file transfers, if SSL is enabled

SFTP User Name The username required for SSL-secured file transfers from the main server

SFTP Password The password required for SSL-secured file transfers from the main server

FTP Port The TCP port on the main server for file transfers, if SSL is not enabled

FTP User Name The username required for non-secured file transfers from the main server

FTP Password The password required for non-secured file transfers from the main server


(2 of 2)


Enable Transfer Specifies whether IPDR file transfers to the target file server are enabled

Transfer Protocol Specifies the file-transfer protocol for IPDR transfers to the target file server

IP Address / Host name The IP address or hostname of the target file server

Port The TCP port that the target file server uses to receive IPDR file transfers

Location A descriptive entry that uniquely identifies the location of the target file server

User The username required for IPDR file transfers to the target file server

Password The username required for IPDR file transfers to the target file server





13 Click Save Configuration. A confirmation page is displayed.

14 Close the browser window.




6.9 Auxiliary database installation

This section describes how to install the 5620 SAM auxiliary database software and enable an auxiliary database in a 5620 SAM system.

An auxiliary database is distributed among multiple stations. To deploy an auxiliary database, you must do the following:

• Perform Procedure 6-7 on each auxiliary database station to install the auxiliary database software.

• Perform Procedure 6-8 to enable the auxiliary database in the 5620 SAM system, after which a data migration to the auxiliary database may occur.

Procedure 6-7 To install a 5620 SAM auxiliary database

Perform this procedure to install and initialize the 5620 SAM auxiliary database software. You require root user privileges on each auxiliary database station to perform the procedure.

1 Perform the following steps on each auxiliary database station.

i Log in to the auxiliary database station as the root user.


iii Navigate to the directory that contains the auxiliary database software.

iv Enter the following:

# ./VerticaSw_PreInstall.sh ↵








Note — Command lines use the # symbol to represent the RHEL CLI prompt for the root user: Do not type the leading # symbol when you enter a command.

Caution — Each auxiliary database in a 5620 SAM auxiliary database cluster requires a dedicated station; you cannot install the auxiliary database software on a station if another 5620 SAM component is installed on the station.





Checking Vertica DBA group samauxdb...

Adding Vertica DBA group samauxdb...

Checking Vertica user samauxdb...

Adding Vertica user samauxdb...

Changing ownership of the directory /opt/5620sam/samauxdb to samauxdb:samauxdb.

Adding samauxdb to sudoers file.

Changing ownership of /opt/5620sam/auxdb files.

INFO: About to add setting to /etc/rc.d/rc.local...

INFO: Completed adding setting to /etc/rc.d/rc.local...

v If the script instructs you to restart the station, enter the following; otherwise, go to step 1 ix:

# init 6 ↵

The station restarts.

vi When the station is restarted, log in to the station as the root user.

vii Open a console window.

viii Navigate to the directory that contains the auxiliary database software.

ix Enter the following commands in sequence:

# yum install samjre-SAM_R_r_revision-Pp.x86_64.rpm ↵

# yum install vertica-V.w.x-y.x86_64.RHEL5.rpm ↵

# yum install samauxdb-SAM_R_r_revision-Pp.x86_64.rpm ↵

whereR_r is the 5620 SAM release identifier, in the form MAJOR_minorrevision is the 5620 SAM revision identifier, such as R1, R3, or another descriptorp is the patch levelV.w.x-y is a version number

x Close the console window.

2 Log in to any auxiliary database station as the root user.



# cp /opt/5620sam/samauxdb/config/install.config.default /opt/5620sam/samauxdb/config/install.config ↵

5 Open the following file using a plain-text editor such as vi:

/opt/5620sam/samauxdb/config/install.config

6 Edit the following lines in the file to read:




hosts=internal_IP1,internal_IP2,internal_IP3

subnet=subnet_address

export_hosts=internal_IP1[export_IP1],internal_IP2[export_IP2],internal_IP3[export_IP3]

whereinternal_IP1, internal_IP2, and internal_IP3 are the IP addresses that the stations use to communicate with each otherexport_IP1, export_IP2, and export_IP3 are the IP addresses that the stations use to communicate with 5620 SAM serverssubnet_address is the address of the subnet that the stations use for external communication

The following is an export_hosts configuration example:

export_hosts=10.1.1.10[198.51.100.10],10.1.1.11[198.51.100.11],10.1.1.12[198.51.100.12]

7 Save and close the file.


# cd /opt/5620sam/samauxdb/bin ↵


# ./auxdbAdmin.sh install ↵

10 The script sequentially attempts to configure each station. When the script prompts for the root password of a station, enter the password. The script performs installation operations on the station.

11 When the script execution is complete, reboot each auxiliary database station to activate the auxiliary database software.

12 When all auxiliary database stations are restarted, log in to a station as the root user.


14 Enter the following to start the auxiliary database software:

# /opt/5620sam/samauxdb/bin/auxdbAdmin.sh start ↵

15 Press ↵ when the script prompts you for a password.

16 Enter the following to display the auxiliary database status:

# /opt/5620sam/samauxdb/bin/auxdbAdmin.sh describe ↵

The script output includes the following:

Database status

Note — If the [export_IP] entry for a station is omitted, the station uses the internal_IP address for communication with the 5620 SAM servers.





DB | Host | State

-------+--------------+-------

samdb | internal_IP1 | STATE



17 Repeat step 16, as required, until the STATE of each DB entry is UP, which indicates that the auxiliary database is operational.

Procedure 6-8 To enable an auxiliary database in a 5620 SAM system

Perform this procedure to specify the stations in an auxiliary database, and to enable the auxiliary database in a 5620 SAM system, after which a data migration may occur.

1 Log in to the main server station as the samadmin user.


3 Enter the following to navigate to the server configuration directory:

bash$ cd /opt/5620sam/server/nms/config ↵

4 Enter the following to make a backup copy of the server configuration file:

bash$ cp nms-server.xml nms-server.xml.backup ↵

5 Open the nms-server.xml file with a plain-text editor, for example, vi.

6 Edit the following section to read:

Caution — This procedure requires a restart of each main server, which is service-affecting. Perform this procedure only during a scheduled maintenance period.

Note 1 — You must perform this procedure on each main server in the 5620 SAM system.

In a redundant 5620 SAM system, you must perform the procedure on the standby main server first.

Note 2 — After you enable a new auxiliary database:

• The existing AA statistics data automatically migrates from the 5620 SAM database to the auxiliary database.

• No accounting or performance statistics migrate, and the existing statistics are no longer retrievable from the 5620 SAM database.

Note 3 — The first performance statistics collection after the data migration does not include periodic counter values.




<samauxdb

enabled="true"

ipaddress="IP_address_1,IP_address_2,IP_address_3" />

where IP_address_1, IP_address_2, and IP_address_3 are one of the following:—the export_IP addresses configured in step 6 of Procedure 6-7—the internal_IP addresses, if no export_IP addresses are configured

7 Save and close the file.

8 Perform the following steps to stop the main server.

i Enter the following to navigate to the server binary directory:




iii Enter the following to display the main server status:



iv The main server is stopped when the command displays the following:


If the command displays a different message, wait five minutes and then return to step 8 iii.


9 Enter the following to start the main server:

bash$ /opt/5620sam/server/nms/bin/nmsserver.bash start ↵

The main server creates the required database elements and begins the migration of statistics data, if any, to the auxiliary database.

10 When a statistics migration fails for any auxiliary database station, the migration is re-attempted. If the migration does not succeed after 10 attempts, the main server shuts down and displays the following message:

Failed to migrate Application Assurance statistics from main database to auxiliary database





In such a scenario, you must do the following:

i Restore the 5620 SAM database.

ii Resolve the cause of the migration failure.

iii Restart the main server.





6.10 Analytics server installation

This section describes how to install and configure a 5620 SAM analytics server in a standalone or redundant 5620 SAM system.

Procedure 6-9 To install and enable a 5620 SAM analytics server

Perform this procedure to install the 5620 SAM analytics server software on a station. You require root and samadmin user privileges on the station to perform the procedure.

Install analytics server

1 Log in as the root user on the station that is to be the analytics server.


3 Navigate to the directory that contains the following installation package files:

• tomcat-SAM_R_r_revision-Pp.x86_64.rpm• samanalytics-R_r_revision-Pp.x86_.rpm

whereR_r is the 5620 SAM release identifier, in the form MAJOR_minor

revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptorp is the patch level

Note — You can install a 5620 SAM analytics server only in a 5620 SAM system that includes an operational auxiliary database. See section 6.9 for auxiliary database installation information.

Caution — A 5620 SAM analytics server requires a dedicated station; you cannot install the analytics server software on a station if another 5620 SAM component is installed on the station.

Note 1 — The samadmin user account is created automatically during the installation.

Note 2 — Command lines in the procedure use the following to represent the RHEL CLI prompts:

• #—root user prompt• bash$—samadmin user prompt

Do not type the leading # symbol or bash$ when you enter a command.





4 Enter the following commands in sequence:

# rpm -ivh tomcat-SAM_R_r_revision-Pp.x86_64.rpm ↵

# rpm -ivh samanalytics-R_r_revision-Pp.x86_.rpm ↵


# su - samadmin ↵

6 If you are deploying the analytics server in a redundant 5620 SAM system, perform the following steps.

i Obtain the instance name of the current primary database, which is shown in the Primary Database panel of the Database Manager form in the client GUI.

ii If the instance name is samdb, go to step 7.

iii If the instance name is something other than samdb, for example, samdb1 or samdb2, open the following file using a plain-text editor such as vi:

/opt/5620sam/analytics/config/install.config

iv Locate the section that begins with the following tag:

#Oracle DB (Repo and JNDI) details

v Edit the following line in the section to read:

dbName=instance_name

where instance_name is the database instance name obtained in step 6 i.

vi Save and close the file.


bash$ cd /opt/5620sam/analytics/bin ↵

8 Enter the following to configure the 5620 SAM analytics server:

bash$ ./AnalyticsAdmin.sh updateConfig ↵

The script displays the following messages and prompt:

Copyright (c) 2000-20XX Alcatel-Lucent. All rights reserved

THIS ACTION UPDATES /opt/5620sam/analytics/config/install.config

Please type 'YES' to continue

9 Enter YES ↵. The following message is displayed.

/opt/5620sam/analytics/config/install.config found.

Note — If a package has dependencies on one or more additional packages, the rpm utility installs the packages.




10 You are sequentially prompted to configure the parameters listed in Table 6-4. If available, a default value is shown in brackets in each prompt.

At each prompt, type a parameter value and press ↵, or press ↵ to accept the default.

Table 6-4 5620 SAM analytics server installation parameters


bash$ ./AnalyticsAdmin.sh install ↵

The 5620 SAM analytics server software is installed.


Enable 5620 SAM analytics server

13 Perform the following steps on each main server in the 5620 SAM system.

i Log in to the main server as the samadmin user.


iii Open the following file using a plain-text editor such as vi:

/opt/5620sam/server/nms/web/tomcat/conf/ nmswebserver.xml

iv Locate the section that begins with the following tag:

<analyticsWebapp

v Edit the following line in the section to read:

Parameter Description

Repository Database HOST IP Address The 5620 SAM database IP address

Repository Database Port The TCP port on the 5620 SAM database station that receives database requests

Auxiliary DB Host for JNDI Connection The auxiliary database IP address

Auxiliary DB Port for JNDI Connection The auxiliary database TCP port that receives database requests

Note — The 5620 SAM analytics server starts automatically after the installation.





serverIp="IP_address">

where IP_address is the IP address of the 5620 SAM analytics server

vi Save and close the file.

14 Perform the following steps to restart the currently active 5620 SAM web server.

i Log in as the samadmin user on the appropriate main server, which is one of the following:

• the main server in a standalone 5620 SAM system• the primary main server in a redundant 5620 SAM system


bash$ /opt/5620sam/server/nms/bin/nmsserver.bash webforce_restart ↵

The web server restarts, and the analytics server is enabled.

iii Close the console window.




7.1 Overview 7-2

7.2 5620 SAM upgrade procedures list 7-2

7.3 5620 SAM system upgrade preparation 7-3

7.4 Standalone system upgrade workflow 7-12

7.5 Standalone system upgrade 7-13

7.6 Redundant system upgrade workflow 7-56

7.7 Redundant system upgrade 7-60

7.8 Auxiliary server upgrade 7-166

7.9 Cflowd auxiliary server upgrade 7-181





7.1 Overview

Before you attempt to perform a procedure in this chapter, ensure that you understand and comply with the relevant requirements, considerations, and precautions described in chapter 1 of this guide.

See Appendix B for detailed 5620 SAM upgrade parameter descriptions.

7.2 5620 SAM upgrade procedures list

Table 7-1 lists the 5620 SAM software upgrade procedures.

Table 7-1 5620 SAM upgrade procedures list

Caution 1 — An upgrade of a 5620 SAM system in a network requires that you thoroughly understand the general and OS-specific requirements of the task. It is essential that you plan, document, and test the upgrade procedure in advance on a lab system that is representative of the target live network.

Contact Alcatel-Lucent technical support to assess the upgrade requirements for your network implementation of the 5620 SAM. Alcatel-Lucent offers an upgrade service and strongly recommends that it be engaged for upgrades in larger or more complex networks.

Caution 2 — Alcatel-Lucent supports 5620 SAM software configuration only under the conditions described in chapter 1.

Note — The upgrade of a 5620 SAM main server that is integrated with a collocated 5650 CPAM server requires additional time if the existing 5650 CPAM checkpoints are retained. The additional time varies, depending on the platform resources, managed network size, and checkpoint schedule. To minimize the upgrade time, you must remove the 5650 CPAM checkpoints before the upgrade,

Procedure Purpose

To perform the pre-upgrade tasks Prepare a standalone or redundant 5620 SAM system for a software upgrade by ensuring the correct conditions are in place, gathering the required system information, and backing up the configuration files and database.

To upgrade a standalone 5620 SAM system Upgrade the 5620 SAM database and server software in a standalone configuration on one or more stations.

To upgrade a redundant 5620 SAM system Upgrade the 5620 SAM database and server software in a redundant deployment.

To upgrade a 5620 SAM auxiliary server Upgrade the auxiliary server software on a station in a standalone or redundant 5620 SAM system.

(1 of 2)




7.3 5620 SAM system upgrade preparation

This section describes how to prepare for the upgrade of a standalone or redundant 5620 SAM system.

Before you attempt a 5620 SAM system upgrade, you must perform Procedure 7-1 to collect the required information and ensure that the proper upgrade conditions are in place.

Procedure 7-1 To perform the pre-upgrade tasks

Perform this procedure to prepare a standalone or redundant 5620 SAM system for a 5620 SAM software upgrade.


• on each main server station• root


Check firewall configuration

1 If you plan to deploy a RHEL iptables or ip6tables firewall for the first time in the 5620 SAM system, ensure that the iptables and ip6tables firewall is disabled. You must enable and configure the iptables and ip6tables firewall only when the upgrade is complete.

To upgrade a 5620 SAM Cflowd auxiliary server Upgrade the Cflowd auxiliary server software on a station in a standalone or redundant 5620 SAM system.

Procedure Purpose

(2 of 2)

Note — Command-line examples use the following to represent the RHEL CLI prompts:


management users


Warning — A 5620 SAM system upgrade from a release earlier than 12.0 R5 has special requirements. To ensure the upgrade success, you must prepare for the upgrade as directed in section 1.2.





Clear failed deployments

2 Clear all outstanding failed deployments; see the “To view and manage failed deployments” procedure in the 5620 SAM User Guide for information about how to clear a failed deployment.

Verify database archive log synchronization

3 If the 5620 SAM system is deployed in a redundant configuration, perform the following steps to ensure that no database archive log gap exists between the primary and standby databases. Otherwise, go to step 4.

i View the Standby DB entry in the client GUI status bar.

ii If the entry displays “Database archive log gap”, perform the following steps to reinstantiate the standby database. Otherwise, go to step 4.

iii Log in to a 5620 SAM client as the admin user.

iv Choose Administration→System Information from the 5620 SAM main menu. The System Information form opens with the General tab displayed.

v Click on the Re-Instantiate Standby button. A dialog box appears.

vi Click on the Yes button. The database reinstantiation begins.

You can view the reinstantiation status on the client GUI status bar or on the System Information form. The Standby Re-instantiation State changes from In Progress to Success when reinstantiation is complete. The start time of the reinstantiation is shown by the Last Attempted Standby Re-instantiation Time indicator.

vii When the reinstantiation is complete, close the System Information form.

Note — If you attempt a database upgrade when an archive log gap exists, the upgrade fails.

Note — Database reinstantiation can take a long time when there is a large amount of statistics data to transfer.




Back up database

4 Alcatel-Lucent strongly recommends that you perform a database backup using one of the following methods before you upgrade the 5620 SAM database.

Perform one of the following.

a Use the 5620 SAM client GUI. See the “5620 SAM database management” chapter of the 5620 SAM System Administrator Guide for information about performing a database backup using the client GUI.

b Use a CLI script. Perform the following steps.

i Log in to the appropriate station as the Oracle management user.

• the standalone database station in a standalone 5620 SAM system• the primary database station in a redundant 5620 SAM system


iii Enter the following to begin the database backup:

bash$ /opt/5620sam/samdb/install/config/samdb/SAMbackup.sh backup_directory ↵

where backup_directory is the directory that is to contain the database backup

The 5620 SAM backs up the database.

iv Record the backup_directory location.

v Copy the file set from backup_directory to a secure and physically separate location for safekeeping.

Verify external-system compatibility

5 Ensure that the new 5620 SAM software is compatible with the software release level of each external system that connects to the 5620 SAM system. Contact Alcatel-Lucent technical support for information about 5620 SAM compatibility with an external system.

Close the LogViewer

6 Close the LogViewer application, if it is open.

Caution 1 — The path of the 5620 SAM database backup directory must not include the 5620 SAM database installation directory, /opt/5620sam/samdb, or data loss may occur.

Caution 2 — Before the 5620 SAM performs a database backup, it deletes the contents of the specified backup directory. Ensure that the backup directory that you specify in this step does not contain files that you want to retain.





Open port for client/server communication

7 Confirm that the firewalls between the 5620 SAM main server and client allow traffic to the HTTP or HTTPS port used for performing automatic client updates. Otherwise, you cannot perform a client installation or upgrade. By default, the auto-update utility uses HTTP. See chapter 4 for information about configuring 5620 SAM clients and servers to communicate using HTTP or HTTPS.

Verify managed-device and 5620 SAM policy compatibility

8 Confirm that the new 5620 SAM software release supports the software release of each 5620 SAM-managed device, including pre-provisioned NEs.

Perform one of the following for each unsupported device before you attempt the upgrade, or a service disruption may occur. See the 5620 SAM Network Element Compatibility Guide for information about managed-device release and 5620 SAM release compatibility.

a Upgrade the device to a software release that the new 5620 SAM software supports; see the appropriate device documentation for information about device software upgrades.

b Remove the device from the 5620 SAM managed network; see the “Device discovery” chapter of the 5620 SAM User Guide for information about performing the following steps.

i Use a 5620 SAM client to unmanage the device.

ii When the device is unmanaged, use the 5620 SAM client to remove the device from the 5620 SAM network.

iii Use the 5620 SAM client to administratively disable or remove the discovery rule element for the device.

c Delete the pre-provisioned NE from the 5620 SAM Pre-Provisioned NE Manager; see the “Self-configuration and discovery” chapter of the 5620 SAM LTE RAN User Guide.

Note — If a 5620 SAM system that is to be upgraded manages a device as a GNE, and the new 5620 SAM release supports native management of the device, you must unmanage the device and delete it from the 5620 SAM database before the upgrade.

After the upgrade, you can use the 5620 SAM to discover and manage the device natively, rather than as a GNE.




Back up configuration files

9 Make a backup copy of each file that you have created or customized in or under the /opt/5620sam/server/nms and /opt/5620sam/server/jre directories on each main server station.

Store the files in a secure location that is unaffected by 5620 SAM upgrade activity.

Caution — A 5620 SAM upgrade does not preserve non-default settings in configuration files such as nms-server.xml. If a 5620 SAM configuration file contains non-default settings that you want to retain after an upgrade, contact Alcatel-Lucent technical support for assistance before the upgrade.

Note — At the beginning of a 5620 SAM server upgrade, the 5620 SAM installation utility backs up specific configuration and log files to a timestamped directory under the installation directory. The utility then deletes directories under the main server installation directory. If you have created or customized a file under this directory, you risk losing the file unless you back up the file before the upgrade to a storage location that is unaffected by the upgrade.





10 If the 5620 SAM system currently manages Small Cell NEs, perform one of the following to back up the Small Cell files.

a If you are upgrading from Release 12.0 R5 or R6, perform the following steps.

i Log in to the main or auxiliary server station as the root user.

ii Create the /smallcell/config directory.

iii Copy the following files to the /smallcell/config directory:

• /opt/5620sam/server/nms/config/nms-femto.xml• /opt/5620sam/server/nms/config/femto/fsconf/config/nms-femto.x

ml.backup• /opt/5620sam/server/nms/config/femto/fsconf/config/sshd_config.

backup

b If you are upgrading from Release 12.0 R7 or later, perform the following steps.

i Log in to the main or auxiliary server station as the samadmin user.


iii Enter the following command:

bash$ /opt/5620sam/nms/server/config/femto/fsconf/fsBackup.sh all path

where path is the directory that is to contain the backup files, and is optional; the default is /smallcell/backup

Gather required information

11 Perform the following steps to obtain the basic system information.

i Open a 5620 SAM client.

ii Choose Administration→System Information from the 5620 SAM main menu. The System Information window is displayed.

Note — You must back up the files on each main or auxiliary server that has a Small Cell configuration.

Note — path must not include a trailing slash character (/).




iii Record the following information for use during the upgrade:

• Domain Name• In the Primary Server panel:

• IP Address• Host Name• Status

• In the Primary Database Server panel:• Database Name• Instance Name• IP Address• Host Name

iv If the 5620 SAM system is deployed in a redundant configuration, record the following information for use during the upgrade:

• In the Standby Server panel:• IP Address• Host Name• Status

• In the Standby Database Server panel:• Database Name• Instance Name• IP Address• Host Name

12 If the 5620 SAM system includes one or more auxiliary servers, click on the Auxiliary Services tab. A list of auxiliary servers is displayed. Otherwise, go to step 15.

13 Perform the following steps for each auxiliary server listed on the form:

i Select the auxiliary server and click on the Properties button. The auxiliary server properties form opens.

ii Record the following information for use during the upgrade:

• Host Name• Auxiliary Server Type• Server Status• Public IP address• Private IP address, if displayed

iii Close the auxiliary server properties form.

14 Record which auxiliary servers have a check mark in the Selected column.

Note — The Selected auxiliary servers are collectively referred to as [Aux1] during a redundant upgrade, and the other auxiliary servers are collectively referred to as [Aux2].





15 If the 5620 SAM system includes one or more client delegate servers, click on the Client Delegate Servers tab. Otherwise, go to step 17.

16 Perform the following steps for each client delegate server listed on the form:

i Select a client delegate server in the list and click on the Properties button. The properties form for the client delegate server opens.

ii Record the IP Address value for use during the upgrade.

iii Close the client delegate server properties form.

17 Close the System Information form.

18 Obtain the following additional information for each main server station in the 5620 SAM system and record it for use during the upgrade:

• additional IP addresses, if NAT or multiple interfaces are used:• IP address that each 5620 SAM database uses to reach the main server• IP address that the 5620 SAM GUI and OSS clients use to reach the main server

(public IP address, if NAT is used)• IP address that the auxiliary servers use to reach the main server• private IP address of the main server (if NAT is used)

• root user password

19 Obtain the following additional information for each database station in the 5620 SAM system and record it for use during the upgrade:

• additional IP addresses, if NAT or multiple interfaces are used:• IP address that each main server uses to reach the database• IP address that the auxiliary servers use to reach the database

• root user password• Oracle management user information:

• username (default at installation is oracle)• group name (default at installation is dba)

• Oracle database user ID (default at installation is samuser)• Oracle database user password• Oracle SYS password

Close client sessions

20 Close all unrequired open 5620 SAM client sessions.

i Open a 5620 SAM client session using an account with security management privileges, such as admin.

ii Click on Administration→Security→5620 SAM User Security in the 5620 SAM main menu. The 5620 SAM User Security - Security Management (Edit) form opens with the General tab displayed.

iii Click on the Sessions tab.

iv Click on the Search button. The form displays a list of the open 5620 SAM client sessions.




v Using the IP addresses in the Client IP column, identify the GUI and OSS clients that are currently logged in.

vi Close the client sessions by selecting them and clicking on the Close Session button. A dialog box appears.

• If you are performing a standalone upgrade, you must close all open 5620 SAM client sessions.

• If you are performing a redundant upgrade, you must close all open 5620 SAM client sessions except for those required to monitor the network during the upgrade.

vii Click on the Yes button to confirm the action.

viii Click on the Search button to refresh the list of open client sessions.

21 If the 5620 SAM client that you are using is not required for network monitoring during the upgrade, close the client by choosing Application→Exit from the 5620 SAM main menu.

Note — One of the listed sessions is the session that you are using. Do not attempt to close this session.





7.4 Standalone system upgrade workflow

The following is the sequence of high-level actions required to upgrade a standalone 5620 SAM system. A reference in quotation marks is a link to a section in Procedure 7-2.

1 Perform the pre-upgrade tasks; see Procedure 7-1.

2 If the 5620 SAM system includes one or more Cflowd auxiliary servers, stop each Cflowd auxiliary server; see “Stop Cflowd auxiliary servers”.

3 Stop the main server; see “Stop main server”.

4 Disable the main server startup daemon; see “Disable main server daemon”.

5 Ensure that sufficient inodes are available for the upgrade on the main server; see “Check main server file system”.

6 Stop the 5620 SAM database; see “Stop 5620 SAM database”.

7 Run a script to prepare the database station for the upgrade; see “Run upgrade preparation script”.

8 Upgrade the database; see “Upgrade standalone 5620 SAM database”.

9 If the 5620 SAM system includes one or more auxiliary servers, upgrade each auxiliary server; see “Upgrade auxiliary servers”.

10 Upgrade the main server; see “Upgrade main server”.

11 If the 5620 SAM system includes one or more Cflowd auxiliary servers, upgrade each Cflowd auxiliary server; see “Upgrade Cflowd auxiliary servers”.

12 Upgrade or install the 5620 SAM client software, as required; see “Upgrade or install 5620 SAM client”.




7.5 Standalone system upgrade

This section describes how to upgrade the software components of a standalone 5620 SAM system. Procedure 7-2 describes how to upgrade the 5620 SAM database and main server software.

Before you begin a 5620 SAM system upgrade, you must collect the required information and ensure that the proper conditions are in place, as described in Procedure 7-1.

Procedure 7-2 To upgrade a standalone 5620 SAM system

Perform this procedure to upgrade the 5620 SAM database and main server software in a standalone deployment on one or more stations. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses.


• on the main server station:• root• samadmin


1 Open at least one GUI client to monitor the network before and after the upgrade.



management users






Caution — If you plan to implement the RHEL iptables and ip6tables firewall as part of the system upgrade, you must ensure that the iptables and ip6tables firewall on each station is disabled before the upgrade.





Stop Cflowd auxiliary servers

2 If the 5620 SAM system includes one or more Cflowd auxiliary servers, stop each Cflowd auxiliary server.

i Log on to the Cflowd auxiliary server as the root user.



# /opt/5620sam/dcp-R_rRn/bin/dcpctl.sh stop ↵


The following messages are displayed.



Stop main server






iv Enter the following to stop the main server application:


v Enter the following to display the main server status:



vi The main server is stopped when the command displays the following status message:


If the command displays a different message, wait five minutes and return to step 3 v. Do not proceed to the next step until the server is stopped.




Disable main server daemon

4 Perform the following steps on the main server station to disable the main server startup daemon. This ensures that the main server does not start in the event of an accident during the upgrade.

i Enter the following to switch to the root user:

bash$ su - ↵


# cd /etc/init.d ↵

iii Enter the following to disable the main server startup daemon:

# mv 5620SAMServerWrapper inactive.5620SAMServerWrapper ↵

Check main server file system

5 If the 5620 SAM system manages more than 3000 NEs, perform the following steps on the main server to ensure that sufficient inodes are available for the upgrade.


# df -i /opt/5620sam/server/nms/bin/depl/mediation ↵

The command returns output similar to the following:

Filesystem Inodes IUsed IFree IUse% Mounted on

/dev/sda2 3842048 65297 3776751 2% /opt/5620sam

ii If the “IUse%” value is greater than 40%, enter the following command to remove the mediation files:

# rm -r /opt/5620sam/server/nms/bin/depl/mediation ↵

Stop 5620 SAM database

6 Perform the following steps to stop the 5620 SAM database.

i Log in to the database station as the root user.



# cd /etc/rc3.d ↵

Note — The command may take several minutes to complete, depending on the number of files in the mediation directory.





iv Enter the following to stop the Oracle proxy daemon:

# ./S965620SAMOracleProxyWrapper stop ↵

v Enter the following to stop the 5620 SAM database daemon:

# ./S95db5620sam stop ↵

Do not proceed until the command displays the following message:

Done

Run upgrade preparation script

7 You must run a script that configures the Oracle management user account.



# cd Linux ↵







3) EXIT


11 Enter 2 ↵.



Caution — Ensure that you run the script included with the new 5620 SAM software. Using a different version of the script may cause the database upgrade to fail.

Note — If you later back out of the database upgrade and want to re-install the previous database, you must do the following before you attempt to re-install the previous database:

• run the current version of the script and specify the remove_project command-line option

• run the previous version of the script and choose option 1• reboot the station





Checking user username... usermod: no changes




passwd: Success



Do you want to change the password for the UNIX user username? [Yes/No]:


a Retain the existing password. Enter No ↵.

b Specify a new password. Perform the following steps.

i Enter Yes ↵. The following prompt is displayed:

New Password:

ii Type the password and press ↵. The following prompt is displayed:


iii Retype the password and press ↵. The following message is displayed if the password update is successful:


13 The following prompt is displayed:




Enter Yes or No, as required, and press ↵. The following messages are displayed, and the script execution is complete.

INFO: About to remove kernel parameters set by a previous run of this script from /etc/sysctl.conf

INFO: Completed removing kernel parameters set by a previous run of this script from /etc/sysctl.conf









INFO: About to remove ulimit parameters set by a previous run of this script from /etc/security/limits.conf

INFO: Completed removing ulimit parameters set by a previous run of this script from /etc/security/limits.conf

INFO: About to set ulimit parameters in etc/security/limits.conf...




# init 6 ↵


The next section of the procedure describes the standalone 5620 SAM database upgrade.

Upgrade standalone 5620 SAM database

15 After the database station reboots, log in to the database station as the root user.


17 Enter the following to stop the Oracle proxy daemon:

# /etc/rc3.d/S965620SAMOracleProxyWrapper stop ↵

18 Enter the following to switch to the Oracle management user:





bash$ cd Linux ↵










22 The 5620 SAM database installer opens, as shown in Figure 7-2. The left pane indicates upgrade progress. The right pane displays release information about the software. Click on the Next button.








24 Select Upgrade a Database, as shown in Figure 7-4. Click on the Next button.





The installer prepares to upgrade the database, as shown in Figure 7-5.






25 If the panel in Figure 7-6 is displayed, perform the following steps. Otherwise, go to step 29.























28 When the panel in Figure 7-9 is displayed, perform the following steps.














29 If the panel in Figure 7-10 is displayed, perform the following steps.

Figure 7-10 Patch Oracle Database Management Software

i Click on the “Start Oracle Patch Installation” button to begin installing the Oracle patch. Oracle patch installation can take an hour or more to complete.

ii Oracle patch installation details are displayed as the patch installation progresses. When the patch installation is complete, as shown in Figure 7-11, click on the Next button.






30 Perform the following steps if the panel shown in Figure 7-12 is displayed.

i Specify the location of the currently installed Oracle software. The information may be required if the upgrade is to be rolled back.

ii Configure the “Keep Old Oracle Directory Contents after Upgrade” parameter.

iii Click on the Next button.

Figure 7-12 Locate Old Oracle Software Directory

Note — If the parameter is not selected, the 5620 SAM database installer removes the directory during the upgrade, and the Oracle software must be reinstalled in the event of an upgrade rollback.




31 Configure the following parameters shown in Figure 7-13 using information from the existing 5620 SAM installation, then click on the Next button:

• Public IP (accessible to servers)• Instance Name• Database User Password

Figure 7-13 Get Upgrade Database Info






If the “Enable 5620 SAM Server IP Validation” parameter is selected, only the server at the specified IP address or hostname can connect to the database.

• Enable 5620 SAM Server IP Validation• Server IP Address





33 The panel in Figure 7-15 is displayed if the “Enable 5620 SAM Server IP Validation” parameter in step 32 is selected. Otherwise, go to step 34.


















36 The panel shown in Figure 7-18 allows you to purge the current 5620 SAM statistics data before the upgrade.

Configure the following parameters, then click on the Next button:

• Purge All Accounting Statistics• Purge All MIB Statistics

Figure 7-18 Purge Statistics

Caution — Purging the statistics data may reduce or increase the upgrade duration, depending on the 5620 SAM release and the database contents. Staging an upgrade in advance of a live upgrade can determine how a statistics purge affects the upgrade duration.

Note — The statistics data for the specified statistics types are permanently deleted from the 5620 SAM database.





37 If you are prompted to run an Oracle patch pre-installation script, as shown in Figure 7-19, run the script in a separate console window as the root user.

Figure 7-19 Oracle Patch Pre-Install Script

38 When the script execution is complete, click on the Next button.

39 You are prompted to begin the database upgrade, as shown in Figure 7-20. A database upgrade can take one hour or more, depending on the tablespace configuration. Click on the Start Process button to begin the database upgrade.

Figure 7-20 Database Upgrade




The next panel displays upgrade progress, as shown in Figure 7-21.

Figure 7-21 Oracle Database Upgrade

40 When the panel in Figure 7-22 is displayed, the 5620 SAM database upgrade is complete, but as shown in the panel text, you must run a script to enable automatic database startup.













For information about how to limit the number of database user login failures, see the “5620 SAM database management procedures” section in the 5620 SAM System Administrator Guide.


bash$ exit ↵

Upgrade auxiliary servers

44 If the 5620 SAM system includes one or more auxiliary servers, upgrade each auxiliary server by performing Procedure 7-4.

Upgrade main server

45 Log into the main server station as the root user.


47 Perform the following steps to ensure that no-one is logged in to the station as the samadmin user.


# who ↵

The active user sessions are listed.

ii If the samadmin user is listed, close each samadmin user session. See the OS documentation for information about closing user sessions.


Note — You do not need to perform this step if the database has been previously configured to limit the database user login failures.





# cd Linux ↵











51 The 5620 SAM server installer opens, as shown in Figure 7-24. The left pane indicates upgrade progress. The right pane displays release information about the software. Click on the Next button.









54 As shown in Figure 7-27, the installer indicates which release of 5620 SAM software is currently installed and the release to which it is to be upgraded. Verify the information. Click on the Next button.







The default is the current license file; the parameter field displays “Use current license file”.


Note 1 — If you are upgrading from one major release to another, for example, from Release 12.0 to Release 13.0, and do not yet have a new license file, you must clear the parameter field before you continue.

Note 2 — If you are upgrading within the same major release, for example, from Release 13.0 R1 to a later 13.0 release, the default is the current license file. Configure the parameter only if you have a new license file.












57 Configure the following parameters, shown in Figure 7-30, using the recorded values from the database upgrade, then click on the Next button.






58 Depending on the existing configuration. the panel in Figure 7-31 is displayed. Configure the following parameters, if required, then click on the Next button:










Perform the following steps:

i Configure the parameters:






ii Click on the Next button. The panel shown in Figure 7-33 is displayed.


iii Click on the Add button. The form shown in Figure 7-34 opens.


iv Configure the parameters:


v Click on the OK button to save the information and close the form.






vi Repeat steps 59 iii to v to specify an additional auxiliary server, if required.

vii If “Enable Call Trace Collection on Auxiliary Servers” is selected in step 59 i, click on the “Configure Call Trace Auxiliary Servers” button shown in Figure 7-33. Otherwise, go to step 60.

viii The form shown in Figure 7-35 opens. Select a preferred auxiliary server in the upper left panel, optionally select the associated reserved auxiliary server in the lower left panel, and click on the “Make Pair from Selected” button. The auxiliary servers move to the list on the right side of the form.


ix Repeat step 59 viii to configure another call-trace auxiliary server pair, if required.




































• IP Address


















65 If the 5620 SAM system includes a 5650 CPAM server, select the check box shown in Figure 7-41 and configure the License File parameter using the absolute file path of the 5650 CPAM license zip file. Click on the Next button.





















68 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 7-44. Click on the Install button to begin the server upgrade.













70 When the main server upgrade is complete, as shown in Figure 7-47, configure the “Start the 5620 SAM Main Server” parameter to specify whether you want the server to start immediately after the upgrade.


71 Click on the Done button to close the server installer. If you specified that the main server is to start after the upgrade, the server starts.

Caution 1 — If you are upgrading from a release earlier than 12.0 R5, the migration of NE configuration backups from the 5620 SAM database to the main-server file system begins during the main server initialization. The operation may take hours or days, depending on the number and size of the NE backups.

Caution 2 — If you need to enable Small Cell management, you must perform additional steps before you start the main server, as described in step 74.

Caution 3 — A 5620 SAM system upgrade is not complete until the main server performs crucial post-upgrade tasks during initialization. Before you attempt an operation such as a conversion to redundancy, you must ensure that the main server has fully initialized, or the operation fails.

Note — The “Start the 5620 SAM Main Server” parameter is configurable only if you specify a 5620 SAM or 5650 CPAM license file during the upgrade.





72 If you are upgrading from a 5620 SAM release earlier than 12.0 R5, perform the following steps.





73 If you specified that the main server is to start immediately after the upgrade, perform the following steps to verify that the server is started.








-- SAM Server is UP


74 If one of the following is true, perform Procedure 5-1 on the main server station:

• You intend to enable Small Cell management for the first time.• The 5620 SAM currently manages Small Cell NEs.

75 If you specified not to start the main server immediately after the upgrade, perform the following steps to start the server manually.





Note — If you did not specify a license file during the upgrade, you cannot start the server until you import a license. See the “Software and license configuration procedures” section in the 5620 SAM System Administrator Guide for information about importing a license.












-- SAM Server is UP



Upgrade Cflowd auxiliary servers

77 If the 5620 SAM system includes one or more Cflowd auxiliary servers, perform Procedure 7-5 on each Cflowd auxiliary server.

Upgrade or install 5620 SAM client

78 If you modify the SSL configuration during a main server upgrade, you cannot upgrade a client that connects to the main server; you must uninstall the client software and re-install it.

As required, perform the appropriate client software uninstallation procedures in the following chapters:

• 14—single-user client• 15—client delegate server

79 As required, perform the appropriate procedures in the following chapters to install or upgrade client software, depending on whether you modify the main server SSL configuration during the upgrade:






7.6 Redundant system upgrade workflow

The primary and standby main server and database roles, and the auxiliary server roles, reverse during an upgrade. The components on the left side of Figure 7-48 initially manage the network; after the upgrade, the components on the right side manage the network.

You can use Figure 7-48 as a reference during an upgrade. The bracketed labels in the figure, for example, [Server1], are used to clearly identify the objects of actions in workflow and procedure steps, where applicable.

Figure 7-48 Redundant upgrade reference diagram

The following is the sequence of high-level actions required to upgrade a redundant 5620 SAM system. A reference in quotation marks is a link to a section in Procedure 7-3.

Caution — A redundant 5620 SAM system upgrade involves a network-management outage, and must be performed only during a scheduled maintenance period of sufficient duration for the upgrade.

23182

Main Server [Server1]

Main Server [Server2]

Management system BEFORE upgrade (Server1 and DB1 are

primary BEFORE upgrade)

Management system AFTER upgrade (Server2 and DB2 are

primary AFTER upgrade)

Database [DB1]

Database [DB2]

Auxiliary Server(s) [Aux1]

(active BEFORE upgrade)

Auxiliary Server(s) [Aux2]

(active AFTER upgrade)

Managed network




To reduce the duration of a redundant system upgrade, some steps can be performed concurrently by multiple operators, as described in Table 7-2.

1 Perform the pre-upgrade tasks; see Procedure 7-1.

2 Open at least one 5620 SAM client to monitor the network until the first server and database are upgraded.

3 Stop the standby main server; see “Stop standby main server [Server2]”.

4 Disable the standby main server startup daemon; see “Disable standby main server daemon [Server2]”.

5 If the 5620 SAM system includes auxiliary servers, stop the [Aux2] auxiliary servers; see “Stop auxiliary servers [Aux2]”.

6 Disable 5620 SAM redundancy functions; see “Disable redundancy [Server1]”.

7 Stop the standby database; see “Stop standby database [DB2]”.

8 Run a script to prepare the standby database station for the upgrade; see “Run upgrade preparation script on standby database station [DB2]”.

9 Upgrade the standby database. This database becomes the new primary database; see “Upgrade standby 5620 SAM database [DB2]”.

10 Upgrade the original standby main server to become the new primary main server; see “Upgrade standby main server [Server2]”.

11 If the 5620 SAM system includes one or more Cflowd auxiliary servers, stop each Cflowd auxiliary server; see “Stop Cflowd auxiliary servers”.

12 If the 5620 SAM system includes auxiliary servers, upgrade the [Aux2] auxiliary servers; see “Upgrade auxiliary servers [Aux2]”.

13 Stop the original primary main server; see “Stop original primary main server [Server1]”.

Caution 1 — The following conditions must be true before you begin a redundant system upgrade; contact Alcatel-Lucent technical support for guidance, if required:

• Each 5620 SAM component is functional.• Each database station is to be associated with the same database

instance name after the upgrade as before the upgrade.• No hardware modifications are to be performed during the upgrade.

Caution 2 — After you stop the standby database in workflow step 7, “Stop standby database [DB2]”, any further configuration changes that are not immediately deployed are lost when the primary database is uninstalled in step 23— “Uninstall original primary database [DB1]”.

Note — This is the beginning of the network management outage.





14 Disable the original primary main server startup daemon; see “Disable original primary main server daemon [Server1]”.

15 Ensure that sufficient inodes are available for the upgrade on the original primary main server; see “Check main server file system [Server1]”.

16 If the 5620 SAM system includes one or more Cflowd auxiliary servers, upgrade each Cflowd auxiliary server; see “Upgrade Cflowd auxiliary servers”.

17 Stop the original primary database; see “Stop original primary database [DB1]”.

18 If the 5620 SAM system includes auxiliary servers, stop the [Aux1] auxiliary servers; see “Stop auxiliary servers [Aux1]”.

19 Start the new primary (original standby) 5620 SAM main server; see “Start new primary main server [Server2]”.

20 If the 5620 SAM system includes auxiliary servers, start the [Aux2] auxiliary servers; see “Start auxiliary servers [Aux2]”.

21 Upgrade or install 5620 SAM single-user clients or client delegate servers, as required; see “Upgrade or install 5620 SAM client”.

22 Perform sanity testing on the upgraded 5620 SAM system using a GUI client; see “Test 5620 SAM system using new client”.

23 Uninstall the original primary database; see “Uninstall original primary database [DB1]”.

24 Run a script to prepare the original primary database station for the new standby database installation; see “Run installation preparation script on original primary database station [DB1]”.

25 Install the new standby database; see “Install standby 5620 SAM database [DB1]”.

26 Reinstantiate the primary database on the new standby database station; see “Reinstantiate primary database on new standby database station [DB1]”.

27 Upgrade the original primary main server to become the new standby main server; see “Upgrade standby main server [Server1]”.

28 If the 5620 SAM system includes auxiliary servers, upgrade the [Aux1] auxiliary servers; see Procedure 7-4.

29 If the 5620 SAM system includes auxiliary servers, start the [Aux1] auxiliary servers; see “Start auxiliary servers [Aux1]”.

30 Upgrade or install additional 5620 SAM single-user clients or client delegate servers, if required; see “Upgrade or install additional clients for redundant system”.

Note — This is the end of the network-management outage.




Table 7-2 lists the redundant 5620 SAM upgrade tasks in a format that involves two operators, A and B, who perform some tasks concurrently.

Table 7-2 Workflow for concurrent task execution during redundant upgrade

5620 SAM system mode

Operator A workflow steps Operator B workflow steps

DUPLEX

1—Pre-upgrade tasks described in Procedure 7-1

2—Open GUI client to monitor network Begin 5620 SAM software download

SIMPLE

X

3— “Stop standby main server [Server2]” 4— “Disable standby main server daemon [Server2]”

5— “Stop auxiliary servers [Aux2]” 6— “Disable redundancy [Server1]”

7— “Stop standby database [DB2]”8— “Run upgrade preparation script on standby database station [DB2]”9— “Upgrade standby 5620 SAM database [DB2]” steps, including starting database activation

—

During database activation:10— “Upgrade standby main server [Server2]”12— “Upgrade auxiliary servers [Aux2]”

After standby main server upgrade:11— “Stop Cflowd auxiliary servers”

After database activation:Remaining “Upgrade standby 5620 SAM database [DB2]” steps

—

O

U

T

A

G

E

13— “Stop original primary main server [Server1]” 14— “Disable original primary main server daemon [Server1]”

15— “Check main server file system [Server1]”16— “Upgrade Cflowd auxiliary servers”

17— “Stop original primary database [DB1]”18— “Stop auxiliary servers [Aux1]”

19— “Start new primary main server [Server2]”Outage persists until device discovery complete

20— “Start auxiliary servers [Aux2]”

SIMPLEX

21— “Upgrade or install 5620 SAM client” 22— “Test 5620 SAM system using new client”

23— “Uninstall original primary database [DB1]” —

24— “Run installation preparation script on original primary database station [DB1]”

—

25— “Install standby 5620 SAM database [DB1]” 27— “Upgrade standby main server [Server1]”

26— “Reinstantiate primary database on new standby database station [DB1]”

—

DUPLEX

28— “Upgrade auxiliary servers [Aux1]”

29— “Start auxiliary servers [Aux1]”

30— “Upgrade or install additional clients for redundant system”





7.7 Redundant system upgrade

This section describes how to upgrade the software components of a redundant 5620 SAM system. Procedure 7-3 describes how to upgrade the 5620 SAM database and main server software.

Before you begin a 5620 SAM system upgrade, you must collect the required information and ensure that the proper conditions are in place, as described in Procedure 7-1.

Procedure 7-3 To upgrade a redundant 5620 SAM system

Perform this procedure to upgrade the 5620 SAM database and main server software in a redundant deployment. Ensure that you record the information that you specify in the procedure, for example, directory names, passwords, and IP addresses. You require the following user privileges to perform this procedure:

on each main server station:

• root• samadmin

on each database station:

• root• Oracle management

1 Open a 5620 SAM client GUI to monitor the network during the upgrade.



management users






Caution — If you plan to implement the RHEL iptables and ip6tables firewall as part of the 5620 SAM system upgrade, you must ensure that the RHEL iptables and ip6tables firewall on each station is disabled before the upgrade.




Stop standby main server [Server2]

2 Perform the following steps to stop the standby main server application.

i Log in to the standby main server station as the samadmin user.









vi The 5620 SAM main server is stopped when the command displays the following status message:



Disable standby main server daemon [Server2]

3 Perform the following steps on the standby main server station to disable the main server startup daemon. This ensures that the standby main server does not start in the event of an accident during the upgrade.


bash$ su - ↵









Stop auxiliary servers [Aux2]

4 If the 5620 SAM system includes auxiliary servers, perform the following steps on each appropriate auxiliary server station [Aux2].



iii Enter the following to stop the auxiliary server application:

bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop ↵

The 5620 SAM auxiliary server stops.

Disable redundancy [Server1]

5 Perform the following steps to disable the 5620 SAM failover and switchover functions.

i Log in to the primary main server station [Server1] as the samadmin user.


iii Enter the following to navigate to the server configuration directory:


iv Enter the following to make a backup copy of the server configuration file:


v Open the nms-server.xml file with a plain-text editor, for example, vi.

vi Locate the section that begins with the <db tag.

vii Locate the following line in the section:

host="IP_address"

viii Ensure that the IP_address value in the line is the IP address of the database designated as DB1.

ix Locate the following line in the section:

database="instance_name"

x Ensure that the instance_name value in the line is the database instance name of the database designated as DB1.

xi Edit the following line in the section that reads:

redundancyEnabled="true"

to read:

redundancyEnabled="false"




xii Save and close the nms-server.xml file.

xiii Enter the following to put the nms-server.xml change into effect:

bash$ /opt/5620sam/server/nms/bin/nmsserver.bash read_config↵

The primary main server application is reconfigured with database redundancy disabled.

Stop standby database [DB2]

6 Perform the following steps to stop the database on the standby database station.

i Log in to the original standby database station as the root user.



# cd /etc/rc3.d ↵






Done

Run upgrade preparation script on standby database station [DB2]



Caution — Ensure that you run the script included with the new 5620 SAM software. Using a different version of the script may cause the database upgrade to fail.

Note — If you later back out of the database upgrade and want to re-install the previous database, you must do the following before you attempt to re-install the previous database:

• run the current version of the script and specify the remove_project command-line option

• run the previous version of the script and choose option 1• reboot the station






# cd Linux ↵







3) EXIT


11 Enter 2 ↵.








passwd: Success



Do you want to change the password for the UNIX user username? [Yes/No]:





New Password:
























14 Enter the following to reboot the standby database station [DB2]:

# init 6 ↵


The next section of the procedure describes the upgrade of the standby 5620 SAM database, which is the new primary 5620 SAM database after the upgrade.





Upgrade standby 5620 SAM database [DB2]

15 After the standby database station [DB2] reboots, log in to the station as the root user.









bash$ cd Linux ↵







Note — After the upgrade, the 5620 SAM database on this station is the new primary database.




22 The 5620 SAM database installer opens, as shown in Figure 7-50. The left pane indicates upgrade progress. The right pane displays release information about the software. Click on the Next button.








24 Select Upgrade a Database, as shown in Figure 7-52. Click on the Next button.


The 5620 SAM installer prepares to upgrade the database, as shown in Figure 7-53.





25 If the panel in Figure 7-54 is displayed, perform the following steps. Otherwise, go to step 29.



ii Enter the following to switch to the root user:

bash$ su - ↵

iii Enter the following to run the script named in the panel:




















28 When the panel in Figure 7-57 is displayed, perform the following steps.















29 If the panel in Figure 7-58 is displayed, perform the following steps.


i Click on the “Start Oracle Patch Installation” button to begin installing the Oracle patch. Oracle patch installation can take an hour or more to complete.

ii Oracle patch installation details are displayed as the patch installation progresses. When the patch installation is complete, as shown in Figure 7-59, click on the Next button.





30 Perform the following steps if the panel shown in Figure 7-60 is displayed.

i Specify the location of the currently installed Oracle software. The information may be required if the upgrade is to be rolled back.

ii Configure the “Keep Old Oracle Directory Contents after Upgrade” parameter.


Figure 7-60 Locate Old Oracle Software Directory

Note — If the parameter is not selected, the 5620 SAM database installer removes the directory during the upgrade, and the Oracle software must be reinstalled in the event of an upgrade rollback.





31 Configure the following parameters shown in Figure 7-61 using information from the current standby database [DB2] configuration, then click on the Next button:

• Public IP (accessible to servers)• Instance Name• Database User Password

Figure 7-61 Get Upgrade Database Info

The installer prepares for the next configuration phase, as shown in Figure 7-62.

Figure 7-62 Please Wait




32 Configure the following parameters, shown in Figure 7-63, using the original primary database [DB1] values. Click on the Next button.



33 You are prompted to activate the standby database [DB2], as shown in Figure 7-64. Click on the Start activation button to proceed with the activation.

Figure 7-64 Activate the Standby Database





34 Database activation details are displayed as the activation progresses. When the activation is complete, as shown in Figure 7-65, click on the Next button.

Figure 7-65 Activate the Standby Database

The installer prepares for the next configuration phase, as shown in Figure 7-66.







• Enable 5620 SAM Server IP Validation• Server One IP Address [Server1]• Server Two IP Address [Server2]
























39 The panel shown in Figure 7-71 allows you to purge the current 5620 SAM statistics data before the upgrade.

Configure the following parameters, then click on the Next button:

• Purge All Accounting Statistics• Purge All MIB Statistics

Figure 7-71 Purge Statistics


Caution — Purging the statistics data may reduce or increase the upgrade duration, depending on the 5620 SAM release and the database contents. Staging an upgrade in advance of a live upgrade can determine how a statistics purge affects the upgrade duration.

Note — The statistics data for the specified statistics types are permanently deleted from the 5620 SAM database.




41 If you are prompted to run an Oracle patch pre-installation script, as shown in Figure 7-72, run the script in a separate console window as the root user.

Figure 7-72 Oracle Patch Pre-install Script

42 When the script execution is complete, click on the Next button.

43 You are prompted to begin the database upgrade, as shown in Figure 7-73. A database upgrade can take two hours or more, depending on the database release and number of database records. Click on the Start Process button to begin the database upgrade.








44 When the panel in Figure 7-75 is displayed, the 5620 SAM database upgrade is complete, but as shown in the panel text, you must run a script to enable automatic database startup.






i Open a separate console window on the station [DB2] as the root user.





This database [DB2] is the new primary database.


For information about how to limit the number of database user login failures, see the “5620 SAM database management procedures” section in the 5620 SAM System Administrator Guide.


bash$ exit ↵

48 Enter the following to reboot the new primary database station:

# init 6 ↵


The next section of the procedure describes the upgrade of the standby main server [Server2], which is the new primary main server after the upgrade.

Upgrade standby main server [Server2]

49 Log in to the original standby main server station [Server2] as the root user.




# who ↵



Note — You do not need to perform this step if the database has been previously configured to limit the database user login failures.







# cd Linux ↵









































61 Configure the following parameters, shown in Figure 7-83, using the recorded values from the new primary [DB2] database upgrade, then click on the Next button.

• Primary Database Server IP Address• Primary Database Instance Name• Database User Password









Note — The “Online Backup Destination” value is a path on the file system of the database station specified in step 61 [DB2].




63 Configure the new standby database [DB1] parameters shown in Figure 7-85, then click on the Next button:

• Standby Database Server IP Address• Standby Database Instance Name• Enable Database Backup File Synchronization












































68 If you select the “Enable Database Alignment” parameter shown in Figure 7-91, you must specify the preferred database of this main server, then click on the Next button. In a typical scenario, this is the new primary database [DB2].

Database alignment associates each main server with the database to which it is most directly connected in terms of network latency. This database is the preferred database of the main server. For example, in a 5620 SAM complex that is geographically dispersed, the preferred database of a main server is the database in the same physical facility; typically, the primary main server and database are in one facility, and the standby main server and database are in another.

When a primary main server starts, it verifies that the database to which it connects is the preferred database. If this database is not the preferred database, the server performs a database switchover to reverse the primary and standby database roles. If the switchover is successful, the main servers and databases in the 5620 SAM complex are aligned. If the switchover fails, each database reverts to the former role, and the main server raises an alarm about the failed switchover.

When database alignment is enabled and you perform a database switchover, the primary main server does not attempt database realignment, because a switchover is a manual operation that is considered to be a purposeful act.








• Delay Time After Database Failover (minutes)This parameter specifies how long, in m, the main server waits after database failover completion before it initiates a standby database reinstantiation.







70 Configure the [Server2] parameters shown in Figure 7-93, then click Next:







Figure 7-93 Main Server Configuration for Clients [Server2]









Configure the [Server2] parameters shown in Figure 7-94:



Figure 7-94 Server Configuration for OSS Clients [Server2]





72 Configure the “Public IP (accessible to peer server)” parameter shown in Figure 7-95 using the IP address that the other main server [Server1] must use to reach this main server [Server2], and click on the Next button.



• Public IP (accessible to peer server) [Server2]• Peer Public IP (accessible to this server) [Server1]











• IP Address



























77 Configure the following main server [Server2] parameters shown in Figure 7-101, then click on the Next button:

• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5620 SAM main server [Server2] and the managed network.


Figure 7-101 Mediation Configuration [Server2]







78 Configure the following peer main server [Server1] parameters shown in Figure 7-102, then click on the Next button:


Figure 7-102 Peer Main Server Configurations [Server1]



Note 1 — The peer server [Server1] is the other 5620 SAM main server, which is the new standby main server after the upgrade.

Note 2 — The “Peer Server SNMP Trap Receiving IPv6 Address” parameter is configurable only if you select the “IPv6 Address Used” parameter in step 77.







Figure 7-103 Peer Main Server Configuration for Clients [Server1]

81 Go to step 83.













84 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 7-106. Click on the Install button to begin the main server upgrade.








Figure 7-108 Installing the server as a Unix Daemon

86 When the main server upgrade is complete, ensure that the “Start the 5620 SAM Main Server” parameter is not selected, as shown in Figure 7-109.


Caution — You must ensure that the main server does not start before you are instructed to start the main server in step 98.





This main server [Server2] is the new primary main server.

87 Click on the Done button to close the server installer.


i Log in as the samadmin user on the new primary main server station.




89 If one of the following is true, perform Procedure 5-1 on the new primary main server station:


Stop Cflowd auxiliary servers

90 If the 5620 SAM system includes one or more Cflowd auxiliary servers, stop each Cflowd auxiliary server.

i Log on to the Cflowd auxiliary server as the root user.





The following messages are displayed.



Upgrade auxiliary servers [Aux2]

91 If the 5620 SAM system includes auxiliary servers, perform Procedure 7-4 on each appropriate auxiliary server station [Aux2].

Note — Do not start the auxiliary servers immediately after you upgrade them; they are started later in this procedure.




Stop original primary main server [Server1]

92 Perform the following steps to stop the original primary main server [Server1] application.

i Log in to the original primary main server station as the samadmin user.












Disable original primary main server daemon [Server1]

93 Perform the following steps to disable the main server startup daemon. This ensures that the main server does not automatically start in the event of a power disruption during the upgrade.


bash$ su - ↵










Check main server file system [Server1]

94 If the 5620 SAM system manages more than 3000 NEs, perform the following steps on the original primary main server [Server1] to ensure that sufficient inodes are available for the upgrade.


# df -i /opt/5620sam/server/nms/bin/depl/mediation ↵

The command returns output similar to the following:

Filesystem Inodes IUsed IFree IUse% Mounted on

/dev/sda2 3842048 65297 3776751 2% /opt/5620sam

ii If the “IUse%” value is greater than 40%, enter the following command to remove the mediation files:

# rm -r /opt/5620sam/server/nms/bin/depl/mediation ↵

Upgrade Cflowd auxiliary servers

95 If the 5620 SAM system includes one or more Cflowd auxiliary servers, perform Procedure 7-5 on each Cflowd auxiliary server.

Stop original primary database [DB1]

96 Perform the following steps to stop the database on the original primary database station.

i Log in to the original primary database station as the root user.



# cd /etc/rc3.d ↵






Done

Note — The command may take several minutes to complete, depending on the number of files in the mediation directory.




Stop auxiliary servers [Aux1]







Start new primary main server [Server2]

98 Perform the following steps to start the new primary main server.

i Enter the following to switch to the samadmin user on the new primary main server station [Server2]:

# su - samadmin ↵





Caution 1 — The new primary database must be upgraded and running before you start the new primary main server.

If you perform the new primary main server and database upgrades concurrently, do not perform this step until the database upgrade is complete, including the station reboot described in step 48.

Caution 2 — A 5620 SAM system upgrade is not complete until each main server performs crucial post-upgrade tasks during initialization. Before you attempt an operation such as a conversion to redundancy, you must ensure that each main server has fully initialized, or the operation fails.

Note — If you did not specify a license file during the main server upgrade, you cannot start the server until you import a license. See the “Software and license configuration procedures” section in the 5620 SAM System Administrator Guide for information about importing a license.








If the new primary main server [Server2] is not completely started, the command may generate exception messages, or display the following as the first line of status information:


The new primary main server [Server2] is completely started when the command returns the following line of output:




Start auxiliary servers [Aux2]






iv Enter the following to start the auxiliary server application:

bash$ ./auxnmsserver.bash auxstart ↵


Upgrade or install 5620 SAM client









Test 5620 SAM system using new client

102 When the new primary main server is started, use a newly installed or upgraded client to perform sanity testing of the new primary main server and database.

See the “Procedures for opening and closing the GUI” section in the 5620 SAM User Guide for information about client operation.

If you need to back out of the upgrade and return the original primary main server [Server1] and database [DB1] to service, you can do so by stopping the new primary main server [Server2] and database [DB2] and restarting the original primary main server [Server1] and database [DB1].

Uninstall original primary database [DB1]

103 Log in to the original primary database station [DB1] as the root user.





106 Enter the following to open the 5620 SAM uninstaller:

bash$ /opt/5620sam/samdb/install/Uninstaller/Uninstall_5620_SAM_Database_Configurator ↵

Note — You must specify the IP address of the new primary main server [Server2] as the primary main server IP address when you install or upgrade the client software.





The splash screen shown in Figure 7-110 opens. The splash screen appearance depends on which 5620 SAM release you are uninstalling.

Figure 7-110 5620 SAM Uninstaller

107 The 5620 SAM database uninstaller opens, as shown in Figure 7-111. The left pane indicates uninstallation progress. The right pane indicates the operations that are to take place. Click on the Next button.

Figure 7-111 Uninstall 5620 SAM Database Configurator




108 A 5620 SAM standby database upgrade requires the removal of the previously installed Oracle software. Select the “Uninstall Oracle software” parameter, as shown in Figure 7-112, and click on the Next button.

Figure 7-112 Uninstall Oracle Software

Note — When the installer removes the Oracle software, it does not delete the Oracle base installation directory, because this directory is typically the home directory of the Oracle management user.





109 As shown in Figure 7-113, you are prompted to run a script that enables the uninstallation of the database daemons. Open a separate console window and run the script.

Figure 7-113 Uninstall Oracle Proxy

110 When the script execution is complete, click on the OK button.

111 Click on the Uninstall button shown in Figure 7-113 to begin the uninstallation.

112 As shown in Figure 7-114, the uninstaller begins to remove files and directories from the original primary database station [DB1].





113 When database uninstallation is complete, as shown in Figure 7-115, click on the Done button to close the database uninstaller.

Figure 7-115 Uninstall Complete


bash$ exit ↵

115 Enter the following to reboot the original primary database station [DB1]:

# init 6 ↵


Run installation preparation script on original primary database station [DB1]

116 After the original primary database station reboots, you must run a script that configures the Oracle management user account.


Caution — Ensure that you run the script included with the new 5620 SAM software. Using a different version of the script may cause the database installation to fail.

Note — If you later back out of the redundant database upgrade and want to re-install the previous database, you must do the following before you attempt to re-install the previous database:

• Run the current version of the script and specify the remove_project command-line option.

• Run the previous version of the script and choose option 1.• Reboot the station.






# cd Linux ↵







3) EXIT


120 Enter 1 ↵.




122 If you accept the default, the following prompt is displayed:

WARNING: Group group already exists locally.

Do you want to use the existing group? [Yes/No]:


a Specify the default group. Type Yes ↵.

b Specify a different group. Type No ↵, and then return to step 121.

123 If the specified group contains a user, the following prompt is displayed:

The user [username] for the group [group] already exists locally.

Do you want to use the existing user? [Yes/No]:


a Specify the existing user. Type Yes ↵. The following messages are displayed:







Changing ownership of the directory /opt/5620sam/oracle12r1to username:group.



passwd: Success



Do you want to change the password for the UNIX user oracle? [Yes/No]:

b Specify a different user. Perform the following steps.

i Type No ↵. The following prompt is displayed:


ii Enter a username and press ↵.





Adding username...




passwd: Success




New Password:

iii Type a password and press ↵. The following prompt is displayed:


iv Retype the password and press ↵. The following message is displayed if the password update is successful:






v Go to step 125.





New Password:
























126 When the script execution is complete, enter the following to reboot the original primary database station [DB1]:

# init 6 ↵


The next section of the procedure describes the installation of the new standby 5620 SAM database on the original primary database station [DB1].

Install standby 5620 SAM database [DB1]

127 After the original primary database station [DB1] reboots, log in to the station as the root user.







bash$ cd Linux ↵





Note — After the upgrade, the 5620 SAM database on this station is the new standby database. Later in the procedure, the primary database is reinstantiated on this station.




































ii Enter the following to switch to the root user:

# su - ↵

iii Enter the following to run the script named in the panel:


































142 Configure the “Public IP (accessible to servers)” parameter shown in Figure 7-127 using the value from the original primary database [DB1] configuration, then click on the Next button.

Figure 7-127 Standby Database Configuration Info [DB1]



























146 Configure the following parameters, shown in Figure 7-131, using the recorded values from the original standby database [DB2] upgrade. Click on the Next button.


Figure 7-131 Primary Database Info [DB2]

147 You are prompted to begin standby database creation, as shown in Figure 7-132. Click on the Start Process button to begin the database creation.





The next panel displays database configuration progress, as shown in Figure 7-133.















bash$ exit ↵

151 Enter the following to reboot the new standby database station:

# init 6 ↵


The next section of the procedure describes the reinstantiation of the primary database on the new standby database station [DB1].

Reinstantiate primary database on new standby database station [DB1]




155 Click on the Yes button. The database reinstantiation begins.


156 When the reinstantiation is complete, close the System Information form.

The next section of the procedure describes the upgrade of the original primary main server [Server1], which is the new standby main server after the upgrade.

Note 1 — Database reinstantiation can take a long time when there is a large amount of statistics data to transfer.

Note 2 — You can perform the original primary main server [Server1] upgrade described in the next section of the procedure while the database reinstantiation is in progress.




Upgrade standby main server [Server1]

157 Log in to the original primary main server station [Server1] as the root user.




# who ↵





# cd Linux ↵







Note — This station is the new standby main server station after the upgrade.




































169 Configure the following primary database [DB2] parameters, shown in Figure 7-142, using the values from the new primary database [DB2] configuration. Click on the Next button.


Figure 7-142 Primary Database Configuration [DB2]




170 Configure the new standby database [DB1] parameters shown in Figure 7-143, then click on the Next button:


Figure 7-143 Standby Database Configuration [DB1]











































175 If you select the “Enable Database Alignment” parameter shown in Figure 7-149, you must specify the preferred database of this main server, then click on the Next button. In a typical scenario, this is the new standby database [DB1].

Database alignment associates each main server with the database to which it is most directly connected in terms of network latency. This database is the preferred database of the main server. For example, in a 5620 SAM complex that is geographically dispersed, the preferred database of a main server is the database in the same physical facility; typically, the primary main server and database are in one facility, and the standby main server and database are in another.

When a primary main server starts, it verifies that the database to which it connects is the preferred database. If this database is not the preferred database, the server performs a database switchover to reverse the primary and standby database roles. If the switchover is successful, the main servers and databases in the 5620 SAM complex are aligned. If the switchover fails, each database reverts to the former role, and the main server raises an alarm about the failed switchover.

When database alignment is enabled and you perform a database switchover, the primary main server does not attempt database realignment, because a switchover is a manual operation that is considered to be a purposeful act.















177 Configure the [Server1] parameters shown in Figure 7-151, then click Next:







Figure 7-151 Main Server Configuration for Clients [Server1]









Configure the standby main server [Server1] parameters shown in Figure 7-152:



Figure 7-152 Server Configuration for OSS Clients [Server1]





179 Configure the “Public IP (accessible to peer server)” parameter shown in Figure 7-153 using the IP address that the other main server [Server2] must use to reach this main server [Server1], and click on the Next button.



• Public IP (accessible to peer server) [Server1]• Peer Public IP (accessible to this server) [Server2]











• IP Address








182 Perform the following steps to enable communication security between the standby main server [Server1] and clients, and between the standby main server [Server1] and auxiliary servers. Otherwise, click on the Next button.







Note — The parameter values must match the values specified during the original standby main server upgrade.













184 Configure the following standby main server [Server1] parameters shown in Figure 7-159, then click on the Next button:

• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the standby main server [Server1] and the managed network.


Figure 7-159 Mediation Configuration [Server1]







185 Configure the following primary main server [Server2] parameters shown in Figure 7-160, then click on the Next button:


Figure 7-160 Peer Main Server Configurations [Server2]



Note 1 — The peer server is the other main server [Server2], which is the new primary main server after the upgrade.

Note 2 — The “Peer Server SNMP Trap Receiving IPv6 Address” parameter is configurable only if you select the “IPv6 Address Used” parameter in step 184.








188 Go to step 190.













191 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 7-164. Click on the Install button to begin the server upgrade.













193 When the main server upgrade is complete, as shown in Figure 7-167, configure the “Start the 5620 SAM Main Server” parameter to specify whether you want the server to start immediately after the upgrade.


194 Click on the Done button to close the server installer. If you specified that the main server is to start immediately after the upgrade, the server starts.

This main server [Server1] is the new standby main server.

Caution 1 — If you are upgrading from a release earlier than 12.0 R5, the migration of NE configuration backups from the 5620 SAM database to the main-server file system begins during the main server initialization. The operation may take hours or days, depending on the number and size of the NE backups.

Caution 2 — If you need to enable Small Cell management, you must perform additional configuration steps before you start the main server, as described in step 196.

Caution 3 — A 5620 SAM system upgrade is not complete until each main server performs crucial post-upgrade tasks during initialization. Before you attempt an operation such as a conversion to redundancy, you must ensure that each main server has fully initialized, or the operation fails.

Note — The “Start the 5620 SAM Main Server” parameter is configurable only if you specify a 5620 SAM or 5650 CPAM license file during the upgrade.





i Log in as the samadmin user on the new standby main server station.




196 If one of the following is true, perform Procedure 5-1 on the new standby main server station:


197 If you specified that the new standby main server [Server1] is to start immediately after the upgrade, perform the following steps to verify that the server is started.










198 If you specified that the new standby main server [Server1] is not to start immediately after the upgrade, perform the following steps to start the server manually.



Note — If you did not specify a license file during the main server upgrade, you cannot start the server until you import a license. See the “Software and license configuration procedures” section in the 5620 SAM System Administrator Guide for information about importing a license.


















Upgrade auxiliary servers [Aux1]

200 If the 5620 SAM system includes auxiliary servers, perform Procedure 7-4 on each appropriate auxiliary server station [Aux1].

Start auxiliary servers [Aux1]






The 5620 SAM auxiliary server starts. Initial server startup can take twenty minutes or more.

Note — Do not start the auxiliary servers immediately after you upgrade them; they are started later in this procedure.




Upgrade or install additional clients for redundant system






Note — You must specify the IP address of the new primary main server [Server2] as the primary main server IP address when you install or upgrade the client software.





7.8 Auxiliary server upgrade

This section describes how to upgrade a 5620 SAM auxiliary server component for a standalone or redundant 5620 SAM system. Procedure 7-4 describes how to upgrade the 5620 SAM auxiliary server software.

Procedure 7-4 To upgrade a 5620 SAM auxiliary server

Perform this procedure to upgrade the 5620 SAM auxiliary server software. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses.

You require the following user privileges on the auxiliary server station to perform this procedure:


1 Perform the following steps to stop the auxiliary server application.

i Log in to the auxiliary server station as the root user.


iii Enter the following to switch to the samadmin user:

# su - samadmin ↵

iv Enter the following to navigate to the server binary directory:


v Enter the following to stop the auxiliary server application:



• #—represents the prompt for the root user• bash$—represents the prompt for the samadmin user









vi Enter the following to display the auxiliary server status:



vii The server is stopped when the command displays the following status message:

Auxiliary Server is stopped

If the command displays a different message, wait five minutes and return to step 1 vi. Do not proceed to the next step until the server is stopped.


# exit ↵



# who ↵


ii If the samadmin user is listed, close each samadmin user session; see the OS documentation for information.



# cd Linux ↵


















9 Select Auxiliary Server Installation, as shown in Figure 7-171. Click on the Next button.












• Server Domain Name (typically 5620sam)This parameter uniquely identifies the 5620 SAM server cluster to which the auxiliary server belongs.

• Public IP (accessible to servers)• Redundancy Supported On the 5620 SAM Main Server

Select this parameter only if the 5620 SAM main servers are deployed in a redundant configuration.

• Enable Stats ServiceSelect this parameter if the 5620 SAM auxiliary server is to be used for statistics collection.

• Enable Call Trace ServiceSelect this parameter if the 5620 SAM auxiliary server is to be used for call-trace data collection.

Figure 7-173 Auxiliary Server Address Configuration







a If the “Redundancy Supported On the 5620 SAM Main Server” parameter in step 11 is not selected, configure the “Server IP Address” parameter shown in Figure 7-174:


b If the “Redundancy Supported On the 5620 SAM Main Server” parameter in step 11 is selected, configure the parameters shown in Figure 7-175:

• Server One IP Address• Server Two IP Address






• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5620 SAM auxiliary server and the OSS clients.



14 If “Enable Call Trace Service” in step 11 is not selected, go to step 16.





15 The panel shown in Figure 7-177 is displayed if you select the “Enable Call Trace Service” parameter in step 11. Configure the following parameters, then click on the Next button:

• IPv6 Address Used• Call Trace Receiving IPv4 Address• Call Trace Receiving IPv6 Address• Call Trace Receiving Directory (typically /opt/5620sam/calltrace)• Debug Trace Receiving Directory (typically /opt/5620sam/debugtrace)

Figure 7-177 Auxiliary Server Call Trace Configuration

Note — The “Call Trace Receiving IPv6 Address” parameter is displayed only when the “IPv6 Address Used” parameter is selected, as shown in Figure 7-177.





• Enable Synchronization of Data• Public IP (accessible to peer auxiliary)• Peer Public IP (accessible to this auxiliary)


Note — The “Public IP (accessible to peer auxiliary)” and “Peer Public IP (accessible to this auxiliary)” parameters are configurable only when the “Enable Synchronization of Data” parameter is enabled.





17 Perform the following steps to enable communication security between the auxiliary server and each main server. Otherwise, click on the Next or Install button to continue.





iii Click on the Next or Install button.





18 The panel in Figure 7-180 is displayed if you select the “Enable Stats Service” parameter in step 11. Specify an OSS XML output location (typically /opt/5620sam/auxserver/xml_output), and then click on the Install button to begin the auxiliary server upgrade.








19 As shown in Figure 7-182, the auxiliary server is installed as a UNIX daemon. Click on the Next button.





20 When the auxiliary server upgrade is complete, as shown in Figure 7-183, configure the “Start the 5620 SAM Auxiliary Server” parameter to specify whether you want the server to start immediately after the upgrade.


If you specify not to start the auxiliary server immediately after the upgrade, you can start the server later by performing the following steps.






Caution 1 — If you are upgrading the auxiliary server as part of a redundant 5620 SAM system upgrade, do not configure the server to start immediately after the upgrade.

Caution 2 — If you need to enable Small Cell management using the auxiliary server, you must perform additional steps before you start the auxiliary server, as described in step 21.

Note — The order in which an auxiliary server and the primary main server initialize is unimportant. A main server synchronizes with an auxiliary server as soon as it is able to communicate with the auxiliary server.





21 If one of the following is true, perform Procedure 5-1 on the auxiliary server station:

• You intend to enable Small Cell management using the auxiliary server for the first time.

• The 5620 SAM currently manages Small Cell NEs using the auxiliary server.

22 Click on the Done button to close the server installer. If you specified that the auxiliary server is to start after the upgrade, the server starts. Initial server startup can take twenty minutes or more.




7.9 Cflowd auxiliary server upgrade

This section describes how to upgrade a 5620 SAM Cflowd auxiliary server in a standalone or redundant 5620 SAM system.

Procedure 7-5 To upgrade a 5620 SAM Cflowd auxiliary server

Perform this procedure to upgrade the 5620 SAM Cflowd auxiliary server software on a station. You require root user privileges on the station to perform the procedure.



3 Stop the Cflowd auxiliary server; enter the following:






4 Navigate to the appropriate directory, depending on the release that is installed:

• 13.0 R4 or earlier:/opt/5620sam/jboss-5.1.0/server/5620sam/conf/dcp-R_rRn

• 13.0 R5 or later:/opt/5620sam/jboss-6.4.0/standalone/configuration/dcp-R_rRn


5 Make a backup copy of the following files, which are required after the upgrade, and store them in a secure location on another station:

• CfdGlobalPolicy.xml—global policy definition that includes the aggregation intervals and counters

• CfdLocalPolicy.xml—collection configuration for managed devices• CfdResultsTransfer.properties—IPDR file transfer settings• CfdSpecialStudyPolicy.xml—special-study policy settings• CfdUappsPolicy.xml—application and protocol filters• SamHostInfoCfg.xml—5620 SAM communication settings

6 Enter the following to navigate to your home directory:

# cd ↵






7 Uninstall the Cflowd auxiliary server; enter the following:

# /opt/5620sam/dcp-R_rRn/uninstall/uninstall ↵

The uninstallation begins, and the script displays a series of progress indicators. The following message is displayed when the uninstallation is complete.

Uninstallation Complete.

8 Download the integration package for the 5620 SAM release from the Alcatel-Lucent software repository and copy the package to the Cflowd auxiliary server station.

9 Uncompress the integration package in a local directory.

10 Navigate to the directory that contains the package files.


# gunzip < DcpInstaller_linux64.tar.gz | tar xvf - ↵

The installation files and directories are extracted to the current directory.


# cd linux64/dcp/util ↵

13 Enter the following to verify and configure the system parameters:

# ./checkInstall.sh ↵


Executing ./checkInstall.sh. Please check /tmp/checkInstall.log.nnnnn for more details

Check PATH setting...

Check /etc/nsswitch.conf setting...

Check OS version...

Check system info...

Check the minimum required OS packages are installed...

package_1

package_2

package_n

the minimum OS packages are installed...OK

Tune OS kernel parameters...

14 If the script displays a message that begins with ERROR, correct the error described in the message and repeat step 13. Check the log file indicated in the script output for information about the error, if required.




15 Enter the following to install the new software:

# ./runInstaller.sh install ↵

The installer displays the following message:

Start to install 5620 SAM DCP. Please check the log in /var/opt/5620sam/logs/install for status!

The installation is complete when the CLI prompt reappears.

16 Navigate to the /opt/5620sam/jboss-6.4.0/standalone/configuration/dcp-R_rRn directory, where R_rRn is the software release identifier.

17 Replace the following files with the backup copies created in step 5:

• CfdGlobalPolicy.xml• CfdLocalPolicy.xml• CfdResultsTransfer.properties• CfdSpecialStudyPolicy.xml• CfdUappsPolicy.xml• SamHostInfoCfg.xml

18 Start the Cflowd auxiliary server.


# cd /opt/5620sam/dcp-R_rRn/bin ↵




The server starts, and displays the following messages:

Starting 5620 SAM DCP server......










8.1 Overview 8-2

8.2 Conversion to redundancy procedures list 8-2

8.3 Conversion to redundancy workflow 8-3

8.4 Conversion to redundancy 8-4





8.1 Overview

Before you attempt to perform a procedure in this chapter, ensure that you understand and comply with the relevant requirements, considerations, and precautions described in chapter 1 of this document.

See Appendix C for 5620 SAM conversion to redundancy parameter descriptions.

8.2 Conversion to redundancy procedures list

Table 8-1 lists the procedures required to convert a standalone 5620 SAM system to a redundant 5620 SAM system.

Table 8-1 5620 SAM conversion to redundancy procedures list

Caution 1 — Converting a standalone 5620 SAM deployment to redundancy requires that you thoroughly understand the general and OS-specific requirements. It is essential that you plan, document, and test the conversion procedure in advance on a lab deployment that is representative of the target live network.

Contact Alcatel-Lucent technical support to assess the conversion requirements for your network implementation of the 5620 SAM. Alcatel-Lucent offers an upgrade service and strongly recommends that it be engaged for conversions in larger or more complex networks.

Caution 2 — Before a 5620 SAM system conversion to redundancy, you must ensure that the RHEL iptables and ip6tables firewall on each station is disabled.

Caution 3 — Alcatel-Lucent supports 5620 SAM software configuration only under the conditions described in chapter 1.

Note 1 — You cannot convert a standalone 5620 SAM deployment to redundancy as part of a 5620 SAM system upgrade. To upgrade your 5620 SAM system and convert it to redundancy, you must upgrade the system before you perform the conversion.

Note 2 — You require a 5620 SAM license file for the new standby main server, or an updated license file that includes the new standby server information. Contact Alcatel-Lucent technical support for more information about 5620 SAM licenses.

Procedure Purpose

To convert a standalone 5620 SAM system to a redundant system

Convert a standalone 5620 SAM system on one or more stations to a redundant 5620 SAM system.




8.3 Conversion to redundancy workflow

The following is the sequence of high-level actions required to convert a standalone 5620 SAM system to a redundant system. A reference in quotation marks is a link to a section in Procedure 8-1.

1 Back up the 5620 SAM configuration files. See “Back up configuration files”.

2 Gather the system information required for the conversion. See “Gather required information”.

3 Close the unrequired 5620 SAM client sessions. See “Close client sessions”.

4 Close the 5620 SAM LogViewer application, if it is running. See “Close 5620 SAM LogViewer”.

5 Back up the 5620 SAM database. See “Back up database”.

6 Stop the main server. See “Stop server”.

7 Disable the main server startup daemon. See “Disable server daemon”.

8 Stop the 5620 SAM database. See “Stop 5620 SAM database”.

9 Prepare the primary database station for the installation. See “Run Oracle pre-installation script”.

10 Convert the standalone database to a primary database. See “Convert standalone database to primary database”.

11 Convert the standalone server to a primary server. See “Convert standalone server to primary server”.

12 Create an Oracle management user account and configure the associated system parameters on the standby database station. See “Prepare new standby database station for standby database installation”.

13 Install the standby database. See “Install standby database”.

14 Install the standby server. See “Install standby server”.

15 Reinstantiate the database on the standby database station. See “Reinstantiate standby database”.

16 Use a 5620 SAM client to perform sanity testing on the newly redundant 5620 SAM system, as required.





8.4 Conversion to redundancy

This section describes how to convert a standalone 5620 SAM system to a redundant system.



management users









Procedure 8-1 To convert a standalone 5620 SAM system to a redundant system

Perform this procedure to convert a 5620 SAM system in a standalone deployment to a redundant system. This requires the following:

• Converting the standalone main server and database to a primary main server and database

• Installing the standby main server and database software• Reinstantiating the new primary database on the new standby database station

Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses.


• on the current standalone server station:• root• samadmin

• on the station that is to be the standby main server station:• root



1 Make a backup copy of each file that you have created or customized in or under the /opt/5620sam/server/nms and /opt/5620sam/server/jre directories on each server station.

Store the files in a secure location that is unaffected by 5620 SAM conversion activity.

Note 1 — The samadmin user account is created on the standby main server station during this procedure.

Note 2 — The Oracle management user account is created on the standby database station during this procedure.

Note — At the beginning of a 5620 SAM server conversion, the 5620 SAM installation utility backs up specific configuration and log files to a timestamped directory under the installation directory. The utility then deletes directories under the server installation directory. If you have created or customized a file under the installation directory, you risk losing the file unless you back up the file before the conversion to a storage location that is unaffected by the conversion.





2 If the 5620 SAM system manages Small Cell NEs, perform the following steps to back up the Small Cell files.

i Log in to the server station as the samadmin user.


iii Enter the following command:

bash$ /opt/5620sam/nms/server/config/femto/fsconf/fsBackup.sh all path

where path is the directory that is to contain the backup files, and is optional; the default is /smallcell/backup


3 Obtain the following information from the main server station and record it for use during the conversion:

• hostname, which is one of the following:• the hostname specified for the main server station during the previous

5620 SAM software installation or upgrade• the local hostname, if an IP address was specified for the main server station

during the previous 5620 SAM software installation or upgrade• IP addresses

• IP address that the current and new 5620 SAM databases require to reach the main server

• IP address that the 5620 SAM GUI and OSS clients require to reach the main server (public IP address, if NAT is used)

• IP address that 5620 SAM auxiliary servers require to reach the main server• private IP address (if NAT is used)

• root user password

4 Obtain the following information from the database station and record it for use during the conversion:

• hostname• IP addresses

• IP addresses that the current and new 5620 SAM main servers require to reach the database

• IP address that the 5620 SAM auxiliary servers to reach the database• root user password• Oracle database user password• Oracle SYS password

Note — path must not include a trailing slash character (/).




5 If the 5620 SAM deployment includes one or more auxiliary servers, perform the following steps. Otherwise, go to step 7.



iii Click on the Auxiliary Services tab.

6 Perform the following steps for each auxiliary server listed on the form:

i Select an auxiliary server in the list and click on the Properties button. The properties form for the auxiliary server opens.

ii Record the following information for use during the conversion:

• Host Name• Auxiliary Server Type• Server Status• Public IP address• Private IP address, if displayed

iii Close the auxiliary server properties form.

7 If the 5620 SAM deployment includes one or more client delegate servers, perform the following steps. Otherwise, go to step 9.



iii Click on the Client Delegate Servers tab.

8 Perform the following steps for each client delegate server listed on the form:

i Select a client delegate server in the list and click on the Properties button. The properties form for the client delegate server opens.

ii Record the IP Address value for use during the conversion.

iii Close the client delegate server properties form.

9 Close the System Information form, if it is open.

Close 5620 SAM LogViewer

10 Close the 5620 SAM LogViewer application, if it is open.

Caution — If the 5620 SAM LogViewer is running during a 5620 SAM conversion, the conversion fails.





Close client sessions

11 Perform the following steps to close all unrequired open 5620 SAM client sessions.








viii Click on the Search button to refresh the list of open client sessions.

Back up database

12 Perform one of the following to back up the 5620 SAM database.

a Use a 5620 SAM client GUI to back up the database. See the “5620 SAM database management” chapter of the 5620 SAM System Administrator Guide for information about performing database backups using the GUI.

b Use a CLI script to back up the database. Perform the following steps.

i Log in to the database station as the Oracle management user.



Caution 1 — The path of the 5620 SAM database backup directory must not include the 5620 SAM database installation directory, /opt/5620sam/samdb, or data loss may occur.

Caution 2 — Before the 5620 SAM performs a database backup, it deletes the contents of the specified backup directory. Ensure that the backup directory that you specify in this step does not contain files that you want to retain.




iii Enter the following to begin the database backup:

bash$ /opt/5620sam/samdb/install/config/samdb/SAMbackup.sh backup_directory ↵

where backup_directory is the directory that is to contain the database backup

The 5620 SAM backs up the database.

iv Record the backup_directory location.

v Copy the file set from backup_directory to a secure and physically separate location for safekeeping.

Stop server














Disable server daemon

14 Perform the following steps to disable the main server startup daemon. This ensures that the main server does not automatically start in the event of a power disruption during the conversion.


bash$ su - ↵







iii Enter the following to disable the main server daemon:


The next section of the procedure describes the conversion of the standalone 5620 SAM database to the primary database in a redundant deployment.

Stop 5620 SAM database





# cd /etc/rc3.d ↵






Done

Run Oracle pre-installation script


Navigate to the directory that contains the new 5620 SAM installation software.


# cd Linux ↵












3) EXIT


19 Enter 1 ↵.




21 If you accept the default, the following prompt is displayed:




a Specify the default group. Type Yes ↵.

b Specify a different group. Type No ↵, and then return to step 20.

22 If the specified group contains a user, the following prompt is displayed:




a Specify the existing user. Type Yes ↵. The following messages are displayed:



Changing ownership of the directory /opt/5620sam/oracle12r1to username:group.



passwd: Success








Do you want to change the password for the UNIX user oracle? [Yes/No]:

b Specify a different user. Perform the following steps.

i Type No ↵. The following prompt is displayed:


ii Enter a username and press ↵.





Adding username...




passwd: Success




New Password:

iii Type a password and press ↵. The following prompt is displayed:


iv Retype the password and press ↵. The following message is displayed if the password update is successful:


v Go to step 24.








New Password:

























Convert standalone database to primary database

25 Log in to the database station as the root user.









bash$ cd Linux ↵




















35 Select Convert Standalone Database to Primary, as shown in Figure 8-5. Click on the Next button.





36 Select Do not Install Oracle Software, as shown in Figure 8-6. Click on the Next button.


The installer prepares to convert the database, as shown in Figure 8-7.







• Public IP (accessible to servers)• Database User Name (typically samuser)

Figure 8-8 Standalone Database Info




38 Configure the parameters shown in Figure 8-9, then click on the Next button. If the “Enable 5620 SAM Server IP Validation” parameter is selected, only the servers at the specified IP addresses or hostnames can connect to the database.

• Enable 5620 SAM Server IP Validation• Server One IP Address• Server Two IP Address






39 Configure the following parameters shown in Figure 8-10, record the information for use later in the procedure, then click on the Next button:

• Standby IP Address• Standby Instance Name

Figure 8-10 Standby Database Info

The installer prepares to convert the database, as shown in Figure 8-11.






41 You are prompted to begin primary database conversion, as shown in Figure 8-12. Database conversion can take one hour or more, depending on the tablespace configuration. Click on the Start Process button to begin the database conversion.

Figure 8-12 Primary Database Conversion

The next panel displays conversion progress, as shown in Figure 8-13.

Figure 8-13 Primary Database Conversion





42 When the panel in Figure 8-14 is displayed, the 5620 SAM database conversion is complete, but as shown in the panel text, you must run a script to enable automatic database startup.









bash$ exit ↵


The next section of the procedure describes the conversion of the standalone main server to the primary main server.

Convert standalone server to primary server

46 Log in to the standalone server station as the root user.







# who ↵


ii If the samadmin user is listed, close each samadmin user session. See the RHEL documentation for information.



# cd Linux ↵



where

R_r is the release identifier, in the form MAJOR_minor








52 The 5620 SAM server installer opens, as shown in Figure 8-16. The left pane indicates the conversion progress. The right pane displays release information about the software. Click on the Next button.







54 Select Main Server Configuration, as shown in Figure 8-18. Click on the Next button.


55 As shown in Figure 8-19, the installer indicates which release of 5620 SAM software is installed. Verify the information. Click on the Next button.



















58 Configure the following parameters, shown in Figure 8-22, using the recorded values from the primary database conversion. Click on the Next button.

• Primary Database Server IP Address• Primary Database Instance Name (typically samdb)• Database User Password


















































































































• IP Address














































78 Go to step 80.













81 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 8-45. Click on the Install button to begin the server conversion.


The next panel displays conversion progress, as shown in Figure 8-46.






82 When the main server conversion is complete, as shown in Figure 8-47, configure the “Start the 5620 SAM Main Server” parameter to specify whether you want the server to start immediately after the conversion.


83 Click on the Done button to close the server installer. If you specified that the main server is to start after the conversion, the server starts. Initial server startup can take twenty minutes or more.

84 If one of the following is true, perform Procedure 5-1 on the primary main server station:


85 If you specified that the main server is to start immediately after the conversion, perform the following steps to verify that the server is started.


# su - samadmin ↵

Caution — If you need to enable Small Cell management, you must perform additional configuration steps before you start the main server, as described in step 84.

Note — The “Start the 5620 SAM Main Server” parameter is configurable only if you specify a 5620 SAM or 5650 CPAM license file during the conversion.











iii If the command output indicates that the server is not completely started, wait five minutes and then return to step 85 iii.

iv Go to step 87.

86 Perform the following steps to start the 5620 SAM main server manually.













Note — If you did not specify a license file during the conversion, you cannot start the server until you import a license. See the “Software and license configuration procedures” section in the 5620 SAM System Administrator Guide for information about importing a license.








The next section of the procedure describes the enabling of the currently disabled main server startup daemon.

Enable server daemon

88 Perform the following steps to enable the main server startup daemon.


bash$ su - ↵



iii Enter the following to enable the main server daemon:

# mv inactive.5620SAMServerWrapper 5620SAMServerWrapper ↵

Prepare new standby database station for standby database installation


Log in as the root user on the station that is to be the standby database station.




# cd Linux ↵

Caution — Ensure that you run the script included with the new 5620 SAM software. Using a different version of the script may cause the database installation to fail.










3) EXIT


94 Enter 1 ↵.






done
















Adding username...




passwd: Success




New Password:
















INFO: Completed setting ulimit parameters in




/etc/security/limits.conf...


100 When the script execution is complete, enter the following to reboot the station:

# init 6 ↵


Install standby database

101 When the reboot is complete, log in as the root user on the station that is to be the standby database station.

102 Enter the following to switch to the Oracle management user created by the pre-installation script:





bash$ cd Linux ↵

































111 Perform the following steps if the panel in Figure 8-55 is displayed.


















113 As shown in Figure 8-57, Oracle installation details are displayed as the installation progresses. When the installation is complete, Click on the Next button.




















115 Configure the “Public IP (accessible to servers)” parameters shown in Figure 8-59, then click on the Next button.

Figure 8-59 Standby Database Configuration Info



























• Primary IP Address• Primary Instance Name (typically samdb)• Primary SYS Password


120 You are prompted to begin standby database creation, as shown in Figure 8-64. Click on the Start Process button to begin the database creation.















bash$ exit ↵

124 Enter the following to reboot the standby database station:

# init 6 ↵


The next section of the procedure describes the installation of the standby main server.

Install standby server

125 Log in as the root user on the station that is to be the standby server station.







# who ↵


ii If the samadmin user is listed, close each samadmin user session. See the RHEL documentation for information.



# cd Linux ↵








































• Primary Database Server IP Address• Primary Database Instance Name (typically samdb)• Database User Password




























































































147 Configure the “Public IP (accessible to peer server)” parameter shown in Figure 8-84 using the IP address the other main server must use to reach this main server, and click on the Next button.














• IP Address















Note — The parameter values must match the values specified during the standalone main server conversion to a primary main server.

































156 Go to step 158.





























163 Click on the Done button to close the server installer. If you specified that the main server is to start immediately after the installation, the server starts. Initial server startup can take twenty minutes or more.

164 If one of the following is true, perform Procedure 5-1 on the standby main server station:



Caution — If you need to enable Small Cell management, you must perform additional configuration steps before you start the main server, as described in step 164.









New Password:











167 If the 5620 SAM system includes an auxiliary database, perform the following steps.

i Log in to the primary main server station as the samadmin user.

ii Open the /opt/5620sam/server/nms/config/nms-server.xml file for viewing.

iii Locate the following section:

<samauxdb

enabled="true_or_false"

ipaddress="address_list" />

iv Record the true_or_false and address_list values.

v Close the nms-server.xml file.

vi Log in to the standby main server station as the samadmin user.

vii Enter the following to navigate to the main server configuration directory:







viii Enter the following to make a backup copy of the main server configuration file:


ix Open the nms-server.xml file using a plain-text editor such as vi.

x Locate the section that begins with the following tag:

<samauxdb

xi Configure the enabled and ipaddress parameters using the recorded values from the primary main server configuration.

xii Save and close the nms-server.xml file.

168 If you specified that the main server is to start after installation, perform the following steps to verify that the server is started.































The next section of the procedure describes the reinstantiation of the primary database on the standby database station.

Reinstantiate standby database




173 Click on the Yes button. The database reinstantiation begins.


Note — Database reinstantiation can take a long time when there is a large amount of statistics data to transfer.





174 When the Standby Re-instantiation State displays Success, close the System Information form.

175 Use a 5620 SAM GUI client to perform sanity testing of the newly redundant main server and database, as required.




9.1 Overview 9-2

9.2 Conversion to IPv6 procedures list 9-2

9.3 Conversion to IPv6 workflow 9-3

9.4 Conversion to IPv6 preparation 9-4

9.5 Standalone system conversion to IPv6 9-8

9.6 Redundant system conversion to IPv6 9-17





9.1 Overview

This chapter describes the conversion of the communication between 5620 SAM components from IPv4 to IPv6.

Before you attempt to perform a procedure in this chapter, ensure that you understand and comply with the network requirements and restrictions in chapters 1 and 2.

9.2 Conversion to IPv6 procedures list

Table 9-1 lists the procedures required to convert a 5620 SAM system to IPv6.

Table 9-1 5620 SAM IPv6 conversion procedures list

Caution 1 — Alcatel-Lucent supports 5620 SAM system configuration only under the conditions described in chapters 1and 2, and in the 5620 SAM Planning Guide.

Caution 2 — Before you convert a 5620 SAM system to IPv6, you must upgrade the 5620 SAM to the release described in this guide.

Caution 3 — If the system to be converted is a newly upgraded system, ensure that the main server starts and fully initializes before you attempt to perform this procedure. An upgraded main server performs crucial post-upgrade tasks during initialization; a conversion attempt fails if the initialization is incomplete.

Caution 4 — A 5620 SAM system conversion to IPv6 involves a network-management outage, and must be performed only during a scheduled maintenance period of sufficient duration for the conversion.

Note 1 — Before you convert a 5620 SAM system to IPv6, each required IPv6 interface must be plumbed and operational. See the RHEL documentation for information about enabling and configuring an IPv6 interface.

Note 2 — Before you convert a 5620 SAM system to IPv6, each 5620 SAM component must be running and operational.

Procedure Purpose

To perform the pre-conversion tasks Prepare a standalone or redundant 5620 SAM system for conversion to IPv6 by ensuring the correct conditions are in place, gathering the required information, and backing up the configuration files and database.

To convert a standalone 5620 SAM system to IPv6

Configure a standalone 5620 SAM system to use IPv6 for inter-component communication.

To convert a redundant 5620 SAM system to IPV6 Configure a redundant 5620 SAM system to use IPv6 for inter-component communication.




9.3 Conversion to IPv6 workflow

The following is the sequence of high-level actions required to convert a standalone or redundant 5620 SAM system from IPv4 to IPv6 inter-component communication.

1 Perform the pre-conversion tasks. See Procedure 9-1 for more information.

2 Perform the appropriate procedure.

a To convert a standalone 5620 SAM system to IPv6, perform Procedure 9-2.

b To convert a redundant 5620 SAM system to IPv6, perform Procedure 9-3.

3 Perform sanity testing of the new 5620 SAM system using one or more 5620 SAM GUI clients.





9.4 Conversion to IPv6 preparation

This section describes how to prepare for the conversion of a standalone or redundant 5620 SAM system from IPv4 to IPV6. Before you attempt a system conversion, you must collect specific information, ensure that the proper conditions are in place, and back up the 5620 SAM management data; Procedure 9-1 describes the preparation activities.

Procedure 9-1 To perform the pre-conversion tasks

Perform this procedure to prepare a standalone or redundant 5620 SAM system for conversion to IPv6. Ensure that you record the information that you specify during this procedure.


• on each main server station:• root• samadmin


Clear outstanding failed deployments

1 Clear all outstanding failed deployments. See the “To view and manage failed deployments” procedure in the 5620 SAM System Administrator Guide for information about how to clear a failed deployment.


2 Make a backup copy of the /opt/5620sam/server/nms/config/nms-server.xml file on each main server station.

3 Copy the file to a secure location that is unaffected by the conversion.

Note — Command-line examples use the following to represent the CLI prompts:


management users






4 Obtain and record the following information for each 5620 SAM database:

• root user password• Oracle management user name (default value at installation is oracle)• Oracle database user ID (default value at installation is samuser)• Oracle database user password• Oracle SYS password

5 Obtain and record the following information for each main server:

• root user password• samadmin user password

Close unrequired clients

6 Perform the following steps to close all open 5620 SAM client sessions except one.








viii Click on the Search button to refresh the list of open client sessions and ensure that only the current session is listed.






Verify database archive log synchronization

7 If the 5620 SAM system is a redundant deployment, ensure that no database archive log gap exists between the primary and standby databases.

i In the open client GUI, view the Standby DB entry in the status bar.

ii If the entry reads “Database archive log gap”, perform the following steps to reinstantiate the standby database. Otherwise, go to step 8.

iii Choose Administration→System Information from the 5620 SAM main menu. The System Information form opens.

iv Click on the Re-Instantiate Standby button. A dialog box appears.

v Click on the Yes button. The database reinstantiation begins.


vi When the reinstantiation is complete, close the System Information form.

Verify database alignment

8 If the 5620 SAM system is a redundant deployment, ensure that the 5620 SAM database that you want as the primary database is the current primary database.

i In the open client GUI, choose Administration→System Information from the 5620 SAM main menu. The System Information form opens.

ii View the IP Address and Hostname values in the Primary Database Server panel and the Preferred DB setting in the Primary Server panel.

iii If the Preferred DB address does not match the Primary Database Server IP address or hostname, perform a database switchover. See the “5620 SAM database management” chapter of the 5620 SAM System Administrator Guide for information about performing a database switchover.

Note — Database reinstantiation can take a long time when there is a large amount of data to transfer.

Note — This step potentially requires a 5620 SAM database switchover, which can take considerable time.




Back up database

9 Back up the 5620 SAM database. See the “5620 SAM database management” chapter of the 5620 SAM System Administrator Guide for information about performing a database backup.

10 Copy the backup file set to another station for safekeeping.

Note — A 5620 SAM database backup can take considerable time, depending on the database size and tablespace layout.





9.5 Standalone system conversion to IPv6

This section describes the conversion of a standalone 5620 SAM system from IPv4 to IPv6.

Procedure 9-2 To convert a standalone 5620 SAM system to IPv6

Perform this procedure to change the communication between 5620 SAM components in a standalone system from IPv4 to IPv6. Ensure that you record the information that you specify during this procedure.


• on the main server station:• root• samadmin


Update hostname mappings

1 Update the /etc/hosts file on each main server, database, auxiliary server, and client delegate server station to associate the station hostname with the IPv6 address of the station instead of an IPv4 address.

Disable main server daemon

2 Perform the following steps to disable the main server startup daemon. This ensures that the main server does not automatically start in the event of a power disruption during the conversion.

i Log in to the main server station as the root user.


Caution — A 5620 SAM system conversion to IPv6 involves a network-management outage, and must be performed only during a scheduled maintenance period of sufficient duration for the conversion.



management users









Stop main server



# su - samadmin ↵








v The main server is stopped when the following is displayed:


If the command displays a different message, wait five minutes and return to step 3 iv. Do not proceed to the next step until the server is stopped.

Stop database





# cd /etc/rc3.d ↵










Do not proceed until the following is displayed:

Done

Uninstall database

5 Perform Procedure 10-6 to uninstall the 5620 SAM database.

Prepare database station for database restore

6 Copy the backup file set to the database station.

7 Navigate to the directory on the database station that contains the 5620 SAM installation software.


# cd Linux ↵







3) EXIT


Enter 1 ↵.


Caution 1 — Ensure that the Uninstall Oracle Software parameter on the Uninstall Oracle Software panel is not selected.

Caution 2 — Do not perform the final step that describes removing files.

Note — The path to the backup file set must be the same as the path to the file set after creation.




Enter the Oracle dba group name [group]:

Press ↵ to accept the default.

The following message is displayed:





12 Enter Yes ↵.



13 Enter Yes ↵.




WARNING: Oracle user with the specified name already exists locally.

Redefining the primary group and home directory of user username ...




passwd: Success



Do you want to change the password for the user username? [Yes/No]:

Type No ↵.






Messages like the following are displayed as the script execution completes:












Restore database




16 Navigate to the directory on the standby database station that contains the 5620 SAM installation software.


bash$ ./DBConfig_RHEL_R_r_revision.bin ↵



The 5620 SAM database configuration utility opens and displays the Introduction panel.

18 Table 9-2 lists, by panel, the parameters that you must configure; click Next or Install to advance through the panel sequence, as required.

Table 9-2 5620 SAM database restore parameters

Note — A 5620 SAM database restore takes considerable time, depending on the database size.

Panel and parameters Configuration action

Software License Agreement

I accept the terms of the License Agreement

Select this option.

Choose Installation Type

Restore a Database Select this option.

Install Oracle Software

(1 of 2)




Stop auxiliary servers

19 If the 5620 SAM system includes auxiliary servers, perform the following steps on each auxiliary server station.





The auxiliary server stops.

Reconfigure auxiliary servers




iii Navigate to the directory that contains the 5620 SAM installation software.


# cd Linux ↵

Do not install Oracle Software Select this option.

Locate the Backup Directory

— Click Choose to specify the directory that contains the backup file set.

General Database Configuration Info

Public IP (accessible to servers) Specify the IPv6 address that the main server uses to reach the database.

Main Server IP Validation

Server IP Address If the “Enable 5620 SAM Server IP Validation” parameter is selected, specify the public IPv6 address of the main server.

Database Restore

— Click Start Process.

Installation Complete

— Open a console window and run the script named in the panel; click Done when the script execution is complete.


(2 of 2)







whereR_r is the release identifier, in the form MAJOR_minorrevision is the revision identifier, such as R1, R3, or another descriptor

The 5620 SAM server configuration utility opens with the Introduction panel displayed.

vi Table 9-3 lists, by panel, the parameters that you must configure; click Next or Install to advance through the panel sequence, as required.

Table 9-3 Auxiliary server parameters

Reconfigure main server

21 Perform the following steps on the main server station.







Select this option.


Auxiliary Server Configuration Select this option.

Auxiliary Server Address Configuration

Public IP (accessible to servers) Specify the IPv6 address that the main server uses to reach the auxiliary server.

Main Server Configuration

Server IP Address Specify the public IPv6 address of the main server.

Server Configuration for OSS Clients

Public IP (accessible to OSS clients)

Specify the IPv6 address that the OSS clients use to reach the auxiliary server.

Synchronization of Data - panel displayed depending on configuration

Public IP (accessible to peer auxiliary)

Specify the IPv6 address that the other auxiliary server in the auxiliary server pair uses to reach this auxiliary server.

Peer Public IP (accessible to this auxiliary)

Specify the IPv6 address that this auxiliary server uses to reach the other auxiliary server in the auxiliary server pair.


Start the 5620 SAM Auxiliary Server

Ensure that the parameter is not selected, and click Done.





# cd Linux ↵






Table 9-4 Main server parameters




Select this option.


Main Server Configuration Select this option.

Database Configuration

Database Server IP Address Specify the IPv6 address that the main server uses to reach the database.

Main Server Configuration for Auxiliary Servers

Public IP (accessible to auxiliary)

Specify the IPv6 address that the auxiliary servers use to reach the main server.

Auxiliary Servers

— Perform the following for each listed auxiliary server.• Select the auxiliary server and click Remove.• Click Add, and use the form that opens to specify the auxiliary server type and IPv6

address.

Main Server Configuration for Clients

Private IP (accessible only by this server)

Specify the private IPv6 address of the interface that the GUI clients use to reach the main server.The parameter is displayed if “Use Hostname for Communication” is unselected.

Public IP (accessible to clients) Specify the IPv6 address that the GUI clients use to reach the main server.The parameter is displayed if “Use Hostname for Communication” is unselected.

Server Configuration for OSS Clients - panel displayed depending on configuration


Specify the IPv6 address that the OSS clients use to reach the main server.

Client Delegate Servers - panel displayed depending on configuration

(1 of 2)





Start auxiliary servers








The auxiliary server starts.

— For each listed client delegate server, do the following.• Select the client delegate server.• Click Edit.• Configure the IP Address parameter using the public IPv6 address of the client

delegate server.• Click OK.

Mediation Configuration

IPv6 Address Used If required, select the parameter to enable IPv6 network management.

SNMP Trap Receiving IPv6 Address

If you select the IPv6 Address Used parameter, specify the IPv6 address that the devices in the managed network must use to reach this main server.

Notification Listening IP Address

If the “Enable CORBA Notification Service” parameter is enabled, specify an IPv6 interface, if required.


Start the 5620 SAM Main Server Select the parameter and click Done.


(2 of 2)




9.6 Redundant system conversion to IPv6

This section describes the conversion of a redundant 5620 SAM system from IPv4 to IPv6.

Procedure 9-3 To convert a redundant 5620 SAM system to IPV6

Perform this procedure to change the communication between 5620 SAM components in a redundant system from IPv4 to IPv6. Ensure that you record the information that you specify during this procedure.




Update hostname mappings

1 Update the /etc/hosts file on each main server, database, auxiliary server, and client delegate server station to associate the station hostname with the IPv6 address of the station instead of an IPv4 address.

Disable standby main server daemon

2 You must disable the standby main server daemon to ensure that the main server does not automatically start in the event of a power disruption during the conversion.

i Log in to the standby main server station as the root user.


Caution — A 5620 SAM system conversion to IPv6 involves a network-management outage, and must be performed only during a scheduled maintenance period of sufficient duration for the conversion.



management users










Stop standby main server

3 Stop the standby main server application.


# su - samadmin ↵




bash$ ./nmsserver.bash force_stop ↵







Stop standby database

4 Stop the standby database.

i Log in to the standby database station as the root user.



# cd /etc/rc3.d ↵





Do not proceed until the following is displayed:




Done

Uninstall standby database

5 Perform Procedure 10-6 to uninstall the standby database.

Prepare standby database station for database restore

6 Copy the backup file set to the standby database station.



# cd Linux ↵







3) EXIT


Enter 1 ↵.








Note — The path to the backup file set must be the same as the path to the file set after creation on the primary database station.








12 Enter Yes ↵.



13 Enter Yes ↵.









passwd: Success




Type No ↵.

















Restore database











Table 9-5 Standby database restore parameters

Note — A 5620 SAM database restore takes considerable time, depending on the database size.




Select this option.


Restore a Database Select this option.



Locate the Backup Directory

— Click Choose to specify the directory that contains the backup file set.


Public IP (accessible to servers) Specify the IPv6 address that the main servers use to reach the database.

(1 of 2)





Stop reserved auxiliary servers

19 If the 5620 SAM system includes auxiliary servers, perform the following steps on each reserved auxiliary server station.





The auxiliary server stops.

Reconfigure reserved auxiliary servers






# cd Linux ↵





Server One IP Address If the “Enable 5620 SAM Server IP Validation” parameter is selected, specify the public IPv6 address of the standby main server.

Server Two IP Address If the “Enable 5620 SAM Server IP Validation” parameter is selected, specify the public IPv6 address of the primary main server.

Database Restore





(2 of 2)






Table 9-6 Reserved auxiliary server parameters

Reconfigure standby main server

21 Perform the following steps on the standby main server station.





# cd Linux ↵




Select this option.




Public IP (accessible to servers) Specify the IPv6 address that the main servers use to reach the auxiliary server.


Server One IP Address Specify the public IPv6 address of the standby main server.

Server Two IP Address Specify the public IPv6 address of the primary main server.











Ensure that the parameter is not selected, and click Done.










Table 9-7 Standby main server parameters




Select this option.



Primary Database Configuration

Primary Database Server IP Address

Specify the IPv6 address that this main server uses to reach the current standby database.

Standby Database Configuration

Standby Database Server IP Address

Specify the IPv6 address that this main server uses to reach the current primary database.



Specify the IPv6 address that the auxiliary servers must use to reach this main server.

Auxiliary Servers


address.








Main Server Configuration for Peer Server

(1 of 2)




Close GUI client

22 Close the open GUI client.

Close LogViewer

23 Close the LogViewer application on the primary main server, if it is open.

Public IP (accessible to peer server)

Specify the IPv6 address that the peer main server uses to reach this main server.

Synchronization of Data


Specify the IPv6 address that the other main server uses to reach this main server.

Peer Public IP (accessible to this server)

Specify the IPv6 address that this main server uses to reach the other main server.




Peer Main Server Configurations

Peer Server IP Address Specify the IPv6 address that this main server uses to reach the peer main server.

Peer Main Server Configurations for Clients

Peer Server IP Address Specify the IPv6 address that the GUI and OSS clients mus use to reach the peer main server.








Start the 5620 SAM Main Server Ensure that the parameter is not selected, and click Done.


(2 of 2)





Disable primary main server daemon

24 You must disable the primary main server daemon to ensure that the main server does not automatically start in the event of a power disruption during the conversion.

i Log in to the primary main server station as the root user.






Stop primary main server

25 Stop the primary main server application.


# su - samadmin ↵




bash$ ./nmsserver.bash force_stop ↵











Stop primary database

26 Stop the primary database.

i Log in to the primary database station as the root user.



# cd /etc/rc3.d ↵





Do not proceed until the command displays the following text string:

Done

Start former standby main server as primary main server

27 Start the former standby main server, which initializes as the primary main server.

i Enter the following on the standby main server station:

# su - samadmin ↵








If the main server is not completely started, the command may generate exception messages, or display the following as the first line of status information:










Start reserved auxiliary servers








The auxiliary server starts.

Test 5620 SAM system using GUI client

29 Use a GUI client to perform sanity testing of the main server and database.

Uninstall former primary database

30 Perform Procedure 10-6 to uninstall the former primary database.

Note — This is the end of the network management outage.






Stop preferred auxiliary servers

31 If the 5620 SAM system includes auxiliary servers, perform the following steps on each preferred auxiliary server station.






Prepare to install database on former primary database station

32 On the former primary database station, navigate to the directory that contains the 5620 SAM installation software.


# cd Linux ↵







3) EXIT


Enter 1 ↵.













37 Enter Yes ↵.



38 Enter Yes ↵.









passwd: Success




Type No ↵.

















Install standby database on former primary database station




41 Navigate to the directory that contains the 5620 SAM installation software.







Table 9-8 Standby database installation parameters




Select this option.


Install & Configure Primary/Standby Database

Select this option.


Standby Database Install Select this option.



Standby Database Configuration Info

Public IP (accessible to servers) Specify the IPv6 address that each main server uses to reach this database.


Server One IP Address If the “Enable 5620 SAM Server IP Validation” parameter is selected, specify the public IPv6 address of the standby main server.

Server Two IP Address If the “Enable 5620 SAM Server IP Validation” parameter is selected, specify the public IPv6 address of the primary main server.

Auxiliary Servers

(1 of 2)





Reinstantiate primary database on new standby database station

44 Perform the “To reinstantiate a 5620 SAM database using a client GUI” or “To reinstantiate a 5620 SAM database using a CLI” procedure in the 5620 SAM System Administrator Guide.

Reconfigure preferred auxiliary servers

45 If the 5620 SAM system includes auxiliary servers, perform the following steps on each preferred auxiliary server station.





# cd Linux ↵






— For each listed auxiliary server, do the following.• Select the auxiliary server.• Click Edit.• Configure the IP Address parameter using the public IPv6 address of the client



Primary IP Address Specify the public IPv6 address of the primary database.Default: —






(2 of 2)




Table 9-9 Preferred auxiliary server parameters

Reconfigure former primary main server

46 Perform the following steps on the former primary main server station.





# cd Linux ↵







Select this option.




Public IP (accessible to servers) Specify the IPv6 address that the main servers use to reach the auxiliary server.


Server One IP Address Specify the public IPv6 address of the standby main server.

Server Two IP Address Specify the public IPv6 address of the primary main server.











Select the parameter and click Done.







Table 9-10 Former primary main server parameters




Select this option.





Specify the IPv6 address that this main server uses to reach the new standby database.



Specify the IPv6 address that this main server uses to reach the new primary database.



Specify the IPv6 address that the auxiliary servers must use to reach this main server.

Auxiliary Servers


address.










Specify the IPv6 address that the peer main server uses to reach this main server.



Specify the IPv6 address that the other main server uses to reach this main server.


Specify the IPv6 address that this main server uses to reach the other main server.

(1 of 2)








Peer Server IP Address Specify the IPv6 address that this main server uses to reach the peer main server.


Peer Server IP Address Specify the IPv6 address that the GUI and OSS clients mus use to reach the peer main server.








Start the 5620 SAM Main Server Select the parameter and click Done.


(2 of 2)








10.1 Overview 10-2

10.2 System uninstallation procedures list 10-2

10.3 System uninstallation workflow 10-3

10.4 System uninstallation 10-3





10.1 Overview

This chapter describes the uninstallation of the following 5620 SAM system components:

• main server• 5620 SAM database• auxiliary database• auxiliary server• Cflowd auxiliary server• analytics server

See the following chapters for client uninstallation information:


A complete 5620 SAM system uninstallation has the following requirements.

• No 5620 SAM software in the system is running when the uninstallation begins.• The order in which the 5620 SAM components are uninstalled is the reverse of

the order in which they are installed.

10.2 System uninstallation procedures list

Table 10-1 lists the 5620 SAM software uninstallation procedures.

Table 10-1 5620 SAM uninstallation procedures list

Note — The uninstallation of a 5620 SAM component does not remove any associated RHEL iptables chains.

Procedure Purpose

To uninstall the 5620 SAM analytics server software Remove the 5620 SAM analytics server software from a station.

To uninstall the 5620 SAM auxiliary database software Erase an auxiliary database and remove the 5620 SAM auxiliary database software from each auxiliary database station.

To uninstall the 5620 SAM auxiliary server software Remove the 5620 SAM auxiliary server software from a station.

To uninstall the Cflowd auxiliary server software Remove the 5620 SAM Cflowd auxiliary server software from a station.

To uninstall the 5620 SAM main server software Remove the 5620 SAM main server software from a station.

(1 of 2)




10.3 System uninstallation workflow

The following is the sequence of high-level actions required to uninstall the 5620 SAM client, server and database components in a 5620 SAM system.

1 Uninstall the single-user GUI clients; see chapter 14.

2 Uninstall the client delegate servers; see chapter 15.

3 Uninstall the analytics server, if required. See Procedure 10-1.

4 Uninstall the auxiliary database, if required. See Procedure 10-2.

5 Uninstall the auxiliary servers, if required. See Procedure 10-3.

6 Uninstall the Cflowd auxiliary servers, if required. See Procedure 10-4.

7 Uninstall the main server. See Procedure 10-5.

8 Uninstall the 5620 SAM database. See Procedure 10-6.

10.4 System uninstallation

The following procedures describe how to remove the software components of a 5620 SAM system.

Procedure 10-1 To uninstall the 5620 SAM analytics server software

Perform this procedure to remove the 5620 SAM analytics server software from a station.

You require samadmin user privileges on the station to perform this procedure:

1 Log on to the analytics server station as the samadmin user.


To uninstall the 5620 SAM database software Remove the 5620 SAM database software.

Procedure Purpose

(2 of 2)

Note — If you are performing a procedure in this section from a remote terminal, you must ensure the following:









bash$ /opt/5620sam/analytics/bin/AnalyticsAdmin.sh uninstall ↵



THIS ACTION WILL ERASE 5620 SAM Analytics Application INSTALLATION


4 Enter YES ↵. If the analytics server is running, the analytics server is stopped and the following messages are displayed:

Stopping 5620 SAM Analytics Application

5620 SAM Analytics Application is not running

5 The analytics server software uninstallation begins. The uninstallation is complete when the script execution is complete.

6 Remove any files and directories that remain in the analytics server installation directory.


Procedure 10-2 To uninstall the 5620 SAM auxiliary database software

Perform this procedure to erase a 5620 SAM auxiliary database, and remove the auxiliary database software from all stations in the auxiliary database cluster.

You require the following user privileges on the auxiliary database station to perform this procedure:

• dba user• samauxdb

1 Log on to an auxiliary database station as the samauxdb user.



bash$ /opt/5620sam/samauxdb/bin/auxdbAdmin.sh uninstall ↵


Caution — Performing this procedure permanently erases all data in the auxiliary database. Before you perform this procedure, ensure that you have a backup of the auxiliary database, if the data is of value.





THIS ACTION WILL ERASE YOUR DATABASE


4 Enter YES ↵. You are prompted for the dba password.

5 Enter the password.

6 The database is stopped, if it is running, and then removed; the following messages are displayed:

Stopping auxiliary database ...

Dropping auxiliary database ...

Removing data and catalog directories from all nodes

7 The auxiliary database software uninstallation begins. The uninstallation is complete when the script execution is complete.


bash$ /opt/5620sam/samauxdb/bin/auxdbAdmin.sh unconfigure ↵

The script displays the following messages, which include the location of an auxiliary database configuration backup file:


Cluster unconfigured. Old configurations file:

/opt/vertica/config/admintools.conf.unconfigured.nnnnnnnnnn

9 Copy the backup file to another station for safekeeping in the event that you need to restore the auxiliary database configuration.

10 Perform the following steps on each auxiliary database station in the cluster:

i Log in to the station as the root user.


iii Enter the following to remove the auxiliary server packages:

# yum erase vertica samauxdb samjre ↵

The following summary information and prompt are displayed:

Loaded plugins: product-id, refresh-packagekit, subscription-manager

This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

Setting up Remove Process

Resolving Dependencies

--> Running transaction check





---> Package samauxdb.x86_64 0:SAM_R_r_revision-Pp will be erased

---> Package samjre.x86_64 0:SAM_R_r_revision-Pp will be erased

---> Package vertica.x86_64 0:n.n.n-n will be erased

--> Finished Dependency Resolution

Dependencies Resolved

===========================================================================

Package Arch Version Repository Size

===========================================================================

Removing:

samauxdb archive version repository size

samjre archive version repository size

vertica archive version repository size

Transaction Summary

===========================================================================

Remove 3 Package(s)

Installed size: nnnM

Is this ok [y/N]:

iv Enter y ↵. The packages are removed.

v Remove any files and directories that remain in the auxiliary database installation directory.

vi Close the open console windows, as required.

Procedure 10-3 To uninstall the 5620 SAM auxiliary server software

Perform this procedure to remove the 5620 SAM auxiliary server software from a station.




You require the following user privileges on the auxiliary server station to perform this procedure:


Stop auxiliary server

1 Perform the following steps to stop the auxiliary server.







v Enter the following to display the auxiliary server status:



vi The server is stopped when the command displays the following status message:

Auxiliary Server is stopped


Uninstall server

2 Enter the following at the prompt to switch to the root user:

bash$ su - ↵

3 Enter the following to open the 5620 SAM server uninstaller:

# /opt/5620sam/auxserver/Uninstaller/Uninstall_Server_Auxiliary↵

Caution — In a redundant 5620 SAM system, you must uninstall the auxiliary servers in the following order:

• reserved auxiliary server of primary main server• preferred auxiliary server of primary main server







4 The 5620 SAM server uninstaller opens, as shown in Figure 10-2. The left pane indicates uninstallation progress. The right pane indicates the operations that are to take place. Click on the Uninstall button to begin the uninstallation.

Figure 10-2 Uninstall 5620 SAM/5650 CPAM Server




5 Read the warning shown in Figure 10-3. Click on the “Continue with the uninstall process” button to begin the uninstallation.

Figure 10-3 Warning

The uninstaller begins to remove auxiliary server files and directories, as shown in Figure 10-4.






6 When the server uninstallation is complete, as shown in Figure 10-5, click on the Done button to close the server uninstaller.


7 Enter the following to reboot the auxiliary server station:

# init 6 ↵


8 Remove any files and directories that remain in the auxiliary server installation directory.

Procedure 10-4 To uninstall the Cflowd auxiliary server software

Perform this procedure to remove the 5620 SAM Cflowd auxiliary server software from a station.

You require root user privileges on the Cflowd auxiliary server station to perform this procedure.

1 Log in to the Cflowd auxiliary server station as the root user.












# /opt/5620sam/dcp-R_rRn/uninstall/uninstall ↵

The uninstallation begins, and the script displays a series of progress indicators. The following message is displayed when the uninstallation is complete.

Uninstallation Complete.


Procedure 10-5 To uninstall the 5620 SAM main server software

Perform this procedure to remove the 5620 SAM main server software from a station.




Stop server and database

1 Perform the following steps to stop the main server.





Caution 1 — This procedure involves stopping the 5620 SAM server and database software. Ensure that you perform this procedure only during a scheduled maintenance period.

Caution 2 — In a redundant 5620 SAM deployment, to avoid a server activity switch, you must uninstall the main servers in the following order:

• standby main server• primary main server













2 Perform the following steps to stop the database.




# cd /etc/rc3.d ↵






Done

Uninstall server

3 Log in to the 5620 SAM main server station as the root user.


5 Enter the following to open the 5620 SAM server uninstaller:

# /opt/5620sam/server/Uninstaller/Uninstall_Server_Main ↵






6 The 5620 SAM server uninstaller opens, as shown in Figure 10-7. The left pane indicates uninstallation progress. The right pane indicates the operations that are to take place. Click on the Uninstall button to begin the uninstallation.







Figure 10-8 Warning

The uninstaller begins to remove 5620 SAM server files and directories, as shown in Figure 10-9.





8 When the server uninstallation is complete, as shown in Figure 10-10, click on the Done button to close the server uninstaller.


9 Enter the following to reboot the main server station:

# init 6 ↵


10 Remove any files and directories that remain in the main server installation directory.

Procedure 10-6 To uninstall the 5620 SAM database software

Perform this procedure to remove the 5620 SAM database software from a station.

You require the following user privileges on the database station to perform this procedure:

• root• Oracle management

1 Log in to the database station as the root user.


3 Enter the following to switch to the oracle user:

# su - oracle ↵





4 Enter the following to open the 5620 SAM database uninstaller:

bash$ /opt/5620sam/samdb/install/Uninstaller/Uninstall_5620_SAM_Database_Configurator ↵



5 The 5620 SAM database uninstaller opens, as shown in Figure 10-12. The left pane indicates uninstallation progress. The right pane indicates the operations that are to take place. Click on the Next button.





6 If required, select the “Uninstall Oracle software” parameter shown in Figure 10-13 to remove the Oracle software from the database station.

Figure 10-13 Uninstall Oracle Software

7 Click on the Next button to begin the Oracle software uninstallation.

Note — When the installer removes the Oracle software, it does not delete the Oracle base installation directory, because this directory is the home directory of the Oracle management user.






Figure 10-14 Uninstall Oracle Proxy


ii Enter the following to run the script named in the panel text:

# /opt/5620sam/samdb/install/config/samdb/SAMDb_uninstall_root.sh ↵





iv Click on the Uninstall button.The uninstaller begins to remove 5620 SAM database files and directories, as shown in Figure 10-15.


9 When database uninstallation is complete, as shown in Figure 10-16, click on the Done button to close the database uninstaller.



bash$ exit ↵






# init 6 ↵


12 Remove any files and directories that remain in the Oracle installation directory and the database directories.



5650 CPAM system deployment

11 — 5650 CPAM installation

12 — 5650 CPAM upgrade

13 — 5650 CPAM uninstallation







11.1 Overview 11-2

11.2 5650 CPAM installation procedures list 11-2

11.3 5650 CPAM installation 11-3





11.1 Overview

Before you attempt to perform a procedure in this chapter, ensure that you understand and comply with the relevant requirements, considerations, and precautions described in chapter 1 of this guide and in the 5650 CPAM User Guide.

See Appendix D for detailed 5650 CPAM installation parameter descriptions.

11.2 5650 CPAM installation procedures list

Table 11-1 lists the 5650 CPAM server software installation procedures.

Table 11-1 5650 CPAM installation procedures list

Caution — Alcatel-Lucent supports 5650 CPAM software configuration only under the conditions described in chapter 1.

Note — The platform requirements for a 5650 CPAM server are the same as the requirements for a 5620 SAM server. Use the 5620 SAM main server guidelines in chapter 1 as the 5650 CPAM server guidelines.

Procedure Purpose

To install a standalone 5650 CPAM system Install the 5650 CPAM server software in a standalone deployment.

To install a redundant 5650 CPAM system Install the 5650 CPAM server software in a redundant deployment.




11.3 5650 CPAM installation

This section describes how to install the 5650 CPAM software in a standalone or redundant deployment. A 5650 CPAM software installation is typically performed as part of a 5620 SAM main server software installation. Procedure 11-1 describes how to install the 5650 CPAM server software in a standalone deployment. Procedure 11-2 describes how to install the 5650 CPAM server software in a redundant deployment.

The procedures in this section are for use only in the following situations:

• when the 5650 CPAM server is to be used without a 5620 SAM main server• when the 5650 CPAM server is to be used with a 5620 SAM main server that is

installed on a station other than the 5650 CPAM station

Procedure 11-1 To install a standalone 5650 CPAM system

Perform this procedure to install the 5650 CPAM server software on a station in a standalone deployment. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses. You require root user privileges on the 5650 CPAM station to perform this procedure.

1 Log in as the root user on the station that is to be the 5650 CPAM station.



Note 1 — The 5650 CPAM software is automatically installed when you install the 5620 SAM main server software, but is activated only after a valid 5650 CPAM license key is added to the 5650 CPAM configuration.





Caution — Before a 5650 CPAM installation, you must ensure that the iptables and ip6tables firewall on each RHEL station is disabled.







# cd Linux ↵






Figure 11-1 5620 SAM | 5650 CPAM installer




6 The 5650 CPAM server installer opens, as shown in Figure 11-2. The left pane indicates installation progress. The right pane displays release information about the software. Click on the Next button.








8 Select CPAM Server Installation, as shown in Figure 11-4. Click on the Next button.


9 As shown in Figure 11-5, the installer indicates which release of 5650 CPAM software is to be installed. Verify the information. Click on the Next button.





10 Configure the License File parameter shown in Figure 11-6 using the absolute file path of the 5650 CPAM license zip file. Click on the Next button.





















Configure the parameters:


Figure 11-9 CPAM Server Configuration for Auxiliary Servers





14 Configure the “Peer Server IP Address” parameter shown in Figure 11-10 by specifying the IP address that the auxiliary servers must use to reach the other 5650 CPAM server, and then click on the Next button.

Figure 11-10 Peer CPAM Server Configuration for Auxiliary Servers














Note 1 — All IP communication from a 5620 SAM auxiliary server to a 5650 CPAM server must originate from one IP address, which is the address specified in this step. A 5650 CPAM server rejects communication from the auxiliary server if the auxiliary server uses a source address other than the address specified in this step.

Note 2 — When you assign the Preferred and Reserved auxiliary servers for this 5650 CPAM server, there are two configurations to consider.

• The auxiliary server that you specify as the Preferred auxiliary server is the same for each 5650 CPAM server. In this configuration, after a server activity switch, the same auxiliary server is used.

• The auxiliary server that you specify as the Preferred auxiliary server is the Reserved auxiliary server of the other 5650 CPAM server. In this configuration, after a server activity switch, the other auxiliary server is used.





vi The form shown in Figure 11-13 opens. Select a preferred auxiliary server in the upper left panel and the associated reserved auxiliary server in the lower left panel, and click on the “Make Pair from Selected” button. The auxiliary servers move to the list on the right side of the form.









• Server Domain Name (typically 5620sam)This parameter uniquely identifies the 5620 SAM server cluster to which the 5650 CPAM server belongs.




• JNDI Server Port (typically 1099)

Figure 11-14 CPAM Server Configuration for Clients

Note — You must select the parameter if the 5650 CPAM server is to use multiple interfaces for GUI and OSS client communication.

Note — The parameter is configurable when the “NAT (network address translation) Used” parameter” is selected.

Note — The parameter is configurable when the “Use Hostname for Communication” parameter is unselected.






• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5650 CPAM server and the OSS clients.













• IP Address



Note — If NAT is used between the 5650 CPAM server and client delegate servers, specify the public IP address.




20 Perform the following steps to enable communication security between the 5650 CPAM server and clients, and between the 5650 CPAM and auxiliary servers. Otherwise, click on the Next button.





iii Click on the Next button. The 5650 CPAM server copies the files and imports them to the server configuration.







• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5650 CPAM server and the managed network.









22 If you require 5650 CPAM client navigation from a 5620 NM system, select the “Enable Navigation from External Systems” parameter shown in Figure 11-20 and specify the TCP port that the client is to use for accepting navigation requests. Click on the Next button.


23 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 11-21, then click on the Install button to begin the server installation.








24 As shown in Figure 11-23, the 5650 CPAM server is installed as a UNIX daemon. Click on the Next button.





25 When the 5650 CPAM server installation is complete, as shown in Figure 11-24, configure the “Start the 5650 CPAM Server” parameter to specify whether you want the server to start immediately after the installation.


26 Click on the Done button to close the server installer. If you specified that the 5650 CPAM server is to start after installation, the server starts. Initial server startup can take twenty minutes or more.

27 The installer creates a user account called samadmin that is required for 5650 CPAM system administration. You must assign a new password to this user account.

Perform the following steps to assign a new samadmin password.




New Password:

Note — The “Start the 5650 CPAM Server” parameter is configurable only if you specify a 5650 CPAM license file during the procedure.











28 Restart each currently open 5620 SAM GUI client that connects to the 5620 SAM/5650 CPAM server.

Note — The 5650 CPAM functions are not available in a client GUI until the client is restarted.




Procedure 11-2 To install a redundant 5650 CPAM system

Perform this procedure to install the 5650 CPAM server software on a station in a redundant deployment. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses. You require root user privileges on each 5650 CPAM station to perform this procedure.

1 Log in as the root user on the station that is to be the 5650 CPAM station.




# cd Linux ↵





Caution — Before a 5650 CPAM installation, you must ensure that the iptables and ip6tables firewall on each RHEL station is disabled.

Note 1 — You must perform this procedure on each 5650 CPAM station in the redundant deployment.

Note 2 — Command-line examples use the # symbol to represent the RHEL CLI prompt. Do not type the leading # symbol when you enter a command.





The splash screen shown in Figure 11-25 opens


6 The 5650 CPAM server installer opens, as shown in Figure 11-26. The left pane indicates installation progress. The right pane displays release information about the software. Click on the Next button.













9 As shown in Figure 11-29, the installer indicates which release of 5650 CPAM software is to be installed. Verify the information. Click on the Next button.















12 Configure the following parameters shown in Figure 11-32. Click on the Next button.



















































18 If you select the “Enable Database Alignment” parameter shown in Figure 11-39, you must specify the preferred database of this 5650 CPAM server, then click on the Next button.

Database alignment associates each server with the database to which it is most directly connected in terms of network latency. This database is the preferred database of the server. For example, in a 5650 CPAM complex that is geographically dispersed, the preferred database of a server is the database in the same physical facility; typically, the primary server and database are in one facility, and the standby server and database are in another.

When a primary server starts, it verifies that the database to which it connects is the preferred database. If this database is not the preferred database, the server performs a database switchover to reverse the primary and standby database roles. If the switchover is successful, the servers and databases in the 5620 SAM/5650 CPAM complex are aligned. If the switchover fails, each database reverts to the former role, and the server raises an alarm about the failed switchover.


When database alignment is enabled and you perform a server activity switch, the primary server performs an automatic database switchover to maintain alignment with the preferred database.






• Enable Auto Re-Instantiation of Standby DatabaseIf this parameter is selected, the 5650 CPAM server automatically reinstantiates the standby database after a database failover.

• Delay Time After Database Failover (minutes)This parameter specifies how long, in minutes, the 5650 CPAM server waits after database failover completion before it initiates a standby database reinstantiation.






















• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between this 5650 CPAM server and the OSS clients.







22 Configure the “Public IP (accessible to peer server)” parameter shown in Figure 11-43 using the IP address that the other 5650 CPAM server must use to reach this 5650 CPAM server, and click on the Next button.

Figure 11-43 CPAM Server Configuration for Peer Server













• IP Address































Figure 11-49 Peer CPAM Server Configurations









Figure 11-50 Peer CPAM Server Configurations for clients

30 Go to step 32.













33 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 11-53, then click on the Install button to begin the server installation.










35 When the 5650 CPAM server installation is complete, as shown in Figure 11-56, configure the “Start the 5650 CPAM Server” parameter to specify whether you want the server to start immediately after the installation.






36 Click on the Done button to close the server installer. If you specified that the 5650 CPAM server is to start after installation, the server starts. Initial server startup can take twenty minutes or more.

37 The installer creates a user account called samadmin that is required for 5650 CPAM system administration. You must assign a new password to this user account.

Perform the following steps to assign a new samadmin password.




New Password:








Note — The 5650 CPAM functions are not available in a client GUI until the client is restarted.








12.1 Overview 12-2

12.2 5650 CPAM upgrade procedures list 12-2

12.3 5650 CPAM upgrade 12-3





12.1 Overview

Before you attempt to perform a procedure in this chapter, ensure that you understand and comply with the relevant requirements, considerations, and precautions described in chapter 1 of this guide and in the 5650 CPAM User Guide.

See Appendix D for detailed 5650 CPAM upgrade parameter descriptions.

12.2 5650 CPAM upgrade procedures list

Table 12-1 lists the 5650 CPAM server software upgrade procedures.

Table 12-1 5650 CPAM upgrade procedures list

Caution — Alcatel-Lucent supports 5650 CPAM software configuration only under the conditions described in chapter 1.

Note 1 — A 5650 CPAM upgrade requires additional time if the existing checkpoints are retained. The additional time varies, depending on the platform resources, managed network size, and checkpoint schedule. To minimize the upgrade time, you must remove the 5650 CPAM checkpoints before the upgrade,

Note 2 — The platform requirements for a 5650 CPAM server are the same as the requirements for a 5620 SAM server. Use the 5620 SAM main server guidelines in chapter 1 as the 5650 CPAM server guidelines.

Procedure Purpose

To upgrade a standalone 5650 CPAM system Upgrade the 5650 CPAM server software in a standalone deployment.

To upgrade a redundant 5650 CPAM system Upgrade the 5650 CPAM server software in a redundant deployment.




12.3 5650 CPAM upgrade

This section describes how to upgrade the 5650 CPAM software in a standalone or redundant deployment. A 5650 CPAM software upgrade is typically performed as part of a 5620 SAM main server software upgrade. Procedure 12-1 describes how to upgrade the 5650 CPAM server software in a standalone deployment. Procedure 12-2 describes how to upgrade the 5650 CPAM server software in a redundant deployment.

The procedures in this section are for use only in the following situations:

• when the 5650 CPAM server is to be used without a 5620 SAM main server• when the 5650 CPAM server is to be used with a 5620 SAM main server that is

installed on a station other than the 5650 CPAM station

The 5650 CPAM and the 7701 CPAA can function only when the software versions are compatible, for example, 5650 CPAM, Release 8.0 R1 and 7701 CPAA, Release 8.0 R1. If you upgrade one component, you must upgrade the other component. See the current 5650 CPAM release notice for product compatibility information.

Note 1 — The 5650 CPAM software is automatically upgraded when you upgrade the 5620 SAM main server software, but is activated only after a valid 5650 CPAM license key is added to the 5650 CPAM configuration.





Note 1 — When you perform a 5620 SAM upgrade, the 5650 CPAM software is upgraded automatically.

Note 2 — You can use the 5650 CPAM to upgrade the 7701 CPAA, or you can upgrade the 7701 CPAA during a 5620 SAM upgrade to save time.





Procedure 12-1 To upgrade a standalone 5650 CPAM system

Perform this procedure to upgrade the 5650 CPAM server software on a station in a standalone deployment. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses. You require the following user privileges on the 5650 CPAM station to perform this procedure:


1 Use the 5650 CPAM to set a reference for each IGP routing domain, for example, OSPF areas, and IS-IS Level 1 and Level 2 domains. See the 5650 CPAM User Guide for information about setting a reference.

2 Use the 5650 CPAM to set a checkpoint for each IGP routing domain, for example, OSPF areas, and IS-IS Level 1 and Level 2 domains. See the 5650 CPAM User Guide for information about setting a checkpoint.

3 Ensure that each 7701 CPAA TCP connection to the 5650 CPAM is administratively and operationally up.

4 Use the 5650 CPAM to back up the 7701 CPAA configuration. See the 5650 CPAM User Guide for information about backing up a 7701 CPAA configuration.

5 Perform the following steps to stop the 5650 CPAM server application.





Caution — If you plan to implement a RHEL iptables and ip6tables firewall as part of the 5650 CPAM upgrade, you must ensure that the iptables and ip6tables firewall on each station is disabled before the upgrade.

Note — Command-line examples use the following to represent the RHEL CLI prompts:



Note — When you stop the 5650 CPAM server application, you also stop the 5620 SAM server application.




iv Enter the following to stop the 5650 CPAM server application:


v Enter the following to display the 5650 CPAM server status:



vi The 5650 CPAM server is stopped when the command displays the following status message:




a Upgrade the 5650 CPAM server as part of a 5620 SAM system upgrade. Perform the following steps.

i Perform the standalone 5620 SAM system upgrade procedure in chapter 7.

ii Go to step 36.

b Upgrade the 5650 CPAM server using this procedure.

7 Log in to the 5650 CPAM station as the root user.




# cd Linux ↵











12 The 5650 CPAM server installer opens, as shown in Figure 12-2. The left pane indicates upgrade progress. The right pane displays release information about the software. Click on the Next button.













15 As shown in Figure 12-5, the installer indicates which release of 5650 CPAM software is currently installed and the release to which it is to be upgraded. Verify the information. Click on the Next button.

















































































• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between the 5650 CPAM server and the OSS clients.













• IP Address































30 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 12-21, then click on the Install button to begin the server upgrade.













32 When the 5650 CPAM server upgrade is complete, as shown in Figure 12-24, configure the “Start the 5650 CPAM Server” parameter to specify whether you want the server to start immediately after the upgrade.


33 Click on the Done button to close the server installer. If you specified that the 5650 CPAM server is to start after the upgrade, the server starts. Initial server startup can take twenty minutes or more.


Caution — Alcatel-Lucent recommends that you do not configure the server to start immediately after an upgrade.


Note — The new 5650 CPAM functions are not available in a client GUI until the client is restarted.





35 Upgrade the 7701 CPAA.

36 Use the upgraded 5650 CPAM to administratively turn up each 7701 CPAA TCP connection to the 5650 CPAM. After this step, each TCP connection between the 5650 CPAM and each 7701 CPAA is operationally up.

Note — You can use the 5650 CPAM or the 5620 SAM to upgrade the 7701 CPAA, or you can upgrade the CPAA independently during a 5620 SAM upgrade to save time.




Procedure 12-2 To upgrade a redundant 5650 CPAM system

Perform this procedure to upgrade the 5650 CPAM server software on a station in a redundant deployment. Ensure that you record the information that you specify during this procedure, for example, directory names, passwords, and IP addresses.

You require the following user privileges on each 5650 CPAM station to perform this procedure:


1 Use the 5650 CPAM to set a reference for each IGP routing domain, for example, OSPF areas, and IS-IS Level 1 and Level 2 domains. See the 5650 CPAM User Guide for information about setting a reference.

2 Use the 5650 CPAM to set a checkpoint for each IGP routing domain, for example, OSPF areas, and IS-IS Level 1 and Level 2 domains. See the 5650 CPAM User Guide for information about setting a checkpoint.

3 Ensure that each 7701 CPAA TCP connection to the 5650 CPAM is administratively and operationally up.

4 Use the 5650 CPAM to back up the 7701 CPAA configuration. See the 5650 CPAM User Guide for information about backing up a 7701 CPAA configuration.

5 Perform the following steps to stop the 5650 CPAM server application.



Caution — If you plan to implement a RHEL iptables and ip6tables firewall as part of the 5650 CPAM upgrade, you must ensure that the iptables and ip6tables firewall on each station is disabled before the upgrade.

Note 1 — You must perform this procedure on each 5650 CPAM station in the redundant deployment.




Note — When you stop the 5650 CPAM server application, you also stop the 5620 SAM server application.







iv Enter the following to stop the 5650 CPAM server application:


v Enter the following to display the 5650 CPAM server status:



vi The 5650 CPAM server is stopped when the command displays the following status message:




a Upgrade the 5650 CPAM server as part of a 5620 SAM system upgrade. Perform the following steps.

i Perform the redundant 5620 SAM system upgrade procedure in chapter 7.

ii Go to step 45.

b Upgrade the 5650 CPAM server using this procedure.

7 Log in to the 5650 CPAM station as the root user.




# cd Linux ↵










12 The 5650 CPAM server installer opens, as shown in Figure 12-26. The left pane indicates upgrade progress. The right pane displays release information about the software. Click on the Next button.













15 As shown in Figure 12-29, the installer indicates which release of 5650 CPAM software is currently installed and the release to which it is to be upgraded. Verify the information. Click on the Next button.






















18 Configure the following parameters shown in Figure 12-32. Click on the Next button.



















































24 If you select the “Enable Database Alignment” parameter shown in Figure 12-39, you must specify the preferred database of this 5650 CPAM server, then click on the Next button.

Database alignment associates each server with the database to which it is most directly connected in terms of network latency. This database is the preferred database of the server. For example, in a 5620 SAM complex that is geographically dispersed, the preferred database of a server is the database in the same physical facility; typically, the primary server and database are in one facility, and the standby server and database are in another.

When a primary server starts, it verifies that the database to which it connects is the preferred database. If this database is not the preferred database, the server performs a database switchover to reverse the primary and standby database roles. If the switchover is successful, the servers and databases in the 5620 SAM/5650 CPAM complex are aligned. If the switchover fails, each database reverts to the former role, and the server raises an alarm about the failed switchover.


When database alignment is enabled and you perform a server activity switch, the primary server performs an automatic database switchover to maintain alignment with the preferred database.






• Enable Auto Re-Instantiation of Standby DatabaseIf this parameter is selected, the 5650 CPAM server automatically reinstantiates the standby database after a database failover.

• Delay Time After Database Failover (minutes)This parameter specifies how long, in minutes, the 5650 CPAM server waits after database failover completion before it initiates a standby database reinstantiation.






















• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between this 5650 CPAM server and the OSS clients.







28 Configure the “Public IP (accessible to peer server)” parameter shown in Figure 12-43 using the IP address that the other 5650 CPAM server must use to reach this 5650 CPAM server, and click on the Next button.

Figure 12-43 CPAM Server Configuration for Peer Server













• IP Address



















• NAT (network address translation) UsedSelect this parameter only if NAT is to be used between this 5650 CPAM server and the managed network.












Figure 12-49 Peer CPAM Server Configurations










36 Go to step 38.













39 Specify an OSS XML output location (typically /opt/5620sam/server/xml_output), as shown in Figure 12-53, then click on the Install button to begin the server upgrade.













41 When the 5650 CPAM server upgrade is complete, as shown in Figure 12-56, configure the “Start the 5650 CPAM Server” parameter to specify whether you want the server to start immediately after the upgrade.


42 Click on the Done button to close the server installer. If you specified that the 5650 CPAM server is to start after the upgrade, the server starts. Initial server startup can take twenty minutes or more.


Caution — Alcatel-Lucent recommends that you do not configure the server to start immediately after an upgrade.


Note — The new 5650 CPAM functions are not available in a client GUI until the client is restarted.





44 Upgrade the 7701 CPAA.

45 Use the upgraded 5650 CPAM to administratively turn up each 7701 CPAA TCP connection to the 5650 CPAM. After this step, each TCP connection between the 5650 CPAM and each 7701 CPAA is operationally up.

Note — You can use the 5650 CPAM or the 5620 SAM to upgrade the 7701 CPAA, or you can upgrade the CPAA independently during a 5620 SAM upgrade to save time.




13.1 Overview 13-2

13.2 5650 CPAM uninstallation procedures list 13-2

13.3 5650 CPAM uninstallation 13-2





13.1 Overview

This chapter contains information about uninstalling the 5650 CPAM software. 5650 CPAM uninstallation requires that no 5650 CPAM software is running when the uninstallation begins.

13.2 5650 CPAM uninstallation procedures list

Table 13-1 lists the 5650 CPAM software uninstallation procedures.

Table 13-1 5650 CPAM uninstallation procedures list

13.3 5650 CPAM uninstallation

The following procedure describes how to remove the 5650 CPAM software in a standalone or redundant deployment.

Note — The uninstallation of a 5620 SAM component does not remove any associated RHEL iptables chains.

Procedure Purpose

To uninstall the 5650 CPAM software Remove the 5650 CPAM server software from a RHEL station.

Caution — This procedure involves stopping the 5650 CPAM server application, which also stops the 5620 SAM server application. Ensure that you perform this procedure only during a scheduled maintenance period.




You require the following user privileges on the 5650 CPAM server station to perform this procedure:


Procedure 13-1 To uninstall the 5650 CPAM software

Perform this procedure to remove the 5650 CPAM software from a station.

1 Log in to the 5650 CPAM server station as the root user:


3 Perform the following steps to stop the 5650 CPAM/5620 SAM server application.


# su - samadmin ↵



iii Enter the following to stop the 5650 CPAM server application:


iv Enter the following to display the 5650 CPAM server status:



v The 5650 CPAM server is stopped when the command displays the following status message:





Note 2 — If you are performing this procedure from a remote terminal, you must ensure the following:









vi Enter the following to switch back to the root user:

bash$ exit ↵

4 Enter the following to open the 5650 CPAM server uninstaller:

# /opt/5620sam/server/Uninstall/Uninstall_5650_CPAM_Server ↵


Figure 13-1 5620 SAM | 5650 CPAM uninstaller

5 The 5650 CPAM server uninstaller opens, as shown in Figure 13-2. The left pane indicates uninstallation progress. The right pane indicates the operations that are to take place. Click on the Uninstall button to begin the uninstallation.






Figure 13-3 Warning

The uninstaller begins to remove 5650 CPAM components, as shown in Figure 13-4.






7 When the 5650 CPAM server uninstallation is complete, as shown in Figure 13-5, click on the Done button to close the server uninstaller.



9 Restart each currently open 5620 SAM GUI client that connects to the 5650 CPAM server.

Note — The 5650 CPAM functions remain in a 5620 SAM client GUI until the client is restarted.



5620 SAM | 5650 CPAM client deployment

14 — Single-user GUI client deployment

15 — Client delegate server deployment







14.1 Overview 14-2

14.2 Single-user client deployment procedures list 14-6

14.3 Single-user client installation 14-7

14.4 Single-user client upgrade 14-32

14.5 Single-user client uninstallation 14-38





14.1 Overview

This chapter describes single-user GUI client deployment in a standalone or redundant 5620 SAM or 5650 CPAM system. You must comply with the general requirements in chapter 1 and the specific requirements in this chapter before you attempt to deploy a single-user GUI client.

Platform requirementsSingle-user client deployment is supported only on the following platforms:

RHEL

See the 5620 SAM Planning Guide for the following RHEL single-user client platform specifications:

• supported OS release and patch level• supported Oracle JRE version

See chapter 2 for the RHEL OS configuration and package information.

Web-based client installation and uninstallation require an Oracle JRE; OpenJDK software is not supported. Procedure 14-1 describes how to install the Oracle JRE.

Microsoft Windows

The following are the supported Windows versions for single-user clients:

• Windows Server 2008 R2• Windows Server 2012• Windows Server 2012 R2• Windows 7, 32- and 64-bit editions• Windows 8 Enterprise, 64-bit edition• Windows 8.1 Enterprise, 64-bit edition

• RHEL • Microsoft Windows

Note — Before you attempt to install the client software on Windows 8, 8.1, Server 2012, or Server 2012 R2 using the GUI-based installer, you must enable Windows 7 compatibility for the installer executable file. See the OS documentation for information about setting compatibility modes.




Security requirements

The following are the single-user client security requirements for each platform:

• Installation, upgrade, and uninstallation require only local user privileges.• Only the user that installs the client software, or a user with sufficient privileges,

such as root or a local administrator, can start a single-user client.• Uninstallation must be performed by the user that installs the client software, or

by a user with sufficient privileges, such as root or a local administrator.





Procedure 14-1 To install the Oracle JRE on a RHEL client station

Perform this procedure to install the required Oracle JRE on a RHEL station for web-based single-user client deployment.

1 Log in to the client station as the root user.

2 Download the required Oracle JRE package from http://www.oracle.com.


4 Enter the following to install the downloaded package:

# /bin/rpm -ivh path/filename

wherepath is the absolute path to the downloaded filefilename is the name of the downloaded file

5 Enter the following commands in sequence to install the Java component:

# alternatives --install /usr/bin/java java /usr/java/jreR.r.r_nn/bin/java 1

# alternatives --set java /usr/java/jreR.r.r_nn/bin/java

whereR.r.r is the Java release identifier, for example, 1.8.0nn is the JRE update identifier, for example, 40

6 Enter the following commands in sequence to install the javaws component:

# alternatives --install /usr/bin/javaws javaws /usr/java/jreR.r.r_nn/bin/javaws 1

# alternatives --set javaws /usr/java/jreR.r.r_nn/bin/javaws


Note 1 — You require root user privileges on the client station.

Note 2 — A leading # symbol in a CLI command represents the CLI prompt; do not include the leading # symbol when you type a command.

Note 1 — See the 5620 SAM Planning Guide to determine which JRE version the client software requires.

Note 2 — The packages must be in rpm format. Download only a file that has an rpm extension; for example:

• jre-version-linux-i586-rpm, for a 32-bit RHEL OS• jre-version-linux-x64-rpm, for a 64-bit RHEL OS

where version is the Java version identifier, such as 8u40, which represents version 8, update 40





a Enter the following commands in sequence to install the 32-bit Mozilla browser plug-in:

# alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so libjavaplugin.so /usr/java/jreR.r.r_nn/lib/i386/libnpjp2.so 1

# alternatives --set libjavaplugin.so /usr/java/jreR.r.r_nn/lib/i386/libnpjp2.so


b Enter the following commands in sequence to install the 64-bit Mozilla browser plug-in:

# alternatives --install /usr/lib64/mozilla/plugins/libjavaplugin.so libjavaplugin.so.x86_64 /usr/java/jreR.r.r_nn/lib/amd64/libnpjp2.so 1

# alternatives --set libjavaplugin.so /usr/java/jreR.r.r_nn/lib/amd64/libnpjp2.so







14.2 Single-user client deployment procedures list

Table 14-1 lists the single-user GUI client deployment procedures.

Table 14-1 Single-user GUI client deployment procedures

Procedure Purpose

To install the Oracle JRE on a RHEL client station Install the required Oracle JRE for web-based single-user client deployment on a RHEL station.

To install a single-user client on RHEL using a web browser

Use a web browser to install the single-user client software on a RHEL station.

To install a single-user client on RHEL using the client installer

Use a file-based utility to install the single-user client software on a RHEL station.

To install a single-user client on Windows using a web browser

Use a web browser to install the single-user client software on a Microsoft Windows station.

To install a single-user client on Windows using the client installer

Use a file-based utility to install the single-user client software on a Microsoft Windows station.

To upgrade a single-user client on RHEL Upgrade the single-user client software on a RHEL station.

To upgrade a single-user client on Windows Upgrade the single-user client software on a Microsoft Windows station.

To uninstall a RHEL single-user client using a web browser

Use a web browser to remove the single-user client software from a RHEL station.

To uninstall a RHEL single-user client using the client uninstaller

Use a file-based utility to remove the single-user client software from a RHEL station.

To uninstall a Windows single-user client using a web browser

Use a web browser to remove the single-user client software from a Microsoft Windows station.

To uninstall a Windows single-user client using an OS utility

Use an OS utility to remove the single-user client software from a Microsoft Windows station.




14.3 Single-user client installation

This section describes how to install a single-user GUI client for a standalone or redundant 5620 SAM or 5650 CPAM system.

Procedures 14-2 and 14-3 describe how to install a single-user client on RHEL.

Procedures 14-4 and 14-5 describe how to install a single-user client on Windows.

Procedure 14-2 To install a single-user client on RHEL using a web browser

Perform this procedure to install the single-user client software on a RHEL station using a web browser.

1 Perform Procedure 14-1 to install the required Oracle JRE on the client station, if it is not installed.

2 Log in to the client station as a user with local privileges.

3 Verify that you have the required access permissions to create the client installation directory. See your system administrator for information about access permissions.

4 Use a browser on the client station to open one of the following URLs:

• http://server:8085/client, if SSL is not enabled on the main server• https://server:8444/client, if SSL is enabled on the main server

where server is the main server IP address or hostname

Note — The unqualified term “server” in this section refers to a 5620 SAM main server or a 5650 CPAM server.

Note 1 — The main or 5650 CPAM server to which the client connects must be running when you perform this procedure.

Note 2 — You require local user privileges on the client station.

Note — Client installation on RHEL requires an Oracle JRE; the use of an OpenJDK JRE is not supported.





The page shown in Figure 14-1 is displayed.

Figure 14-1 5620 SAM client page

5 Click on the “Install or Launch 5620 SAM Client” link. The form shown in Figure 14-2 is displayed.

Figure 14-2 Opening samclientdesktop.jnlp


i Select the Open it with option.

ii Click on the Choose button and use the form that opens to specify the javaws file of a supported Oracle JRE.

iii Click on the OK button.




7 If a security dialog like the one shown in Figure 14-3 is displayed, click on the Run button.

Figure 14-3 Security Information

8 If the Java setup utility shown in Figure 14-4 opens, the installed Java version requires an update. Click on the Install button. Otherwise, go to step 11.

Figure 14-4 Java Setup - Welcome





The setup utility displays installation progress, as shown in Figure 14-5.

Figure 14-5 Java Setup Progress

9 When the panel shown in Figure 14-6 is displayed, the Java setup is complete. Click on the Close button.

Figure 14-6 Java Setup - Complete

10 If a security dialog like the one in Figure 14-7 is displayed, click on the Run button.

Figure 14-7 Security dialog




11 Perform the following steps when the panel shown in Figure 14-8 is displayed.

Figure 14-8 Install 5620 SAM

i Select the check box to accept the terms of the license agreement.

ii If required, specify a client installation location other than the default.

iii Click on the OK button. The client installation begins, and the panel shown in Figure 14-9 is displayed. The panel uses separate bars to indicate the overall and current task progress.

Figure 14-9 Updating...





When the installation is complete, the client login form opens.

12 Log in to the client.

Procedure 14-3 To install a single-user client on RHEL using the client installer

Perform this procedure to install the single-user client software on a RHEL station using a file-based utility.




4 Navigate to the directory that contains the installation software.


# cd Linux ↵

Note — The default GUI client login credentials are the following:

• Login Name—admin• Password—5620Sam!



Note 3 — If you perform this procedure from a remote terminal, you must ensure the following:



Otherwise, the installer GUI does not open.






# ./ClientInstall_RHEL_SAM_R_r_revision.bin ↵





7 The client installer opens, as shown in Figure 14-11. The left pane lists the installation steps. The right pane displays the current step. Click on the Next button.








9 Select Client Installation and Configuration, as shown in Figure 14-13. Click on the Next button.





10 Specify a base directory in which to install the software, as shown in Figure 14-14. Click on the Next button.

Figure 14-14 Specify the Base Directory for 5620 SAM Client Files

11 As shown in Figure 14-15, the installer indicates which software release is to be installed. Verify the information. Click on the Next button.







a Configure the single-user client for a standalone system.

i Ensure that the “Redundancy Support” parameter is disabled, as shown in Figure 14-16.


ii Configure the “Server IP Address/Hostname” parameter using the IP address or hostname that the client must use to reach the server.

iii Select the “Enable Secure Communication” parameter if SSL is enabled on the server.

iv Click on the Install button.

b Configure the single-user client for a redundant system.

i Select the “Redundancy Support” parameter shown in Figure 14-16.

ii Configure the “Server IP Address/Hostname” parameter using the IP address or hostname that the client must use to reach the primary server.

iii Configure the “Server Two IP Address/Hostname” parameter using the IP address or hostname that the client must use to reach the standby server.

iv Select the “Enable Secure Communication” parameter if SSL is enabled on the servers.

v Click on the Install button.





Figure 14-17 Installing 5620 SAM Client

13 When the installation is complete, as shown in Figure 14-18, configure the “Start the 5620 SAM Client” parameter to specify whether you want the client to start immediately after the installation.






14 Click on the Done button to close the installer. If you specified that the client is to start, the client update utility displays the panel shown in Figure 14-19, which uses separate bars to indicate the overall and current task progress.


When the update is complete, the client login form opens.

15 If you specified that the client is not to start immediately after the installation, you can start the client later by entering the following at a CLI prompt:

path/nms/bin/nmsclient.bash ↵

where path is the client installation location, typically /opt/5620sam/client

The client update utility displays the panel shown in Figure 14-19, which uses separate bars to indicate the overall and current task progress.



Note — You must be logged in as the same user that installed the client.






Procedure 14-4 To install a single-user client on Windows using a web browser

Perform this procedure to install the single-user client software on a Microsoft Windows station using a web browser.



3 See the 5620 SAM Planning Guide to determine which Java version the client installer requires.


a If an earlier version of Java is installed on the client station, ensure that the client station has Internet access so that the installer can automatically download and install the required version.

b If Java is not installed on the client station, visit http://java.com to download and install Java.












6 Click on the “Install or Launch 5620 SAM Client” link. The form shown in Figure 14-21 is displayed.

Figure 14-21 Opening samclientdesktop.jnlp

7 Ensure that “Open with” is selected, then click on the OK button. A Java installer opens and begins to download components.





Figure 14-22 Security Information

9 If the Java setup utility shown in Figure 14-23 opens, the installed Java version requires an update. Click on the Install button. Otherwise, go to step 11.

Figure 14-23 Java Setup - Welcome





The setup utility displays installation progress, as shown in Figure 14-24.

Figure 14-24 Java Setup Progress

10 When the panel shown in Figure 14-25 is displayed, the Java setup is complete. Click on the Close button.

Figure 14-25 Java Setup - Complete





Figure 14-26 Security dialog

12 Perform the following steps when the panel shown in Figure 14-27 is displayed.

Figure 14-27 Install 5620 SAM

i Select the check box to accept the terms of the license agreement.

ii If required, specify a client installation location other than the default.





iii Click on the OK button. The client installation begins, and the panel shown in Figure 14-28 is displayed. The panel uses separate bars to indicate the overall and current task progress.


When the installation is complete, the client login form opens.







Procedure 14-5 To install a single-user client on Windows using the client installer

Perform this procedure to install the single-user client software on a Microsoft Windows station using a file-based utility.


2 Verify that you have the required access permissions to create the client installation directory; see your system administrator for information.

3 Navigate to the directory that contains the client installation software.

4 Double-click on ClientInstall_SAM_R_r_revision.exe


















7 Select Client Installation and Configuration, as shown in Figure 14-32. Click on the Next button.














a Configure the single-user client for a standalone system.

i Ensure that the “Redundancy Support” parameter is not selected, as shown in Figure 14-35.


ii Configure the “Server IP Address/Hostname” parameter using the IP address or hostname that the client must use to reach the server.



b Configure the single-user client for a redundant system.


ii Configure the “Server IP Address/Hostname” parameter using the IP address or hostname that the client must use to reach the primary server.

iii Configure the “Server Two IP Address/Hostname” parameter using the IP address or hostname that the client must use to reach the standby server.









11 When the installation is complete, as shown in Figure 14-37, configure the “Start the 5620 SAM Client” parameter to specify whether you want the client to start immediately after the installation.





12 Click on the Done button to close the installer. If you specified that the client is to start, the client update utility displays the panel shown in Figure 14-38, which uses separate bars to indicate the overall and current task progress.



13 If you specified not to start the client immediately after the installation, you can start the client later by double-clicking on the 5620 SAM Client App desktop icon.

The client update utility displays the panel shown in Figure 14-38, which uses separate bars to indicate the overall and current task progress.



Note — You must be logged in as the same user that installed the client.







14.4 Single-user client upgrade

This section describes how to upgrade a single-user client in a standalone or redundant 5620 SAM or 5650 CPAM system.

Procedure 14-6 describes how to upgrade a single-user client on RHEL.

Procedure 14-7 describes how to upgrade a single-user client on Windows.

Procedure 14-6 To upgrade a single-user client on RHEL

Perform this procedure to upgrade the single-user client software on a RHEL station.

1 Log in to the client station as the user that installed the client software.

2 Close the client GUI, if it is open.


a Double-click on the 5620 SAM Client App desktop icon.

b Use a web browser.

i Open one of the following URLs:




Note — The main or 5650 CPAM server to which the client connects must be upgraded and running when you perform this procedure.






ii Click on the “Install or Launch 5620 SAM Client” link.

The client update utility detects the new software on the server and displays the panel shown in Figure 14-40.

Figure 14-40 Upgrade prompt





4 Click on the Yes button to begin the upgrade.

5 If a security message informs you that the upgrade is blocked, cancel the upgrade and go to step 3 b.

Otherwise, as shown in Figure 14-41, the next panel uses separate bars to indicate the current and overall task progress.


When the upgrade is complete, the client login form opens.





Procedure 14-7 To upgrade a single-user client on Windows

Perform this procedure to upgrade the single-user client software on a Microsoft Windows station.

1 Log in to the client station as the user that installed the client software.











Note — The main or 5650 CPAM server to which the client connects must be upgraded and running when you perform this procedure.








5 If a security message informs you that the upgrade is blocked, cancel the upgrade and go to step 3 b.Otherwise, as shown in Figure 14-44, the next panel uses separate bars to indicate the overall and current task progress.











14.5 Single-user client uninstallation

This section describes how to uninstall a single-user client using a web browser or a local uninstallation utility.

Procedures 14-8 and 14-9 describe how to uninstall a single-user client on RHEL.

Procedures 14-10 and 14-11 describe how to uninstall a single-user client on Windows.

Procedure 14-8 To uninstall a RHEL single-user client using a web browser

Perform this procedure to remove the single-user client software from a RHEL station using a web browser.

1 Log in to the client station as the user that installed the client software, or as the root user.





Note — The installation method determines the uninstallation method; a single-user client installed using a web browser must be uninstalled using a web browser.



Note 2 — If you are not the original installer of the client software, you require root user privileges on the client station.





Figure 14-45 5620 SAM Client page

4 Click on the “Uninstall 5620 SAM Client” link. The form shown in Figure 14-46 is displayed. Ensure that “Open with” is selected, then click on the OK button.

Figure 14-46 Opening samclient_uninstall.jnlp





5 If a security warning like the one shown in Figure 14-47 is displayed, click on the Run button.

Figure 14-47 Warning - Security

6 The client uninstaller opens, as shown in Figure 14-48. Click on the Yes button to begin the uninstallation.

Figure 14-48 Uninstall...




The panel in Figure 14-49 opens and displays the uninstallation progress.


7 The uninstallation is complete when the panel in Figure 14-50 is displayed. Click on the OK button to close the uninstaller.






Procedure 14-9 To uninstall a RHEL single-user client using the client uninstaller

Perform this procedure to remove the single-user client software from a RHEL station using the client uninstallation utility.

1 Log in to the client station as the user that installed the client software, or as the root user.



4 Enter the following to open the client uninstaller:

path/Uninstaller/Uninstall_5620_SAM_Client ↵




Note — If you are not the original installer of the client software, you require root user privileges on the client station.

Note — Ensure that the current working directory is not a directory below the client installation directory, typically /opt/5620sam/client.




5 The client uninstaller opens, as shown in Figure 14-52. The left pane lists the uninstallation steps. The right pane displays the current step. Click on the Uninstall button.

Figure 14-52 Uninstall 5620 SAM Client

6 As shown in Figure 14-53, a warning is displayed. Ensure that the conditions are true, and then click on the “Continue with the uninstall process” button.

Figure 14-53 Warning





The uninstaller removes the software, as shown in Figure 14-54.


7 When the uninstallation is complete, as shown in Figure 14-55, click on the Done button to close the uninstaller.





Procedure 14-10 To uninstall a Windows single-user client using a web browser

Perform this procedure to remove the single-user client software from a Microsoft Windows station using a web browser.

1 Log in to the client station as the user that installed the client software, or as a local administrator.








Note 2 — If you are not the original installer of the client software, you require local administrator privileges on the client station.





4 Click on the “Uninstall 5620 SAM Client” link. The form shown in Figure 14-57 is displayed. Ensure that “Open with” is selected, then click on the OK button.

Figure 14-57 Opening samclient_uninstall.jnlp

5 If a security warning like the one shown in Figure 14-58 is displayed, click on the Run button.

Figure 14-58 Warning - Security




6 The client uninstaller opens, as shown in Figure 14-59. Click on the Yes button to begin the client uninstallation.


The panel in Figure 14-60 opens and displays the uninstallation progress.






7 The client uninstallation is complete when the panel in Figure 14-61 is displayed. Click on the OK button to close the uninstaller.





Procedure 14-11 To uninstall a Windows single-user client using an OS utility

Perform this procedure to remove the single-user client software from a Microsoft Windows station using the Windows program uninstallation utility.

1 Log in to the client station as the user that installed the client software, or as a local administrator.



i Click on Start→Control Panel. The Control Panel window opens.

ii Under the Programs category, click on Uninstall a Program. The Programs and Features window opens.

iii Right-click on 5620 SAM Client and select Uninstall/Change.

iv If a security warning is displayed, click on the Continue button.


Figure 14-62 5620 SAM uninstaller

Note — If you are not the original installer of the client software, you require local administrator privileges on the client station.





4 The client installer opens, as shown in Figure 14-63. The left pane lists the uninstallation steps. The right pane displays the current step. Click on the Uninstall button.


5 As shown in Figure 14-64, a warning is displayed. Ensure that the conditions are true, then click on the “Continue with the uninstall process” button.





6 The uninstaller removes the software, as shown in Figure 14-65.




8 Close the Programs and Features window.








15.1 Overview 15-2

15.2 Client delegate server deployment procedures list 15-4

15.3 Client delegate server installation 15-5

15.4 Client delegate server upgrade 15-26

15.5 Client delegate server uninstallation 15-32





15.1 Overview

This chapter describes client delegate server deployment in a standalone or redundant 5620 SAM or 5650 CPAM system. You must comply with the general requirements in chapter 1 and the specific requirements in this chapter before you attempt to deploy a client delegate server.

Platform requirements

Client delegate server deployment is supported only on the following platform types:

If the 5620 SAM or 5650 CPAM system uses a firewall, you must ensure that the firewall allows traffic to pass between the remote client stations and a client delegate server. See the 5620 SAM Planning Guide for firewall configuration information.

RHEL

A remote station that connects to a RHEL client delegate server requires X.11 or native X display redirection. X-window emulation software is not supported.

See the 5620 SAM Planning Guide for the OS release and patch level requirements of a client delegate server on RHEL.

See chapter 2 for the RHEL OS configuration and package information.

Microsoft Windows

The following are the supported Windows client delegate server platforms:

• Windows Server 2008 R2• Windows Server 2012• Windows Server 2012 R2

Security requirements

Adding a client delegate server to an existing 5620 SAM or 5650 CPAM system requires root and samadmin privileges on each main server station.

RHEL

Client delegate server deployment requires root user privileges.

• RHEL • Microsoft Windows

Note — Before you attempt to install the client delegate server software on Windows Server 2012 or Windows Server 2012 R2, you must enable Windows 7 compatibility for the installer executable file. See the OS documentation for information about setting compatibility modes.




Microsoft Windows

Client delegate server deployment requires local administrator privileges.





15.2 Client delegate server deployment procedures list

Table 15-1 lists the client delegate server deployment procedures.

Table 15-1 Client delegate server deployment procedures

Procedure Purpose

To install a client delegate server on RHEL Install the client delegate server software on a RHEL station.

To install a client delegate server on Windows Install the client delegate server software on a Microsoft Windows station.

To add a client delegate server to an existing system

Add a new client delegate server to an existing 5620 SAM or 5650 CPAM system.

To upgrade a client delegate server on RHEL Upgrade the client delegate server software on a RHEL station.

To upgrade a client delegate server on Windows Upgrade the client delegate server software on a Microsoft Windows station.

To uninstall a RHEL client delegate server Remove the client delegate server software from a RHEL station.

To uninstall a Windows client delegate server Remove the client delegate server software from a Microsoft Windows station.




15.3 Client delegate server installation

This section describes how to install a client delegate server for a standalone or redundant 5620 SAM or 5650 CPAM system.

Procedure 15-1 describes how to install a client delegate server on RHEL.

Procedure 15-2 describes how to install a client delegate server on Windows.

Procedure 15-1 To install a client delegate server on RHEL

Perform this procedure to install the client delegate server software on a RHEL station.

1 Perform Procedure 14-1 to install the Oracle JRE and JDK components on the client delegate server station, if they are not installed.

2 Log in to the client delegate server station as the root user.




# cd Linux ↵


Note 1 — The main or 5650 CPAM server to which the client delegate server connects must be running when you perform this procedure.

Note 2 — You require root user privileges on the client delegate server station.

Note 3 — If you are performing this procedure from a remote terminal, you must ensure the following:



Otherwise, the installer GUI does not open.

Note 4 — A leading # symbol in a CLI command represents the RHEL CLI prompt; do not include the leading # symbol when you type a command.






# ./ClientInstall_RHEL_SAM_R_r_revision.bin ↵












9 Select Client Delegate Installation and Configuration, as shown in Figure 15-4. Click on the Next button.














a Configure the client delegate server for a standalone system.



ii Configure the “Server IP Address” parameter using the IP address or hostname that the client delegate must use to reach the server.



b Configure the client delegate server for a redundant system.


ii Configure the “Server IP Address” parameter using the IP address or hostname that the client delegate server must use to reach the primary server.

iii Configure the “Server Two IP Address” parameter using the IP address or hostname that the client delegate server must use to reach the standby server.









13 When the installation is complete, ensure that the “Start the 5620 SAM Client” parameter is selected, as shown in Figure 15-9.





14 Click on the Done button to close the installer. The client update utility displays the panel shown in Figure 15-10, which uses separate bars to indicate the overall and current task progress.



15 Click on the Cancel button to close the login form.

16 If this is the first server installation on the station, the installer creates a user account called samadmin for system administration. You must assign a password to this user account.

Perform the following steps to assign a samadmin password.




New Password:

ii Enter a password and press ↵.


Confirm Password:

iii Enter the password again and press ↵. The password is changed.

iv Record the password and store it in a secure location.





Configure remote client access

17 A server installation on RHEL creates a RHEL user group named sam. A user that opens a remote client session must belong to the sam user group.

Add each user that requires client access to the sam user group.

18 As required, preserve the GUI preferences of each RHEL single-user client user that is migrating to the client delegate server.

i Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories.

ii Copy all files in the RHEL_home/5620SAM/guiPreference directory to the same directory on the client delegate server station, where RHEL_home is the RHEL user home directory.

19 As required, preserve the GUI preferences of each Windows single-user client user that is migrating to the client delegate server.


ii Copy all files in the Win_home\5620SAM\guiPreference directory to the following directory on the client delegate server station:

RHEL_home/5620SAM/guiPreference

whereWin_home is the Windows user home directory, which is defined in the USERPROFILE environment variableRHEL_home is the RHEL user home directory

20 Perform the following steps on each station that is to open a client GUI session through the client delegate server.

i Open a remote login session on the client delegate server.

ii Configure display redirection from the client delegate server station to the current station.

iii Enter the following to open a client session:

path/nms/bin/nmsclient.bash ↵

where path is the client delegate server installation location, typically /opt/5620sam/client

The client login form opens.

iv Log in to ensure that the GUI opens and is correctly displayed.




Procedure 15-2 To install a client delegate server on Windows

Perform this procedure to install the client delegate server software on a Windows station.

1 Log in to the client delegate server station as a local administrator.

2 Navigate to the directory that contains the client installation software.

3 Double-click on ClientInstall_SAM_R_r_revision.exe





Note 1 — The main or 5650 CPAM server to which the client delegate server connects must be running when you perform this procedure.

Note 2 — You require local administrator privileges on the client delegate server station.












6 Select Client Delegate Installation and Configuration, as shown in Figure 15-14. Click on the Next button.














a Configure the client delegate server for a standalone system.



ii Configure the “Server IP Address” parameter using the IP address or hostname that the client delegate server must use to reach the server.



b Configure the client delegate server for a redundant system.


ii Configure the “Server IP Address” parameter using the IP address or hostname that the client delegate server must use to reach the primary server.

iii Configure the “Server Two IP Address” parameter using the IP address or hostname that the client delegate server must use to reach the standby server.









10 When the installation is complete, ensure that the “Start the 5620 SAM Client” parameter is selected, as shown in Figure 15-19.





11 Click on the Done button to close the installer.The client update utility displays the panel shown in Figure 15-20, which uses separate bars to indicate the overall and current task progress.



12 Click on the Cancel button to close the login form.

Configure remote client access

13 As required, preserve the GUI preferences of each Windows single-user client user that is migrating to the client delegate server.


ii Copy all files in the Win_home\5620SAM\guiPreference directory to the same directory on the client delegate server station, where Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable.

14 As required, preserve the GUI preferences of each RHEL single-user client user that is migrating to the client delegate server.


ii Copy all files in the RHEL_home/5620SAM/guiPreference directory to the following directory on the client delegate server station:





Win_home\5620SAM\guiPreference

whereRHEL_home is the RHEL user home directoryWin_home is the Windows user home directory, which is defined in the USERPROFILE environment variable

15 Open a Windows remote desktop session on the client delegate server station.

16 Double-click on the 5620 SAM Client App desktop icon. The client login form opens.

17 Log in to ensure that the GUI opens and is correctly displayed.

Note — The default client login credentials are the following:





Procedure 15-3 To add a client delegate server to an existing system

Perform this procedure to add a new client delegate server to an existing 5620 SAM or 5650 CPAM system. You must use the server configuration utility to add the client delegate server to each server configuration.

1 If the system is deployed in a standalone configuration, go to step 5.

2 Perform steps 5 to 14 on the standby server, which is called Server B in this procedure.

3 Perform steps 5 to 14 on the primary server, which is called Server A in this procedure.

4 Go to step 16.

5 Log in to the server station as the root user.


7 Perform the following steps to stop the server application.


# su - samadmin ↵



Caution — This procedure requires that you add the client delegate server to each 5620 SAM main server or 5650 CPAM server configuration and restart each server, which is service-affecting. Perform this procedure only during a scheduled maintenance period.

Note 1 — You require the following user privileges on each server station:


Note 2 — CLI commands use the following to represent the CLI prompt:

• #—the prompt for the root user• bash$—the prompt for the samadmin user


Note — After you stop the primary server in step 7, a server activity switch occurs and Server B manages the network.

If required, you can revert to the previous primary and standby roles of Server A and Server B by performing an activity switch in step 15.





iii Enter the following to stop the server application:


iv Enter the following to display the server status:



v The server is stopped when the command displays the following status message:


If the command displays a different message, wait five minutes and then return to step 7 iv.



bash$ exit ↵




# cd Linux ↵









Figure 15-21 5620 SAM server configuration utility

13 Perform the following steps to add the client delegate server to the server configuration.

i Click on the Next button in the “Introduction” panel.

ii Accept the terms of the license agreement in the “Software License Agreement” panel.


iv Choose Main Server Configuration in the “Choose Installation Type” panel.


vi Click on the Next button on each successive panel until the “Additional Server Configuration” panel is displayed.

vii Select the “Client Delegate Server Supported” parameter.

viii Click on the Next button until the “Client Delegate Servers” panel is displayed.

ix Click on the Add button.

x Configure the “IP Address” parameter.

Note — If NAT is used between the server and the client delegate server, you must specify the public IP address of the client delegate server.





xi Configure the Install Directory Path parameter to specify the absolute path of the client installation location on the client delegate server station.

xii Click on the OK button to save the information and close the form.

xiii Click on the Next button in each successive panel until the “Installation Complete” panel is displayed.

xiv Click on the Done button to close the server configuration utility.

14 Perform the following steps to start the server application.


# su - samadmin ↵



iii Enter the following to start the server application:


iv Enter the following to display the server status:



If the server is not completely started, the first line of status information is the following:


The server is completely started when the command returns the one of the following messages:

• standalone server:-- SAM Server is Up

• primary server:-- Primary Server is UP

• standby server:-- Standby Server is UP



Note — If the parameter is not configured, the 5620 SAM uses the default location, which is one of the following:

• /opt/5620sam/client, for a client delegate server on RHEL• C:\5620sam\client, for a client delegate server on Windows




15 To revert to the previous primary and standby server roles in a redundant deployment, perform the following steps.

i Log in to Server B as the samadmin user.


iii Enter the following at the CLI prompt to initiate a server activity switch:


The server activity switch begins. Server B restarts as the standby server, and Server A manages the network as the primary server.

iv Log in to Server A as the samadmin user.

v Open a console window.

vi Enter the following to display the server status:



If the server is not completely started, the first line of status information is the following:


The server is completely started when the command returns the following message:


vii If the command output indicates that the server is not completely started, wait five minutes and then return to step 15 vi.

16 Close the open console windows, as required.





15.4 Client delegate server upgrade

This section describes how to upgrade a client delegate server in a standalone or redundant 5620 SAM or 5650 CPAM system.

Procedure 15-4 describes how to upgrade a client delegate server on RHEL.

Procedure 15-5 describes how to upgrade a client delegate server on Windows.

Procedure 15-4 To upgrade a client delegate server on RHEL

Perform this procedure to upgrade the client delegate server software on a RHEL station.

1 Close each remote client GUI session that the client delegate server hosts.


3 Close the local client GUI, if it is open.








Note 1 — The main or 5650 CPAM server to which the client delegate server connects must be upgraded and running when you perform this procedure.














5 Click on the Yes button to begin the upgrade. As shown in Figure 15-24, the next panel uses separate bars to indicate the current and overall task progress.







Procedure 15-5 To upgrade a client delegate server on Windows

Perform this procedure to upgrade the client delegate server software on a Windows station.


2 Log in to the client delegate server station as the user that installed the client software.








Note — The main or 5650 CPAM server to which the client delegate server connects must be upgraded and running when you perform this procedure.








5 The client update utility detects the new software on the server and displays the panel shown in Figure 15-26.






7 If a security message informs you that the upgrade is blocked, you must cancel the upgrade and go to step 4 b.

Otherwise, as shown in Figure 15-27, the next panel uses separate bars to indicate the overall and current task progress.








15.5 Client delegate server uninstallation

This section describes how to uninstall a client delegate server.

Procedure 15-6 describes how to uninstall a client delegate server on RHEL.

Procedure 15-7 describes how to uninstall a client delegate server on Windows.

Procedure 15-6 To uninstall a RHEL client delegate server

Perform this procedure to remove the client delegate server software from a RHEL station.





5 Enter the following to open the client uninstaller:

# path/Uninstaller/Uninstall_5620_SAM_Client ↵




Note — Ensure that the current working directory is not a directory below the client installation directory, typically /opt/5620sam/client.

























Procedure 15-7 To uninstall a Windows client delegate server

Perform this procedure to remove the client delegate server software from a Windows station.


2 Log in to the client delegate server station as a local administrator.



i Click on Start→Control Panel. The Control Panel window opens.

ii Under the Programs category, click on Uninstall a Program. The Programs and Features window opens.

iii Right-click on 5620 SAM Client and choose Uninstall/Change.

iv If a security warning is displayed, click on the Continue button.


Figure 15-33 5620 SAM uninstaller

Note — You require local administrator privileges on the client delegate server station.
















8 Close the Programs and Features window.



Appendices

A. 5620 SAM installation parameters

B. 5620 SAM upgrade parameters

C. 5620 SAM conversion to redundancy parameters

D. 5650 CPAM installation parameters

E. 5650 CPAM upgrade parameters





Alcatel-Lucent 5620 SAM | 5650 CPAM A-15620 SAM | 5650 CPAMInstallation and Upgrade Guide


A.1 Standalone database and main server installation parameters A-2

A.2 Redundant database and main server installation parameters A-10

A.3 Auxiliary server installation parameters A-30

A.4 Single-user client and client delegate server installation parameters A-33



A-2 Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


A.1 Standalone database and main server installation parameters

Tables A-1 and A-2 list and describe the configurable parameters for a standalone 5620 SAM database and main server installation. The tables are ordered to follow the standalone installation workflows in chapter 6. The parameters in each table are grouped by installer panel in the order that the panels are displayed.

Table A-1 Standalone database installation parameters




You accept the license terms and conditions. You must select this parameter before you can proceed to the next panel.

I do NOT accept the terms of the License Agreement (default)

You do not accept the license terms and conditions. You cannot proceed to the next panel when this parameter is selected.


Install & Configure a Standalone Database (default)

Installs a standalone databaseYou must choose this option.

Restore a Database Restores a database using a backup file set

Upgrade a Database Upgrades a database


Installs a primary or standby database for a redundant 5620 SAM deployment


Install Oracle Software (default)

Installs the Oracle software

Do not install Oracle Software Does not install the Oracle software


Public IP (accessible to servers)

The IP address that the main server must use to reach this databaseDefault: IP address of primary network interface

Database Name The name of the databaseThe name must:• contain 8 or fewer characters• consist of ASCII characters only• have a letter as the first character• not be an Oracle restricted database name; see the appropriate Oracle

documentation for more information

Default: samdb

Instance Name The name that the Oracle software associates with the database processesThe name must:• contain 8 or fewer characters• consist of ASCII characters only• have a letter as the first character

Default: samdb

(1 of 3)




Database User Name The database usernameDefault: samuser

Database User Password The database password, which can be set only during installationThe password value that you specify must meet the following criteria:• The password must be between 4 and 30 characters long.• The password must contain at least three of the following:




Ensure that you record the password for future use.Default: available from Alcatel-Lucent technical support

Confirm Database User Password

General Database Configuration Info (cont.)

Database Listener Port The TCP port on this station that the Oracle database listener is to use to communicate with the main serverDefault: 1523

Database Proxy Port The TCP port on this station that the main server is to use for non-JDBC operationsDefault: 9002

Oracle SYS Password

SYS Password The password that Oracle requires to start the databaseThe password value that you specify must meet the following criteria:• The password must be between 4 and 30 characters long.• The password must contain at least three of the following:




Default: available from Alcatel-Lucent technical support

Confirm SYS Password


Enable 5620 SAM Server IP Validation

If selected, allows only the main server specified by the “SAM Server IP Address” parameter to connect to the databaseDefault: unselected

Server IP Address The IP address of the only main server that is allowed to connect to the databaseThe parameter is configurable when the “Enable 5620 SAM Server IP Validation” parameter is selected.Default: —

Auxiliary Server IP Validation


(2 of 3)





IP Address The IP address or hostname of the auxiliary serverDefault: —

Archive Log Destination

Unlabeled field The directory in which the database is to store the archive logsDatabase transactions are stored in the archive log directory until a database backup is performed. Alcatel-Lucent recommends that you regularly back up the database to avoid filling the partition that contains the archive log directory.Default: /opt/5620sam/samdb/archivelog

Choose the Redo Log Directory

Unlabeled field The directory in which the database is to store the redo logsDefault: /opt/5620sam/samdb/redolog

Accounting Statistics Database Retention Period

Accounting Statistics Data Retention Period

The length of time, in days, that the database is to retain statistics recordsDefault: 1

Data Layout Option

Multiple Tablespace mapping of Stats and Alarm tablespaces (default)

Separate tablespaces for the statistics and alarm data, and one tablespace for other data

Multiple Tablespace mapping of all tablespaces

Separate tablespaces for the statistics and alarm data, and multiple tablespaces for other data

Accounting Statistics Data File Directory

Unlabeled field The directory that is to contain the accounting statistics tablespace filesDefault: /opt/5620sam/samdb/tablespace/statstbs01


(3 of 3)




Table A-2 Standalone main server installation parameters








Main Server Installation (default)

Installs the main server softwareYou must choose this option.

Main Server Configuration Configures the main server software

Auxiliary Server Installation Installs the auxiliary server software

Auxiliary Server Configuration Configures the auxiliary server software

CPAM Server Installation Installs the 5650 CPAM server software

CPAM Server Configuration Configures the 5650 CPAM server software

Specify the Base Directory for 5620 SAM Main Server Files

Unlabeled field The directory in which the main server files are to be installedDefault: /opt/5620sam/server

License Information for 5620 SAM Main Server

License File The absolute file path of the 5620 SAM license zip fileDefault: —

Additional Server Configuration

Redundancy Supported If selected, specifies that the 5620 SAM system is deployed in a redundant configurationYou must leave this parameter unselected.Default: unselected

Auxiliary Server Supported If selected, specifies that the 5620 SAM deployment includes one or more auxiliary serversDefault: unselected

Client Delegate Server Supported

If selected, specifies that the 5620 SAM deployment includes one or more client delegate serversDefault: unselected


Database Server IP Address The IP address that the main server must use to reach the database stationThe value must match the “Public IP (accessible to servers)” value specified on the “General Database Configuration Info (cont.)” panel during the database installation.Default: —

Database Server Port The TCP port on the database station that the main server must use to reach the databaseThe value must match the “Database Listener Port” value specified on the “General Database Configuration Info (cont.)” panel during the database installation.Default: 1523

(1 of 5)





Database Instance Name The name that the Oracle software associates with the database processesThe value must match the “Instance Name” value specified on the “General Database Configuration Info” panel during the database installation.Default: samdb

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “General Database Configuration Info” panel during the database installation.Default: samuser

Database User Password The database passwordThe value must match the “Database User Password” value specified on the “General Database Configuration Info” panel during the database installation.Default: available from Alcatel-Lucent technical support

Database Proxy Port The TCP port on the database station that the main server is to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “General Database Configuration Info (cont.)” panel during the database installation.Default: 9002

Online Database Backup

Online Backup Interval (Hours) How often, in hours, the 5620 SAM is to back up the databaseDefault: 24

Online Backup Destination The backup directory on the database stationAlcatel-Lucent recommends that you do the following:• Specify an Online Backup Destination that can hold at least five times the expected

database size.• Ensure that the available space in the Online Backup Destination is sufficient to

accommodate the database growth associated with network growth.

Default: /opt/5620sam/dbbackup

Number Of Backup Sets The number of database backup sets that the 5620 SAM is to retainThe 5620 SAM creates a separate directory for each backup set. For example, if the Online Backup Destination is /opt/5620sam/dbbackup and the Number Of Backup Sets is 3, the /opt/5620sam/dbbackup directory contains the backupset_1, backupset_2, and backupset_3 subdirectories.Default: 3



The IP address that the auxiliary servers must use to reach the main serverDefault: —

Enable Stats Collection on Auxiliary Servers

If selected, specifies that one or more auxiliary server is to be used for statistics collectionDefault: unselected

Enable Call Trace Collection on Auxiliary Servers

If selected, specifies that one or more auxiliary servers are to be used for call-trace data collectionDefault: unselected

Auxiliary Server Configuration

IP Address The IP address that the main server must use to reach the auxiliary serverDefault: —


(2 of 5)




Type Preferred—specifies that the main server uses this auxiliary server under normal conditionsReserved—specifies that the main server uses this auxiliary server when the Preferred auxiliary server is unavailableDefault: Preferred

Main Server Configuration For Clients

Server Domain Name The unique identifier of the 5620 SAM server clusterDefault: 5620sam

Use Hostname for Communication

If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach the main serverYou must select this parameter if the main server is to use multiple interfaces for GUI and OSS client communication.Default: unselected

NAT (network address translation) Used

If selected, specifies that NAT is used between the main server and the GUI clients, OSS clients, and auxiliary serversDefault: unselected


The IP address that the NAT router uses to reach the main serverThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.Default: IP address of primary network interface

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach the main serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.Default: —

JNDI Server port The TCP port on this station that the GUI clients are to use for EJB JNDI messagingAlcatel-Lucent recommends that you accept the default value unless one of the following is true:• Another application uses the port.• There is a firewall between the clients and the main server.

Default: 1099

Enable AA Stats File Processing If selected, specifies that the 5620 SAM is to collect AA accounting statisticsDefault: unselected

AA Stats File Format Specifes the format of the collected AA accounting statistics filesThe parameter is configurable when the “Enable AA Stats File Processing” parameter is selected.Default: ram

Enable 3GPP OSS Interface If selected, specifies that the 5620 SAM 3GPP OSS interface is to be enabledDefault: unselected



If selected, specifies that NAT is used between the main server and the OSS clientsDefault: unselected


The IP address that the OSS clients must use to reach the main serverDefault: IP address of primary network interface

Client Delegate Servers

IP Address The IP address that the main server must use to reach the client delegate serverDefault: —


(3 of 5)





Install Directory Path The absolute file path of the client installation location on the client delegate server stationDefault: /opt/5620sam/client for RHEL, and C:\5620sam\client for Windows

SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the main server and clients, and between the main and auxiliary serversDefault: unselected

Keystore File The SSL keystore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: —

Keystore Password The SSL keystore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: —

Truststore File The SSL truststore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: /opt/cacerts.trustStore

Truststore Password The SSL truststore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: —

Enable WebDAV access to activation data

If selected, specifies that WebDAV access to eNodeB activation data is enabled on the main server.Default: unselected

License Information for 5650 CPAM Server

Include 5650 CPAM Server License Information

If selected, specifies that a 5650 CPAM is to be integrated with the 5620 SAM systemDefault: unselected

License File The absolute file path of the 5650 CPAM license zip fileThe parameter is configurable when the “Include 5650 CPAM Server License Information” parameter is selected.Default: —



If selected, specifies that NAT is used between the main server and the managed NEs

IPv6 Address Used If selected, specifies that the main server uses IPv6 to manage one or more NEs


The IPv4 address that the managed NEs must use to reach the main serverDefault: IP address of primary network interface


The IPv6 address that the managed NEs use to reach the main serverThe parameter is configurable when the “IPv6 Address Used parameter” is selected.Default: —

SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach the main serverDefault: 162


(4 of 5)




Trap Log Id The SNMP trap log ID that is associated with the main serverDefault: 98

Enable CORBA Notification Service

Specifies whether to enable the service that receives 1830 PSS CORBA notificationsDefault: unselected


The IP address of the interface that the main server uses to receive CORBA notificationsDefault: IP address of primary network interface

Navigation from External Systems

Enable Navigation from External Systems

If selected, enables the forwarding of 5620 SAM client GUI activity to a 5620 NMDefault: unselected

TCP pot for accepting GUI navigation requests

The TCP port on this station that is to accept 5620 NM navigation requestsThe parameter is configurable when the “Enable Navigation from External Systems” parameter is selected.Default: —

XML Output Directory

Unlabeled field The directory that is to contain the output of OSSI file export operationsDefault: /opt/5620sam/server/xml_output


Start the 5620 SAM Main Server If selected, specifies that the main server is to start automatically after the installationDefault: unselected


(5 of 5)





A.2 Redundant database and main server installation parameters

Tables A-3 to A-6 list and describe the configurable parameters for a redundant 5620 SAM database and main server installation. The tables are ordered to follow the redundant installation workflow in chapter 6. The parameters in each table are grouped by installer panel in the order that the panels are displayed.

Table A-3 Primary database installation parameters









Installs a standalone database




Installs a primary or standby database for a redundant 5620 SAM deploymentYou must choose this option.


Primary Database Install (default)

Installs the primary database in a redundant deploymentYou must choose this option.

Convert Standalone Database to Primary

Converts a standalone database to the primary database in a redundant deployment

Standby Database Install Installs the standby database in a redundant deployment



Installs the Oracle softwareYou must choose this option.


Primary Database Configuration Info


The IP address that the main servers must use to reach this databaseDefault: IP address of primary network interface

Database Name The name of the databaseThe name must:• contain 8 or fewer characters• consist of ASCII characters only• have a letter as the first character• not be an Oracle restricted database name; see the appropriate Oracle

documentation for more information

Default: samdb

(1 of 4)




Instance Name The name that the Oracle software associates with the database processes on this stationThe name must:• contain 8 or fewer characters• consist of ASCII characters only• have a letter as the first character

Default: samdb1


Database User Password The database password, which can be set only during installationThe password value that you specify must meet the following criteria:• The password must be between 4 and 30 characters long.• The password must contain at least three of the following:




Ensure that you record the password for future use.Default: available from Alcatel-Lucent technical support

Confirm Database User Password

Primary Database Configuration Info (cont.)

Database Listener Port The TCP port on this station that the Oracle database listener is to use to communicate with the main serversDefault: 1523

Database Proxy Port The TCP port on this station that each main server is to use for non-JDBC operationsDefault: 9002

Database File Server Port The TCP port on this station that the database is to use for file transfers to and from the peer database stationDefault: 9003

Oracle SYS Password

SYS Password The password that Oracle requires to start the databaseThe password value that you specify must meet the following criteria:• The password must be between 4 and 30 characters long.• The password must contain at least three of the following:




Default: available from Alcatel-Lucent technical support

Confirm SYS Password


(2 of 4)







If selected, allows only the main servers specified by the “Server One IP Address” and “Server Two IP Address” parameters to connect to the databaseDefault: unselected

Server One IP Address The IP address of the primary main server that is allowed to connect to this database instanceThe parameter is configurable when the “Enable 5620 SAM Server IP Validation” parameter is selected.Default: —

Server Two IP Address The IP address of the standby main server that is allowed to connect to this database instanceThe parameter is configurable when the “Enable 5620 SAM Server IP Validation” parameter is selected.Default: —



Archive Log Destination

Unlabeled field The directory on this station in which the database is to store the archive logsDatabase transactions are stored in the archive log directory until a database backup is performed. Alcatel-Lucent recommends that you regularly back up the database to avoid filling the partition that contains the archive log directory.Default: /opt/5620sam/samdb/archivelog

Choose the Redo Log Directory

Unlabeled field The directory in which the database is to store the redo logsDefault: /opt/5620sam/samdb/redolog



The length of time, in days, that the database is to retain statistics recordsDefault: 1

Data Layout Option

Multiple Tablespace mapping of Stats and Alarm tablespaces (default)

Separate tablespaces for the statistics and alarm data, and one tablespace for other data

Multiple Tablespace mapping of all tablespaces

Separate tablespaces for the statistics and alarm data, and multiple tablespaces for other data

Accounting Statistics Data File Directory

Unlabeled field The directory that is to contain the accounting statistics tablespace filesDefault: /opt/5620sam/samdb/tablespace/statstbs01

Standby Database Info

Standby IP Address The IP address that each main server and this database must use to reach the peer databaseDefault: —


(3 of 4)




Standby Instance Name The name that the Oracle software associates with the peer database processesThe name must:• contain 8 or fewer characters• consist of ASCII characters only• have a letter as the first character

Default: samdb2

Standby Archive Log Destination

The directory on the peer database station in which the database is to store the archive logsDatabase transactions are stored in the archive log directory until a database backup is performed. Alcatel-Lucent recommends that you regularly back up the database to avoid filling the partition that contains the archive log directory.Default: the directory specified in the “Archive Log Destination” panel


(4 of 4)





Table A-4 Standby database installation parameters
















Installs the primary database in a redundant deployment



Standby Database Install Installs the standby database in a redundant deploymentYou must choose this option.







The IP address that each main server must use to reach this databaseDefault: IP address of primary network interface

Database Proxy Port The TCP port on this station that each main server is to use for non-JDBC operationsDefault: 9002




If selected, allows only the main servers specified by the “Server One IP Address” and “Server Two IP Address” parameters to connect to the databaseDefault: unselected


(1 of 2)







Primary Database Info

Primary IP Address The IP address of the peer databaseDefault: —

Primary Instance Name The name that the Oracle software associates with the peer database processesDefault: samdb1

Primary SYS Password The password that Oracle requires to start the peer database instanceThe value must match the “SYS Password” value specified on the “Oracle SYS Password” panel during the primary database installation.

Primary Database Listener Port The TCP port on the peer database station that the Oracle database listener is to use to communicate with the main serversDefault: 1523

Primary Database Proxy Port The TCP port on the peer database station that each main server is to use for non-JDBC operationsDefault: 9002


(2 of 2)





Table A-5 Primary main server installation parameters




















Redundancy Supported If selected, specifies that the 5620 SAM system is deployed in a redundant configurationYou must select this parameter.Default: unselected






The IP address that this main server must use to reach the primary database stationThe value must match the “Public IP (accessible to servers)” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: —

Primary Database Server Port The TCP port on the primary database station that this main server must use to reach the databaseThe value must match the “Database Listener Port” value specified on the “Primary Database Configuration Info (cont.)” panel during the primary database installation.Default: 1523

(1 of 7)




Primary Database Instance Name

The name that the Oracle software associates with the database processes on this stationThe value must match the “Instance Name” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: samdb1

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: samuser

Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: available from Alcatel-Lucent technical support

Primary Database Proxy Port The TCP port on the primary database station that this main server is to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Primary Database Configuration Info (cont.)” panel during the primary database installation.Default: 9002










The IP address that this main server must use to reach the standby database stationDefault: —

Standby Database Instance Name

The name that the Oracle software associates with the standby database processesDefault: samdb2

Standby Database Proxy Port The TCP port on the standby database station that this main server is to use for non-JDBC operationsDefault: 9002

Enable Database Backup File Synchronization

If selected, specifies that each 5620 SAM database backup file set is copied to the peer database after the backup completesYou must configure this parameter the same on each main server.You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth required for database backup file synchronization.


(2 of 7)







The IP address that the auxiliary servers must use to reach this main serverDefault: —





Peer Main Server Configuration for Auxiliary Servers

Peer Server IP Address The IP address that the auxiliary servers must use to reach the peer main serverDefault: —


IP Address The IP address that this main server must use to reach the auxiliary serverDefault: —

Type Preferred—specifies that this main server uses this auxiliary server under normal conditionsReserved—specifies that this main server uses this auxiliary server when the Preferred auxiliary server is unavailableDefault: Preferred

Database Alignment

Enable Database Alignment If selected, enables automatic database alignmentDefault: unselected

IP_address_1:instance_name (Primary Preferred) (default)

If selected, specifies that the database that is the designated primary database is the preferred database of the primary main serverThe parameter is configurable when the “Enable Database Alignment” parameter is selected.

IP_address_2:instance_name (Standby Preferred)

If selected, specifies that the database that is the designated standby database is the preferred database of the primary main serverThe parameter is configurable when the “Enable Database Alignment” parameter is selected.

Auto Re-Instantiation After Database Failover

Enable Auto Re-Instantiation of Standby Database

If selected, enables automatic reinstantiation of the primary database on the standby database station after a database failoverDefault: unselected

Delay Time After Database Failover (minutes)

The time, in minutes, that is to elapse between database failover completion and the standby database reinstantiationThe parameter is configurable when the “Enable Auto Re-Instantiation of Standby Database” parameter is selected.Default: 60




(3 of 7)





If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach this main serverYou must select this parameter if the main server is to use multiple interfaces for GUI and OSS client communication.Default: unselected


If selected, specifies that NAT is used between this main server and the GUI clients, OSS clients, and auxiliary serversDefault: unselected


The IP address that the NAT router uses to reach this main serverThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.Default: IP address of primary network interface

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach this main serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.Default: —


Default: 1099






If selected, specifies that NAT is used between this main server and the OSS clientsDefault: unselected


The IP address that the OSS clients must use to reach this main serverDefault: IP address of primary network interface



The IP address that the peer main server must use to reach this main serverDefault: —



The IP address that the other main server uses to reach this main serverDefault: IP address of primary network interface


The IP address that this main server uses to reach the other main serverDefault: —



(4 of 7)





IP Address The IP address that this main server must use to reach the client delegate serverDefault: —


SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the main servers and clients, and between the main and auxiliary serversDefault: unselected

Keystore File The SSL keystore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: —


Truststore File The SSL truststore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: /opt/cacerts.trustStore










If selected, specifies that NAT is used between this main server and the managed NEs

IPv6 Address Used If selected, specifies that this main server uses IPv6 to manage one or more NEs


The IPv4 address that the managed NEs must use to reach this main serverDefault: IP address of primary network interface


The IPv6 address that the managed NEs use to reach this main serverThe parameter is configurable when the “IPv6 Address Used” parameter is selected.Default: —


(5 of 7)




SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach this main serverDefault: 162

Trap Log Id The SNMP trap log ID that is associated with this main serverDefault: 98






Peer Server IP Address The IP address that this main server must use to reach the peer main serverDefault: —

Peer Server Trap Log Id The SNMP trap log ID that is associated with the peer main serverDefault: 98

Peer Server SNMP Trap Receiving IPv4 Address

The IPv4 address that the managed NEs must use to reach the peer main serverDefault: —


The IPv6 address that the managed NEs use to reach the peer main serverThe parameter is configurable when the “IPv6 Address Used” parameter on the “Mediation Configuration” panel is selected.Default: —

Peer Server SNMP Trap Receiving Port

The TCP port on the peer main server station that the managed NEs must use to reach the peer main serverDefault: 162


Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is selected.Default: —

Peer Server IP Address The IP address that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is unselected.Default: —

JNDI Peer Server Port The TCP port on the peer main server station that the GUI clients are to use for EJB JNDI messagingAlcatel-Lucent recommends that you accept the default value unless one of the following is true:• Another application uses the port.• There is a firewall between the clients and the main server.

Default: 1099





(6 of 7)












(7 of 7)




Table A-6 Standby main server installation parameters


























The IP address that this main server must use to reach the primary database stationThe value must match the “Public IP (accessible to servers)” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: —

Primary Database Server Port The TCP port on the primary database station that this main server must use to reach the databaseThe value must match the “Database Listener Port” value specified on the “Primary Database Configuration Info (cont.)” panel during the primary database installation.Default: 1523

(1 of 7)






The name that the Oracle software associates with the primary database processesThe value must match the “Instance Name” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: samdb1

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: samuser

Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Primary Database Configuration Info” panel during the primary database installation.Default: available from Alcatel-Lucent technical support

Primary Database Proxy Port The TCP port on the primary database station that this main server is to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Primary Database Configuration Info (cont.)” panel during the primary database installation.Default: 9002












The name that the Oracle software associates with the standby database processesDefault: samdb2






(2 of 7)













IP Address The IP address that this main server must use to reach the auxiliary serverDefault: —

Type Preferred—specifies that this main server uses this auxiliary server under normal conditionsReserved—specifies that this main server uses this auxiliary server when the Preferred auxiliary server is unavailableDefault: Preferred

Database Alignment


IP_address_1:instance_name (Primary Preferred)


IP_address_2:instance_name (Standby Preferred) (default)










(3 of 7)






If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach the main serverYou must select this parameter if the main server is to use multiple interfaces for GUI and OSS client communication.Default: unselected







Default: 1099



















(4 of 7)






SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the main server and clients, and between the main and auxiliary serversDefault: unselected

Keystore File The SSL keystore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Keystore File” value specified in the “SSL Configuration” panel during the primary main server installation.Default: —

Keystore Password The SSL keystore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Keystore Password” value specified in the “SSL Configuration” panel during the primary main server installation.Default: —

Truststore File The SSL truststore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Truststore File” value specified in the “SSL Configuration” panel during the primary main server installation.Default: /opt/cacerts.trustStore

Truststore Password The SSL truststore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Truststore Password” value specified in the “SSL Configuration” panel during the primary main server installation.Default: —












(5 of 7)






The IPv4 address that the managed NEs must use to reach this main serverDefault: IP address of primary network interface



SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach this main serverDefault: 162
















Peer Server Hostname The hostname that the GUI and OSS clients must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is selected.Default: —



Default: 1099



(6 of 7)













(7 of 7)





A.3 Auxiliary server installation parameters

Table A-7 lists and describes the parameters that are configurable during a 5620 SAM auxiliary server installation. The parameters are grouped by installer panel in the order that the panels are displayed.

Table A-7 Auxiliary server installation parameters









Installs the main server software


Auxiliary Server Installation Installs the auxiliary server softwareYou must choose this option.




Specify the Base Directory for 5620 SAM Auxiliary Server Files

Unlabeled field The directory in which the auxiliary server files are to be installedDefault: /opt/5620sam/auxserver




The IP address that each main server must use to reach this auxiliary serverDefault: —

Redundancy Supported On the 5620 SAM Main Server

If selected, specifies that the 5620 SAM system is deployed in a redundant configurationDefault: unselected

Enable Stats Service If selected, specifies that the 5620 SAM auxiliary server is to be used for statistics data collectionDefault: selected

Enable Call Trace Service If selected, specifies that the 5620 SAM auxiliary server is to be used for call-trace data collectionDefault: unselected


(1 of 3)




Server IP Address The IP address that this auxiliary server must use to reach the main server in a standalone deploymentThe parameter is configurable when the “Redundancy Supported On the 5620 SAM Main Server” parameter on the “Auxiliary Server Address Configuration” panel is unselected.Default: —

Server One IP Address The IP address that this auxiliary server must use to reach the primary main server in a redundant deploymentThe parameter is configurable when the “Redundancy Supported On the 5620 SAM Main Server” parameter on the “Auxiliary Server Address Configuration” panel is selected.Default: —

Server Two IP Address The IP address that this auxiliary server must use to reach the standby main server in a redundant deploymentThe parameter is configurable when the “Redundancy Supported On the 5620 SAM Main Server” parameter on the “Auxiliary Server Address Configuration” panel is selected.Default: —



If selected, specifies that NAT is used between the auxiliary server and the OSS clientsDefault: unselected


The IP address that the OSS clients must use to reach the auxiliary serverDefault: IP address of primary network interface

Auxiliary Server Call Trace Configuration

IPv6 Address Used If selected, specifies that an IPv6 address on the auxiliary server, in addition to an IPv4 address, is used for call-trace data collectionDefault: unselected

Call Trace Receiving IPv4 Address

The IPv4 address that the managed devices must use to reach this auxiliary server; if NAT is used, this is a public addressDefault: IP address of primary network interface


The IPv6 address that the managed devices use to reach this auxiliary server; if NAT is used, this is a public addressThe parameter is configurable when the “IPv6 Address Used” parameter is selected.Default: —

Call Trace Receiving Directory The local directory in which call-trace data is storedDefault: /opt/5620sam/calltrace

Debug Trace Receiving Directory

The local directory in which debug trace data is storedDefault: /opt/5620sam/debugtrace


Enable Synchronization of Data If selected, specifies that the collected data on this auxiliary server is synchronized with the data on the other auxiliary server in the auxiliary server pairDefault: selected


The IP address that the other auxiliary server in the auxiliary server pair uses to reach this auxiliary serverDefault: IP address of primary network interface


The IP address that this auxiliary server uses to reach the other auxiliary server in the auxiliary server pairDefault: —

SSL Configuration


(2 of 3)





Enable Secure Communication If selected, specifies that SSL communication security is to be used between the auxiliary and main servers

Keystore File The SSL keystore file that the auxiliary server imports to the auxiliary server configurationDefault: —

Keystore Password The SSL keystore file passwordThis value must match the “Keystore Password” value specified in the “SSL Configuration” panel during the main server installation.Default: —





If selected, specifies that the auxiliary server is to start automatically after the installationDefault: unselected


(3 of 3)




A.4 Single-user client and client delegate server installation parameters

Table A-8 lists and describes the parameters that are configurable during a 5620 SAM single-user client or client delegate server installation. The parameters are grouped by installer panel in the order that the panels are displayed.

Table A-8 Single-user client and client delegate server installation parameters








Client Installation and Configuration (default)

Installs the single-user client software

Client Delegate Installation and Configuration

Installs the client delegate server software

Client Configuration Configures the single-user client or client delegate server software

Specify the Base Directory for 5620 SAM Client Files

Unlabeled field The directory in which the client files are to be installedDefault: /opt/5620sam/client


Server IP Address/Hostname The IP address or hostname that the client software must use to reach the main server in a standalone deployment, or the primary main server in a redundant deploymentDefault: —

Redundancy Support If selected, specifies that the 5620 SAM system is a redundant deploymentDefault: unselected

Server Two IP Address/Hostname

The IP address or hostname that the client software must use to reach the standby main server in a redundant deploymentThe parameter is configurable when the “Redundancy Support” parameter is selected.Default: —

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the client and each main server


Start the 5620 SAM Client If selected, specifies that the client software is to start automatically after the installationDefault: selected






Alcatel-Lucent 5620 SAM | 5650 CPAM B-15620 SAM | 5650 CPAMInstallation and Upgrade Guide


B.1 Standalone database and main server upgrade parameters B-2

B.2 Redundant database and main server upgrade parameters B-8

B.3 Auxiliary server upgrade parameters B-22



B-2 Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


B.1 Standalone database and main server upgrade parameters

Tables B-1 and B-2 list and describe the configurable parameters for a standalone 5620 SAM database and main server upgrade. The tables are ordered to follow the standalone upgrade workflow in chapter 7. The parameters in each table are grouped by installer panel in the order that the panels are displayed.

Table B-1 Standalone database upgrade parameters

Note — Unless stated, the default value for a parameter is the value specified during the previous upgrade or installation.











Upgrade a Database Upgrades a databaseYou must choose this option.



Locate Old Oracle Software Directory

Unlabeled field The directory in which the Oracle software is currently installed

Keep Old Oracle Directory Contents after Upgrade

Specifies whether to keep the existing Oracle software; if the parameter is not selected, the 5620 SAM database installer removes the directory during the upgrade, and the Oracle software must be reinstalled in the event of an upgrade rollback

Get Upgrade Database Info


The IP address that the main server must use to reach the database

Database Name The name of the database

Instance Name The name that the Oracle software associates with the database processes

Database User Name The database username

Database User Password The database password, which is set during installation

Get Upgrade Database Info (cont.)

Database Listener Port The TCP port on this station that the Oracle database listener uses to communicate with the main server

Database Proxy Port The TCP port on this station that the main server is to use for non-JDBC operations

(1 of 2)






If selected, allows only the main server specified by the “SAM Server IP Address” parameter to connect to the database

Server IP Address The IP address of the only main server that is allowed to connect to the databaseThe parameter is configurable when the “Enable 5620 SAM Server IP Validation” parameter is selected.


IP Address The IP address or hostname of the auxiliary server



The length of time, in days, that the database is to retain statistics records

Purge Statistics

Purge All Accounting Statistics Permanently delete the accounting statistics data from the database to reduce the time required for the database upgradeDefault: unselected

Purge All MIB Statistics Permanently delete the MIB statistics data from the database to reduce the time required for the database upgrade

Default: unselected


(2 of 2)





Table B-2 Standalone main server upgrade parameters
















License File The absolute file path of the 5620 SAM license zip fileIf you are upgrading from one major release to another and do not yet have the license for the new release, you must clear the parameter field.Default: the currently active license file


Redundancy Supported If selected, specifies that the 5620 SAM system is deployed in a redundant configurationYou must leave this parameter unselected.

Auxiliary Server Supported If selected, specifies that the 5620 SAM deployment includes one or more auxiliary servers.


If selected, specifies that the 5620 SAM deployment includes one or more client delegate servers.


Database Server IP Address The IP address that the main server must use to reach the database stationThe value must match the “Public IP (accessible to servers)” value specified on the “Get Upgrade Database Info” panel during the database upgrade.

Database Server Port The TCP port on the database station that the main server uses to reach the databaseThe value must match the “Database Listener Port” value specified on the “Get Upgrade Database Info (cont.)” panel during the database upgrade.

Database Instance Name The name that the Oracle software associates with the database processesThe value must match the “Instance Name” value specified on the “Get Upgrade Database Info” panel during the database upgrade.

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Get Upgrade Database Info” panel during the database upgrade.

Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Get Upgrade Database Info” panel during the database upgrade.

(1 of 4)




Database Proxy Port The TCP port on the database station that the main server is to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Get Upgrade Database Info (cont.)” panel during the database upgrade.


Online Backup Interval (Hours) How often, in hours, the 5620 SAM is to back up the database

Online Backup Destination The backup directory on the database station

Number Of Backup Sets The number of database backup sets that the 5620 SAM is to retain



The IP address that the auxiliary servers must use to reach the main server


If selected, specifies that one or more auxiliary server is to be used for statistics collection


If selected, specifies that one or more auxiliary servers are to be used for call-trace data collection


IP Address The IP address that the main server must use to reach the auxiliary server

Type Preferred—specifies that the main server uses this auxiliary server under normal conditionsReserved—specifies that the main server uses this auxiliary server when the Preferred auxiliary server is unavailable


Server Domain Name The unique identifier of the 5620 SAM server cluster


If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach the main serverYou must select this parameter if the main server is to use multiple interfaces for GUI and OSS client communication.


If selected, specifies that NAT is used between the main server and the GUI clients, OSS clients, and auxiliary servers


The IP address that the NAT router uses to reach the main serverThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach the main serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.

JNDI Server port The TCP port on this station that the GUI clients use for EJB JNDI messaging

Enable AA Stats File Processing If selected, specifies that the 5620 SAM is to collect AA accounting statistics

AA Stats File Format Specifes the format of the collected AA accounting statistics filesThe parameter is configurable when the “Enable AA Stats File Processing” parameter is selected.

Enable 3GPP OSS Interface If selected, specifies that the 5620 SAM 3GPP OSS interface is to be enabled



If selected, specifies that NAT is used between the main server and the OSS clients


(2 of 4)






The IP address that the OSS clients must use to reach the main server


IP Address The IP address that the main server must use to reach the client delegate server

Install Directory Path The absolute file path of the client installation location on the client delegate server station

SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the main server and clients, and between the main and auxiliary servers

Keystore File The SSL keystore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.

Keystore Password The SSL keystore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.

Truststore File The SSL truststore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.

Truststore Password The SSL truststore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.


If selected, specifies that WebDAV access to eNodeB activation data is enabled on the main server.



If selected, specifies that a 5650 CPAM is to be integrated with the 5620 SAM system

License File The absolute file path of the 5650 CPAM license zip fileThe parameter is configurable when the “Include 5650 CPAM Server License Information” parameter is selected.If you are upgrading from one major release to another and do not yet have the license for the new release, you must clear the parameter field.Default: the currently active license file



If selected, specifies that NAT is used between the main server and the managed NEs

IPv6 Address Used If selected, specifies that the main server uses IPv6 to manage one or more NEs


The IPv4 address that the managed NEs must use to reach the main server


The IPv6 address that the managed NEs use to reach the main serverThe parameter is configurable when the “IPv6 Address Used” parameter is selected.

SNMP Trap Receiving Port The TCP port that the managed NEs use to reach the main server

Trap Log Id The SNMP trap log ID that is associated with the main server


Specifies whether to enable the service that receives 1830 PSS CORBA notifications


(3 of 4)





The IP address of the interface that the main server uses to receive CORBA notifications



If selected, enables the forwarding of 5620 SAM client GUI activity to a 5620 NM


The TCP port on this station that is to accept 5620 NM navigation requestsThe parameter is configurable when the “Enable Navigation from External Systems” parameter is selected.


Unlabeled field The directory that is to contain the output of OSSI file export operations


Start the 5620 SAM Main Server If selected, specifies that the main server is to start automatically after the upgradeDefault: unselected


(4 of 4)





B.2 Redundant database and main server upgrade parameters

Tables B-3 to B-6 list and describe the configurable parameters for a redundant 5620 SAM database and main server upgrade. The tables are ordered to follow the redundant upgrade workflow in chapter 7. The parameters in each table are grouped by installer panel in the order that the panels are displayed.

Table B-3 Standby database upgrade parameters












Upgrade a Database Upgrades a databaseYou must choose this option.



Locate Old Oracle Software Directory

Unlabeled field The directory in which the Oracle software is currently installed

Keep Old Oracle Directory Contents after Upgrade

Specifies whether to keep the existing Oracle software; if the parameter is not selected, the 5620 SAM database installer removes the directory during the upgrade, and the Oracle software must be reinstalled in the event of an upgrade rollback

Get Upgrade Database Info


If selected, specifies that NAT is used between this database and the main servers


The IP address that the main servers must use to reach this database

Private IP The IP address that the NAT router uses to reach this databaseThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.


Instance Name The name that the Oracle software associates with the database processes on this station


(1 of 2)





Get Upgrade Database Info (cont.)

Database Listener Port The TCP port on this station that the Oracle database listener uses to communicate with the main servers

Database Proxy Port The TCP port on this station that the main servers are to use for non-JDBC operations

Database File Server Port The TCP port on this station that the database is to use for file transfers to and from the peer database station


Primary IP Address The IP address that the main servers use to reach the peer database instance

Primary Instance Name The name that the Oracle software associates with the database processes on the peer database station

Primary SYS Password The password that Oracle requires to start the peer database instanceThe value must match the “SYS Password” value specified on the “Oracle SYS Password” panel during the original primary database installation.



If selected, allows only the main servers specified by the “Server One IP Address” and “Server Two IP Address” parameters to connect to this database instance

Server One IP Address The IP address of the primary main server that is allowed to connect to this database instanceThe parameter is configurable when the “Enable 5620 SAM Server IP Validation” parameter is selected.

Server Two IP Address The IP address of the standby main server that is allowed to connect to this database instanceThe parameter is configurable when the “Enable 5620 SAM Server IP Validation” parameter is selected.


IP Address The IP address or hostname of the auxiliary server



The length of time, in days, that the database is to retain statistics records

Purge Statistics

Purge All Accounting Statistics Permanently delete the accounting statistics data from the database to reduce the time required for the database upgrade

Purge All MIB Statistics Permanently delete the MIB statistics data from the database to reduce the time required for the database upgrade


(2 of 2)





Table B-4 Standby main server upgrade parameters


















Redundancy Supported If selected, specifies that the 5620 SAM system is deployed in a redundant configurationYou must select this parameter.






The IP address that this main server must use to reach the primary database stationThe value must match the “Public IP (accessible to servers)” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

Primary Database Server Port The TCP port on the primary database station that this main server uses to reach the databaseThe value must match the “Database Listener Port” value specified on the “Get Upgrade Database Info (cont.)” panel during the standby database upgrade.


The name that the Oracle software associates with the primary database processesThe value must match the “Instance Name” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

(1 of 5)




Primary Database Proxy Port The TCP port on the primary database station that this main server is to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Get Upgrade Database Info (cont.)” panel during the standby database upgrade.







The IP address that this main server must use to reach the standby database station


The name that the Oracle software associates with the standby database processes

Standby Database Proxy Port The TCP port on the standby database station that this main server is to use for non-JDBC operations


If selected, specifies that each 5620 SAM database backup file set is copied to the peer database after the backup completes

You must configure this parameter the same on each main server.You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth required for database backup file synchronization.



The IP address that the auxiliary servers must use to reach this main server






Peer Server IP Address The IP address that the auxiliary servers must use to reach the peer main server


IP Address The IP address that this main server must use to reach the auxiliary server

Type Preferred—specifies that this main server uses this auxiliary server under normal conditionsReserved—specifies that this main server uses this auxiliary server when the Preferred auxiliary server is unavailable

Database Alignment





(2 of 5)









If selected, enables automatic reinstantiation of the primary database on the standby database station after a database failover


The time, in minutes, that is to elapses between database failover completion and the standby database reinstantiationThe parameter is configurable when the “Enable Auto Re-Instantiation of Standby Database” parameter is selected.




If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach this main serverYou must select this parameter if the main server is to use multiple interfaces for GUI and OSS client communication.


If selected, specifies that NAT is used between this main server and the GUI clients, OSS clients, and auxiliary servers


The IP address that the NAT router uses to reach this main serverThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach this main serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.







If selected, specifies that NAT is used between this main server and the OSS clients


The IP address that the OSS clients must use to reach this main server



The IP address that the peer main server must use to reach this main server



The IP address that the other main server uses to reach this main server


The IP address that this main server uses to reach the other main server



(3 of 5)




IP Address The IP address that this main server must use to reach the client delegate server


SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the main servers and clients, and between the main and auxiliary servers
















The IPv4 address that the managed NEs must use to reach this main server


The IPv6 address that the managed NEs use to reach this main serverThe parameter is configurable when the “IPv6 Address Used” parameter is selected.

SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach this main server

Trap Log Id The SNMP trap log ID that is associated with this main server






Peer Server IP Address The IP address that this main server uses to reach the peer main server


(4 of 5)





Peer Server Trap Log Id The SNMP trap log ID that is associated with the peer main server


The IPv4 address that the managed NEs must use to reach the peer main server


The IPv6 address that the managed NEs use to reach the peer main serverThe parameter is configurable when the “IPv6 Address Used” parameter on the “Mediation Configuration” panel is selected.


The TCP port on the peer main server station that the managed NEs must use to reach the peer main server


Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is selected.

Peer Server IP Address The IP address that the GUI clients, OSS clients, and auxiliary servers use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is unselected.

JNDI Peer Server Port The TCP port on the peer main server station that the GUI clients use for EJB JNDI messaging











(5 of 5)




Table B-5 New standby database installation parameters



























Database Proxy Port The TCP port on this station that the main servers are to use for non-JDBC operationsDefault: 9002




If selected, allows only the main servers specified by the “Server One IP Address” and “Server Two IP Address” parameters to connect to this database instanceDefault: unselected


(1 of 2)









Primary IP Address The IP address of the peer databaseDefault: —

Primary Instance Name The name that the Oracle software associates with the peer database processes

Primary SYS Password The password that Oracle requires to start the peer database instanceThe value must match the “SYS Password” value specified on the “Oracle SYS Password” panel during the original standby database installation.

Primary Database Listener Port The TCP port on the peer database station that the Oracle database listener is to use to communicate with the main serverDefault: 1523

Primary Database Proxy Port The TCP port on the peer database station that the main servers are to use for non-JDBC operationsDefault: 9002


(2 of 2)




Table B-6 Original primary main server upgrade parameters


















Redundancy Supported If selected, specifies that the 5620 SAM system is deployed in a redundant configurationYou must select this parameter.






The IP address that this main server must use to reach the new primary database stationThe value must match the “Public IP (accessible to servers)” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

Primary Database Server Port The TCP port on the new primary database station that this main server uses to reach the databaseThe value must match the “Database Listener Port” value specified on the “Get Upgrade Database Info (cont.)” panel during the standby database upgrade.


The name that the Oracle software associates with the database processes on the new primary database stationThe value must match the “Instance Name” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

(1 of 5)





Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Get Upgrade Database Info” panel during the standby database upgrade.

Primary Database Proxy Port The TCP port on the new primary database station that the main servers are to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Get Upgrade Database Info (cont.)” panel during the standby database upgrade.







The IP address that this main server must use to reach the new standby database station


The name that the Oracle software associates with the database processes on the new standby database station

Standby Database Proxy Port The TCP port on the new standby database station that the main servers are to use for non-JDBC operations











Peer Server IP Address The IP address that the auxiliary servers must use to reach the peer main server




Database Alignment

Enable Database Alignment If selected, enables automatic database alignment




(2 of 5)










The time, in minutes, that is to elapse between database failover completion and the standby database reinstantiationThe parameter is configurable when the “Enable Auto Re-Instantiation of Standby Database” parameter is selected.





















The IP address that the peer main server must use to reach this main server








(3 of 5)







SSL Configuration


Keystore File The SSL keystore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Keystore File” value specified in the “SSL Configuration” panel during the original standby main server upgrade.

Keystore Password The SSL keystore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Keystore Password” value specified in the “SSL Configuration” panel during the original standby main server upgrade.

Truststore File The SSL truststore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Truststore File” value specified in the “SSL Configuration” panel during the original standby main server upgrade.

Truststore Password The SSL truststore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Truststore Password” value specified in the “SSL Configuration” panel during the original standby main server upgrade.















SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach this main server



(4 of 5)









Peer Server IP Address The IP address that this main server must use to reach the peer main server







The TCP port on the peer main server station that the managed NEs use to reach the peer main server


Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer main server

The parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is selected.

Peer Server IP Address The IP address that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is unselected.

JNDI Peer Server Port The TCP port on the peer main server station that the GUI clients use for EJB JNDI messaging











(5 of 5)





B.3 Auxiliary server upgrade parameters

Table B-7 lists and describes the parameters that are configurable during a 5620 SAM auxiliary server upgrade. The parameters are grouped by installer panel in the order that the panels are displayed.

Table B-7 Auxiliary server upgrade parameters












Auxiliary Server Installation Installs the auxiliary server softwareYou must choose this option.







The IP address that each main server must use to reach this auxiliary server

Redundancy Supported On the 5620 SAM Main Server

If selected, specifies that the 5620 SAM system is deployed in a redundant configuration

Enable Stats Service If selected, specifies that the 5620 SAM auxiliary server is used for statistics data collection

Enable Call Trace Service If selected, specifies that the 5620 SAM auxiliary server is used for call-trace data collection


Server IP Address The IP address that this auxiliary server must use to reach the main server in a standalone deploymentThe parameter is configurable when the “Redundancy Supported On the 5620 SAM Main Server” parameter on the “Auxiliary Server Address Configuration” panel is unselected.

(1 of 2)




Server One IP Address The IP address that this auxiliary server must use to reach the primary main server in a redundant deploymentThe parameter is configurable when the “Redundancy Supported On the 5620 SAM Main Server” parameter on the “Auxiliary Server Address Configuration” panel is selected.

Server Two IP Address The IP address that this auxiliary server must use to reach the standby main server in a redundant deploymentThe parameter is configurable when the “Redundancy Supported On the 5620 SAM Main Server” parameter on the “Auxiliary Server Address Configuration” panel is selected.



If selected, specifies that NAT is used between the auxiliary server and the OSS clients


The IP address that the OSS clients must use to reach the auxiliary server

Auxiliary Server Call Trace Configuration

IPv6 Address Used If selected, specifies that an IPv6 address on the auxiliary server, in addition to an IPv4 address, is used for call-trace data collection


The IPv4 address that the managed devices must use to reach this auxiliary server; if NAT is used, this is a public address


The IPv6 address that the managed devices use to reach this auxiliary server; if NAT is used, this is a public addressThe parameter is configurable when the “IPv6 Address Used” parameter is selected.

Call Trace Receiving Directory The local directory in which call-trace data is stored

Debug Trace Receiving Directory

The local directory in which debug trace data is stored


Enable Synchronization of Data If selected, specifies that the collected data on this auxiliary server is synchronized with the data on the other auxiliary server in the auxiliary server pair


The IP address that the other auxiliary server in the auxiliary server pair uses to reach this auxiliary server


The IP address that this auxiliary server uses to reach the other auxiliary server in the auxiliary server pair

SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the auxiliary and main servers

Keystore File The SSL keystore file that the auxiliary server imports to the auxiliary server configuration

Keystore Password The SSL keystore file passwordThis value must match the “Keystore Password” value specified in the “SSL Configuration” panel during the main server installation.





If selected, specifies that the auxiliary server is to start automatically after the upgradeDefault: unselected


(2 of 2)






Alcatel-Lucent 5620 SAM | 5650 CPAM C-15620 SAM | 5650 CPAMInstallation and Upgrade Guide


C.1 5620 SAM conversion to redundancy parameters C-2



C-2 Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


C.1 5620 SAM conversion to redundancy parameters

Tables C-1 to C-4 list and describe the configurable parameters for the conversion of a standalone 5620 SAM database and main server to redundancy. The tables are ordered to follow the conversion workflow in chapter 8. The parameters in each table are grouped by installer panel in the order that the panels are displayed.

Table C-1 Standalone database conversion parameters



















Converts a standalone database to the primary database in a redundant deploymentYou must choose this option.

Standby Database Install Installs the standby database in a redundant deployment



Installs the Oracle software

Do not install Oracle Software Does not install the Oracle softwareYou must choose this option.

Specify the Base Directory for 5620 SAM Database Files

Unlabeled field The directory in which the database files are installed

Specify the Base Directory for Oracle Software

Unlabeled field The directory in which the Oracle files are installed

Standalone Database Info

(1 of 2)







Instance Name The name that the Oracle software associates with the database processes on this station



Standalone Database Info (cont.)

Database Listener Port The TCP port on this station that the Oracle database listener is to use to communicate with each main server

Database Proxy Port The TCP port on this station that the main servers are to use for non-JDBC operations

Database File Server Port The TCP port on this station that the database is to use for file transfers to and from the peer database station



If selected, allows only the main servers specified by the “Server One IP Address” and “Server Two IP Address” parameters to connect to this database instance



Standby Database Info

Standby IP Address The IP address that each main server and this database instance must use to reach the peer database instanceDefault: —

Standby Instance Name The name that the Oracle software associates with the database processes on the peer database stationThe name must:• contain 8 or fewer characters• consist of ASCII characters only• have a letter as the first character

Default: samdb2

Standby Archive Log Destination

The directory on the peer database station in which the database is to store the archive logsDatabase transactions are stored in the archive log directory until a database backup is performed. Alcatel-Lucent recommends that you regularly back up the database to avoid filling the partition that contains the archive log directory.Default: /opt/5620sam/samdb/archivelog


(2 of 2)





Table C-2 Standalone main server conversion parameters










Main Server Configuration Configures the main server softwareYou must choose this option.






Unlabeled field The directory in which the main server files are installed


License File The absolute file path of the 5620 SAM license zip file



Auxiliary Server Supported If selected, specifies that the 5620 SAM deployment includes one or more auxiliary servers


If selected, specifies that the 5620 SAM deployment includes one or more client delegate servers



The IP address that this main server must use to reach the primary database stationThe value must match the “Public IP (accessible to servers)” value specified on the “Standalone Database Info” panel during the standalone database conversion.

Primary Database Server Port The TCP port on the primary database station that this main server must use to reach the databaseThe value must match the “Database Listener Port” value specified on the “Standalone Database Info (cont.)” panel during the standalone database conversion.


The name that the Oracle software associates with the database processes on the primary database stationThe value must match the “Instance Name” value specified on the “Standalone Database Info” panel during the standalone database conversion.

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Standalone Database Info” panel during the standalone database conversion.

(1 of 5)




Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Standalone Database Info” panel during the standalone database conversion.

Primary Database Proxy Port The TCP port on the primary database station that the main servers are to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Standalone Database Info (cont.)” panel during the standalone database conversion.









The name that the Oracle software associates with the database processes on the standby database stationDefault: samdb2

Standby Database Proxy Port The TCP port on the standby database station that the main servers are to use for non-JDBC operationsDefault: 9002















Database Alignment



(2 of 5)


































The IP address that the peer main server must use to reach this main serverDefault: IP address of primary network interface





(3 of 5)









SSL Configuration











License File The absolute file path of the 5650 CPAM license zip fileThe parameter is configurable when the “Include 5650 CPAM Server License Information” parameter is selected.









SNMP Trap Receiving Port The TCP port that the managed NEs use to reach this main server








(4 of 5)





Peer Server IP Address The IP address that this main server must use to reach the peer main server







The TCP port on the peer main server station that the managed NEs must use to reach the peer main server


Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is selected.

Peer Server IP Address The IP address that the GUI and OSS clients must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is unselected.

JNDI Peer Server Port The TCP port on the peer main server station that the GUI clients are to use for EJB JNDI messaging









Start the 5620 SAM Main Server If selected, specifies that the main server is to start automatically after the conversionDefault: unselected


(5 of 5)




Table C-3 Standby database installation parameters


























The IP address that the main servers must use to reach this databaseDefault: IP address of primary network interface

Database Proxy Port The TCP port on this station that the main servers are to use for non-JDBC operationsDefault: 9002




If selected, allows only the main servers specified by the “Server One IP Address” and “Server Two IP Address” parameters to connect to this database instanceDefault: unselected


(1 of 2)






Auxiliary Servers



Primary IP Address The IP address that each main server must use to reach the peer database stationDefault: —

Primary Instance Name The name that the Oracle software associates with the database processes on the peer database stationDefault: samdb

Primary SYS Password The password that Oracle requires to start the databaseDefault: available from Alcatel-Lucent technical support

Primary Database Listener Port The TCP port on the peer database station that the Oracle database listener uses to communicate with each main serverDefault: 1523

Primary Database Proxy Port The TCP port on the peer database station that the main servers are to use for non-JDBC operationsDefault: 9002


(2 of 2)




Table C-4 Standby main server installation parameters




















Redundancy Supported If selected, specifies that the 5620 SAM system is deployed in a redundant configurationYou must choose this option.Default: unselected






The IP address that this main server must use to reach the primary database stationThe value must match the Public IP (accessible to servers)” value specified on the “Standalone Database Info” panel during the standalone database conversion.Default: —

Primary Database Server Port The TCP port on the primary database station that this main server must use to reach the databaseThe value must match the “Database Listener Port” value specified on the “Standalone Database Info (cont.)” panel during the standalone database conversion.Default: 1523

(1 of 7)






The name that the Oracle software associates with the database processes on the primary database stationThe value must match the “Instance Name” value specified on the “Standalone Database Info” panel during the standalone database conversion.Default: samdb

Database User Name The database usernameThe value must match the “Database User Name” value specified on the “Standalone Database Info” panel during the standalone database conversion.Default: samuser

Database User Password The database passwordThe value must match the “Database User Password” value specified on the “Standalone Database Info” panel during the standalone database conversion.Default: available from Alcatel-Lucent technical support

Primary Database Proxy Port The TCP port on the primary database station that this main server is to use for non-JDBC operationsThe value must match the “Database Proxy Port” value specified on the “Standalone Database Info (cont.)” panel during the standalone database conversion.Default: 9002















(2 of 7)
















IP Address The IP address that each main server must use to reach the auxiliary serverDefault: —

Type Preferred—specifies that the main server uses this auxiliary server under normal conditionsReserved—specifies that the main server uses this auxiliary server when the Preferred auxiliary server is unavailableDefault: Preferred

Database Alignment













(3 of 7)







If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach this main serverYou must select this parameter if the main server is to use multiple interfaces for GUI and OSS client communication.Default: unselected







Default: 1099


















(4 of 7)







SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the main servers and clients, and between the main and auxiliary serversDefault: unselected

Keystore File The SSL keystore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Keystore File” value specified in the “SSL Configuration” panel during the standalone main server conversion to a primary main server.


This value must match the “Keystore Password” value specified in the “SSL Configuration” panel during the standalone main server conversion to a primary main server.

Truststore File The SSL truststore file that the main server imports to the main server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Truststore File” value specified in the “SSL Configuration” panel during the standalone main server conversion to a primary main server.

Truststore Password The SSL truststore file passwordThe parameter is configurable when the “Enable Secure Communication” parameter is selected.This value must match the “Truststore Password” value specified in the “SSL Configuration” panel during the standalone main server conversion to a primary main server.












(5 of 7)






The IPv4 address that the managed NEs must use to reach this main serverDefault: —



SNMP Trap Receiving Port The TCP port that the managed NEs must use to reach this main serverDefault: 162
















Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer main serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “Main Server Configuration For Clients” panel is selected.Default: —



Default: 1099


(6 of 7)














(7 of 7)






Alcatel-Lucent 5620 SAM | 5650 CPAM D-15620 SAM | 5650 CPAMInstallation and Upgrade Guide


D.1 5650 CPAM installation parameters D-2



D-2 Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


D.1 5650 CPAM installation parameters

Table D-1 lists and describes the parameters that are configurable during a standalone 5650 CPAM server installation. Table D-2 lists and describes the parameters that are configurable for each 5650 CPAM server during a redundant installation. The parameters are grouped by installer panel in the order that the panels are displayed.

Table D-1 Standalone 5650 CPAM server installation parameters









Installs the 5620 SAM main server software

Main Server Configuration Configures the 5620 SAM main server software

Auxiliary Server Installation Installs the 5620 SAM auxiliary server software

Auxiliary Server Configuration Configures the 5620 SAM auxiliary server software

CPAM Server Installation Installs the 5650 CPAM server softwareYou must choose this option.


Specify the Base Directory for 5650 CPAM Server Files

Unlabeled field The directory in which the 5650 CPAM server files are to be installedDefault: /opt/5620sam/server


License File The absolute file path of the 5650 CPAM license zip fileDefault: —


Redundancy Supported If selected, specifies that the 5650 CPAM system is deployed in a redundant configurationYou must leave this parameter unselected.Default: unselected

Auxiliary Server Supported If selected, specifies that the 5650 CPAM deployment includes one or more auxiliary serversDefault: unselected


If selected, specifies that the 5650 CPAM deployment includes one or more client delegate serversDefault: unselected


(1 of 4)




Database Server IP Address The IP address that the 5650 CPAM server must use to reach the database stationDefault: —

Database Server Port The TCP port on the database station that the 5650 CPAM server must use to reach the databaseDefault: 1523

Database Instance Name The name that the Oracle software associates with the database processesDefault: samdb


Database User Password The database passwordDefault: available from Alcatel-Lucent technical support

Database Proxy Port The TCP port on the database station that the 5650 CPAM server is to use for redundancy communication, such as the initiation of a database failover or notification of a server activity switchDefault: 9002

CPAM Server Configuration for Auxiliary Servers


The IP address that the auxiliary servers must use to reach the 5650 CPAM serverDefault: —


If selected, specifies that at least one auxiliary server is to be used for statistics collection


If selected, specifies that at least two auxiliary servers are to be used for call-trace data collection


IP Address The IP address that the 5650 CPAM server must use to reach the auxiliary serverDefault: —

Type Preferred—specifies that the 5650 CPAM server uses this auxiliary server under normal conditionsReserved—specifies that the 5650 CPAM server uses this auxiliary server when the Preferred auxiliary server is unavailableDefault: Preferred

CPAM Server Configuration for Clients

Server Domain Name The unique identifier of the 5620 SAM/5650 CPAM server clusterDefault: 5620sam


If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach the 5650 CPAM serverYou must select this parameter if the 5650 CPAM server is to use multiple interfaces for GUI and OSS client communication.Default: unselected


If selected, specifies that NAT is used between the 5650 CPAM server and the GUI clients, OSS clients, and auxiliary serversDefault: unselected


The IP address that the NAT router uses to reach the 5650 CPAM serverThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.Default: IP address of primary network interface


(2 of 4)





Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach the 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.Default: —

JNDI Server port The TCP port on this station that the GUI clients are to use for EJB JNDI messagingAlcatel-Lucent recommends that you accept the default value unless one of the following is true:• Another application uses the port.• There is a firewall between the clients and the 5650 CPAM server.

Default: 1099



If selected, specifies that NAT is used between the 5650 CPAM server and the OSS clientsDefault: unselected


The IP address that the OSS clients must use to reach the 5650 CPAM serverDefault: IP address of primary network interface


IP Address The IP address that the 5650 CPAM server must use to reach the client delegate serverDefault: —


SSL Configuration

Enable Secure Communication If selected, specifies that SSL communication security is to be used between the 5650 CPAM server and clients, and between the 5650 CPAM and auxiliary servers

Keystore File The SSL keystore file that the 5650 CPAM server imports to the 5650 CPAM server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: —


Truststore File The SSL truststore file that the 5650 CPAM server imports to the 5650 CPAM server configurationThe parameter is configurable when the “Enable Secure Communication” parameter is selected.Default: /opt/cacerts.trustStore




If selected, specifies that NAT is used between the 5650 CPAM server and the managed NEs

IPv6 Address Used If selected, specifies that the 5650 CPAM server uses IPv6 to manage one or more NEs


(3 of 4)





The IPv4 address that the managed NEs must use to reach the 5650 CPAM serverDefault: IP address of primary network interface


The IPv6 address that the managed NEs use to reach the 5650 CPAM serverThe parameter is configurable when the “IPv6 Address Used parameter” is selected.Default: —

SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach the 5650 CPAM serverDefault: 162

Trap Log Id The SNMP trap log ID that is associated with the 5650 CPAM serverDefault: 98




The IP address of the interface that the 5650 CPAM server uses to receive CORBA notificationsDefault: IP address of primary network interface









Start the 5650 CPAM Server If selected, specifies that the 5650 CPAM server is to start automatically after the installationDefault: unselected


(4 of 4)





Table D-2 Redundant 5650 CPAM server installation parameters
















Unlabeled field The directory in which the 5650 CPAM server files are to be installedDefault: /opt/5620sam/server


License File The absolute file path of the 5650 CPAM license zip fileDefault: —


Redundancy Supported If selected, specifies that the 5650 CPAM system is deployed in a redundant configurationYou must select this parameter.Default: unselected

Auxiliary Server Supported If selected, specifies that the 5650 CPAM deployment includes one or more auxiliary serversDefault: unselected


If selected, specifies that the 5650 CPAM deployment includes one or more client delegate serversDefault: unselected



The IP address that this 5650 CPAM server must use to reach the primary database stationDefault: —

Primary Database Server Port The TCP port on the primary database station that is to receive communication from this 5650 CPAM serverDefault: 1523


The name that the Oracle software associates with the database processes on the primary database stationDefault: samdb1

(1 of 6)





Database User Password The database passwordDefault: available from Alcatel-Lucent technical support

Primary Database Proxy Port The TCP port on the primary database station that this 5650 CPAM server is to use for redundancy communication, such as the initiation of a database failover or notification of a server activity switchDefault: 9002



The IP address that this 5650 CPAM server must use to reach the standby database stationDefault: —



Standby Database Proxy Port The TCP port on the standby database station that this 5650 CPAM server is to use for redundancy communication, such as the initiation of a database failover or notification of a server activity switch

Default: 9002


If selected, specifies that each 5650 CPAM database backup file set is copied to the peer database after the backup completesYou must configure this parameter the same on each 5650 CPAM server.You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth required for database backup file synchronization.



The IP address that the auxiliary servers must use to reach this 5650 CPAM serverDefault: —






IP Address The IP address that this 5650 CPAM server must use to reach the auxiliary serverDefault: —

Type Preferred—specifies that this 5650 CPAM server uses this auxiliary server under normal conditionsReserved—specifies that this 5650 CPAM server uses this auxiliary server when the Preferred auxiliary server is unavailableDefault: Preferred

Database Alignment



If selected, specifies that the database that is the designated primary database is the preferred database of the primary 5650 CPAM serverThe parameter is configurable when the “Enable Database Alignment” parameter is selected.


(2 of 6)






If selected, specifies that the database that is the designated standby database is the preferred database of the primary 5650 CPAM serverThe parameter is configurable when the “Enable Database Alignment” parameter is selected.







Server Domain Name The unique identifier of the 5620 SAM/5650 CPAM server clusterDefault: 5620sam


If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach this 5650 CPAM server

You must select this parameter if the 5650 CPAM server is to use multiple interfaces for GUI and OSS client communication.Default: unselected


If selected, specifies that NAT is used between this 5650 CPAM server and the GUI clients, OSS clients, and auxiliary serversDefault: unselected


The IP address that the NAT router uses to reach this stationThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.Default: IP address of primary network interface

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach this 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.Default: —


Default: 1099



If selected, specifies that NAT is used between this 5650 CPAM server and the OSS clientsDefault: unselected


The IP address that the OSS clients must use to reach this 5650 CPAM serverDefault: IP address of primary network interface



(3 of 6)




IP Address The IP address that this 5650 CPAM server must use to reach the client delegate serverDefault: —


CPAM Server Configuration for Peer Server


The IP address that the peer 5650 CPAM server must use to reach this 5650 CPAM serverDefault: —



The IP address that the other 5650 CPAM server uses to reach this 5650 CPAM serverDefault: IP address of primary network interface


The IP address that this 5650 CPAM server uses to reach the other 5650 CPAM serverDefault: —

SSL Configuration








If selected, specifies that NAT is used between this 5650 CPAM server and the managed NEs

IPv6 Address Used If selected, specifies that this 5650 CPAM server uses IPv6 to manage one or more NEs


The IPv4 address that the managed NEs must use to reach this 5650 CPAM serverDefault: IP address of primary network interface


The IPv6 address that the managed NEs use to reach this 5650 CPAM serverThe parameter is configurable when the “IPv6 Address Used” parameter is selected.Default: —


(4 of 6)





SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach this 5650 CPAM serverDefault: 162

Trap Log Id The SNMP trap log ID that is associated with this 5650 CPAM serverDefault: 98




The IP address of the interface that the 5650 CPAM server uses to receive CORBA notificationsDefault: IP address of primary network interface

Peer CPAM Server Configurations

Peer Server IP Address The IP address that this 5650 CPAM server must use to reach the peer 5650 CPAM serverDefault: —

Peer Server Trap Log Id The SNMP trap log ID that is associated with the peer 5650 CPAM serverDefault: 98


The IPv4 address that the managed NEs must use to reach the peer 5650 CPAM serverDefault: —


The IPv6 address that the managed NEs use to reach the peer 5650 CPAM serverThe parameter is configurable when the “IPv6 Address Used” parameter on the “Mediation Configuration” panel is selected.


The TCP port on the peer 5650 CPAM server station that the managed NEs must use to reach the peer 5650 CPAM serverDefault: 162

Peer CPAM Server Configurations for clients

Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “CPAM Server Configuration for Clients” panel is selected.Default: —

Peer Server IP Address The IP address that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “CPAM Server Configuration for Clients” panel is unselected.Default: —

JNDI Peer Server Port The TCP port on the peer 5650 CPAM server station that the GUI clients use for EJB JNDI messagingAlcatel-Lucent recommends that you accept the default value unless one of the following is true:• Another application uses the port.• There is a firewall between the clients and the 5650 CPAM server.

Default: 1099





(5 of 6)









Start the 5650 CPAM Server If selected, specifies that the 5650 CPAM server is to start automatically after the installationDefault: unselected


(6 of 6)






Alcatel-Lucent 5620 SAM | 5650 CPAM E-15620 SAM | 5650 CPAMInstallation and Upgrade Guide


E.1 5650 CPAM upgrade parameters E-2



E-2 Alcatel-Lucent 5620 SAM | 5650 CPAM5620 SAM | 5650 CPAM


E.1 5650 CPAM upgrade parameters

Table E-1 lists and describes the parameters that are configurable during a standalone 5650 CPAM server upgrade. Table E-2 lists and describes the parameters that are configurable for each 5650 CPAM server during a redundant upgrade. The parameters are grouped by installer panel in the order that the panels are displayed.

Table E-1 Standalone 5650 CPAM server upgrade parameters

















Unlabeled field The directory in which the 5650 CPAM server files are installed


License File The absolute file path of the 5650 CPAM license zip fileIf you are upgrading from one major release to another and do not yet have the license for the new release, you must clear the parameter field.Default: the currently active license file


Redundancy Supported If selected, specifies that the 5650 CPAM system is deployed in a redundant configurationYou must leave this parameter unselected.

Auxiliary Server Supported If selected, specifies that the 5650 CPAM deployment includes one or more auxiliary servers


If selected, specifies that the 5650 CPAM deployment includes one or more client delegate servers


(1 of 4)




Database Server IP Address The IP address that the 5650 CPAM server uses to reach the database station

Database Server Port The TCP port on the database station that the 5650 CPAM server must use to reach the database

Database Instance Name The name that the Oracle software associates with the database processes


Database User Password The database password

Database Proxy Port The TCP port on the database station that the 5650 CPAM server is to use for redundancy communication, such as the initiation of a database failover or notification of a server activity switch



The IP address that the auxiliary servers must use to reach the 5650 CPAM server






IP Address The IP address that the 5650 CPAM server must use to reach the auxiliary server

Type Preferred—specifies that the 5650 CPAM server uses this auxiliary server under normal conditionsReserved—specifies that the 5650 CPAM server uses this auxiliary server when the Preferred auxiliary server is unavailable


Server Domain Name The unique identifier of the 5620 SAM/5650 CPAM server cluster


If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach the 5650 CPAM serverYou must select this parameter if the 5650 CPAM server is to use multiple interfaces for GUI and OSS client communication.


If selected, specifies that NAT is used between the 5650 CPAM server and the GUI clients, OSS clients, and auxiliary servers


The IP address that the NAT router uses to reach the 5650 CPAM serverThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach the 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.




If selected, specifies that NAT is used between the 5650 CPAM server and the OSS clients


The IP address that the OSS clients must use to reach the 5650 CPAM server


(2 of 4)






IP Address The IP address that the 5650 CPAM server must use to reach the client delegate server


SSL Configuration








If selected, specifies that NAT is used between the 5650 CPAM server and the managed NEs

IPv6 Address Used If selected, specifies that the 5650 CPAM server uses IPv6 to manage one or more NEs


The IPv4 address that the managed NEs must use to reach the 5650 CPAM server


The IPv6 address that the managed NEs use to reach the 5650 CPAM serverThe parameter is configurable when the “IPv6 Address Used parameter” is selected.

SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach the 5650 CPAM server

Trap Log Id The SNMP trap log ID that is associated with the 5650 CPAM server




The IP address of the interface that the 5650 CPAM server uses to receive CORBA notifications







(3 of 4)







Start the 5650 CPAM Server If selected, specifies that the 5650 CPAM server is to start automatically after the upgradeDefault: unselected


(4 of 4)





Table E-2 Redundant 5650 CPAM server upgrade parameters
















Unlabeled field The directory in which the 5650 CPAM server files are installed


License File The absolute file path of the 5650 CPAM license zip fileIf you are upgrading from one major release to another and do not yet have the license for the new release, you must clear the parameter field.Default: the currently active license file


Redundancy Supported If selected, specifies that the 5650 CPAM system is deployed in a redundant configurationYou must select this parameter.

Auxiliary Server Supported If selected, specifies that the 5650 CPAM deployment includes one or more auxiliary servers


If selected, specifies that the 5650 CPAM deployment includes one or more client delegate servers



The IP address that this 5650 CPAM server must use to reach the primary database station

Primary Database Server Port The TCP port on the primary database station that is to receive communication from this 5650 CPAM server


The name that the Oracle software associates with the database processes on the primary database station


Database User Password The database password

Primary Database Proxy Port The TCP port on the primary database station that this 5650 CPAM server is to use for redundancy communication, such as the initiation of a database failover or notification of a server activity switch

(1 of 5)






The IP address that this 5650 CPAM server must use to reach the standby database station


The name that the Oracle software associates with the database processes on the standby database station

Standby Database Proxy Port The TCP port on the standby database station that this 5650 CPAM server is to use for redundancy communication, such as the initiation of a database failover or notification of a server activity switch


If selected, specifies that each 5650 CPAM database backup file set is copied to the peer database after the backup completesYou must configure this parameter the same on each 5650 CPAM server.You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth required for database backup file synchronization.



The IP address that the auxiliary servers must use to reach this 5650 CPAM server






IP Address The IP address that this 5650 CPAM server must use to reach the auxiliary server

Type Preferred—specifies that this 5650 CPAM server uses this auxiliary server under normal conditionsReserved—specifies that this 5650 CPAM server uses this auxiliary server when the Preferred auxiliary server is unavailable

Database Alignment

Enable Database Alignment If selected, enables automatic database alignment


If selected, specifies that the database that is the designated primary database is the preferred database of the primary 5650 CPAM serverThe parameter is configurable when the “Enable Database Alignment” parameter is selected.


If selected, specifies that the database that is the designated standby database is the preferred database of the primary 5650 CPAM serverThe parameter is configurable when the “Enable Database Alignment” parameter is selected.







Server Domain Name The unique identifier of the 5620 SAM/5650 CPAM server cluster


(2 of 5)






If selected, specifies that the GUI clients, OSS clients, and auxiliary servers use a hostname, rather than an IP address, to reach this 5650 CPAM serverYou must select this parameter if the 5650 CPAM server is to use multiple interfaces for GUI and OSS client communication.


If selected, specifies that NAT is used between this 5650 CPAM server and the GUI clients, OSS clients, and auxiliary servers


The IP address that the NAT router uses to reach this stationThe parameter is configurable when the “NAT (network address translation) Used” parameter is selected.

Public IP (accessible to clients) The IP address that the GUI and OSS clients must use to reach this 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter is unselected.




If selected, specifies that NAT is used between this 5650 CPAM server and the OSS clients


The IP address that the OSS clients must use to reach this 5650 CPAM server


IP Address The IP address that this 5650 CPAM server must use to reach the client delegate server


CPAM Server Configuration for Peer Server


The IP address that the peer 5650 CPAM server must use to reach this 5650 CPAM server



The IP address that the other 5650 CPAM server uses to reach this 5650 CPAM server


The IP address that this 5650 CPAM server uses to reach the other 5650 CPAM server

SSL Configuration





(3 of 5)








If selected, specifies that NAT is used between this 5650 CPAM server and the managed NEs

IPv6 Address Used If selected, specifies that this 5650 CPAM server uses IPv6 to manage one or more NEs


The IPv4 address that the managed NEs use to reach this 5650 CPAM server


The IPv6 address that the managed NEs use to reach this 5650 CPAM serverThe parameter is configurable when the “IPv6 Address Used” parameter is selected.

SNMP Trap Receiving Port The TCP port on this station that the managed NEs must use to reach this 5650 CPAM server

Trap Log Id The SNMP trap log ID that is associated with this 5650 CPAM server




The IP address of the interface that the 5650 CPAM server uses to receive CORBA notifications

Peer CPAM Server Configurations

Peer Server IP Address The IP address that this 5650 CPAM server must use to reach the peer 5650 CPAM server

Peer Server Trap Log Id The SNMP trap log ID that is associated with the peer 5650 CPAM server


The IPv4 address that the managed NEs must use to reach the peer 5650 CPAM server


The IPv6 address that the managed NEs use to reach the peer 5650 CPAM serverThe parameter is configurable when the “IPv6 Address Used” parameter on the “Mediation Configuration” panel is selected.


The TCP port on the peer 5650 CPAM server station that the managed NEs must use to reach the peer 5650 CPAM server

Peer CPAM Server Configurations for clients

Peer Server Hostname The hostname that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the “CPAM Server Configuration for Clients” panel is selected.

Peer Server IP Address The IP address that the GUI clients, OSS clients, and auxiliary servers must use to reach the peer 5650 CPAM serverThe parameter is configurable when the “Use Hostname for Communication” parameter on the” CPAM Server Configuration for Clients” panel is unselected.


(4 of 5)





JNDI Peer Server Port The TCP port on the peer 5650 CPAM server station that the GUI clients use for EJB JNDI messagingAlcatel-Lucent recommends that you accept the default value unless one of the following is true:• Another application uses the port.• There is a firewall between the clients and the 5650 CPAM server.









Start the 5650 CPAM Server If selected, specifies that the 5650 CPAM server is to start automatically after the upgrade

Default: unselected


(5 of 5)


Customer documentation and product support

Customer documentationCustomer Documentation Welcome Page

Technical Supporthttp://support.alcatel-lucent.com

Documentation [email protected]


https://infoproducts.alcatel-lucent.com/cgi-bin/doc_welc.pl

http://support.alcatel-lucent.com

mailto:[email protected]

© 2016 Alcatel-Lucent. All rights reserved.

www.alcatel-lucent.com

Installation and Upgrade Guide - Nokia Documentation

Documents