3JL01001BFAARJZZA - V1 - 5520 AMS Release 9.4 Installation and Migration Guide

Alcatel-Lucent 5520
ACCESS MANAGEMENT SYSTEM| RELEASE 9.4

INSTALLATION AND MIGRATION GUIDE
3JL-01001-BFAA-RJZZA Edition 04
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2015 Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is
subject to change without notice.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners.
Copyright 2015 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.
PRINTED ON
RECYCLED PAPER
Preface
The 5520 AMS provides fault, configuration, and performance management of the
underlying access networks, using a GUI and hierarchical tree navigation. The
5520 AMS also supports network-productivity features such as equipment profile
management, NE backup and restore, and NE software management.
Documentation
The 5520 AMS Release Notice provides information about changes or enhancements
made to the software and its features, as well as information about delivery,
compatibility, and customer documentation.
The 5520 AMS Solution Planning Guide provides information about how to plan the
purchase and configuration of hardware and software to support the deployment of
the 5520 AMS.
The 5520 AMS Server Configuration Technical Guidelines provides information
about how to prepare hardware for installation of the 5520 AMS, including
information about installing the server, setting up a cluster and configuring a
network.
The 5520 AMS Installation and Migration Guide provides information about how to
install, optimize, and uninstall the 5520 AMS server, client, and plug-in components,
as well as how to migrate data to the 5520 AMS from other EMSs.
The 5520 AMS Administrator Guide provides information about administrative
functions, including management of server-client communication, users, NE
communication, schedules, links, and codes.
The 5520 AMS User Guide provides information about user functions, including
monitoring, fault, and alarm management and performing tasks that are common to
all NEs.
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 iii
3JL-01001-BFAA-RJZZA Edition 04 Installation and Migration Guide
Preface
The 5520 AMS Northbound Interface Guide provides information about functions
supported by the 5520 AMS NBI.
The 5520 AMS Solution Glossary provides descriptions of 5520 AMS-related terms
and acronyms.
The 5520 AMS Alarm Analyzer Installation and User Guide provides an overview of
the 5520 AMS Alarm Analyzer and instructions to perform alarm analysis functions
in the 5520 AMS GUI.
Conventions used in this guide

The following table lists the conventions that are used in this guide.
Table 1 Documentation conventions
Convention Description Examples
Key name Identifies a keyboard key Delete
Italics Identifies a variable hostname
Key+Key Type the appropriate consecutive keystroke sequence. CTRL+G

Key-Key Type the appropriate simultaneous keystroke sequence. CTRL-G
Press the Return or Enter key. Press
An em dash in a table cell indicates that there is no

information or that the category is not applicable.
* An asterisk is a wildcard character that means any Path_analysis.*file
character in a search argument.
An asterisk also indicates a default option for an NMTI
parameter.
Indicates a submenu FileSave
(p. x-y) Indicates the page number. (p. 1-2)
Important information
The following conventions are used to indicate important information:
Warning Warning indicates that the described task or situation

may, or will, cause equipment damage or serious performance
problems.
Caution Caution indicates that the described task or situation may,

or will, cause service interruption.
iv August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

Installation and Migration Guide Edition 04 3JL-01001-BFAA-RJZZA
Preface
Note Note provides information that is, or may be, of special

interest.
Applies to The Applies to note indicates that the described task or

situation applies only in the situation specified.
Navigation steps
The 5520 AMS GUI allows you to navigate to objects using any of the following
methods:
Navigation trees in the Network and Administration perspectivesexpand,
collapse, and choose objects
Graphical Viewdouble-click objects
Search and Find utilitiesenter information about the object in a window
See the 5520 AMS User Guide for more information about navigating in the GUI.
Procedure 1 Example of NE navigation convention

1 Navigate to the NE and choose object.
2 Right-click object and choose menu item.
Procedures with options or substeps

When there are options in a procedure, they are identified by an unordered list. When
there are substeps in a procedure, they are identified by roman numerals.
Procedure 2 Example of options in a procedure
At step 1 (p. v), you can choose to perform one of the options provided in the unordered
list. At step 2 (p. v), you must do what the step indicates.
1 This step offers two options. You must choose one of the following:
This is one option.

This is another option.
2 You must perform this step.
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 v

Preface
Procedure 3 Example of substeps in a procedure
At step 1 (p. vi), you must perform a series of substeps within a step. At step 2 (p. vi),
you must do what the step indicates.
1 This step has a series of substeps that you must perform to complete the step. You
must perform the following substeps:
i This is the first substep.
ii This is the second substep.
iii This is the third substep.
2 You must perform this step.
Multiple PDF file search

You can use Adobe Reader, Release 6.0 or later, to search multiple PDF files for a
term. Adobe Reader displays the results in a display panel. The results are grouped
by PDF file. You can expand the entry for each file.
Note The PDF files in which you search must be in the same
folder.
Procedure 4 To search multiple PDF files for a term

1 Open Adobe Reader.
2 Choose EditSearch from the Adobe Reader main menu. The Search panel opens.
3 Enter the term to search for.
4 Select the All PDF Documents in option.
5 Choose the folder in which to search using the drop-down menu.
6 Select the following search criteria, if required:
Whole words only

Case-Sensitive
Include Bookmarks
Include Comments
7 Click Search.
vi August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

Preface
Adobe Reader displays the search results. Click on the + symbol to expand the
entries for each file.
Note After you click on a hyperlink, right-click and choose Previous

View from the contextual menu to return to the location of the
hyperlink that you clicked on.
Contact information
If you have questions or comments about this documentation, contact:
documentation.feedback@alcatel-lucent.com
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 vii
Preface
viii August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
Table of contents
Table of contents
Preface
Documentation ........................................................................... iii
Conventions used in this guide ......................................................... iv
Important information ................................................................ iv
Navigation steps ........................................................................ v
Procedure 1 Example of NE navigation convention ............................... v
Procedures with options or substeps ................................................ v
Procedure 2 Example of options in a procedure ................................... v
Procedure 3 Example of substeps in a procedure ................................ vi
Multiple PDF file search ................................................................. vi
Procedure 4 To search multiple PDF files for a term ............................ vi
Contact information .................................................................... vii
Getting started
1 Whats new 1-1

1.1 Whats new in Release 9.4 ............................................................ 1-2
1.2 Whats new in Release 9.3.10 ........................................................ 1-3
1.3 Whats new in Release 9.3.0 ......................................................... 1-4
1.4 Whats new in Release 9.2.30 ........................................................ 1-5
2 Overviews 2-1
2.1 Guide overview ......................................................................... 2-2
2.2 Installation and migration overview ................................................. 2-2
Installation terms .................................................................... 2-3
Environment variables .............................................................. 2-4
5520 AMS server roles ............................................................... 2-5
Standalone (simplex) installation ................................................. 2-6
Clusters: redundancy and load-balancing ....................................... 2-6
Sites: geographic redundancy ..................................................... 2-8
Using the 5520 AMS with a NAT server .......................................... 2-10
2.3 5529 Enhanced Applications ......................................................... 2-10
2.4 Technical support ..................................................................... 2-10
Procedure 2-1 To find contact information for technical assistance ....... 2-10
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 iii
Table of contents
Installing the 5520 AMS
3 5520 AMS installation overview 3-1

3.1 Simplex installation overview ........................................................ 3-2
Server installation tasks ............................................................ 3-3
3.2 Cluster installation overview ......................................................... 3-3
Overview .............................................................................. 3-4
Cluster installation tasks ........................................................... 3-6
3.3 Geographic redundancy installation overview ..................................... 3-7
Site components ..................................................................... 3-7
Site configuration ................................................................... 3-8
Health state of a 5520 AMS system ............................................... 3-8
Loss of a site ......................................................................... 3-8
Geographic redundancy installation tasks ...................................... 3-11
3.4 Software plug-in installation overview ............................................. 3-12
Installing and activating software plug-ins ..................................... 3-12
Deactivating software plug-ins ................................................... 3-13
3.5 Patch installation overview .......................................................... 3-14
Installing and activating patches ................................................ 3-14
Deactivating patches .............................................................. 3-16
3.6 Emergency fix installation overview ............................................... 3-18
Installing and activating emergency fixes ...................................... 3-18
Deactivating emergency fixes .................................................... 3-19
4 Setting up 5520 AMS infrastructure 4-1

4.1 Setting up the 5520 AMS infrastructure ............................................. 4-2
5520 AMS server requirements in a simplex setup ............................. 4-2
5520 AMS server requirements in a cluster setup .............................. 4-2
Procedure 4-1 To prepare the 5520 AMS infrastructure ....................... 4-3
4.2 Configuring NTP ........................................................................ 4-4
Procedure 4-2 To configure an NTP server on Solaris systems ............... 4-4
Procedure 4-3 To configure an NTP client on Solaris systems ................ 4-5
Procedure 4-4 To configure an NTP server on Red Hat Enterprise
Linux systems .................................................................. 4-6
Procedure 4-5 To configure an NTP client on Red Hat Enterprise
Linux systems .................................................................. 4-7
Procedure 4-6 To configure NTP clients to access the NTP Server on
Red Hat Enterprise Linux systems .......................................... 4-7
4.3 Configuring storage .................................................................... 4-8
Configuring ZFS pools ............................................................... 4-8
Procedure 4-7 To configure ZFS pools ............................................ 4-9
Configuring LVM volumes .......................................................... 4-10
Procedure 4-8 To configure LVM volumes ...................................... 4-11
4.4 User and group IDs .................................................................... 4-11
4.5 Configuring locale settings ........................................................... 4-12
Procedure 4-9 To configure the locale settings ............................... 4-12
iv August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

Table of contents
5 Downloading software for the 5520 AMS and 5529 Enhanced

Applications 5-1
5.1 Downloading software for the 5520 AMS and 5529 Enhanced Applications .... 5-2
Procedure 5-1 To download software ............................................ 5-2
Procedure 5-2 To verify the MD5 hash value .................................... 5-3
5.2 Extracting the downloaded installation files ....................................... 5-3
Procedure 5-3 To extract the downloaded installation file to a new
directory ........................................................................ 5-4
6 Installing the 5520 AMS solution components 6-1

6.1 Installing the 5520 AMS solution overview .......................................... 6-2
6.2 Pre-requisite tasks ..................................................................... 6-2
6.3 Installing the 5520 AMS solution ..................................................... 6-4
Procedure 6-1 To install and activate the 5520 AMS solution ................ 6-4
Procedure 6-2 To manually configure sudo .................................... 6-21
6.4 Saving the configuration settings for installation of a 5520 AMS server ...... 6-21
Procedure 6-3 To save the configuration settings for the installation
of a 5520 AMS server ......................................................... 6-22
6.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes ................................ 6-23
5520 AMS NE plug-in software file ............................................... 6-23
Patch software file ................................................................. 6-24
Emergency fix software file ...................................................... 6-24
5529 Enhanced Applications and plug-ins software file ...................... 6-24
Installing and activating the 5520 AMS solution components ................ 6-25
Procedure 6-4 To install the 5520 AMS NE plug-ins, 5529 Enhanced
Applications and plug-ins, and patches and emergency fixes
together or individually ..................................................... 6-27
Procedure 6-5 To activate the 5520 AMS NE plug-ins, 5529 Enhanced
Deactivating the 5520 AMS solution components .............................. 6-31
Procedure 6-6 To deactivate the 5520 AMS NE plug-ins, 5529 Enhanced
Installing, activating or deactivating the 5520 AMS solution components . 6-35
Procedure 6-7 To install, activate, install and activate, or
deactivate the 5520 AMS solution components .......................... 6-35
6.6 Verifying the installed software components on the 5520 AMS server ........ 6-38
Procedure 6-8 To verify the installed software components ................ 6-38
6.7 Changing passwords for default users .............................................. 6-39
Procedure 6-9 To change the password of a default user on the 5520 AMS
application server ............................................................ 6-39
7 Activating, starting and stopping the servers 7-1

7.1 Activating, starting and stopping the servers ..................................... 7-2
Procedure 7-1 To activate a server ............................................... 7-2
Procedure 7-2 To start a server ................................................... 7-2
Procedure 7-3 To start a cluster .................................................. 7-3
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 v

Table of contents
Procedure 7-4 To stop a server ................................................... 7-4

Procedure 7-5 To stop a cluster ................................................... 7-4
8 Configuring the 5520 AMS to support NAT 8-1

8.1 Configuring the 5520 AMS to support NAT ......................................... 8-2
Procedure 8-1 To configure the 5520 AMS to support NAT .................... 8-2
9 Converting a simplex installation to a cluster 9-1

9.1 Converting a simplex installation to a cluster ..................................... 9-2
Procedure 9-1 To convert a simplex server to a cluster server .............. 9-2
9.2 Adding and removing servers ......................................................... 9-5
Adding servers ....................................................................... 9-5
Procedure 9-2 To configure a newly added application server in a site
in the 5520 AMS GUI ........................................................... 9-5
Removing servers .................................................................... 9-6
Procedure 9-3 To remove an application server from a cluster .............. 9-6
Redistributing management of NEs ............................................... 9-7
Procedure 9-4 To split NE data .................................................... 9-8
10 Configuring geographic redundancy 10-1

10.1 Overview ................................................................................ 10-2
10.2 Ping-pong protection ................................................................. 10-2
Procedure 10-1 To overrule ping-pong protection ............................ 10-2
10.3 Configuring geographic redundancy ................................................ 10-3
Procedure 10-2 To configure data replication between sites ............... 10-3
Procedure 10-3 To configure the 5520 AMS to run a script if one site
is down ......................................................................... 10-6
10.4 Configuring the OSS arbiter .......................................................... 10-7
Procedure 10-4 To configure the OSS arbiter in a geographically
redundant installation ....................................................... 10-7
Procedure 10-5 To start the OSS arbiter in a geographically redundant
installation .................................................................... 10-9
10.5 Modifying geographic redundancy .................................................. 10-9
Procedure 10-6 To switch between the active and standby site .......... 10-10
Procedure 10-7 To change a geographically redundant installation to two
independent sites .......................................................... 10-11
Triggering a forced full synchronization of shared data ................... 10-12
Procedure 10-8 To trigger a forced full synchronization of shared data 10-12
11 Updating firewall rules 11-1

11.1 Updating firewall rules ............................................................... 11-2
Procedure 11-1 To update firewall rules ....................................... 11-2
12 Installing the 5520 AMS client 12-1

12.1 Client installation overview ......................................................... 12-2
Shared client installation ......................................................... 12-2
Client installation tasks ........................................................... 12-3
vi August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

Table of contents
12.2 Installing a single 5520 AMS client .................................................. 12-4

Procedure 12-1 To install a single 5520 AMS client in Windows/Red Hat
Enterprise Linux System ..................................................... 12-4
12.3 Installing a shared 5520 AMS client ................................................. 12-6
Procedure 12-2 To install a shared client in Windows ........................ 12-6
Procedure 12-3 To install a shared 5520 AMS client in Red Hat
Enterprise Linux .............................................................. 12-8
Individual work spaces with a shared client ................................... 12-9
Procedure 12-4 To install a shared client with the shared
client wrapper .............................................................. 12-10
Procedure 12-5 To configure the presentation server and login title
to use the shared client wrapper ........................................ 12-12
12.4 Launching and updating the 5520 AMS client ................................... 12-13
Procedure 12-6 To launch and update the 5520 AMS client ............... 12-14
Procedure 12-7 To update permissions for the plug-ins directory ........ 12-19
Procedure 12-8 To make the site name visible in the GUI login window
when multiple users access the shared 5520 AMS client in Red Hat
Enterprise Linux ............................................................ 12-19
Procedure 12-9 To display hours in the 0 to 24 convention in the
5520 AMS client ............................................................. 12-20
12.5 Changing passwords for default users in the 5520 AMS GUI .................. 12-20
Procedure 12-10 To change a default user password in the 5520
AMS GUI ...................................................................... 12-21
12.6 Adding a license to the 5520 AMS ................................................. 12-21
Procedure 12-11 To add a license key from the 5520 AMS GUI ........... 12-22
Procedure 12-12 To add a license key from the 5520 AMS server ........ 12-23
License installation error scenarios ........................................... 12-23
Migrating to the 5520 AMS, Release 9.4
13 Migrating to the 5520 AMS, Release 9.4 13-1

13.1 Migration overview .................................................................... 13-2
In-place migration .................................................................. 13-3
Out-of-place migration ............................................................ 13-4
Migration support between operating systems and architectures .......... 13-5
13.2 Installing the 5520 AMS, Release 9.4 on the same server running an earlier
5520 AMS release ............................................................... 13-5
13.3 Migrating NEs ........................................................................... 13-6
13.4 Migration dependencies of the data migration script ........................... 13-6
Data not migrated from the earlier 5520 AMS release ....................... 13-6
13.5 Updating software plug-ins to a new version ..................................... 13-7
13.6 External TL1 Gateway migration .................................................... 13-7
13.7 Migration with a customized keystore ............................................. 13-8
13.8 Migrating templates ................................................................... 13-9
13.9 Migrating licenses ..................................................................... 13-9
14 Migration scenarios and associated task list 14-1
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 vii
Table of contents
14.1 Overview of the migration scenarios ............................................... 14-2

14.2 Automated in-place migration from an earlier 5520 AMS release to the
5520 AMS, Release 9.4 ......................................................... 14-2
14.3 Out-of-place migration from an earlier 5520 AMS release to the 5520 AMS,
Release 9.4 ...................................................................... 14-4
14.4 Checking the consistency of alarm rules after migration ....................... 14-9
15 Pre-migration tasks 15-1

15.1 Overview of the pre-migration tasks ............................................... 15-2
15.2 Transferring the 5520 AMS software to the 5520 AMS servers .................. 15-2
15.3 Server configuration overview ...................................................... 15-2
15.4 Generating a hostid ................................................................... 15-3
Procedure 15-1 To generate a hostid ........................................... 15-3
15.5 Installing the 5520 AMS, Release 9.4 for migration .............................. 15-4
Procedure 15-2 To install the 5520 AMS solution for migration ............. 15-4
15.6 Installing the 5520 AMS solution software components for migration ...... 15-21
Procedure 15-3 To install 5520 AMS solution software components for
migration .................................................................... 15-22
16 Migration tasks 16-1

16.1 Overview of the migration tasks .................................................... 16-2
16.2 Migrating the switchover script ..................................................... 16-2
Procedure 16-1 To migrate the switchover_hook.sh script .................. 16-3
16.3 Enabling SSL ............................................................................ 16-4
Procedure 16-2 To enable SSL with a customized keystore ................. 16-4
16.4 Enabling geographic redundancy .................................................... 16-5
Procedure 16-3 To configure data replication between sites ............... 16-6
16.5 Backing up the 5520 AMS database for an out-of-place migration ............ 16-9
16.6 Transfer the backup file of 5520 AMS database to the new server .......... 16-10
16.7 Copying data files from the earlier 5520 AMS release to the 5520 AMS,
Release 9.4 .................................................................... 16-11
Copying data files from a backup file in an out-of-place migration
scenario ...................................................................... 16-11
Procedure 16-4 To copy data files from a backup file
(interactive mode) ......................................................... 16-12
(non-interactive mode) .................................................... 16-14
16.8 Starting the 5520 AMS, Release 9.4 servers ..................................... 16-16
Sequence of starting the 5520 AMS, Release 9.4 servers in cluster
setups and geographically redundant setups ........................... 16-17
Procedure 16-6 To start a server .............................................. 16-18
Procedure 16-7 To check the migration status .............................. 16-20
16.9 Adding licenses to the 5520 AMS, Release 9.4 installation ................... 16-20
16.10 Installing the 5520 AMS, Release 9.4 client ..................................... 16-20
16.11 Launching the 5520 AMS, Release 9.4 client .................................... 16-21
16.12 Updating the anonymous FTP user path ......................................... 16-21
Procedure 16-8 To update the anonymous FTP user path ................. 16-22
17 Post-migration tasks 17-1
viii August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
Table of contents
17.1 Overview of the post-migration tasks .............................................. 17-2

17.2 Migrating ONT SIP data ............................................................... 17-2
17.3 Importing GUI settings ................................................................ 17-2
Procedure 17-1 To import GUI settings ......................................... 17-3
17.4 Deleting the former site of the earlier 5520 AMS release ....................... 17-4
Procedure 17-2 To delete the former site of the earlier 5520
AMS release .................................................................... 17-5
Uninstalling the 5520 AMS
18 Uninstalling 5520 AMS components 18-1

18.1 Uninstalling 5520 AMS components overview ..................................... 18-2
18.2 Uninstalling software plug-ins ....................................................... 18-2
18.3 Uninstalling patches .................................................................. 18-3
18.4 Uninstalling emergency fixes ........................................................ 18-4
18.5 Uninstalling 5520 AMS NE plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes ................................ 18-5
Procedure 18-1 To uninstall the 5520 AMS NE plug-ins, 5529 Enhanced
18.6 Uninstalling a 5520 AMS client ...................................................... 18-8
Procedure 18-2 To uninstall the earlier 5520 AMS client application in
Windows ....................................................................... 18-8
Procedure 18-3 To uninstall the 5520 AMS client application in Red Hat
Enterprise Linux ............................................................. 18-9
18.7 Uninstalling the 5520 AMS server ................................................. 18-10
Procedure 18-4 To uninstall the 5520 AMS server ........................... 18-11
Appendix
A.1 To install and activate the 5520 AMS solution in a simplex setup .............. B-2
A.2 To install and activate NE Plug-in ................................................... B-3
A.3 To install the 5529 Enhanced Applications ......................................... B-3
B.1 Overview of the manual in-place migration scenarios ........................... B-2
Migration path and strategy ....................................................... B-2
B.2 Manual in-place migration associated task list .................................... B-2
Migrate a simplex installation ..................................................... B-2
Migrate a cluster installation ...................................................... B-4
Migrate a geographically redundant installation ............................... B-6
B.3 Pre-migration tasks for manual in-place migration ............................... B-8
Installing the 5520 AMS, Release 9.4 for migration (In-place-manual) ...... B-9
Procedure B-1 To install the 5520 AMS solution for manual in-place
migration ....................................................................... B-9
Installing the 5520 AMS solution software components for migration ..... B-22
Backing up the 5520 AMS database .............................................. B-22
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 ix

Table of contents
B.4 Migration tasks for manual in-place migration ................................... B-23

Stopping the earlier 5520 AMS release servers ................................ B-23
Procedure B-2 To stop a server in a simplex setup or all servers
in a cluster setup ............................................................. B-24
Disabling SSL ........................................................................ B-24
Procedure B-3 To disable SSL ..................................................... B-25
Migrating the switchover script .................................................. B-25
Activating the 5520 AMS, Release 9.4 servers ................................. B-26
Procedure B-4 To activate a server .............................................. B-26
Activating the 5520 AMS software plug-ins ..................................... B-27
Procedure B-5 To activate a software plug-in ................................. B-28
Enabling SSL ......................................................................... B-30
Enabling geographic redundancy ................................................. B-30
Copying data files from the earlier 5520 AMS release to the 5520 AMS,
Release 9.4 .................................................................... B-31
Procedure B-6 To copy data files from the previous release
(interactive mode) ........................................................... B-32
(non-interactive mode) ...................................................... B-34
Starting the 5520 AMS, Release 9.4 servers .................................... B-36
Adding licenses to the 5520 AMS, Release 9.4 installation .................. B-37
Installing the 5520 AMS, Release 9.4 client .................................... B-37
Launching the 5520 AMS, Release 9.4 client ................................... B-37
Updating the anonymous FTP user path ........................................ B-38
B.5 Post-migration tasks .................................................................. B-38
Importing GUI settings ............................................................. B-39
Uninstalling the earlier 5520 AMS release ..................................... B-39
Procedure B-8 To uninstall software plug-ins after migration .............. B-41
Procedure B-9 To uninstall a software plug-in manually after migration . B-43
Procedure B-10 To uninstall a 5520 AMS patch ................................ B-44
Uninstalling the 5520 AMS client in the earlier 5520 AMS release .......... B-44
Uninstalling the earlier 5520 AMS server after migration .................... B-44
Procedure B-11 To uninstall the earlier 5520 AMS server after migration B-45
Rolling back to the earlier 5520 AMS release .................................. B-45
Procedure B-12 To stop a server in a simplex setup or all servers in a
cluster setup .................................................................. B-46
Procedure B-13 To activate a server ............................................ B-46
Procedure B-14 To start a server ................................................ B-47
x August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

List of figures
List of figures
Figure 2-1 Standalone (simplex) installation of the 5520 AMS ............................... 2-6
Figure 2-2 Cluster installation of the 5520 AMS ................................................ 2-7
Figure 2-3 Simplest geographic redundancy installation of the 5520 AMS ................. 2-8
Figure 2-4 Typical geographic redundancy installation of the 5520 AMS .................. 2-9
Figure 3-1 Geographic redundancy installation of the 5520 AMS with an OSS arbiter .. 3-11
Figure 4-1 Volume setup on Red Hat Enterprise Linux systems ............................ 4-10
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 xi

List of figures
xii August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
List of tables
List of tables
Table 1 Documentation conventions ............................................................ iv
Table 1-1 Whats new in Release 9.4 ............................................................ 1-2
Table 1-2 Whats new in Release 9.3.10 ........................................................ 1-3
Table 1-3 Whats new in Release 9.3.0 ......................................................... 1-5
Table 1-4 Whats new in Release 9.2.30 ........................................................ 1-5
Table 2-1 Key terms ................................................................................ 2-3
Table 2-2 Environment variables ................................................................. 2-4
Table 3-1 User accounts ........................................................................... 3-2
Table 3-2 Install the 5520 AMS, Release 9.4 in a standalone (simplex) configuration ... 3-3
Table 3-3 UNIX user accounts ..................................................................... 3-6
Table 3-4 Install the 5520 AMS in a cluster configuration .................................... 3-6
Table 3-5 Scenarios for geographically redundant switchover .............................. 3-9
Table 3-6 Install the 5520 AMS, Release 9.4 in a geographically redundant
installation ...................................................................... 3-11
Table 3-7 Install and activate a software plug-in ............................................ 3-13
Table 3-8 Deactivate a software plug-in ....................................................... 3-13
Table 3-9 Install the 5520 AMS patches - cases ............................................... 3-14
Table 3-10 Install and activate a 5520 AMS patch ............................................ 3-15
Table 3-11 Deactivating the 5520 AMS patches - cases ...................................... 3-16
Table 3-12 Deactivate a 5520 AMS patch ....................................................... 3-17
Table 3-13 Install and activate an emergency fix ............................................. 3-19
Table 3-14 Deactivate an emergency fix ....................................................... 3-20
Table 4-1 Configure NTP on Red Hat Enterprise Linux systems ............................. 4-4
Table 6-1 Pre-requisite tasks for installing the 5520 AMS .................................... 6-2
Table 6-2 Installation result ..................................................................... 6-19
Table 6-3 Activation result ....................................................................... 6-20
Table 6-4 Install and activate the 5520 AMS solution components ........................ 6-25
Table 6-5 Deactivate the 5520 AMS solution components ................................... 6-32
Table 9-1 Convert from a simplex installation to a cluster .................................. 9-2
Table 10-1 Modify geographic redundancy ..................................................... 10-9
Table 12-1 Types of client installation ......................................................... 12-2
Table 12-2 Install the 5520 AMS client .......................................................... 12-4
Table 12-3 License installation from the 5520 AMS server ................................ 12-23
Table 12-4 License installation error scenarios ............................................. 12-23
Table 13-1 Supported migration path and data migration strategy ....................... 13-2
Table 13-2 5520 AMS migration support between operating systems and
architectures, in the 5520 AMS Release 9.4 ................................ 13-5
Table 13-3 Data not migrated from the earlier 5520 AMS release to the 5520 AMS,
Release 9.4 ...................................................................... 13-6
Table 13-4 Updating a software plug-in to a new version ................................... 13-7
Table 13-5 External TL1 Gateway migration behavior from the earlier 5520 AMS
release to the 5520 AMS, Release 9.4 ....................................... 13-8
Table 14-1 Migration path and data migration strategy for automated in-place and
out-of-place migrations ....................................................... 14-2
Table 14-2 Automated in-place migration path and data migration strategy ........... 14-3
Table 14-3 Automated in-place migration for simplex, cluster, and geographical
redundant installations ........................................................ 14-3
Table 14-4 Out-of-place migration path and data migration strategy .................... 14-4
Table 14-5 Simplex migration - Out-of-place .................................................. 14-4
Table 14-6 Cluster migration - Out-of-place ................................................... 14-5
Table 14-7 Geographically redundant migration - Out-of-place ........................... 14-7
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 xiii
List of tables
Table 15-1 Migration result ..................................................................... 15-16

Table 15-2 Activation result .................................................................... 15-17
Table 16-1 Start sequence of the 5520 AMS, Release 9.4 servers in cluster setups ... 16-17
Table 16-2 Start sequence of the 5520 AMS, Release 9.4 servers in geographically
redundant setups ............................................................. 16-18
Table 18-1 Uninstalling the software plug-ins - cases ........................................ 18-2
Table 18-2 Uninstall a software plug-in ........................................................ 18-2
Table 18-3 Uninstalling the 5520 AMS patches - cases ....................................... 18-3
Table 18-4 Uninstall a 5520 AMS patch ......................................................... 18-3
Table 18-5 Uninstalling the emergency fixes - cases ......................................... 18-4
Table 18-6 Uninstall an emergency fix ......................................................... 18-4
Table 18-7 Uninstall the 5520 AMS solution components .................................... 18-5
Table A-1 Result of installation of standalone server in a simplex setup .................. B-3
Table B-1 In-place migration path and data migration strategy (manual) ................. B-2
Table B-2 Simplex installation migration - In-place (manual) ............................... B-3
Table B-3 Cluster migration - In-place (manual) ............................................... B-4
Table B-4 Geographically redundant migration - In-place (manual) ........................ B-6
Table B-5 Migration result ........................................................................ B-20
Table B-6 Activation result ....................................................................... B-21
Table B-7 Uninstall the earlier 5520 AMS release after migrating to the 5520 AMS,
Release 9.4 ...................................................................... B-40
xiv August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
List of procedures
List of procedures
Procedure 1 Example of NE navigation convention ............................................... v
Procedure 2 Example of options in a procedure .................................................. v
Procedure 3 Example of substeps in a procedure ................................................ vi
Procedure 4 To search multiple PDF files for a term ............................................ vi
Procedure 2-1 To find contact information for technical assistance ...................... 2-10
Procedure 4-1 To prepare the 5520 AMS infrastructure ....................................... 4-3
Procedure 4-2 To configure an NTP server on Solaris systems ............................... 4-4
Procedure 4-3 To configure an NTP client on Solaris systems ............................... 4-5
Procedure 4-4 To configure an NTP server on Red Hat Enterprise Linux systems ........ 4-6
Procedure 4-5 To configure an NTP client on Red Hat Enterprise Linux systems ......... 4-7
Procedure 4-6 To configure NTP clients to access the NTP Server on Red Hat Enterprise
Linux systems .................................................................... 4-7
Procedure 4-7 To configure ZFS pools ........................................................... 4-9
Procedure 4-8 To configure LVM volumes ...................................................... 4-11
Procedure 4-9 To configure the locale settings ............................................... 4-12
Procedure 5-1 To download software ............................................................ 5-2
Procedure 5-2 To verify the MD5 hash value .................................................... 5-3
Procedure 5-3 To extract the downloaded installation file to a new directory ........... 5-4
Procedure 6-1 To install and activate the 5520 AMS solution ................................ 6-4
Procedure 6-2 To manually configure sudo .................................................... 6-21
Procedure 6-3 To save the configuration settings for the installation of a 5520
AMS server ....................................................................... 6-22
Procedure 6-4 To install the 5520 AMS NE plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes together or individually ... 6-27
Procedure 6-5 To activate the 5520 AMS NE plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes together or individually ... 6-29
Procedure 6-6 To deactivate the 5520 AMS NE plug-ins, 5529 Enhanced Applications
and plug-ins, and patches and emergency fixes together or
individually ...................................................................... 6-32
Procedure 6-7 To install, activate, install and activate, or deactivate the 5520
AMS solution components ..................................................... 6-35
Procedure 6-8 To verify the installed software components ................................ 6-38
Procedure 6-9 To change the password of a default user on the 5520 AMS
application server .............................................................. 6-39
Procedure 7-1 To activate a server .............................................................. 7-2
Procedure 7-2 To start a server ................................................................... 7-2
Procedure 7-3 To start a cluster .................................................................. 7-3
Procedure 7-4 To stop a server ................................................................... 7-4
Procedure 7-5 To stop a cluster .................................................................. 7-4
Procedure 8-1 To configure the 5520 AMS to support NAT ................................... 8-2
Procedure 9-1 To convert a simplex server to a cluster server .............................. 9-2
Procedure 9-2 To configure a newly added application server in a site in the 5520
AMS GUI ........................................................................... 9-5
Procedure 9-3 To remove an application server from a cluster ............................. 9-6
Procedure 9-4 To split NE data ................................................................... 9-8
Procedure 10-1 To overrule ping-pong protection ............................................ 10-2
Procedure 10-2 To configure data replication between sites ............................... 10-3
Procedure 10-3 To configure the 5520 AMS to run a script if one site is down ........... 10-6
Procedure 10-4 To configure the OSS arbiter in a geographically redundant
installation ...................................................................... 10-7
Procedure 10-5 To start the OSS arbiter in a geographically redundant installation .... 10-9
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 xv

List of procedures
Procedure 10-6 To switch between the active and standby site ......................... 10-10
Procedure 10-7 To change a geographically redundant installation to two
independent sites ............................................................ 10-11
Procedure 10-8 To trigger a forced full synchronization of shared data ................ 10-12
Procedure 11-1 To update firewall rules ....................................................... 11-2
Procedure 12-1 To install a single 5520 AMS client in Windows/Red Hat Enterprise
Linux System .................................................................... 12-4
Procedure 12-2 To install a shared client in Windows ....................................... 12-6
Procedure 12-3 To install a shared 5520 AMS client in Red Hat Enterprise Linux ........ 12-8
Procedure 12-4 To install a shared client with the shared client wrapper ............. 12-10
Procedure 12-5 To configure the presentation server and login title to use the
shared client wrapper ....................................................... 12-12
Procedure 12-6 To launch and update the 5520 AMS client ............................... 12-14
Procedure 12-7 To update permissions for the plug-ins directory ....................... 12-19
Procedure 12-8 To make the site name visible in the GUI login window when
multiple users access the shared 5520 AMS client in Red Hat
Enterprise Linux .............................................................. 12-19
Procedure 12-9 To display hours in the 0 to 24 convention in the 5520 AMS client ... 12-20
Procedure 12-10 To change a default user password in the 5520 AMS GUI ............. 12-21
Procedure 12-11 To add a license key from the 5520 AMS GUI ........................... 12-22
Procedure 12-12 To add a license key from the 5520 AMS server ........................ 12-23
Procedure 15-1 To generate a hostid ........................................................... 15-3
Procedure 15-2 To install the 5520 AMS solution for migration ............................. 15-4
Procedure 15-3 To install 5520 AMS solution software components for migration .... 15-22
Procedure 16-1 To migrate the switchover_hook.sh script .................................. 16-3
Procedure 16-2 To enable SSL with a customized keystore ................................. 16-4
Procedure 16-3 To configure data replication between sites ............................... 16-6
Procedure 16-4 To copy data files from a backup file (interactive mode) .............. 16-12
Procedure 16-5 To copy data files from a backup file (non-interactive mode) ........ 16-14
Procedure 16-6 To start a server .............................................................. 16-18
Procedure 16-7 To check the migration status .............................................. 16-20
Procedure 16-8 To update the anonymous FTP user path ................................. 16-22
Procedure 17-1 To import GUI settings ......................................................... 17-3
Procedure 17-2 To delete the former site of the earlier 5520 AMS release .............. 17-5
Procedure 18-1 To uninstall the 5520 AMS NE plug-ins, 5529 Enhanced Applications
and plug-ins, and patches and emergency fixes together or
individually ...................................................................... 18-6
Procedure 18-2 To uninstall the earlier 5520 AMS client application in Windows ....... 18-8
Procedure 18-3 To uninstall the 5520 AMS client application in Red Hat Enterprise
Linux ............................................................................. 18-9
Procedure 18-4 To uninstall the 5520 AMS server ........................................... 18-11
Procedure B-1 To install the 5520 AMS solution for manual in-place migration ........... B-9
Procedure B-2 To stop a server in a simplex setup or all servers in a cluster setup .... B-24
Procedure B-3 To disable SSL .................................................................... B-25
Procedure B-4 To activate a server ............................................................. B-26
Procedure B-5 To activate a software plug-in ................................................. B-28
Procedure B-6 To copy data files from the previous release (interactive mode) ........ B-32
Procedure B-7 To copy data files from the previous release (non-interactive mode) ... B-34
Procedure B-8 To uninstall software plug-ins after migration .............................. B-41
Procedure B-9 To uninstall a software plug-in manually after migration ................. B-43
Procedure B-10 To uninstall a 5520 AMS patch ................................................ B-44
Procedure B-11 To uninstall the earlier 5520 AMS server after migration ................ B-45
xvi August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
List of procedures
Procedure B-12 To stop a server in a simplex setup or all servers in a cluster setup ... B-46
Procedure B-13 To activate a server ............................................................B-46
Procedure B-14 To start a server ................................................................ B-47
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 xvii
List of procedures
xviii August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
Getting started
1 Whats new
2 Overviews
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015

August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
1 Whats new
1.1 Whats new in Release 9.4 1-2
1.2 Whats new in Release 9.3.10 1-3
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 1-1
1 Whats new
1.1 Whats new in Release 9.4
Table 1-1 Whats new in Release 9.4 (p. 1-2) lists the new 5520 AMS features and
enhancements added to the 5520 AMS Installation and Migration Guide for Release
9.4.
Table 1-1 Whats new in Release 9.4
Feature/enhancement Description See
New features/enhancements
EMS migration engine Added information regarding the automated in-place migration. Chapters 14,15, 16, and
implementation Appendix B
Migration to 5520 AMS 9.4. Updated migration path to 5520 AMS, Release 9.4. Chapters 13, 14, and
Appendix B
Support for sudo to Updated procedure to configure sudo automatically and Procedures 6-1 and 6-2,
execute root only manually. and 13.1
commands
Red Hat Enterprise Linux Updated the RHEL version to 6.5. Section 2.2
version
VMware setup Added information about the pre-requisite for a VMware setup. Table 6-1
pre-requisite
Subnet address Modified the steps to include the subnet address configuration. Procedures 6-1, 9-1, and
configuration 15-2
Environment variables Added new environment variables to the table. Table 2-2
ams_cluster start/restart Added a note for starting a database server manually when the Subsection Overview
server is down due to split brain condition.
Documentation changes
To prepare the 5520 AMS Made the FTP connectivity verification an optional step and Procedure 4-1
infrastructure added a note for the same.
Deactivating a patch Added the step to deactivate a patch during uninstalltion of a Procedure Uninstalling
5520 AMS patch. the earlier 5520 AMS
release
Configure locale settings Updated the procedure to configure locale settings for Red Hat Procedure 4-9
Enterprise Linux.
Configuring geographic Added a step to stop the servers before performing the switch Procedure 10-6
redundancy between active and standby sites.
Environment variables Added new environment variaables to the table. Table 2-2
Database storage Added information about database storage configuration. Sub-section Configuring
LVM volumes
Table 6-1
GUI Settings Import Added a note for the support of GUI Settings Import option. Section 17.3
Edit the config.ini file to Updated the procedure to modify the config.ini file to display Procedure 12-9
display hour convention the required hour convention.
Install 5520 AMS client Updated the result for single and shared client installation. Procedures 12-1 and 12-3
Migration overview Added a caution note for 5529 Enhanced Applications and NE Section 13.1
plug-ins migration
(1 of 2)
1-2 August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
1 Whats new
Migration overview Added a caution note to not stop or restart a server when Section13.1
migration is in progress.
Installing 5520 AMS for Added a note to indicate that additional 5529 Enhanced Section 15.5
migration Applications and NE plug-ins can be installed in the current
release.
In-place migration Updated the information to indicate that in an in-place Sub-section In-place
migration scenario the new release of the 5520 AMS is installed migration
and activate on the same server.
Geographically redundant Added information about the health status of AMS system and Sub-section Health
switchover scenarios geographically redundant switchover scenarios. state of a 5520 AMS
system
Table 3-5
Solaris client All the instances of Solaris client support has been removed from -
the document.
GSIP 5.0 Support Added the latest GSIP version supported. Section 17.2
Geographic redundancy Added a note for enabling the geographic redandancy settings Section 15.5
post migration.
MaxStartups Removed the section for configuring the maximum number of -

concurrent SSH connections.
Simplex to Cluster Updated the procedure for changes in converting from a simplex Section 9.1
to cluster setup.
PermitRootLogin Added a note for enabling PermitRootLogin parameter in the SSH Procedure 6-1
parameter configuration file.
Generating hostid Added information about generating a hostid. Section 15.4
Tables 14-3, 14-5, 14-6,
14-7, B-2, B-3, and B-4
(2 of 2)
1.2 Whats new in Release 9.3.10
Table 1-2 Whats new in Release 9.3.10 (p. 1-3) lists the new 5520 AMS features and
9.3.10.
Table 1-2 Whats new in Release 9.3.10
Checking alarm rules Added an instruction to check alarm rules after migrating to a Section 14.4
new 5520 AMS release or updating NE plug-ins.
Migration paths to Migration to 5520 AMS Release 9.3.10 is supported from: Chapters 13, 14, 15, 16,
5520 AMS Release 9.3.10 5520 AMS Release 9.2.10 and 17
5520 AMS Release 9.2.30
Red Hat Enterprise Linux Added Red Hat Enterprise Linux client information. Chapter 12
client Procedure 18-3
(1 of 2)
1 Whats new
Firewall rules Moved updating firewall rules section to a chapter Chapter 11
ams_server version Added a procedure to verify the installed software components
GSIP release 4.8 Added the latest GSIP version supported. Section 13.5
Server startup time Added note on the time taken on a first time server startup. Procedure 7-2
Modifying the Added a note on modifying properties in amsclient.ini while Section 12.4
amsclient.ini properties launching the 5520 AMS client from absolute path.
Sitename.xml Update the sitename.xml information while converting from Procedure 9-1
simplex server to cluster server.
Site name Updated the note to list the special characters that are allowed Procedure 6-1and 15-2
while searching the name of a site name.
Configuration directory Updated the path of the configuration directory . Procedures 12-9 and
12-10
Install shared client in Updated the procedure to edit the config.ini file . Procedure 12-9
Windows
To activate a server Added a warning and note to the procedure. Procedure B-4
Uninstall 5520 AMS client Updated the procedure to uninstall 5520 AMS client application Procedure 18-3
in Red Hat Enterprise in Red Hat Enterprise Linux
Linux
Installation and migration Updated the references to Solaris and Red Hat Enterprise Linux Chapters 6 and 15
procedures for all the installation and migration types.
Installer prompts for Removed the table listing the questions not prompted by the Section 15.2
in-place migration installer during an in-place migration and updated the content
and added a note
Install a shared client in Updated the procedure to install a shared client in Windows for Procedure 12-2
Windows the user workspace configuration
Uninstalling software Added a note on clearing the exception thrown by Windows Section 18.2
plug-ins client when uninstalling a plug without first deactivating it
Installing 32-bit Added information about 32-bit compatibility packages on Red Section 15.5
compatibility packages on Hat Linux Enterprise systems.
Red Hat Linux Enterprise
systems
(2 of 2)
9.3.0.
1 Whats new
Migration paths to Migration to 5520 AMS Release 9.3.0 is supported from Release Sections 13.1, 13.3,
5520 AMS Release 9.3.0 9.2.30. 13.4, 13.5, and 13.9
Red Hat Enterprise Linux Added a section to describe the configuration of LVM volumes. Sub-section Configuring
support LVM volumes
Updated the illustration of the cluster installation of 5520 AMS. Figure 2-2
Updated the LVM volume configuration pre-requisites. Table 6-1
Added Red Hat Enterprise Linux information. Procedures 4-1
Updated information related to Solaris systems and Red Hat Section 4.1
Enterprise Linux systems.
Virtual machine Added a note on configuring the virtual machine. Section 4.1
ams_server status output Updated the ams_server status output. Procedures 10-2 and 16-3
Installer question for Updated the installer question for the configuration of the
shared and database shared data and local database directory.
directory
Multicast bind IP address Added a note on multicast bind IP address. Section 3.2
MaxStartups parameter Updated the command to configure the MaxStartups parameter. -
9.2.30.
Migration paths to Migration to 5520 AMS Release 9.2.30 is supported from: Sections 13.1, 13.4,
5520 AMS Release 9.2.30 5520 AMS Release 9.1.0 13.2, 13.3, and 13.4
(1 of 2)
1 Whats new
Installing the 5520 AMS Regrouped the 5520 AMS installation overview sections, and Chapter 3
solution added sections on the installation overview of software plug-ins
and emergency fixes.
Regrouped the information on setting up the 5520 AMS Chapter 4

infrastructure.
Added a section on extracting the downloaded installation files. Section 5.2
Regrouped the 5520 AMS installation-related sections. Chapter 6
Added a section to provide an overview of installing the 5520

AMS solution.
Added a section on the pre-requisite tasks to be performed

before the 5520 AMS installation.
Updated the 5520 AMS installation procedures to include
information to install the 5520 AMS solution.
Added a section to describe the option to save the

configuration settings for installation of a 5520 AMS server.
Added a section on installing the 5520 AMS NE plug-ins, 5529

Enhanced Applications and plug-ins, and patches and
emergency fixes.
Updated the installation procedures during migration to include

information on installing the 5520 AMS solution in an in-place
and out-of-place migration scenario.
Regrouped the 5520 AMS uninstallation sections, and added Chapter 18
sections on the uninstallation of software plug-ins and
emergency fixes.
Added information on installing and activating the 5520 AMS Section 2.1
solution.
Automatic site switchover Added information on the automatic site switchover in Automatic site
geographically redundant setups. switchover
Added information on ping-pong protection. Section 10.2
Updated the procedure to include the step to enable automatic Procedure 10-2
switchover.
Updated the procedure to include a note regarding disabling Procedure 10-7

geographical redundancy.
Improved 5520 AMS Updated the migration chapters to include information on the Chapters 13, 14, 15, 16,
upgrade time data migration strategies depending on the migration path. and 17
Limiting the bandwidth Added a note on limiting the bandwidth across the WAN for Section 10.3
across the WAN for replication, in a geographically redundant setup with two data
replication servers at the standby site.
(2 of 2)
2 Overviews
2.1 Guide overview 2-2
2.2 Installation and migration overview 2-2
2.3 5529 Enhanced Applications 2-10
2.4 Technical support 2-10
2 Overviews
2.1 Guide overview
The 5520 AMS Installation and Migration Guide includes procedures to:
Prepare hardware for installation of Install emergency fixes

the 5520 AMS Install the 5520 AMS client for
Prepare a network for 5520 AMS Windows, and Red Hat Enterprise
operation Linux
Secure your 5520 AMS installation Migrate data from an earlier release
Install the 5520 AMS software of the 5520 AMS to the 5520 AMS,
Install software plug-ins Release 9.4.
Install the 5520 AMS patches Uninstall the 5520 AMS
Each installation chapter includes pre-installation, installation, and post-installation

tasks.
You can install and activate the 5520 AMS solution comprising the 5520 AMS
software, 5520 AMS NE plug-ins, 5529 Enhanced Applications and plug-ins,
patches and emergency fixes.
To perform the procedures in this guide, you must be familiar with the operating
system.
2.2 Installation and migration overview
The 5520 AMS uses a client-server architecture pattern. Management applications

operate on a central server infrastructure, called the site, and clients.
The 5520 AMS server software supports installation and migration in several
configurations:
In a standalone (simplex) configuration on a single server
As a cluster of linked machines, each able to serve a dedicated role as an
application or data server and provide load sharing and redundancy support
At multiple sites, each consisting of a single server or a cluster of servers, to
provide backup for the active site in the event of a disaster.
Note Alcatel-Lucent recommends that all 5520 AMS upgrades be

staged beforehand to check if any critical issue is detected during the
staging. For assistance with staging, contact your local
Alcatel-Lucent support representative. See Section 2.4 Technical
support (p. 2-10) for information on technical support.
The 5520 AMS is designed to be installed on SPARC- or x86- based servers running
the Solaris 10 or x86 based servers running the Red Hat Enterprise Linux 6.5
operating system.
The client application of the 5520 AMS can be installed on the workstation of each
user in either the Windows, or Red Hat Enterprise Linux operating systems.
Installation on a presentation server allows administrators to install and maintain a
single copy of the client application for use by many operators.
2 Overviews
Installation terms
Table 2-1 Key terms (p. 2-3) defines key terms used to describe 5520 AMS
configurations.
Table 2-1 Key terms
Term Definition
Site A single geographic location where one or more 5520 AMS

servers are configured and connected by a low-latency LAN.
Each server can function as:
an application server
a data server
a presentation server
a data and application server combination
Active site The site where the 5520 AMS configuration is fully operational.
There can be only one active site.
Standby site The site that serves as a backup for the active site. Typically,
the standby site is at a different geographic location, connected
over a WAN. The MySQL database and shared directories are
replicated between the two sites, so that a set of current data
is continually maintained at the standby site.
Preferred data server The preferred data server is the server that has priority to
become the active server at startup of the cluster.
Non-preferred data The non-preferred data server is the server that does not have
server priority to become the active server at startup of the cluster.
Secondary database Acts as the preferred data server at the standby site. It may have
its own alternate.
Active data server Within a site, only one MySQL server is active. This is the active
data server. At startup, the MySQL server on the preferred data
server is the master.
Standby data server Within a site, a backup MySQL server can be ready to start when
the active data server fails. This is the standby data server.
The standby data server initiates MySQL replication requests to
receive updates from the active data server.
Shared data directory All data to which all servers need access is stored on the shared
data directory. You must configure this directory when installing
the 5520 AMS.
The contents of this directory are replicated between servers
using the ZFS file system on Solaris systems and on the LVM
volume on Red Hat Enterprise Linux systems.
Local data directory Data that is not required by all servers is stored in the local data
directory. You must configure this directory when installing the
5520 AMS.
2 Overviews
Before you can perform the procedures in this guide, your hardware infrastructure
must be in place. For detailed hardware requirements and network specifications, see
the 5520 AMS Solution Planning Guide.
Note 1 The performance of the 5520 AMS has been tested and
certified assuming that it has full use of system resources that meet the
specifications described in the 5520 AMS Solution Planning Guide.
Adding third-party applications to the 5520 AMS environment can
have unpredictable effects on system performance. As a result,
Alcatel-Lucent makes no warranty regarding the performance of the
5520 AMS when third-party applications are installed on 5520 AMS
application or data servers.
Note 2 If you use Alcatel-Lucent 5529 Enhanced Applications in
addition to the 5520 AMS, contact your sales representative for
further information about your specific installation requirements.
When you have performed the installation procedures in this guide, the 5520 AMS
software and client will be running and ready for an administrator to perform
site-specific configuration.
For information about administrative functions, including management of
server-client communication, users, NE communication, schedules, links, and codes,
see the 5520 AMS Administrator Guide.
For information about user functions, including monitoring and fault management,
and tasks that are common to all NEs, see the 5520 AMS User Guide.
For information specific to management of a particular NE, including migration to a
new major release, see the Operations and Maintenance guide for the NE.
Environment variables
The 5520 AMS defines environment variables for directories on the servers. These
variables can be used by the amssys user. Table 2-2 Environment variables (p. 2-4)
describes environment variables used in the procedures found in this guide. The
environmental variables define the path related to the active 5520 AMS release only.
The $PATH variable for the amssys user includes the directory where most scripts
are found. Therefore, you do not need to enter a path to run a script when you are
logged in as amssys. You do not need to enter ./ before the script name.
Table 2-2 Environment variables
Environment variable Description
$AMS_EXTERNAL_LOCALDATA_HOME The directory where data is stored that is external to the 5520 AMS
software and that is local to one server. An example is
/var/opt/ams/local/common.
$AMS_LOCAL_DATA_DIR The directory where local data is stored. By default, this is /var/opt.
$AMS_LOCALDATA_HOME The subdirectory where data files that are separate from the database
are stored. An example is /var/opt/ams/local/ams-9.4-999000.
(1 of 2)
2 Overviews
Environment variable Description
$AMS_EXTERNAL_SHAREDDATA_HOME The directory where data is stored that is external to the 5520 AMS
software and that all servers need access to. An example is
/var/opt/ams/shared/common.
$AMS_SHARED_DATA_DIR The directory where shared data is stored. By default, this is /var/opt.
$AMS_SHAREDDATA_HOME The directory where shared data is stored. An example is

/var/opt/ams/shared/ams-9.4.00-999000.
$AMS_SOFTWARE_HOME The directory where the 5520 AMS software is stored. An example is
/opt/ams/software/ams-9.4.00-999000.
$AMS_LOG_DIR The directory where 5520 AMS logs are stored. An example is
/var/opt/ams/local/ams-9.4.00-999000/traces/log.
$AMS_CONF_DIR The directory where configuration files for the 5520 AMS are stored. An
example is /opt/ams/software/ams-9.4.00-999000/conf.
$PLATFORM_SCRIPTS_DIR The directory where platform scripts for the 5520 AMS are stored. An
example is /opt/ams/software/ams-9.4.00-999000/lib/platform/bin.
$AMS_DEBUG_DIR The directory where 5520 AMS traces and debug files are stored. An
example is /var/opt/ams/local/ams-9.4.00-248124/traces/debug.
$AMSSFTPDB_USER_HOME_DIR The directory where the user home directory is located.
$AMS_DATABASE_DIR The directory where the database directory is located
(2 of 2)
5520 AMS server roles

You can assign roles to servers during installation. A server can function as an
application server (A), a data server (D), a combination of application and data server
(A+D), or an arbiter server. You can also use a presentation server to deploy the
5520 AMS client application.
An application server hosts the 5520 AMS software, the JBoss server, and
software plug-ins that support specific NEs and provide expanded capabilities.
A data server hosts the MySQL database that supports the 5520 AMS, and stores
data required by the 5520 AMS application.
A presentation server, although not configured as part of 5520 AMS server
installation, is a server on which you install a shared 5520 AMS client for use by
many operators.
An arbiter server avoids the potential active/active server condition in an A+D,
A+D cluster setup. If the active server becomes unavailable because of hardware
or software failure, the standby server negotiates with the arbiter server to take
ownership of the database and assume the role of the active server.
To avoid the active/active server condition, the arbiter server acts as an external
party in an A+D, A+D setup that decides which of the two servers can take
ownership of the database, and become the active server.
In the absence of an arbiter server in the A+D, A+D cluster setup, an active/active
server condition arises when the communication is lost between the servers due
to communication failure, and the standby server cannot reach the active server.
The standby server assumes that the active server is unavailable, and becomes the
active server. The clients connected to the active server will continue to function,
assuming the client-facing interface is still up. This could result in two active
servers in the cluster, and two data sets will be evolving separately. The
2 Overviews
5520 AMS cannot merge these data sets, impacting the entire 5520 AMS. The
5520 AMS raises Risk for dual master critical alarm in both data servers. When
the communication is restored, upon identifying that there are two active servers,
the 5520 AMS goes down automatically. The system administrator needs to
manually start the 5520 AMS and choose the server whose data needs to be kept.
Standalone (simplex) installation

In a standalone (simplex) installation, a single server fills both application and
database roles. Operators connect to the server using the client application, which
can be installed on individual workstations or on the 5520 AMS server. The client
can be installed on the server either as separate copies in the home directory of each
user, or as a single shared client installation. Figure 2-1 Standalone (simplex)
installation of the 5520 AMS (p. 2-6) shows an example of a standalone (simplex)
installation.
Figure 2-1 Standalone (simplex) installation of the 5520 AMS
WAN DCN
Presentation Application
server and data server
Operators Network Elements
Clusters: redundancy and load-balancing

In a cluster installation, two or more servers are linked together as a Site object. Each
server in the cluster can act as an application server, a data server, or both. A typical
cluster can include two application servers to share the processing load, an active
data server, and a standby data server.
The group of data servers in a cluster provide redundancy for the 5520 AMS
database. The shared file system copies shared data between the servers. MySQL
replication copies database commands. The set of application servers in a cluster
provide load sharing and some redundancy.
Note Do not mix the machine architectures and operating systems.

Use the same setup for the same operation or configuration.
When the application server is fully started, the 5520 AMS client discovers the
application and data servers in the cluster and shows them as objects in the GUI.
2 Overviews
When installing in a cluster configuration, you require an appropriate 5520 AMS

license. When requesting your license, you must provide the host IDs for all
application servers in the cluster. To add new application servers in the future, you
must request a new license by providing all server host IDs, including that of the new
server. Figure 2-2 Cluster installation of the 5520 AMS (p. 2-7) shows an example
of a cluster installation.
Figure 2-2 Cluster installation of the 5520 AMS
Client
network LAN DCN
Presentation
Operators server
MySQL replication Network
Elements
Shared Replication
Application + Application +
standby database active database
Non-preferred Preferred
data server data server
Check updates
MySQL
Updates replication
MySQL MySQL
Slave Master
Non-preferred Preferred
data server data server
Check updates
Shared
Updates replication
Shared Shared
Filesystem Filesystem
Database replication
The 5520 AMS uses MySQL as a database. MySQL replication is done in
master/slave mode. The master MySQL server runs on the active data server and the
slave runs on the standby data server. If the preferred data server is active when the
cluster is started, it becomes the active data server.
Shared data replication

Application servers store NE-related files, such as NE backups, NE software, and
SIP configuration files, in the shared data directory. When a file is received from an
NE, the application server stores it first in the local data directory, then sends it to the
active data server for storage in the shared data directory. The information is then
deleted from the local data directory. When information is sent to the NE, the reverse
process is used. The application server requests the information from the active data
server, stores it in the local data directory, then sends it to the NE. Data is transferred
using SFTP.
2 Overviews
To ensure that the data is stable when a transfer takes place, frozen snapshots of the
file system are transferred. To allow this to be done, the shared files must be stored
on a ZFS file system on Solaris systems, and on the LVM volume on Red Hat
Enterprise Linux systems.
Note 1 In a cluster setup, the mount points of the shared and
database file systems in the active data server and the standby data
server must be the same.
Note 2 When the 5520 AMS server is stopped, the shared data
directory on the active data server in a redundant database
configuration is changed to read-only mode. Changes to the shared
data must be done on a running active data server. It is not
recommended to manually change the file system to read/write mode.
Sites: geographic redundancy

By configuring servers at multiple sites, you provide geographic redundancy, which
protects your network from a disaster-related failure at the active site.
Each site is a cluster which, in the simplest case, can consist of just a single server,
with one site acting as a backup server on standby.
Note Do not mix the machine architectures and operating systems.
Use the same setup for the same operation or configuration.
Figure 2-3 Simplest geographic redundancy installation of the 5520 AMS (p. 2-8)
shows an example of geographic redundancy on a simplex installation.
Figure 2-3 Simplest geographic redundancy installation of the 5520 AMS
Presentation
server
Active application
and data server
Client
network DCN
5520 AMS GUI Backup

transfer
Standby application
and data server
2 Overviews
In a more typical installation, each site is a separate cluster, with one active and one
on standby.
At the active site, all applications servers are operational and share the processing
load. An active data server is supported by a local standby server ready to take
over in the event of failure of the preferred server.
At the standby site, a second pair of servers the secondary data server and its
alternate are configured and running, but the application servers are inactive.
Figure 2-4 Typical geographic redundancy installation of the 5520 AMS (p. 2-9)
shows an example of geographic redundancy on a cluster installation.
Figure 2-4 Typical geographic redundancy installation of the 5520 AMS
Active site Standby site
WAN
Application Application Application Application

server server server server
LAN LAN
Active Standby Standby Standby

data data data data
Legend:
Shared file system replication
MySQL replication
Regardless of the installation, the shared file system is replicated between the active
and standby data servers. MySQL replication copies database commands between
the active data servers at the active and standby sites. This ensures that the same
updates to the database are executed at both sites.
In a cluster installation, data is copied from the active data server at the active site to
the standby data server at the standby site. If the active data server at the active site
fails, the standby server at the active site becomes an active data server. At that time,
data is copied from the new active data server at the active site to the standby data
server at the standby site.
2 Overviews
In the event that both data servers fail at the active site, a manual switchover is
required to change the active site.
Note In a geographically redundant setup, the mount points of the

ZFS shared and database replication file systems in the active data
server and the standby data server must be the same.
Using the 5520 AMS with a NAT server

You can use a NAT server between the 5520 AMS server and the client, or between
the 5520 AMS and the NEs. If you use a NAT server between the 5520 AMS and the
client, you may need to modify the application server configuration file. For
configuring the 5520 AMS to support NAT, see Chapter 8 Configuring the 5520
AMS to support NAT (p. 8-1).
If you use a NAT server between the 5520 AMS and the NEs, you need to perform
some configuration in the client. See the 5520 AMS Administrator Guide for more
information.
2.3 5529 Enhanced Applications
The 5529 Enhanced Applications are a set of optional products that expand the
management capabilities provided by the 5520 AMS. Each application provides a
specific management function. The supported applications are:
5529 Access Provisioning Center
5529 Inventory Data Manager
5529 Large-scale Release Manager
5529 OSS Alarm Dispatcher
5529 Statistics and Data Collector
For more information about one of the 5529 Enhanced Applications, see the product
documentation for the application.
2.4 Technical support
Include the release of the 5520 AMS and the 5520 AMS plug-in release and version
when reporting issues to Alcatel-Lucent Technical Support.
Procedure 2-1 To find contact information for technical assistance (p. 2-10)
describes how to find the contact information for technical assistance for a country.
Procedure 2-1 To find contact information for technical assistance

1 Go to http://support.alcatel-lucent.com.
2 Log in to the Alcatel-Lucent Customer and Business Partner Portals with the user
name and password for your OLCS account.
2 Overviews
Result: A customized Customer Center page opens.
3 Under Product Technical Support, select a country.
Result: The Alcatel-Lucent Support Contact Numbers window opens and displays
the phone and e-mail contact information for technical assistance for the selected
country.
2 Overviews
Installing the 5520 AMS
3 5520 AMS installation overview
4 Setting up 5520 AMS infrastructure
5 Downloading software for the 5520 AMS and 5529 Enhanced

Applications
6 Installing the 5520 AMS solution components
7 Activating, starting and stopping the servers
8 Configuring the 5520 AMS to support NAT
9 Converting a simplex installation to a cluster
10 Configuring geographic redundancy
11 Updating firewall rules
12 Installing the 5520 AMS client

3.1 Simplex installation overview 3-2
3.2 Cluster installation overview 3-3
3.3 Geographic redundancy installation overview 3-7
3.4 Software plug-in installation overview 3-12
3.5 Patch installation overview 3-14
3.6 Emergency fix installation overview 3-18
3.1 Simplex installation overview
This section describes the simplex installation case, in which the 5520 AMS server
runs entirely on a single machine. Procedures include installation and
post-installation tasks, both mandatory and optional. Verify that all mandatory
procedures have been performed.
Note 1 Alcatel-Lucent recommends that you review the 5520 AMS
Solution Planning Guide before you proceed to install the 5520 AMS.
Note 2 This section describes the installation of the 5520 AMS,
Release 9.4. If you are migrating from an earlier release of the
5520 AMS, see Chapter 14 Migration scenarios and associated task
list (p. 14-1) for additional procedures to migrate your data.
Installing the 5520 AMS puts the software files in the correct location ready for use.
However, until you activate a server, the server is in a passive, standby mode.
Activating the software ensures that the plug-in installation environment is ready and
that it is safe to start the server.
Starting the server starts the 5520 AMS processes.
The 5520 AMS must be able to resolve the hostname. During the installation of the
5520 AMS, the installer checks if the hostname has been configured in the /etc/hosts
file of the server. If the hostname is not found, the installer exits with an error
message indicating that the hostname does not exist in the /etc/hosts file.
Different components of the 5520 AMS are installed in different directories on the
server; you are prompted for these locations during installation. This includes
separate locations for:
5520 AMS server software
MySQL database
Local data storage
Shared data storage
Choose and configure these locations before starting your installation.

When you install the 5520 AMS, the following user accounts are created on the
server:
Table 3-1 User accounts
User account Description
amssys This account is used when starting the server. The default password for the
amssys user account is amssys. You will be prompted to change this password
when the installation is complete.
amsftp This account is used by the system for FTP operations. The default password
for the amsftp user account is amsftp.
amssftp This account is used by the system for SFTP operations. The default password
for the amssftp user account is amssftp.
Server installation tasks

Table 3-2 Install the 5520 AMS, Release 9.4 in a standalone (simplex) configuration
(p. 3-3) lists the tasks to install the 5520 AMS in a standalone (simplex)
configuration. Before you proceed, you need root access to the server. The root
account can perform any action.
Table 3-2 Install the 5520 AMS, Release 9.4 in a standalone (simplex) configuration
Task # Task See
1 Prepare the server infrastructure. Procedure 4-1 To prepare the 5520 AMS
infrastructure (p. 4-3)
2 Install and activate the 5520 AMS solution. Procedure 6-1 To install and activate the
5520 AMS solution (p. 6-4)
3 If you use a NAT server, configure the 5520 AMS to support Section 8.1 Configuring the 5520 AMS to support
NAT. NAT (p. 8-2)
4 Start the 5520 AMS. Procedure 7-2 To start a server (p. 7-2)
5 Install the 5520 AMS client and apply client updates. Chapter 12 Installing the 5520 AMS client (p.
12-1)
6 Apply 5520 AMS licenses to your server. Procedure 12-11 To add a license key from the
5520 AMS GUI (p. 12-22)
7 (Optional) Set up the server as a cluster server to simplify Chapter 9 Converting a simplex installation to a
future expansion to a cluster. cluster (p. 9-1)
You have completed the set of installation tasks.
3.2 Cluster installation overview
This section describes options for configuring a set of networked servers to work
cooperatively as a cluster, providing both load balancing and redundancy in case of
the failure of the application or data server. Procedures include pre-installation tasks,
installation, and post-installation tasks, both mandatory and optional. Verify that all
mandatory procedures have been performed.
Cluster configurations are described in more detail in Chapter 2 Overviews (p. 2-1).
Note This section describes the installation of the 5520 AMS,

Release 9.4. If you are migrating to the 5520 AMS Release 9.4 from
an earlier release of the 5520 AMS, see Chapter 14 Migration
scenarios and associated task list (p. 14-1) for additional procedures
to migrate your data.
Overview
In a cluster configuration, the 5520 AMS is installed on a set of servers in a network,
each filling specific roles and working together as a unit. Each physical server in the
cluster can function as:
An application server (A) running the 5520 AMS with either a master or
non-master application server role. Multiple running application servers will
balance the processing load between them, and if the master application server
fails, any of the available non-master servers can take over its role.
A data server (D) running the MySQL database and storing system and NE data
serving the 5520 AMS. Each cluster has one active data server and may have an
alternate on standby. If the active data server fails, the standby server
automatically takes over its role.
Both an application and data server (A+D), as both types can be installed on the
same physical server.
An arbiter server performing the arbiter functionality to avoid the potential
active/active server condition in a cluster A+D, A+D setup.
A cluster configuration provides redundancy for both application and data servers. If
the active data server fails, the standby data server can take over its role. Similarly,
if the application server fails, any of the available application servers can take over
its role. Cluster configuration also provides load balancing, because multiple running
servers can share processing demands.
Note In a cluster with a combinaton of application and data servers
(A+D), if both the data servers are down due to split brain condition,
you must manually start the server which has the most recent and
complete data using ams_server start. After the server is active, use
the ams_server start to bring up the other server as standby.
The ams_cluster start or restart brings up the most recent active data
server instead of the preferred data server.
Servers in a cluster use, at minimum, two IP addresses:

Cluster IP address: for communication among servers in the cluster. The
multicast IP address must be associated with the cluster IP address in the routing
table.
Network IP address: for communication to the NEs and the rest of the network
On Solaris systems, if IPMP is in use, the virtual IP address is used as the cluster IP
address.
Note 1 To change or add a specific sub-network for intra-cluster
communication in a cluster setup, contact your local Alcatel-Lucent
Customer Support representative.
Note 2 For multiple cluster configurations within the same LAN or
WAN, each cluster must have a unique multicast bind IP address. The
multicast bind IP address must not be reachable from other clusters
within the same LAN or WAN. For example, if two clusters have the
same multicast address, then these two clusters form a large cluster.
Servers can also be installed at multiple sites for geographic redundancy. If a failure
occurs at the active site, the standby site can be manually activated. Each site can be
a simplex or cluster setup. See Section 3.3 Geographic redundancy installation
overview (p. 3-7) for more information about geographic redundancy and for
information about installing at multiple sites.
Caution All data servers in the cluster must have the same amount
of memory. See the 5520 AMS Solution Planning Guide for
information about hardware requirements.
Note 1 When requesting your 5520 AMS license, you must

provide the host IDs of all servers that will constitute the cluster. If
you add another server, request a new license for the cluster that
includes host IDs of all servers, including the new server.
Note 2 If you use a machine with multiple NICs as the 5520 AMS
application server and need to launch the client using all available
interfaces, all the network IP addresses must be entered during
installation.
The 5520 AMS must be able to resolve the hostnames of all nodes in the cluster.
During the installation of the 5520 AMS in a cluster, the installer checks if the
hostnames have been configured in the /etc/hosts file of each server. If a hostname is
not found, the installer exists with an error message indicating that the hostname does
not exist in the /etc/hosts file.
When a master application server fails and its functions switch to another server, any
5520 AMS clients logged in to the server are logged off, displaying the message
Connection lost due to Master Application Server switchover.
When a new server is added to the cluster, 5520 AMS clients will not be logged off.
If a user tries to establish a connection while the server is starting up, the user
receives the message server currently in startup in the client login window.
Different components of the 5520 AMS are installed in different directories on the
server. You are prompted for these locations during installation. This includes
separate locations for:
5520 AMS server software
MySQL database
Local data storage
Shared data storage
Choose and configure these locations before starting your installation.

When you install the 5520 AMS, the following UNIX user accounts are created on
the server:
Table 3-3 UNIX user accounts
User account Description
amssys This account is used when starting the server. The default password for the
amssys user account is amssys. You will be prompted to change this password
when the installation is complete.
amsftp This account is used by the system for FTP operations. The default password
for the amsftp user account is amsftp.
amssftp This account is used by the system for SFTP operations. The default password
for the amssftp user account is amssftp.
The root account can perform all actions.
Caution On a cluster, passwords must be aligned at all times.
Cluster installation tasks

Table 3-4 Install the 5520 AMS in a cluster configuration (p. 3-6) provides the tasks
to set up a cluster. Before you proceed, you need root access to the servers.
However, until you activate a server, the server is in a passive, standby mode.
that it will be safe to start the server.
Starting the server starts the 5520 AMS processes.
Table 3-4 Install the 5520 AMS in a cluster configuration
Task # Task See

1 Set up the cluster infrastructure. Procedure 4-1 To prepare the 5520 AMS
2 Install and activate the 5520 AMS solution in a cluster Procedure 6-1 To install and activate the
5520 AMS solution (p. 6-4) to install a preferred
data server.
3 Start the preferred 5520 AMS data server. Procedure 7-2 To start a server (p. 7-2)
4 Start the alternate 5520 AMS data server.
5 Start one 5520 AMS application server.
6 Start the arbiter server.
7 Start additional application servers:

Verify that all processes on the application server you 5520 AMS Administrator Guide
started are running.
Start all additional application servers. Procedure 7-2 To start a server (p. 7-2)
(1 of 2)
Task # Task See
8 Verify that the IP addresses of the JBoss servers are added

to the /etc/hosts file of the machine that will be launching
the client.
9 If you will be using a NAT server between the application Procedure 8-1 To configure the 5520 AMS to
servers and the 5520 AMS client and the servers are on the support NAT (p. 8-2)
private side of the NAT server, add the translated IP
addresses to the configuration file for each application
server.
10 Install, launch, and download updates to the 5520 AMS Chapter 12 Installing the 5520 AMS client (p.
client. 12-1)
11 Apply licenses to all application servers. Procedure 12-11 To add a license key from the
5520 AMS GUI (p. 12-22)
12 Perform optional post-installation tasks. 5520 AMS Administrator Guide to display the
server process statuses and the cluster status.
You have completed the set of installation tasks.
(2 of 2)
3.3 Geographic redundancy installation overview
The 5520 AMS allows you to configure two sites, one in active mode and the other
in standby. Data is continually replicated between the sites so that in the event of the
failure of the active site, the standby site can take over all of its functions until the
problem is resolved.
Each site can be set up in a simplex or cluster configuration. For information on the
5520 AMS installation, see Chapter 6 Installing the 5520 AMS solution components
(p. 6-1).
Geographic redundancy requires configuration of file system replication of the
shared data between the active and standby site.
The 5520 AMS uses MySQL replication of database information between the active
and standby site. MySQL replication of database information allows updates made
to the database at the active site to be copied to the standby site in near real time.
Sites must be in perfect NTP synchronization. See Procedure 4-2 To configure an
NTP server on Solaris systems (p. 4-4) and Procedure 4-3 To configure an NTP client
on Solaris systems (p. 4-5) to configure NTP.
Site components
Each site in this configuration consists of one or more servers; if a site includes more
than one server, configure it as a cluster. All servers in the cluster must be connected
with a low-latency LAN. See the 5520 AMS Solution Planning Guide for detailed
system requirements and system specifications.
Caution All data servers in the geographically redundant

installation must have the same amount of memory. See the
5520 AMS Solution Planning Guide for information about hardware
requirements.
The minimum requirement for a site is that you have one application server and one
data server, or a combination of application and data server, and an optional arbiter
server.
Note 1 An arbiter server is recommended only when the servers in
the site are configured as a combination of application and data
server.
Note 2 An arbiter server performs the arbiter functionality in a
single cluster only. In a geographically redundant system, an arbiter
server performs the arbiter functionality only in the active site. If you
want to use an arbiter server in both sites, optionally you can install
an additional arbiter server in the other site. For information on
installing an arbiter server in a cluster, see Section 6.3 Installing the
5520 AMS solution (p. 6-4).
The sites must have different site names. All messages exchanged are identified by
site name.
Site configuration
At both the active and standby site, activate all application and data servers,
configure the data servers using the ams_geo_configure script and start the servers.
Health state of a 5520 AMS system

The health of the 5520 AMS system is checked periodically using the
amsgeomonitor process. The 5520 AMS system consists of multiple sites with
application or data servers, or a combination of application and data servers.
The health state of a system can be classified as follows:
Healthy: No problem has been detected.
Degraded: Problem has been detected but it is not critical.
Failed: A critical issue is affecting the performance of the system or does not
allow the system to function.
For more information on the health status, see the 5520 AMS Administrator Guide.
Loss of a site
If one site in a geographically redundant installation goes down, you can configure
the 5520 AMS to run a script that you have configured according to your
requirements. If the active site goes down, a switchover is required. You can perform
a manual switchover or use an OSS arbiter to automate the switchover process.
Note When the active or standby site goes down, there can be a
delay in the socket timing out. This will result in a corresponding
delay in the process monitor detecting that the site is down.
Configuring a script to run upon loss of a site

If the TCP socket connection to one site is closed or dropped the 5520 AMS invokes
the activeSiteDown.sh or stanbySiteDown.sh scripts. By default, these scripts return
a value of 0. You can modify them to run a script of your choice. See Procedure 10-3
To configure the 5520 AMS to run a script if one site is down (p. 10-6) for more
information.
Manual site switchover

If the active site fails, the servers at the standby site can be manually started. These
servers will use the data replicated in the shared folder to ensure continuity. See
Procedure 10-6 To switch between the active and standby site (p. 10-10) to perform
a switchover.
Automatic site switchover

An automatic site switchover is performed in the following scenarios:
If the active site is unavailable, and after twelve retries if the active site is still
unhealthy, an automatic site switchover is performed.
In case of an active-active site scenario, the following statuses will be checked to
determine the site which will become the active site:
Health status of both sites (The site must be healthy to become the active site).
AMS server status (The server should be in 'Starting' or 'Running' state).
System active time (If both sites are healthy, the site which has been healthy for the
longest time becomes the active site).
The other site switches to standby state.
In case of a standby-standby site scenario, the following statuses will be checked
to determine the site which will become the active site:
Health status of both sites (The site must be healthy to become the active site).
The last active time (If both sites are healthy, the site was last active becomes the
active site.
The other site switches to standby state.
Table 3-5 Scenarios for geographically redundant switchover (p. 3-9) summarizes
the scenarios that triggers site switchover in a geographically redundant setup.
Table 3-5 Scenarios for geographically redundant switchover
Local state (site) Local health (site) Remote state (site) Remote health (site)
Active Unhealthy Standby Healthy
Standby Healthy Active Unhealthy
Standby Unhealthy Unknown Unknown
Standby(1) Healthy(1) Standby(1) Healthy(1)
Active(2) Healthy(2) Active(2) Healthy(2)
Notes
(1) The local site has been active recently than the remote site.
(2) The local site has been started recently than the remote site.
The servers at the active site are started automatically and the server status is
monitored again. For information on the health statuses, see the 5520 AMS
Administrator Guide.
Note To configure the number of retries to check the health of the
system, modify the MAX_CRITICAL_COUNTER parameter in the
amsgeomonitor.conf file available in
$AMS_SOFTWARE_HOME/conf.
Ping-pong protection
In a ping-pong scenario, the system continuously switches over in a never-ending
cycle. For information on ping-pong protection, see Section 10.2 Ping-pong
protection (p. 10-2).
Automating site switchover using an OSS arbiter

You can configure an OSS such as IBM Tivoli Application Manager or IBM Tivoli
Services Manager to act as an arbiter for a geographically redundant installation. The
OSS must be connected to both sites using the client network or the DCN. Using the
synchronization network is not recommended.
The OSS arbiter periodically checks the data servers of the active site. If the active
site is down after five retries, the OSS arbiter initiates a switchover. After completing
the switchover the OSS arbiter exits. To restart monitoring at the new active site the
OSS arbiter has to be restarted manually.
Caution The OSS arbiter will initiate a switchover if it is unable to
connect to the active site after five retries. A switchover will be
initiated in the following situations:
The active site has been stopped for maintenance
The standby site can connect to the active site but the OSS arbiter
cannot, for example, if the network link between the OSS arbiter
and the active site is down.
Figure 3-1 Geographic redundancy installation of the 5520 AMS with an OSS arbiter
(p. 3-11) shows a geographically redundant installation with an OSS arbiter.
Figure 3-1 Geographic redundancy installation of the 5520 AMS with an OSS arbiter
OSS 5520 AMS client DCN NEs
Client
Network
Application Application Application Application
host A host B host W host X
Cluster Cluster
Network Network
Data Data Data Data

host C host D host Y host Z
Synchronization
Network
SITE 1 (WAN) SITE 2
Geographic redundancy installation tasks

installation (p. 3-11) describes the tasks to set up a geographically redundant
installation.
Table 3-6 Install the 5520 AMS, Release 9.4 in a geographically redundant installation
Task # Task See
1 Set up the active site. The site can consist of a single server running Procedure 4-1 To prepare the 5520 AMS
both the database and 5520 AMS application server, or a infrastructure (p. 4-3) to prepare the
multi-server cluster. 5520 AMS infrastructure.
2 Set up the standby site. The site can consist of a single server
running both the database and 5520 AMS application server, or a
multi-server cluster.
3 In a simplex setup, install and activate the 5520 AMS solution on the Procedure 6-1 To install and activate
standalone server in both active and standby sites. the 5520 AMS solution (p. 6-4)
In a cluster setup, install and activate the 5520 AMS solution on all
5520 AMS application servers and data servers, and optionally, the
arbiter server of a cluster in both active and standby sites.
4 Verify that the data servers at both sites have IP connectivity over
the network on which you need them to exchange data.
(1 of 2)
Task # Task See
5 Configure geographic redundancy on data servers. Section 10.3 Configuring geographic

redundancy (p. 10-3)
6 (Optional) Configure the 5520 AMS to run a script if one site is down. Procedure 10-3 To configure the
5520 AMS to run a script if one site is
down (p. 10-6)
7 (Optional) Configure the OSS arbiter. Procedure 10-4 To configure the OSS
arbiter in a geographically redundant
installation (p. 10-7)
8 (Optional) Start the OSS arbiter. Procedure 10-5 To start the OSS arbiter
in a geographically redundant
installation (p. 10-9)
9 Start the 5520 AMS. Procedure 7-2 To start a server (p. 7-2)
10 Verify that the IP addresses of the JBoss servers are added to the
/etc/hosts file of the machine that will be launching the client.
11 If you will be using a NAT server between the application servers Procedure 8-1 To configure the
and the 5520 AMS client and the servers are on the private side of 5520 AMS to support NAT (p. 8-2)
the NAT server, add the translated IP addresses to the configuration
file for each application server.
12 Install, launch, and download updates to the 5520 AMS client. Chapter 12 Installing the 5520 AMS
client (p. 12-1)
13 Apply licenses to all application servers at both sites. Procedure 12-11 To add a license key
from the 5520 AMS GUI (p. 12-22)
You have completed the set of installation and configuration tasks.
(2 of 2)
3.4 Software plug-in installation overview
This section describes the installation, activation and deactivation of 5520 AMS NE
plug-ins, or 5529 Enhanced Applications and plug-ins.
Installing and activating software plug-ins

Table 3-7 Install and activate a software plug-in (p. 3-13) lists the tasks to install and
activate the 5520 AMS NE plug-ins, or 5529 Enhanced Applications and plug-ins.
Note You can install and activate the 5520 AMS NE plug-ins, or
5529 Enhanced Applications and plug-ins simultaneously with the
5520 AMS core software. See Chapter 6 Installing the 5520 AMS
solution components (p. 6-1).
Before you proceed, ensure to install and activate the 5520 AMS, see Section6.3
Installing the 5520 AMS solution (p. 6-4) to install the 5520 AMS in the required
servers.
Table 3-7 Install and activate a software plug-in
Task # Task See
1 If the 5520 AMS is started, stop the 5520 AMS.
To stop the server in a simplex setup, use the ams_server stop command. Procedure 7-4 To stop a server
(p. 7-4)
To stop all servers in a cluster setup, use the ams_cluster stop command. Procedure 7-5 To stop a cluster
(p. 7-4)
2 Install and activate the software plug-in. Procedure 6-4 To install the
5520 AMS NE plug-ins, 5529
Enhanced Applications and
plug-ins, and patches and
emergency fixes together or
individually (p. 6-27) or
Procedure 6-7 To install,
activate, install and activate, or
deactivate the 5520 AMS solution
components (p. 6-35)
3 Start the 5520 AMS.
To start the server in a simplex setup, use the ams_server start command. Procedure 7-2 To start a server
(p. 7-2)
To start all servers in a cluster setup, use the ams_cluster start command. Procedure 7-3 To start a cluster
(p. 7-3)
You have completed the set of installation and activation tasks.
Deactivating software plug-ins

Table 3-8 Deactivate a software plug-in (p. 3-13) lists the tasks to deactivate the
5520 AMS NE plug-ins or 5529 Enhanced Applications and plug-ins.
Table 3-8 Deactivate a software plug-in
Task # Task See
1 Backup the currently installed 5520 AMS. 5520 AMS Administrator Guide
2 Stop the 5520 AMS.

To stop the server in a simplex setup, use the ams_server stop command. Procedure 7-4 To stop a server (p.
7-4)
(p. 7-4)
3 Deactivate the software plug-in. Procedure 6-6 To deactivate the

5520 AMS NE plug-ins, 5529
individually (p. 6-32)
(1 of 2)
Task # Task See
(p. 7-2)
(p. 7-3)
You have completed the set of deactivation tasks.
(2 of 2)
3.5 Patch installation overview
This section describes the installation and deactivation of a 5520 AMS patch.
Note In a cluster environment, you must install and uninstall the
patch on each server in the cluster.
Installing and activating patches

You can install and activate the 5520 AMS patches based on the case listed in Table
3-9 Install the 5520 AMS patches - cases (p. 3-14).
Table 3-9 Install the 5520 AMS patches - cases
Case # Case
1 Install a 5520 AMS patch on the base load.

2 Install a 5520 AMS patch when a previous 5520 AMS patch has already been installed.
For example, installing 5520 AMS Patch02 when 5520 AMS Patch01 is already installed.
Note 1 If you are installing a patch greater than 5520 AMS Patch01
when no prior 5520 AMS patch has been installed, you can install any
required version of the 5520 AMS patch. The higher version of
5520 AMS patch includes the overall fixes of all the lower versions of
5520 AMS patch. For example, 5520 AMS Patch03 contains the fixes
included in 5520 AMS Patch01, 5520 AMS Patch02, and 5520 AMS
Patch03.
Note 2 You can install and activate a 5520 AMS patch
simultaneously with the 5520 AMS, 5520 AMS NE plug-ins, 5529
Enhanced Applications and plug-ins, and emergency fixes. See
Chapter 6 Installing the 5520 AMS solution components (p. 6-1).
Caution A cluster installation must not have two servers running

with different plug-ins installed. After you uninstall plug-ins from one
server, stop the other server before starting the updated server.
Table 3-10 Install and activate a 5520 AMS patch (p. 3-15) lists the tasks to install
and activate a 5520 AMS patch.
Table 3-10 Install and activate a 5520 AMS patch
Task # Task See
2 Perform one of the following steps: The release notices for the applicable
If you are installing new patches for 5529 Enhanced Applications, 5529 Enhanced Applications patches
prepare the applications for uninstallation.
If you are not installing new patches for 5529 Enhanced

Applications, proceed to task 3 (p. 3-15).
3 Uninstall the current 5520 AMS client. Section 18.6 Uninstalling a 5520 AMS
client (p. 18-8)
To stop the server in a simplex setup, use the ams_server stop Procedure 7-4 To stop a server (p. 7-4)
command.
To stop all servers in a cluster setup, use the ams_cluster stop Procedure 7-5 To stop a cluster (p. 7-4)
command.
5 Perform one of the following steps: 5520 AMS Administrator Guide
If SSL is enabled, disable SSL.
Perform this step only on application servers or on combination of
application and data servers.
If SSL is not enabled, proceed to task 6 (p. 3-15).
6 Deactivate and uninstall only the existing plug-ins that you will be Procedure 18-1 To uninstall the
patching, as applicable: 5520 AMS NE plug-ins, 5529 Enhanced
NE support plug-ins Applications and plug-ins, and patches
and emergency fixes together or
SIP application plug-in
SIP plug-ins for NEs
5529 Enhanced Applications
NE support plug-ins for the 5529 Enhanced Applications
Depending on the 5520 AMS patch installation case, proceed to

perform one of the following tasks:
If you are installing a 5520 AMS patch on the base load, proceed to
task 8 (p. 3-15).
If you are installing a 5520 AMS patch when a previous 5520 AMS
patch has already been installed, proceed to task 7 (p. 3-15).
7 Deactivate and uninstall the existing 5520 AMS patch. Procedure 18-1 To uninstall the
Uninstalling the existing 5520 AMS patch is optional. In case of issues 5520 AMS NE plug-ins, 5529 Enhanced
during upgrade, you can roll back to the previous 5520 AMS patch, if it Applications and plug-ins, and patches
is not uninstalled. and emergency fixes together or
8 Install and activate the 5520 AMS patch. Procedure 6-4 To install the 5520 AMS
NE plug-ins, 5529 Enhanced
Applications and plug-ins, and patches
or Procedure 6-7 To install, activate,
install and activate, or deactivate the
5520 AMS solution components (p. 6-35)
(1 of 2)
Task # Task See
9 Install and activate the new plug-ins, as applicable: Procedure 6-4 To install the 5520 AMS
NE support plug-ins NE plug-ins, 5529 Enhanced
SIP application plug-in and emergency fixes together or
SIP plug-ins for NEs individually (p. 6-27)
NE support plug-ins for the 5529 Enhanced Applications
Ensure to install and activate the NE support plug-ins before you install
and activate the NE support plug-ins for the 5529 Enhanced
Applications.
10 Enable SSL. 5520 AMS Administrator Guide

To start the server in a simplex setup, use the ams_server start Procedure 7-2 To start a server (p. 7-2)
command.
To start all servers in a cluster setup, use the ams_cluster start Procedure 7-3 To start a cluster (p. 7-3)
command.
12 Download and install a new 5520 AMS client. Chapter 12 Installing the 5520 AMS
client (p. 12-1)
(2 of 2)
Deactivating patches
You can deactivate the 5520 AMS patches based on the case listed in Table 3-11
Deactivating the 5520 AMS patches - cases (p. 3-16).
Table 3-11 Deactivating the 5520 AMS patches - cases
Case # Case
1 Deactivate the 5520 AMS patch on the base load.

For example, the 5520 AMS patch installed on the base load is having issues and requires
deactivation. Deactivating this 5520 AMS patch retains only the base load.
2 Deactivate a 5520 AMS patch to install a higher 5520 AMS patch.

For example, deactivating 5520 AMS Patch01 to install 5520 AMS Patch02.
3 Deactivate a 5520 AMS patch to roll back to a previous 5520 AMS patch.
For example, 5520 AMS Patch 02 is having issues and requires deactivation. If the 5520 AMS
Patch01 is deactivated, activate the patch. If the 5520 AMS Patch01 is uninstalled, install
the patch.
Table 3-12 Deactivate a 5520 AMS patch (p. 3-17) lists the tasks to deactivate a
5520 AMS patch.
Before you proceed, ensure that you are able to log in to the 5520 AMS server as
amssys.

Table 3-12 Deactivate a 5520 AMS patch
Task # Task See
command.
command.
3 Deactivate the 5520 AMS patch. Procedure 6-6 To deactivate the 5520 AMS
NE plug-ins, 5529 Enhanced Applications
and plug-ins, and patches and emergency
fixes together or individually (p. 6-32)
4 Depending on the deactivation case, perform one of the following

tasks:
If you deactivated the patch to continue with an unpatched
system, enable SSL. Go to task 5 (p. 3-17).
If you deactivated the 5520 AMS patch to install a higher Procedure 6-4 To install the 5520 AMS NE
5520 AMS patch or to roll back to a previous 5520 AMS patch, plug-ins, 5529 Enhanced Applications and
install and activate the required 5520 AMS patch. plug-ins, and patches and emergency fixes
together or individually (p. 6-27) or
Procedure 6-7 To install, activate, install
and activate, or deactivate the 5520 AMS
solution components (p. 6-35) for
installing and activating the patch.
Procedure 6-5 To activate the 5520 AMS
fixes together or individually (p. 6-29) or
activating the patch.
5 Enable SSL. 5520 AMS Administrator Guide


command.
command.
7 Uninstall the current 5520 AMS client. Section 18.6 Uninstalling a 5520 AMS
client (p. 18-8)
(1 of 2)
Task # Task See
8 Download and install the compatible 5520 AMS client. Chapter 12 Installing the 5520 AMS client
(p. 12-1)
(2 of 2)
3.6 Emergency fix installation overview
This section provides an overview of the installation, activation and deactivation of

emergency fixes.
Note In a cluster environment, you must install the emergency fix
on each server in the cluster.
Installing and activating emergency fixes

Table 3-13 Install and activate an emergency fix (p. 3-19) lists the tasks to install and
activate an emergency fix.
Note 1 You can install and activate any required version of the
emergency fix. However, to install and activate an emergency fix
when a newer version of the emergency fix is already activated,
deactivate the newer version of the emergency fix prior to installing
the older version of the emergency fix.
Note 2 You can install and activate an incremental version of the
emergency fix. For example, you can install and activate EF3 after
installing and activating EF1 and EF2.
Note 3 You can install and activate an emergency fix
simultaneously with the 5520 AMS, 5520 AMS NE plug-ins, 5529
Enhanced Applications and plug-ins, and patches. See Chapter 6
Installing the 5520 AMS solution components (p. 6-1).
Table 3-13 Install and activate an emergency fix
Task # Task See
command.
command.
3 Install and activate the emergency fix. Procedure 6-4 To install the 5520 AMS
NE plug-ins, 5529 Enhanced
or Procedure 6-7 To install, activate,
install and activate, or deactivate the
5520 AMS solution components (p.
6-35)

command.
command.
5 If the emergency fix you installed and activated contains any fix for
the 5520 AMS client, perform the following steps:
1) Uninstall the current 5520 AMS client. Section 18.6 Uninstalling a 5520 AMS
client (p. 18-8)
2) Download and install a new 5520 AMS client. Chapter 12 Installing the 5520 AMS
client (p. 12-1)
Note If you have not uninstalled the current 5520 AMS client, and
if you log in to the current 5520 AMS client after installing the
emergency fix containing any fix for the 5520 AMS client, the
following version incompatibility warning is displayed:
Incompatibility between GUI Version and the Server Version.
Download and install the new 5520 AMS client.
Deactivating emergency fixes

Table 3-14 Deactivate an emergency fix (p. 3-20) lists the tasks to deactivate an
emergency fix.
Table 3-14 Deactivate an emergency fix
Task # Task See
command.
To stop all servers in a cluster setup, use the ams_cluster stop Procedure 7-5 To stop a cluster (p.
command. 7-4)
3 Deactivate the emergency fix. Procedure 6-6 To deactivate the

5520 AMS NE plug-ins, 5529 Enhanced
To start the server in a simplex setup, use the ams_server start Procedure 7-2 To start a server (p.
command. 7-2)
To start all servers in a cluster setup, use the ams_cluster start Procedure 7-3 To start a cluster (p.
command. 7-3)
5 If the emergency fix you dectivated contained any fix for the
5520 AMS client, perform the following steps:
Section 18.6 Uninstalling a 5520 AMS
1) Uninstall the current 5520 AMS client.
client (p. 18-8)
2) Download and install the older compatible 5520 AMS client.
Chapter 12 Installing the 5520 AMS
client (p. 12-1)
4.1 Setting up the 5520 AMS infrastructure 4-2
4.2 Configuring NTP 4-4
4.3 Configuring storage 4-8
4.4 User and group IDs 4-11
4.5 Configuring locale settings 4-12
4.1 Setting up the 5520 AMS infrastructure
This section describes the requirements to set up a 5520 AMS infrastructure in a

simplex or cluster setup.
You can install the 5520 AMS on a virtual machine. For information on virtual
machines, see the 5520 AMS Server Configuration Technical Guidelines document.
Note Alcatel-Lucent does not recommend using the combination

of application and data server (A+D) on a single virtual machine.
To protect against connection failure, Alcatel-Lucent recommends that you use

redundant Ethernet interfaces. Also, it is recommended that you segregate the
network into three logical subnets: one for the client subnet, one for the server
subnet, and two for the internal LAN.
5520 AMS server requirements in a simplex setup

In a simplex setup, a 5520 AMS installation requires a server to run the 5520 AMS
application and database, and a network connection to client terminals and the NEs
that the server will manage. See the 5520 AMS Solution Planning Guide and the
5520 AMS Server Configuration Technical Guidelines document for details.
5520 AMS server requirements in a cluster setup

The cluster specific server hardware and network requirements are described in the
5520 AMS Solution Planning Guide. However, any cluster installation requires the
following configurations:
One or more servers running the same operating system to act as application
servers.
One or more servers running the same operating system to act as data servers;
each server can be an application server as well.
A dedicated subnet for local cluster communication.
On Solaris systems, ZFS pools are configured on both the preferred and
non-preferred data servers.
On Red Hat Enterprise Linux systems, LVM volumes are configured on both the
preferred and non-preferred data servers.
A low-latency LAN to connect the servers in the cluster, dedicated for use by the
5520 AMS.
Before you proceed, you need root access to the server.
Procedure 4-1 To prepare the 5520 AMS infrastructure

1 Install the operating system.
Note 1 For the Solaris operating system, install with the patch level
recommended in the 5520 AMS Release Notice.
Note 2 For the Red Hat Enterprise Linux operating system, ensure to
have the latest updates installed.
Note 3 See the 5520 AMS Solution Planning Guide for hardware
requirements and network specifications.
Note 4 Alcatel-Lucent recommends that you do not change the

default umask value of 022.
2 Verify network connectivity with the standalone server (in a simplex setup) or all
servers (in a cluster setup) on which you will install the 5520 AMS.
3 (Optional) Configure NTP. See Section 4.2 Configuring NTP (p. 4-4).
If you are setting up the infrastructure for a simplex setup, go to Step 7 (p. 4-3).
If you are setting up the infrastructure for a cluster setup, go to Step 4 (p. 4-3).
4 Configure swap space. See the 5520 AMS Solution Planning Guide for
recommendations.
5 Connect the servers in the cluster with a low-latency LAN and test their mutual
connectivity.
6 On Solaris systems, if your cluster includes non-preferred servers, set up IPMP

router interconnections to use a virtual IP address to represent each set of
redundant servers.
7 Depending on the type of setup, perform one of the following steps:
Setup Solaris Systems Red Hat Enterprise Linux systems
Simplex setup Configure ZFS pools. See Procedure 4-7 Configure LVM volumes. See
To configure ZFS pools (p. 4-9). Procedure 4-8 To configure LVM
volumes (p. 4-11).
Cluster setup Configure ZFS on both data servers. Configure LVM volumes on both
See Procedure 4-7 To configure ZFS data servers and a combination of
pools (p. 4-9). application and data servers. See
4-8 To configure LVM volumes (p.
4-11).
8 Configure locale settings. See Procedure 4-9 To configure the locale settings (p.
4-12).
4.2 Configuring NTP
Clocks within all servers that are part of 5520 AMS cluster must be synchronized
with each other as timestamps are used to ensure that the cluster remains internally
consistent. This can be achieved using a common NTP server that receives time
information from each clustered server. The following are example procedures to
configure NTP.
The following are example procedures to configure NTP.
On Solaris systems, use Procedure 4-2 To configure an NTP server on Solaris
systems (p. 4-4) to set up a standalone NTP server. Use Procedure 4-3 To configure
an NTP client on Solaris systems (p. 4-5) to set up an external synchronized NTP
server.
On Red Hat Enterprise Linux systems, depending on the type of configuration, use
the procedures in Table 4-1 Configure NTP on Red Hat Enterprise Linux systems (p.
4-4) to configure NTP.
Table 4-1 Configure NTP on Red Hat Enterprise Linux systems
Type of configuration See
Set up a standalone NTP server Procedure 4-4 To configure an NTP server on Red
Hat Enterprise Linux systems (p. 4-6)
Set up an external synchronized NTP server Procedure 4-5 To configure an NTP client on Red
Hat Enterprise Linux systems (p. 4-7)
Configure NTP clients to access the NTP server Procedure 4-6 To configure NTP clients to access
the NTP Server on Red Hat Enterprise Linux
systems (p. 4-7)
For more details on configuring an NTP server and NTP client on Solaris systems,
see the Solaris documentation.
For more details on configuring an NTP server and an NTP client on Red Hat
Enterprise Linux systems, see the Red Hat Enterprise Linux documentation.
Procedure 4-2 To configure an NTP server on Solaris systems
Use this procedure on Solaris systems to configure a server to act as an NTP server. The
NEs will synchronize with the 5520 AMS server for NTP information.
1 Log in to the server as root.
2 To switch to the /etc/inet folder, type:
cd /etc/inet
3 To create an NTP configuration file, type:
cp ntp.server ntp.conf
4 To open the configuration file, type:
vi ntp.conf
5 Choose the line server 127.127.XType.0 and change the line to:
server 127.127.1.0
6 Choose the line fudge 127.127.XType.0 stratum 0 and change the line to:
fudge 127.127.1.0
7 To start NTP manually, type:
svcadm enable ntp:default
Procedure 4-3 To configure an NTP client on Solaris systems
Use this procedure on Solaris systems to configure a server to act as an NTP client. The
NTP client will synchronize with the NTP server to retrieve time information.
2 To disable NTP, type:
svcadm disable svc:/network/ntp
3 To switch to the /etc/inet folder, type:
cd /etc/inet
4 To create an NTP configuration file, type:
cp ntp.client ntp.conf
vi ntp.conf
6 Remove the following line:
multicastclient 224.0.1.1
7 Add the following lines:
server IP address of ntp server
fudge IP address of ntp server
where:
IP address of NTP server is the IP address of the NTP server.
8 Perform one of the following steps:
To reboot the server (recommended), type:
shutdown -y -i6 -g0
To start NTP manually, type:
svcadm enable ntp:default
Procedure 4-4 To configure an NTP server on Red Hat Enterprise

Linux systems
Use this procedure on Red Hat Enterprise Linux systems to configure a server to act as
an NTP server. The NEs will synchronize with the 5520 AMS server for NTP information.
2 To install and enable NTPD on the Red Hat Enterprise Linux NTPD Server, type:
chkconfig ntpd on
3 To open the NTP configuration file, type:
vi /etc/ntp.conf
Note To deny all access to any machine, ensure that the line
restrict default ignore exists in the configuration file.
4 To add the IP address of the remote NTP server, type:
server remote_NTP_server
where:
remote_NTP_server is the IP address of the remote NTP server or the IP address of the public NTP
server located at www.ntp.org
5 To specifically authorize policy settings, type:
restrict remote_NTP_server mask netmask nomodify notrap noquery
where:
remote_NTP_server is the IP address of the remote NTP server or the IP address of the public NTP
server located at www.ntp.org
netmask is the network mask for the remote NTP server.
6 Save and close the configuration file.
Procedure 4-5 To configure an NTP client on Red Hat Enterprise

Linux systems
Use this procedure on Red Hat Enterprise Linux systems to configure a server to act as
an NTP client. The NTP client will synchronize with the NTP server to retrieve time
information.
Note Ensure that the NTP package is installed on the server. For
more information, see Procedure 4-4 To configure an NTP server on Red
Hat Enterprise Linux systems (p. 4-6).
vi /etc/ntp.conf
3 To add the site NTP server, type:
server site_NTP_server
where:
site_NTP_server is the hostname or IP address of the site NTP server.
4 Save and close the configuration file.
Procedure 4-6 To configure NTP clients to access the NTP Server on

Red Hat Enterprise Linux systems
Use this procedure on Red Hat Enterprise Linux systems to allow legitimate NTP clients
to access the NTP server.
Caution Ensure to check the security policies before applying

firewall rules to allow NTP synchronization.
Note 1 Ensure that an NTP server is configured in Linux. For more

information, see Procedure 4-4 To configure an NTP server on Red Hat
Enterprise Linux systems (p. 4-6).
Note 2 Ensure that an NTP client is configured in Linux. For more

information, see Procedure 4-5 To configure an NTP client on Red Hat
Enterprise Linux systems (p. 4-7).
vi /etc/ntp.conf
3 To add an access policy, type:
restrict NTP_client_IP mask netmask nomodify notrap
where:
NTP_client_IP is the IP address of the configured NTP client including desktop systems.
netmask is the network mask for the configured NTP client.
4 Save and close the file.
5 To start NTPD, type:
service ntpd start
service iptables restart
netstat -tulpn
4.3 Configuring storage
This section describes the procedures to configure storage.
Configuring ZFS pools
Applies to This section is applicable to Solaris systems only.
The following is an example procedure to configure ZFS pools. See the Solaris
documentation for more details.
The use of ZFS for a standalone server is mandatory only in a geographically
redundant system. Otherwise, the use of ZFS is strongly recommended to improve
backup times, but is not required.
Use ZFS for the database and shared directories. You can use ZFS or a local directory
for the software and local data directories.
Note On Solaris systems which have been installed with a ZFS

root filesystem, the 5520 AMS can use the zpool that has been created
for Solaris.
Procedure 4-7 To configure ZFS pools
Perform this procedure on each server. Before you proceed, you need root access to
each server you configure. All data servers in the cluster must have the same amount
of memory. The memory for application servers is not restricted.
Note 1 Use ZFS for the database and shared directories. You can use
ZFS or a local directory for the software and local data directories.
Note 2 If you installed Solaris using ZFS, the 5520 AMS can use the
zpool that has been created for Solaris.
Note 3 The zpool version on the preferred data server and the
non-preferred data server in a cluster setup must be the same.
1 Designate a preferred data server and a non-preferred data server.
2 To create a ZFS pool, login to the server as root and type:
zpool create poolname location
where:
poolname is the name you choose for the pool.
location is the disk ID of the location you have chosen for the ZFS pool. For example, c0t0d0s6.
3 To set an alternate mount point for the ZFS pool, type:
zfs set mountpoint= mount_point poolname
where:
poolname is the name you choose for the pool.
mount_point is the path where you need to mount the zpool.
Warning The mount points of the ZFS file systems in the preferred
data server and the non-preferred data server in a cluster setup must
be the same.
Configuring LVM volumes
Applies to This section is applicable to Red Hat Enterprise Linux

systems only.
The following is an example procedure to configure LVM volumes. For more details
on configuring LVM volumes, see the 5520 AMS Server Configuration Technical
Guidelines.
Pre-requisites:
Use a standalone server.
Use logical volumes for the database directories.
Ensure to have the same or more free Physical Extents (PE) than the database
volume in the volume group. For information on configuring LVM volumes, see
the 5520 AMS Server Configuration Technical Guidelines document.
Figure 4-1 Volume setup on Red Hat Enterprise Linux systems (p. 4-10) shows
the volume setup on Red Hat Enterprise Linux systems.
Figure 4-1 Volume setup on Red Hat Enterprise Linux systems
Bootdisk Bootdisk 5520 AMS disk

vgroot vgroot vgams
/ / /
Swap volume Swap volume Database volume
Database volume Shared volume
Free physical extents* Free physical extents*
Single Volume Setup Multiple Volume Setup
* Free physical extents Database volume
Note 1 It is recommended to have a specific logical volume group

for the 5520 AMS.
Note 2 The 5520 AMS database storage must be configured in a
dedicated logical volume. No other data must be present in this
volume. Do not allocate all diskspace of the volume group containing
the logical volume for the database.
In order to create database snapshots reliably, AMS must be able to
create a temporary logical volume which can grow to the same size as
the database volume. The amount of unallocated space (free PE)
within the volume group must be equal to or bigger than the size of
the database volume.
Procedure 4-8 To configure LVM volumes
Note Perform this procedure on simplex servers, data servers, and

combination of application and data servers.
Before you proceed, you need root access to each server you configure. All the data
servers in the cluster must have the same amount of memory size. The memory size for
application servers is not restricted.
1 To create a volume group, login to the server as root and type:
vgcreate vgname /dev/location
where:
vgname is the name you choose for the volume group.
location is the disk ID of the location you have chosen for the volume group. For example,
c0t0d0s6.
2 To create a logical volume login to the server as root and type:
lvcreate -L size -n lvname vgname
where:
lvname is the name of the logical volume.
size is the size of the volume.
3 Add the logical volume to the /etc/fstab file to get properly mounted:
/dev/mapper/vgname-lvname mount_point ext4 defaults 0 0
where:
lvname is the name of the logical volume.
mount_point is the path to mount the logical volume.
Warning The mount points of the database file systems in the

preferred data server and the non-preferred data server in a cluster
setup must be the same.
4.4 User and group IDs
The 5520 AMS installation creates default users with the following default user and
group identifiers:
amssys: 553000
amsftp: 553001
amssftp: 553002
If any of these identifiers is already in use, define the NA_UID and NA_GID
environment variables to over-ride the default. The value of the NA_UID and
NA_GID variables will become the user and group identifiers for the amssys user.
For example, if you enter the following commands:
export NA_UID=553010
export NA_GID=553010
The user and group identifiers will be as follows:

amssys: 553010
amsftp: 553011
amssftp: 553012
Note 1 All the servers in the cluster must have the same group
identifier.
Note 2 In a geographically redundant configuration, the active and
standby sites must have the same group identifier.
4.5 Configuring locale settings
You must configure the locale settings of the standalone server in a simplex setup or
each designated 5520 AMS application and data server in the cluster, before
installing the 5520 AMS application.
Procedure 4-9 To configure the locale settings

1 Login to the server as root.
2 To modify the default locale settings, you need to modify the configuration file to
include the following settings:
CMASK=022
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1
LANG=C
Note 1 On Solaris systems, modify /etc/default/init.
Note 2 On RHEL systems, modify /etc/sysconfig/i18n.
3 Save the modified file.
4 Restart the server to confirm the modifications.
5 Downloading software for the
5520 AMS and 5529 Enhanced
Applications
5.1 Downloading software for the 5520 AMS and 5529 Enhanced
Applications 5-2
5.2 Extracting the downloaded installation files 5-3
5 Downloading software for the 5520 AMS and 5529 Enhanced Applications
5.1 Downloading software for the 5520 AMS and 5529

Enhanced Applications
The electronic delivery site provides access to product software packages. To obtain
access to the service, contact your Alcatel-Lucent representative.
Use Procedure 5-1 To download software (p. 5-2) to download software for the
5520 AMS and 5529 Enhanced Applications.
Procedure 5-1 To download software

1 Go to http://www.alcatel-lucent.com/myaccess, and click Sign In/Register.
2 Log in to the Alcatel-Lucent Customer and Business Partner Portals with the user
name and password for your OLCS account.
Result: A customized Customer Center page opens.
3 Choose the product name from the Technical Content for drop-down menu.
4 Click Downloads: Electronic Delivery.
Result: The Electronic Delivery page opens. This page lists a series of drop-down
menus that you must use to navigate through the hierarchy of software items.
5 Choose a software item from the drop-down menu.
Result: The page refreshes and displays a drop-down menu that contains entries
for additional software items associated with the selected item. Depending on the
product, you may need to repeat this step multiple times. Each time you choose
a software item from a drop-down menu, the page may refresh and display an
additional drop-down menu.
6 Click Next.
Result: A software download page opens. This page contains installation

instructions and notes, a table with detailed information about your software
download (file name, size, and hash values), and two download options.
Record the MD5 hash value that is provided prior to downloading the software. You
require this information when you perform Procedure 5-2 To verify the MD5 hash
value (p. 5-3).
Example: MD5:99fcf60b878f1a97d45b003e3ed5e37c.
7 Choose one of the following software download options:
Enter a Download Directory and choose a Log Detail Level (the options are Low,
Medium, High), then click Download to start the file transfer.
Click Download Plus to start the file transfer with the GetPlus(R) download
agent, and follow the instructions on the screen.
Note The Download Plus option may not be available on the
software download page. The system prompts you to install a browser
plug-in to activate this download option, and provides you with
installation instructions. Some browser versions do not support the
Download Plus plug-in.
Procedure 5-2 To verify the MD5 hash value
Before you proceed, you must record the MD5 hash value of the software before it is
downloaded. See Procedure 5-1 To download software (p. 5-2) for more information.
1 Log in as amssys to the server where you downloaded the software.
2 To display the MD5 hash value for the downloaded software, type:
digest -a md5 software_filename
where:
software_filename is the directory path to the software and the software filename.
Example: digest a md5 /MyDownloads/ams-9.4.00.0-108719-solaris-sparc.tar
Result: The system responds with the MD5 hash value for the software file. For
example, 99fcf60b878f1a97d45b003e3ed5e37c.
3 Verify that the MD5 hash value of the software before it was downloaded (as
recorded from the electronic delivery site) matches the hash value that is
generated by the digest utility.
If the hash values do not match, contact Alcatel-Lucent Technical Support.
5.2 Extracting the downloaded installation files
Use Procedure 5-3 To extract the downloaded installation file to a new directory (p.
5-4) to create a directory for the downloaded installation files, extract the files to that
directory, and make the installation files executable.
Procedure 5-3 To extract the downloaded installation file to a new

directory
Caution 1 The names of directories that will store 5520 AMS data
cannot include spaces.
Caution 2 The installation .tar file must be extracted on the

5520 AMS server, and not on a PC.
1 To create a directory, type:
cd /var/tmp
mkdir extract_dir
where extract_dir is the name you assign to the directory.
2 To change to the new directory, type:
cd extract_dir
3 To move the installation file to the new directory, type:
mv location/installation_filename.tar .
where:
location is the path to the directory where you saved the software file.
installation_filename is the installation filename, and will be in the format
ams-release-operating_system-architecture
where:
release is the release of the 5520 AMS software. An example is ams-9.4.00-999000.
operating_system is solaris for the Solaris operating system, and redhat for the Red Hat Enterprise
Linux operating system.
architecture is sparc or x86 for Solaris, and x86_64 for Red Hat Enterprise Linux.
4 To extract the installation file to the directory, type:
tar xvf installation_filename.tar
5 To go to the sw directory, type:
cd sw
6 To make the installation file executable, type:
chmod 755 installation_filename.bin
6 Installing the 5520 AMS solution
components
6.1 Installing the 5520 AMS solution overview 6-2
6.2 Pre-requisite tasks 6-2
6.3 Installing the 5520 AMS solution 6-4
6.4 Saving the configuration settings for installation of a 5520 AMS

server 6-21
6.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced Applications

and plug-ins, and patches and emergency fixes 6-23
6.6 Verifying the installed software components on the 5520 AMS

server 6-38
6.7 Changing passwords for default users 6-39
6.1 Installing the 5520 AMS solution overview
The 5520 AMS solution comprises the 5520 AMS core software, 5520 AMS NE
plug-ins, 5529 Enhanced Applications and plug-ins, and patches and emergency
fixes.
Use one of the following installation and activation methods:
Install and activate all 5520 AMS solution components:
Without the configuration file (recommended).
In this recommended method, all 5520 AMS solution components are installed and
activated using a single command.
With a configuration file.
In this method, the configuration settings for installation are saved in a configuration
file prior to the installation. This configuration file is used to retrieve the user inputs
while installing and activating all 5520 AMS solution components in a
non-interactive mode.
For information on saving the configuration settings for installation, see Section 6.4
Saving the configuration settings for installation of a 5520 AMS server (p. 6-21).
Install and activate only the 5520 AMS core software (excluding the other
5520 AMS solution components). Install and activate the other 5520 AMS
solution components separately.
Depending on the type of installation, perform the Procedure 6-1 To install and
activate the 5520 AMS solution (p. 6-4) to install and activate 5520 AMS solution
components in a simplex or cluster setup.
6.2 Pre-requisite tasks
Before installing each 5520 AMS solution component, ensure to perform the
pre-requisite tasks mentioned in Table 6-1 Pre-requisite tasks for installing the
5520 AMS (p. 6-2).
Table 6-1 Pre-requisite tasks for installing the 5520 AMS
Pre-requisite task See
Obtain the 5520 AMS license key from Alcatel-Lucent. For information on license keys, see
the 5520 AMS Administrator Guide.
To obtain a license key, contact
your Alcatel-Lucent account
representative.
Prepare the server that will host the 5520 AMS and install the For system requirements and
operating system. recommended settings, see the
5520 AMS Solution Planning Guide.
On the Red Hat Enterprise Linux server, zip be installed for -

successful installation.
On Red Hat Enterprise Linux systems, the 5520 AMS database -

storage must be configured in a dedicated logical volume. No
other data must be present in the volume.
On Red Hat Enterprise Linux systems, the following For information on configuring LVM
pre-requisites on volumes are applicable to simplex servers, volumes on an already created
data servers, and combination of application and data volume setup for installing the
servers: 5520 AMS, see the 5520 AMS Server
Database volume: A separate logical volume in which to Configuration Technical
install the 5520 AMS database. Guidelines.
Free Physical Extents (PE): Do not allocate all diskspace
of the volume group containing the logical volume for
the database. In order to create reliable database
snapshots, AMS must be able to create a temporary
logical volume which can grow to the same size as the
database volume. The amount of unallocated free PE
(unallocated space) within the volume group must be
equal to or bigger than the size of the database volume.
If the installer displays error messages due to insufficient
unallocated disk space, resize the volume group to
ensure that there are sufficient unallocated PEs to
create the volume with free disk space.
volume: Alcatel-Lucent recommends a separate logical
volume in which to store the shared data.
On a server running the Red Hat Enterprise Linux operating -

system, do not choose to back up the database to the /tmp
directory, the shared data directory or the LVM volume of
the database storage directory.
On Red Hat Enterprise Linux systems, for using the ODMT and For information about the 32-bit
PBMT tools you must install the 32-bit compatibility compatibility packages, see the
packages glibc.i686 and libstdc++.i686. These packages 5520 AMS Server Configuration
are required on Simplex and Application servers only. Technical Guidelines
Ensure that the system locale is set to English or an Section 4.5 Configuring locale
ISO8859-1 based language. settings (p. 4-12)
Ensure that the SSH service is running on the server. 5520 AMS Server Configuration
Technical Guidelines
If the default user and group identifiers are in use, over-ride Section 4.4 User and group IDs (p.
them. 4-11)
Ensure that the root home directory ~ and your ~/.ssh -

directory on the server must be writable by root only.
When installing the 5520 AMS release:
Obtain the software file and make it executable. Chapter 5 Downloading software for
the 5520 AMS and 5529 Enhanced
Obtain root access to the server on which you are Applications (p. 5-1)
installing the 5520 AMS.
When installing and activating the 5520 AMS NE plug-ins, -

5529 Enhanced Applications and plug-ins, patches, and
emergency fixes together or separately:
Obtain the software files and make them executable. Chapter 5 Downloading software for
the 5520 AMS and 5529 Enhanced
Ensure that the 5520 AMS release is installed and Applications (p. 5-1)
activated.
Sections 6.3 Installing the 5520 AMS
It will be easier if the .bin files of the software plug-ins, solution (p. 6-4)
patches, and emergency fixes that you want to install
and activate are stored in a single directory.
Ensure that you are able to log in to the -

5520 AMS servers as amssys.
When installing and activating the 5520 AMS NE plug-ins,

5529 Enhanced Applications and plug-ins, and patches, and
emergency fixes together or separately, if the 5520 AMS is
started, stop the 5520 AMS.
When deactivating or uninstalling the 5520 AMS NE plug-ins,
5529 Enhanced Applications and plug-ins, and patches, and
emergency fixes together or separately, stop the 5520 AMS.
To stop the server in a simplex setup, use the Procedure 7-4 To stop a server (p.
ams_server stop command. 7-4)
To stop all servers in a cluster setup, use the Procedure 7-5 To stop a cluster (p.
ams_cluster stop command. 7-4)
If you are installing the 5520 AMS using a configuration file, Procedure 6-3 To save the
ensure that the configuration file is generated. configuration settings for the
installation of a 5520 AMS server (p.
6-22)
If you are installing a VMware setup, ensure that the 5520 AMS Server Configuration
configuration is correct. Technical Guidelines
6.3 Installing the 5520 AMS solution
Use Procedure 6-1 To install and activate the 5520 AMS solution (p. 6-4) to install
and activate the 5520 AMS solution in a simplex setup.
Before you proceed, ensure to perform the pre-requisite tasks. See Section 6.2
Pre-requisite tasks (p. 6-2).
Note For samples of simplex server, NE plug-in, and VAP

installations, see Appendix A Examples of the installation and
activation of the 5520 AMS solution (p. A-1)
Procedure 6-1 To install and activate the 5520 AMS solution
Caution The server can be installed and activated at the same time
only when no other 5520 AMS installation is running on the server.
Note Complete this procedure to install the 5520 AMS for the first
time. If you have an earlier version of the 5520 AMS that is already
installed and you want to upgrade it to new version, see Chapter 15
Pre-migration tasks (p. 15-1) for automated in-place migration and
out-of-place migration. For manual in-place migration tasks, see
Appendix B.2 Manual in-place migration associated task list (p. B-2).
1 Log in to the server as root or amssys.
2 To go to the directory containing the executable installation file, type:
cd /var/tmp/extract_dir/sw
where extract_dir is the directory where you extracted the installation files in Procedure 5-3 To
extract the downloaded installation file to a new directory (p. 5-4).
3 Execute one of the following commands depending on the installation scenario:
Scenario Execute the following command: Result
Install and activate all ./installation_filename.bin --activate-force The installation software displays the
5520 AMS solution --includevapsplugs directory_path following confirmation:
components without a
configuration file where: Checking OS and version ...
(recommended)
installation_filename.bin is the AMS Core installation filename, and OK.
will be in the format ams-release-operating_system-architecture
where: Checking hostname ... OK
release is the release of the 5520 AMS software. An example is
ams-9.4.00-216228-redhat-x86_64.bin Checking SSH (ssh,
operating_system is solaris for the Solaris operating system, and ssh-keygen, ssh-keyscan, scp,
redhat for the Red Hat Enterprise Linux operating system. sftp) ...
architecture is sparc or x86 for Solaris, and x86_64 for Red Hat
Enterprise Linux.
The installer prompts you for the location of
directory_path is the path to the directory containing the VAPs and/or the SSH library:
NE Plugs .bin files. If only a subset of files in a directory needs to be
installed or if the .bin files are stored in different directories, specify Enter the path to the SSH
the absolute path and filename of each .bin file.
tools [ /usr/bin (default) ]:
Install and activate ./installation_filename.bin --activate-force
only the 5520 AMS core Proceed to step 4 (p. 6-6).
software (excluding
other solution
components)
Install and activate all ./installation_filename.bin -c The installation proceeds based on the
5520 AMS solution [path_and_filename --activate-force] settings saved in the configuration file. The
components using a --includevapsplugs directory_path choices saved in the configuration file are
configuration file displayed. See Table 6-2 Installation result
where: (p. 6-19) for the installation result.
path_and_filename is the location and name of the configuration file
in the server. For example, /tmp/simplex. By default,
path_and_filename is /tmp/install-env.
./installation_filename.bin -c
path_and_filename --includevapsplugs
directory_path
where:
in the server. For example, /tmp/simplex.
directory_path is the path to the directory containing the .bin files. If
only a subset of files in a directory need to be installed, or if the .bin
files are stored in different directories, the absolute path and
filename of each .bin file needs to be specified.
4 The installer prompts you for the location of the SSH configuration file.
To use the default SSH implementation path, press .

To use SSH implementation other than default version or to move the SSH tools
to another location, enter new path and press .
Enter the path to the 'sshd_config' file [ /etc/ssh (default) ]:
5 The installer prompts you for the shell to be used by the amssys and amsftp users.
To assign the default shell, press .

To assign a shell other than the default value, enter the path and shell. For
example, on Solaris systems: usr/bin/bash.
Enter the full path and executable file name of the default shell
used by the amssys and amsftp users [/bin/sh (default)]:
6 The installer prompts you for the name of the installation site.
Enter the site name that uniquely identifies the cluster (only
alphanumeric, -, _ allowed):
7 Type a name for the site and press .
Note 1 The site name can include only alphabets, digits, _ and -. No
special characters are allowed.
Note 2 Ensure that the site name that you provide is the same across
the preferred, non-preferred, application, combination of application
and data, and arbiter servers in a cluster setup.
Result: The installer prompts you to confirm the site name.
Is this correct [ no (default) | yes ]?
8 Type y and press to accept the site name or else press for a prompt to enter
a new site name.
Result: The installer prompts you for the installation type:
Is this a simplex (i.e. standalone) system? [ yes (default) | no

]?:
9 Perform one of the following:
If then Result
the system is a simplex press . Depending on whether your server has one or multiple subnet addresses, the
server following prompts are displayed:
If the server on which you are installing has a single NIC, the installer
displays the following prompt:
Enter the subnets on which the GUI clients are

allowed to connect [subnet address (default)]:
Note: Use CIDR format (e.g. 10.1.2.0/24). Multiple

subnets can be entered using a comma separated list
where:
Subnet address is the default subnet addresses of the NIC detected by the
5520 AMS installer.
Go to step 15 (p. 6-12)
If the server on which you are installing has multiple NICs or virtual subnet
addresses, the installer displays the following prompt:

allowed to connect:

Go to step 15 (p. 6-12).
the system is member of type n and The installer prompts you for the server role:
a cluster press .
Enter the role of this server (default role is application
server):
[1] Application server
[2] Data server
[3] Application + Data server
[4] Arbiter
Go to step 10 (p. 6-9).
If you need to install then Result
an application server type 1 and The installer prompts you for the cluster subnet address and provides the IP
press . address of each NIC:
a data server type 2 and Enter the subnet (in CIDR format e.g 10.1.2.0/24) to
press . exchange server cluster information:
A combination of type 3 and The cluster subnet is: Subnet addresses
application and data press .
server where:
An arbiter server type 4 and Subnet addresses is the list of subnet addresses for NICs installed on the
press . server.
Is this correct [no (default) | yes]?
11 Type y and press to accept the subnet address or press for a prompt to modify
the subnet address.
If you are installing then
an application server or the installer prompts you for the multicast IP address for application
a combination of information:
application and data
server Enter the multicast IP address to exchange application
information [225.1.2.5 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
Type y and press to accept the IP address or press for a prompt to modify
the IP address.
Result: The installer prompts you for the multicast IP address for server
information:
Enter the multicast IP address to exchange server
where:
Note: Data server IP addresses should be reachable via the

same network interface as the one used to exchange cluster
information
For application server, go to step 12 (p. 6-10)

For combination of application and data server, go to step 13 (p. 6-10)
If you are installing then
a data server the installer prompts you for the multicast IP address for server information:

where:
Note: Data server IP addresses should be reachable

via the same network interface as the one used to
exchange cluster information
Go to step 13 (p. 6-10)
an arbiter server the installer prompts you for the multicast IP address for server information:

where:
Go to step 15 (p. 6-12)
Caution The multicast IP address must be the same for all database
and application server installations.
12 For application server, the installer prompts you to enter the IP address or DNS
name of the server.
Result:
Enter the IP address or DNS name of the preferred data server:
IP address
The data server will be (is) running on IP address
where IP addresses is the list of the IP addresses or the DNS name installed on the
server.
13 The installer prompts you to identify the presence of alternate data server:
Do you want to configure an alternate data server [no (default)

| IP address (or) DNS name?
14 Entering an IP address or DNS name indicates that you are setting up a system with
a redundant data server and causes the installer to collect additional information
about the redundant configuration.
Perform one of the following steps:
To configure an alternate data server to act as a backup, enter its IP address

or DNS name and press .
Result: The installer prompts you to confirm the subnet address or DNS name
of the server.
Confirm the information displayed.
Correct the information as required.
Press , if you do not want to configure an alternate data server.
The following message is displayed:
The data server will be (is) running on IP address.
Is this correct [ no (default) | yes ]? yes
where:
IP address is the IP address you provided.
If you are installing: Result

an application server If the server machine has multiple NICs or virtual subnet addresses, the installer prompts you
for interfaces to which GUI clients can connect:
Enter the subnets on which the GUI clients are allowed to

connect:
Note: Use CIDR format (e.g. 10.1.2.0/24). Multiple subnets can

be entered using a comma separated list
GUI subnet address:

where:
the GUI subnet addresses or address is the subnet address that you provide.
Go to step 15 (p. 6-12).
a data server The installer further checks whether the current server is the preferred data server:
Will the local data server be the preferred one [ no (default)

| yes ]?
To configure the data server as the preferred data server, type y and press .
To configure the data server as a non-preferred data server, type n and press .
Go to step 15 (p. 6-12).
If you are installing: Result
a combination of The installer further checks whether the current server is the preferred data server:
server Will the local data server be the preferred one [ no (default)
| yes ]?
To configure the server as the preferred data server, type y and press .
To configure the server as a non-preferred data server, type n and press .
If the server machine has multiple NICs or virtual Subnet addresses, the installer prompts you
Enter the Subnet address of the NIC on which GUI clients are
allowed to connect:

GUI subnet address:

where:
Go to step 15 (p. 6-12).
15 The installer prompts you for the software installation directory:
In which top directory do you want to install the software [ /opt

(default) ]?
To accept the default /opt directory, press :

To modify the directory, press for a prompt.
Note The location entered here will be used by the installer to

create a subfolder /ams/software and copy the 5520 AMS application to
this subfolder.
If you are installing: then
a simplex server, data the installer prompts you for the local data directory:
server, combination of
application and data In which top directory do you want to store the local data files
server, or application [ /var/opt (default)]
server
Go to step 17 (p. 6-13).
an arbiter server the installer prompts you for the local data directory:
In which top directory do you want to store the local data files
[ /var/opt (default) ]?
If you are installing on Red Hat Enterprise, go to step 19 (p. 6-14) or else go to step 24 (p. 6-16)
To accept the default /var/opt directory, press .

Note The location entered here will be used by the installer and
later by the 5520 AMS application to store the data files that are
separate from the database in the subfolder /ams/local.
a simplex server, data the installer prompts you for the shared data directory:
server, or a
combination of In which top directory do you want to store the shared data
application and data files on the data servers ?
server,
(This location should be same in all the servers in the cluster)
Go to step 18 (p. 6-13).
an application the installer prompts you for the shared data directory:
In which top directory do you want to store the shared data

files on the data servers ?

Note 1 On Solaris systems, type the mount point of the ZFS pool to
choose a ZFS pool you created in the Procedure 4-7 To configure ZFS
pools (p. 4-9).
Note 2 On Red Hat Enterprise Linux systems, to choose an LV, refer

to the Procedure 4-8 To configure LVM volumes (p. 4-11).

install the files designated as shared in an /am/shared subfolder.
Result:
a simplex server, or a the installer prompts you for the database installation directory:
combination of
application and data In which top directory do you want to put the database storage
server, [ /var/opt (default) ]?
a data server the installer prompts you for the database installation directory:
In which top directory do you want to put the database storage

19 On a Red Hat Enterprise Linux system, the installer prompts you to select the
option to install the AMS:
Result:
AMS requires a method to invoke ams_os_service.sh as superuser. Please

select means to do so:
[1] Using ssh keyless authentication (auto configure, default)
[2] Using sudo (auto configure)
[3] Using sudo (manual configured)
Type Result
1 and press . Go to step 21 (p. 6-16)

For data server and arbiter server, go to step
24 (p. 6-16)
2 and press . The 5520 AMS installer adds the amssys to the
sudo configuration and the command
ams_os_service.sh (passwordless) is added.
Go to step 21 (p. 6-16)
24 (p. 6-16)
3 and press . The installer prompts you to create a sudo file

under /etc directory:
Update sudo configuration so

user amssys can invoke "sudo
/var/opt/ams/users/amssys/lib/p
latform/bin/ams_os_service.sh"
Press enter when correctly

configured
Press .
To configure the sudo configuration file, see
Procedure 6-2 To manually configure sudo (p.
6-21).
The installer verifies the functionality of the
sudo configuration file and prompts the next
question. Go to step 21 (p. 6-16)
24 (p. 6-16)
Note If the sudo configuration file is not created, the installer displays the
following message:
Error: Failed to check sudo command

/var/opt/ams/users/amssys/lib/platform/bin/ams/ams_os_service.sh
Update sudo configuration so user amssys can invoke sudo

/var/opt/ams/users/amssys/lib/platform/bin/ams/ams_os_service.sh
Press enter when correctly configured.
Note 1 A periodic check is performed on the ams_os_service_sh to

verify that it is functioning properly. The default value for the timer is
set to 3600 (1 hour). An alarm is raised in the event of the sudo
configuration is not functioning properly. For more information on the
alarms, see 5520 AMS Administrator Guide.
Note 2 The chosen option is stored in the ams.conf parameter

AMS_OS_SERVICE_METHOD as ssh, sudoauto , or sudoman.
Note 3 If AMS_OS_SERVICE_METHOD is set to SSH then

PermitRootLogin parameter must be enabled in the SSH configuration
file: /etc/ssh/sshd_config
21 The installer prompts you to store the local NE software files:
In which top directory do you want to store the local NE software

files [ /ams (default) ]?
22 To accept the default /ams directory, press .
Note 1 On Solaris systems, type the mount point of ZFS pool to

choose a ZFS pool you created in Procedure 4-7 To configure ZFS pools
(p. 4-9).
Note 2 The directory name should not exceed more than 13

characters. The length of the absolute directory name where NE
software and tools are stored depends on NE restrictions.
Note 3 During operation, data required by the NE software migration

tools will be copied to the location you entered here.
For simplex server, go to step 24 (p. 6-16)
For application server or combination of application and data server, go to step

23 (p. 6-16)
23 The installer prompts you to block the client interface during the startup of the
server:
Do you want to block the client interface during the startup of

server [yes | no (default)]?
Perform one of the following:
To block the client interface during server startup, type yes and press .
To allow requests on the client interface during server startup, type no and
press .
Note If you choose yes, IP filtering will be enabled. For information

on the client login behavior when IP filtering is enabled or disabled in
cluster setups, see the 5520 AMS User Guide.
24 The installer prompts you for the MySQL root user password:
Enter the password for MySQL root user ( no space allowed) [ mysql
(default) ]:
To use the default password, press .

To set the MySQL root user password, enter the new password and press .
Result: The installer prompts you to confirm the MySQL root user password:
Confirm the password for MySQL root user:
25 Retype the password and press .
Result: The installer prompts you for the MySQL admin application user password:
Enter the password for MySQL admin application user (no space
allowed) [ mysql (default) ]:

To set the MySQL admin application user password, enter the new password
and press .
Result: The installer prompts you to confirm the MySQL admin application user
password:
Confirm the password for MySQL admin application user:
Result: The installer prompts you for the MySQL replication user password:
Enter the password for MySQL replication user ( no space allowed)

[ mysql (default) ]:

To set the MySQL replication password, enter the new password and press .
Result: The installer prompts you to confirm the MySQL replication user password:
Confirm the password for MySQL replication user:
30 On Red Hat Enterprise Linux systems:
simplex, data server, or the installer displays the following message:

combination of
application and data Checking LVM Database partition...
server
OK
Checking packages....
OK
application server the installer displays the following message:
OK
31 The installer prompts you to confirm the installation:
Are you sure you want to install [ no (default) | yes ]?
Type y and press .
The installer checks available disk space and then proceeds to install the 5520 AMS
application.
Table 6-2 Installation result
Result of installation
Monitor status messages for updates and error messages. When the installation is
complete, the installer displays information reminding you about server configuration,
including:
User home directory
Software directory
Local and shared data directories
Database directory
Do not forget to change the password for user amssys
If the --includevapsplugs option was used to install other solution components along
with the 5520 AMS software, the installer proceeds to install the 5520 AMS plug-ins,
5529 Enhanced Applications and plug-ins, and patches and emergency fix, and displays
the following message:
Installing Patchs/EFs/Apps/Plugs/Vaps...
The installer displays the summary of the software plug-ins, patch and emergency fix
selected for installation. The installer then proceeds to install each software plugin,
patch and emergency fix, and displays the status of each installation:
Installing application <installation .bin file>
Installing application...
Extracting application content.........................done
Installation Complete!
32 The installer prompts you to activate the product.
Do you want to activate this product [yes (default)/no]?
33 Type y and press .
Table 6-3 Activation result
Result of activation
A log file named install.log, which records all messages displayed during the installation, is created in the local data
directory. The installer initiates the activation of the 5520 AMS server, and displays the following message:
Automatic activation enabled
Initializing..
The installer displays a series of status messages, and when the installation is complete, displays the following
message:
Activation finished
If the installation is executed on a Red Hat Enterprise Linux server, then the installer displays the following message
indicating that there are changes required to the firewall configuration:
***Warning***
* There are changes to the firewall rules required for this application to run
correctly.
* Execute /opt/ams/software/<installation_directory>/bin/ams_updatefirewall
script for more details.
* You need to be root to actually apply these changes.
*****************
Activation finished
If the activation is executed in Red Hat Enterprise Linux server using sudo (auto configure) mode, the 5520 AMS
installer creates the -5520ams_sudoers - file in the sudoers.d directory containing the following content:
Defaults:amssys !requiretty
amssys ALL= NOPASSWD:installation_directory/ams_os_service.sh
where: installation_directory is the installation path chosen at the time of the 5520 AMS software installation.
Go to step 34 (p. 6-21)
The installer activates the 5520 AMS NE plug-ins, 5529 Enhanced Applications and plug-ins, and patches and emergency
fixes. The installer displays the summary of the software plug-ins, patch and emergency fix selected for activation.
The installer then proceeds to activate each installed software plugin, patch and emergency fix, and displays the
status of each activation:
Activating application <application name>
Checking AMS setup...
Found home: /var/opt/ams/users/amssys
Found AMS root installation dir: /opt/ams/software/<installation_directory>
Copying files (gui/server/script)...done
Activation Complete!
34 For Red Hat Enterprise Linux systems, update the firewall configuration. For more
information on updating the firewall, see Procedure 11-1 To update firewall rules
(p. 11-2).
Note If the --includevapsplugs option was not used, install the other
5520 AMS solution components separately. See Section 6.5 Installing
5520 AMS NE plug-ins, 5529 Enhanced Applications and plug-ins, and
patches and emergency fixes (p. 6-23).
Procedure 6-2 To manually configure sudo
Applies to This procedure is applicable for Red Hat Enterprise Linux

only.
Perform the following procedure to manually configure sudo:
1 Navigate to etc/sudoers directory.
2 In a Text editor, and enter the following information and save as

5520ams_sudoers:
Defaults:amssys !requiretty
amssys ALL= NOPASSWD: installation_directory/ams_os_service.sh
where: installation_directory is the path chosen at time of the 5520 AMS core software
installation.
Result: The 5520ams_sudoers file is created.
6.4 Saving the configuration settings for installation of a

5520 AMS server
Use Procedure 6-3 To save the configuration settings for the installation of a
5520 AMS server (p. 6-22) to save the configuration settings for the installation of a
5520 AMS server type, in preparation for installing the 5520 AMS solution using the
configuration file that contains the installation settings. When the installation .bin
file is executed with the --noinstall command option, the user is prompted with the
questions asked during a normal installation, and the user responses are saved by
default to /tmp/install-env, or to a user-defined file.
The saved configuration file is used to retrieve the user inputs while installing and
activating the 5520 AMS solution in a non-interactive mode.
Note Prior to installing and activating the 5520 AMS solution

using the saved configuration file, you must save the configuration
settings for the type of server installation on the server. In the case of
a cluster with multiples servers of the same type (for example,
multiple application servers), you must save the configuration
settings separately on each server.
Before you proceed, ensure to perform the relevant pre-requisite tasks. See Section
6.2 Pre-requisite tasks (p. 6-2).
Procedure 6-3 To save the configuration settings for the installation

of a 5520 AMS server
3 To save the configuration settings for the installation to a file, type the following
command:
./installation_filename.bin --noinstall -c path_and_filename
where:
where:
release is the release of the 5520 AMS software. An example is ams-9.4-999000.
operating_system is solaris for the Solaris operating system, and redhat for the Red Hat Enterprise
Linux operating system.
path_and_filename is the location and name of the configuration file in the server. For example,
/tmp/simplex.
Note 1 Use the --noinstall option for installation of the 5520 AMS
core only.
Note 2 If the installation .bin file is executed with the --noinstall

option only, without specifying the -c path_and_filename option to save
the configuration settings to a user-defined file, the configuration
settings will be saved by default to /tmp/install-env.
Note 3 If a copy of the same version of the 5520 AMS is already

installed on the server, the installer exits and displays the message
"ERROR: This AMS version is already installed. Uninstall it first."
Result: The installer displays the installation prompts and saves the user
responses to the specified configuration file. For more information on the
appropriate responses for each type of server installation, refer to the relevant
installation procedure of the type of 5520 AMS server.
Finally, you are prompted to confirm the generation of a configuration file:
Are you sure you want to generate a configuration file [ no

(default) | yes ]?
Result: The installer displays the following message:
The 'noinstall' option is specified so not performing actual

installation.
The settings are stored in file path_and_filename. To use it

execute installation_filename.bin -c path_and_filename
where installation_filename is the installation filename used in Step 3 To save the configuration
settings for the installation to a file, type the following command: (p. 6-22).
Proceed to install the type of server for which the configuration file was created, using
the configuration file. For information on installation of the different types of server,
see Procedure 6-1 To install and activate the 5520 AMS solution (p. 6-4).
6.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced

Perform the procedures in this section to install, activate or deactivate the 5520 AMS
solution components comprising 5520 AMS NE plug-ins, 5529 Enhanced
Applications and plug-ins, and patches and emergency fixes together, or
individually.
When you install the 5520 AMS client, download corresponding plug-in updates to
the client application.
5520 AMS NE plug-in software file

The 5520 AMS provides software plug-ins to support specific NEs and to add
expanded capabilities. Install and activate these plug-ins on the 5520 AMS server.
When you install the 5520 AMS client, download corresponding plug-in-driven
updates to the client application.
The 5520 AMS NE plug-in software file will be in the format:
plugin-combo-ne-release_x.x_9.4-nnnnnn.bin
where:
ne is the NE type.
release is the NE release number.
x.x is the plug-in version number, for example, 1.0.
nnnnnn is the build number.
An example of a plug-in file is plugin-combo-isam-4.5-1.0_9.4-999324.bin, which
is used to manage the 7302 ISAM/7330 ISAM FTTN, Release 4.5.
Note 1 If you use SIP with the NE, install both the SIP application
plug-in and the SIP plug-in for your release of the NE.
Note 2 Other NE plug-ins may also have dependencies. For more
information about dependencies for the NE plug-in you install, see the
Release Notice for the NE.
Patch software file

The patch software file will be in the format:
installation_filename.bin
where:
where:
release is the release of the 5520 AMS software. An example is ams-9.4.x-999000,
where x indicates the patch release number.
operating_system is solaris for the Solaris operating system, and redhat for the Red
Hat Enterprise Linux operating system.
Emergency fix software file

The emergency fix software file will be in the format:
ams-releaseEFx.bin
where:
release is the release of the 5520 AMS software. An example is 9.4.00-999000.
x is the emergency fix version.
5529 Enhanced Applications and plug-ins software file

Application and NE support plug-ins for 5529 Enhanced Applications are installed
and activated using the same scripts as plug-ins for the 5520 AMS.
The 5529 Enhanced Applications software file will be in the format:
app-vap-release-nnnnn-operating_system-architecture.bin
where:
vap is the 5529 Enhanced Application. An example is apc or idm.
release is the release of the 5520 AMS software. An example is 9.4.00_9.4.
nnnnn is the build number.
operating_system is solaris for the Solaris operating system, and redhat for the Red
Hat Enterprise Linux operating system.
For example, app-apc-9.4.3_9.3.0-199878-solaris-x86.bin.
Note If the app-apc is activated during the combo plug installation,

then the plugin-apc is automatically activated.
The 5529 Enhanced Applications NE plug-in software file will be in the format:
plugin-vap-ne-release_x.x_9.4.y_9.4-nnnnnn.bin
where:
ne is the NE type.
release is the NE release number.
x.x is the plug-in version number, for example, 1.0.
y is the major or patch release number of the 5520 AMS release. For a major release,
y is 0. For a patch release, y is 1, 2 ... n.
nnnnnn is the build number.
For example, plugin-apc-gpon-4.6-1.3_9.4.3_9.4-199878.bin
For information about 5529 Enhanced Applications, see the documentation for the
application.
Installing and activating the 5520 AMS solution components

Table 6-4 Install and activate the 5520 AMS solution components (p. 6-25) lists the
tasks to install and activate the 5520 AMS solution components together or
individually.
Before you proceed, ensure to install and activate the 5520 AMS, using Section 6.3
Installing the 5520 AMS solution (p. 6-4).
Table 6-4 Install and activate the 5520 AMS solution components
Task # Task See

1 If the 5520 AMS is started, stop the 5520 AMS.
To stop the server in a simplex setup, use the ams_server stop command. Procedure 7-4 To stop a server (p.
7-4)
(p. 7-4)
(1 of 2)
Task # Task See
2 Install and activate the 5520 AMS solution components together or Procedure 6-4 To install the
individually. 5520 AMS NE plug-ins, 5529
individually (p. 6-27) or
Procedure 6-7 To install,
activate, install and activate, or
deactivate the 5520 AMS solution
components (p. 6-35)
(p. 7-2)
(p. 7-3)
(2 of 2)
If you are installing and activating the 5520 AMS NE plug-ins, or 5529 Enhanced
Applications and plug-ins individually, see the installation and activation tasks in
Section 3.4 Software plug-in installation overview (p. 3-12).
If you are installing and activating a patch individually, see the installation and
activation tasks in Section 3.5 Patch installation overview (p. 3-14).
If you are installing and activating an emergency fix individually, see the installation
and activation tasks in Section 3.6 Emergency fix installation overview (p. 3-18).
Note Ensure to install and activate the 5520 AMS NE plug-ins
before installing the 5529 Enhanced Applications plug-ins, when
installing them together or individually.
In a cluster installation, the procedures must be performed on each server in the

cluster.
Caution The cluster must not have two servers running with
different plug-ins or patches or emergency fixes installed. After you
install plug-ins, patches, and emergency fixes on one server, stop the
other server before starting the updated server.
To perform the procedures in this section, you must be able to log in to the
5520 AMS servers as amssys.
Procedure 6-4 To install the 5520 AMS NE plug-ins, 5529 Enhanced

Applications and plug-ins, and patches and emergency fixes together
or individually
Before you proceed, ensure that the relevant pre-requisite tasks are performed. See
Section 6.2 Pre-requisite tasks (p. 6-2).
Note When installing and activating a patch, open a new terminal to

perform the installation and activation of the patch. A terminal used to
deactivate the earlier patch must not be used to install and activate a
new patch.
1 Log in to the 5520 AMS server as amssys.
2 To run the installer script, type:
ams_install.sh
Result: The script presents the main menu:
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
h) Help
q) Quit
Choice:
3 Type i and press .
Result: The script prompts you for the location of the installation files:
Enter the full path to the directory containing the software to

be installed:
4 Type the path to the directory and press .
Result: The script displays the following message:
Do you want to activate the software once it is installed [y|n

(default)] ?
To activate the 5520 AMS solution components immediately after installation,

type y and press .
To install the 5520 AMS solution components without activating them, press .
Result: The script prompts you for the text to filter the 5520 AMS solution
components:
Display only the items containing the following text [all items
(default)] :
To display only the 5520 AMS solution components in the directory based on a
filter, type the filter text and press . For example, if you type 9.4 and press
, only the 5520 AMS solution components containing 9.4 in the filename will
be displayed.
To display all 5520 AMS solution components in the directory, press .
Result: The script presents the installation menu. The menu includes a numbered
list of uninstalled 5520 AMS solution components in the directory based on the
filter, for example:
"Main > Install" menu:
0 -Select-All-
1 5520 AMS solution component filename
x) Execute
q) Quit
Choice:
7 Perform the following steps:
i Type the number corresponding to a 5520 AMS solution component you need
to install and press .
To choose all items, type 0 .
To choose multiple items, type several numbers separated by spaces or

commas. For example, 1,2,3 or 1 2 3 .
Result: The menu is presented again, with the numbers for the 5520 AMS
solution components you chose in square brackets ([ ]).
ii To deselect an item, type the number again and press .
iii When you have chosen all the 5520 AMS solution components you need to
install, type x and press .
Result: The script displays a summary of your choices and prompts you to confirm:
Summary:
- Selection:
list of the 5520 AMS solution components you chose
- Options:

be installed: directory

(default)]? y or n
Are you sure you want to Install [y|n (default)] ?
where:
directory is the directory you entered in step 4 (p. 6-27).
y or n is the choice you entered in step 5 (p. 6-27).
Result: The installation proceeds, displaying success messages for the installation
of each 5520 AMS solution component. If you opted to activate the solution
components, the installer then proceeds to display success messages for the
activation of each solution component.
The script presents the main menu.
9 To quit, type q and press .
Note If alarm rules are defined, execute the Check All Rules
command in the Alarm Rules view in the 5520 AMS GUI after installing
or updating NE plug-ins to check the consistency of the defined alarm
rules.

Applications and plug-ins, and patches and emergency fixes together
or individually
Use this procedure to activate the 5520 AMS solution components if you did not activate
them when you performed the installation. Installing the 5520 AMS solution
components puts the software files in the correct location ready for use. However, until
you activate the 5520 AMS solution components, the software is in a passive mode.
Note 1 If you try to activate an emergency fix when a newer version

of the emergency fix is active, the following error message is displayed:
ERROR: Cannot activate EF because a more recent EF is

active. Deactivate that one first.
Note 2 When activating an emergency fix, if the 5520 AMS, 5520 AMS
patch, software plug-ins, or the existing version of the emergency fix is
not compatible with the version of the emergency fix you are
activating, the following error message is displayed:
ERROR: Valid version for EF is not installed.
Before you proceed, ensure that:
The 5520 AMS solution components you are activating are installed. See
Procedure 6-4 To install the 5520 AMS NE plug-ins, 5529 Enhanced Applications
and plug-ins, and patches and emergency fixes together or individually (p.
6-27).
You are able to log in to the 5520 AMS server as amssys.
ams_install.sh
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
q) Quit
h) Help
Choice:
3 Type a and press .
components:
(default)] :
be displayed.
Result: The script presents the activation menu. The menu includes a numbered
list of installed 5520 AMS solution components in the directory based on the filter,
for example:
"Main > Activate" menu:
0 -Select-All-
x) Execute
q) Quit
Choice:
to activate and press .

activate, type x and press .
Summary:
- Selection:
Are you sure you want to Activate [y|n (default)] ?
Result: The activation proceeds, displaying success messages for each 5520 AMS
solution component.
Deactivating the 5520 AMS solution components

Table 6-5 Deactivate the 5520 AMS solution components (p. 6-32) lists the tasks to
deactivate the 5520 AMS solution components together or individually.
Table 6-5 Deactivate the 5520 AMS solution components
Task # Task See
command.
command.
3 Deactivate the 5520 AMS solution components together or Procedure 6-4 To install the 5520 AMS NE
individually. plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency
fixes together or individually (p. 6-27) for
deactivating the 5520 AMS solution
components together or individually.
deactivating the 5520 AMS solution
components together.
command.
command.
If you are deactivating the 5520 AMS NE plug-ins, or 5529 Enhanced

Applications and plug-ins individually, see the deactivation tasks in Deactivating
software plug-ins (p. 3-13).
If you are deactivating a patch individually, see the deactivation tasks in
Deactivating patches (p. 3-16).
If you are deactivating an emergency fix individually, see the deactivation tasks in
Deactivating emergency fixes (p. 3-19).
Procedure 6-6 To deactivate the 5520 AMS NE plug-ins, 5529

Enhanced Applications and plug-ins, and patches and emergency
fixes together or individually
Note If you try to deactivate an emergency fix before deactivating

the newer version of the emergency fix, the following error message is
displayed:
ERROR: Cannot deactivate EF because a more recent EF is

The 5520 AMS solution components you are deactivating are activated. See
Applications and plug-ins, and patches and emergency fixes together or
individually (p. 6-29).
ams_install.sh
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
h) Help
q) Quit
Choice:
3 Type d and press .
components:
(default)] :
be displayed.
Result: The script presents the deactivation menu. The menu includes a
numbered list of installed 5520 AMS solution components based on the filter, for
example:
"Main > Deactivate" menu:
0 -Select-All-
x) Execute
q) Quit
Choice:
to deactivate and press .

deactivate, type x and press .
Result: The script displays a summary of your choice and prompts you to confirm:
Summary:
- Selection:
- Options:
Are you sure you want to Deactivate [y|n (default)] ?
Result: The deactivation proceeds, displaying the success message.
Installing, activating or deactivating the 5520 AMS solution

components
Use Procedure 6-7 To install, activate, install and activate, or deactivate the 5520
AMS solution components (p. 6-35) to perform one of the following tasks:
Install, activate, or install and activate the 5520 AMS solution components
comprising the 5520 AMS NE plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes together or separately.
Deactivate the 5520 AMS solution components comprising the 5520 AMS NE
fixes together.
For the complete list of tasks to install and activate the 5520 AMS solution
components, see Table 6-4 Install and activate the 5520 AMS solution components
(p. 6-25).
For the complete list of tasks to deactivate the solution components, see Table 6-5
Deactivate the 5520 AMS solution components (p. 6-32).
Procedure 6-7 To install, activate, install and activate, or deactivate

the 5520 AMS solution components
Caution Using this procedure to deactivate the 5520 AMS solution

components together deactivates all the active software plug-ins,
patches, and emergency fixes installed on the server. Only the
5520 AMS software remains active.
Before you proceed, ensure that the relevant pre-requisite tasks are performed. See
Section 6.2 Pre-requisite tasks (p. 6-2).
2 Execute one of the following commands:
Install and activate ams_install.sh --installActivate The installer displays the summary of the selected
5520 AMS NE plug-ins, directory_path 5520 AMS solution components.
5529 Enhanced If you used the --installActivate option or the --install
Applications and where directory_path is the path to the option, the installer then proceeds to install each
plug-ins, and patches directory containing the .bin files. If only a 5520 AMS solution component, and displays the status
and emergency fixes subset of files in a directory needs to be of each installation:
together or as installed, or if the .bin files are stored in
individual components different directories, specify the absolute path Installing application <installation
and filename of each .bin file.
.bin file>
Install 5520 AMS NE ams_install.sh --install Installing application...

plug-ins, 5529 directory_path
Enhanced Applications Extracting application
and plug-ins, and content.........................done
patches and
emergency fixes
together or as Installation Complete!
individual components
If you used the --installActivate option, or the
Activate 5520 AMS NE ams_install.sh --activate --activate option, the installer then proceeds to
plug-ins, 5529 directory_path activate each each 5520 AMS solution component, and
Enhanced Applications displays the status of each activation:
and plug-ins, and
patches and Activating application <application
emergency fixes
together or as name>
individual components
Found home:
/var/opt/ams/users/amssys
Found AMS root installation dir:

/opt/ams/software/<installation_dire
ctory>
Copying files
(gui/server/script)...done
Deactivate 5520 AMS ams_install.sh --deactivate The installer displays the summary of the active
NE plug-ins, 5529 5520 AMS solution components that will be
Enhanced Applications deactivated. The installer then proceeds to deactivate
and plug-ins, and each 5520 AMS solution component, and displays the
patches and status of each deactivation:
emergency fixes
together Deactive application
<application_name>
<application_name> has been

successfully deactivated!
done
6.6 Verifying the installed software components on the 5520

AMS server
Use this procedure to compare the system configuration with the

GoldenEMSSwConfig file.
Procedure 6-8 To verify the installed software components

1 Login to the server as amssys.
2 To view the version details of the installed software components, type:
ams_server version
Result: The command displays all the installed components with the version
details.
3 You can edit a GoldenEMSSwConfig file or generate the config file on a reference
system using 'ams_server version save' command.
To create a GoldenEMSSwConfig file using the save option, type:
ams_server version save
Result: The command generates the GoldenEMSSwConfig file with details of the
installed server components.
Note If you do not enter a file name, output is displayed on the

console. However, if you provide a file name, the output is saved in the
file you have created.
For more information about the GoldenEMSSwConfig file , see the 5520 AMS
Administrator Guide.
4 To verify and compare the installed software components with the system
configuration, type:
ams_server version verify <filename>
Where <filename> is the name of the GoldenEMSSwConfig file.
Result: The GoldenEMSSwConfig file is updated with software component details.

The following is an example of the output:
[Ok] ams has correct version activated
[Ok] ams-9.3.101EF1 has correct version activated
[Ok] app-ansitl1 is ignored on dataserver.
[Fail] APP-apc is not activated
[Fail] app-dcscript has version 9.3.10.0_9.3.10-232526 instead of

9.3.10.2_9.3.10-232526
[Ok] app-idm has correct version activated
[Ok] app-lrm has correct version activated
[Ok] app-spfe has correct version activated
[Ok] plugin-combo-g6-12.3 has correct version activated
[Ok] plugin-combo-gpon-4.8 is ignored on dataserver
[Fail] plugin-ansitl1-g6-12.7 is not activated
[Fail] plugin-apc-avginclplugs-x.y is not activated
[Fail] app-np should not be activated
[Fail] ams-9.3.10.1EF1 should not be activated
6 errors found
Note In the Data server, you can only view the details of the
software components such as core, patches, and emergency fixes.
6.7 Changing passwords for default users
You need to change the password for the amssys user on each server in the cluster.
If needed, you can also change the passwords for amsftp and amssftp. To change the
passwords for all users, you need root access to the application server.
The password for amssys is changed in the server only. The passwords for amsftp
and amssftp must be changed in the servers and in the GUI. See Procedure 12-10 To
change a default user password in the 5520 AMS GUI (p. 12-21) to change a user
password in the GUI.
Procedure 6-9 To change the password of a default user on the

5520 AMS application server
Caution Passwords for the amsftp and amssftp users cannot include
the @ or : symbols.
1 Log in to the 5520 AMS application server as root.
2 In a terminal window, type:
passwd username
where:
username is the name of the user whose password you need to change.
3 Enter the new user password.
4 Re-enter the new password.
Note Solaris allows three attempts to re-enter the new password.

After three unsuccessful attempts, you will need to enter the passwd
command again.
7 Activating, starting and stopping the
servers
7.1 Activating, starting and stopping the servers 7-2
7.1 Activating, starting and stopping the servers
However, until you activate a server, the server is in a passive, standby mode. You
can activate the server as part of the installation by using the --activate or
--activate-force options, or you can activate the servers as a separate step.
that it will be safe to start the server.
You can start or stop all the servers in the cluster with a single script, or you can start
or stop each server individually.
If you are starting the servers individually, for optimal startup speed, start the data
servers before starting the application servers. Start the preferred data server before
the non-preferred data server.
Procedure 7-1 To activate a server
Before you proceed:
The server must be installed.

You must be able to log in to the server as root.
2 To run the server activation script, type:
install_dir/ams/software/release/bin/ams_activate.sh
where:
install_dir is the software directory you chose during installation; by default, this is /opt.
Procedure 7-2 To start a server
Use this procedure to start a server.
Before you proceed:
The server must be installed and activated.

You must be able to log in to the server as amssys.
1 Log in to the server as amssys.
2 To start the server, type:
ams_server start
Note 1 It can take up to 15 min to fully start all 5520 AMS server
processes. Because client connections are not accepted until the server
is fully started, there will be a significant delay between issuing the
ams_server start command with this procedure, and the ability to log in
with a 5520 AMS client.
Note 2 It can take up to 10 minutes or longer for the first server to

startup from a clean database as the database tables needs to be
created.
Procedure 7-3 To start a cluster
Use this procedure to start all the servers in a cluster.
Note After a fresh installation, the servers in a cluster must be

started separately using the ams_server script for the first time.
Subsequently the ams_cluster script can be used to start the servers.
Before you proceed:
The servers must be installed and activated.

You must be able to log in to the servers as amssys.
1 Log in to one of the servers in the cluster as amssys.
2 To start the cluster, type one of the following commands:
If you are not using a geographically redundant installation, type:
ams_cluster start
To start the cluster as the active site in a geographically redundant

installation, type:
ams_cluster start -force active
To start the cluster as the standby site in a geographically redundant

installation, type:
ams_cluster start -force standby
Procedure 7-4 To stop a server
Use this procedure to stop a server.
Before you proceed, you must be able to log in to the server as amssys.
1 Log in to the server as amssys.
2 To stop the server, type:
ams_server stop
Procedure 7-5 To stop a cluster
Use this procedure to stop all the servers in a cluster.
Before you proceed, you must be able to log in to the servers as amssys.
1 Log in to one of the servers in the cluster as amssys.
2 To stop the cluster, type:
ams_cluster stop
8 Configuring the 5520 AMS to support
NAT
8.1 Configuring the 5520 AMS to support NAT 8-2
8 Configuring the 5520 AMS to support NAT
8.1 Configuring the 5520 AMS to support NAT
Use this procedure to configure the 5520 AMS servers to communicate with
5520 AMS clients behind a NAT server. Add the translated IP address of the
5520 AMS server to the installation and configuration settings file on each
application server.
You can also use a NAT server between the 5520 AMS servers and the NEs. See the
5520 AMS Administrator Guide for more information.
Before you proceed, you must be able to log in to the 5520 AMS application servers
as amssys.
Procedure 8-1 To configure the 5520 AMS to support NAT
Perform this procedure on each application server.
1 Log in to the 5520 AMS application server as amssys.
conf/ams.conf
3 Set the AMS_CLIENT_CONNECT_IP variable to one of the following values:
The translated IP address of the server.

A hostname with a fully qualified domain name, if the server can resolve the
hostname.
4 Save and exit the ams.conf file.
To restart the 5520 AMS application, if the 5520 AMS server is running, type:
ams_server restart
To start the server, if you are finished configuring the 5520 AMS server, type:
ams_server start
9 Converting a simplex installation to
a cluster
9.1 Converting a simplex installation to a cluster 9-2
9.2 Adding and removing servers 9-5
9.1 Converting a simplex installation to a cluster
You can convert a simplex installation to a cluster. After conversion, data,

application or data and application servers can be added to the cluster as needed.
You can set up a simplex server as a cluster server at any time.
Table 9-1 Convert from a simplex installation to a cluster (p. 9-2) lists the tasks to
set up a cluster by adding new application, data or application and data servers.
Before you proceed:
The simplex server must be running.
The 5520 AMS license must include the hostnames of all the servers in the
cluster. Contact Alcatel-Lucent to update your license.
Table 9-1 Convert from a simplex installation to a cluster
Task # Task See
1 Set up the cluster infrastructure. Chapter 4 Setting up 5520 AMS

2 Perform the following on the simplex server: Procedure 9-1 To convert a simplex
i Log in to the server as amssys. server to a cluster server (p. 9-2) to run
the script to convert a simplex server to
a cluster server
ii To stop the server, type:
ams_server stop
iii Run the script to convert the simplex server to

a cluster server.
iv To start the server, type:
ams_server start
3 Install and activate the 5520 AMS solution on the new application Procedure 6-1 To install and activate the
servers. Verify that you have installed all the plug-ins you need. 5520 AMS solution (p. 6-4)
4 Start the new application servers. Procedure 7-2 To start a server (p. 7-2)
5 Apply the updated license to all the application servers in the new Procedure 12-11 To add a license key
cluster. from the 5520 AMS GUI (p. 12-22)
You have completed the set of conversion tasks.
Procedure 9-1 To convert a simplex server to a cluster server

1 Log in to the simplex server as amssys.
2 To run the conversion script, type:
ams_simplex_to_cluster.sh
Result: The script displays the following confirmations:
bash-4.1$ ams_simplex_to_cluster.sh
Checking if AMS is running
The script prompts you for the cluster subnet address and provides the subnet
address of each NIC card in the server:
Enter the subnet (in CIDR format e.g 10.1.2.0/24) to exchange

server cluster information [135.249.34.0/24 (default)]:
Subnet addresses
Subnet address:
where:
Subnet addresses is the list of subnet addresses for NICs installed on the server.
3 Type a subnet address from the list and press .
Result: The script prompts you to confirm the subnet address.
Confirm the subnet address displayed.

Correct the subnet address as required.
Result: The script prompts you for the multicast IP address for server information:
Enter the multicast IP address to exchange application information

[ 225.1.2.5 (default) ]:
To accept the default IP address, press .

Type a different IP address and press .
Caution The multicast IP address must be kept the same for all
database and application server installations.
Result: The script prompts you to confirm the multicast IP address.
Confirm the IP address displayed.

Correct the IP address as required.
Result: The script prompts you for the multicast IP address for application
information:
Enter the multicast IP address to exchange server information

[225.1.2.6 (default) ]:

Type a different IP address and press .
Caution The multicast IP address must be kept the same for all
database and application server installations.
Result: The script prompts you to configure an alternate data server:
Do you want to configure an alternate data server [ "no"

(default)| "IP-address" | "DNS name" ]?

To configure an alternate data server, type the IP address or DNS name of the
alternate data server and press.
Result: The script prompts you to update AMS configuration:
Are you sure you want to update ams configuration [ no (default)|

yes ]?
To continue, press .
To update AMS configuration, type Yes and press .
Update AMS_SITE_NAME=
Updated AMS_CLUSTERNAME=TEST
Updated AMS_MULTICAST_IP=225.1.1.1
Updated AMS_MULTICAST2_IP=225.2.2.2
Updated AMS_CLUSTER_NETWORK=135.249.34.0/24
Updated AMS_DATASERVERS=localhost
Updated AMS_APPSERVER_ENABLED=true
Updated AMS_DATASERVER_ENABLED=true
Updated AMS_ARBITER_ENABLED=false
Updated AMS_PREFERRED_SERVER=true
*** WARNING ***
* There are changes to the firewall rules required for this

application to run correctly.
*
Execute/opt/ams/software/ams-9.4.00-282513/bin/ams_updatefirewal
l script for more details.
10 Return to Table 9-1 Convert from a simplex installation to a cluster (p. 9-2) to
resume the conversion tasks.
9.2 Adding and removing servers
Servers can be added to, and removed from, a cluster after you have created it.
Adding servers
Application and data servers can be added to an existing cluster.
If you install a new alternate data server, it will establish communication with the
preferred server automatically when started.
If you add a new server to the cluster, confirm that the new server is in the Site object
in the 5520 AMS GUI and configure the server as required.
Procedure 9-2 To configure a newly added application server in a

site in the 5520 AMS GUI
Use this procedure to confirm that the newly added application server in a cluster is in
the Site object in the 5520 AMS GUI, and to configure the server as required.
Before you proceed:
The cluster must already be configured.

The data server must be running.
The license must contain the host ID for the new application server.
1 Install, activate, and start the new 5520 AMS server by following the appropriate
procedure in this chapter. When prompted for a site name, use the same site
name you provided when installing other servers in the cluster.
Note Server and application multicast IP addresses must be the

same as the existing ones.
2 Confirm that the new server is present in the Site object:
i Open a copy of the 5520 AMS client and log in to an application server that is
already running as part of the cluster. You must log in as an administrator.
ii Open the Administration perspective.
iii Navigate to the Application Server object for the server that has been added
by choosing EMS AdministrationEMS SystemSiteApplication & Data
Servers in the Administration Tree.
Result: If communication with the server is established and ongoing, the

server status is Up. If communication is not yet established, the server status
is Down.
3 Select the Application Server object and configure the parameters in the Object
Details view as required.
4 Trap management for NEs will be automatically allocated to the new server over
time. Optionally, perform the following steps to force a redistribution of NE traps
among the available servers:
i Right-click the Site object and choose Rebalance from the contextual menu.
A dialog box appears, warning that rebalancing can take some time.
ii Click OK.
Note In a geographically redundant setup, you can only perform a

rebalance on the active site. To confirm which site is active, see the
Object Details view for the Site.
Removing servers
You can remove application and data servers from the cluster. There must always be
at least one application and one data server present in the cluster for the cluster to
function.
If you stop and uninstall a standby data server, you need take no further action. The
active data server will continue to function as part of your 5520 AMS cluster.
If you stop and uninstall the active data server where a standby data server is present,
you also need take no further action. The former standby data server will take over
data operations.
To remove an application server from the cluster, you must also manage the Site
object in the 5520 AMS GUI. Procedure 9-3 To remove an application server from
a cluster (p. 9-6) describes how to remove an application server from a cluster in the
5520 AMS.
Note When you remove a server from a cluster, the ams_cluster

status script will continue to show the status of the uninstalled server.
To reset the script, restart all the servers.
Procedure 9-3 To remove an application server from a cluster
Use this procedure to remove an application server from the cluster.
Before you proceed:
The cluster must be configured.

The application and data servers must be running.
You must be able to log in to the application server as amssys.

You must be able to log in to the 5520 AMS client as an administrator. See the
5520 AMS Administrator Guide for more information.
1 To stop the application server, perform the following steps:
i Log in to the server as amssys.
ii To stop the server, type:
ams_server stop
Result: The tasks of the server will be reallocated among the remaining
application servers.
2 Open a 5520 AMS client and log in to an application server that is already running
as part of the cluster. You must log in as an administrator.
3 Open the Administration perspective.
4 Navigate to the Application Server object for the server you have stopped by
choosing EMS AdministrationEMS SystemSiteApplication & Data Servers in
the Administration Tree.
Result: The server status is Down for this application server because there is no
current connection to the server.
5 Right-click the Application Server object and choose Delete from the contextual
menu.
Result: A confirmation dialog box prompts you to confirm deletion of the server.
6 Click Yes.
Result: The server is deleted from the Application Servers object.
7 Optionally, perform the following steps to force a redistribution of NE traps among

the available servers:
i Right-click the Site object and choose Rebalance from the contextual menu.
A dialog box appears, warning that rebalancing can take some time.
ii Click OK.
Redistributing management of NEs

You can split one EMS system into two systems, for example if the network has
expanded beyond the maximum size supported by the 5520 AMS. To redistribute
management of NEs, export NE data from the old server and import it on the new
server.
Note To export schedules, select both the Schedules application

and the application that includes the scheduled jobs. For example, to
export a scheduled NE backup, select both Schedules and NE Backup
(database only) and Jobs.
Procedure 9-4 To split NE data (p. 9-8) describes how to split NE data.
Procedure 9-4 To split NE data

1 Log in to the 5520 AMS client for the old server as an administrator.
2 Close other client sessions to avoid conflicts in the exported data:
i Determine the IP address of the workstation on which you are running the
5520 AMS client.
ii Open the Administration perspective.
iii Open EMS AdministrationUser ManagementActive Sessions in the

Administration Tree.
Result: Under the Active Sessions element, there is a list of all active user
sessions, each identified by the IP address of the computer on which the
client application is running.
iv Request other users to log out of the 5520 AMS, or close the other active
sessions by selecting all but your own session, right-clicking the selection,
and choosing Delete from the contextual menu.
3 Choose FileExport.
Result: The Export window opens. The top of the window shows the directory
where the export file will be saved.
4 Choose the data you need to export from the server.
i In the Application Filter panel, select the check box beside a data type to
include that data in the export process, or use Select All and Clear All to
select or clear all check boxes at once.
ii Select the Select NE Filter check box and click Add to open the NE Selection
window. In the NE Selection window, choose the NEs for which you need to
export data.
5 Click Finish.
Result: The Export tool creates a .tar file containing all of the exported data, and
displays a status window showing the results of the export operation.
The exported data file has the filename exportdate-time.tar
where:
date is the current date in the format ddmmmyyyy.
time is the time the export was performed in the format hh-mm-ss.
For example: export07Apr2011-10-12-11.tar
6 Log in to the 5520 AMS client for the new server as an administrator.
7 Verify that no other users are logged in to the 5520 AMS server. You can view a list
of users currently logged in under EMS AdministrationUser
ManagementActive Sessions in the Administration perspective.
Note If there are other users logged in to the 5520 AMS server,
determine which active session is yours and delete the other active
sessions.
8 Migrate data in preparation for import to the 5520 AMS:
i From the 5520 AMS menu, choose FileImport.
Result: The Import File Selection window opens.
ii Click Browse and navigate to the export data file you created on the old
server. Click Finish to return to the Import File Selection window.
9 Click Next.
Result: The second Import window opens.
10 In the Application Filter panel, select the data types you need to import, or click
Select All to include all data types for import.
Result: After you select at least one type of data to import, the Finish button is
enabled.
11 To import your data, click Finish.
12 Review the Import Results window for errors that may have occurred while
importing data.
13 Resolve errors reported by the import:
i If errors occur due to duplicate data, remove the duplicate objects from the
5520 AMS database. Then repeat this procedure.
ii If other errors occur, you can proceed with the import but any data that is
the subject of errors will not be imported. For guidance with specific error
messages, contact Alcatel-Lucent technical support at
http://support.alcatel-lucent.com. See Procedure 2-1 To find contact
information for technical assistance (p. 2-10) for more information.
Note To store the information in the Import Results window, click

Copy to Clipboard.
Result: All entries created are copied to the clipboard.
Paste the results into a text editor and save the file.
10.1 Overview 10-2
10.2 Ping-pong protection 10-2
10.3 Configuring geographic redundancy 10-3
10.4 Configuring the OSS arbiter 10-7
10.5 Modifying geographic redundancy 10-9
10.1 Overview
This chapter provides the procedures to configure geographic redundancy in a 5520

AMS site. For detailed information on the geographic redundancy installation tasks,
see Section 3.3 Geographic redundancy installation overview (p. 3-7).
10.2 Ping-pong protection
In a ping-pong scenario, the system continuously switches over in a never-ending

cycle. For example, in a geographically redundant setup with an AD server in both
active and standby sites, the server in the active site (Server A) is the active server
and the server in the standby site (Server B) is the standby server. Server A and
Server B are healthy. If one of the 5520 AMS processes on Server A becomes
unhealthy, the health script indicates the process state as unhealthy. Server A
becomes the standby server and Server B becomes the active server. If the earlier
unhealthy 5520 AMS process on Server A becomes healthy, Server A becomes
healthy immediately but remains the standby server. If the same 5520 AMS process
on Server B becomes unhealthy, Server B becomes Unavailable and becomes the
standby server, and Server A becomes the active server. If the earlier unhealthy
5520 AMS process on Server B becomes healthy, Server B becomes healthy again.
If the 5520 AMS process on Server A becomes unhealthy, Server A becomes
Unavailable, and becomes the standby server. Hence, the system continuously
switches over in a never-ending cycle, and is called the ping-pong scenario.
To protect against the ping-pong scenario, after a server goes to the standby state, it
cannot become active within the configured time limit. The default time limit is 30
minutes. The site will report itself Unavailable during this period regardless of the
actual health state. So, when the 5520 AMS process uses the memory on the other
server in the setup, no healthy alternative is available and the server remains active.
Note To configure the timer value for ping-ping protection,

modify the PINGPONG_PROTECTION_TIMEOUT parameter in
the amsgeomonitor.conf file in $AMS_SOFTWARE_HOME/conf.
When ping-pong protection is initiated, both servers can refuse to start. To overrule
the ping-pong protection, perform Procedure 10-1 To overrule ping-pong protection
(p. 10-2).
Procedure 10-1 To overrule ping-pong protection

1 Log in to the server on which the ping-pong protection timer is running, as amssys.
2 To overrule ping-pong protection, type:
ams_server resetgeo
Result: The ping-pong protection timer is stopped, overruling the ping-ping

protection.
Note Starting the servers depends on the system state. If the system
state indicates healthy, the servers are started automatically.
10.3 Configuring geographic redundancy
Use the procedures in this section to set up geographic redundancy and to configure
the 5520 AMS to run a script if one site is down.
Note In a geographically redundant setup with two data servers at

the standby site, to limit the bandwidth across the WAN for
replication from the active data server at the active site to one of the
data servers at the standby site, ensure that one of the data servers at
the standby site remains shutdown. If both data servers at the standby
site are started, they will replicate across the WAN from the active
data server at the active site.
Configure data replication on each data server at the active site and standby site. See
installation (p. 3-11) for the context in which to perform this procedure.
Before you proceed:
The servers must be activated.
Procedure 10-2 To configure data replication between sites

1 Verify that the data servers have IP connectivity over the network they will use
for data replication.
2 Log in to the preferred data server at the active site as amssys.
3 To run the geographic redundancy configuration script, type:
ams_geo_configure.sh
Result: If any snapshots of data are found on the server, the script prompts you
to clean them:
Clean up existing snapshots of filesystem - data/sharedata:
[ 1 ] yes
2 no
Choice:
To clean up the existing snapshots, type 1 and press .

To keep the snapshots only if you have verified that they are valid, type 2 and
press .
Result: The script prompts you to enable geographic redundancy:
Enable geographic redundancy mode:
[1] yes
2 no
Choice:
5 To enable geographic redundancy, press .
Result: The script prompts you about which site you are configuring:
Is this the active or the standby site:
[1] active
2 standby
3 -Previous menu-
Choice:
6 Perform one of the following steps
To indicate that this is the active site, press .

To indicate that this is the standby site, type 2 and press .
Result: The script prompts you to confirm your choice:
Are you sure you want to make this site the active site [ no
(default) | yes ]?
Result: The script prompts you for the name of the other site:
Enter the name of the remote site
Value:
8 Type the name of the other site and press .
Result: The script prompts you for the IP address of the preferred data server at
the standby site:
Enter the IP address of the preferred dataserver at site name
Value:
where:
name is the name of the site you entered.
9 Type the IP address of the preferred data server at the standby site and press .
Result: The script prompts you for the IP address of the non-preferred data server
at the standby site:
Enter the IP address of the non-preferred dataserver at site name
Value:
where:
name is the name you entered in step 8 (p. 10-4).
10 (Optional) If you have two data servers at the standby site, type the IP address of
the non-preferred data server at the standby site and press .
Result: The script prompts you for the local network interface to use for
synchronization traffic:
Select the local NIC used to synchronize data with site name:
[1] bge0 (IP address)
2 bge1 (IP address)
Choice:
where:
name is the site name.
IP address is the IP address of the network interface.
11 Type the number corresponding to the IP address for your local network interface.
Result: The script prompts you for enabling geographic redundancy:
Enable automatic switchover ? [ no (default) | yes ]
To enable automatic switchover, type y and press .

To disable automatic switchover, press .
Result: The script provides a summary:
Summary:
Remote site name: name
IP address of preferred data server on remote site: IP address
IP address of non-preferred data server on remote site: IP address
Local NIC for synchronization: bge0
Automatic switchover: enabled or disabled
The script prompts you to confirm:
Are you sure you want to enable geographic redundancy? [ no

(default) | yes ]
Note If you have a second data server at the active site, repeat the
procedure for the second server.
14 Repeat steps 2 (p. 10-3) to 13 (p. 10-6) on the data servers at the standby site.
15 Start the servers at the active site. See Procedure 7-2 To start a server (p. 7-2).
16 To verify that the JBoss server at the active site is running, type the following on
an application server:
ams_server status
When the script output says the JBoss server is running, go to step 17 (p. 10-6).
17 Start the servers at the standby site. See Procedure 7-2 To start a server (p. 7-2).
Note The servers at the active site will start all processes. The
standby site will start the process monitor, EMS services, and MySQL
process where MySQL acts as the standby database.
18 To confirm that the sites are communicating with each other, check the
processmonitor log file, located at $AMS_LOG_DIR/processmonitor.log.
Result: The log should contain the following line:
Event: Established connection with remote site.
For more information about system logs, see the 5520 AMS Administrator Guide.
Procedure 10-3 To configure the 5520 AMS to run a script if one site
is down
Perform this procedure on each server.
1 Log in as amssys to each data server in the standby site.
2 To configure a script to run when the active site is down, open the following file
in a text editor:
$PLATFORM_SCRIPTS_DIR/activeSiteDown.sh
3 Add instructions to execute your script, save and close the file.
4 Log in as amssys to each data server in the active site.
5 To configure a script to run when the standby site is down, open the following file
in a text editor:
$PLATFORM_SCRIPTS_DIR/stanbySiteDown.sh
6 Add instructions to execute your script, save and close the file.
Result: When a site becomes unreachable, the 5520 AMS will initiate your script.
10.4 Configuring the OSS arbiter
Note The OSS arbiter is not provided by Alcatel-Lucent.
To use an OSS arbiter for automatic switchovers, configure the OSS arbiter with the
IP addresses of the data servers at both sites. The OSS arbiter sends the SSH key to
all the data servers.
Start the OSS arbiter in the following situations:
To initiate monitoring of the health of both sites.
To restart monitoring after a switchover.
To perform the procedures in this section, you must be able to log in as amssys to the
server where the OSS arbiter is installed.
Procedure 10-4 To configure the OSS arbiter in a geographically

redundant installation
Caution The DEMO_IT_infrastructure_integration script is intended

for demonstration purposes only. Alcatel-Lucent does not guarantee the
script and advises that you do not use the script in a live deployment.
The script is only provided to demonstrate the principle of how a
geographically redundant installation can be monitored for an
automatic switchover.
1 Log in as amssys to the server where the OSS arbiter is installed.
2 To start the configuration script, type:
DEMO_IT_infrastructure_integration config
the active site:
Enter the IP address of the preferred data server of active site
3 Enter the IP address and press .
at the active site:
Enter the IP address of the non-preferred data server of active

site
5 If there is only one data server at the active site, press .
the standby site:
Enter the IP address of the preferred data server of standby site
Enter the IP address of the non-preferred data server of standby

site
8 If there is only one data server at the standby site, press .
Result: The script presents a success message:
Update Arbiter configuration
The script updates the SSH keys and prompts you to confirm the connection:
Update ssh key...
Server IP address
The authenticity of host 'IP address (IP address)' can't be

established.
RSA key fingerprint is fingerprint.
Are you sure you want to continue connecting (yes/no)?
Result: The script confirms the update and prompts you for a password:
Warning: Permanently added 'IP address' (RSA) to the list of known

hosts.
Password:
10 Enter the password for the amssys user and press .
Result: The script repeats steps 9 (p. 10-8) and 10 (p. 10-8) for each of the other
data servers.
The configuration is complete.
Procedure 10-5 To start the OSS arbiter in a geographically

redundant installation
1 Log in as amssys to the server where the OSS arbiter is installed.
2 To start the OSS arbiter, type:
DEMO_IT_infrastructure_integration start
Result: The OSS arbiter begins monitoring the health of the sites. The following is
an example of the output:
Start Arbiter
Arbiter configuration
IP address of the preferred dataserver of active site:

192.168.95.70
IP address of the non-preferred dataserver of active site:

192.168.95.78
IP address of the preferred dataserver of standby site:

192.168.99.83
IP address of the non-preferred dataserver of standby site:

192.168.99.85
Checking Active site status
Active site is up
Sleep 10 seconds...
Checking Active site status
Active site is up
10.5 Modifying geographic redundancy
Upon setting up geographic redundancy, you can perform a manual switchover, or

use the configuration script to disable geographic redundancy or trigger a forced full
synchronization of shared data.
Depending on the option, use the procedures in Table 10-1 Modify geographic
redundancy (p. 10-9) to modify geographic redundancy.
Table 10-1 Modify geographic redundancy
Option See
Perform a manual Procedure 10-6 To switch between the active and

switchover standby site (p. 10-10)
Option See
Disable geographic Procedure 10-7 To change a geographically redundant

redundancy installation to two independent sites (p. 10-11)
Trigger a forced full Procedure 10-8 To trigger a forced full synchronization

synchronization of shared data (p. 10-12)
To perform the procedures in this section, you must be able to log in to the servers
as amssys.
Procedure 10-6 To switch between the active and standby site

1 Log in to one of the servers as amssys.
2 Stop the 5520 AMS servers at the active and standby sites to perform the
switchover.
Note The server does not allow to switch between active and
standby sites in a running state. Alcatel-Lucent recommends to wait for
the FS sync to be completed before stopping the servers. To force stop
the servers without checking the FS sync, use the following command:
ams_server stop [-force]

3 To complete the switchover, perform one of the following procedures:
To make the local site the active site, type:
ams_cluster switch active
Result: The script checks the other site:
Active site status is being checked (May take several seconds)
If the other site is active, the script returns a warning:
WARNING: Remote site reports to be Active Site.
ERROR: Cannot switch to active.
If the other site is unreachable, the script returns a warning:
WARNING: Cannot check if the remote site is active or not.
ERROR: Cannot switch to active.
To make the local site the standby site, type:
ams_cluster switch standby
To make the local site the active site without checking the status of the other
site, type:
ams_cluster switch -force active
4 Restart the 5520 ams servers.
Procedure 10-7 To change a geographically redundant installation to

two independent sites
Note If geographical redundancy is disabled, the automatic

switchover will be disabled.
1 Log in to the data server at either site as amssys.
Result: The script prompts you for the desired change:
Which actions to perform:
[ 1 ] Switch site mode (activestandby) or (standbyactive)
2 Disable geographical redundancy
3 Force full synchronization on next periodic synchronization
4 Exit
Choice:
Note If you are a logged in to the standby server, the switch mode
option available to the operator is (standby active).
3 Type 2 and press .
Result: The script prompts you to confirm:
Are you sure you want to disable geographic redundancy? [ no

(default) | yes ]
Result: Geographical redundancy is disabled. Both sites remain in the same state,
but data is not replicated between them.
5 Restart the servers at both sites. Perform the following on each server:
i Log in to the server as amssys.
ii To restart the server, type:
ams_server restart
Triggering a forced full synchronization of shared data

Run the configuration script on the data server at the active site to trigger a forced
full synchronization of data files in the shared data directory, in case data mismatch
exists between active and standby sites.
Note 1 A full synchronization is an incremental synchronization
for the data in the database.
Note 2 To trigger a full synchronization of the data in the database,
clear the database at the standby site. On the data server at the standby
site, type:
ams_remove_data.sh
The complete database is replicated during the next synchronization.
Procedure 10-8 To trigger a forced full synchronization of shared

data
1 Log in to the data server at the active site as amssys.
Result: The script prompts you for the desired change:
Which actions to perform:
[ 1 ] Switch site mode (activestandby)
2 Disable geographical redundancy
3 Force full synchronization on next periodic synchronization
4 Exit
Choice:
Result: The script displays the following output:
Finished. Next incremental sync will trigger a full sync.
4 To check the status of full synchronization, perform the following steps:
i Log in to the data server at the standby site as amssys.
ii Run the ams_server script. Type:
ams_server status
iii See the FS sync status parameter in the output for the full synchronization
status.
Note The full synchronization of shared data may take several hours
depending on the data size.
Applies to This chapter applies to Red Hat Enterprise Linux

systems only.
11.1 Updating firewall rules 11-2
11.1 Updating firewall rules
Changes can occur to the firewall rules in the following scenarios:

The 5520 AMS is installed, or the 5529 Enhanced Applications or 5520 AMS NE
plug-ins are installed and activated using the ams_install script.
The 5520 AMS is uninstalled, or the 5529 Enhanced Applications or 5520 AMS
NE plug-ins are deactivated and uninstalled using the ams_install script.
Geographic redundancy is enabled or disabled.
A simplex installation setup is converted to a cluster setup.
vsftpd is configured.
When any of the actions are performed with the specified script and if changes to the
firewall rules are identified, the following warning will be displayed:
There are changes to the firewall rules required for this application
to run correctly. Execute ams_updatefirewall script for more details.
Perform Procedure 11-1 To update firewall rules (p. 11-2) on Red Hat Enterprise
Linux systems to update the firewall rules.
Note If the ams_updatefirewall script is run on a Solaris system,

the following error message is displayed:
ERROR: Not supported on this platform
Procedure 11-1 To update firewall rules

1 Log in to 5520 AMS server as root.
2 To check if there are changes to the firewall rules, type:
./ams_updatefirewall
Result:
If there is no change to the firewall rules, the following message is displayed:
All ports are already added to firewall.
If there are changes to the firewall rules, a table listing the missing port rules in
the iptables is displayed. The following message is displayed:
Do you want to add these ports to the iptables [ no (default) |

yes ]?
3 To add the missing ports to the iptables, type y and press .
Result: The missing ports are added to the iptables. The following message is
displayed:
Adding ports to the iptables
Done
4 To check the updates to the iptables, type:
/etc/init.d/iptables status
Result: The status of the iptables is displayed.
12.1 Client installation overview 12-2
12.2 Installing a single 5520 AMS client 12-4
12.3 Installing a shared 5520 AMS client 12-6
12.4 Launching and updating the 5520 AMS client 12-13
12.5 Changing passwords for default users in the 5520 AMS

GUI 12-20
12.6 Adding a license to the 5520 AMS 12-21
12.1 Client installation overview
You have three options for deploying the 5520 AMS client application:
Table 12-1 Types of client installation
Type of installation Description
Single installation In either the Windows or Red Hat Enterprise Linux operating systems, install a
single client for use by a single operator at each workstation or on a server.
Multiple installations On a server running the Windows(1) or Red Hat Enterprise Linux operating system,
install a separate copy of the client in the home directory of each user on the
server. Each copy of the client application is installed and updated separately
from the others.
Shared installation On either a Windows or Red Hat Enterprise Linux server, install a copy of the
client that can be used by many operators simultaneously.
Notes
(1) Alcatel-Lucent does not recommend to have multiple installations on the Windows client.
Shared client installation

In a shared client installation, a single shared copy of the 5520 AMS client is
installed on a Red Hat Enterprise Linux systems or a Windows server. Users log in
to this server and launch the client there, rather than on their individual workstations.
A key benefit of a shared installation is the reduction in administrative overhead. A
shared installation allows you to install and apply updates to the client application
only once, rather than separately for each copy of the client that is installed.
Although the client application is shared, each user ID has a private work space on
the server. Two log files that record client-based events (output.log and
GuiAlarm.log) for individual users are maintained in the home directory of the user.
Shared client installation in Red Hat Enterprise Linux

On Red Hat Enterprise Linux servers, only a root user can install the 5520 AMS
client in the shared configuration. When the root user is installing the client, the
shared configuration is the default selection; for other users, a single installation is
default.
The Red Hat Enterprise Linux client installation program creates the amssys user
group and user account if they do not already exist on the host server. The default
amssys user password is amssys.
When installing in Red Hat Enterprise Linux, you have the option to configure the
shared installation as either restricted or unrestricted:
A restricted client can be launched only by users who are members of the amssys
user group on the host server.
An unrestricted client can be launched by anyone who is logged in to the host
server.
Note Only one instance of the 5520 AMS client application can be
open at a time for a UNIX user account. To ensure that multiple users
can have simultaneous access to the shared client, create separate user
accounts for each operator who can log in to the 5520 AMS client
concurrently.
If more than one user shares the same user ID on a Red Hat Enterprise Linux server,
you may choose to use the shared client wrapper script to create individual work
spaces. See Individual work spaces with a shared client (p. 12-9).
Shared client software updates in Red Hat Enterprise Linux

Only the root and amssys users can apply software updates, which are periodically
available from the 5520 AMS server, because these are the only users who have
access to the common installation area for the client. For this reason, the automatic
download of updates is disabled for shared installations. You must manually trigger
software updates after logging in to the client, as described in Procedure 12-6 To
launch and update the 5520 AMS client (p. 12-14). For all other users, the menu
selections HelpInstall and HelpUpdate are permanently disabled.
Note For amssys or root users to have access to the install and
update menu items, they must launch the client from the installation
directory.
Client software updates in Windows

Only Windows users with write access to the folder where the 5520 AMS client is
installed can apply software updates, which are periodically available from the
5520 AMS server. A user with write access to the client installation folder can
automatically download updates as normal.
Client installation tasks

Table 12-2 Install the 5520 AMS client (p. 12-4) lists the tasks to install the
5520 AMS client.
Table 12-2 Install the 5520 AMS client
Task # Task See
1 Install the 5520 AMS client application in single Procedure 12-1 To install a single 5520 AMS client in
or shared configuration. Windows/Red Hat Enterprise Linux System (p. 12-4) to
install a single client in the Windows or Red Hat
Enterprise Linux operating system. Repeat this step for
each Windows or Red Hat Enterprise Linux workstation
requiring a copy of the client.
Procedure 12-2 To install a shared client in Windows (p.
12-6) to install a shared client on a Windows server
Procedure 12-3 To install a shared 5520 AMS client in Red
Hat Enterprise Linux (p. 12-8) to install a shared client on
a Red Hat Enterprise Linux presentation server
2 Launch the client and apply software updates Procedure 12-6 To launch and update the 5520 AMS client (p.
available from the 5520 AMS server. 12-14)
3 Update passwords for the amsftp or amssftp user Procedure 12-10 To change a default user password in the
if needed. 5520 AMS GUI (p. 12-21)
4 Apply license keys. Section 12.6 Adding a license to the 5520 AMS (p. 12-21)
You have completed the set of client installation tasks.
Note 1 Alcatel-Lucent recommends that you use the

SolThemeTraditional theme with the 5520 AMS GUI. However, you
are free to use your preferred theme.
Note 2 Ensure that you have installed Internet Explorer version
R7.x or higher on your Microsoft Windows client for the Map view to
display object icons properly. For example, with Internet Explorer
R6.0, the selected objects are not surrounded by a blue rectangle in the
Map view.
12.2 Installing a single 5520 AMS client
The procedures in this section describe the installation of a single client application
intended for use by one operator. You can install a single client under Windows , or
Red Hat Enterprise Linux operating systems.
In a Red Hat Enterprise Linux system, each user can install a separate copy of the
client application. However, a shared installation may be much more efficient to
install and maintain. To install a shared installation, you need root access to the
server.
You can download the client software from a 5520 AMS, Release 9.4 application
server.
Procedure 12-1 To install a single 5520 AMS client in Windows/Red

Hat Enterprise Linux System
Use this procedure to install a single (not shared) copy of the 5520 AMS client in the
Windows/Red Hat Enterprise Linux operating system.
Before you proceed:
The 5520 AMS server must be installed, activated, and running.

You need the IP address or DNS name of a 5520 AMS, Release 9.4 application
server.
You need access to a Web browser.
For Red Hat Enterprise Linux systems, a user account with its own separate
home directory must exist.
1 Log in to the server or workstation on which you are installing the 5520 AMS client
application as a non root user.
2 Open a Web browser and navigate to the client distribution page on the 5520 AMS
server. Type the following URL:
http://server:8080/ams-client
where:
server is the IP address or DNS name of the 5520 AMS application server.
Result: A 5520 AMS Client Distribution page opens, which includes instructions for
downloading the 5520 AMS client.
3 Click one of the following to download a client:
Download Client (Windows PC) link, and save the resulting client installation
file to the local system.
Download Client (Redhat PC X86_64) link, and save the resulting file to the
home directory of a user.
On Windows systems:
Navigate to the location where you saved the client installation file and unzip
it.
Result: A copy of the client application is extracted within a /ams subfolder in
the location you selected, including the client launch file, amsclient.exe.
On Red Hat Enterprise Linux systems:
Navigate to the location where you saved the client installation file and
to make the installation file executable, type:
chmod 555 directory/filename
where:
directory is the directory where you saved the client installation file.
filename is the filename of the client installation file.
To run the client installer, type:
./filename
Result: The installation software displays the following confirmation:
Checking OS and version ... OK.
The installer prompts you for the client installation type:
You are not root. Installation will be non-shared
Do you want to allow a user to open multiple GUIs ? [ yes

| no (default) ]?
Type yes.
Allowing multiple GUIs per user
In which top directory you want to install the software
The directory should exist ["/opt" (default) |

"user_home_directory" | "<directory>" ]?
where:
user_home_directory is the home directory for the user you are logged in as.

To accept the default /opt directory, press .
To install the client in your home directory, type the path provided in
the prompt and press .
To install the client in another directory, type the path to another
directory to which you have access and press .
Result: When the installation is completed, the installer presents the location of
the log file.
12.3 Installing a shared 5520 AMS client
A shared installation is possible in Windows or Red Hat Linux operating systems.

See Shared client installation (p. 12-2) for more information about the capabilities,
limitations, and options available to you for a shared client installation.
You can download the client software from a 5520 AMS, Release 9.4 application
server.
Procedure 12-2 To install a shared client in Windows (p. 12-6) describes how to
install a shared client in Windows.
Procedure 12-3 To install a shared 5520 AMS client in Red Hat Enterprise Linux (p.
12-8) describes how to install a shared client in Windows.
If you need to use the shared client wrapper in Red Hat Enterprise Linux, see the
Procedure 12-4 To install a shared client with the shared client wrapper (p. 12-10).
Procedure 12-2 To install a shared client in Windows
Use this procedure to install a shared copy of the 5520 AMS client on a Windows server.
Before you proceed:

You need the IP address or DNS name of a 5520 AMS, Release 9.4 application
server.
1 Log in to the Windows server on which you are installing the 5520 AMS client
application.
2 Create a directory for the installation of the 5520 AMS shared client.
3 Configure the access permissions for the client directory. To start the 5520 AMS
client, a Windows user requires read and execute access to the directory. To
download and apply updates in the 5520 AMS client, a Windows user requires write
access to the directory in addition to read and execute access.
where:
5 Click the Download Client (Windows PC) link, and save the resulting file to the
local system.
6 Navigate to the location where you saved the client installation file and unzip it
into the directory you created in step 2 (p. 12-7).
Result: A copy of the client application is extracted within an /ams subfolder in

the location you selected, including the client launch file, amsclient.exe.
7 By default, the location of the 5520 AMS client user workspace and configuration
directories is @user.home/5520AMS/9.4. If required, perform the following steps
to change the location of the user workspaces.
i Navigate to the 5520 AMS configuration directory.
ii Open the config.ini file for editing.
iii Configure the following attribute:
osgi.instance.area=user_workspace
where:
user_workspace is the location where you need the 5520 AMS to create individual user
workspace directories.
iv Save the config.ini file.
Procedure 12-3 To install a shared 5520 AMS client in Red Hat

Enterprise Linux
Use this procedure to install a shared copy of the 5520 AMS client on a Red Hat
Enterprise Linux presentation server.
Before you proceed:

You need the IP address or DNS name of the 5520 AMS, Release 9.4 application
server.
You must be able to log in to the server hosting the shared client as root.
1 Log in to the presentation server (for Red Hat Enterprise Linux) on which you are
installing the 5520 AMS client application as root.
where:
3 Click the Download Client (Redhat PC X86_64) link, and save the resulting file to
the local system.
4 Navigate to the location where you saved the client installation file to make the
installation file executable, type:
where:
5 To run the client installer, type:
./filename
Result: The installation software displays the following confirmation:
Checking OS and version ... OK.
Do you want a single installation used by multiple operators

(shared installation)? [ yes (default) | no ]
6 Press .
Result: The installer prompts you for installation restrictions:
Shared mode is set
Do you want to allow a user to open multiple GUIs ? [ yes | no

(default) ]?
Type yes.
Allowing multiple GUIs per user
Restrict the usage of software to amssys group? [ no (default) |

yes ]
The amssys user group will be created on the host server during installation (if not
already present). If you choose yes, then only members of the amssys group will
be able to run the 5520 AMS client. If you choose no, then all users logged in to
the server and who can access the client application file can run it.
To restrict usage to members of the amssys user group, type y and press .
To allow unrestricted usage of the client application, press .
Result: The installer prompts for the installation directory:
Nonrestrictive mode is set
In which top directory do you want to install the software
The directory should exist [ "/opt" (default) | "current

directory" | "<directory>"]?
where:
current directory is the directory in which you are running the installer.

To save to the current directory, type the path provided in the prompt and
press .
To save to a different directory, type the path of a directory that will hold the
5520 AMS client and press .
Result: The installation proceeds and the client application is put in the directory
you selected. A log of the installation is created in /var/adm/log/, and named
ams-client-installation.nnnn.log, where nnnn is a random four-digit number.
Individual work spaces with a shared client

If you use a shared 5520 AMS client with a Red Hat Enterprise Linux server, a work
space directory is created for each UNIX user ID. The work space directory stores
temporary data. If multiple 5520 AMS operators share the same UNIX user ID, you
can create individual work spaces for each operator using the shared client wrapper
script. When the operator enters a 5520 AMS username and password, the shared
client wrapper creates a work space directory for the operator and logs the operator
in to the client.
You can use the shared client wrapper script if your environment meets the following
criteria:
An SGD, Tarantella, or Citrix application server is in use.
Operators do not each have their own UNIX account or home directory.
Operators do not have access to the presentation server using UNIX shells, for
example, Telnet.
The client is installed in shared mode.
Warning The use of the client wrapper script creates a working

environment that is not secure. If your environment does not meet the
criteria, Alcatel-Lucent does not recommend using the client wrapper
script.
To use the shared client wrapper in a cluster, perform the following procedures:
Install the client and wrapper. See Procedure 12-4 To install a shared client with
the shared client wrapper (p. 12-10) for more information.
Configure the presentation server to use the wrapper. See Procedure 12-5 To
configure the presentation server and login title to use the shared client wrapper
(p. 12-12) for more information.
As part of configuring the presentation server to use the wrapper, start the client once
without using the wrapper script. This allows the client to learn the site and the IP
addresses of all application servers.
Before you proceed, you must be able to log in to the 5520 AMS server as root.
Procedure 12-4 To install a shared client with the shared client

wrapper
1 Log in to the presentation server on which you are installing the 5520 AMS client
application as root.
where:
server is the IP address or DNS name of the 5520 AMS server.
3 Click the Download Client (Redhat PC X86_64) link, and save the resulting file to
the local system.
4 Navigate to the location where you saved the client installation file and to make
the installation file executable, type:
where:
5 To run the client installer, type:
filename --sharedunixaccountwrapper
Result: The installer checks for the appropriate operating system, then begins the
installation process.
Do you want a single installation used by multiple operators

(shared installation)? [ yes (default) | no ]
6 Press .
Result: The installer prompts you for installation restrictions:
Restrict the usage of software to amssys group? [ no (default) |

yes ]
The amssys user group will be created on the host server during installation (if not
already present). If you choose yes, then only members of the amssys group will
be able to run the 5520 AMS client. If you choose no, then all users logged in to
the server and who can access the client application file can run it.
To restrict usage to members of the amssys user group, type y and press .
To allow unrestricted usage of the client application, press .
Result: The installer prompts for the installation directory:
In which top directory do you want to install the software
The directory should exist [ "opt" (default) | "directory" ]?
where:
directory is the directory in which you are running the installer.

To save to a different directory, type the path of a directory that will hold the
5520 AMS client and press .
Result: The installation proceeds and the client application is put in the directory
you selected. A log of the installation is created in /var/adm/log/, and named
ams-client-installation.nnnn.log (where nnnn is a random four-digit number).
Procedure 12-5 To configure the presentation server and login title

to use the shared client wrapper
1 To create a directory on the server where the work spaces will be stored, type:
mkdir /udr
mkdir /udr/amsworkspaces
2 Verify that the new directory is writable by the UNIX account the presentation
server will use.
3 Configure the presentation server and login title to provide an icon on the desktop
for each 5520 AMS application server.
Configure the icon so that double-clicking on it will invoke the following

command:
client_dir/amsclient_wrapper --prefix=<workspace_path>
--server=<server_information> --logintitle=<GUI login title>
where:
client_dir is the directory where the shared client is installed. By default, this is /opt.
workspace_path is the path where workspaces will be stored. For example, /udr/amsworkspaces.
server_information is a comma-separated list of the IP addresses, hostnames or site names the
operators will log in to.
GUI login title is the new title that you want to provide to the Login dialog of the Red Hat
Enterprise Linux GUI.
For example:
./amsclient_wrapper --prefix=/udr/amsworkspaces --server=amsmtxsrv05

--logintitle=5520 AMS Login - Texas
Note 1 The --logintitle argument is optional. If the login title

comprises several words, the title must be within double quotes ( ) in
the --logintitle argument.
Note 2 The ams_client wrapper script takes an additional optional

argument: -allowmultiple. This argument allows multiple logins by the
same 5520 AMS user. See the 5520 AMS User Guide for information
about using the -allowmultiple argument with the amsclient.exe script.
4 To start the client to learn the site information, type:
client_dir/ams/ams
5 In the login window, enter the following parameters:
Server: the hostname or IP address of the 5520 AMS application server

User: admin
Password: admin
Result: A window opens, prompting you to change the password.
6 Enter the default administrator password, enter and confirm the new password,
and click Finish.
Result: The 5520 AMS client establishes a connection with the site and learns the
IP addresses of all application servers. After this connection is established, the
shared client wrapper will be able to log in to any available application server.
12.4 Launching and updating the 5520 AMS client
After the 5520 AMS client is installed, launch the client to download software
updates based on the software plug-ins you have added to the 5520 AMS server.
In a single-user installation, you are automatically prompted to install any available
updates each time you log in. You can also check for updates manually anytime, by
choosing HelpInstall from the 5520 AMS GUI menu. The procedure in this
section describes how to download and apply updates in response to the automatic
prompt at login.
In a shared Red Hat Enterprise s installation, only the user amssys is permitted to
download software updates for the shared client. When logged in to the client, the
amssys user must trigger the updates manually, as described in Procedure 12-6 To
launch and update the 5520 AMS client (p. 12-14). The root user must also update
the permissions to ensure that all users have access to the updates, see Procedure 12-7
To update permissions for the plug-ins directory (p. 12-19).
In a shared Windows installation, only users with write access to the client
installation directory can download software updates.
Users of a shared client are not automatically prompted to download updates, nor can
they use the Help menu to download updates automatically. The HelpInstall and
HelpUpdate menus are permanently disabled for users who are not members of the
amssys group.
Before you proceed:
You need the IP address of the 5520 AMS server. For cluster installations of the
5520 AMS, this can be the IP address of any application server in the cluster, or
the IP address of the presentation server.
The client machine must be able to resolve the hostname of the server machine.
The 5520 AMS software must be installed, activated, and started on the server.
In a cluster setup, ensure that at least one 5520 AMS application server has fully
started. For information on the client login behavior in cluster setups, see the
5520 AMS User Guide.
The 5520 AMS client must be installed.
The software plug-ins must be installed and activated on the 5520 AMS server.
For a shared installation in Windows, you must have write access to the directory
where the client is installed.
Note 1 When you launch the 5520 AMS client, if the Graphical
View is opened by default, or opened immediately after launching the
client, an exception appears. To avoid this exception, perform the
following steps:
Open Internet Explorer.
From the Tools menu, select Internet Options.
Select the Advanced tab in the Internet Options dialog.
Select the Disable Script Debugging (Other) check box.
Note 2 In Windows client, when you launch the 5520 AMS client
from the absolute path after making the SSL changes, modify the
following properties in amsclient.ini:
Djavax.net.ssl.trustStore=<ams-client-installation-path>/keystore,
where ams-client-installation-path is the full path of the 5520
AMS client.
Djavax.net.ssl.keystore=<ams-client-installation-path>/keystore,
where ams-client-installation-path is the full path of the 5520
AMS client.
Procedure 12-6 To launch and update the 5520 AMS client
Use this procedure to launch and update the 5520 AMS client.
1 Log in to the workstation on which you need to launch the 5520 AMS client.
2 Navigate to the folder in which you installed the 5520 AMS client application.
3 To start the client in the Windows operating system, perform one of the following
steps:
Double-click the client application, amsclient.exe.

From the Windows command prompt, type one of the following commands:
To log in without a startup option, type:
path/amsclient.exe
To allow multiple logins to the 5520 AMS client, type:
path/amsclient.exe -allowmultiple
To specify a server to log in to, type:
path/amsclient.exe -serverip IP_address
To specify a server to log in to and prevent the Server field in the login
window from being changed, type:
path/amsclient.exe -serverip IP_address

-grayoutserveratlogin
To specify an object to navigate to in the GUI, type:
path/amsclient.exe -objectid object
To disable automatic updates in the client, type:
path/amsclient.exe -noclientupdates
where:
path is the path to the 5520 AMS client installation directory; for example, C:\Program
Files\ams.
IP_address is the IP address of the server.
object is the identifier of an object in the Network Tree; for example,
ams:application.nelist:group:/name=2. This navigates to a group with the name 2
immediately after you log in. When the filter is applied, only groups with matching NEs are
shown in the Network Tree.
Result: The 5520 AMS client opens and displays a login window.
4 To start the client application in the Red Hat Enterprise Linux operating system,
type:
client_dir/ams/amsclient
where:
client_dir is the installation directory you chose when you installed the client.
Note If you need to start the client in the background, type:
client_dir/ams/ams
5 In the login window, enter the following parameters:
Server: the hostname or IP address of the 5520 AMS application server

User: admin
Password: admin
Result: A window opens, prompting you to change the password.
6 Enter the default administrator password, enter and confirm the new password,
and click Finish.
Result: The 5520 AMS client establishes a connection with the server.
If you did not install plug-ins on the server, the client does not require an
update and the procedure is complete.
Continue to step 8 (p. 12-16).
If this is a single-user installation or a shared installation on Windows, you will

be prompted automatically to install updates. Go to step 9 (p. 12-17).
If this is a shared installation on Red Hat Enterprise Linux, only members of the
amssys user group can install software updates, and you must begin the process
manually. To install the available software updates, perform the following
steps:
i In the 5520 AMS GUI menu, choose HelpInstall.
Result: The Install/Update window opens.
ii Click Search for new features to install, and click Next.
Result: The Install window opens.
iii Go to step 10 (p. 12-17).
Result: An Updates Found window opens, indicating that software updates are
available. The window prompts you to download the updates to your copy of the
5520 AMS client.
To download all available updates, click Yes. Go to step 11 (p. 12-17).

Select the Select Plugins check box and click Yes to select from among the
available updates.
Result: An Updates window opens. Go to step 10 (p. 12-17).
In the Updates window, a collapsed object tree contains the available updates.
10 Perform the following steps.
i Expand the tree to reveal all update objects.
ii Select the check box beside each update you need to install.
As you select each update, the 5520 AMS client checks the compatibility of
the update with your current installation. If an error occurs when selecting
an update, click Error Details to see more information about the source of
the problem.
iii Click Next.
Result: The Feature License window appears, displaying the terms of the license
and an option to accept or decline these terms.
11 To accept the licensing terms, choose I accept the terms in the license
agreements and click Next.
Result: The Install window summarizes the features to be installed, including for
each feature:
Feature name
Feature version
Size of the installed feature
Direction where the feature will be installed
12 Perform one of the following procedures:
To install the features in the default directory, go to step 13 (p. 12-18).

Note Alcatel-Lucent recommends that you use the default
installation directory.
Change the installation directory for a plug-in:
i Select the plug-in from the list.
ii Click Change Directory.
Result: The New Update Site window appears.
iii To select a configured location, or add a new location, click Add New
and navigate to the location in the resulting navigation window.
iv Repeat steps i (p. 12-18) through iii (p. 12-18) for each plug-in whose
installation directory you need to change.
v Click OK in the New Update Site window.
Result: The window closes.
13 Click Finish.
Result: The VerificationFeature Verification window opens.
If you selected multiple features in step 10 (p. 12-17), click Install All.
If you selected only one feature or need to confirm each feature that you
install, click Install.
Result: The Install/Update confirmation window reopens, recommending that you

restart the client to apply the changes.
To install the features and close and start the client, click Yes.
Result: The client feature update installation is complete.
To cancel the feature installation, click No.
If you need to apply changes without restarting the client, click Apply
Changes.
Note Some feature updates may not appear properly until you
restart the client.
Procedure 12-7 To update permissions for the plug-ins directory
Before you proceed, you need root access to the server where the 5520 AMS client is
installed.
1 Log in as root to the server where the 5520 AMS client is installed.
2 To change to the directory where the client is installed, type:
cd client_dir/ams
where:
3 To run the script to update the permissions, type:
./chmodpluginsdir
Result: The script displays a confirmation:
Done.
The permissions are updated and all users can access the updates.
Procedure 12-8 To make the site name visible in the GUI login
window when multiple users access the shared 5520 AMS client in
Red Hat Enterprise Linux
1 Log in to the 5520 AMS server with the first created user.
2 Start the 5520 AMS client application in the Red Hat Enterprise operating system.
Type:
client_dir/ams/amsclient
where:
3 Log in to the 5520 AMS client using the site name.
4 When the login is successful using the site name, modify the permissions on the
siteconfig.xml file in the configuration directory. In the 5520 AMS server, type:
chmod 666 client_dir/configuration/siteconfig.xml
where:
Result: In the GUI login window, the site name is visible in the drop-down list to
all other users.
Procedure 12-9 To display hours in the 0 to 24 convention in the

5520 AMS client
Perform this procedure on Windows or Red Hat Enterprise Linux systems.
1 Log in to the server where the 5520 AMS client is installed.
2 Navigate to the configuration directory. Type:
cd client_dir/ams/configuration
where:
client_dir is the directory where the 5520 AMS client is installed.
3 Edit the config.ini file.
On Windows systems, open the config.ini file.

The config.ini file is located in the following path:
client_dir\ams\configuration
where client_dir is the directory where the 5520 AMS client is installed.
On Red Hat Enterprise Linux systems, open the config.ini file and type:
vi config.ini
4 Add the following lines:
osgi.nl=en
country.code=GB
6 Restart the 5520 AMS client.
Result: In the 5520 AMS client, the hours are displayed in the 0 to 24 convention.
Note The changes to the config.ini file will be applied only when the
5520 AMS client is restarted.
12.5 Changing passwords for default users in the 5520 AMS GUI
Use this procedure if you changed the passwords of the amsftp or amssftp users in
the 5520 AMS server by performing Procedure 6-9 To change the password of a
default user on the 5520 AMS application server (p. 6-39).
Procedure 12-10 To change a default user password in the 5520 AMS

GUI
Caution Passwords for the amsftp and amssftp users cannot include
the @ or : symbols.
1 Log in to the 5520 AMS client as an administrator.
2 In the Administration Tree, choose one of the following options:
EMS AdministrationConfigurationEMS/NE ProtocolsFile Server

CredentialsSFTP User
EMS AdministrationConfigurationEMS/NE ProtocolsFile Server
CredentialsFTP User
Result: The Object Details view opens.
3 Enter the password you configured on the 5520 AMS server and click the Apply
icon ( ) to save the change.
12.6 Adding a license to the 5520 AMS
Your license from Alcatel-Lucent includes a license key, in the form of a long string
of alphanumeric characters. The license key encodes the set of features you have
licensed, the period of the license, and for some objects the quantity to which your
license entitles you.
Use any of the following procedures to add a license key. See Table 12-2 Install the
5520 AMS client (p. 12-4) for the context in which to perform this procedure.
Before you proceed:
The 5520 AMS server must be installed, activated, and started.
Any software plug-ins must be installed and activated.
At least one copy of the 5520 AMS client application must be installed.
In a cluster installation, your license must include the host ID of every server that
is part of the cluster.
In a cluster installation, each server must be able to resolve the host names of all
other nodes in the cluster, either using DNS or by adding the list of all hosts to the
/etc/hosts file on each server.
Licenses can be installed using the Create License wizard of the GUI by:
uploading valid .tar, .pdf, or .txt license files in the License File field, or
copying a valid license key in the License Key field
If both License File and License Key fields are populated in the Create License
wizard of the GUI, both licenses will be validated and installed. See Procedure 12-11
To add a license key from the 5520 AMS GUI (p. 12-22).
Licenses can also be installed from valid .tar, .pdf, or .txt license files in the 5520
AMS server using the ams_install_license.sh script. See Procedure 12-12 To add a
license key from the 5520 AMS server (p. 12-23).
You can add a license for objects that are not already in your license list. If you add
a license key that includes an object for which you are already licensed, you will
receive an error message.
Note 1 A .tar file can contain multiple .pdf or .txt license files,
which are uncompressed after uploading to the server. The individual
license files are then validated before installation.
Note 2 A .txt file or .pdf file can contain multiple licenses.
In a .txt file, each license is presented in the following format: Key:

Value, where Key identifies the application or component to which
the license applies, and Value is the license key. Each license is
separated by the delimiter #----.
In a .pdf file, multiple licenses are presented in a table with two
columns. The first column identifies the application or component
to which the license applies, and the second column includes the
license key.
Procedure 12-11 To add a license key from the 5520 AMS GUI
1 In the Administration Tree, choose EMS AdministrationLicense.
2 Right-click License and choose CreateLicense.
Result: The Create License window opens.
Copy the license key from the locally stored license file and paste it in the
License Key field. Optionally, enter the description of the license in the
Description field.
Browse and select the license file (in .txt, .pdf, or .tar file format) in the
License File field. The default option is .txt.
4 Click Finish to verify and install the licenses.
Result: The licenses are verified and installed. In case an error occurs, no license
will be installed. See Table 12-4 License installation error scenarios (p. 12-23) for
the scenarios in which installation of licenses may fail.
5 Close and restart the 5520 AMS client for the newly installed licenses to take
effect.
Procedure 12-12 To add a license key from the 5520 AMS server
1 Log in to the 5520 AMS server as amssys or root.
2 Transfer the license files to be installed to a temporary directory in the 5520 AMS
server.
3 Execute one of the following command options, as applicable:
Table 12-3 License installation from the 5520 AMS server
To install licenses Command options Command example
From a single file ams_install_license.sh [-force] ams_install_license.sh -force /var/opt/tmp/license/license.txt

<full path and name of license
file>
From multiple files ams_install_license.sh [-force] ams_install_license.sh -force /var/opt/tmp/license/license.txt,

<full path and name of license /var/opt/tmp/license/license.tar, /var/opt/tmp/license/license.pdf
file1>, <full path and name of
license file2>, <full path and
name of license filen>
From multiple files ams_install_license.sh [-force] ams_install_license.sh -force /var/opt/tmp/license/*.pdf

of the same file <full path to license file>/*.<file or
format supported by extension>
wildcard file ams_install_license.sh -force /var/opt/tmp/license/9.4*.txt
selection pattern
Notes
(1) When you use the -force option, the script forcefully installs all licenses from the license file(s).
If the license exists, then the existing license is replaced by the new license.
Result: The licenses are verified and installed. In case an error occurs, no license
will be installed. See Table 12-4 License installation error scenarios (p. 12-23) for
the scenarios in which installation of licenses may fail.
License installation error scenarios

Table 12-4 License installation error scenarios (p. 12-23) lists the scenarios in which
a license installation may fail.
Table 12-4 License installation error scenarios
Error Scenario The license installation fails with the error message:
If an error occurs while processing Error processing license [txt/pdf/tar] file {file name}
the license file
If no license is found or the license License file {file name} corrupted or doesn't contain license
file is corrupted keys
If a file format other than .pdf, The uploaded license file format { file name } is not support-
.txt, or.tar is uploaded ed
Error Scenario The license installation fails with the error message:
If the path and filename entered in The uploaded license file { file name } doesn't exist
the License File field is incorrect
If you install a duplicate license License Key(s) {keys that are already present in the system}
already exists
If you install a license which has Expired license

expired
If you install a license the host ID of The hostid in the license does not match the hostid of the
which does not match the host ID server(s) {host id present in the license key}
of the 5520 AMS server
Migrating to the 5520 AMS, Release 9.4
13 Migrating to the 5520 AMS, Release 9.4
14 Migration scenarios and associated task list
15 Pre-migration tasks
16 Migration tasks
17 Post-migration tasks

13 Migrating to the 5520 AMS, Release
9.4
13.1 Migration overview 13-2
13.2 Installing the 5520 AMS, Release 9.4 on the same server running
an earlier 5520 AMS release 13-5
13.3 Migrating NEs 13-6
13.4 Migration dependencies of the data migration script 13-6
13.5 Updating software plug-ins to a new version 13-7
13.6 External TL1 Gateway migration 13-7
13.7 Migration with a customized keystore 13-8
13.8 Migrating templates 13-9
13.9 Migrating licenses 13-9
13.1 Migration overview
You can migrate a simplex installation, a cluster installation or a geographically

redundant installation to the 5520 AMS, Release 9.4 from the supported 5520 AMS
releases. Table 13-1 Supported migration path and data migration strategy (p. 13-2)
lists the supported migration paths, and the data migration strategy.
Note If you are migrating from one patch release to another patch
release within the same 5520 AMS release, then you do not need to
migrate the data.
Table 13-1 Supported migration path and data migration strategy
Migration path Data migration strategy
From To
5520 AMS, Release 9.2.30 5520 AMS, Release 9.4 Data is migrated:
5520 AMS, Release 9.3.10

By copying the data files from a
backup file of the earlier 5520 AMS
release to the current active release
directories, or
By copying the data files from the
earlier 5520 AMS release to the
current active release directories.
Tool used for migration: The

ams_copy_datafiles script
This migration strategy supports in-place
and out-of place migration.
In this strategy, the 5529 Enhanced
Applications and plug-ins, and the
5520 AMS NE plug-ins that need to be
migrated must be installed and activated
in the current active release before the
script is executed for data migration.
Caution 1 For the migration to be successful ensure that the same

set of 5529 Enhanced Applications and NE plug-ins are migrated to
the current 5520 AMS release.
Caution 2 Do not stop or restart the server when the migration is
in progress. If the server is stopped, then execute the
ams_copy_datafiles script all over again to copy the data of the earlier
5520 AMS release from the backup file to the 5520 AMS, Release
9.4.
Note 1 On Red Hat Enterprise Linux systems, when migrating to

the 5520 AMS, Release 9.4, the 5520 AMS, by default, uses root SSH
sessions requiring superuser permisssions to execute commands.
Note 2 Migrating to the 5520 AMS, Release 9.4 volume contains
references to the earlier 5520 AMS release. The earlier 5520 AMS
release may refer to the 5520 AMS, Release 9.2.30, or 9.3.10,
depending on the earlier release from which data is migrated to the
5520 AMS, Release 9.4.
In-place migration
In-place migration refers to migration to a new release of 5520 AMS on the same
machine where the earlier 5520 AMS release is installed. The new release of the
5520 AMS is installed and activated on the same server. Data files of the earlier
release are copied to the current active release from an earlier release directory that
exists on the same machine. You can perform the in-place migration in the following
two ways:
Automated in-place migration using ams_migrate script
Manual in-place migration
Automated in-place migration

The ams_migrate script can be used to perform 5520 AMS in-place migration on
simplex, cluster, or geographically redundant systems. For seamless migration, the
script:
Performs the pre-migration health check
Distributes and installs the new release software
Takes the previous release backup
Activates the new release
Copies the data
Performs the migration and starts the servers
Configures the license
Configures the SSL - if the SSL was configured in the source release
Rolls back to the previous release if the migration is unsuccessful
The ams_migration script also allows the option to select individual menu options.
For example, the user can select options:
1 Distribute and install software
2 AMS backup
To selectively choose the options :
At the choose prompt, type the options that you want to deselect, and press . You
must choose the options in the order they present and not randomly.
Then, again at the choose prompt, type x and press .
The selected steps are executed and then the command execution is terminated. If
you try to execute the --migrate command again, then the following error is
displayed:
The target release server already exists.
To access the further steps in the migration process, the user must execute the
ams_migrate script from the source release software bin directory.
For the detailed sequence of automated in-place migration for simplex, cluster or
geographically redundant site installations, see Chapter 14 Migration scenarios and
associated task list (p. 14-1).
For the detailed execution of the script, see Procedure 15-2 To install the 5520 AMS
solution for migration (p. 15-4).
Note If the automated in-place migration is unsuccessful, navigate

to the software bin directory of the new release (Release 9.4) and
execute the following command to resume the migration:
ams_migrate
All the actions and messages during the script execution are captured in a log file
named ams_migration.log.
Manual in-place migration

You can also perform each migration activity manually. For detailed sequence of
manual in-place migration for simplex, cluster, or geographically redundant
installations, see Appendix B.2 Manual in-place migration associated task list (p.
B-2). For information on the manual in-place migration procedure, see Procedure
B-1 To install the 5520 AMS solution for manual in-place migration (p. B-9)
Out-of-place migration
Out-of-place migration refers to migration to a new release of 5520 AMS on a server
which is different from the server where the earlier 5520 AMS release is installed.
1 The new release of the 5520 AMS is installed and activated on a new server.
2 Data files of the earlier 5520 AMS release are saved to a backup file.
3 This backup file is transferred from the server of the earlier 5520 AMS release
to the server containing the current active release.
4 The data from the backup file is then copied to the current active release
directory.
For the detailed sequence of out-of-place migration for simplex server, cluster or
geographically redundant site installation, see Chapter 14 Migration scenarios and
associated task list (p. 14-1).
Migration support between operating systems and architectures

Table 13-2 5520 AMS migration support between operating systems and
architectures, in the 5520 AMS Release 9.4 (p. 13-5) lists the 5520 AMS migration
support between operating systems and architectures, in the 5520 AMS, Release
9.4.
Table 13-2 5520 AMS migration support between operating systems and architectures,
in the 5520 AMS Release 9.4
From 5520 AMS, Operating System and Architecture To 5520 AMS, Release 9.4
Release
9.2.30 or 9.3.10 Solaris x86 Red Hat Enterprise Linux
Solaris SPARC Solaris x86
Solaris SPARC Red Hat Enterprise Linux
Note 1 To migrate the 5520 AMS, Release 9.4 from the Solaris
operating system to the Red Hat Enterprise Linux operating system,
perform an out-of-place migration.
Note 2 Alcatel-Lucent recommends to use ams _copy_datafiles
script to migrate data within the same release for different operating
systems.
For information on copying data files, see Section 16.7 Copying data
files from the earlier 5520 AMS release to the 5520 AMS, Release 9.4
(p. 16-11)
13.2 Installing the 5520 AMS, Release 9.4 on the same server
running an earlier 5520 AMS release
You can install the 5520 AMS, Release 9.4 on the same server hosting the earlier
5520 AMS release if you are performing a manual or automated in-place migration.
However, both applications cannot be running at the same time. You must stop the
processes for one before starting them for the other.
If you install the 5520 AMS, Release 9.4 on a server that already has a 5520 AMS
server running, the server will save software, shared data, and local data in the same
locations as the existing installation. You will not be prompted to choose the
locations.
13.3 Migrating NEs
All NEs will be migrated along with their supervision state. The NEs which do not
have a 5520 AMS plug-in for Release 9.4 will be displayed with an invalid NE
Type/Release in the 5520 AMS GUI.
Note You can delete the NEs with an invalid NE Type/Release

from the GUI. See the 5520 AMS User Guide.
If any of the NEs that you migrate has an xVPS agent, Alcatel-Lucent recommends
that you verify that the VLAN bridges are intact after completing the migration.
Note When migrating from the earlier 5520 AMS release to the
5520 AMS, Release 9.4, it can take up to 30 minutes after startup of
the Release 9.4, when the 5520 AMS application can receive traps
from the managed network elements.
13.4 Migration dependencies of the data migration script
This section lists the migration dependencies for the data migration script.
Data not migrated from the earlier 5520 AMS release

Release 9.4 (p. 13-6) lists the data not migrated from the earlier 5520 AMS release
to the 5520 AMS, Release 9.4.
Before performing a migration, record any data listed in Table 13-3 Data not
migrated from the earlier 5520 AMS release to the 5520 AMS, Release 9.4 (p. 13-6)
that you plan to reconfigure in the 5520 AMS, Release 9.4. Back up any files
containing data listed in Table 13-3 Data not migrated from the earlier 5520 AMS
release to the 5520 AMS, Release 9.4 (p. 13-6), and that you need to preserve
following the migration, before uninstalling the earlier 5520 AMS release.
Release 9.4
Data Comments
Cluster switchover script The switchover_hook.sh script is not migrated.
5520 AMS and 5529 Enhanced The 5520 AMS and 5529 Enhanced Applications licenses are not
Applications Licenses migrated.
13.5 Updating software plug-ins to a new version
Updates will be available periodically for the installed software plug-ins comprising
5520 AMS NE plug-ins, and 5529 Enhanced Applications and plug-ins. Table 13-4
Updating a software plug-in to a new version (p. 13-7) lists the tasks to update a
software plug-in to a new version.
Table 13-4 Updating a software plug-in to a new version
Task # Task See
1 Back up the currently installed 5520 AMS. 5520 AMS Administrator Guide
command.
command.
3 Deactivate and uninstall the existing software plug-in. Procedure 6-6 To deactivate the 5520 AMS
Uninstalling the existing software plug-in is optional. In case of NE plug-ins, 5529 Enhanced Applications
issues during upgrade, you can roll back to the previous software and plug-ins, and patches and emergency
plug-in, if it is not uninstalled. fixes together or individually (p. 6-32) to
deactivate the software plug-in.
Procedure 18-1 To uninstall the 5520 AMS
fixes together or individually (p. 18-6) to
uninstall the software plug-in.
4 Install and activate the new software plug-in. Procedure 6-4 To install the 5520 AMS NE
plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes
together or individually (p. 6-27) or
solution components (p. 6-35)
command.
command.
You have completed the set of tasks required to update a software plug-in to a new version.
13.6 External TL1 Gateway migration
Any External TL1 Gateways imported from the earlier 5520 AMS release will be
associated with the current active Site object in the 5520 AMS, Release 9.4.
The successful import of the gateway and the association of imported NEs depends
on the following criteria in the 5520 AMS, Release 9.4:
Whether the Use Single External TL1 Gateway Server check box has been
selected in the Site object. When this check box is selected, only one External
TL1 Gateway server object can be created for the Site.
For more information about site settings, see the 5520 AMS Administrator Guide.
Whether an External TL1 Gateway already exists.
If an External TL1 Gateway already exists, whether it has the same name or IP
address as the gateway being imported.
Table 13-5 External TL1 Gateway migration behavior from the earlier 5520 AMS
release to the 5520 AMS, Release 9.4 (p. 13-8) outlines the behavior after import
according to each criterion.
Table 13-5 External TL1 Gateway migration behavior from the earlier 5520 AMS release
to the 5520 AMS, Release 9.4
Use Single External TL1 External TL1 External TL1 No External TL1
Gateway Server check box Gateway exists Gateway exists Gateway exists
with the same with a different
name or IP name and IP
address address
Selected Gateway import Gateway import The External TL1

fails fails Gateway is
NEs imported are NEs imported are imported.
not associated with not associated NEs imported are
an External TL1 with an External not associated with
Gateway. TL1 Gateway. an External TL1
Gateway.
Unselected The External TL1 The External TL1 The External TL1
Gateway is Gateway is Gateway is
imported. imported. imported.
Association Association Association
between imported between imported between imported
NEs and the NEs and the NEs and the
External TL1 External TL1 External TL1
Gateway is Gateway is Gateway is
maintained. maintained. maintained.
Migrating an External TL1 Gateway in a cluster

If you have integrated the External TL1 Gateway with a cluster, unconfigure the
integration before migrating the 5520 AMS and reconfigure it after the migration.
See the 5520 AMS Administrator Guide for more information.
13.7 Migration with a customized keystore
If you enabled a customized keystore with the earlier 5520 AMS release, you can
continue to use the same keystore with the 5520 AMS, Release 9.4.
Disable SSL during the migration and enable it again after the migration is
completed. This will ensure that the customized keystore is included with the client
download file.
For more information about managing a customized keystore, see the SSL chapter in
the 5520 AMS Administrator Guide.
13.8 Migrating templates
Only the NE-specific template data for the installed NE plugs will be migrated. The
NE-specific template data for NE plugs that are not installed will not be migrated.
13.9 Migrating licenses
When migrating from the earlier 5520 AMS release, the 5520 AMS and 5529
Enhanced Applications licenses are not migrated.
When migrating from the earlier 5520 AMS release to the 5520 AMS, Release 9.4,
only the ISAM feature licenses are migrated.
14 Migration scenarios and associated
task list
14.1 Overview of the migration scenarios 14-2
14.2 Automated in-place migration from an earlier 5520 AMS release

to the 5520 AMS, Release 9.4 14-2
14.3 Out-of-place migration from an earlier 5520 AMS release to the

5520 AMS, Release 9.4 14-4
14.4 Checking the consistency of alarm rules after migration 14-9
14.1 Overview of the migration scenarios
This chapter describes the following migration scenarios and the associated task list
when migrating from an earlier 5520 AMS release to the 5520 AMS, Release 9.4:
Automated in-place migration and associated tasks list for simplex, cluster, or
geographically redundant installation from an earlier 5520 AMS release to the
5520 AMS release 9.4.
Out-of-place migration and associated tasks list for simplex, cluster, or
geographically redundant installation from an earlier 5520 AMS release to the
5520 AMS 9.4.
Before you proceed to perform the migration tasks, you need root or amssys access
to all servers.
Based on the migration strategy, Table 14-1 Migration path and data migration
strategy for automated in-place and out-of-place migrations (p. 14-2) lists the task
tables for automated in-place migration and out-of-place migration of simplex,
cluster, or geographically redundant installation to the 5520 AMS, Release 9.4.
Table 14-1 Migration path and data migration strategy for automated in-place and
out-of-place migrations
Migration path Migration strategy See
From To
(5520 AMS,
Release)
5520 AMS, 5520 AMS, In-place migration Section 14.2 Automated

Release 9.2.30 Release 9.4 in-place migration from an
5520 AMS, earlier 5520 AMS release to the
Release 9.3.10 5520 AMS, Release 9.4 (p.
14-2)
Out-of-place migration Section 14.3 Out-of-place

migration from an earlier 5520
AMS release to the 5520 AMS,
Release 9.4 (p. 14-4)
14.2 Automated in-place migration from an earlier 5520 AMS

release to the 5520 AMS, Release 9.4
This section provides the steps to perform automated in-place migration for a
simplex, cluster, or geographically redundant installation from an earlier 5520 AMS
release to 5520 AMS 9.4 release, see the tasks listed in the Table 14-3 Automated
in-place migration for simplex, cluster, and geographical redundant installations (p.
14-3). To perform an in-place migration manually, see Appendix B Manual in-place
migration procedures (p. B-1).
Table 14-2 Automated in-place migration path and data migration strategy
Migration path See
From To
5520 AMS, Release 5520 AMS, Release Table 14-3 Automated in-place
9.2.30 9.4 migration for simplex, cluster,
5520 AMS, Release and geographical redundant
9.3.10 installations (p. 14-3)
Table 14-3 Automated in-place migration for simplex, cluster, and geographical redundant installations
Task # Task See
Pre-migration tasks (non-service affecting)
1 Ensure that the previous release of the 5520 AMS is existing and running. -
2 Download and save the required license keys to a temporary directory Procedure 12-12 To add a license key
in the 5520 AMS server. from the 5520 AMS server (p. 12-23)
3 Transfer the 5520 AMS, Release 9.4 software to the 5520 AMS server. Section 15.2 Transferring the
5520 AMS software to the 5520 AMS
servers (p. 15-2)
4 Check and update the hostid. Section 15.4 Generating a hostid (p.
15-3)
5 Install the 5520 AMS, Release 9.4 software to the 5520 AMS server. Procedure 15-2 To install the
Note- The 5520 AMS, Release 9.4 software needs to be transferred to a 5520 AMS solution for migration (p.
single server in the cluster. The ams_migrate script enables automatic 15-4)
distribution and installation of the software to other servers in the
cluster.
Migration tasks (service affecting)
6 Execute the ams_migrate script. Section 15.5 Installing the 5520 AMS,
Release 9.4 for migration (p. 15-4)
7 Rollback Section 15.5 Installing the 5520 AMS,

In the event of an unsuccessful migration, the ams_migrate script will Release 9.4 for migration (p. 15-4)
roll back to the previous active software version on all servers and start
the servers.
Post-migration tasks (non-service affecting)
8 Install the 5520 AMS, Release 9.4 client. Section 16.10 Installing the 5520 AMS,
Release 9.4 client (p. 16-20)
9 Launch the 5520 AMS, Release 9.4 client. Section 16.11 Launching the
5520 AMS, Release 9.4 client (p.
16-21)
10 (Optional) Import GUI settings. Section 17.3 Importing GUI settings

(p. 17-2)
11 (Optional) If the Release 9.4 is successfully operational, then uninstall Section Uninstalling the earlier 5520
the earlier 5520 AMS release. AMS release (p. B-39)
You have completed the set of automated in-place migration tasks.
14.3 Out-of-place migration from an earlier 5520 AMS release to

the 5520 AMS, Release 9.4
Based on the migration strategy, Table 14-4 Out-of-place migration path and data
migration strategy (p. 14-4) lists the task tables for an out-of-place migration of a
simplex, cluster, and geographically installation to the 5520 AMS, Release 9.4.
Table 14-4 Out-of-place migration path and data migration strategy
Migration path See
From To
5520 AMS, Release 5520 AMS, Release Table 14-5 Simplex migration -
9.2.30 9.4 Out-of-place (p. 14-4)
5520 AMS, Release
Table 14-6 Cluster migration -
9.3.10
Out-of-place (p. 14-5)
Table 14-7 Geographically

redundant migration -
Out-of-place (p. 14-7)
Out-of-place simplex migration

Table 14-5 Simplex migration - Out-of-place (p. 14-4) lists the tasks to perform an
out-of-place migration from an earlier 5520 AMS release to the 5520 AMS, Release
9.4, if your original site was configured as a simplex setup.
Table 14-5 Simplex migration - Out-of-place
Task # Task See

Pre-migration tasks
servers (p. 15-2)
15-3)
3 Install and activate the 5520 AMS Release 9.4 on a new 5520 AMS server. Section 15.5 Installing the 5520 AMS,
Release 9.4 for migration (p. 15-4)
4 Install and activate the required 5520 AMS NE plug-in Release 9.4 Section 15.6 Installing the 5520 AMS
versions, and 5529 Enhanced Applications and plug-in Release 9.4 solution software components for
versions that you are migrating from the earlier 5520 AMS release. migration (p. 15-21)
Caution - If the 5520 AMS NE plug-ins, 5529 Enhanced

Applications and plug-ins used before the migration are
not installed with the 5520 AMS Release 9.4, their
persistency will not be migrated. These plug-ins cannot be
migrated later.
Migration tasks
5 (Optional) Migrate the switchover script to the 5520 AMS, Release 9.4 Section 16.2 Migrating the switchover
server. script (p. 16-2)
(1 of 2)
Task # Task See
6 If you are using a customized keystore, enable SSL. Section 16.3 Enabling SSL (p. 16-4)
7 Back up the database of the earlier 5520 AMS release. Section 16.5 Backing up the 5520 AMS
database for an out-of-place
migration (p. 16-9)
8 Transfer the backup file of the earlier 5520 AMS release to the Section 16.6 Transfer the backup file
5520 AMS, Release 9.4 server. of 5520 AMS database to the new
server (p. 16-10)
9 Copy the data of the earlier 5520 AMS release from the backup file to Section 16.7 Copying data files from
the 5520 AMS Release 9.4 directories using the ams_copy_datafiles the earlier 5520 AMS release to the
script. 5520 AMS, Release 9.4 (p. 16-11)
10 Start the 5520 AMS, Release 9.4 server. Section 16.8 Starting the 5520 AMS,
Release 9.4 servers (p. 16-16)
11 Add licenses for the 5520 AMS installation using the script. Section 16.9 Adding licenses to the
5520 AMS, Release 9.4 installation (p.
16-20)
16-21)
14 If you are migrating ONT SIP data from 7342 ISAM FTTU R4.9 or earlier, Section 16.12 Updating the
update the anonymous FTP user path. anonymous FTP user path (p. 16-21)
Post-migration tasks

(p. 17-2)
16 (Optional) Delete the former site of the earlier 5520 AMS release. Section 17.4 Deleting the former site
of the earlier 5520 AMS release (p.
17-4)
You have completed the set of migration tasks.
(2 of 2)
Out-of-place cluster migration

Table 14-6 Cluster migration - Out-of-place (p. 14-5) describes the tasks to perform
an out-of-place migration from the earlier 5520 AMS release to the 5520 AMS,
Release 9.4, if your original site was configured as a cluster.
Table 14-6 Cluster migration - Out-of-place
Task # Task See
Pre-migration tasks
1 Transfer the 5520 AMS, Release 9.4 software to the 5520 AMS servers in Section 15.2 Transferring the
the cluster. 5520 AMS software to the 5520 AMS
servers (p. 15-2)
15-3)
(1 of 3)
Task # Task See
3 Perform the following steps to install and activate the 5520 AMS, Section 15.5 Installing the 5520 AMS,
Release 9.4 on new hardware: Release 9.4 for migration (p. 15-4)
Install and activate the preferred data server.
Install and activate the non-preferred data server, if your cluster
includes one.
Install and activate the dedicated 5520 AMS application server, if
your cluster includes one.
Install and activate any additional dedicated 5520 AMS application
servers that will be part of your cluster.
Install and activate the arbiter server, if your cluster includes one.

Applications and plug-ins used before the migration are not
installed with the 5520 AMS Release 9.4, their persistency
will not be migrated. These plug-ins cannot be migrated
later.
Migration tasks
5 (Optional) Migrate the switchover script. Section 16.2 Migrating the switchover
script (p. 16-2)
migration (p. 16-9)
5520 AMS, Release 9.4 servers. of 5520 AMS database to the new
server (p. 16-10)
the 5520 AMS Release 9.4 preferred data servers using the the earlier 5520 AMS release to the
ams_copy_datafiles script. 5520 AMS, Release 9.4 (p. 16-11)
10 Start the following 5520 AMS, Release 9.4 servers (in the following Section 16.8 Starting the 5520 AMS,
order): Release 9.4 servers (p. 16-16)
Arbiter server, if applicable.
Preferred data server.
One of the application servers.
The application server that is started first becomes the master

application server.
Starting the application server triggers the migration.
11 Ensure that the migration is complete, using the ams_server status Section 16.8 Starting the 5520 AMS,
command. Release 9.4 servers (p. 16-16)
Non-preferred data server.
The remaining application servers.
13 Add licenses for the 5520 AMS installation using the script. Section 16.9 Adding licenses to the
16-20)
(2 of 3)
Task # Task See
16-21)
(p. 17-2)
18 (Optional) Delete the former site of the earlier 5520 AMS release. Section 17.4 Deleting the former site
of the earlier 5520 AMS release (p.
17-4)
(3 of 3)
Out-of-place geographically redundant migration

Table 14-7 Geographically redundant migration - Out-of-place (p. 14-7) describes
the tasks to perform an out-of-place migration from an earlier 5520 AMS release to
the 5520 AMS, Release 9.4, if your original site was configured as a geographically
redundant setup.
Table 14-7 Geographically redundant migration - Out-of-place
Task # Task See

Pre-migration tasks
the geographically redundant site. 5520 AMS software to the 5520 AMS
servers (p. 15-2)
15-3)
3 Perform the following steps on new active and standby sites to install Section 15.5 Installing the 5520 AMS,
and activate the 5520 AMS, Release 9.4: Release 9.4 for migration (p. 15-4)
Install and activate the preferred data server.
Install and activate the non-preferred data server, if your cluster
includes one.
Install and activate the dedicated 5520 AMS application server, if
your cluster includes one.
Install and activate any additional dedicated 5520 AMS application
servers that will be part of your cluster.
Install and activate the arbiter server, if your cluster includes one.

later.
Migration tasks
(1 of 2)
Task # Task See
5 (Optional) Migrate the switchover script. Section 16.2 Migrating the switchover
script (p. 16-2)
7 Enable geographic redundancy. Section 16.4 Enabling geographic

migration (p. 16-9)
5520 AMS, Release 9.4 servers in the active site. of 5520 AMS database to the new
server (p. 16-10)
the 5520 AMS, Release 9.4 preferred data server at the active site using the earlier 5520 AMS release to the
the ams_copy_datafiles script. 5520 AMS, Release 9.4 (p. 16-11)
Arbiter server at the active site, if applicable.
Preferred data server at the active site.
One of the application servers at the active site.

application server.
12 Ensure that the migration is complete, using the ams_server status Section 16.8 Starting the 5520 AMS,
command. Release 9.4 servers (p. 16-16)
Non-preferred data server at the active site, if applicable.
The remaining application servers at the active site.
Arbiter server at the standby site, if applicable.
Preferred data server at the standby site.
Non-preferred data server at the standby site, if applicable.
Application servers at the standby site.
14 Add licenses for the 5520 AMS installation at the active and standby site Section 16.9 Adding licenses to the
using the script. 5520 AMS, Release 9.4 installation (p.
16-20)
15 Install at least one 5520 AMS, Release 9.4 client. Section 16.10 Installing the 5520 AMS,
16-21)

(p. 17-2)
19 (Optional) Delete the former active and standby sites of the earlier Section 17.4 Deleting the former site
5520 AMS release. of the earlier 5520 AMS release (p.
17-4)
(2 of 2)
14.4 Checking the consistency of alarm rules after migration
If alarm rules are defined, execute the Check All Rules command in the Alarm Rules
view of the 5520 AMS GUI after migrating the 5520 AMS to a new release to check
the consistency of the defined alarm rules. For more information about alarm rules,
see the 5520 AMS Administrator Guide.
15.1 Overview of the pre-migration tasks 15-2
15.2 Transferring the 5520 AMS software to the 5520 AMS

servers 15-2
15.3 Server configuration overview 15-2
15.5 Installing the 5520 AMS, Release 9.4 for migration 15-4
15.6 Installing the 5520 AMS solution software components for

migration 15-21
15.1 Overview of the pre-migration tasks
This chapter describes the tasks that are performed before migration of an earlier
5520 AMS release to the 5520 AMS Release 9.4.
Note The tasks in this chapter are non-service affecting and can be
performed before the maintenance window. However, you must
perform the tasks in this chapter as close to the maintenance window
as possible, and ensure that no database changes are made after
performing the export and backup tasks.
For the complete list of tasks to migrate from an earlier 5520 AMS release to the
5520 AMS, Release 9.4, see Chapter 14 Migration scenarios and associated task list
(p. 14-1).
15.2 Transferring the 5520 AMS software to the 5520 AMS

servers
Pre-requisite: Access to product software packages. See Chapter 5 Downloading

software for the 5520 AMS and 5529 Enhanced Applications (p. 5-1).
Obtain the 5520 AMS, Release 9.4 software file from the Alcatel-Lucent Electronic
Download site and transfer it to the 5520 AMS server or servers in case of a cluster
migration.
The file will be in the format ams-release-operating_system-architecture.tar
where:
release is the release of the 5520 AMS software that you are installing. An
example is ams-9.4.00-999000.
operating_system is solaris for the Solaris operating system, and redhat for the
Red Hat Enterprise Linux operating system.
For information about downloading the 5520 AMS installation file, see Chapter 5
Downloading software for the 5520 AMS and 5529 Enhanced Applications (p. 5-1).
Proceed to: Install the 5520 AMS Release 9.4 on the servers. Depending on the type
of the setup, use the Section 15.5 Installing the 5520 AMS, Release 9.4 for migration
(p. 15-4), to install the 5520 AMS, Release 9.4 for migration.
15.3 Server configuration overview
A cluster or geographically redundant setup can consist of a combination of one or

more of the following servers:
One or more Application servers (A)
One or more Data servers (D)
One or more Application and Data servers (A+D)
An Arbiter server (a), if applicable
For the server definitions, see Chapter 2 Overviews (p. 2-1).
15.4 Generating a hostid
Applies to This section applies to 5520 AMS Release 9.3.10 and

9.4.
You must generate a hostid when migrating to a new 5520 AMS release and before
installing the new the 5520 AMS release during the following scenaris:
When the hostid is 007f0100 or 00000000
When the file etc/hostid does not exist.
Before you proceed, when performing migration on a cluster ensure that the state of
the 5520 AMS cluster is healthy.
Perform the following procedure to generate a hostid.
Procedure 15-1 To generate a hostid

1 To check whether the hostid exists, type:
ls -la /etc/hostid
2 To show hostid, type:
hostid
If the hostid is 007f0100 or 00000000, generate a new hostid. Type:
/sbin/genhostid
If the file /etc/hostid does not exist, update the current hostid to /etc/hostid.
Type:
currentId=`hostid`
a=ècho $currentId | cut -c 7,8`
b=ècho $currentId | cut -c 5,6`
c=ècho $currentId | cut -c 3,4`
d=ècho $currentId | cut -c 1,2`
echo -ne \\x$a\\x$b\\x$c\\x$d > /etc/hostid
Result: The hostid is updated.
15.5 Installing the 5520 AMS, Release 9.4 for migration
Pre-requisite: Transferring the 5520 AMS software to the 5520 AMS servers. See
Section 15.2 Transferring the 5520 AMS software to the 5520 AMS servers (p.
15-2).
For more information on the 5520 AMS software installation and activation
methods, see Section 6.1 Installing the 5520 AMS solution overview (p. 6-2) to
install 5520 AMS server software on a simplex, cluster or geographically redundant
setup, in preparation for migrating to the 5520 AMS, Release 9.4 from an earlier
5520 AMS release.
Before you proceed:
For information on the pre-requisites to migrate 5520 AMS software from an
earlier release to Release 9.4, see Table 6-1 Pre-requisite tasks for installing the
5520 AMS (p. 6-2).
For out-of-place migration:
Ensure that all the servers in a cluster setup are in a healthy state and running.
Ensure that the same set of 5529 Enhanced Applications and NE plug-ins are
migrated to the current 5520 AMS release.
Note You can also install additional 5529 Enhanced Applications
and NE plug-ins in the current 5520 AMS release.
Use the procedure in this section to install the 5520 AMS, Release 9.4 on a simplex,
cluster, or geographically redundant setup, in preparation for migration from an
earlier 5520 AMS release.
Note During migration the 5520 AMS installation files are not
copied to the geographically redundant site. You must enable and
configure the geographic redundancy settings again post migration.
For information on server configurations, see 15.3 Server configuration overview (p.
15-2).
Procedure 15-2 To install the 5520 AMS solution for migration

Migrate all 5520 AMS In the case of automated in-place migration: The migration script displays the following
solution components confirmation:
without a ./amscore.binary_filename.bin --migrate
configuration file Checkin OS and version...
(recommended) where:
amscore.binary_filename.bin is the name of the bin file. OK
For example: [1] Distribute and install
ams--9.4-redhat-x64-12345.bin --migrate software
[2] AMS Backup
[3] Activate new release
[4] Perform data copy
[5] Migrate + full start
[6] Configure license
[7] Configure SSL
8 Rollback
x) Execute
q) Quit
Proceed to step 32 (p. 15-18)
Migrate all 5520 AMS In the case of out-of-place migration: The installation software displays the
solution components following confirmation:
without a ./installation_filename.bin --activate-force
configuration file --includevapsplugs directory_path Checking OS and version ...
(recommended) OK.
where directory_path is the path to the directory containing the VAPs
and/or NE Plugs .bin files. If only a subset of files in a directory need
to be installed, or if the .bin files are stored in different directories,
Checking hostname ... OK
the absolute path and filename of each .bin file needs to be specified.
where: Checking SSH (ssh,
ssh-keygen, ssh-keyscan, scp,
release is the release of the VAP or NE plug-in. An example for is VAP sftp) ...
is app-idm-1.0_9.4-246228.bin and for NE plug-in is
The installer prompts you for the location of
plugin-combo-gpon-4.7-1.0_9.4-156320.bin.
the SSH library:
Migrate only the 5520 In the case of out-of-place migration:
AMS core software Enter the path to the SSH
(excluding other ./installation_filename.bin --activate-force tools [ /usr/bin (default) ]:
solution components)
Proceed to step 4 (p. 15-6).
Migrate all 5520 AMS In the case of out-of-place migration: The migration proceeds based on the
solution components settings saved in the configuration file. The
using a configuration ./installation_filename.bin -c choices saved in the configuration file are
file path_and_filename --activate-force displayed. See Table 15-1 Migration result
--includevapsplugs directory_path (p. 15-16) for the migration result.
where:
./installation_filename.bin -c
path_and_filename --includevapsplugs
directory_path
where:


a new site name.

]?:
If then Result


where:
5520 AMS installer.
Go to step 15 (p. 15-12)

allowed to connect:

Go to step 15 (p. 15-12).
a cluster press .
server):
[2] Data server
[4] Arbiter
Go to step 10 (p. 15-9).
If you need to migrate then Result
A combination of type 3 and The cluster subnet is: Subnet addresses
server where:
press . server.
the subnet address.
If you are migrating then
where:
the IP address.
information:
where:

information
For application server, go to step 12 (p. 15-10)

For combination of application and data server, go to step 13 (p. 15-10)
If you are migrating then

where:

Go to step 13 (p. 15-10)

where:
Go to step 15 (p. 15-12)
name of the server.
Result:
IP address
server.

14 Entering an IP address or DNS name indicates that you are setting up a system with

of the server.
where:
If you are migrating: Result


connect:

GUI subnet address:

where:
Go to step 15 (p. 15-12).

| yes ]?
Go to step 15 (p. 15-12).
| yes ]?
allowed to connect:

GUI subnet address:

where:
Go to step 15 (p. 15-12).

(default) ]?


this subfolder.
If you are migrating: then
server
Go to step 17 (p. 15-13).
Go to step 21 (p. 15-14).

server, or a
server,
Go to step 18 (p. 15-13).

Go to step 19 (p. 15-14).

pools (p. 4-9).


Result:
combination of
Go to step 19 (p. 15-14).

Go to step 21 (p. 15-14).


(p. 4-9).


For simplex server, go to step 22 (p. 15-15)

21 (p. 15-14)
server:

press .

(default) ]:


and press .
password:



combination of
server
OK
OK
OK
Type y and press .
application.
Table 15-1 Migration result
Result of migration
including user home directory, software directory, local and shared data directories,
and database directory.
with the 5520 AMS software, the installer proceeds to install the selected software
components, and displays the following message:
The installer displays the summary of the software components selected for
installation. The installer then proceeds to install each software component, and
displays the status of each installation:
Table 15-2 Activation result
directory. If the --activate-force option is executed (only applicable in an out-of-place migration scenario), the
installer initiates the activation of the 5520 AMS server, and displays the following message:
Initializing..
message:
Activation finished
***Warning***
correctly.
*****************
Activation finished
For more information on updating the firewall, see Procedure 11-1 To update firewall rules (p. 11-2).
If the --activate-force option is executed (only applicable in an out-of-place migration scenario), the installer displays
the summary of the software components selected for activation. The installer then proceeds to activate each
installed software component, and displays the status of each activation:
32 For automated in-place migration, perform the following steps:
i Type x and press .
Result
The migration script performs a pre-install health check up to verify that all the
servers are running and healthy and that there is sufficient disk space available.
If the health check is successfull then you see the following output:
Running health check before install...
Ok
Distribute and install software...
Note: This can take a few minutes...
Done
Go to step ii (p. 15-18)
If the health check is not successful, then the installer prompts you with the error
message:
Running health check before install...
Site status is not healthy
Failed
*** Error ***
The migration tool has detected a severe error (see above or in

/var/opt/ams/local/ams_migration.log)
Do you want to continue abort or rollback [c | a| r| (default)]?
where:
Choose c to ignore the issue and continue with the migration process.
Choose a to abort the migration process. Choosing this option allows the user
to stop the migration process, fix the issue and start from the point where the
process was last stopped. To restart the process, the user must go to the source
release software bin directory and execute the ams_migrate script and choose
the appropriate option.
ii The installer prompts you to create an ams back up before starting the
migration process.
It is advised to create an ams backup before starting the

migration process.
Create an AMS backup now [yes (default) |no]
iii Type yes and press .
Result: The installer prompts you to enter the path to store the backup file.
Enter the full path to the directory where the backup file
needs to be stored (default: /opt/ams/local):
iv Perform one of the following to enter the path to store the backup file:
To choose the default directory path, press .

To enter a new directory path, type the new directory path and press .
Result: The following message is displayed.
Creating AMS Backup...
Note: This can take a few minutes...
Done
Activate new release
*** WARNING ***
Next step will stop the running AMS system and thus the AMS
and all relates services will not be available
v The installer prompts you to confirm the stop sequence.
is it okay to initiate AMS stop sequence [no(default)|yes]:
vi Type yes and press .
Result:
Running ams_cluster stop...
vii The installer prompts you to activate the 5520 AMS 9.4 release.
Open another terminal and execute the command

/ams/ams/software/filename/bin/ams_activate.sh on server
localhost by user root. Press y when server activation is
completed
viii Enter y and press .
Result:
Done
Perform data copy...
Note: This can take a few minutes ...
Done
The script performs the migration anand starts the active dataserver.
Migrate and full start
First database server is starting...
First application servers is starting...
Migrating: Converting CORE
If you are migrating a cluster installation, then you also see the following prompt:
Remaining servers are starting up...
For Red Hat Enterprise Linux servers, the migration script executes the
ams_update_firewall.sh script.
If the migration or server startup is not successful, then the script displays the
following error message:
The migration tool has detected a severe error (See above or in

/var/opt/ams/local/ams_migration.log
Do you want to continue, abort or rollback[c|a|r(default)]?
If migration is not successful, select the rollback option. The 5520 AMS 9.4 server
is stopped and the previous release server is activated and started.
ix The installer prompts you to enter the path for the license files to configure
the licenses.
Enter the full path of the license files [Multiple files

separated by comma]:
x Enter the path and press .
Result: The migration script executes the ams_install_license script to

configure the license.
Configure license...
Done
xi The installer prompts you for enabling the SSL.
Note The SSL option is available only if the ams_check_ssl

command returns SSL is enabled.
If the SSL was enabled in the previous release client, the migration
script executes ams_enable_ssl.sh on all the application servers.
Do you want to enable SSL with the default AMS keystore [yes
(default) | no]?
xii Type yes and press .
Result:
Configure client SSL...
Done
xiii To quit, type q and press .
Note Perform one of the following steps:
If the --includevapsplugs option was not used to install the required

plug-ins during 5520 AMS installation, proceed to install the
software plug-ins. See Section 15.6 Installing the 5520 AMS solution
software components for migration (p. 15-21).
If the required plug-ins have been installed during 5520 AMS
installation, proceed to migrate the switchover_hook.sh script. See
Section 16.2 Migrating the switchover script (p. 16-2)
15.6 Installing the 5520 AMS solution software components for

migration
Applies to This procedure is applicable to out-of-place migration.
Pre-requisite: One of the following tasks:

Installing the 5520 AMS server software in a simplex setup in preparation for
migrating to the 5520 AMS, Release 9.4. See Section 15.5 Installing the
5520 AMS, Release 9.4 for migration (p. 15-4).
Installing the 5520 AMS, Release 9.4 in a cluster or a geographically redundant
installation in preparation for migrating to the 5520 AMS, Release 9.4. See
Section 15.5 Installing the 5520 AMS, Release 9.4 for migration (p. 15-4).
Use Procedure 15-3 To install 5520 AMS solution software components for
migration (p. 15-22) to install new software components such as 5520 AMS NE
plug-ins, 5529 Enhanced Applications and plug-ins as part of a migration of the core.
To update from one version of a software component to another, see Section 13.5
Updating software plug-ins to a new version (p. 13-7). You can also install the
software components using the ams_install.sh script in the non-interactive mode. See
Section 6.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced Applications and
plug-ins, and patches and emergency fixes (p. 6-23) for more information.
Before you proceed:
If you are performing an out-of-place migration from an earlier 5520 AMS
release to the 5520 AMS, Release 9.4, the 5520 AMS, Release 9.4 server must be
installed and activated.
You need the binary installation files for the 5520 AMS solution components you
are adding to the 5520 AMS server. The 5520 AMS software components will be
downloaded as .tar files. For information about downloading an installation file,
see the Release Notice for the 5520 AMS solution component. Extract the binary
installation files of the 5520 AMS solution components to a temporary directory
in the 5520 AMS server prior to installation. See Procedure 5-3 To extract the
downloaded installation file to a new directory (p. 5-4).
You must be able to log in to the 5520 AMS server as amssys.
Procedure 15-3 To install 5520 AMS solution software components

for migration
2 To run the installer script, type one of the following commands:
If the active server is running the 5520 AMS, Release 9.4, type:
ams_install.sh
If the active server is running a release earlier than Release 9.4, to run the
installer from 5520 AMS, Release 9.4, type:
install_dir/ams/software/release/bin/ams_install.sh
where:
install_dir is the directory where software is stored; by default this is /opt.
release is the release of the 5520 AMS. An example is ams-9.4.00-999000.
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
h) Help
q) Quit
Choice:
3 Type i and press .
Result: The script prompts you for the location of the installation files:

be installed:
4 Type the path to the directory and press .

(default)] ?
Caution Do not activate the software plug-ins now if you are

performing an manual in-place migration from an earlier 5520 AMS
release to the 5520 AMS, Release 9.4.
To activate the software components after installation, type yes and press .
Perform this step in an out-of-place migration scenario.
To install the software components without activating them, press .
Result: The script prompts you for the text to filter the software components:
(default)] :
To display only the software components in the directory based on a filter,

type the filter text and press . For example, if you type 9.4 and press , only
the software files containing 9.4 in the filename will be displayed.
To display all software components in the directory, press .
Result: The script presents the installation menu. The menu includes a numbered
list of uninstalled software components in the directory based on the filter, for
example:
"Main > Install" menu:
0 -Select-All-
1 enhanced application / plug-in filename
2 enhanced application / plug-in filename
x) Execute
q) Quit
Choice:
i Type the number corresponding to a software component you need to install

and press .

Result: The menu is presented again, with the numbers for the software
components you chose in square brackets ([ ]).
iii When you have chosen all the software components you need to install, type
x and press .
Summary:
- Selection:
list of enhanced applications/plug-ins you chose
- Options:

be installed: directory

(default)]? y or n
where
directory is the directory you entered in step 4 (p. 15-23).
y or n is the choice you entered in step 5 (p. 15-23).
Result: The installation proceeds, displaying success messages for each plug-in.
Result: The 5520 AMS software components are installed for migration.
Proceed to: Depending on the migration path, proceed to the applicable task:
Migration path Proceed to See
Out-of-place migration from an 1. Migrate the Section 16.2 Migrating the

earlier 5520 AMS release to the switchover_hook.sh script, switchover script (p. 16-2)
5520 AMS, Release 9.4 if the script was modified.
2. Enable SSL if a Section 16.3 Enabling SSL (p.

customized keystored is 16-4)
used.
3. Enable geographical Section 16.4 Enabling
redundancy in case of a geographic redundancy (p.
geographical redundancy 16-5)
setup.
4. Back up the database of Section 16.5 Backing up the

the earlier 5520 AMS 5520 AMS database for an
release for an out-of place out-of-place migration (p.
migration. 16-9)
16 Migration tasks
16.1 Overview of the migration tasks 16-2
16.2 Migrating the switchover script 16-2
16.3 Enabling SSL 16-4
16.4 Enabling geographic redundancy 16-5
16.5 Backing up the 5520 AMS database for an out-of-place

migration 16-9
16.6 Transfer the backup file of 5520 AMS database to the new
server 16-10
16.7 Copying data files from the earlier 5520 AMS release to the
5520 AMS, Release 9.4 16-11
16.8 Starting the 5520 AMS, Release 9.4 servers 16-16
16.9 Adding licenses to the 5520 AMS, Release 9.4

installation 16-20
16.10 Installing the 5520 AMS, Release 9.4 client 16-20
16.11 Launching the 5520 AMS, Release 9.4 client 16-21
16.12 Updating the anonymous FTP user path 16-21
16 Migration tasks
16.1 Overview of the migration tasks
This chapter describes the migration tasks that are performed during migration of an
earlier 5520 AMS release to the 5520 AMS, Release 9.4.
Caution The tasks in this chapter are service-affecting and must be

performed during the maintenance window.
For the complete list of tasks to perform an automated in-place and manual
out-of-place migration from an earlier 5520 AMS release to the 5520 AMS, Release
9.4, see Chapter 14 Migration scenarios and associated task list (p. 14-1). For the
complete list of tasks to perform a manual in-place migration from and earlier 5520
AMS release to the 5520 AMS, Release 9.4, see Appendix B.2 Manual in-place
migration associated task list (p. B-2)
16.2 Migrating the switchover script
Pre-requisite: Depending on the migration path, ensure that the pre-requisite has
been completed:
Migration path Pre-requisite See
Out-of-place migration from an earlier Installing and activating Section 15.6 Installing the
5520 AMS release to the 5520 AMS, software plug-ins 5520 AMS solution software
Release 9.4 components for migration
(p. 15-21)
Use Procedure 16-1 To migrate the switchover_hook.sh script (p. 16-3) to migrate
the switchover_hook.sh script to the 5520 AMS, Release 9.4.
Note Perform Procedure 16-1 To migrate the switchover_hook.sh
script (p. 16-3) only when there are changes to the
switchover_hook.sh script.
Before you proceed, you must to be able to log in to the application server as amssys.
16 Migration tasks
Procedure 16-1 To migrate the switchover_hook.sh script

1 Log in to the application server as amssys.
2 To change to the database scripts directory, type:
cd install_dir/ams/software/earlier_rel_dir/lib/dataserver/bin
where:
install_dir is the directory on the 5520 AMS server where software is installed. By default, this is
/opt.
earlier_rel_dir is the directory of the earlier 5520 AMS release. An example is ams-9.3.0-108719,
if you are migrating from the 5520 AMS, Release 9.3.0 to the 5520 AMS Release 9.4.
3 To copy the switchover hook script to the 5520 AMS, Release 9.4, type:
cp switchover_hook.sh
install_dir/ams/software/current_rel_dir/lib/dataserver/bin
where:
install_dir is the directory on the 5520 AMS server where software is installed. By default, this is
/opt.
current_rel_dir is the directory of the 5520 AMS, Release 9.4. An example is ams-9.4.00-999000.
Result: The switchover_hook.sh script is migrated.

Out-of-place migration from an 1. Enable SSL if a Section 16.3 Enabling SSL (p.
earlier 5520 AMS release to the customized keystored is 16-4)
5520 AMS, Release 9.4 used.
2. Enable geographical Section 16.4 Enabling

redundancy in case of a geographic redundancy (p.
geographical redundancy 16-5)
setup.
3. Back up the 5520 AMS Section 16.5 Backing up the

database of the earlier 5520 AMS database for an
release for an out-of place out-of-place migration (p.
migration. 16-9)
16 Migration tasks
16.3 Enabling SSL
been completed:
Out-of-place migration from an earlier 1. Installing and activating the Section 15.6
5520 AMS release to the 5520 AMS, Release 5520 AMS software plug-ins. Installing the
9.4 5520 AMS
solution
software
components
for migration
(p. 15-21)
2. Migrating the Section 16.2

switchover_hook.sh script, if it was Migrating the
modified. switchover
script (p.
16-2)
Use Procedure 16-2 To enable SSL with a customized keystore (p. 16-4) to enable
SSL, using a customized keystore and keystore password. For information on
generating a customized keystore, see the 5520 AMS Administrator Guide.
Before you proceed, you need the path to the keystore file on the 5520 AMS server
and the keystore password.
Procedure 16-2 To enable SSL with a customized keystore

2 To enable SSL, type:
ams_enable_ssl.sh [path_to_keystore] [keystore_password]
where:
path_to_keystore is the path to the keystore.
keystore_password is the keystore password.
For example:
ams_enable_ssl.sh /tmp/ams.keystore amsams
Result: The SSL is enabled.
16 Migration tasks
Proceed to: Depending on the scenario specified in the table, proceed to the applicable
task:
Migration path Scenario Proceed to See
Out-of-place migration from an In a simplex or cluster setup Copy the data files SectionCopying data
earlier 5520 AMS release to the from the earlier files from a backup
5520 AMS, Release 9.4 release file in an out-of-place
migration scenario
In a geographically Enable geographical Section 16.4 Enabling

redundant setup redundancy geographic
16.4 Enabling geographic redundancy
Applies to This section applies to migrating a geographically

redundant setup to the 5520 AMS, Release 9.4 only.
been completed:
Out-of-place migration from an 1. Installing and activating the Section 15.6

earlier 5520 AMS release to the 5520 AMS and 5529 Enhanced Installing the
5520 AMS, Release 9.4 Applications software plug-ins 5520 AMS solution
software
components for
migration (p. 15-21)
2. Migrating the Section 16.2

switchover_hook.sh script if it was Migrating the
modified in the earlier release switchover script
(p. 16-2)
3. Enabling SSL (applicable if a Section 16.3

customized keystore is used) Enabling SSL (p.
16-4)
Use Procedure 16-3 To configure data replication between sites (p. 16-6) to enable
geographic redundancy.
16 Migration tasks
Procedure 16-3 To configure data replication between sites

1 Verify that the data servers have IP connectivity over the network they will use
for data replication.
2 Log in to the preferred data server at the active site as amssys.
Result: If any snapshots of data are found on the server, the script prompts you
to clean them:
Clean up existing snapshots of filesystem - data/sharedata:
[ 1 ] yes
2 no
Choice:
Note Type 2 to keep the snapshots only if you have verified that they
are valid.
Result: The script prompts you to enable geographic redundancy:
Enable geographic redundancy mode:
[1] yes
2 no
Choice:
5 To enable geographic redundancy, press .
Result: The script prompts you about which site you are configuring:
Is this the active or the standby site:
[1] active
2 standby
3 -Previous menu-
Choice:
To indicate an active site, press .

To indicate a standby site, type 2.
Result: The script prompts you to confirm your choice:
16 Migration tasks
Are you sure you want to make this site the active site [ no
(default) | yes ]?
Result: The script prompts you for the name of the other site:
Enter the name of the remote site
Value:
8 Type the name of the other site and press .
the standby site:
Enter the IP address of the preferred dataserver at site name
Value:
where:
name is the site name you entered.
9 Type the IP address of the preferred data server at the standby site and press .
Enter the IP address of the non-preferred dataserver at site name
Value:
where:
name is the name you entered in step 8 (p. 16-7).
10 (Optional) If you have two data servers at the standby site, type the IP address of
the non-preferred data server at the standby site and press .
Result: The script prompts you for the local network interface to use for
synchronization traffic:
Select the local NIC used to synchronize data with site name:
1 bge0 (IP address)
2 bge1 (IP address)
Choice:
where:
name is the site name.
IP address is the IP address of the network interface.
11 Type the number corresponding to the IP address for your local network interface.
Result: The script provides a summary:
Summary:
Remote site name: name
16 Migration tasks
IP address of preferred data server on remote site: IP address
IP address of non-preferred data server on remote site: IP address
Local NIC for synchronization: bge0
The script prompts you to confirm:
Are you sure you want to enable geographic redundancy? [ no

(default) | yes ]
Note If you have a second data server at the active site, repeat the
procedure for the second server.
13 Repeat steps 2 (p. 16-6) to 12 (p. 16-8) on the data servers at the standby site.
14 Start the servers at the active site. See Procedure 16-6 To start a server (p. 16-18).
15 To verify that the JBoss server at the active site is running, type the following on
an application server:
ams_server status
When the script output says the JBoss server is running, go to step 16 (p. 16-8).
16 Start the servers at the standby site. See Procedure 16-6 To start a server (p.
16-18).
Note The servers at the active site will start all processes. The
standby site will start the process monitor, EMS services, and MySQL
process where MySQL acts as the standby database.
17 To confirm that the sites are communicating with each other, check the
processmonitor log file, located at $AMS_LOG_DIR/processmonitor.log.
The log should contain the following line:
Event: Established connection with remote site.
For more information about system logs, see the 5520 AMS Administrator Guide.
Result: The data replication between sites is configured.
16 Migration tasks
task:
Out-of-place migration from an earler Back up the database Section 16.5 Backing up the
5520 AMS release to the 5520 AMS, for an out-of-place 5520 AMS database for an
Release 9.4 migration out-of-place migration (p.
16-9)
16.5 Backing up the 5520 AMS database for an out-of-place

migration
Applies to This section applies to out-of-place migration from an

Pre-requisite: Ensure that the applicable pre-requisites listed in the table have been
completed:
Out-of-place migration from an 1. Installing and activating the Section 15.6

earlier 5520 AMS release to the 5520 AMS and 5529 Enhanced Installing the
5520 AMS, Release 9.4 Applications software plug-ins 5520 AMS solution
software
components for
migration (p. 15-21)
2. Migrating the switchover_hook.sh Section 16.2
script (applicable if the script was Migrating the
modified in the earlier release) switchover script
(p. 16-2)
3. Enabling SSL (applicable if a Section 16.3

customized keystore is used) Enabling SSL (p.
16-4)
4. Enabling geographical Section 16.4

redundancy, in case of a Enabling
geographically redundant setup geographic
redundancy (p.
16-5)
16 Migration tasks
You must back up the 5520 AMS database before performing the migration tasks.
For information on backing up the database, see the 5520 AMS Administrator Guide
for the earlier release.
Note Perform the backup as close to the maintenance window as
possible to ensure that there are no database changes after the backup
is complete.
Proceed to: Perform the following task:
Out-of-place migration from an Transfer the backup file of the Section 16.6
earlier 5520 AMS release to the earlier 5520 AMS release to the Transfer the backup
5520 AMS, Release 9.4 server on which the 5520 AMS file of 5520 AMS
Release 9.4 is installed database to the
new server (p.
16-10)
16.6 Transfer the backup file of 5520 AMS database to the new
server
Applies to This section applies to out-of-place migration from an

Pre-requisite: Ensure that the applicable pre-requisite listed in the table has been
completed:
Out-of-place migration from an Backing up the 5520 AMS database Section 16.5
earlier 5520 AMS release to the for an out-of-place migration Backing up the
5520 AMS, Release 9.4 5520 AMS database
for an out-of-place
migration (p. 16-9)
Transfer the backup file of the earlier 5520 AMS release database to the server on
which the 5520 AMS, Release 9.4 will be installed.
16 Migration tasks
Out-of-place migration from the Copy data files from a backup file of Section Copying
earlier 5520 AMS release to the the earlier 5520 AMS release data files from a
5520 AMS, Release 9.4 backup file in an
out-of-place
migration scenario
16.7 Copying data files from the earlier 5520 AMS release to the
5520 AMS, Release 9.4
been completed:
Out-of-place migration from Transferring the backup file of Section 16.6

the earlier 5520 AMS release the earlier release to the server Transfer the
to the 5520 AMS, Release 9.4 in which 5520 AMS Release 9.4 is backup file of
installed 5520 AMS
database to
the new
server (p.
16-10)
The ams_copy_datafiles script is used to copy data from the earlier 5520 AMS
release to the current 5520 AMS release from a backup file in the case of an
out-of-place migration.
This script supports migration of data from the 5520 AMS, Release 9.2.10 Patch 03
or later to the 5520 AMS, Release 9.4. For the 5520 AMS releases earlier than
Release 9.2.10, this script is not supported for migration. The script can be executed
in the interactive mode and the non-interactive mode on the data server. If you run
this script on any other server, the following error message is displayed:
ERROR: This script only runs on data servers.
Copying data files from a backup file in an out-of-place migration

scenario
Use Procedure 16-4 To copy data files from a backup file (interactive mode) (p.
16-12) to copy data files from a backup file, in the interactive mode.
Use Procedure 16-5 To copy data files from a backup file (non-interactive mode) (p.
16-14) to copy data files from a backup file, in the non-interactive mode.
16 Migration tasks
Procedure 16-4 To copy data files from a backup file (interactive

mode)
Before you proceed, ensure that a backup file of the earlier 5520 AMS release from
which data needs to be copied to the current active release exists in the 5520 AMS
server on which you are performing this procedure.
1 Log in to the 5520 AMS, Release 9.4 preferred data server as amssys.
2 To copy the data from a backup file, type:
ams_copy_datafiles
Result:
If data files are not already migrated to the current active release, one of the
following messages are displayed:
If a previous release exists on the 5520 AMS server, the following message is
displayed:
Select the source of the data files:
1 AMS release on the server.
2 AMS backup file.
Choice [ 1 (default) | 2 ]?
Go to step 4 (p. 16-13).

If no previous release is found on the 5520 AMS server, the following message
is displayed:
Enter the full path to the directory containing the AMS

backup file:
Go to step 5 (p. 16-13).

If data files are already migrated to the current active release, the following
message is displayed:
Data files already exists for the active AMS release, do you
want to overwrite existing data files? Choice [yes | no
(default)]?
Warning The --overwrite option deletes the complete persistency of

the current active release. This option must be used with extreme
caution, in exceptional circumstances (for example, if the previous
copy was aborted because the disk was full).
Go to step 3 (p. 16-12).
3 Type yes if you are sure you want to overwrite the existing persistency data, and
press .
Result: One of the following messages are displayed:
If a previous release exists on the 5520 AMS server, the following message is
displayed:
16 Migration tasks
2 AMS backup file.
Go to step 4 (p. 16-13).

If no previous release is found on the 5520 AMS server, the following message is
displayed:
Enter the full path to the directory containing the AMS backup
file:
Go to step 5 (p. 16-13).
Result: The following message is displayed:
Enter the full path to the directory containing the AMS backup
file:
5 Enter the absolute path and filename of the backup file generated using the
ams_backup.sh script, and press .
Result: The following messages are displayed, showing the progress and result of
the operation:
Removing old data...............OK (if persistency data is

already migrated)
Extracting data from backup file backup-filename.tar
Extracting AMS_SHAREDDATA_HOME to
/var/opt/ams/shared/current-release-number...........OK
Extracting AMS_SHAREDDATA_NEBACKUP_DIR to
/var/opt/ams/shared/common.......................OK
Extracting emlplatform to
/var/opt/ams/database/current-release-number/emlplatform....OK
Extracting ibdatadir to
/var/opt/ams/database/current-release-number/ibdatadir......OK
Extracting iblogs to
/var/opt/ams/database/current-release-number/iblogs.......OK
Upgrading mysql................................................
Upgrade mysql successful.
Where:
current_release_number is the release directory of the current active release.
backup-filename is the name of the backup file.
16 Migration tasks
The data from the backup file is successfully copied to the current active release.
Note If the data migration fails, the copied data is cleaned up from
the current active release. You need to fix the error, and re-execute
this operation.
Out-of-place migration from the Start the 5520 AMS servers. Section 16.8
earlier 5520 AMS release to the Starting the
5520 AMS, Release 9.4 5520 AMS, Release
9.4 servers (p.
16-16)

(non-interactive mode)
Before you proceed, ensure that a backup file of the earlier 5520 AMS release from
which data needs to be copied to the current active release exists in the 5520 AMS
server on which you are performing this procedure.
ams_copy_datafiles --force --from-backup absolute path of backup

file
where absolute path of backup file is the absolute path and name of the backup file generated
using the ams_backup.sh script.
Result:
If data files are not already migrated to the current active release, the
following messages are displayed, showing the progress and result of the
operation:
/var/opt/ams/database/current-release-number/emlplatform...OK
16 Migration tasks
/var/opt/ams/database/current-release-number/ibdatadir.....OK
Upgrading mysql..............................................
Where:
The persistency data from the backup file is successfully copied to the current
active release. End of procedure.
ERROR: Data files already exist for the active AMS release.
Use option --overwrite to remove exiting data files.

Go to step 3 (p. 16-15) only if you want to overwrite the persistency data of
the current active release.
3 Re-execute the command with the overwrite option. To overwrite existing

persistency data, type:
ams_copy_datafiles --force --overwrite --from-backup absolute

path of backup file
Where absolute path of backup file is the absolute path and name of the backup file generated
using the ams_backup.sh script.
the operation:
Removing old data...............OK
/var/opt/ams/database/current-release-number/emlplatform....OK
/var/opt/ams/database/current-release-number/ibdatadir......OK
16 Migration tasks
Upgrading mysql................................................
Where:
Existing data of the current active release is overwritten with the data files of the
specified backup file.
this operation.
Out-of-place migration from the Start the 5520 AMS servers. Section 16.8
earlier 5520 AMS release to the Starting the
5520 AMS, Release 9.4 5520 AMS, Release
9.4 servers (p.
16-16)
16.8 Starting the 5520 AMS, Release 9.4 servers
been completed:
Out-of-place migration Copying data files from a Section Copying

from the earlier 5520 AMS backup file data files from a
release to the 5520 AMS, backup file in an
Release 9.4 out-of-place
migration
scenario
When migrating a single server, start the 5520 AMS, Release 9.4 server. When
migrating a cluster or a geographically redundant installation, start the 5520 AMS,
Release 9.4 servers in a sequence.
16 Migration tasks
Sequence of starting the 5520 AMS, Release 9.4 servers in cluster

setups and geographically redundant setups
Table 16-1 Start sequence of the 5520 AMS, Release 9.4 servers in cluster setups (p.
16-17) lists the sequence of starting the 5520 AMS, Release 9.4 servers in a cluster
setup.
Table 16-1 Start sequence of the 5520 AMS, Release 9.4 servers in cluster setups
Migration path Server start sequence See
From To
5520 AMS, 5520 AMS, 1. Start the arbiter server, if applicable. Procedure
Release Release 2. Start the preferred data server. 16-6 To
9.3.10 9.4 start a
3. Start one of the application servers. server (p.
5520 AMS,
Release (The application server that is started first becomes the 16-18)
9.2.30 master application server.
Starting the application server triggers the migration.)
4. Check the migration status. Procedure

Ensure that the migration is complete, and the status of 16-7 To
the AMS server process is Running (Master). check the
migration
status (p.
16-20)
5. Start the non-preferred data server. Procedure

6. Start the remaining application servers. 16-6 To
start a
server (p.
16-18)
redundant setups (p. 16-18) lists the sequence of starting the 5520 AMS, Release 9.4
servers in a geographically redundant setup.
16 Migration tasks
redundant setups
Migration path Server start sequence See
From To
5520 AMS, 5520 AMS, 1. Start the arbiter server at the active site, if Procedure
Release Release applicable. 16-6 To start a
9.3.10 9.4 2. Start the preferred data server at the active site. server (p.
5520 AMS, 16-18)
3. Start one of the application servers at the active
Release site. (The application server that is started first at
9.2.30 the active site becomes the master application
server.
Starting the application server at the active site
triggers the migration.)
4. Check the migration status. Procedure

Ensure that the migration is complete, and the 16-7 To check
status of the AMS server process is Running the migration
(Master). status (p.
16-20)
5. Start the non-preferred data server at the active Procedure

site, if applicable. 16-6 To start a
6. Start the remaining application servers at the server (p.
active site. 16-18)
7. Start the arbiter server at the standby site, if
applicable.
8. Start the preferred data server at the standby site.
9. Start the non-preferred data server at the standby
site, if applicable.
10. Start the application servers at the standby site.
Use Procedure 16-6 To start a server (p. 16-18) to start the 5520 AMS, Release 9.4
server.
Use Procedure 16-7 To check the migration status (p. 16-20) to check the migration
status.
Before you proceed:
You must be able to log in to the 5520 AMS server as amssys.
Procedure 16-6 To start a server
Note It can take up to 15 minutes to fully start all the 5520 AMS
server processes. The client connections are not accepted until the
server is fully started as there will be a significant delay between issuing
the ams_server start command with this procedure, and the ability to
log in with a 5520 AMS client.
ams_server start
16 Migration tasks
Result: The 5520 AMS server is started.
Note 1 Repeat steps 1 (p. 16-18) and 2 (p. 16-18) on each 5520 AMS
server in the cluster or geographically redundant setup.
Note 2 If you attempt to start the first 5520 AMS server with an
empty database, the following message is displayed:
WARNING: The AMS is starting up with an empty database.
If you are migrating from AMS R9.2.10 or later, answer

'no' to the question below & invoke the script
'ams_copy_datafiles'
Do you want to proceed: [yes | no (default)]?
To quit the start-up, press .

When migrating from the 5520 AMS, Release 9.2.30 or 9.3.10 to the
5520 AMS, Release 9.4, execute the ams_copy_datafiles script. See
Section 16.7 Copying data files from the earlier 5520 AMS release to
the 5520 AMS, Release 9.4 (p. 16-11).
To continue with the start-up, type y and press . The warning
message will not be displayed during the next start-up.
task:
Migration path Setup Proceed to See
Out-of-place migration from the In a simplex setup Add licenses to the Section 16.9 Adding
earlier 5520 AMS release to the 5520 AMS Release 9.4 licenses to the
5520 AMS, Release 9.4 installation. 5520 AMS, Release
9.4 installation (p.
16-20)
In a cluster or geographically 1. Check the migration Procedure 16-7 To

redundant setup status to ensure that check the migration
migration is complete if status (p. 16-20)
you have started the Procedure 16-6 To
master application server. start a server (p.
2. Ensure that all servers 16-18)
are started. Section 16.9 Adding
3. Add licenses to the licenses to the
5520 AMS Release 9.4 5520 AMS, Release
installation. 9.4 installation (p.
16-20)
16 Migration tasks
Procedure 16-7 To check the migration status
Applies to This procedure applies only to migrating a cluster or a

geographically redundant installation from the earlier 5520 AMS re-
lease to the 5520 AMS, Release 9.4.
Pre-requisite: Starting the master application server. See Table 16-1 Start sequence of
the 5520 AMS, Release 9.4 servers in cluster setups (p. 16-17).
1 Log in to the application server as amssys.
2 To check the migration status, type:
ams_server status
Result: The server status containing the migration status is displayed.
The migration status will be displayed in the following format:
AMS server ... Migrating: Step current_step_num of total_steps

- current_step_description
where:
current_step_num is the current migration step number.
total_steps is the total number of migration steps.
current_step_description is the description of the current migration step.
3 Repeat step 2 (p. 16-20) till the migration is complete, and the status of the AMS
server process is Running (Master).
Proceed to: Start the remaining servers as per the sequence. See Table 16-1 Start
sequence of the 5520 AMS, Release 9.4 servers in cluster setups (p. 16-17).
16.9 Adding licenses to the 5520 AMS, Release 9.4 installation
Pre-requisite: Starting the servers. See Section 16.8 Starting the 5520 AMS, Release
9.4 servers (p. 16-16).
Add the license key to the 5520 AMS installation. See Section 12.6 Adding a license
to the 5520 AMS (p. 12-21) in Chapter 12 Installing the 5520 AMS client (p. 12-1).
Proceed to: Install the 5520 AMS, Release 9.4 client. See Section 16.10 Installing
the 5520 AMS, Release 9.4 client (p. 16-20).
16.10 Installing the 5520 AMS, Release 9.4 client
Pre-requisite: Adding licenses to the 5520 AMS, Release 9.4 installation. See
Section 16.9 Adding licenses to the 5520 AMS, Release 9.4 installation (p. 16-20).
16 Migration tasks
Install the 5520 AMS, Release 9.4 client application. See Sections 12.2 Installing a
single 5520 AMS client (p. 12-4) and 12.3 Installing a shared 5520 AMS client (p.
12-6) in Chapter 12 Installing the 5520 AMS client (p. 12-1).
Proceed to: Launch the 5520 AMS, Release 9.4 client. See Section 16.11 Launching
the 5520 AMS, Release 9.4 client (p. 16-21).
16.11 Launching the 5520 AMS, Release 9.4 client
Pre-requisite: Installing the 5520 AMS, Release 9.4 client. See Section 16.10
Installing the 5520 AMS, Release 9.4 client (p. 16-20).
Launch the 5520 AMS, Release 9.4 client application. See Section 12.4 Launching
and updating the 5520 AMS client (p. 12-13) in Chapter 12 Installing the 5520 AMS
client (p. 12-1).
Proceed to: Depending on the scenario specified in the table, proceed to the
applicable task:
Out-of-place migration from the earlier If you are not migrating ONT Section 17.3
5520 AMS release to the 5520 AMS, Release SIP data from 7342 ISAM FTTU Importing GUI
9.4 R4.9 or earlier, import the GUI settings (p. 17-2)
settings.
16.12 Updating the anonymous FTP user path
Applies to This section is applicable only if you are migrating

ONT SIP data from 7342 ISAM FTTU R4.9 or earlier.
been completed:
Out-of-place migration from the 5520 AMS Launching the 5520 AMS client Section 16.11
release to the 5520 AMS, Release 9.4 Launching the
5520 AMS, Release
9.4 client (p.
16-21)
16 Migration tasks
Migration of the /etc/passwd file is not supported when migrating to the 5520 AMS,
Release 9.4. If you are migrating ONT SIP data, update the anonymous FTP user to
point to the new release. Use Procedure 16-8 To update the anonymous FTP user
path (p. 16-22) to update the anonymous FTP user path.
Before you proceed, you need root access to the 5520 AMS, Release 9.4 server
containing active data.
Procedure 16-8 To update the anonymous FTP user path

1 Log in to the 5520 AMS, Release 9.4 server containing active data, as root.
2 To open the password file, type:
vi /etc/passwd
3 Add the following line:
ftp:x:123:1:AnonymousFTP:$AMS_SHAREDDATA_HOME/ne:/bin/true
Note Ensure to replace $AMS_SHAREDDATA_HOME with the

directory, for the 5520 AMS, Release 9.4, where shared data is stored.
5 To open the ftpaccess file, type:
vi /etc/ftpd/ftpaccess
6 Add the following command:
# allow-retrieve relative class-anonusers /sip
Result: The anonymous FTP user path is updated.
task:
Out-of-place migration from the earlier Import GUI settings. Section 17.3
5520 AMS release to the 5520 AMS, Release Importing GUI
9.4 settings (p. 17-2)
17.1 Overview of the post-migration tasks 17-2
17.2 Migrating ONT SIP data 17-2
17.3 Importing GUI settings 17-2
17.4 Deleting the former site of the earlier 5520 AMS release 17-4
17.1 Overview of the post-migration tasks
This chapter describes the tasks that are performed after the migration of an earlier
5520 AMS release to the 5520 AMS, Release 9.4.
Note The tasks in this chapter are non-service affecting and can be
performed after the maintenance window.
5520 AMS, Release 9.4, see Chapter 14 Migration scenarios and associated task list
(p. 14-1).
17.2 Migrating ONT SIP data
The following ONT SIP releases can be migrated from the NEs on the earlier
5520 AMS release to the 5520 AMS, Release 9.4:
1.4
1.5
1.6
2.1
3.0
3.1
4.4
4.4v2
4.5
4.6
4.7
4.8
5.0
17.3 Importing GUI settings
Pre-requisite: Depending on the scenario specified, ensure that the pre-requisite has
been completed:

Out-of-place migration 1. Launching the 5520 AMS Section 16.11 Launching the
from the earlier 5520 AMS client 5520 AMS, Release 9.4 client (p.
release to the 5520 AMS, 16-21)
Release 9.4
2. Updating the anonymous Section 16.12 Updating the
FTP user path, if you are anonymous FTP user path (p. 16-21)
migrating ONT SIP data from
7342 ISAM FTTU R4.9 or earlier
Migrating GUI settings opens the same perspectives and views as were open in the
earlier release client at the time it was last closed.
Use Procedure 17-1 To import GUI settings (p. 17-3) to import the GUI settings.
Note From Release 9.4, importing the GUI settings of previous

releases is not supported.
The GUI Settings Import option is supported only:
Between releases prior to Release 9.4
From Release 9.4 and later releases.
Procedure 17-1 To import GUI settings

1 In the 5520 AMS, Release 9.4 client, choose FileGUI Settings Import.
Result: The GUI Settings Import window opens.
2 In the AMS Client Workspace Directory field, click Browse and navigate to your
workspace directory. An example is D:\Documents and
Settings\operatorID\5520AMS\earlier release\workspace.
3 Click OK.
4 Click Finish in the GUI Settings Import window.
5 To restart the GUI, click Yes.
Result: The GUI Settings are imported. The same perspectives are open as you had
opened in the earlier release client.
Note You may receive the following error when you choose a per-
spective:
Unable to read workbench state. Reason: Problems occurred

restoring perspective.
If this occurs, right-click the perspective button (for example, Adminis-

tration) and choose Reset.
Result: The perspective is reset to the default.
task:
Out-of-place migration Delete the former site of the Section 17.4 Deleting the
from the earlier earlier 5520 AMS release former site of the earlier
5520 AMS release to the (optional). 5520 AMS release (p. 17-4)
17.4 Deleting the former site of the earlier 5520 AMS release
Applies to This section applies to out-of-place migration from the

been completed:

Out-of-place migration 1. Launching the 5520 AMS Section 16.11 Launching the
from the earlier 5520 AMS client 5520 AMS, Release 9.4 client (p.
release to the 5520 AMS, 16-21)
Release 9.4
2. Updating the anonymous Section 16.12 Updating the
FTP user path, if you are anonymous FTP user path (p. 16-21)
migrating ONT SIP data from
7342 ISAM FTTU R4.9 or
earlier
3. Importing GUI settings Section 17.3 Importing GUI settings

(p. 17-2)
If you imported the data from a different server, the former site of the earlier
5520 AMS release appears in the Administration Tree in the 5520 AMS, Release 9.4
client.
Use Procedure 17-2 To delete the former site of the earlier 5520 AMS release (p.
17-5) to delete the former site of the earlier 5520 AMS release.
Procedure 17-2 To delete the former site of the earlier 5520 AMS
release
1 In the Administration Tree, choose EMS Administration EMS
System Site Application Servers.
2 Right-click the Application Server object for the server to be deleted and choose
Delete. To delete the object, click Yes.
3 Choose EMS Administration EMS System Site External TL1 GW

Servers External TL1 GW server.
4 Right-click the External TL1 Gateway server and choose Delete. To delete the
object, click Yes.
5 Right-click the Site object and choose Delete. To delete the site, click Yes.
Result: The former site of the earlier 5520 AMS release is deleted from the
Administration Tree.
If the former site of the earlier 5520 AMS release is deleted, you have completed an
out-of-place migration from the earlier 5520 AMS release to the 5520 AMS, Release 9.4.
task:
Migration from the earlier If the migration is successful: Section Uninstalling the
5520 AMS release to the 5520 Uninstall the earlier 5520 AMS earlier 5520 AMS release (p.
AMS, Release 9.4 release (optional). B-39)
If the migration is unsuccessful: Section Rolling back to the

Roll back to the earlier 5520 AMS earlier 5520 AMS release (p.
release (optional). B-45)
Uninstalling the 5520 AMS
18 Uninstalling 5520 AMS components

18.1 Uninstalling 5520 AMS components overview 18-2
18.2 Uninstalling software plug-ins 18-2
18.3 Uninstalling patches 18-3
18.4 Uninstalling emergency fixes 18-4
18.5 Uninstalling 5520 AMS NE plug-ins, 5529 Enhanced Applications

and plug-ins, and patches and emergency fixes 18-5
18.6 Uninstalling a 5520 AMS client 18-8
18.7 Uninstalling the 5520 AMS server 18-10
18.1 Uninstalling 5520 AMS components overview
To remove the 5520 AMS, Release 9.4, from your server, uninstall the plug-ins, the
client, the server, patches, and emergency fixes.
If you are uninstalling an earlier release of the 5520 AMS as part of a migration, the
procedures may be different. For information about migrating to the 5520 AMS,
Release 9.4, see Chapter 14 Migration scenarios and associated task list (p. 14-1).
Note If you uninstall the arbiter server, manually clear the "Arbiter
Unavailable" alarm. See the 5520 AMS Administrator Guide for more
information on cluster alarms.
18.2 Uninstalling software plug-ins
You can uninstall 5520 AMS NE plug-ins, or 5529 Enhanced Applications and
plug-ins based on the case listed in Table 18-1 Uninstalling the software plug-ins -
cases (p. 18-2).
Table 18-1 Uninstalling the software plug-ins - cases
Case # Case
1 Uninstall a software plug-in that is already deactivated.
2 Uninstall a software plug-in by deactivating it during uninstallation.
Note After you have uninstalled a plugin, if you log out and log in
again, the Windows client throws an exception for the graphical view
that was open on the NE before the plug was uninstalled. To clear the
exception, just close the view.
Table 18-2 Uninstall a software plug-in (p. 18-2) lists the tasks to uninstall
5520 AMS NE plug-ins, or 5529 Enhanced Applications and plug-ins.
Table 18-2 Uninstall a software plug-in
Task # Task See

1 Back up the currently installed 5520 AMS. 5520 AMS Administrator
Guide
(p. 7-4)
To stop all servers in a cluster setup, use the ams_cluster stop command. Procedure 7-5 To stop a
cluster (p. 7-4)
(1 of 2)
Task # Task See
3 Uninstall the software plug-in. Procedure 18-1 To uninstall

the 5520 AMS NE plug-ins,
and plug-ins, and patches and
To start the server in a simplex setup, use the ams_server start command. Procedure 7-2 To start a
server (p. 7-2)
To start all servers in a cluster setup, use the ams_cluster start command. Procedure 7-3 To start a
cluster (p. 7-3)
You have completed the set of uninstallation tasks.
(2 of 2)
18.3 Uninstalling patches
You can uninstall the 5520 AMS patches based on the case listed in Table 18-3
Uninstalling the 5520 AMS patches - cases (p. 18-3).
Table 18-3 Uninstalling the 5520 AMS patches - cases
Case # Case
1 Uninstall a 5520 AMS patch that is already deactivated.

2 Uninstall a 5520 AMS patch by deactivating it during uninstallation.
Table 18-4 Uninstall a 5520 AMS patch (p. 18-3) lists the tasks to uninstall a
5520 AMS patch.

Table 18-4 Uninstall a 5520 AMS patch
Task # Task See

Guide
(p. 7-4)
cluster (p. 7-4)
(1 of 2)
Task # Task See
3 Uninstall the 5520 AMS patch. Procedure 18-1 To uninstall

server (p. 7-2)
cluster (p. 7-3)
(2 of 2)
18.4 Uninstalling emergency fixes
You can uninstall the emergency fixes based on the case listed in Table 18-5
Uninstalling the emergency fixes - cases (p. 18-4).
Table 18-5 Uninstalling the emergency fixes - cases
Case # Case
1 Uninstall an emergency fix that is already deactivated.

2 Uninstall an emergency fix by deactivating it during uninstallation.
Table 18-6 Uninstall an emergency fix (p. 18-4) lists the tasks to uninstall an
emergency fix.
Table 18-6 Uninstall an emergency fix
Task # Task See

Guide
(p. 7-4)
cluster (p. 7-4)
3 Uninstall the emergency fix. Procedure 18-1 To uninstall

(1 of 2)
Task # Task See
server (p. 7-2)
cluster (p. 7-3)
(2 of 2)
18.5 Uninstalling 5520 AMS NE plug-ins, 5529 Enhanced

Use the Procedure 18-1 To uninstall the 5520 AMS NE plug-ins, 5529 Enhanced
Applications and plug-ins, and patches and emergency fixes together or individually
(p. 18-6) to uninstall the 5520 AMS solution components comprising the 5520 AMS
NE plug-ins, 5529 Enhanced Applications and plug-ins, and patches and emergency
fixes together or individually from the 5520 AMS system.
In a cluster configuration, uninstall the 5520 AMS solution components from each
server.
Caution A cluster installation must not have two application

servers running with different plug-ins installed. After you uninstall
plug-ins from one application server, stop the other server before
starting the updated server.
Table 18-7 Uninstall the 5520 AMS solution components (p. 18-5) lists the tasks to
uninstall the 5520 AMS solution components comprising the 5520 AMS NE
fixes together.
Table 18-7 Uninstall the 5520 AMS solution components
Task # Task See

Guide

(p. 7-4)
cluster (p. 7-4)
3 Uninstall the 5520 AMS solution components together or individually. Procedure 18-1 To uninstall
(1 of 2)
Task # Task See
server (p. 7-2)
cluster (p. 7-3)
(2 of 2)
If you are uninstalling the 5520 AMS NE plug-ins, or 5529 Enhanced Applications
and plug-ins individually, see the uninstallation tasks in Section 18.2 Uninstalling
software plug-ins (p. 18-2).
If you are uninstalling a patch individually, see the uninstallation tasks in Section
18.3 Uninstalling patches (p. 18-3).
If you are uninstalling an emergency fix individually, see the uninstallation tasks in
Section 18.4 Uninstalling emergency fixes (p. 18-4).
Procedure 18-1 To uninstall the 5520 AMS NE plug-ins, 5529

Enhanced Applications and plug-ins, and patches and emergency
fixes together or individually
Before you proceed, you must be able to log in to the 5520 AMS server as amssys.
Note If you try to uninstall an emergency fix before uninstalling the

newer version of the emergency fix, the following error message is
displayed:
ERROR: Cannot deactivate EF because a more recent EF is

ams_install.sh
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
h) Help
q) Quit
Choice:
3 Type u and press .
Do you want to deactivate the software before uninstalling it [y|n

(default)] ?
If you want to deactivate the 5520 AMS solution components before

uninstallation, type y and press .
If you do not want to deactivate the 5520 AMS solution components before
uninstallation, type n and press .
Result: The script prompts you for the text to filter the plug-ins:
(default)] :
be displayed.
Result: The script presents the uninstallation menu. The menu includes a
numbered list of installed 5520 AMS solution components based on the filter, for
example:
"Main > Uninstall" menu:
0 -Select-All-
x) Execute
q) Quit
Choice:
Note If you entered y in Step 4 (p. 18-7), the list consists of all active
and inactive 5520 AMS solution components.
If you entered n in Step 4 (p. 18-7), the list consists of inactive 5520 AMS
solution components only.
to uninstall and press .

uninstall, type x and press .
Summary:
- Selection:
- Options:

(default)]? y
Are you sure you want to Uninstall [y|n (default)] ?
Result: The uninstallation proceeds, displaying success messages for each

5520 AMS solution component.
18.6 Uninstalling a 5520 AMS client
To remove the client from a Windows system, you only need to delete the client
application folder. To remove the client from a Red Hat Enterprise system, you must
remove all client files.
Procedure 18-2 To uninstall the earlier 5520 AMS client application

in Windows
1 Log in to the workstation or server on which the client is installed.
2 Navigate to the folder in which you installed the client application.
3 To uninstall the client application file, delete the folder ams in which the client
application, amsclient.exe, is located.
4 If you do not plan to reinstall the same version of the 5520 AMS client, delete the
folder user_home\5520AMS\version.
where:
user_home is the users home directory.
version is the version of the 5520 AMS, for example, 9.4
Result: The earlier 5520 AMS client application in Windows is uninstalled.
Proceed to: Import the GUI settings (optional). See Section 17.3 Importing GUI settings
(p. 17-2).
Procedure 18-3 To uninstall the 5520 AMS client application in Red

Hat Enterprise Linux
Caution This procedure requires you to perform a recursive delete

operation.
1 Log in as root to the server where the 5520 AMS client is installed.
2 To change to the directory where the client is installed, type:
cd directory
where:
directory is the directory where the client is installed.
3 To remove the installation log file, type:
rm install.log
4 To change to the directory where the client files are available, type:
cd directory/ams
where:
directory is the directory where the client is installed.
5 To remove the client files, type:
rm ams amsclient amsclient.ini chmodpluginsdir keystore

translator.jar
6 To remove the client directories, type:
rm -r .eclipseproduct
rm -r configuration
rm -r features
rm -r jre
rm -r plugins
7 If the 5520 AMS software is not installed on the server and you need to remove the
amssys user and group, type:
userdel amssys
groupdel amssys
Result: The 5520 AMS client application in Solaris in uninstalled.
Proceed to: Install the 5520 AMS, Release 9.4 client. See Section 16.10 Installing the
5520 AMS, Release 9.4 client (p. 16-20).
18.7 Uninstalling the 5520 AMS server
To uninstall the entire 5520 AMS server, you must stop and uninstall the software.
This will permanently remove all data from your system, including the installation
log.
Run the uninstall script from a directory outside the program hierarchy.
If there is more than one 5520 AMS version installed, the version you are
uninstalling must not be the active one. For example, to migrate from 5520 AMS,
Release 9.2.10 to 5520 AMS, Release 9.4, activate the 5520 AMS, Release 9.4
server before you uninstall the 5520 AMS, Release 9.2.10.
Before you proceed:
You need root access to the 5520 AMS server.
The plug-ins for the earlier version of the 5520 AMS and any 5529 Enhanced
Applications you use must be uninstalled. See Section 18.5 Uninstalling
5520 AMS NE plug-ins, 5529 Enhanced Applications and plug-ins, and patches
and emergency fixes (p. 18-5) for more information.
If you have installed a patch for the earlier version of the 5520 AMS, the patch
must be uninstalled. See Procedure 18-1 To uninstall the 5520 AMS NE plug-ins,
5529 Enhanced Applications and plug-ins, and patches and emergency fixes
together or individually (p. 18-6).
Procedure 18-4 To uninstall the 5520 AMS server
Follow this procedure to uninstall the 5520 AMS server. Run the uninstall script from a
directory outside the program hierarchy.
1 Log in to the application server on which the 5520 AMS is installed as root.
2 To stop the 5520 AMS server, type:
install_dir/ams/software/release/bin/ams_server stop
where:
Result: Status messages indicate the progress in stopping the server.
3 To uninstall the 5520 AMS server, type:
install_dir/ams/software/release/bin/ams_uninstall
Result: Status messages indicate the progress in deleting the software from the
server.
Appendix
A. Examples of the installation and activation of the 5520 AMS

solution
B. Manual in-place migration procedures

A. Examples of the installation and
activation of the 5520 AMS
solution
A.1 To install and activate the 5520 AMS solution in a simplex

setup B-2
A.2 To install and activate NE Plug-in B-3
A.3 To install the 5529 Enhanced Applications B-3
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 A-1
A. Examples of the installation and activation of the 5520 AMS solution
A.1 To install and activate the 5520 AMS solution in a simplex

setup
The following is an example for installation and activation of the 5520 AMS solution
in a simplex setup.
cd /var/tmp/downloads/sw .
./ams-9.2.30-170892-solaris-x86.bin --activate-force
Enter full pathname and executable of the program used as the amssys
and amsftp user's shell on login [/bin/sh (default)]:
Enter the site name that uniquely identifies the cluster (no space
allowed):
Is this a simplex (i.e. standalone) system? [ yes (default) | no ]?:
This machine has only a single NIC. Autoselecting for GUI client
interfaces
(default) ]?
139.250.76.66
[/var/opt (default) ]?
In which top directory do you want to store the shared data files

In which top directory do you want to store the local NE software files
[ /ams (default) ]?
(default) ]?
Confirm the password for MySQL root user?
allowed)[ mysql (default) ]:
Confirm the password for MySQL admin application user?

[mysql (default) ]:
A-2 August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
Confirm the password for MySQL replication user?
Table A-1 Result of installation of standalone server in a simplex setup
Result

Initializing..
Activation finished
Installing application ams-9.4.30-170892-solaris-x86.bin
Found AMS root installation dir: /opt/ams/software
A.2 To install and activate NE Plug-in
The following is an example of the installation and activation of the NE plug-in.

ams_install.sh --installActivate
var/temp/downloads/plugin-combo-gpon-4.8-1.0_9.2.30-201234.bin
Extracting application content...
....................................................................
....................................................................
..............The plugin is installed and activated.
A.3 To install the 5529 Enhanced Applications
The following is an example of the installation of the 5529 Enhanced Applications.

ams_install.sh
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 A-3
h) Help
q) Quit
Choice: i
Enter the full path to the directory containing the software to be

installed:
./var/downloads/9.3.10/plugin-apc-isam-5.0-1.0_9.3.10_9.3.10-225445
Do you want to activate the software once it is installed

[y|n(default)] ?
Display only the items containing the following text [all

items<defaukt>]:
Main > Activate" menu:
0 -Select-All-
1 plugin-combo-isam-r5.0-1.0_9.3.10-225445
x) Execute
q) Quit
Choice: 1
Summary:
- Selection: plugin-combo-isam-5.0-1.0_9.3.10_9.3.10-225445
Active application plugin-combo-isam-5.0-1.0_9.3.10_9.3.10-225445
Executing pre-activation scripts...
Pre-activate processing for isam....done
Executing post-activation scripts...
waiting to complete...
now completed.
done
A-4 August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
B. Manual in-place migration
procedures
B.1 Overview of the manual in-place migration scenarios B-2
B.2 Manual in-place migration associated task list B-2
B.3 Pre-migration tasks for manual in-place migration B-8
B.4 Migration tasks for manual in-place migration B-23
B.5 Post-migration tasks B-38
Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 B-1
B.1 Overview of the manual in-place migration scenarios

This apendix describes the following manual in-place migration scenarios and the
associated task list when migrating from an earlier 5520 AMS release to the
5520 AMS, Release 9.4:
Migrating a simplex installation.
Migrating a cluster installation.
Migrating a geographically redundant installation.
Before you proceed to perform the migration tasks, you need root or amssys access
to all servers.
Migration path and strategy

Based on the migration strategy, Table B-1 In-place migration path and data
migration strategy (manual) (p. B-2) lists the task tables for an in-place migration of
a simplex, cluster, and geographically installation to the 5520 AMS, Release 9.4.
Table B-1 In-place migration path and data migration strategy (manual)
Migration path See
From To
5520 AMS, Release 5520 AMS, Release Table B-2 Simplex installation
9.2.30 9.4 migration - In-place (manual)
5520 AMS, Release (p. B-3)
9.3.10
Table B-3 Cluster migration -
In-place (manual) (p. B-4)
Table B-4 Geographically

redundant migration - In-place
(manual) (p. B-6)
B.2 Manual in-place migration associated task list
This section provides the list of the associated tasks to manually perform the in-place
migration for simplex, cluster, and geographically redundant installations.
Migrate a simplex installation

Table B-2 Simplex installation migration - In-place (manual) (p. B-3) lists the tasks
to perform a manual in-place migration from an earlier 5520 AMS release to the
5520 AMS, Release 9.4, if your original site was configured as a simplex setup.
B-2 August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4
Table B-2 Simplex installation migration - In-place (manual)
Task # Task See
servers (p. 15-2)
15-3)
3 Install the 5520 AMS Release 9.4. Section Installing the 5520 AMS,
Release 9.4 for migration
Caution - Ensure that the 5520 AMS, Release 9.4 is not (In-place-manual) (p. B-9)
activated.
4 Install the required 5520 AMS NE plug-in Release 9.4 versions, and 5529 Section 15.6 Installing the 5520 AMS
Enhanced Applications and plug-in Release 9.4 versions that you are solution software components for
migrating from the earlier 5520 AMS release. migration (p. 15-21)
Caution 1- If the 5520 AMS NE plug-ins, 5529 Enhanced

Applications and plug-ins used before the migration are
not installed with the 5520 AMS Release 9.4, their
persistency will not be migrated. These plug-ins cannot be
migrated later.
Caution 2- Ensure that the 5520 AMS NE plug-ins, and 5529
Enhanced Applications and plug-ins are not activated.
5 Back up the database of the earlier 5520 AMS release. Section Backing up the 5520 AMS
database (p. B-22)
6 Stop the earlier 5520 AMS release server. Section Stopping the earlier 5520 AMS
release servers (p. B-23)
7 If you are using a customized keystore, disable SSL. Section Disabling SSL (p. B-24)
8 (Optional) Migrate the switchover script. Section Migrating the switchover
script (p. B-25)
9 Activate the 5520 AMS, Release 9.4 server. Section Activating the 5520 AMS,
Release 9.4 servers (p. B-26)
10 Activate the 5520 AMS plug-ins and 5529 Enhanced Applications. Section Activating the 5520 AMS
software plug-ins (p. B-27)
11 If you are using a customized keystore, enable SSL. Section Enabling SSL (p. B-30)
12 Copy the data from the earlier 5520 AMS release to the 5520 AMS Section Copying data files from the
Release 9.4 directories using the ams_copy_datafiles script. earlier 5520 AMS release to the 5520
AMS, Release 9.4 (p. B-31)
13 Start the 5520 AMS, Release 9.4 server. Section Starting the 5520 AMS,
14 Add licenses for the 5520 AMS installation using the script. Section Adding licenses to the
B-37)
15 Install the 5520 AMS, Release 9.4 client. Section Installing the 5520 AMS,
Release 9.4 client (p. B-37)
16 Launch the 5520 AMS, Release 9.4 client. Section Launching the 5520 AMS,
(1 of 2)
Task # Task See
17 If you are migrating ONT SIP data from 7342 ISAM FTTU R4.9 or earlier, Section Updating the anonymous FTP
update the anonymous FTP user path. user path (p. B-38)
18 (Optional) Import GUI settings. Section Importing GUI settings (p.

B-39)
19 (Optional) Perform one of the following tasks:

If the migration is successful, uninstall the earlier 5520 AMS release.
Section Uninstalling the earlier 5520
AMS release (p. B-39)
If the migration is unsuccessful, roll back to the earlier 5520 AMS
release. Section Rolling back to the earlier
5520 AMS release (p. B-45)
(2 of 2)
Migrate a cluster installation

Table B-3 Cluster migration - In-place (manual) (p. B-4) describes the tasks to
perform a manual in-place migration from an earlier 5520 AMS release to the
5520 AMS, Release 9.4, if your original site was configured as a cluster.
Table B-3 Cluster migration - In-place (manual)
Task # Task See
the cluster. 5520 AMS software to the 5520 AMS
servers (p. 15-2)
15-3)
3 Perform the following steps to install the 5520 AMS, Release 9.4: Section Installing the 5520 AMS,
Install the preferred data server. Release 9.4 for migration
(In-place-manual) (p. B-9)
Install the non-preferred data server, if your cluster includes one.
Install the dedicated 5520 AMS application server, if your cluster
includes one.
Install any additional dedicated 5520 AMS application servers that
will be part of your cluster.
Install the arbiter server, if your cluster includes one.
Caution - Ensure that the 5520 AMS, Release 9.4 servers are
not activated.
(1 of 3)
Task # Task See

later.
database (p. B-22)
6 Stop the earlier 5520 AMS release servers. Section Stopping the earlier
5520 AMS release servers (p. B-23)
script (p. B-25)
9 Activate the 5520 AMS, Release 9.4 servers that are part of the cluster. Section Activating the 5520 AMS,
10 Activate the 5520 AMS plug-ins and 5529 Enhanced Applications on all Section Activating the 5520 AMS
the 5520 AMS, Release 9.4 servers. software plug-ins (p. B-27)
12 Copy the data from the earlier 5520 AMS release to the 5520 AMS, Section Copying data files from the
Release 9.4 preferred data server using the ams_copy_datafiles script. earlier 5520 AMS release to the 5520
AMS, Release 9.4 (p. B-31)
13 Start the following 5520 AMS, Release 9.4 servers (in the following Section Starting the 5520 AMS,
order): Release 9.4 servers (p. B-36)
Arbiter server, if applicable.
Preferred data server.
One of the application servers
application server.
14 Ensure that the migration is complete, using the ams_server status Section Starting the 5520 AMS,
command. Release 9.4 servers (p. B-36)
Non-preferred data server.
The remaining application servers.
16 Add licenses for the 5520 AMS installation using the script. Section Adding licenses to the
B-37)
17 Install the 5520 AMS, Release 9.4 client. Section Installing the 5520 AMS,
(2 of 3)
Task # Task See

B-39)

If the migration is successful, uninstall the earlier 5520 AMS release Section Uninstalling the earlier 5520
servers that are part of the cluster. AMS release (p. B-39)
If the migration is unsuccessful, roll back to the earlier 5520 AMS Section Rolling back to the earlier
release in the cluster. 5520 AMS release (p. B-45)
(3 of 3)
Migrate a geographically redundant installation

Table B-4 Geographically redundant migration - In-place (manual) (p. B-6)
describes the tasks to perform a manual in-place migration from an earlier
5520 AMS release to the 5520 AMS, Release 9.4, if your original site was
configured as a geographically redundant setup.
Table B-4 Geographically redundant migration - In-place (manual)
Task Task See

#

the geographically redundant site. 5520 AMS software to the 5520 AMS
servers (p. 15-2)
15-3)
3 Perform the following steps on the active and standby sites to install the Section Installing the 5520 AMS,
5520 AMS, Release 9.4: Release 9.4 for migration
Install the preferred data server. (In-place-manual) (p. B-9)
Install the non-preferred data server, if your cluster includes one.
Install the dedicated 5520 AMS application server, if your cluster
includes one.
Install any additional dedicated 5520 AMS application servers that
will be part of your cluster.
Install the arbiter server, if your cluster includes one.
Caution - Ensure that the 5520 AMS, Release 9.4 servers are
not activated.
(1 of 3)
Task Task See

#

later.
database (p. B-22)
6 Stop the earlier 5520 AMS release servers in the active and standby sites. Section Stopping the earlier
5520 AMS release servers (p. B-23)
For simplex configurations, use the ams_server script to stop the server.
For cluster configurations, use the ams_cluster script to stop the servers
in the cluster.

script (p. B-25)
9 Activate the 5520 AMS, Release 9.4 on the servers in the active and Section Activating the 5520 AMS,
standby sites. Release 9.4 servers (p. B-26)
10 Activate the 5520 AMS plug-ins and 5529 Enhanced Applications on all Section Activating the 5520 AMS
the 5520 AMS, Release 9.4 servers. software plug-ins (p. B-27)
12 Enable geographic redundancy. Section Enabling geographic
redundancy (p. B-30)
13 Copy the data of the earlier 5520 AMS release to the 5520 AMS, Release Section Copying data files from the
9.4 preferred data server at the active site using the ams_copy_datafiles earlier 5520 AMS release to the 5520
script. AMS, Release 9.4 (p. B-31)
Arbiter server at the active site, if applicable.
Preferred data server at the active site.
One of the application servers at the active site.
application server.
15 Ensure that the migration is complete, using the ams_server status Section Starting the 5520 AMS,
command. Release 9.4 servers (p. B-36)
(2 of 3)
Task Task See

#
Non-preferred data server at the active site, if applicable.
The remaining application servers at the active site.
Arbiter server at the standby site, if applicable.
Preferred data server at the standby site.
Non-preferred data server at the standby site, if applicable.
Application servers at the standby site.
17 Add licenses for the 5520 AMS installation at the active and standby site Section Adding licenses to the
using the script. 5520 AMS, Release 9.4 installation (p.
B-37)
18 Install at least one 5520 AMS, Release 9.4 client. Section Installing the 5520 AMS,

B-39)

If the migration is successful, uninstall the earlier 5520 AMS release Section Uninstalling the earlier 5520
in the active and standby sites. AMS release (p. B-39)
If the migration is unsuccessful, roll back to the earlier 5520 AMS Section Rolling back to the earlier
release in the active and standby sites. 5520 AMS release (p. B-45)
(3 of 3)
B.3 Pre-migration tasks for manual in-place migration

This section describes the tasks that are performed before the manual in-place
migration of an earlier 5520 AMS release to the 5520 AMS Release 9.4.
Note The tasks in this section are non-service affecting and can be
performed before the maintenance window. However, you must
perform the tasks in this chapter as close to the maintenance window
as possible, and ensure that no database changes are made after
performing the export and backup tasks.
5520 AMS, Release 9.4, see Section B.2 Manual in-place migration associated task
list (p. B-2).
Installing the 5520 AMS, Release 9.4 for migration

(In-place-manual)
Pre-requisite: Transferring the 5520 AMS software to the 5520 AMS servers. See
Section 15.2 Transferring the 5520 AMS software to the 5520 AMS servers (p.
15-2).
Use Procedure B-1 To install the 5520 AMS solution for manual in-place migration
(p. B-9) to install 5520 AMS server software on a simplex installation, in preparation
for migrating to the 5520 AMS, Release 9.4 from an earlier 5520 AMS release. For
information on the pre-requisites to perform the migration, see Section 6.2
Pre-requisite tasks (p. 6-2).
In case of a manual in-place migration from an older release to current release, the
paths defined during the previous installation are considered and autopopulated for
the software, local data, shared data, and database directories. Thus, the installer does
not prompt the user for any inputs. The user is only prompted to confirm the
installation.
Note The user is not allowed to make any changes to this

information.
Procedure B-1 To install the 5520 AMS solution for manual in-place
migration
Migrate all 5520 AMS ./installation_filename.bin --includevapsplugs The installation software displays the
solution components directory_path following confirmation:
without a
configuration file where directory_path is the path to the directory containing the VAPs Checking OS and version ...
(recommended) and/or NE Plugs .bin files. If only a subset of files in a directory need OK.
to be installed, or if the .bin files are stored in different directories,
the absolute path and filename of each .bin file needs to be specified.
Checking hostname ... OK
where:
release is the release of the VAP or NE plug-in. An example for is VAP Checking SSH (ssh,
is app-idm-1.0_9.4-246228.bin and for NE plug-in is
plugin-combo-gpon-4.7-1.0_9.4-156320.bin. ssh-keygen, ssh-keyscan, scp,
sftp) ...
Migrate only the 5520 ./installation_filename.bin
AMS core software The installer prompts you for the location of
(excluding other the SSH library:
solution components)
Enter the path to the SSH
tools [ /usr/bin (default) ]:
Proceed to step 4 (p. B-10).
Migrate all 5520 AMS In the case of out-of-place migration: The migration proceeds based on the
solution components settings saved in the configuration file. The
using a configuration ./installation_filename.bin -c choices saved in the configuration file are
file path_and_filename ---includevapsplugs displayed. See Table B-5 Migration result (p.
directory_path B-20) for the migration result.
where:


a new site name.

]?:
If then Result


where:
5520 AMS installer.
Go to step 15 (p. B-15)

allowed to connect:

Go to step 15 (p. B-15).
If then Result
a cluster press .
server):
[2] Data server
[4] Arbiter
If you need to migrate then Result
A combination of type 3 and
The cluster subnet is: Subnet addresses
server
where:
press . server.
the subnet address.
If you are then
where:
the IP address.
information:

where:

information
For application server, go to step 12 (p. B-14)

For combination of application and data server, go to step 13 (p. B-14)

where:

If you are then

where:
name of the server.
Result:
IP address
server.

14 Entering a IP address or DNS name indicates that you are setting up a system with

of the server.
where:

connect:

GUI subnet address:

where:

| yes ]?
| yes ]?
allowed to connect:

GUI subnet address:

where:

(default) ]?


this subfolder.
server

server, or a
server,


pools (p. 4-9).


Result:

combination of



(p. 4-9).


For simplex server, go to step 22 (p. B-18)

21 (p. B-18)
server:

press .

(default) ]:


and press .
password:



combination of
server
OK
OK
OK
Type y and press .
application.
Table B-5 Migration result
Result of migration
including user home directory, software directory, local and shared data directories,
and database directory.
with the 5520 AMS software, the installer proceeds to install the selected software
components, and displays the following message:
The installer displays the summary of the software components selected for
installation. The installer then proceeds to install each software component, and
displays the status of each installation:
Table B-6 Activation result
directory. If the --activate-force option is executed (only applicable in an out-of-place migration scenario), the
installer initiates the activation of the 5520 AMS server, and displays the following message:
Initializing..
message:
Activation finished
***Warning***
correctly.
*****************
Activation finished
For more information on updating the firewall, see Procedure 11-1 To update firewall rules (p. 11-2).
If the --activate-force option is executed (only applicable in an out-of-place migration scenario), the installer displays
the summary of the software components selected for activation. The installer then proceeds to activate each
installed software component, and displays the status of each activation:
Note Perform one of the following steps:
If the --includevapsplugs option was not used to install the required

plug-ins during 5520 AMS installation, proceed to install the
software plug-ins. See Section 15.6 Installing the 5520 AMS solution
software components for migration (p. 15-21).
If the required plug-ins have been installed during 5520 AMS
installation, proceed to migrate the switchover_hook.sh script. See
Section Migrating the switchover script (p. B-25)
Installing the 5520 AMS solution software components for migration

Use Procedure 15.2 Transferring the 5520 AMS software to the 5520 AMS servers
(p. 15-2) to install new software components such as 5520 AMS NE plug-ins, 5529
Enhanced Applications and plug-ins as part of a migration of the core. To update
from one version of a software component to another, see Section 13.5 Updating
software plug-ins to a new version (p. 13-7). You can also install the software
components using the ams_install.sh script in the non-interactive mode. See Section
6.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced Applications and plug-ins,
and patches and emergency fixes (p. 6-23) for more information.
Before you proceed:
If you are performing a manual in-place migration from an earlier 5520 AMS
release to the 5520 AMS, Release 9.4, the 5520 AMS, Release 9.4 server must be
installed but not activated.
You need the binary installation files for the 5520 AMS solution components you
are adding to the 5520 AMS server. The 5520 AMS software components will be
downloaded as .tar files. For information about downloading an installation file,
see the Release Notice for the 5520 AMS solution component. Extract the binary
installation files of the 5520 AMS solution components to a temporary directory
in the 5520 AMS server prior to installation. See Procedure 5-3 To extract the
downloaded installation file to a new directory (p. 5-4).
Backing up the 5520 AMS database
Applies to This section applies to manual in-place migration from

an earlier 5520 AMS release to the 5520 AMS, Release 9.4.
Pre-requisite: Installing the 5520 AMS solution software components, such as

5520 AMS NE plug-ins and 5529 Enhanced Applications and plug-ins. See Section
Installing the 5520 AMS solution software components for migration (p. B-22).
You must back up the 5520 AMS database before performing the migration tasks.
For information on backing up the database, see the 5520 AMS Administrator Guide
for the earlier release.
Note 1 Perform the backup as close to the maintenance window as
possible to ensure that there are no database changes after the backup
is complete.
Note 2 Backing up the 5520 AMS database is not mandatory, but
Alcatel-Lucent recommends backing up the 5520 AMS database
before migrating to the 5520 AMS, Release 9.4.
Proceed to: Stop the 5520 AMS server. See Section Stopping the earlier 5520 AMS
release servers (p. B-23).
B.4 Migration tasks for manual in-place migration
This section describes the migration tasks that are performed during the manual
in-place migration of an earlier 5520 AMS release to the 5520 AMS, Release 9.4.
Caution The tasks in this section are service-affecting and must be

performed during the maintenance window.
Stopping the earlier 5520 AMS release servers

been completed:
Manual in-place migration Backing up the 5520 AMS Section Backing up the 5520 AMS
from an earlier 5520 AMS database database (p. B-22)
release to the 5520 AMS,
Release 9.4
Use Procedure B-2 To stop a server in a simplex setup or all servers in a cluster setup
(p. B-24) to stop the earlier 5520 AMS release server in a simplex setup or all earlier
5520 AMS release servers in a cluster setup.
Before you proceed, you must be able to log in to the 5520 AMS servers as amssys.
Procedure B-2 To stop a server in a simplex setup or all servers in a

cluster setup
1 Log in to the earlier 5520 AMS release server as amssys.
To stop a server in a simplex setup, type:
ams_server stop
Result: The 5520 AMS server is stopped.
To stop all servers in a cluster setup, type:
ams_cluster stop
Result: All servers in the 5520 AMS cluster are stopped.
task:
Manual in-place If you are using a customized Disable SSL Section Stopping the
migration from an earlier keystore earlier 5520 AMS release
5520 AMS release to the servers (p. B-23)
If you are not using a customized
keystore, and:
The switchover_hook.sh script has Migrate the Section Migrating the

been modified switchover_hook.sh switchover script (p. B-25)
script
The switchover_hook.sh script has Activate the 5520 AMS Section Activating the
not been modified Release 9.4 servers. 5520 AMS, Release 9.4
servers (p. B-26)
Disabling SSL
been completed:
Manual in-place migration Stopping the 5520 AMS Section Stopping the earlier
from an earlier 5520 AMS servers 5520 AMS release servers (p. B-23)
Release 9.4
If you are using a customized keystore, use Procedure B-3 To disable SSL (p. B-25)
to disable SSL.
Note In a cluster environment, you must disable SSL on every

server in the cluster.
Procedure B-3 To disable SSL

1 Log in to the 5520 AMS server as amssys, if you are not already logged in.
2 To disable SSL, type:
ams_disable_ssl.sh
Result: The SSL is disabled.
task:
Manual in-place The switchover_hook.sh Migrate the Section Migrating the

migration from script has been modified in switchover_hook.sh switchover script (p.
an earlier the earlier release script B-25)
5520 AMS
release to the The switchover_hook.sh Activate the 5520 AMS Section Activating the
5520 AMS, script has not been Release 9.4 servers. 5520 AMS, Release 9.4
Release 9.4 modified in the earlier servers (p. B-26)
release
Migrating the switchover script

been completed:
Migration path Prerequisite See
In-place migration from an 1. Stopping the 5520 AMS Section Stopping the earlier
earlier 5520 AMS release to the servers 5520 AMS release servers (p.
5520 AMS, Release 9.4 B-23)
2. Disabling SSL (if a customized Section Disabling SSL (p. B-24)

keystore is used).
Use Procedure 16-1 To migrate the switchover_hook.sh script (p. 16-3) to migrate
the switchover_hook.sh script to the 5520 AMS, Release 9.4.
Note Perform the Procedure 16-1 To migrate the

switchover_hook.sh script (p. 16-3) only when there are changes to
the switchover_hook.sh script.
Before you proceed, you must be able to log in to the application server as amssys.
Activating the 5520 AMS, Release 9.4 servers

been completed:
Manual in-place migration from an 1. Stopping the 5520 AMS Section Stopping the
earlier 5520 AMS release to the 5520 servers earlier 5520 AMS
AMS, Release 9.4 release servers (p.
B-23)
2. Disabling SSL (applicable if a Section Disabling SSL

customized keystore is used) (p. B-24)
3. Migrating the Section Migrating the
switchover_hook.sh script switchover script (p.
(applicable if the script was B-25)
modified in the earlier release)
Use Procedure B-4 To activate a server (p. B-26) to activate the 5520 AMS, Release
9.4 servers. In a cluster, you must activate the 5520 AMS, Release 9.4 on each server
in the cluster.
Before you proceed:
The servers must be installed.
You must be able to log in to the servers as root.
Procedure B-4 To activate a server

1 Log in to the 5520 AMS server as root.
where:
install_dir is the software directory you chose during installation; by default, this is /opt
Result: The 5520 AMS server is activated.
Warning After activating the 5520 AMS 9.4 server, ensure to close
all the amssys session and login again or reload the profile.
Note Post-migration from an earlier release to Release 9.3.10, upon execution

of the "cd $AMS_LOG_DIR" command, to avoid landing in the log directory of the
earlier release from which you just migrated, you must end all amssys sessions and
log in again or reload the profile.

Manual in-place migration from an earlier 5520 Activate the 5520 AMS Section Activating
AMS release to the 5520 AMS, Release 9.4 software plug-ins and 5529 the 5520 AMS
Enhanced Applications. software plug-ins
(p. B-27)
Activating the 5520 AMS software plug-ins

been completed:
Manual in-place migration from an earlier Activating the 5520 AMS Release Section
5520 AMS release to the 5520 AMS, Release 9.4 servers Activating the
9.4 5520 AMS,
Release 9.4
servers (p.
B-26)
Use Procedure B-5 To activate a software plug-in (p. B-28) to activate new plug-ins
as part of a migration of the core. To update from one version of a plug-in to another,
see Section 13.5 Updating software plug-ins to a new version (p. 13-7).
Use Procedure B-5 To activate a software plug-in (p. B-28) to activate a software
plug-in if you did not activate it when you performed the installation. Installing the
plug-in puts the software files in the correct location ready for use. However, until
you activate the plug-in, the software is in a passive, standby mode.
Activating the plug-in software puts its files in a location where they will be started
by the JBoss server.

The 5520 AMS, Release 9.4 server is installed and activated.
You have installed the plug-in you are activating.
Procedure B-5 To activate a software plug-in

ams_install.sh
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
q) Quit
h) Help
Choice:
3 Type a and press .
(default)] :
To display only the plug-ins in the directory based on a filter, type the filter
text and press . For example, if you type 9.4 and press , only the plug-in
files containing 9.4 in the filename will be displayed.
To display all plug-ins in the directory, press .
Result: The script presents the activation menu. The menu includes a numbered
list of installed plug-ins in the directory based on the filter, for example:
"Main > Activate" menu:
0 -Select-All-
1 plug-in filename
2 plug-in filename
x) Execute
q) Quit
Choice:
i Type the number corresponding to a plug-in you need to activate and press .

Result: The menu is presented again, with the numbers for the plug-ins you
chose in square brackets ([ ]).
iii When you have chosen all the plug-ins you need to activate, type x and press
.
Summary:
- Selection:
list of plug-ins you chose
Are you sure you want to Activate [y|n (default)] ?
Result: The installation proceeds, displaying success messages for each plug-in.
Result: The selected software plug-ins are activated.
task:
Manual in-place migration If a customized keystore is used Enable SSL Section 16.3 Enabling SSL
from an earlier 5520 AMS (p. 16-4)
Release 9.4
Manual in-place migration If a customized keystore is not

from an earlier 5520 AMS used, then:
Release 9.4 In a simplex or cluster setup Copy the data files Section Copying data files
from the earlier from the earlier 5520 AMS
release release to the 5520 AMS,
Release 9.4 (p. B-31)
In a geographically redundant setup Enable geographical Section Enabling geographic

redundancy redundancy (p. B-30)
Enabling SSL
been completed:
Manual in-place migration Activating the 5520 Section Activating the

from and earlier 5520 AMS AMS software 5520 AMS software plug-ins
release to the 5520 AMS, plug-ins (p. B-27)
Release 9.4
Use the procedure 16-2 To enable SSL with a customized keystore (p. 16-4) to enable
the SSL, using a customized keystore and keystore password. For information on
generating a customized keystore, see 5520 AMS Administrator Guide.
Before you proceed, you need the path to the keystore file on the 5520 AMS server
and the keystore password.
Enabling geographic redundancy
Applies to This section applies on to migrating a geogrpahically

redundant setup to the 5520 AMS, Release 9.4 only.
been completed:
Manual in-place migration Activating the 5520 Section Activating the

from an earlier 5520 AMS AMS software 5520 AMS software plug-ins
release to the 5520 AMS, plug-ins (p. B-27)
Release 9.4
2. Enabling SSL Section Enabling SSL (p.
(applicable if a B-30)
customized keystore
is used)
Use Procedure 16-3 To configure data replication between sites (p. 16-6) to enable
geographic redundance.
Copying data files from the earlier 5520 AMS release to the 5520
AMS, Release 9.4
been completed:
Migration path Setup Pre-requisite See

Manual in-place migration Simplex or cluster setup 1. Activating the Section Activating the
from an earlier 5520 AMS 5520 AMS and 5529 5520 AMS software plug-ins
release to the 5520 AMS, Enhanced (p. B-27)
Release 9.4 Applications
software plug-ins
2. Enabling SSL Section Enabling SSL (p.

(applicable if a B-30)
customized keystore
is used)
Geographically redundant setup Enabling Section Enabling geographic

geographical redundancy (p. B-30)
redundancy
In case of a manual in-place migration, the ams_copy_datafiles script is used to copy

the data from the earlier 5520 AMS release to the current 5520 AMS release.
This script supports migration of data from 5520 AMS, Release 9.2.30 or 9.3.10 to
5520 AMS, Release 9.4. For the 5520 AMS release earlier than Release 9.2.30, this
script is not supported for migration. The script can be executed in the interactive
mode and non-interactive mode on the data server. If you run this script on any other
server, the following error message is displayed:
Error: This script only runs on data servers.
Copying data files from a previous release in an in-place migration scenario

Use Procedure B-6 To copy data files from the previous release (interactive mode)
(p. B-32) to copy data files from an earlier 5520 AMS release on the server, in the
interactive mode.
Use Procedure B-7 To copy data files from the previous release (non-interactive
mode) (p. B-34) to copy data files from an earlier 5520 AMS release on the server,
in the non-interactive mode.

(interactive mode)
Before you proceed, ensure that an earlier 5520 AMS release from which you want to
copy the data exists in the server on which you are performing this procedure.
ams_copy_datafiles
Result:
following message is displayed:
2 AMS backup file.

Data files already exists for the active AMS release, do you
want to overwrite existing data files? Choice [yes | no
(default)]?

3 Type yes if you are sure you want to overwrite the existing persistency data, and
press .
2 AMS backup file.
Select the AMS release to copy from:
1 prev-release-number (previously active)
2 prev-release-number2
3 prev-release-number3
Choice (default = 1)?
Where prev-release-number is the previously active release number found in the 5520 AMS server.
5 Type 1 to select the most recently active previous release, or type the number of
any other previous release from which you want to copy data, and press .
the operation:
Removing old data................OK (if persistency data already

exists)
Copying data from ams release prev-release-number
Copying MYSQL_DATA data from

/var/opt/ams/database/prev-release-number to
/var/opt/ams/database/current-release-number...............OK
Copying AMS_SHAREDDATA_HOME data from

/var/opt/ams/shared/prev-release-number to
/var/opt/ams/shared/current-release-number..........OK
Upgrading mysql.........................................OK
Upgrade MySQL successful.
where:
prev-release-number is the release directory of the previous active release.
The data from the previous active release is successfully copied to the current
active release.
this operation.
Manual in-place migration from the Start the 5520 AMS servers. Section Starting the
earlier 5520 AMS release to the 5520 AMS, Release
5520 AMS, Release 9.4 9.4 servers (p.
B-36)

(non-interactive mode)
Before you proceed, ensure that an earlier 5520 AMS release from which you want to
copy the data exists in the server on which you are performing this procedure.
To copy the data from the last active release, type:
ams_copy_datafiles --force
By default, data is copied from the last active release, if the --from-release option
is not specified.
To copy the data from a previous release which is not the last active release, type:
ams_copy_datafiles --force --from-release prev-release-number

where prev-release-number is the name of the release directory of the previous release from
which data needs to be migrated.
Data is copied from the specified previous release on the server.
Result:
following messages are displayed, showing the progress and result of the
operation:


Where:
The persistency data from the previous release is successfully copied to the
current active release. End of procedure.
ERROR: Data files already exist for the active AMS release.
Use option --overwrite to remove exiting data files.

Go to step 3 (p. B-35) only if you want to overwrite the persistency data of the
current active release.
3 Re-execute the command with the overwrite option. Perform one of the following
steps:
To overwrite existing persistency data with data from the last active release, type:
ams_copy_datafiles --force --overwrite
Existing data is overwritten with the data files of the last active release.
To overwrite existing persistency data with data from the previous release on the
server, type:
ams_copy_datafiles --force --overwrite --from-release

prev-release-number
Existing data is overwritten with the data files of the specified previous release.
where prev-release-number is the name of the release directory of the previous active
release from which data needs to be migrated.
the operation:
Removing old data.........................................OK


Where:
The persistency data from the previous release is successfully copied to the
current active release.
this operation.

Manual in-place migration from the Start the 5520 AMS servers. Section Starting
earlier 5520 AMS release to the the 5520 AMS,
5520 AMS, Release 9.4. Release 9.4 servers
(p. B-36)
Starting the 5520 AMS, Release 9.4 servers

been completed:
Migration path Setup Pre-requisite See
Manual in-place migration Simplex, Copying data files from the Section Copying
from the earlier 5520 AMS cluster or earlier release data files from
release to the 5520 AMS, geographically the earlier 5520
Release 9.4. redundant AMS release to
setup the 5520 AMS,
Release 9.4
When migrating a single server, start the 5520 AMS, Release 9.4 server. When
migrating a cluster or a geographically redundant installation, start the 5520 AMS,
Release 9.4 servers in a sequence. For more information on the starting sequence of
the servers in a cluster or a geographically redundant installation, see Section
Sequence of starting the 5520 AMS, Release 9.4 servers in cluster setups and
geographically redundant setups (p. 16-17).
Use the procedure 16-6 To start a server (p. 16-18) to start the 5520 AMS, Release
9.4 server.
Use the procedure 16-7 To check the migration status (p. 16-20) to check the
migration status.
Before you proceed:
You must be able to lot into the 5520 AMS server as amssys.
Adding licenses to the 5520 AMS, Release 9.4 installation

Pre-requisite: Starting the servers. See Section Starting the 5520 AMS, Release 9.4
servers (p. B-36).
Add the license key to the 5520 AMS installation. See Section 12.6 Adding a license
to the 5520 AMS (p. 12-21) in Chapter 12 Installing the 5520 AMS client (p. 12-1).
Proceed to: Install the 5520 AMS, Release 9.4 client. See Section Installing the
5520 AMS, Release 9.4 client (p. B-37).
Installing the 5520 AMS, Release 9.4 client

Pre-requisite: Adding licenses to the 5520 AMS, Release 9.4 installation. See
Section Adding licenses to the 5520 AMS, Release 9.4 installation (p. B-37).
Install the 5520 AMS, Release 9.4 client application. See Sections 12.2 Installing a
single 5520 AMS client (p. 12-4) and 12.3 Installing a shared 5520 AMS client (p.
12-6) in Chapter 12 Installing the 5520 AMS client (p. 12-1).
Proceed to: Launch the 5520 AMS, Release 9.4 client. See Section Launching the
5520 AMS, Release 9.4 client (p. B-37).
Launching the 5520 AMS, Release 9.4 client

Pre-requisite: Installing the 5520 AMS, Release 9.4 client. See Section Installing
the 5520 AMS, Release 9.4 client (p. B-37).
Launch the 5520 AMS, Release 9.4 client application. See Section 12.4 Launching
and updating the 5520 AMS client (p. 12-13) in Chapter 12 Installing the 5520 AMS
client (p. 12-1).
applicable task:
Manual in-place migration from the earlier If you are migrating ONT SIP Section Updating
5520 AMS release to the 5520 AMS, Release data from 7342 ISAM FTTU the anonymous
9.4 R4.9 or earlier, update the FTP user path (p.
anonymous FTP user path. B-38)
Updating the anonymous FTP user path
Applies to This section is applicable only if you are migrating

ONT SIP data from 7342 ISAM FTTU R4.9 or earlier.
been completed:

Manual in-place migration from the earlier Launching the 5520 AMS client Section Launching
5520 AMS release to the 5520 AMS, Release the 5520 AMS,
9.4 Release 9.4 client
(p. B-37)
Migration of the /etc/passwd file is not supported when migrating to the 5520 AMS,
Release 9.4. If you are migrating ONT SIP data, update the anonymous FTP user to
point to the new release. Use Procedure 16-8 To update the anonymous FTP user
path (p. 16-22) to update the anonymous FTP user path.
Before you proceed, you need root access to the 5520 AMS, Release 9.4 server
containing active data.
B.5 Post-migration tasks
This section describes the tasks that are performed after the manual in-place
migration of an earlier 5520 AMS release to the 5520 AMS. Release 9.4.
Note The tasks in this section are non-service affecting and can be
performed after the maintenance window.
For complete list of manual in-place migration tasks from and earlier 5520 AMS
release to the 5520 AMS, Release 9.4, see Section B.2 Manual in-place migration
associated task list (p. B-2)
Importing GUI settings

been completed:
Manual in-place migration Launching the 5520 AMS client Section Launching the 5520 AMS,
from the earlier 5520 AMS Release 9.4 client (p. B-37)
Release 9.4
Migrating GUI settings opens the same perspectives and views as were open in the
earlier release client at the time it was last closed.
Use the Procedure 17-1 To import GUI settings (p. 17-3) to import the GUI settings.
applicable task:

Manual in-place If the migration is successful: Section Uninstalling the
migration from the Uninstall the earlier 5520 AMS earlier 5520 AMS release (p.
earlier 5520 AMS release release (optional). B-39)
to the 5520 AMS,
Release 9.4 If the migration is unsuccessful: Section Rolling back to the
Roll back to the earlier 5520 AMS earlier 5520 AMS release (p.
release (optional). B-45)
Uninstalling the earlier 5520 AMS release

Pre-requisite: Ensure that the pre-requisite has been completed:
Manual in-place migration Importing GUI settings Section Importing GUI

from the earlier 5520 AMS settings (p. B-39)
Release 9.4
Caution Ensure that the migration to 5520 AMS, Release 9.4 is

successful before uninstalling the earlier 5520 AMS release.
To uninstall the earlier 5520 AMS release you must uninstall the software. This will
permanently remove all data from the earlier release from your system, including the
installation log. Perform the procedures in this section for each application server in
the cluster.
If there is more than one 5520 AMS version installed, the version you are
uninstalling must not be the active one. For example, to migrate from the 5520 AMS,
Release 9.3.10 to the 5520 AMS, Release 9.4, activate the 5520 AMS, Release 9.4
server before you can uninstall the 5520 AMS, Release 9.3.10.
Before you proceed, you need root access to the 5520 AMS server.
Table B-7 Uninstall the earlier 5520 AMS release after migrating to the 5520 AMS,
Release 9.4 (p. B-40) describes the tasks to uninstall the earlier 5520 AMS release.
Table B-7 Uninstall the earlier 5520 AMS release after migrating to the 5520 AMS, Release 9.4
Task # Task See
1 Uninstall the plug-ins for the earlier 5520 AMS release and any 5529 Enhanced Procedure B-8 To uninstall
Applications you use. software plug-ins after
migration (p. B-41) or
Procedure B-9 To uninstall a
software plug-in manually
after migration (p. B-43)
2 If you have installed a patch for the earlier 5520 AMS release, uninstall the Procedure B-10 To uninstall a
patch. 5520 AMS patch (p. B-44)
3 Uninstall the 5520 AMS client in the earlier 5520 AMS release. Section Uninstalling the
5520 AMS client in the earlier
5520 AMS release (p. B-44)
4 Uninstall the earlier 5520 AMS server. Procedure B-11 To uninstall

the earlier 5520 AMS server
after migration (p. B-45)
Uninstalling plug-ins after migration

Use the procedures in this section to uninstall plug-ins after migration. To uninstall
plug-ins from a running system, see Section 18.5 Uninstalling 5520 AMS NE
fixes (p. 18-5).
You can uninstall a plug-in using a script or manually.
Procedure B-8 To uninstall software plug-ins after migration
Before you proceed, you must be able to log in to the application server as amssys.
install_dir/ams/software/release/bin/ams_install.sh
where:
"Main" menu
i) Install
a) Activate
d) Deactivate
u) Uninstall
o) Overview
h) Help
q) Quit
Choice:
3 Type u and press .

(default)] ?
4 Type n and press .
(default)] :
To display only the plug-ins in the directory based on a filter, type the filter
text and press . For example, if you type 9.3.10 and press , only the plug-in
files containing 9.3.10 in the filename will be displayed.
To display all plug-ins in the directory, press .
Result: The script presents the uninstallation menu. The menu includes a
numbered list of installed plug-ins based on the filter, for example:
"Main > Uninstall" menu:
0 -Select-All-
1 plug-in filename
2 plug-in filename
x) Execute
q) Quit
Choice:
i Type the number corresponding to a plug-in you need to uninstall and press
.

Result: The menu is presented again, with the numbers for the plug-ins you
chose in square brackets ([ ]).
iii When you have chosen all the plug-ins you need to uninstall, type x and press
.
Summary:
- Selection:
list of plug-ins you chose
- Options:

(default)]? n
Are you sure you want to Uninstall [y|n (default)] ?
Result: The uninstallation proceeds, displaying success messages for each plug-in.
Result: The selected software plug-ins are uninstalled.
Proceed to: After all plug-ins have been uninstalled, perform one of the following tasks:
If you have installed a patch for the earlier 5520 AMS release, uninstall the patch.
See Procedure B-10 To uninstall a 5520 AMS patch (p. B-44).
If you have not installed a patch for the earlier 5520 AMS release, proceed to
uninstall the earlier 5520 AMS client. See Section Uninstalling the 5520 AMS client
in the earlier 5520 AMS release (p. B-44).
Procedure B-9 To uninstall a software plug-in manually after

migration
2 Perform the following to uninstall the plug-in:
i To run the uninstall script, type:
local_data_dir/ams/local/repository/plug-in_name/bin/uninsta
ll.sh
where:
plug-in_name is the name of the plug-in you want to uninstall.
Result: The script prompts you to confirm:
Are you sure you want to uninstall plug-in (y/n)?
ii Type y and press .
3 Repeat step 2 (p. B-43) for each plugin that needs to be uninstalled.
Result: The selected software plug-ins are uninstalled.
Proceed to: Perform one of the following tasks:
If you have installed a patch for the earlier 5520 AMS release, uninstall the patch.
See Procedure B-10 To uninstall a 5520 AMS patch (p. B-44).
If you have not installed a patch for the earlier 5520 AMS release, proceed to
uninstall the earlier 5520 AMS client. See Section Uninstalling the 5520 AMS client
in the earlier 5520 AMS release (p. B-44).
Uninstalling a 5520 AMS patch

Use Procedure B-10 To uninstall a 5520 AMS patch (p. B-44) to uninstall a
5520 AMS patch.
Procedure B-10 To uninstall a 5520 AMS patch

2 To deactivate a patch if installed, type:
local_data_dir/ams/local/repository/patch_name/bin/deactivate.sh

where:
patch_name is the name of the 5520 AMS patch you want to deactivate.
Result: The selected 5520 AMS patch is deactivated.
3 To uninstall the patch, type:
local_data_dir/ams/local/repository/patch_name/bin/uninstall.sh

where:
patch_name is the name of the 5520 AMS patch you want to uninstall.
Result: The selected 5520 AMS patch is uninstalled.
Proceed to: Uninstall the earlier 5520 AMS client. See Section Uninstalling the 5520 AMS
client in the earlier 5520 AMS release (p. B-44).
Uninstalling the 5520 AMS client in the earlier 5520 AMS release
Uninstall the 5520 AMS client in the earlier 5520 AMS release. See the 5520 AMS
Installation and Migration Guide for the applicable earlier 5520 AMS release.
Proceed to: Uninstall the earlier 5520 AMS server. See Procedure B-11 To uninstall
the earlier 5520 AMS server after migration (p. B-45).
Uninstalling the earlier 5520 AMS server after migration

Use Procedure B-11 To uninstall the earlier 5520 AMS server after migration (p.
B-45) to uninstall the earlier 5520 AMS server after migration.
Procedure B-11 To uninstall the earlier 5520 AMS server after

migration
1 Log in as root to the server on which the earlier 5520 AMS is installed.
2 To uninstall the 5520 AMS server, type:
install_dir/ams/software/earlier_release/bin/ams_uninstall
where:
install_dir is the software directory you chose during installation of the earlier 5520 AMS release;
by default, this is /opt.
earlier_release is the release of the earlier 5520 AMS software. An example is ams-9.3.10-999000.
Result: Status messages indicate the progress in deleting the software from the
server.
If all uninstallation tasks are performed, you have completed the migration of an
earlier 5520 AMS release to the 5520 AMS Release 9.4.
Rolling back to the earlier 5520 AMS release

Pre-requisite: Ensure that the pre-requisite has been completed:
Manual in-place migration from the earlier Importing GUI settings Section
5520 AMS release to the 5520 AMS, Importing GUI
Release 9.4 settings (p.
B-39)
If the migration to 5520 AMS, Release 9.4 is unsuccessful, you can roll back to the
earlier 5520 AMS release.
Stopping the 5520 AMS Release 9.4 servers

Use Procedure B-12 To stop a server in a simplex setup or all servers in a cluster
setup (p. B-46) to stop the 5520 AMS, Release 9.4 server in a simplex setup or all
5520 AMS, Release 9.4 servers in a cluster setup.
Before you proceed, you must be able to log in to the 5520 AMS servers as amssys.
Procedure B-12 To stop a server in a simplex setup or all servers in

a cluster setup
1 Log in to the 5520 AMS Release 9.4 server as amssys.
To stop a server in a simplex setup, type:
ams_server stop
Result: The 5520 AMS server is stopped.
To stop all servers in a cluster setup, type:
ams_cluster stop
Result: All servers in the 5520 AMS cluster are stopped.
Proceed to: Activate the earlier 5520 AMS release servers. See Activating the earlier
5520 AMS release servers (p. B-46).
Activating the earlier 5520 AMS release servers

Pre-requisite: Stopping the Release servers. See Stopping the 5520 AMS Release 9.4
servers (p. B-45).
Use Procedure B-13 To activate a server (p. B-46) to activate the earlier 5520 AMS
release servers. In a cluster, you must activate the earlier 5520 AMS release on each
server in the cluster.
Before you proceed, you must be able to log in to the servers as root.
Procedure B-13 To activate a server

1 Log in to the earlier 5520 AMS release server as root.
where:
install_dir is the software directory you chose during installation; by default, this is /opt
Result: The 5520 AMS server is activated.
Proceed to: Start the earlier 5520 AMS release servers. See Starting the earlier
5520 AMS release servers (p. B-47).
Starting the earlier 5520 AMS release servers

Pre-requisite: Activate the earlier 5520 AMS release servers. See Activating the
earlier 5520 AMS release servers (p. B-46).
Use Procedure 17-2 To delete the former site of the earlier 5520 AMS release (p.
17-5) to start the earlier 5520 AMS release server.
In case of a cluster setup, start the 5520 AMS servers in the following order:
Arbiter server, if applicable
Preferred data server
Non-preferred data server
Application servers (the application server that is started first becomes the master
application server)
In case of a geographically redundant setup, start the 5520 AMS servers in the
following order:
Arbiter server at the active site, if applicable
Preferred data server at the active site
Non-preferred data server at the active site, if applicable
Application servers at the active site (the application server that is started first at
the active site becomes the master application server)
Arbiter server at the standby site, if applicable
Preferred data server at the standby site
Non-preferred data server at the standby site, if applicable
Application servers at the standby site
Before you proceed, you must be able to log in to the server as amssys.
Procedure B-14 To start a server
Note It can take up to 15 minutes to fully start all 5520 AMS server
processes. Because client connections are not accepted until the server
is fully started, there will be a significant delay between issuing the
ams_server start command with this procedure, and the ability to log in
with a 5520 AMS client.
1 Log in to the earlier 5520 AMS release server as amssys.
ams_server start
Result: The earlier 5520 AMS release server is started.
Note Repeat steps 1 (p. B-47) and 2 (p. B-47) in each 5520 AMS
server in the cluster or geographically redundant setup.
You have completed the tasks to roll back to an earlier 5520 AMS release from the
5520 AMS, Release 9.4.
Customer documentation and product support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at
alcatel-lucent.com. If you are a new user and require access to this
service, please contact your Alcatel-Lucent sales representative.
Technical Support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
2015 Alcatel-Lucent. All rights reserved.
3JL-01001-BFAA-RJZZA Edition 04

3JL01001BFAARJZZA - V1 - 5520 AMS Release 9.4 Installation and Migration Guide

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3JL01001BFAARJZZA - V1 - 5520 AMS Release 9.4 Installation and Migration Guide

Загружено:

Авторское право:

Доступные форматы

Alcatel-Lucent 5520

ACCESS MANAGEMENT SYSTEM| RELEASE 9.4

Copyright 2015 Alcatel-Lucent.

Conventions used in this guide

Table 1 Documentation conventions

Convention Description Examples

Key name Identifies a keyboard key Delete

Italics Identifies a variable hostname

Key+Key Type the appropriate consecutive keystroke sequence. CTRL+G

Press the Return or Enter key. Press

An em dash in a table cell indicates that there is no

Indicates a submenu FileSave

(p. x-y) Indicates the page number. (p. 1-2)

Warning Warning indicates that the described task or situation

Caution Caution indicates that the described task or situation may,

iv August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

Note Note provides information that is, or may be, of special

Applies to The Applies to note indicates that the described task or

Procedure 1 Example of NE navigation convention

2 Right-click object and choose menu item.

Procedures with options or substeps

Procedure 2 Example of options in a procedure

This is one option.

2 You must perform this step.

Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 v

Procedure 3 Example of substeps in a procedure

i This is the first substep.

ii This is the second substep.

iii This is the third substep.

2 You must perform this step.

Multiple PDF file search

Procedure 4 To search multiple PDF files for a term

3 Enter the term to search for.

4 Select the All PDF Documents in option.

5 Choose the folder in which to search using the drop-down menu.

6 Select the following search criteria, if required:

Whole words only

vi August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

Note After you click on a hyperlink, right-click and choose Previous

1 Whats new 1-1

Installing the 5520 AMS

3 5520 AMS installation overview 3-1

4 Setting up 5520 AMS infrastructure 4-1

iv August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

5 Downloading software for the 5520 AMS and 5529 Enhanced

6 Installing the 5520 AMS solution components 6-1

7 Activating, starting and stopping the servers 7-1

Alcatel-Lucent 5520 Access Management System, Release 9.4 August 2015 v

Procedure 7-4 To stop a server ................................................... 7-4

8 Configuring the 5520 AMS to support NAT 8-1

9 Converting a simplex installation to a cluster 9-1

10 Configuring geographic redundancy 10-1

11 Updating firewall rules 11-1

12 Installing the 5520 AMS client 12-1

vi August 2015 Alcatel-Lucent 5520 Access Management System, Release 9.4

12.2 Installing a single 5520 AMS client .................................................. 12-4

Migrating to the 5520 AMS, Release 9.4

13 Migrating to the 5520 AMS, Release 9.4 13-1

14 Migration scenarios and associated task list 14-1

14.1 Overview of the migration scenarios ............................................... 14-2

15 Pre-migration tasks 15-1

16 Migration tasks 16-1

17 Post-migration tasks 17-1