5520 AMS Release 9 7 Installation and Migration Guide

Prévia do material em texto

Nokia — Proprietary and confidential
Use pursuant to applicable agreements
 
5520 Access Management System, 
Release 9.7
Installation and Migration Guide
3JL-01001-BTAA-RJZZA
Issue: 01
March 2019
Installation and Migration Guide
2
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Nokia is a registered trademark of Nokia Corporation. Other products and company 
names mentioned herein may be trademarks or tradenames of their respective 
owners.
The information presented is subject to change without notice. No responsibility is 
assumed for inaccuracies contained herein.
© 2019 Nokia.
Contains proprietary/trade secret information which is the property of Nokia and must 
not be made available to, or copied or used by anyone outside Nokia without its 
written authorization. Not to be used or disclosed except in accordance with 
applicable agreements.
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 3
 
Table of contents
1 Preface...........................................................................................19
1.1 Documentation ..........................................................................................19
1.2 Conventions used in this guide..................................................................20
1.2.1 Important information.................................................................................20
1.2.2 Navigation steps ........................................................................................21
1.2.3 Procedures with options or substeps.........................................................21
1.3 Multiple PDF file search.............................................................................22
1.4 Contact information ...................................................................................23
Getting started
2 What’s new ....................................................................................27
2.1 What’s new in Release 9.7 ........................................................................27
2.2 What’s new in Release 9.6.07 ...................................................................28
2.3 What’s new in Release 9.6.05 ...................................................................30
2.4 What’s new in Release 9.6.03 ...................................................................30
2.5 What’s new in Release 9.6 ........................................................................31
2.6 What’s new in Release 9.5 ........................................................................33
2.7 What’s new in Release 9.4 ........................................................................35
2.8 What’s new in Release 9.3.10 ...................................................................36
2.9 What’s new in Release 9.3.0 .....................................................................37
2.10 What’s new in Release 9.2.30 ...................................................................38
3 Overviews......................................................................................41
3.1 Guide overview..........................................................................................41
3.2 Installation and migration overview ...........................................................41
3.2.1 Installation terms .......................................................................................42
3.2.2 Environment variables ...............................................................................44
3.2.3 Path variables............................................................................................45
3.2.4 5520 AMS server roles ..............................................................................46
3.2.5 Simplex (standalone) installation...............................................................47
3.2.6 Clusters: redundancy and load-balancing .................................................47
3.2.6.1 Database replication..................................................................................48
3.2.6.2 Shared data replication..............................................................................48
3.2.7 Sites: geographic redundancy ...................................................................49
3.2.8 Using the 5520 AMS with a NAT server ....................................................51
3.3 5529 Enhanced Applications .....................................................................51
3.4 Technical support ......................................................................................51
Installing the 5520 AMS
4 5520 AMS installation overview ..................................................55
4.1 Simplex installation overview.....................................................................55
4.1.1 Server installation tasks.............................................................................56
4.2 Cluster installation overview......................................................................57
4.2.1 Overview....................................................................................................57
4.2.2 Cluster installation tasks............................................................................60
4.3 Geographic redundancy installation overview...........................................61
4
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4.3.1 Site components........................................................................................62
4.3.2 Site configuration.......................................................................................62
4.3.3 Health state of a 5520 AMS system ..........................................................62
4.3.4 Loss of a site .............................................................................................63
4.3.4.1 Configuring a script to run upon loss of a site ...........................................63
4.3.4.2 Manual site switchover ..............................................................................63
4.3.4.3 Automatic site switchover ..........................................................................63
4.3.4.4 Ping-pong protection .................................................................................64
4.3.4.5 Automating site switchover using an OSS arbiter .....................................65
4.3.5 Geographic redundancy installation tasks.................................................66
4.4 Software plug-in installation overview .......................................................66
4.4.1 Installing and activating software plug-ins .................................................67
4.4.2 Deactivating software plug-ins...................................................................67
4.5 Patch installation overview ........................................................................68
4.5.1 Installing and activating patches................................................................68
4.5.2 Deactivating patches .................................................................................71
4.6 Emergency fix installation overview...........................................................72
4.6.1 Installing and activating emergency fixes ..................................................73
4.6.2 Deactivating emergency fixes....................................................................74
5 Setting up 5520 AMS infrastructure............................................77
5.1 Setting up the 5520 AMS infrastructure.....................................................77
5.1.1 5520 AMS server requirements in a simplex setup ...................................77
5.1.2 5520 AMS server requirements in a cluster setup.....................................78
5.2 Configuring NTP........................................................................................79
5.3 Configuring storage ...................................................................................82
5.3.1Configuring LVM volumes .........................................................................82
5.4 User and group IDs ...................................................................................84
5.5 Configuring locale settings ........................................................................85
5.6 SSH session timeouts ...............................................................................86
6 Downloading software for the 5520 AMS and 
5529 Enhanced Applications .......................................................87
6.1 Downloading software for the 5520 AMS and 5529 Enhanced 
Applications ...............................................................................................87
6.2 Extracting the downloaded installation files...............................................89
7 Installing the 5520 AMS solution components ..........................91
7.1 Installing the 5520 AMS solution overview................................................91
7.2 Pre-requisite tasks.....................................................................................92
7.3 Installing the 5520 AMS solution ...............................................................94
7.4 Saving the configuration settings for installation of a 5520 AMS 
server.......................................................................................................113
7.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced Applications and 
plug-ins, and patches and emergency fixes ............................................115
7.5.1 5520 AMS NE plug-in software file..........................................................116
7.5.2 Patch software file ...................................................................................116
7.5.3 Emergency fix software file......................................................................117
7.5.4 5529 Enhanced Applications and plug-ins software file ..........................117
7.5.5 Nokia Access Virtualizer Adaptor plug-ins software file ..........................117
7.5.6 Installing and activating the 5520 AMS solution components .................118
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 5
 
7.5.7 Deactivating the 5520 AMS solution components ...................................124
7.5.8 Installing, activating or deactivating the 5520 AMS solution 
components .............................................................................................127
7.6 Verifying the installed software components on the 5520 AMS 
server.......................................................................................................129
7.7 Modifying the parameter values in the configuration file .........................131
8 Activating, starting and stopping the servers .........................133
8.1 Activating, starting and stopping the servers...........................................133
9 Configuring the 5520 AMS to support NAT..............................137
9.1 Configuring the 5520 AMS to support NAT ............................................137
10 Converting a simplex installation to a cluster .........................139
10.1 Converting a simplex installation to a cluster ..........................................139
10.2 Adding and removing servers..................................................................142
10.2.1 Adding servers.........................................................................................142
10.2.2 Removing servers....................................................................................144
10.3 Redistributing management of NEs.........................................................146
10.3.1 Export NE data from the old server and import it to the new server........146
10.3.2 Move AMS backup from old server to new server, and reduce data.......148
10.4 Convert a cluster with single NIC to inter-cluster.....................................151
11 Configuring geographic redundancy........................................153
11.1 Overview..................................................................................................153
11.2 Ping-pong protection ...............................................................................153
11.3 Configuring geographic redundancy........................................................154
11.4 Configuring the OSS arbiter ....................................................................159
11.5 Modifying geographic redundancy...........................................................161
11.5.1 Triggering a forced full synchronization of shared data...........................164
12 Updating firewall rules ...............................................................167
12.1 Overview..................................................................................................167
12.2 Updating firewall rules .............................................................................167
13 Installing the 5520 AMS client ...................................................169
13.1 Client installation overview ......................................................................169
13.1.1 Shared client installation..........................................................................169
13.1.1.1 Shared client installation in Red Hat Enterprise Linux.............................170
13.1.1.2 Shared client software updates in Red Hat Enterprise Linux ..................171
13.1.1.3 Client software updates in Windows........................................................171
13.1.2 Client installation tasks ............................................................................171
13.2 Installing multiple 5520 AMS clients ........................................................172
13.3 Installing a single 5520 AMS client..........................................................172
13.4 Installing a shared 5520 AMS client ........................................................175
13.4.1 Individual work spaces with a shared client.............................................179
13.5 Launching and updating the 5520 AMS client .........................................183
13.6 Automatic client upgrade during patch and emergency fix 
installation................................................................................................191
13.6.1 Saving the current 5520 AMS GUI ..........................................................191
13.6.2 Roll back to an earlier version of the 5520 AMS GUI ..............................191
13.7 Changing passwords for default users in the 5520 AMS GUI .................191
6
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
13.8 Adding a license to the 5520 AMS ..........................................................192
13.8.1 License installation error scenarios .........................................................194
14 5520 AMS server maintenance ..................................................197
14.1 Overview..................................................................................................197
Migrating to the 5520 AMS, Release 9.7
15 Migrating to the 5520 AMS, Release 9.7 ...................................201
15.1 Migration overview...................................................................................202
15.1.1 In-place migration ....................................................................................204
15.1.1.1 Automated in-place migration..................................................................204
15.1.1.2 Manual in-place migration .......................................................................206
15.1.2 Out-of-place migration .............................................................................206
15.2 Installing the 5520 AMS, Release 9.7 on the same server running 
an earlier 5520 AMS release ...................................................................207
15.3 Migrating NEs..........................................................................................20715.4 Migration dependencies of the data migration script ...............................207
15.4.1 Data not migrated from the earlier 5520 AMS release ............................207
15.5 Updating software plug-ins to a new version...........................................208
15.6 External TL1 Gateway migration .............................................................209
15.7 Migration with a customized keystore......................................................209
15.8 Migrating templates .................................................................................209
15.9 Migrating licenses....................................................................................209
16 Migration scenarios and associated task list ..........................211
16.1 Overview of the migration scenarios .......................................................211
16.2 Automated in-place migration from an earlier 5520 AMS release to 
the 5520 AMS, Release 9.7.....................................................................212
16.3 Out-of-place migration from an earlier 5520 AMS release to the 
5520 AMS, Release 9.7...........................................................................213
16.3.1 Out-of-place simplex migration................................................................214
16.3.2 Out-of-place cluster migration .................................................................215
16.3.3 Out-of-place geographically redundant migration....................................216
16.4 Checking the consistency of alarm rules after migration .........................218
17 Pre-migration tasks ...................................................................219
17.1 Overview of the pre-migration tasks ........................................................219
17.2 Transferring the 5520 AMS software to the 5520 AMS servers ..............219
17.3 Server configuration overview .................................................................220
17.4 Installing the 5520 AMS, Release 9.7 for migration ................................220
17.5 Installing the 5520 AMS solution software components for 
migration..................................................................................................245
17.6 Rollback scenarios ..................................................................................249
18 Migration tasks ...........................................................................253
18.1 Overview of the migration tasks ..............................................................253
18.2 Migrating the switchover script ................................................................254
18.3 Enabling SSL...........................................................................................255
18.4 Enabling geographic redundancy ............................................................256
18.5 Backing up the 5520 AMS database for an out-of-place migration .........260
18.6 Transfer the backup file of 5520 AMS database to the new server.........261
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 7
 
18.7 Copying data files from the earlier 5520 AMS release to the 
5520 AMS, Release 9.7...........................................................................262
18.7.1 Copying data files from a backup file in an out-of-place migration 
scenario ...................................................................................................263
18.8 Starting the 5520 AMS, Release 9.7 servers ..........................................267
18.8.1 Sequence of starting the 5520 AMS, Release 9.7 servers in cluster 
setups and geographically redundant setups ..........................................268
18.9 Adding licenses to the 5520 AMS, Release 9.7 installation ....................273
18.10 Installing the 5520 AMS, Release 9.7 client ............................................273
18.11 Launching the 5520 AMS, Release 9.7 client..........................................273
18.12 Updating the anonymous FTP user path.................................................274
19 Post-migration tasks ..................................................................277
19.1 Overview of the post-migration tasks ......................................................277
19.2 Migrating ONT SIP data ..........................................................................277
19.3 Importing GUI settings.............................................................................278
19.4 Deleting the former site of the earlier 5520 AMS release........................279
Uninstalling the 5520 AMS
20 Uninstalling 5520 AMS components.........................................285
20.1 Uninstalling 5520 AMS components overview ........................................285
20.2 Uninstalling software plug-ins..................................................................285
20.3 Uninstalling patches ................................................................................286
20.4 Uninstalling emergency fixes...................................................................287
20.5 Uninstalling 5520 AMS NE plug-ins, 5529 Enhanced Applications 
and plug-ins, and patches and emergency fixes .....................................288
20.6 Uninstalling a 5520 AMS client................................................................292
20.7 Uninstalling the 5520 AMS server ...........................................................293
Appendix
21 Examples of the installation and activation of the 5520 
AMS solution...............................................................................299
21.1 To install and activate the 5520 AMS solution in a simplex setup...........299
21.2 To install and activate NE Plug-in............................................................300
21.3 To install the 5529 Enhanced Applications..............................................301
22 Manual in-place migration procedures.....................................303
22.1 Overview of the manual in-place migration scenarios .............................303
22.1.1 Migration path and strategy .....................................................................303
22.2 Manual in-place migration associated task list ........................................304
22.2.1 Migrate a simplex installation ..................................................................304
22.2.2 Migrate a cluster installation ....................................................................305
22.2.3 Migrate a geographically redundant installation ......................................307
22.3 Pre-migration tasks for manual in-place migration ..................................310
22.3.1 Installing the 5520 AMS, Release 9.7 for migration (In-place-
manual)....................................................................................................310
22.3.2 Installing the 5520 AMS solution software components for 
migration..................................................................................................325
22.3.3 Backing up the 5520 AMS database .......................................................325
22.4 Migration tasks for manual in-place migration .........................................326
8
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
22.4.1 Stopping the earlier 5520 AMS release servers ......................................326
22.4.2 Disabling SSL..........................................................................................327
22.4.3 Migrating the switchover script ................................................................328
22.4.4 Activating the 5520 AMS, Release 9.7 servers .......................................329
22.4.5 Activating the 5520 AMS software plug-ins .............................................330
22.4.6 Enabling SSL...........................................................................................333
22.4.7 Enabling geographic redundancy ............................................................33422.4.8 Copying data files from the earlier 5520 AMS release to the 5520 
AMS, Release 9.7....................................................................................334
22.4.8.1 Copying data files from a previous release in an in-place migration 
scenario ...................................................................................................335
22.4.9 Starting the 5520 AMS, Release 9.7 servers ..........................................339
22.4.10 Adding licenses to the 5520 AMS, Release 9.7 installation ....................340
22.4.11 Installing the 5520 AMS, Release 9.7 client ............................................340
22.4.12 Launching the 5520 AMS, Release 9.7 client..........................................340
22.4.13 Updating the anonymous FTP user path.................................................341
22.5 Post-migration tasks ................................................................................341
22.5.1 Importing GUI settings.............................................................................342
22.5.2 Uninstalling the earlier 5520 AMS release ..............................................342
22.5.2.1 Uninstalling plug-ins after migration ........................................................343
22.5.2.2 Uninstalling a 5520 AMS patch ...............................................................347
22.5.3 Uninstalling the 5520 AMS client in the earlier 5520 AMS release .........348
22.5.4 Uninstalling the earlier 5520 AMS server after migration ........................348
22.5.5 Rolling back to the earlier 5520 AMS release .........................................349
22.5.5.1 Stopping the 5520 AMS Release 9.7 servers..........................................349
22.5.5.2 Activating the earlier 5520 AMS release servers.....................................350
22.5.5.3 Starting the earlier 5520 AMS release servers........................................350
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 9
 
List of figures
3 Overviews......................................................................................41
Figure 1 Simplex (standalone) installation of the 5520 AMS...................................47
Figure 2 Cluster installation of the 5520 AMS .........................................................48
Figure 3 Simplest geographic redundancy installation of the 5520 AMS ................49
Figure 4 Typical geographic redundancy installation of the 5520 AMS...................50
4 5520 AMS installation overview ..................................................55
Figure 5 Geographic redundancy installation of the 5520 AMS with an OSS 
arbiter ........................................................................................................65
5 Setting up 5520 AMS infrastructure............................................77
Figure 6 Volume setup on Red Hat Enterprise Linux systems ................................83
10
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 11
 
List of tables
1 Preface...........................................................................................19
Table 1 Documentation conventions ......................................................................20
2 What’s new ....................................................................................27
Table 2 What’s new in Release 9.7 ........................................................................27
Table 3 What’s new in Release 9.6.07 ...................................................................28
Table 4 What’s new in Release 9.6.05 ...................................................................30
Table 5 What’s new in Release 9.6.03 ...................................................................30
Table 6 What’s new in Release 9.6 ........................................................................32
Table 7 What’s new in Release 9.5 ........................................................................33
Table 8 What’s new in Release 9.4 ........................................................................35
Table 9 What’s new in Release 9.3.10 ...................................................................36
Table 10 What’s new in Release 9.3.0 .....................................................................37
Table 11 What’s new in Release 9.2.30 ...................................................................38
3 Overviews......................................................................................41
Table 12 Key terms ..................................................................................................42
Table 13 Environment variables ...............................................................................45
Table 14 Path variables............................................................................................45
4 5520 AMS installation overview ..................................................55
Table 15 User accounts............................................................................................56
Table 16 Install the 5520 AMS, Release 9.7 in a simplex (standalone) 
configuration ..............................................................................................56
Table 17 UNIX user accounts...................................................................................60
Table 18 Install the 5520 AMS in a cluster configuration .........................................60
Table 19 Scenarios for geographically redundant switchover ..................................64
Table 20 Install the 5520 AMS, Release 9.7 in a geographically redundant 
installation..................................................................................................66
Table 21 Install and activate a software plug-in .......................................................67
Table 22 Deactivate a software plug-in ....................................................................67
Table 23 Install the 5520 AMS patches - cases .......................................................69
Table 24 Install and activate a 5520 AMS patch ......................................................69
Table 25 Deactivating the 5520 AMS patches - cases.............................................71
Table 26 Deactivate a 5520 AMS patch ...................................................................71
Table 27 Install and activate an emergency fix ........................................................74
Table 28 Deactivate an emergency fix .....................................................................74
5 Setting up 5520 AMS infrastructure............................................77
Table 29 Configure NTP on Red Hat Enterprise Linux systems ..............................79
7 Installing the 5520 AMS solution components ..........................91
Table 30 Pre-requisite tasks for installing the 5520 AMS.........................................92
Table 31 Installation result......................................................................................110
Table 32 Activation result .......................................................................................111
Table 33 Install and activate the 5520 AMS solution components .........................118
Table 34 Deactivate the 5520 AMS solution components......................................124
12
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
10 Converting a simplex installation to a cluster .........................139
Table 35 Convert from a simplex installation to a cluster .......................................139
Table 36 High-level procedure for splitting AMS ....................................................149
11 Configuring geographic redundancy........................................153
Table 37 Modify geographic redundancy ...............................................................162
13 Installing the 5520AMS client ...................................................169
Table 38 Types of client installation .......................................................................169
Table 39 Install the 5520 AMS client ......................................................................172
Table 40 License installation from the 5520 AMS server .......................................194
Table 41 License installation error scenarios .........................................................195
15 Migrating to the 5520 AMS, Release 9.7 ...................................201
Table 42 Supported migration path and data migration strategy............................203
Table 43 Data not migrated from the earlier 5520 AMS release to the 
5520 AMS, Release 9.7...........................................................................208
Table 44 Updating a software plug-in to a new version..........................................208
16 Migration scenarios and associated task list ..........................211
Table 45 Migration path and data migration strategy for automated in-place 
and out-of-place migrations .....................................................................212
Table 46 Automated in-place migration path and data migration strategy .............212
Table 47 Automated in-place migration for simplex, cluster, and 
geographical redundant installations .......................................................212
Table 48 Out-of-place migration path and data migration strategy ........................213
Table 49 Simplex migration - Out-of-place .............................................................214
Table 50 Cluster migration - Out-of-place ..............................................................215
Table 51 Geographically redundant migration - Out-of-place.................................216
17 Pre-migration tasks ...................................................................219
Table 52 Migration result ........................................................................................236
Table 53 Activation result .......................................................................................237
18 Migration tasks ...........................................................................253
Table 54 Start sequence of the 5520 AMS, Release 9.7 servers in cluster 
setups ......................................................................................................268
Table 55 Start sequence of the 5520 AMS, Release 9.7 servers in 
geographically redundant setups.............................................................269
20 Uninstalling 5520 AMS components.........................................285
Table 56 Uninstalling the software plug-ins - cases ...............................................286
Table 57 Uninstall a software plug-in .....................................................................286
Table 58 Uninstalling the 5520 AMS patches - cases ............................................286
Table 59 Uninstall a 5520 AMS patch ....................................................................287
Table 60 Uninstalling the emergency fixes - cases ................................................287
Table 61 Uninstall an emergency fix ......................................................................288
Table 62 Uninstall the 5520 AMS solution components .........................................288
21 Examples of the installation and activation of the 5520 
AMS solution...............................................................................299
Table 63 Result of installation of standalone server in a simplex setup .................300
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 13
 
22 Manual in-place migration procedures.....................................303
Table 64 In-place migration path and data migration strategy (manual) ................304
Table 65 Simplex installation migration - In-place (manual)...................................304
Table 66 Cluster migration - In-place (manual) ......................................................306
Table 67 Geographically redundant migration - In-place (manual) ........................308
Table 68 Migration result ........................................................................................323
Table 69 Activation result .......................................................................................324
Table 70 Uninstall the earlier 5520 AMS release after migrating to the 
5520 AMS, Release 9.7...........................................................................343
14
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 15
 
List of procedures
1 Preface...........................................................................................19
Procedure 1 Example of NE navigation convention.......................................................21
Procedure 2 Example of options in a procedure ............................................................22
Procedure 3 Example of substeps in a procedure .........................................................22
Procedure 4 To search multiple PDF files for a term .....................................................23
3 Overviews......................................................................................41
Procedure 5 To find contact information for technical assistance..................................52
5 Setting up 5520 AMS infrastructure............................................77
Procedure 6 To prepare the 5520 AMS infrastructure ...................................................78
Procedure 7 To configure an NTP server on Red Hat Enterprise Linux systems ..........80
Procedure 8 To configure an NTP client on Red Hat Enterprise Linux systems............81
Procedure 9 To configure NTP clients to access the NTP Server on Red Hat 
Enterprise Linux systems ..........................................................................81
Procedure 10 To configure LVM volumes........................................................................83
Procedure 11 To configure the locale settings.................................................................85
6 Downloading software for the 5520 AMS and 
5529 Enhanced Applications .......................................................87
Procedure 12 To download software ...............................................................................87
Procedure 13 To verify the MD5 hash value....................................................................88
Procedure 14 To extract the downloaded installation file to a new directory ...................89
7 Installing the 5520 AMS solution components ..........................91
Procedure 15 To install and activate the 5520 AMS solution...........................................94
Procedure 16 To manually configure sudo ....................................................................113
Procedure 17 To save the configuration settings for the installation of a 
5520 AMS server.....................................................................................114
Procedure 18 To install the 5520 AMS NE plug-ins, 5529 Enhanced Applications 
and plug-ins, and patches and emergency fixes together or individually 119
Procedure 19 To activate the 5520 AMS NE plug-ins, 5529 Enhanced 
Applications and plug-ins, and patches and emergency fixes together or 
individually ...............................................................................................122
Procedure 20 To deactivate the 5520 AMS NE plug-ins, 5529 Enhanced 
Applications and plug-ins, and patches and emergency fixes together or 
individually ...............................................................................................125
Procedure 21 To install, activate, install and activate, or deactivate the 5520 AMS 
solution components................................................................................127Procedure 22 To verify the installed software components ...........................................129
8 Activating, starting and stopping the servers .........................133
Procedure 23 To activate a server .................................................................................133
Procedure 24 To start a server ......................................................................................133
Procedure 25 To start a cluster......................................................................................134
Procedure 26 To stop a server.......................................................................................135
Procedure 27 To stop a cluster ......................................................................................135
16
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
9 Configuring the 5520 AMS to support NAT..............................137
Procedure 28 To configure the 5520 AMS to support NAT............................................137
10 Converting a simplex installation to a cluster .........................139
Procedure 29 To convert a simplex server to a cluster server.......................................140
Procedure 30 To configure a newly added application server in a site in the 
5520 AMS GUI ........................................................................................142
Procedure 31 To update the SSH key of a server in a cluster .......................................143
Procedure 32 To remove an application server from a cluster ......................................144
Procedure 33 To split NE data .......................................................................................146
Procedure 34 To convert a cluster with single NIC to inter-cluster ................................151
Procedure 35 To cleanup old alarms from the database ...............................................152
11 Configuring geographic redundancy........................................153
Procedure 36 To overrule ping-pong protection.............................................................154
Procedure 37 To configure data replication between sites ............................................155
Procedure 38 To configure the 5520 AMS to run a script if one site is down ................158
Procedure 39 To configure the OSS arbiter in a geographically redundant 
installation................................................................................................159
Procedure 40 To start the OSS arbiter in a geographically redundant installation ........161
Procedure 41 To switch between the active and standby site .......................................162
Procedure 42 To change a geographically redundant installation to two 
independent sites ....................................................................................163
Procedure 43 To trigger a forced full synchronization of shared data............................164
12 Updating firewall rules ...............................................................167
Procedure 44 To update firewall rules ...........................................................................168
13 Installing the 5520 AMS client ...................................................169
Procedure 45 To install a single 5520 AMS client in Windows/Red Hat Enterprise 
Linux System...........................................................................................173
Procedure 46 To install a shared client in Windows ......................................................175
Procedure 47 To install a shared 5520 AMS client in Red Hat Enterprise Linux ...........177
Procedure 48 To install a shared client with the shared client wrapper .........................180
Procedure 49 To configure the presentation server and login title to use the 
shared client wrapper ..............................................................................181
Procedure 50 To launch and update the 5520 AMS client.............................................184
Procedure 51 To update permissions for the plug-ins directory.....................................189
Procedure 52 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 ........................................................................................................189
Procedure 53 To display hours in the 0 to 24 convention in the 5520 AMS client .........190
Procedure 54 To change a default user password in the 5520 AMS GUI .....................192
Procedure 55 To add a license key from the 5520 AMS GUI ........................................193
Procedure 56 To add a license key from the 5520 AMS server.....................................194
14 5520 AMS server maintenance ..................................................197
Procedure 57 5520 AMS server maintenance in a cluster.............................................197
17 Pre-migration tasks ...................................................................219
Procedure 58 To install the 5520 AMS solution for migration ........................................222
Procedure 59 To install 5520 AMS solution software components for migration...........246
Installation and Migration Guide
Issue: 01 3JL-01001-BTAA-RJZZA 17
 
Procedure 60 Rollback in geographically redundant setup............................................249
Procedure 61 Rollback in cluster with single data server...............................................250
Procedure 62 Rollback in cluster without database switch ............................................250
Procedure 63 Rollback in cluster with database switch .................................................251
18 Migration tasks ...........................................................................253
Procedure 64 To migrate the switchover_hook.sh script ...............................................254
Procedure 65 To enable SSL with a customized keystore.............................................256
Procedure 66 To configure data replication between sites ............................................257
Procedure 67 To copy data files from a backup file (interactive mode) .........................263
Procedure 68 To copy data files from a backup file (non-interactive mode) ..................265
Procedure 69 To start a server ......................................................................................270
Procedure 70 To check the migration status..................................................................272
Procedure 71 To update the anonymous FTP user path ...............................................274
19 Post-migration tasks ..................................................................277
Procedure 72 To import GUI settings.............................................................................278
Procedure 73 To delete the former site of the earlier 5520 AMS release ......................280
20 Uninstalling 5520 AMS components.........................................285
Procedure 74 To uninstall the 5520 AMS NE plug-ins, 5529 Enhanced 
Applications and plug-ins, and patches and emergency fixes together or 
individually ...............................................................................................289
Procedure 75 To uninstall the earlier 5520 AMS client application in Windows ............292
Procedure 76 To uninstall the 5520 AMS client application in Red Hat Enterprise 
Linux .......................................................................................................292
Procedure 77 To uninstall the 5520 AMS server ...........................................................294
22 Manual in-place migration procedures.....................................303
Procedure 78 To install the 5520 AMS solution for manual in-place migration..............310
Procedure 79 To stop a server in a simplex setup or all servers in a cluster setup .......327
Procedure 80 To disableSSL ........................................................................................328
Procedure 81 To activate a server .................................................................................329
Procedure 82 To activate a software plug-in..................................................................331
Procedure 83 To copy data files from the previous release (interactive mode) .............335
Procedure 84 To copy data files from the previous release (non-interactive mode)......337
Procedure 85 To uninstall software plug-ins after migration ..........................................344
Procedure 86 To uninstall a software plug-in manually after migration .........................346
Procedure 87 To uninstall a 5520 AMS patch................................................................347
Procedure 88 To uninstall the earlier 5520 AMS server after migration ........................348
Procedure 89 To stop a server in a simplex setup or all servers in a cluster setup .......349
Procedure 90 To activate a server .................................................................................350
Procedure 91 To start a server ......................................................................................351
18
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Preface
Issue: 01 3JL-01001-BTAA-RJZZA 19
 
1 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.
1.1 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.
The5520 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.
The 5520 AMS Northbound Interface Guide provides information about functions 
supported by the 5520 AMS NBI.
The 5520 AMS Glossary provides descriptions of 5520 AMS-related terms and 
acronyms.
The 5520 AMS and 5529 Enhanced Applications Alarm Search Tool provides 
information about the 5529 Enhanced Applications Alarms.
The 5520 AMS and 5529 Enhanced Applications Privacy Considerations provides 
information on the product features that impact privacy and the measures taken to 
protect such data.
Preface
20
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
1.2 Conventions used in this guide
The following table lists the conventions that are used in this guide.
Table 1 Documentation conventions
1.2.1 Important information
The following conventions are used to indicate important information:
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 
character” in a search argument.
An asterisk also indicates a default option for an NMTI 
parameter.
Path_analysis.*file
→ Indicates a submenu File→Save
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. 
Installation and Migration Guide Preface
Issue: 01 3JL-01001-BTAA-RJZZA 21
 
1.2.2 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 perspectives—expand, 
collapse, and choose objects
• Graphical View—double-click objects
• Search and Find utilities—enter 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.
1.2.3 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.
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.
Preface
22
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 2 Example of options in a procedure
At step 1, you can choose to perform one of the options provided in the unordered list. At step 2, 
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.
Procedure 3 Example of substeps in a procedure
At step 1, you must perform a series of substeps within a step. At step 2, 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.
1.3 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.
Installation and Migration Guide Preface
Issue: 01 3JL-01001-BTAA-RJZZA 23
 
Procedure 4 To search multiple PDF files for a term
1 Open Adobe Reader.
2 Choose Edit→Search 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.
Adobe Reader displays the search results. Click on the + symbol to expand the entries for 
each file.
1.4 Contact information
If you have questions or comments about this documentation, contact:
documentation.feedback@nokia.com
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.
Preface
24
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Getting started
Issue: 01 3JL-01001-BTAA-RJZZA 25
 
Getting started
2 What’s new
3 Overviews
Getting started
26
Installation and MigrationGuide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 27
 
2 What’s new
2.1 What’s new in Release 9.7
2.2 What’s new in Release 9.6.07
2.3 What’s new in Release 9.6.05
2.4 What’s new in Release 9.6.03
2.5 What’s new in Release 9.6
2.6 What’s new in Release 9.5
2.7 What’s new in Release 9.4
2.8 What’s new in Release 9.3.10
2.9 What’s new in Release 9.3.0
2.10 What’s new in Release 9.2.30
2.1 What’s new in Release 9.7
Table 2 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.7.
Table 2 What’s new in Release 9.7
Feature/enhancement Description See
New features/enhancements
Migration to 5520 AMS 
Release 9.7
Updated migration path to 5520 AMS, Release 9.7. Chapters 15, 16, 18, and 
22
Added information about --migrate script. Section 15.1.1.1
IGMP snooping Added information about IGMP snooping. Sub-section 4.2.1
Increase horizontal scaling Updated the procedure to configure a newly added application 
server in a site in the 5520 AMS GUI.
Procedure 30
Move AMS backup from 
old server to new server, 
and reduce data
Added high-level tasks for splitting the AMS into two systems. Section 10.3
(1 of 2)
What’s new
28
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
2.2 What’s new in Release 9.6.07
Table 3 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.6.07.
Table 3 What’s new in Release 9.6.07
GoldenEMSSwConfig file Updated information about “ams_install --cluster” script. Section 7.5
Updated the procedure to include a prompt for the location of 
the GoldenEMSSwConfig configuration file.
Procedure 58
Patch installation Updated the note about patch installation. Section 4.5
Default admin user Added a note on the default admin user which is not created 
after the 5520 AMS installation.
Procedure 15
Documentation changes
Configuring Sudo Modified the file name to 5520ams_sudoers. Procedure 16
Updated the option name to sudomanual in the ams.conf 
parameter AMS_OS_SERVICE_METHOD.
Procedure 15
Deactivation of 5529 
Enhanced applications
Added information on the deletion of user workspace directory 
for the deactivation of 5529 Enhanced applications.
Procedure 20
Cluster start and stop in 
maintenance mode
Updated the procedures to start a cluster and to stop a cluster. Procedure 25 and 27
Default SSL Added a note on default SSL in the application and data server. Procedure 15
Usage of standalone and 
(A+D)
Modified the instances of standalone (simplex) to simplex 
(standalone) and (A+D) to (AD).
Sections 3.2, 5.1, 11.2, 
14.1 and 17.3
Sub-sections 3.2.4, 3.2.5, 
4.1.1 and 4.2.1
Installation and Migration 
Script
Replaced the prompts for subnets with network interfaces. Procedures 15, 29, 58, 
and 78.
Installing the 5520 AMS Added a note on the client interface during the startup of the 
server.
Procedures 15, 58, and 
78
AMS client download and 
log in requirement post 
migration
Add a prerequisite for downloading and logging in to AMS client 
post migration.
Section 17.4
Feature/enhancement Description See
(2 of 2)
Feature/enhancement Description See
New features/enhancements
(1 of 2)
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 29
 
Security improvements for 
AMS database
Added an user account for amsdb user. Tables 15 and 17
Added amsdb user to the default user and group identifiers. Section 5.4
Added new environment variable $MYSQL_DATA to the table. Table 13
Updated the prompt to enter password for database user. Procedures 15, 58 and 
78
Added a note on amsdb user and group. Sub-section 22.5.5
CIS and STIG hardened 
platforms
Added information about CIS and STIG hardened RHEL 
platforms.
Section 3.2
Migration to 5520 AMS 
Release 9.6.07
Updated migration path to 5520 AMS, Release 9.6.07. Chapters 15, 16, 18, and 
22
Updated information about license migration. Section 15.9
RHEL version number Updated the RHEL version number to 6.x/7.x. Sections 3.2 and 15.1
Download of AMS client 
with authentication
Included information about the AMS client download with valid 
user credentials.
Sections 13.3 and 13.4
Procedures 45, 46, 47, 
and 48
Privacy Considerations Included the 5520 AMS and 5529 Enhanced Applications Privacy 
Considerations document to the related documentation section.
Section 1.1
Rework Database 
replication/Shared data 
replication
Included a prerequisite on rollback and prerequisite to ensure 
taking ams database backup before migration.
Section 15.1 and 16.1
Included information about server start sequence after migration 
and rollback in a cluster setup.
Table 47
Section 17.6
Updated steps and output for migration. Procedure 58
Updated the server start sequence of manual and automated 
migration in cluster and geographically redundant setups.
Table 54, 55, 50, and 66
Documentation changes
Windows server 2008 
presentation server
Removed information about activating the compatibility mode for 
Windows server 2008 presentation server.
Section 13.4
Disk space Included information about the prerequisite for migration. Section 17.4
LDAP dictionary update Added a prerequisite to update configuration file for LDAP users 
using authorization, from a release earlier than 9.6.
Section 17.4
Operating system 
reimaged in cluster
Added a procedure to update the SSH key of a server. Procedure 31
Migration in geographical 
redundant setup
Added a prerequisite to not perform migration on the
active and standby sites in parallel.
Section 17.4
Shell access permissions 
for AMS users
Updated the example on shell for AMS users for installation and 
activation of AMS in simplex.
Updated the installer prompt step on shell access for AMS users.
Section 21.1
Procedures 15, 58, and 
78
Feature/enhancement Description See
(2 of 2)
What’s new
30
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
2.3 What’s new in Release 9.6.05
Table 4 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.6.05.
Table 4 What’s new in Release 9.6.05
Notes
(1) To use this functionality, you must have Nokia Access Virtualizer Adaptor installed. Contact your Nokia technical representative for more 
information.
2.4 What’s new in Release 9.6.03
Table 5 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.6.03.
Table 5 What’s new in Release 9.6.03
Feature/enhancement Description See
New features/enhancements
Migration to 5520 AMS 
Release 9.6.05
Updated migration path to 5520 AMS, Release 9.6.05. Chapters 15, 16, 18 and 
22
Removed section for migration support between operating 
systems and architectures.
—
chroot configuration Added a pre-requisite to remove the chroot configuration for 
amssftp and amsftp user accounts before performing the rollback 
procedure.
Section 22.5.5
Nokia Access Virtualizer 
Adaptor software 
plug-ins(1)
Added information about the Nokia Access Virtualizer Adaptor 
software plug-ins used in the 5520 AMS.
Sub-section 7.5.5
Documentation changes
Modifying the parameter 
values in ams.conf file
Added a section to list the parameters that can be modified after 
the 5520 AMS installation.
Section 7.7
Windows server 2008 
presentation server
Added information about activating the compatibility mode for 
Windows server 2008 presentation server.
Section 13.4
Server in maintenance 
mode
Added key terms for ‘Application server maintenance mode’ and 
‘OS System maintenance mode’.
Updated the procedure for server maintenance in a cluster.
Table 12
Procedure 57
Feature/enhancement Description See
New features/enhancements
(1 of 2)
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 31
 
2.5 What’s new in Release 9.6
Table 6 lists the new 5520AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.6.
Migration to 5520 AMS 
Release 9.6.03
Updated migration path to 5520 AMS, Release 9.6.03. Chapters 7, 15, 16, 18, 
Appendix 22 and Section 
20.7
Updated the RHEL version number. Section 3.2
R9.6.03 release Updated the bin file format for Release 9.6.03. Procedure 15
Sub-section 7.5.1
AMS support server Updated the AMS support server.
Added x86_64 to Red Hat Enterprise Linux Versions
x86 server changed to Intel 64bit server.
Section 3.2
Configure the 5520 AMS 
so that all defaults are 
secure
The URL for the 5520 AMS client is updated with HTTPS as 
default.
Procedure 45, 46, 47 and 
48
Server maintenance Added a chapter on server maintenance Chapter 14
Documentation changes
5529 Enhanced 
Applications
Added a note on Nokia 5529 Enhanced Applications. Section 15.1
Pre-requisite task Updated table with pre-requisite that special characters are not 
supported in the directory name
Section7.2 
Naming criteria of the 
5520 AMS Server host 
name
Added the naming criteria of the 5520 AMS Server host
name as a pre-requisite task
Table 30
Automated in-place 
migration script execution
Added note about ensuring to follow the screen instructions while 
executing the automated scripts
Section 15.1.1.1 and 
Procedure 58
Required Red Hat 
Enterprise Linux packages
Added information about the pre-requisite for installing the 
required Red Hat Enterprise Linux packages.
Table 30
ams_server start Modified the note for ams_server start script. Procedure 69
Sequence of starting the 
data servers in a cluster
Updated the sequence of starting the data server in a cluster. Sub-sections 16.3.2 and 
22.2.2
Warning on the system 
running with adapted sysctl 
settings
Added a note on the warning that appears during AMS 
installation.
Procedure 15
Installing NE plug-ins Added a note on installing 5 or more NE plug-ins and increasing 
the allocated memory.
Section 13.5
LDAP authentication Added a pre-requisite on LDAP authentication. Section 17.4
Split brain condition Updated the note on split brain condition in case of geographically 
redundant cluster.
Section 4.2.1
Feature/enhancement Description See
(2 of 2)
What’s new
32
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 6 What’s new in Release 9.6
Feature/enhancement Description See
New features/enhancements
Migration to 5520 AMS 9.6 Updated migration path to 5520 AMS, Release 9.6 Chapters 15, 16, 
Appendix 22, Sections 
18.7, 20.7 and Procedure 
69.
Removed note on SSH sessions requiring superuser permissions 
to execute commands.
Section 15.1
OpenJDK version Updated the OpenJDK version to 1.8 Procedures 15 and 58
RHEL version number Updated the RHEL version number. Section 3.2
Convert cluster with single 
NIC to inter-cluster
Added information about converting a cluster with single NIC to 
inter-cluster.
Section 10.4
Documentation changes
Configuring sudo Modified the directory path. Procedure 16
Installation and Migration 
procedures
Updated the procedure to install and activate the 5520 AMS 
solution.
Procedure 15
Updated the procedure to install the 5520 AMS solution for 
migration.
Procedure 58
Pre-requisite table for 
installation
Deleted pre-requisite installations which are described in SCTG 
guide to avoid redundancy.
Table 30
Migration procedures Updated the procedure to disable geographic redundancy. Tables 51 and 67
External TL1 Gateway 
migration
Removed the content from External TL1 Gateway migration. Section 15.6
Unallocated space (free 
PE)
Updated the content regarding unallocated space (free PE). Table 30 and 
Seb-section 5.3.1
Geographically redundant 
migration
Added a note on geographically redundant standby site. Tables 51 and 67
Client installation Updated information for installing the 5520 AMS client. Sub-section 13.1.1.2, 
Section 13.5 and 
Procedures 45, 47, 48 
and 50
Shared Client Added information and a note on some constraints by the root 
user for shared client launch.
Sub-Section 13.1.1.1
Multiple client installation Added information on the Out of Memory error that occurs during 
the multiple client installation.
Section 13.2
Migration between 
operating systems
Added a note on no rollback support for migration between 
operating systems.
 —
Out-of-place migration Added a note on site configuration. Section 15.1.2
System user Added a note on ‘system’ user. Section 17.4
Parameter values Added a note about the configuration of parameter values in the 
*.conf files.
Section 17.4
To download software Updated the procedure to download software. Procedure 12
(1 of 2)
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 33
 
2.6 What’s new in Release 9.5
Table 7 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.5.
Table 7 What’s new in Release 9.5
Shared client Added information on shared client installation as non root user. Section 13.1.1.1
Uninstalling the 5520 AMS 
server
Added a note and updated procedure regarding deactivating the 
patch before the 5520 AMS migration.
Sections 20.7 and 22.5.4
ams_cluster stop|restart Added a note on ams_cluster where stop and restart script stop 
the servers in the 5520 AMS cluster in the maintenance mode.
Procedure 27
5520 AMS client Added a note about enabling cache on the last reachable server 
in a network.
Section 13.5
NIC configuration in a 
cluster setup
Added a note about NIC configuration in a cluster setup. Procedure 15
Feature/enhancement Description See
(2 of 2)
Feature/enhancement Description See
New features/enhancements
Migration to 5520 AMS 9.5 Updated migration path to 5520 AMS, Release 9.5. Chapters 15, 16, and 
Appendix 22
Kill Solaris client Removed references to Solaris from the guide. Entire guide
Automatic client software 
upgrade during Patch or 
Emergency fix installation
Added information about automatic 5520 AMS client software 
upgrade during patch or emergency fix installation.
Section 13.6
Tables 24 and 27
Discontinue Import/Export 
for Migration
Removed information about import and export option and added 
information about support of import or export on the same 
release.
Sections 17.1 and 15.6
Appendix 22.3
Sub-section 
Redistributing 
management of NEs
ams_cluster start|restart Added a note for starting a database server manually when the 
server is down due to split brain condition.
Sub-section Overview
GSIP 5.0 Support Added the latest GSIP version supported. Section 19.2
5520 AMS restart event Added information about the behavior of 5520 AMS restart event. Sub-sections Server 
installation tasks, Cluster 
installation tasks, and 
Geographic redundancy 
installation tasks
Change of database from 
MYSQL to MariaDB
Updated instances of the term ‘MYSQL’ to the generic term 
‘Database’.
Sections 3.2, 4.1, 4.2, 
4.3, 7.3, 10.1, 11.3, 17.1, 
18.4, 21.1, 22.3, and 22.4
(1 of 2)
What’s new
34
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
SSH session timeout Added a new section for SSH session timeout.
Added a note regarding SSH sessions.
Section 5.6, Procedure 
77
Documentation changes
Support of encryption by 
the Web Browser
Added a note about the Web Browser support for encryption. Section 3.2
Geo-redundant switchover Added information about determining geographically redundant 
switchover.
Sub-section Health state 
of a 5520 AMS system
Table 19
Patch uninstallation Added a note for deactivating a patch before activating a newer 
release of 5520 AMS during migration.
Sub-section Uninstalling 
a 5520 AMS patch
Block port during startup 
option
Modified the default option for block port during startup. Procedures 15, 58, and 
78
IGMP snooping Added a note about disabling IGMP snooping in a cluster 
network.
Sub-section Overview
Geographic redundancy Added a note for enabling the geographicredundancy settings 
post migration.
Section 17.4
MaxStartups Removed the section for configuring the maximum number of 
concurrent SSH connections.
—
ams_updatefirewall.sh 
script
Added information about ams_updatefirewall script. Section 12.1
ams_install_license.sh 
script
Updated the ams_install_license.sh script usage information. Table 40
ams_simplex_to_cluster.s
h script
Updated information for converting a simplex installation to a 
cluster using ams_simplex_to_cluster script.
Chapter 10
PermitRootLogin 
parameter 
Added a note for enabling PermitRootLogin parameter in the SSH 
configuration file.
Procedure 15
Obsolete entries in cluster 
installation
Removed obsolete entries of cluster installation. Tables 18 and 20
GUI Settings Import option Modified the note for GUI Settings Import option. Section 19.3
NE management interface Updated information for Installing the 5520 AMS solution.
Updated firewall rules.
Procedure 15
Section 12.2
Change password for 
amssftp or amsftp
Added a note for synchronizing the amssftp or amsftp password 
manually.
Removed the section for changing the passwords for default 
users.
Sub-section Out-of-place 
migration.
—
Migration between 
operating systems
Added a note to reinstall the NE software release after 5520 AMS 
hardware is migrated from Solaris system to Red Hat Enterprise 
Linux system.
—
Downloading Patch and 
emergency fix installation 
files
Add a note about downloading the patch and emergency fix 
installation files.
Section 6.2
OpenJDK Added procedure to install OpenJDK-7-devel as a prerequisite 
task.
Sections 7.2 and 7.3
Feature/enhancement Description See
(2 of 2)
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 35
 
2.7 What’s new in Release 9.4
Table 8 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.4.
Table 8 What’s new in Release 9.4
Feature/enhancement Description See
New features/enhancements
Support Solaris 
presentation server
Added Solaris presentation server related information. -
EMS migration engine 
implementation
Added information regarding the automated in-place migration. Chapters 16, 17, 18, and 
Appendix 22
Migration to 5520 AMS 9.4. Updated migration path to 5520 AMS, Release 9.4. Chapters 15, 16, and 
Appendix 22
Support for sudo to 
execute “root only” 
commands
Updated procedure to configure sudo automatically and 
manually.
Procedures 15 and 16, 
and 15.1
Red Hat Enterprise Linux 
version
Updated the RHEL version to 6.5. Section 3.2 
VMware setup 
pre-requisite
Added information about the pre-requisite for a VMware setup. Table 30
Subnet address 
configuration
Modified the steps to include the subnet address configuration. Procedures 15, 29, and 
58
Environment variables Added new environment variables to the table. Table 13
Documentation changes
To prepare the 5520 AMS 
infrastructure
Made the FTP connectivity verification an optional step and 
added a note for the same.
Procedure 6
Deactivating a patch Added the step to deactivate a patch during uninstalltion of a 5520 
AMS patch.
Procedure 88
Configure locale settings Updated the procedure to configure locale settings for Red Hat 
Enterprise Linux.
Procedure 11
Configuring geographic 
redundancy
Added a step to stop the servers before performing the switch 
between active and standby sites.
Procedure 41
Environment variables Added new environment variaables to the table. Table 3.2
Database storage Added information about database storage configuration. Sub-section “Configuring 
LVM volumes”
Table 30
Upgrade the GTK version Added a procedure to upgrade the GTK version on the 5520 AMS 
client in Solaris.
-
Rollback the GTK version Added a procedure to rollback the GTK version to default version 
in Solaris.
-
GUI Settings Import Added a note for the support of GUI Settings Import option. Section 19.3
(1 of 2)
What’s new
36
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
2.8 What’s new in Release 9.3.10
Table 9 lists the new 5520 AMS features and enhancements added to the 5520 AMS 
Installation and Migration Guide for Release 9.3.10.
Table 9 What’s new in Release 9.3.10
Edit the config.ini file to 
display hour convention
Updated the procedure to modify the config.ini file to display the 
required hour convention.
Procedure 53
Install 5520 AMS client Updated the result for single and shared client installation. Procedures 13.1 and 
13.4
Migration overview Added a caution note for 5529 Enhanced Applications and NE 
plug-ins migration 
Section 15.1
Migration overview Added a caution note to not stop or restart a server when 
migration is in progress.
Section 15.1
Installing 5520 AMS for 
migration
Added a note to indicate that additional 5529 Enhanced 
Applications and NE plug-ins can be installed in the current 
release.
Section 17.4
In-place migration Updated the information to indicate that in an in-place migration 
scenario the new release of the 5520 AMS is installed and 
activate on the same server.
Sub-section “In-place 
migration”
Feature/enhancement Description See
(2 of 2)
Feature/enhancement Description See
New features/enhancements
Checking alarm rules Added an instruction to check alarm rules after migrating to a new 
5520 AMS release or updating NE plug-ins.
Section 16.4
Migration paths to 
5520 AMS Release 9.3.10
Migration to 5520 AMS Release 9.3.10 is supported from:
• 5520 AMS Release 9.2.10
• 5520 AMS Release 9.2.30
• 5520 AMS Release 9.3.0
Chapters 15, 16, 17, 18, 
and 19
Red Hat Enterprise Linux 
client
Added Red Hat Enterprise Linux client information. Chapter 13 
Procedure 76
Firewall rules Moved updating firewall rules section to a chapter Chapter 12
ams_server version Added a procedure to verify the installed software components
GSIP release 4.8 Added the latest GSIP version supported. Section 15.5
Documentation changes
Server startup time Added note on the time taken on a first time server startup. Procedure 24
Modifying the amsclient.ini 
properties
Added a note on modifying properties in amsclient.ini while 
launching the 5520 AMS client from absolute path.
Section 13.5
Sitename.xml Update the sitename.xml information while converting from 
simplex server to cluster server.
Procedure 29
(1 of 2)
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 37
 
2.9 What’s new in Release 9.3.0
Table 10 lists the new 5520 AMS features and enhancements added to the 
5520 AMS Installation and Migration Guide for Release 9.3.0.
Table 10 What’s new in Release 9.3.0
Site name Updated the note to list the special characters that are allowed 
while searching the name of a site name.
Procedures 15 and 58
Configuration directory Updated the path of the configuration directory. Procedures 53 and 54
Install shared client in 
Windows
Updated the procedure to edit the config.ini file. Procedure 53
To activate a server Added a warning and note to the procedure. Procedure 81
Uninstall 5520 AMS client 
in Red Hat Enterprise Linux
Updated the procedure to uninstall 5520 AMS client application in 
Red Hat Enterprise Linux
Procedure 76
Installation and migration 
procedures
Updated the references to Solaris and Red Hat Enterprise Linux 
for all the installation and migration types.
Chapters 7 and 17 
Installer prompts for 
in-place migration
Removed the table listing the questions not prompted by the 
installer during an in-place migration and updated the content and 
added a note 
Section 17.2
Install a shared client in 
Windows
Updated the procedure to install a shared client in Windows for 
the user workspace configuration
Procedure 46
Uninstalling software 
plug-ins
Added a note on clearing the exception thrown by Windows client 
when uninstalling a plug without first deactivating it
Section 20.2
Installing 32-bit 
compatibility packages on 
Red Hat Linux Enterprise 
systems
Addedinformation about 32-bit compatibility packages on Red 
Hat Linux Enterprise systems.
Section 17.4
Feature/enhancement Description See
(2 of 2)
Feature/enhancement Description See
New features/enhancements
Migration paths to
5520 AMS Release 9.3.0
Migration to 5520 AMS Release 9.3.0 is supported from Release 
9.2.30.
Sections 15.1, 15.3, 15.4, 
15.5, 15.9 
Red Hat Enterprise Linux 
support
Added a section to describe the configuration of LVM volumes. Sub-section Configuring 
LVM volumes
Updated the illustration of the cluster installation of 5520 AMS. Figure 2
Updated the LVM volume configuration pre-requisites. Table 30
Added Red Hat Enterprise Linux information. Procedures 6
Updated information related to Solaris systems and Red Hat 
Enterprise Linux systems.
Section 5.1
Virtual machine Added a note on configuring the virtual machine. Section 5.1
(1 of 2)
What’s new
38
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
2.10 What’s new in Release 9.2.30
Table 11 lists the new 5520 AMS features and enhancements added to the 
5520 AMS Installation and Migration Guide for Release 9.2.30.
Table 11 What’s new in Release 9.2.30
Documentation changes
ams_server status output Updated the ams_server status output. Procedures 37 and 66
Installer question for 
shared and database 
directory
Updated the installer question for the configuration of the shared 
data and local database directory.
Multicast bind IP address Added a note on multicast bind IP address. Section 4.2
MaxStartups parameter Updated the command to configure the MaxStartups parameter. -
Feature/enhancement Description See
(2 of 2)
Feature/enhancement Description See
New features/enhancements
Migration paths to 
5520 AMS Release 9.2.30
Migration to 5520 AMS Release 9.2.30 is supported from:
• 5520 AMS Release 9.1.0
• 5520 AMS Release 9.1.10
• 5520 AMS Release 9.2.10
• 5520 AMS Release 9.2.20
Sections 15.1, 15.4, 15.2, 
15.3, and 15.4
(1 of 2)
Installation and Migration Guide What’s new
Issue: 01 3JL-01001-BTAA-RJZZA 39
 
Installing the 5520 AMS 
solution
Regrouped the 5520 AMS installation overview sections, and 
added sections on the installation overview of software plug-ins 
and emergency fixes.
Chapter 4
Regrouped the information on setting up the 5520 AMS 
infrastructure.
Chapter 5
Added a section on extracting the downloaded installation files. Section 6.2
Regrouped the 5520 AMS installation-related sections. Chapter 7
• 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 
sections on the uninstallation of software plug-ins and emergency 
fixes.
Chapter 20
Added information on installing and activating the 5520 AMS 
solution.
Section 3.1
Automatic site switchover Added information on the automatic site switchover in 
geographically redundant setups.
Automatic site switchover
Added information on ping-pong protection. Section 11.2
Updated the procedure to include the step to enable automatic 
switchover.
Procedure 37
Updated the procedure to include a note regarding disabling 
geographical redundancy.
Procedure 42
Improved 5520 AMS 
upgrade time
Updated the migration chapters to include information on the data 
migration strategies depending on the migration path.
Chapters 15, 16, 17, 18, 
and 19
Documentation changes
Limiting the bandwidth 
across the WAN for 
replication
Added a note on limiting the bandwidth across the WAN for 
replication, in a geographically redundant setup with two data 
servers at the standby site.
Section 11.3
Feature/enhancement Description See
(2 of 2)
What’s new
40
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Overviews
Issue: 01 3JL-01001-BTAA-RJZZA 41
 
3 Overviews
3.1 Guide overview
3.2 Installation and migration overview
3.3 5529 Enhanced Applications
3.4 Technical support
3.1 Guide overview
The 5520 AMS Installation and Migration Guide includes procedures to:
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.
3.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. 
• Prepare hardware for installation 
of the 5520 AMS
• Prepare a network for 5520 AMS 
operation
• Secure your 5520 AMS 
installation
• Install the 5520 AMS software
• Install software plug-ins 
• Install the 5520 AMS patches
• Install emergency fixes
• Install the 5520 AMS client for 
Windows, and Red Hat 
Enterprise Linux
• Migrate data from an earlier 
release of the 5520 AMS to the 
5520 AMS, Release 9.7. 
• Uninstall the 5520 AMS
Overviews
42
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
The 5520 AMS server software supports installation and migration in several 
configurations: 
• In a simplex (standalone) 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.
The 5520 AMS is designed to be installed on Intel 64bit based servers running the 
Red Hat Enterprise Linux 6.x x86_64 in the RHEL6 stream or 7.x in the RHEL7 
stream operating system.
For additional security, the 5520 AMS is designed to be installed on the following 
hardened RHEL platforms:
• Center for Internet Security (CIS)
• Security Technical Implementation Guide (STIG)
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.
3.2.1 Installation terms
Table 12 defines key terms used to describe 5520 AMS configurations.
Table 12 Key terms
Note — Nokia 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 Nokia support representative. See Section 3.4 for 
information on technical support.
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.
(1 of 2)
Installation and Migration Guide Overviews
Issue: 01 3JL-01001-BTAA-RJZZA 43
 
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 database and shared directories are replicated 
between the twosites, 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 
server
The non-preferred data server is the server that does not have 
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 database server is active. This is the active 
data server. At startup, the database server on the preferred data 
server is the master. 
Standby data server Within a site, a backup database server can be ready to start 
when the active data server fails. This is the standby data server. 
The standby data server initiates database 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 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.
Application server 
maintenance mode
If you want to bring down the running server or virtual machine for 
a short maintenance break (less than 10 minutes), then it is 
recommended to first bring the AMS application into maintenance 
mode by using the command ams_server stop maintenance. This 
has as effect that AMS will not try to rebalance the NE to other 
AMS servers which will save recovery time and decrease overall 
system load.
Operating System 
maintenance mode
5520 AMS registers itself as Linux service. In case the output of 
the command ams_server status shows that the EMS service is 
in maintenance mode, it means that a serious problem at the level 
of the OS has occurred from which the AMS application cannot 
recover.
Term Definition
(2 of 2)
Overviews
44
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
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. 
3.2.2 Environment variables
The 5520 AMS defines environment variables for directories on the servers. These 
variables can be used by the amssys user. Table 13 describes environment variables 
used in the procedures available 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.
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, Nokia 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 Nokia 5529 Enhanced Applications in 
addition to the 5520 AMS, contact your sales representative for 
further information about your specific installation 
requirements. 
Note 3 — Ensure that your Web Browser supports the 
encryption that is used to generate the keystore for a SSL. 
Otherwise, the Web Browser will be unable to display the AMS 
Download Page.
Installation and Migration Guide Overviews
Issue: 01 3JL-01001-BTAA-RJZZA 45
 
Table 13 Environment variables
3.2.3 Path variables
The application server provides access only to certain specific directories and does 
not allow free access of path traversal.
The directories other than the following are restricted from free access of path 
traversal.
Table 14 Path 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.7-999000.
$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.7-999000.
$AMS_SOFTWARE_HOME The directory where the 5520 AMS software is stored. An example is 
/opt/ams/software/ams-9.7-999000.
$AMS_LOG_DIR The directory where 5520 AMS logs are stored. An example is 
/var/opt/ams/local/ams-9.7-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.7-999000/conf.
$PLATFORM_SCRIPTS_DIR The directory where platform scripts for the 5520 AMS are stored. An 
example is /opt/ams/software/ams-9.7-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.7-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
$MYSQL_DATA The directory where the 5520 AMS data is stored. An example is 
/var/opt/ams/users/amsdb
PATH Variable Default Path
$AMS_LOCALDATA_HOME /var/opt/ams/local/ams-<version>
(1 of 2)
Overviews
46
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
3.2.4 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 
(AD), 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 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 AD/AD 
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 avoidthe active/active server condition, the arbiter server acts as an external 
party in an AD/AD 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 AD/AD 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 
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.
$AMS_EXTERNAL_LOCALDATA_HOM
E
/var/opt/ams/local/common
$AMS_SWM_REPO_DIR /ams
$AMS_SOFTWARE_HOME /opt/ams/software/ams-<version> 
$TMP_DIR /tmp or /var/tmp
PATH Variable Default Path
(2 of 2)
Installation and Migration Guide Overviews
Issue: 01 3JL-01001-BTAA-RJZZA 47
 
3.2.5 Simplex (standalone) installation
In a simplex (standalone) 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 1 shows an example of a simplex 
(standalone) installation.
Figure 1 Simplex (standalone) installation of the 5520 AMS
3.2.6 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. Database 
replication copies database commands. The set of application servers in a cluster 
provide load sharing and some redundancy.
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. 
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 shows an example of a cluster installation.
WAN DCN
Application
and data server
Operators Network Elements
Presentation
server
Note — Do not mix the machine architectures and operating 
systems. Use the same setup for the same operation or 
configuration.
Overviews
48
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Figure 2 Cluster installation of the 5520 AMS
3.2.6.1 Database replication
Database replication is done in master/slave mode. The master database 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. 
3.2.6.2 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. 
LAN
Application +
active database
Application +
standby database
Shared Replication
Database replication
Check updates
Updates
Check updates
Updates
Preferred
data server
Database
Master
Non-preferred
data server
Database
Slave
Non-preferred
data server
Shared
Filesystem
Preferred
data server
Shared
Filesystem
Shared
replication
Database
 replication
Presentation
serverOperators
Client
network
Network
Elements
DCN
Installation and Migration Guide Overviews
Issue: 01 3JL-01001-BTAA-RJZZA 49
 
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 the LVM volume on Red Hat Enterprise Linux systems.
3.2.7 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.
Figure 3 shows an example of geographic redundancy on a simplex installation.
Figure 3 Simplest geographic redundancy installation of the 5520 AMS
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.
Note — Do not mix the machine architectures and operating 
systems. Use the same setup for the same operation or 
configuration.
Active application
and data server
5520 AMS GUI
Standby application
and data server
Presentation
server
Client
network DCN
Backup
transfer
Overviews
50
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 4 shows an example of geographic redundancy on a cluster installation. 
Figure 4 Typical geographic redundancy installation of the 5520 AMS
Regardless of the installation, the shared file system is replicated between the active 
and standby data servers. Database 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. 
LAN
Application
server
Application
server
Standby
data
server
LAN
WAN
Application
server
Applicationserver
Standby
data
server
Active
data
server
Standby
data
server
Active site Standby site
Database replication
Shared file system replication
Legend:
Installation and Migration Guide Overviews
Issue: 01 3JL-01001-BTAA-RJZZA 51
 
In the event that both data servers fail at the active site, a manual switchover is 
required to change the active site. 
3.2.8 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 9. 
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.
3.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.
3.4 Technical support
Include the release of the 5520 AMS and the 5520 AMS plug-in release and version 
when reporting issues to Nokia Technical Support. 
Procedure 5 describes how to find the contact information for technical assistance 
for a country.
Note — In a geographically redundant setup, the mount points 
of the Red Hat Enterprise Linux shared and database 
replication file systems in the active data server and the 
standby data server must be the same.
Overviews
52
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 5 To find contact information for technical assistance
1 Go to http://support.alcatel-lucent.com.
2 Log in to the Nokia Customer and Business Partner Portals with the user name and password 
for your OLCS account.
Result: A customized Customer Center page opens.
3 Under Product Technical Support, select a country.
Result: The Nokia Support Contact Numbers window opens and displays the phone and 
e-mail contact information for technical assistance for the selected country.
http://support.alcatel-lucent.com
Installation and Migration Guide Installing the 5520 AMS
Issue: 01 3JL-01001-BTAA-RJZZA 53
 
Installing the 5520 AMS
4 5520 AMS installation overview
5 Setting up 5520 AMS infrastructure
6 Downloading software for the 5520 AMS and 5529 Enhanced 
Applications
7 Installing the 5520 AMS solution components
8 Activating, starting and stopping the servers
9 Configuring the 5520 AMS to support NAT
10 Converting a simplex installation to a cluster
11 Configuring geographic redundancy
12 Updating firewall rules
13 Installing the 5520 AMS client
14 5520 AMS server maintenance
Installing the 5520 AMS
54
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 55
 
4 5520 AMS installation overview
4.1 Simplex installation overview
4.2 Cluster installation overview
4.3 Geographic redundancy installation overview
4.4 Software plug-in installation overview
4.5 Patch installation overview
4.6 Emergency fix installation overview
4.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.
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.
Note 1 — Nokia 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.7. If you are migrating from an earlier 
release of the 5520 AMS, see Chapter 16 for additional 
procedures to migrate your data.
5520 AMS installation overview
56
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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
• 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 15 User accounts
4.1.1 Server installation tasks
Table 16 lists the tasks to install the 5520 AMS in a simplex (standalone) 
configuration. Before you proceed, you need root access to the server. The root 
account can perform any action.
Table 16 Install the 5520 AMS, Release 9.7 in a simplex (standalone) configuration
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.
amsdb This account is used for the 5520 AMS database, with no login permission to 
access any of the servers in the cluster (Application, Data and Arbiter servers). 
The default password for the amsdb user account is amsdb.
Note — Whenever the active site starts up an alarm is 
generated. There is only one alarm raised per site. The alarm 
gets cleared when the active site is up and running.
Task 
#
Task See
1 Prepare the server infrastructure. Procedure 6
(1 of 2)
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 57
 
4.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 3.
4.2.1 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 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 standbyserver 
automatically takes over its role.
2 Install and activate the 5520 AMS solution. Procedure 15
3 If you use a NAT server, configure the 5520 AMS to support 
NAT.
Section 9.1
4 Start the 5520 AMS. Procedure 24
5 Install the 5520 AMS client and apply client updates. Chapter 13
6 Apply 5520 AMS licenses to your server. Procedure 55
7 (Optional) Set up the server as a cluster server to simplify future 
expansion to a cluster.
Chapter 10
You have completed the set of installation tasks.
Task 
#
Task See
(2 of 2)
Note — This section describes the installation of the 
5520 AMS, Release 9.7. If you are migrating to the 5520 AMS 
Release 9.7 from an earlier release of the 5520 AMS, see 
Chapter 16 for additional procedures to migrate your data.
5520 AMS installation overview
58
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
• Both an application and data server (AD), 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 AD/AD 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. 
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.
Note — In a cluster with a combination of application and data 
servers (AD), 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.
In case of geographically redundant cluster, if the cluster 
communication interface between the data servers are down in 
the active site, you need to manually start the server which has 
the most recent and complete data using ams_server start.
Note 1 — To change or add a specific sub-network for 
intra-cluster communication in a cluster setup, contact your 
local Nokia 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.
Note 3 — On a cluster network IGMP snooping must be 
disabled for the clusters to communicate with each other. If you 
want to enable the IGMP snooping, refer to the 5520 AMS 
Administrator Guide.
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 59
 
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 4.3 for more information about geographic 
redundancy and for information about installing at multiple sites.
Before you install the 5520 AMS in a cluster configuration, ensure that the names of 
all the available hosts are included in the /etc/host file of each server.
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.
Ensure that /etc/hosts file of each server is verified and updated at each AMS start. 
Any new host added after installation of the 5520 AMS should have an entry in the 
local file /etc/host so that when the 5520 AMS is restarted the new host is identified.
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
• 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:
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.
5520 AMS installation overview
60
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 17 UNIX user accounts
The root account can perform all actions.
4.2.2 Cluster installation tasks
Table 18 provides the tasks to set up a cluster. Before you proceed, you need root 
access to the servers.
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 will be safe to start the server.
Starting the server starts the 5520 AMS processes.
Table 18 Install the 5520 AMS in a cluster configuration
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.
amsdb This account is used for the 5520 AMS database, with no login permission to 
access any of the servers in the cluster (Application, Data and Arbiter servers). 
The default password for the amsdb user account is amsdb.
Caution — On a cluster, passwords must be aligned at all 
times.
Note 1 — Whenever the active site starts up an alarm is 
generated. There is only one alarm raised per site. The alarm 
gets cleared when the active site is up and running.
Note 2 — There is no alarm raised during a master switchover 
in a cluster setup.
Task 
#
Task See
1 Set up the cluster infrastructure. Procedure 6
(1 of 2)
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 61
 
4.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 eventof 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 7.
Geographic redundancy requires configuration of file system replication of the 
shared data between the active and standby site. 
The 5520 AMS uses replication of database information between the active and 
standby site. The 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. 
2 Install and activate the 5520 AMS solution in a cluster Procedure 15 to install a preferred data server.
3 Start the preferred 5520 AMS data server. Procedure 24
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 
started are running.
5520 AMS Administrator Guide
• Start all additional application servers. Procedure 24
8 If you will be using a NAT server between the application 
servers and the 5520 AMS client and the servers are on the 
private side of the NAT server, add the translated IP 
addresses to the configuration file for each application server.
Procedure 28
9 Install, launch, and download updates to the 5520 AMS client. Chapter 13
10 Apply licenses to all application servers. Procedure 55
11 Perform optional post-installation tasks. 5520 AMS Administrator Guide to display the 
server process status and the cluster status.
You have completed the set of installation tasks.
Task 
#
Task See
(2 of 2)
5520 AMS installation overview
62
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4.3.1 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.
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.
The sites must have different site names. All messages exchanged are identified by 
site name.
4.3.2 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.
4.3.3 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.
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.
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 7.3.
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 63
 
For more information on the health status, see the 5520 AMS Administrator Guide.
4.3.4 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.
4.3.4.1 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 38 
for more information.
4.3.4.2 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 41 to perform a switchover.
4.3.4.3 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 status 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.
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.
5520 AMS installation overview
64
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
• In case of a standby-standby site scenario, the following status 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 which was last active becomes 
the active site).
The other site switches to standby state.
Table 19 summarizes the scenarios that triggers site switchover in a geographically 
redundant setup. 
Table 19 Scenarios for geographically redundant switchover
Notes
(1) The site that switched to standby state most recently becomes the active site.
(2) The site that became active most recently becomes the standby site.
The servers at the active site are started automatically and the server status is 
monitored again. For information on the health status, see the 5520 AMS 
Administrator Guide.
4.3.4.4 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 11.2. 
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)
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.
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 65
 
4.3.4.5 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.
Figure 5 shows a geographically redundant installation with an OSS arbiter.
Figure 5 Geographic redundancy installation of the 5520 AMS with an OSS arbiter
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. 
Application
server
host A
Application
server
host B
Cluster
Network
OSS
Data
server
host C
Data
server
host D
SITE 1
Application
server
host W
Application
server
host X
Cluster
Network
Data
server
host Y
Data
server
host Z
SITE 2
NEs5520 AMS client 
Client
Network
DCN
Synchronization
Network
(WAN)
5520 AMS installation overview
66
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4.3.5 Geographic redundancy installation tasks
Table 20 describes the tasks to set up a geographically redundant installation. 
Table 20 Install the 5520 AMS, Release 9.7 in a geographically redundant installation
4.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.
Note — In a geographic simplex setup, during a site switchover 
an alarm is raised on the newly started active site. There is only 
one alarm raised per site. The alarm gets cleared when the 
active site is up and running.
You can view the alarm details for additional information about 
the site switchover or the active site restarting.
Task # Task See
1 Set up the active site. The site can consist of a single server running 
both the database and 5520 AMS application server, or a 
multi-server cluster. 
Procedure 6 to prepare the 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 
standalone server in both active and standby sites.
Procedure 15 
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.
—
5 Configure geographic redundancy on data servers. Section 11.3
6 (Optional) Configure the 5520 AMS to run a script if one site is down. Procedure 38
7 (Optional) Configure the OSS arbiter. Procedure 39
8 (Optional) Start the OSS arbiter. Procedure 40
9 Start the 5520 AMS. Procedure 24
10 If you will be using a NAT server between the application servers and 
the 5520 AMS client and the servers are on the private side of the 
NAT server, add the translated IP addresses to the configuration file 
for each application server.
Procedure 28
11 Install, launch, and download updates to the 5520 AMS client. Chapter 13
12 Apply licenses to all application servers at both sites. Procedure 55
You have completed the set of installation and configuration tasks.
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 67
 
4.4.1 Installing and activating software plug-ins
Table 21 lists the tasks to install and activate the 5520 AMS NE plug-ins, or 
5529 Enhanced Applications and plug-ins.
Before you proceed, ensure to install and activate the 5520 AMS, see Section 7.3 to 
install the 5520 AMS in the required servers.
Table 21 Install and activate a software plug-in
4.4.2 Deactivating software plug-ins
Table 22 lists the tasks to deactivate the 5520 AMS NE plug-ins or 5529 Enhanced 
Applications and plug-ins.
Table 22 Deactivate a software plug-in
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 
7.
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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ command. Procedure 27
2 Install and activate the software plug-in. Procedure 18 or Procedure 21
3 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ command. Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ command. Procedure 25
You have completed the set of installation and activation tasks.
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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ command. Procedure 27
3 Deactivate the software plug-in. Procedure 20
(1 of 2)
5520 AMS installation overview
68
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4.5 Patch installation overview
This section describes the installation and deactivation of a 5520 AMS patch. 
4.5.1 Installing and activating patches
You can install and activate the 5520 AMS patches based on the case listed in 
Table 23.
4 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ command. Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ command. Procedure 25
You have completed the set of deactivation tasks.
Task 
#
Task See
(2 of 2)
Note — In a cluster environment, the patch must be installed 
and uninstalled on all servers in the cluster.
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 69
 
Table 23 Install the 5520 AMS patches - cases
Table 24 lists the tasks to install and activate a 5520 AMS patch.
Table 24 Install and activate a 5520 AMS patch
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 7.
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.
Task 
#
Task See
1 Backup the currently installed 5520 AMS. 5520 AMS Administrator Guide
2 Perform one of the following steps:
• If you are installing new patches for 5529 Enhanced Applications, 
prepare the applications for uninstallation.
The release notices for the applicable 
5529 Enhanced Applications patches
• If you are not installing new patches for 5529 Enhanced 
Applications, proceed to task 3.
3 Uninstall the current 5520 AMS client. Section 20.6
4 Stop the 5520 AMS.
To stop the server in a simplex setup, use the ‘ams_server stop’ 
command.Procedure 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ 
command.
Procedure 27
(1 of 2)
5520 AMS installation overview
70
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
5 Perform one of the following steps:
• If SSL is enabled, disable SSL.
Perform this step only on application servers or on combination of 
application and data servers.
5520 AMS Administrator Guide
• If SSL is not enabled, proceed to task 6.
6 Deactivate and uninstall only the existing plug-ins that you will be 
patching, as applicable:
• NE support plug-ins
• SIP application plug-in
• SIP plug-ins for NEs
• 5529 Enhanced Applications 
• NE support plug-ins for the 5529 Enhanced Applications
Procedure 74
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.
• If you are installing a 5520 AMS patch when a previous 5520 AMS 
patch has already been installed, proceed to task 7.
7 Deactivate and uninstall the existing 5520 AMS patch.
Uninstalling the existing 5520 AMS patch is optional. In case of issues 
during upgrade, you can roll back to the previous 5520 AMS patch, if it 
is not uninstalled.
Procedure 74
8 Install and activate the 5520 AMS patch. Procedure 18 
or Procedure 21
9 Install and activate the new plug-ins, as applicable:
• NE support plug-ins
• SIP application plug-in
• SIP plug-ins for NEs
• 5529 Enhanced Applications 
• 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.
Procedure 18
10 Enable SSL.
Perform this step only on application servers or on combination of 
application and data servers.
5520 AMS Administrator Guide
11 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ 
command.
Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ 
command.
Procedure 25
12 Launch and log on to the 5520 AMS client. Section 13.6
You have completed the set of installation and activation tasks.
Task 
#
Task See
(2 of 2)
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 71
 
4.5.2 Deactivating patches
You can deactivate the 5520 AMS patches based on the case listed in Table 25.
Table 25 Deactivating the 5520 AMS patches - cases
Table 26 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 26 Deactivate a 5520 AMS patch
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.
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.
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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ 
command.
Procedure 27
3 Deactivate the 5520 AMS patch. Procedure 20
(1 of 2)
5520 AMS installation overview
72
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4.6 Emergency fix installation overview
This section provides an overview of the installation, activation and deactivation of 
emergency fixes.
4 Depending on the deactivation case, perform one of the following 
tasks:
• If you have deactivated the patch to continue with an unpatched 
system, enable SSL. Go to task 5.
• If you have deactivated the 5520 AMS patch to install a higher 
5520 AMS patch or to roll back to a previous 5520 AMS patch, 
install and activate the required 5520 AMS patch.
Procedure 18 or Procedure 21 for installing 
and activating the patch.
Procedure 19 or Procedure 21 for 
activating the patch.
5 Enable SSL.
Perform this step only on application servers or on combination of 
application and data servers.
5520 AMS Administrator Guide
6 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ 
command.
Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ 
command.
Procedure 25
7 Uninstall the current 5520 AMS client. Section 20.6
8 Download and install the compatible 5520 AMS client. Chapter 13
You have completed the set of deactivation tasks.
Task 
#
Task See
(2 of 2)
Note — In a cluster environment, you must install the 
emergency fix on each server in the cluster.
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 73
 
4.6.1 Installing and activating emergency fixes
Table 27 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 7.
5520 AMS installation overview
74
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 27 Install and activate an emergency fix
4.6.2 Deactivating emergency fixes
Table 28 lists the tasks to deactivate an emergency fix.
Table 28 Deactivate an emergency fix
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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ 
command.
Procedure 27
3 Install and activate the emergency fix. Procedure 18 
or Procedure 21
4 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ 
command.
Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ 
command.
Procedure 25
5 Launch and log on to the 5520 AMS client. Section 13.6
You have completed the set of installation and activation tasks.
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.
Task 
#
Task See
1 Backup the currently installed 5520 AMS. 5520 AMS Administrator Guide
(1 of 2)
Installation and Migration Guide 5520 AMS installation overview
Issue: 01 3JL-01001-BTAA-RJZZA 75
 
2 Stop the 5520 AMS.
To stop the server in a simplex setup, use the ‘ams_server stop’ 
command.
Procedure 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ 
command.
Procedure 27
3 Deactivate the emergency fix. Procedure 20
4 Start the 5520 AMS.
To start the server ina simplex setup, use the ‘ams_server start’ 
command.
Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ 
command.
Procedure 25
5 If the emergency fix, that you deactivated, contained any fix for the 
5520 AMS client, perform the following steps:
1) Uninstall the current 5520 AMS client.
2) Download and install the older compatible 5520 AMS client.
Section 20.6
Chapter 13
You have completed the set of deactivation tasks.
Task 
#
Task See
(2 of 2)
5520 AMS installation overview
76
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Setting up 5520 AMS infrastructure
Issue: 01 3JL-01001-BTAA-RJZZA 77
 
5 Setting up 5520 AMS 
infrastructure
5.1 Setting up the 5520 AMS infrastructure
5.2 Configuring NTP
5.3 Configuring storage
5.4 User and group IDs
5.5 Configuring locale settings
5.6 SSH session timeouts
5.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.
To protect against connection failure, Nokia 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.
5.1.1 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.
Note — Nokia does not recommend using the combination of 
application and data server (AD) on a single virtual machine.
Setting up 5520 AMS infrastructure
78
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
5.1.2 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 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 6 To prepare the 5520 AMS infrastructure
1 Install the operating system.
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 5.2.
If you are setting up the infrastructure for a simplex setup, go to Step 6.
If you are setting up the infrastructure for a cluster setup, go to Step 4.
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.
Note 1 — For the Red Hat Enterprise Linux operating system, ensure to 
have the latest updates installed.
Note 2 — See the 5520 AMS Solution Planning Guide for hardware 
requirements and network specifications.
Note 3 — Nokia recommends that you do not change the default umask 
value of 022.
Installation and Migration Guide Setting up 5520 AMS infrastructure
Issue: 01 3JL-01001-BTAA-RJZZA 79
 
6 Depending on the type of setup, perform one of the following steps:
7 Configure locale settings. See Procedure 11.
5.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.
On Red Hat Enterprise Linux systems, depending on the type of configuration, use 
the procedures in Table 29 to configure NTP.
Table 29 Configure NTP on Red Hat Enterprise Linux systems
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.
Setup Red Hat Enterprise Linux systems
Simplex setup Configure LVM volumes. See Procedure 10.
Cluster setup Configure LVM volumes on both data servers and a 
combination of application and data servers. See 10.
Type of configuration See
Set up a standalone NTP server Procedure 7
Set up an external synchronized NTP server Procedure 8
Configure NTP clients to access the NTP 
server
Procedure 9
Setting up 5520 AMS infrastructure
80
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 7 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.
1 Log in to the server as root.
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 ↵
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.
Note — To deny all access to any machine, ensure that the line “restrict 
default ignore” exists in the configuration file.
Installation and Migration Guide Setting up 5520 AMS infrastructure
Issue: 01 3JL-01001-BTAA-RJZZA 81
 
Procedure 8 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.
1 Log in to the server as root.
2 To open the NTP configuration file, type:
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 9 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.
1 Log in to the server as root.
2 To open the NTP configuration file, type:
vi /etc/ntp.conf ↵
Note — Ensure that the NTP package is installed on the server. For 
more information, see Procedure 7.
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 7.
Note 2 — Ensure that an NTP client is configured in Linux. For more 
information, see Procedure 8.
Setting up 5520 AMS infrastructure
82
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
3 To add an access policy, type:
restrict NTP_client_IP mask netmask nomodify notrap ↵
where:
NTP_client_IP is the IP addressof 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
netstat -tulpn
5.3 Configuring storage
This section describes the procedures to configure storage.
5.3.1 Configuring LVM volumes
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 6 shows the volume setup on Red Hat Enterprise Linux systems.
Applies to — This section is applicable to Red Hat Enterprise 
Linux systems only.
Installation and Migration Guide Setting up 5520 AMS infrastructure
Issue: 01 3JL-01001-BTAA-RJZZA 83
 
Figure 6 Volume setup on Red Hat Enterprise Linux systems
Procedure 10 To configure LVM volumes
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.
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 bigger than 
the size of the database volume.
Bootdisk
Single Volume Setup Multiple Volume Setup
/
Swap volume
Database volume
Free physical extents*
5520 AMS disk
/
Database volume
Shared volume
Free physical extents*
Bootdisk
/
Swap volume
vgroot vgamsvgroot
* Free physical extents Database volume
Note — Perform this procedure on simplex servers, data servers, and 
combination of application and data servers.
Setting up 5520 AMS infrastructure
84
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
5.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
• amsdb: 553004
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
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.
Installation and Migration Guide Setting up 5520 AMS infrastructure
Issue: 01 3JL-01001-BTAA-RJZZA 85
 
• amssftp: 553012
• amsdb: 553014
5.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 11 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
3 Save the modified file. 
4 Restart the server to confirm the modifications.
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.
Note — On RHEL systems, modify /etc/sysconfig/i18n.
Setting up 5520 AMS infrastructure
86
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
5.6 SSH session timeouts
The ams_configure_ssh_timeouts script is used to enable/disable/check SSH 
session timeouts. See the 5520 AMS Administrator Guide for information about this 
script.
The ams_configure_ssh_timeouts script updates the SSH session timeout on the 
local server only. In a cluster setup, this script must be executed on all cluster 
members with the same timeout. In a geographically redundant setup, this script 
must be executed on all sites with the same timeout.
Installation and Migration Guide Downloading software for the 5520 AMS and
5529 Enhanced Applications
Issue: 01 3JL-01001-BTAA-RJZZA 87
 
6 Downloading software for the 
5520 AMS and 5529 Enhanced 
Applications
6.1 Downloading software for the 5520 AMS and 5529 Enhanced 
Applications
6.2 Extracting the downloaded installation files
6.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 Nokia representative.
Use Procedure 12 to download software for the 5520 AMS and 5529 Enhanced 
Applications.
Procedure 12 To download software
1 Go to https://support.alcatel-lucent.com/portal/web/support/ and click Login/Register.
2 Choose 5520 AMS from the Product information drop-down menu.
3 Select 5520 AMS in Software downloads. The Electronic Delivery > Downloads page opens.
4 Select release from the "Please navigate through the hierarchy to download" drop-down list.
5 List of packages is displayed. Check the package that you want to download and click Next.
6 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 13.
Downloading software for the 5520 AMS and 
5529 Enhanced Applications
88
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
Procedure 13 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 12 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 pathto the software and the software filename.
Example: digest –a md5 /MyDownloads/ams-9.7.00-268052-redhat-x86_64.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 Nokia Technical Support.
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.
Installation and Migration Guide Downloading software for the 5520 AMS and
5529 Enhanced Applications
Issue: 01 3JL-01001-BTAA-RJZZA 89
 
6.2 Extracting the downloaded installation files
Use Procedure 14 to create a directory for the downloaded installation files, extract 
the files to that directory, and make the installation files executable.
Procedure 14 To extract the downloaded installation file to a new directory
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.7-999000.
operating_system is the Red Hat Enterprise Linux operating system.
architecture is x86_64 for Red Hat Enterprise Linux.
4 To extract the installation file to the directory, type:
tar xvf installation_filename.tar ↵
Applies to — Procedure 14 is applicable for 5520 AMS patch 
and emergency fix installations.
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.
Downloading software for the 5520 AMS and 
5529 Enhanced Applications
90
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
5 To go to the sw directory, type:
cd sw ↵
6 To make the installation file executable, type:
chmod 755 installation_filename.bin ↵
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 91
 
7 Installing the 5520 AMS solution 
components
7.1 Installing the 5520 AMS solution overview
7.2 Pre-requisite tasks
7.3 Installing the 5520 AMS solution
7.4 Saving the configuration settings for installation of a 5520 AMS server
7.5 Installing 5520 AMS NE plug-ins, 5529 Enhanced Applications and 
plug-ins, and patches and emergency fixes
7.6 Verifying the installed software components on the 5520 AMS server
7.7 Modifying the parameter values in the configuration file
7.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 7.4.
• 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 15 to install and activate 
5520 AMS solution components in a simplex or cluster setup.
Installing the 5520 AMS solution components
92
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
7.2 Pre-requisite tasks
Before installing each 5520 AMS solution component, ensure to perform the 
pre-requisite tasks mentioned in Table 30.
Table 30 Pre-requisite tasks for installing the 5520 AMS
Pre-requisite task See
Obtain the 5520 AMS license key from Nokia. For information on license keys, see 
the 5520 AMS Administrator Guide.
To obtain a license key, contact your 
Nokia account representative.
Prepare the server that will host the 5520 AMS and install the 
operating system.
For system requirements and 
recommended settings, see the 
5520 AMS Solution Planning Guide.
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 
pre-requisites on volumes are applicable to simplex servers, 
data servers, and combination of application and data servers:
• Database volume: A separate logical volume in which to 
install the 5520 AMS database.
• 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 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: Nokia recommends a separate logical volume in 
which to store the shared data.
For information on configuring LVM 
volumes on an already created 
volume setup for installing the 
5520 AMS, see the 5520 AMS 
Server Configuration Technical 
Guidelines.
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.
-
Ensure that no special characters are used in the directory 
name. Only alphanumeric, “-”, “_” and “.” are allowed.
-
Ensure that the system locale is set to English or an 
ISO8859-1 based language.
Section 5.5
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 
them.
Section 5.4
(1 of 2)
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 93
 
For detailed information on software packages and configurations that must be 
installed additionally for each server role, refer the 5520 AMS Server Configuration 
Technical Guidelines.
Ensure that the root home directory ~ and your ~/.ssh 
directory on the server must be writable by root only.
-
Ensure to verify that the hostname of the AMS Server is 
named with the following permitted characters:
• Alphabets in either lower case or upper case
• Numerals from 0 to 9
• Special characters: Hyphen (-) and/or Period (.)
-
When installing the 5520 AMS release:
• Obtain the software file and make it executable.
• Obtain root access to the server on which you are 
installing the 5520 AMS.
Chapter 6
When installing and activating the 5520 AMS NE plug-ins, 
5529 Enhanced Applications and plug-ins, patches, and 
emergency fixes togetheror separately:
-
• Obtain the software files and make them executable.
• Ensure that the 5520 AMS release is installed and 
activated.
• It will be easier if the .bin files of the software plug-ins, 
patches, and emergency fixes that you want to install and 
activate are stored in a single directory.
Chapter 6
Sections 7.3 
• 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 ‘ams_server 
stop’ command.
Procedure 26
• To stop all servers in a cluster setup, use the ‘ams_cluster 
stop’ command.
Procedure 27
If you are installing the 5520 AMS using a configuration file, 
ensure that the configuration file is generated.
Procedure 17
If you are installing a VMware setup, ensure that the 
configuration is correct.
5520 AMS Server Configuration 
Technical Guidelines
Ensure all the required Red Hat Enterprise Linux packages 
are installed.
5520 AMS Server Configuration 
Technical Guidelines
Pre-requisite task See
(2 of 2)
Installing the 5520 AMS solution components
94
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
7.3 Installing the 5520 AMS solution
Use Procedure 15 to install and activate the 5520 AMS solution in a simplex setup.
Before you proceed, ensure to perform the pre-requisite tasks. See Section 7.2.
Procedure 15 To install and activate the 5520 AMS solution
Note — For samples of simplex server, NE plug-in, and VAP 
installations, see Appendix 21.
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 — Modifying the settings in the file /etc/sysctl.conf can impact the 
performance and 5520 AMS functionality. AMS detects these setting 
changes and displays the following warning during AMS installation:
Warning: System running with adapted sysctl settings 
which might impact AMS functionality
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 16 for 
automated in-place migration and out-of-place migration. For manual 
in-place migration tasks, see Appendix 22.2.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 95
 
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 14.
3 Execute one of the following commands depending on the installation scenario:
Note 1 — From Release 9.7 onwards, the default admin user is not 
created after installing the 5520 AMS. You need to manually create an 
initial AMS Administrator account. See the 5520 AMS Administrator 
Guide for more information.
Note 2 — After installing the 5520 AMS, you must manually start the 
server. See Procedure 24.
Note 3 — Ensure that the same SSL certificate is running in all the 
machines of a cluster (Application server (A), Data server (D), both 
Application and Data server (A+D)) and simplex setup at all times. In case 
of geographically redundant setup, the same SSL certificate is applicable 
for all the servers on both active and standby sites.
Scenario Execute the following command: Result
Install and activate all 
5520 AMS solution 
components without a 
configuration file 
(recommended)
./installation_filename.bin --activate-force 
--includevapsplugs directory_path ↵
where:
installation_filename.bin is the AMS Core 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.7-216228-redhat-x86_64.bin
operating_system is the Red Hat Enterprise Linux operating system.
architecture is x86_64 for Red Hat Enterprise Linux.
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 needs to be 
installed or if the .bin files are stored in different directories, specify the 
absolute path and filename of each .bin file.
The installation software displays the 
following confirmation:
Checking OS and version ... 
OK.
Checking hostname ... OK
Checking SSH (ssh, 
ssh-keygen, ssh-keyscan, scp, 
sftp) ...
The installer prompts you for the location of 
the SSH library:
Enter the path to the SSH 
tools [ /usr/bin (default) ]:
Proceed to step 5.
Install and activate 
only the 5520 AMS 
core software 
(excluding other 
solution components)
./installation_filename.bin --activate-force ↵
Installing the 5520 AMS solution components
96
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4 The installer prompts you for the location of the SSH tools.
Enter the path to the SSH tools [ /usr/bin (default) ]:
5 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) ]:
6 The installer prompts you for the location of the OpenJDK8 installation directory.
Enter the path to the OpenJDK 8 installation directory (default = 
/usr/lib/jvm/java-1.8.0-openjdk.x86_64):
If the OpenJDK-8-devel directory path is other than the default directory path, enter the 
directory path. 
/usr/local/java/java-1.8.0-openjdk.x86_64 
7 The installer prompts you for the shell to be used by the amssys user.
• To assign the default shell, press ↵.
• To assign a shell other than the default value, enter the path and shell. 
Enter the full path and executable file name of the default shell used 
by the amssys user [/bin/sh (default)]:
Install and activate all 
5520 AMS solution 
components using a 
configuration file
./installation_filename.bin -c 
[path_and_filename --activate-force] 
--includevapsplugs directory_path ↵
where:
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:
path_and_filename is the location and name of the configuration file 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. 
The installation proceeds based on the 
settings saved in the configuration file. The 
choices saved in the configuration file are 
displayed. See Table 31 for the installation 
result.
Scenario Execute the following command: Result
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 97
 
8 The installer prompts you for the name of the installation site.
Enter the site name that uniquely identifies the cluster (only 
alphanumeric, ‘-’, ‘_’ allowed):
9 Type a name for the site and press ↵.
Result: The installer prompts you to confirm the site name. 
Is this correct [ no (default) | yes ]?
10 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 ]?:
11 Perform one of the following:
Note — 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.
If then Result
The system is a simplex 
server
press ↵. The installer prompts you for the network interfaces:
Enter the network interface(s) used for GUI clients 
communication:
Note: Multiple interfaces can be entered using a 
comma separated list eth1, eth2
The GUI client interface(s) is “eth1,eth2”
Is this correct [no (default) | yes ]? yes
Enter the network interface(s) used for NE 
communication:
Note: Multiple interfaces can be entered using a 
comma separated list eth1, eth2
The NE interface(s) is “eth1,eth2”
Is this correct [ no (default) | yes ]? yes
The client interface refers to both GUI and NBI interfaces.
Go to step 17.
Installing the 5520 AMS solution components
98
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
12 Perform one of the following steps:
The system is member of 
a cluster
type n and 
press ↵.
The installer prompts you for the server role:
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 12.
If then Result
Note — In a cluster configuration there are some restrictions regarding 
the network configuration for the cluster network segment.
At all times there can be only one NIC connected to that subnet. Also, the 
use of virtual network interfaces (like eth0:0) is prohibited for cluster 
network connectivity.
If you need to install then Result
An application server type 1 and 
press ↵.
The installer prompts you for the network interface used for cluster 
communication:
Enter the network interface used for cluster 
communication:
eth2
The cluster interface is “eth2”.
Is this correct [no (default) | yes ]? yes:
A data server type 2 and 
press ↵.
A combination of 
application and data 
server
type 3 and 
press ↵.
An arbiter server type 4 and 
press ↵.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 99
 
13 Type y and press ↵ to accept the network interface or press ↵ for a prompt to modify the 
network interface.
If you are installing then
An application server or a 
combination of 
application and data 
server
The installer prompts you for the multicast IP address for application information:
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 
information [225.1.2.6 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
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 14
For combination of application and data server, go to step 15
A data server The installer prompts you for the multicast IP address for server information:
Enter the multicast IP address to exchange server 
information [225.1.2.6 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
Note: Data server IP addresses should be reachable 
via the same network interface as the one used to 
exchange cluster information
Go to step 15
Installing the 5520 AMS solution components
100
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
14 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
Is this correct [ no (default) | yes ]? y
where IP addresses is the list of the IP addresses or the DNS name installed on the server.
15 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”?
16 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.
An arbiter server The installer prompts you for the multicast IP address for server information:
Enter the multicast IP address to exchange server 
information [225.1.2.6 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
Go to step 17
Caution — The multicast IP address must be the same for all database 
and application server installations.
If you are installing then
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 101
 
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.
Perform one of the following steps:
• 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 The installer prompts you for the network interfaces:
Enter the network interface(s) used for GUI clients 
communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The GUI client interface(s) is “eth1,eth2”
Is this correct [no (default) | yes ]? yes
Enter the network interface(s) used for NE communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The NE interface(s) is “eth1, eth2”
Is this correct? [no (default) | yes ]? yes
The client interface refers to both GUI and NBI interfaces.
Go to step 17.
Installing the 5520 AMS solution components
102
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
17 The installer prompts you for the software installation directory:
In which top directory do you want to install the software [ /opt 
(default) ]?
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 
↵. 
The installer prompts you for the network interfaces:
Enter the network interface(s) used for GUI clients 
communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The GUI client interface(s) is “eth1,eth2”
Is this correct [no (default) | yes ]? yes
Enter the network interface(s) used for NE communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The NE interface(s) is “eth1, eth2”
Is this correct? [no (default) | yes ]? yes
The client interface refers to both GUI and NBI interfaces.
Go to step 17.
A combination of 
application and 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 server as the preferred data server, type y and press ↵. 
• To configure the server as a non-preferred data server, type n and press ↵. 
Go to step 17.
If you are installing: Result
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 103
 
18 Perform one of the following steps:
• To accept the default /opt directory, press ↵.
• To modify the directory, enter the path and press ↵.
19 Perform one of the following steps:
• To accept the default /var/opt directory, press ↵.
• To modify the directory, enter the path and press ↵.
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 
server, combination of 
application and data 
server, or application 
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)]
Go to step 19.
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 21 or else go to step 26
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.
If you are installing: then
A simplex server, data 
server, or a combination 
of application and data 
server, 
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 ?
(This location should be same in all the servers in the cluster)
Go to step 20.
Installing the 5520 AMS solution components
104
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
20 Perform one of the following steps:
• To accept the default /var/opt directory, press ↵.
• To modify the directory, enter the path and press ↵.
Result: 
21 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)
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 ?
(This location should be same in all the servers in the cluster)
If you are installing on Red Hat Enterprise, go to step 21 or else go to step 23
If you are installing: then
Note — On Red Hat Enterprise Linux systems, to choose an LV, refer 
to the Procedure 10.
Note — The location entered here will be used by the installer to install 
the files designated as shared in an /ams/shared subfolder.
If you are installing: then
A simplex server, or a 
combination of 
application and data 
server,
The installer prompts you for the database installation directory:
In which top directory do you want to put the database storage?
If you are installing on Red Hat Enterprise, go to step 21 or else go to step 23
A data server The installer prompts you for the database installation directory:
In which top directory do you want to put the database storage?
If you are installing on Red Hat Enterprise, go to step 21 or else go to step 26
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 105
 
[3] Using sudo (manual configured)
Installing the 5520 AMS solution components
106
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
22 Perform one of the following:
Type Result
1 and press ↵. Go to step 23
For data server and arbiter server, go to step 26
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 23
For data server and arbiter server, go to step 26
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 16.
The installer verifies the functionality of the sudo 
configuration file and prompts the next question. 
Go to step 23
For data server and arbiter server, go to step 26
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.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 107
 
23 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) ]?
(This location should be same in all the servers in the cluster)
24 To accept the default /ams directory, press ↵. 
For simplex server, go to step 26
For application server or combination of application and data server, go to step 25
25 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 (default)| no]? 
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 if the sudo configuration 
is not functioning properly. For more information on the alarms, see the 
5520 AMS Administrator Guide.
Note 2 — The chosen option is stored in the ams.conf parameter 
AMS_OS_SERVICE_METHOD as “ssh”, “sudoauto”, or “sudomanual”.
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.
Note 1 — 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 2 — During operation, data required by the NE software migration 
tools will be copied to the location you entered here.
Installing the 5520 AMS solution components
108
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 ↵.
26 The installer prompts you for the database user password:
Enter the password for database 552xadmin user (no space allowed) [ mysql 
(default) ]:
Perform one of the following steps:
• To use the default password, press ↵.
• To set the database user password, enter the new password and press ↵.
Result: The installer prompts you to confirm the database user password:
Confirm the password for database 552xadmin user:
27 Retype the password and press ↵.
Result: The installer prompts you for the database admin application user password:
Enter the password for database admin application user (no space allowed) 
[ mysql (default) ]:
28 Perform one of the following steps:
• To use the default password, press ↵.
• To set the database admin application user password, enter the new password and press 
↵.
Result: The installer prompts you to confirm the database admin application user password:
Confirm the password for database admin application user:
29 Retype the password and press ↵.
Result: The installer prompts you for the database replicationuser password:
Enter the password for database replication user ( no space allowed) [ 
Note 1 — 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.
Note 2 — If you choose no, one of the following result can occur.
• the OSS returns an error
• the service request is timed out
• the 5520 AMS client shows exception errors
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 109
 
mysql (default) ]:
30 Perform one of the following steps:
• To use the default password, press ↵.
• To set the database replication password, enter the new password and press ↵.
Result: The installer prompts you to confirm the database replication user password:
Confirm the password for database replication user:
31 Retype the password and press ↵. 
32 On Red Hat Enterprise Linux systems:
33 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. 
If you are installing: then
Simplex, data server, or 
combination of 
application and data 
server
The installer displays the following message:
Checking LVM Database partition...
OK
Checking packages....
OK
Application server The installer displays the following message:
Checking packages....
OK
Installing the 5520 AMS solution components
110
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 31 Installation result
34 The installer prompts you to activate the product.
Do you want to activate this product [yes (default)/no]?
35 Type y and press ↵.
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!
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 111
 
Table 32 Activation result
Installing the 5520 AMS solution components
112
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 36
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!
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 113
 
36 For Red Hat Enterprise Linux systems, update the firewall configuration. For more 
information on updating the firewall, see Procedure 44.
Procedure 16 To manually configure sudo
Perform the following procedure to manually configure sudo:
1 Navigate to etc/sudoers.d directory.
2 In a Text editor, 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.
7.4 Saving the configuration settings for 
installation of a 5520 AMS server
Use Procedure 17 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.
Note — If the --includevapsplugs option was not used, install the other 
5520 AMS solution components separately. See Section 7.5.
Applies to — This procedure is applicable for Red Hat Enterprise Linux 
only.
Installing the 5520 AMS solution components
114
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
The saved configuration file is used to retrieve the user inputs while installing and 
activating the 5520 AMS solution in a non-interactive mode.
Before you proceed, ensure to perform the relevant pre-requisite tasks. See 
Section 7.2.
Procedure 17 To save the configuration settings for the installation of a 5520 AMS 
server
1 Log in to the server as root.
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 14.
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:
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.7-999000.
operating_system is the Red Hat Enterprise Linux operating system.
architecture is x86_64 for Red Hat Enterprise Linux.
path_and_filename is the location and name of the configuration file in the server. For example, /tmp/simplex.
Note — Prior to installing and activating the 5520 AMS solutionusing 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.
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." 
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 115
 
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 ]?
4 Type y and press ↵.
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.
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 15.
7.5 Installing 5520 AMS NE plug-ins, 
5529 Enhanced Applications and plug-ins, 
and patches and emergency fixes
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.
You can also execute the ams_install script with --cluster option to install, deactivate, 
and activate the 5520 AMS solution components. By executing the script on a local 
host, the install, deactivate, and activate actions are executed on all the servers in 
the 5520 AMS cluster. Before the actual execution starts, the following prompt is 
displayed indicating the list of hosts that will be altered, and a confirmation message 
appears.
ams_install will alter the software configuration on following hosts:
135-249-12-43, 135-249-12-44, 135-249-12-45
Are you sure you want continue[ no (default) | yes ]?
For more information, see the 5520 AMS Administrator Guide.
Installing the 5520 AMS solution components
116
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
When you install the 5520 AMS client, download corresponding plug-in updates to 
the client application. 
7.5.1 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_y.y.yy-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.y.yy is the AMS release number
nnnnnn is the build number.
An example of a plug-in file is plugin-combo-isam-fgn4.4-2.0_9.7-359631.bin, which 
is used to manage the 7302/7330 ISAM FTTN, Release FGN4.4.
7.5.2 Patch software file
The patch software file will be in the format:
installation_filename.bin
where:
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.7.x-999000, 
where x indicates the patch release number.
operating_system is the Red Hat Enterprise Linux operating system.
architecture is x86_64 for Red Hat Enterprise Linux.
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.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 117
 
7.5.3 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.7-999000.
x is the emergency fix version.
7.5.4 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.5.00_9.7.
nnnnn is the build number.
operating_system is the Red Hat Enterprise Linux operating system.
architecture is x86_64 for Red Hat Enterprise Linux.
For example, app-apc-9.7.xx-xxxxxx -redhat-x86_64.bin.
The 5529 Enhanced Applications NE plug-in software file will be in the same format 
as the NE plug-in. For the software file format, see Section 7.5.1.
For information about 5529 Enhanced Applications, see the documentation for the 
application.
7.5.5 Nokia Access Virtualizer Adaptor plug-ins software 
file
Application and NE support plug-ins for Nokia Access Virtualizer Adaptor are 
installed and activated using the same scripts as plug-ins for the 5520 AMS. 
Note — If the app-apc is activated during the combo plug 
installation, then the plugin-apc is automatically activated.
Installing the 5520 AMS solution components
118
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
See the Getting started with Nokia Access Virtualizer Adaptor and 5520 AMS/5529 
Enhanced Applications Guide for information about the NE software plug-in formats 
for the 5520 AMS.
7.5.6 Installing and activating the 5520 AMS solution 
components
Table 33 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 7.3.
Table 33 Install and activate the 5520 AMS solution components
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 4.4.
If you are installing and activating a patch individually, see the installation and 
activation tasks in Section 4.5.
If you are installing and activating an emergency fix individually, see the installation 
and activation tasks in Section 4.6.
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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ command. Procedure 27
2 Install and activate the 5520 AMS solution components together or 
individually.
Procedure 18 or Procedure 21
3 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ command. Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ command. Procedure 25
You have completed the set of installationand activation tasks.
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.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 119
 
In a cluster installation, the procedures must be performed on each server in the 
cluster.
To perform the procedures in this section, you must be able to log in to the 5520 AMS 
servers as amssys.
Procedure 18 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 7.2.
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: 
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 servers before starting the updated 
server.
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.
Installing the 5520 AMS solution components
120
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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)] 
?
5 Perform one of the following steps:
• 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)] :
6 Perform one of the following steps:
• 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.7 and press ↵, only the 5520 AMS 
solution components containing 9.7 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
2 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 ↵.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 121
 
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:
Enter the full path to the directory containing the software to be 
installed: directory
Do you want to activate the software once it is installed [y|n (default)]? 
y or n
Are you sure you want to Install [y|n (default)] ?
where:
directory is the directory you entered in step 4.
y or n is the choice you entered in step 5.
8 Type y and press ↵.
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.
Installing the 5520 AMS solution components
122
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 19 To activate the 5520 AMS NE plug-ins, 5529 Enhanced 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.
Before you proceed, ensure that:
• The 5520 AMS solution components you are activating are installed. See Procedure 18.
• You are able to log in to the 5520 AMS server as amssys.
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
q) Quit
h) Help
Choice: 
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.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 123
 
3 Type a and 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)] :
4 Perform one of the following steps:
• 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.7 and press ↵, only the 5520 AMS 
solution components containing 9.7 in the filename will be displayed.
• To display all 5520 AMS solution components in the directory, press ↵.
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-
1 5520 AMS solution component filename
2 5520 AMS solution component filename
x) Execute
q) Quit
Choice: 
5 Perform the following steps: 
i Type the number corresponding to a 5520 AMS solution component you need to 
activate 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 activate, 
type x and press ↵.
Result: The script displaysa summary of your choices and prompts you to confirm: 
Summary:
- Selection: 
Installing the 5520 AMS solution components
124
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
list of the 5520 AMS solution components you chose
Are you sure you want to Activate [y|n (default)] ?
6 Type y and press ↵.
Result: The activation proceeds, displaying success messages for each 5520 AMS solution 
component.
The script presents the main menu.
7 To quit, type q and press ↵.
7.5.7 Deactivating the 5520 AMS solution components
Table 34 lists the tasks to deactivate the 5520 AMS solution components together or 
individually.
Table 34 Deactivate the 5520 AMS solution components
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”.
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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ 
command.
Procedure 27
3 Deactivate the 5520 AMS solution components together or 
individually.
Procedure 18 for deactivating the 
5520 AMS solution components together 
or individually.
Procedure 21 for deactivating the 
5520 AMS solution components together.
4 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ 
command.
Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ 
command.
Procedure 25
You have completed the set of deactivation tasks.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 125
 
If you are deactivating a patch individually, see the deactivation tasks in 
“Deactivating patches”.
If you are deactivating an emergency fix individually, see the deactivation tasks in 
“Deactivating emergency fixes”.
Procedure 20 To deactivate 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 5520 AMS solution components you are deactivating are activated. See Procedure 
19.
• You are able to log in to the 5520 AMS server as amssys.
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 d and press ↵.
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 
active. Deactivate that one first.
Installing the 5520 AMS solution components
126
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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)] :
4 Perform one of the following steps:
• 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.7 and press ↵, only the 5520 AMS 
solution components containing 9.7 in the filename will be displayed.
• To display all 5520 AMS solution components in the directory, press ↵.
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-
1 5520 AMS solution component filename
2 5520 AMS solution component filename
x) Execute
q) Quit
Choice: 
5 Perform the following steps: 
i Type the number corresponding to a 5520 AMS solution component you need to 
deactivate 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 deactivate, 
type x and press ↵.
Result: The script displays a summary of your choice and prompts you to confirm: 
Summary:
- Selection: 
list of the 5520 AMS solution components you chose
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 127
 
- Options:
Are you sure you want to Deactivate [y|n (default)] ?
6 Type y and press ↵.
Result: The deactivation proceeds, displaying the success message.
The script presents the main menu. 
7 To quit, type q and press ↵.
If you have deactivated the 5529 Enhanced Applications and plug-ins, then you need to delete the 
5520 AMS client user workspace directory available at @user.home/5520AMS/<Release>.
7.5.8 Installing, activating or deactivating the 5520 AMS 
solution components
Use Procedure 21 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 
plug-ins, 5529 Enhanced Applications and plug-ins, and patches and emergency 
fixes together.
For the complete list of tasks to install and activate the 5520 AMS solution 
components, see Table 33.
For the complete list of tasks to deactivate the solution components, see Table 34.
Procedure 21 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.
Installing the 5520 AMS solution components
128
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Before you proceed, ensure that the relevant pre-requisite tasks are performed. See Section 7.2.
1 Log in to the 5520 AMS server as amssys.
2 Execute one of the following commands:
Scenario Execute the following command: Result
Install and activate 
5520 AMS NE 
plug-ins, 
5529 Enhanced 
Applications and 
plug-ins, and patches 
and emergency fixes 
together or as 
individual components
ams_install.sh --installActivate 
directory_path ↵
where directory_path is the path to the directory 
containing the .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 the 
absolute path and filename of each .bin file.
The installer displays the summary of the selected 
5520 AMS solution components.
If you used the --installActivate option or the --install 
option, the installer then proceeds to install each 
5520 AMS solution component, and displays the status 
of each installation: 
Installing application <installation 
.bin file>
Installing application...
Extracting application 
content.........................done
Installation Complete!
If you used the --installActivate option, or the --activate 
option, the installer then proceeds to activate each each 
5520 AMS solution component, 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_dire
ctory>
Copying files 
(gui/server/script)...done
Activation Complete!
Install 5520 AMS NE 
plug-ins, 
5529 Enhanced 
Applications and 
plug-ins, and patches 
and emergency fixes 
together or as 
individual components
ams_install.sh--install 
directory_path ↵
Activate 5520 AMS NE 
plug-ins, 
5529 Enhanced 
Applications and 
plug-ins, and patches 
and emergency fixes 
together or as 
individual components
ams_install.sh --activate 
directory_path ↵
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 129
 
7.6 Verifying the installed software components 
on the 5520 AMS server
Use this procedure to compare the system configuration with the 
GoldenEMSSwConfig file.
Procedure 22 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 ↵
Deactivate 5520 AMS 
NE plug-ins, 
5529 Enhanced 
Applications and 
plug-ins, and patches 
and emergency fixes 
together
ams_install.sh --deactivate ↵ The installer displays the summary of the active 
5520 AMS solution components that will be deactivated. 
The installer then proceeds to deactivate each 
5520 AMS solution component, and displays the status 
of each deactivation: 
Deactive application 
<application_name>
<application_name> has been 
successfully deactivated!
done
Scenario Execute the following command: Result
Installing the 5520 AMS solution components
130
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Result: The command generates the GoldenEMSSwConfig file with details of the installed 
server components.
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
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.
Installation and Migration Guide Installing the 5520 AMS solution components
Issue: 01 3JL-01001-BTAA-RJZZA 131
 
6 errors found 
7.7 Modifying the parameter values in the 
configuration file
After the 5520 AMS installation, you can modify the value of the parameters in the 
configuration file (ams.conf) available at $AMS_SOFTWARE_HOME/conf/. The 
parameters that can be modified are:
• AMS_CLIENT_CONNECT_IP
• AMS_BLOCK_IP
• AMS_PROCESSMONITOR_TRACELEVEL
• AMS_REPLICATION_TRACELEVEL
• AMS_SCRIPTS_TRACELEVEL
• AMS_CLIENT_BIND_IP
• AMS_NE_BIND_IP
• AMS_OS_SERVICE_METHOD
• AMS_CLIENT_NETWORK
• AMS_NE_NETWORK
• AMS_CLIENT_NETWORK_NIC
• AMS_NE_NETWORK_NIC
Note — In the Data server, you can only view the details of the software 
components such as core, patches, and emergency fixes.
Installing the 5520 AMS solution components
132
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Activating, starting and stopping the servers
Issue: 01 3JL-01001-BTAA-RJZZA 133
 
8 Activating, starting and stopping 
the servers
8.1 Activating, starting and stopping the servers
8.1 Activating, starting and stopping the servers
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. 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.
Activating the software ensures that the plug-in installation environment is ready and 
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 23 To activate a server
Before you proceed:
• The server must be installed.
• You must be able to log in to the server as root.
1 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.
release is the release of the 5520 AMS software. An example is ams-9.7-999000.
Procedure 24 To start a server
Use this procedure to start a server.
Activating, starting and stopping the servers
134
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 ↵
Procedure 25 To start a cluster
Use this procedure to start all the servers in a cluster.
Note 1 — 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.
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.
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.
Installation and Migration Guide Activating, starting and stopping the servers
Issue: 01 3JL-01001-BTAA-RJZZA 135
 
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 ↵
• To start a single application server in the cluster, type:
ams_server start ↵
Procedure 26 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 27 To stop a cluster
Use this procedure to stop all the servers in a cluster.
Activating, starting and stopping the servers
136
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 one of the following commands:
• To stop the whole cluster, type:
ams_cluster stop ↵
• To stop a single application server in the cluster, type:
ams_server stop maintenance ↵
Note 1 — The ams_cluster script options ams_cluster stop or 
ams_cluster restart stop the servers in the 5520 AMS cluster in 
maintenance mode. No NE rebalancing is performed during ams_cluster 
stop or restart options.
Note 2 — The ams_server script option ams_server stop maintenance 
stops the server in maintenance mode. No NE rebalancing is performed 
when one or more servers are stopped using ams_server stop 
maintenance option.
Installation and Migration Guide Configuring the 5520 AMS to support NAT
Issue: 01 3JL-01001-BTAA-RJZZA 137
 
9 Configuring the 5520 AMS to 
support NAT
9.1 Configuring the 5520 AMS to support NAT
9.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 28 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. 
2 To open the configuration file, type:
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.
Configuring the 5520 AMS to support NAT
138
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4 Save and exit the ams.conf file. 
5 Perform one of the following steps:
• 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 ↵
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA 139
 
10 Converting a simplex installation 
to a cluster
10.1 Converting a simplex installation to a cluster
10.2 Adding and removing servers
10.3 Redistributing management of NEs
10.4 Convert a cluster with single NIC to inter-cluster
10.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 35 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 Nokia to update your license.
• You must be able to log in to the servers as amssys.
Table 35 Convert from a simplex installation to a cluster
Task 
#
Task See
1 Set up the cluster infrastructure. Chapter 5
2 Perform the following on the simplex server:
• Log in to the server as amssys.
• To stop the server, type: 
ams_server stop ↵
• Run the script to convert the simplex server to a cluster server.
• To start the server, type: 
ams_server start ↵
Procedure 29 to run the script to convert 
a simplex server to a cluster server
3 Install and activate the 5520 AMS solution on the new application 
servers. Verify that you have installed all the plug-ins you need.
Procedure 15
4 Start the new application servers. Procedure 24
(1 of 2)
Converting a simplex installation to a cluster
140
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 29 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 network interface used for cluster communication:
Enter the network interface used for cluster communication:
eth2
The cluster interface is “eth2”
Is this correct [no (default) | yes ]? yes
3 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) ]:
4 Perform one of the following steps:
• To accept the default IP address, press ↵.
• Type a different IP address and press ↵.
Result: The script prompts you to confirm the multicast IP address. 
5 Apply the updated license to all the application servers in the new 
cluster.
Procedure 55
You have completed the set of conversion tasks.
Task 
#
Task See
(2 of 2)
Caution — The multicast IP address must be kept the same for all 
database and application server installations.
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA 141
 
5 Perform one of the following steps:
• 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) ]:
6 Perform one of the following steps:
• To accept the default IP address, press ↵.
• Type a different IP address and press ↵.
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" ]?
7 Perform one of the following steps:
• To accept the default data server, press ↵.
• 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 ]?
8 Perform one of the following steps:
• To continue, press ↵.
• To update AMS configuration, type Yes and press ↵.
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
Caution — The multicast IP address must be kept the same for all 
database and application server installations.
Converting a simplex installation to a cluster
142
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.7.00-282513/bin/ams_updatefirewall 
script for more details.
* You need to be root to actually apply these changes.
9 Return to Table 35 to resume the conversion tasks.
10.2 Adding and removing servers
Servers can be added to, and removed from, a cluster after you have created it.
10.2.1 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 30 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.
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA143
 
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.
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 Administration→EMS System→Site→Application & 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.
5 Restart the cluster by typing: 
ams_cluster restart ↵
Procedure 31 To update the SSH key of a server in a cluster
In a cluster, when the operating system is reimaged in an existing application server or a data 
server, perform the following steps to update the SSH key:
1 Stop the server that was reimaged. To stop the server, type
ams_server stop
Note — Server and application multicast IP addresses must be the 
same as the existing ones.
Converting a simplex installation to a cluster
144
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
2 On the remaining servers, run the following command to delete the old SSH key of the 
reimaged server:
ams_cluster deletehost <reimaged_server_ip address>
3 Run the following command to restart all the servers in the cluster and ensure that the old 
SSH key is deleted.
ams_cluster restart
4 Start the server that is reimaged. For information to start the server, see Procedure 88.
10.2.2 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 32 describes how to remove an application 
server from a cluster in the 5520 AMS.
Procedure 32 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.
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.
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA 145
 
• 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 
Administration→EMS System→Site→Application & 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.
Converting a simplex installation to a cluster
146
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
10.3 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. You can 
redistribute the management of NEs in the following ways:
• Export NE data from the old server and import it to the new server
• Move AMS backup from old server to new server, and reduce data
10.3.1 Export NE data from the old server and import it to 
the new server
Procedure 33 describes how to split NE data using the export and import method.
Procedure 33 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 Administration→User Management→Active 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. 
Note 1 — To import NE data, source and the target servers 
must have the same 5520 AMS release, patch, and the 
emergency fix version.
Note 2 — 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.
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA 147
 
3 Choose File→Export.
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 loggedin under EMS Administration→User Management→Active Sessions in the 
Administration perspective.
8 Migrate data in preparation for import to the 5520 AMS:
i From the 5520 AMS menu, choose File→Import.
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.
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.
Converting a simplex installation to a cluster
148
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 Nokia 
technical support at http://support.alcatel-lucent.com. See Procedure 5 for more 
information.
10.3.2 Move AMS backup from old server to new server, 
and reduce data
You can move the AMS backup from old server to new server, and reduce data.
The following table provides high-level procedure for splitting the AMS into two 
systems:
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.
http://support.alcatel-lucent.com
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA 149
 
Table 36 High-level procedure for splitting AMS
Task 
#
Task On original 
AMS 
(AMS1)
On new 
AMS 
(AMS2)
See
1 Create Partition Access Profile 
“managedNe”
x 5520 AMS Administrator 
Guide
2 Create Partition Access Profile 
“unmanagedNe”
x
3 Assign PAP-Group “allManagedNe” 
to PAP “managedNe”
x
4 Assign all NE to PAP “managedNe” x
5 Change Operator-Defaults to make 
PAP-Group “allManagedNe” as 
default
x
6 Assign all users to “allManagedNe” 
PAP and remove from allPAPs
x
7 Configure a new AMS x 5520 AMS Installation and 
Migration Guide
8 Configure AMS backup on the new 
AMS
x 5520 AMS Administrator 
Guide
9 Check OSS connectivity with new 
AMS
x 5520 AMS Installation and 
Migration Guide
10 Configure schedule backup on the 
slave database server (unpacked with 
automatic transfer on second 
instance) using 
“ams_schedule_backup” script
x 5520 AMS Administrator 
Guide
11 Stop both clusters on the new AMS 
using “ams_cluster stop” script, in 
case they are running 
x
12 Restore database backup of preferred 
data server on the new AMS
x
13 Start preferred data server of the new 
AMS using “ams_server start” script
x
14 Start all application servers of the new 
AMS using “ams_server start” script
x
15 Install license on the new AMS x 5520 AMS Installation and 
Migration Guide
16 (Optional) Verify NP tracking settings 
on the new AMS
x NP documentation
This task is only required if 
you have installed NP. 
Please contact your Nokia 
representative for further 
information.
(1 of 3)
Converting a simplex installation to a cluster
150
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
17 Stop supervision of NE that are 
transferred to the new AMS
x 5520 AMS User Guide
18 Stop supervision of NE that are 
managed by the original AMS
x
19 Assign NE managed by the new AMS 
to “PAPunmanagedNe”
x 5520 AMS Administrator 
Guide
20 Assign NE managed by the original 
AMS to “PAPunmanagedNe”
x
21 Assign NE-group managed by the 
new AMS to “PAPunmanagedNe”
x
22 Assign NE-group managed by the 
original AMS to “PAPunmanagedNe”
x
23 Start OSS provision x 5520 AMS Installation and 
Migration Guide
24 Start AMS standby data server on the 
new AMS using “ams_server start” 
script
x 5520 AMS Administrator 
Guide
25 (Optional) Start Geographic 
Redundancy on the new AMS
x 5520 AMS Installation and 
Migration Guide
26 Remove the old host names and site 
names from the original AMS
x
27 (Optional) Clean-up APC database on 
the original AMS
x APC documentation
28 (Optional) Clean-up NP database on 
the original AMS
x NP documentation
This task is only required if 
you have installed NP. 
Please contact your Nokia 
representative for further 
information.
29 Remove unmanaged NEs from the 
original AMS
x 5520 AMS User Guide
30 (Optional) Clean-up APC database on 
the new AMS
x APC documentation
31 (Optional) Clean-up NP database on 
the new AMS
x NP documentation
This task is only required if 
you have installed NP. 
Please contact your Nokia 
representative for further 
information.
32 Remove unmanaged NEs from the 
new AMS
x 5520 AMS User Guide
Task 
#
Task On original 
AMS 
(AMS1)
On new 
AMS 
(AMS2)
See
(2 of 3)
Installation and Migration Guide Converting a simplex installation to a cluster
Issue: 01 3JL-01001-BTAA-RJZZA 151
 
10.4 Convert a cluster with single NIC to 
inter-cluster
In a cluster with a single NIC, the cluster traffic is also routed through the same NIC. 
In a small cluster, this configuration is ideal. But, in a cluster with two or more 
application and data servers, the cluster traffic affects the bandwidth usage of the 
client, OSS, and NE when there is only one NIC to handle the network traffic.
You can reconfigure a cluster with single NIC and route the traffic to the correct 
interfaces such as cluster, client, or NE; and improve network security. 
To reconfigure a cluster with a separate NIC, perform the steps mentioned in 
Procedures 34 and 35. 
Procedure 34 To convert a cluster with single NIC to inter-cluster
You must login to the server as amssys or root user.
1 Stop the cluster.
2 Execute the ams_change_ip_subnet_server script on each server in the cluster. 
33 (Optional) Defragment the database 
on the original AMS to free up disk 
space using “ams_db_defragment” 
script
x 5520 AMS Administrator 
Guide
34 (Optional) Defragment the database 
on the new AMS to free up disk space 
using “ams_db_defragment” script
x
Warning — The service provisions are lost between the backup 
time and the actual AMS split time, and should preferably be 
re-played.
Note — During maintenance window, you need to perform only 
the tasks from 11 to 23.
Task 
#
Task On original 
AMS 
(AMS1)
On new 
AMS 
(AMS2)
See
(3 of 3)
Converting a simplex installation to a cluster
152
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
For information about using the ams_change_ip_subnet_server script, see the 5520 AMS 
Administrator Guide.
3 Restart each server in the cluster using ams_server start script.
At the end, clear the information that were there on the old servers, that is, the 
servers using the old IP address. For instance, tables such as 
ProvisionedClusterNodeDetail, DataServer, ProvisionedClusterNode, and Alarms 
tables with old data will be removed. For information about how to cleanup the old 
alarms from the database, see Procedure 35. 
Procedure 35 To cleanup old alarms from the database
Perform one of the following actions to cleanup the old alarms from the database:
• Using the client: From the AMS client, navigate to EMS Administration → EMS System 
→ Site (server_name) → Application & Data Servers → <old machine IP address>. 
Right-click and Delete the old machine.
• Using the command line: Execute 'ams_cluster deletehost <old machine IP address>’ 
script.
Note— If the networking information of the client NIC is modified, you 
must manually enter a new IP address in the login window. 
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 153
 
11 Configuring geographic 
redundancy
11.1 Overview
11.2 Ping-pong protection
11.3 Configuring geographic redundancy
11.4 Configuring the OSS arbiter
11.5 Modifying geographic redundancy
11.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 4.3.
11.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 both Application and 
Data server (AD) 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.
Configuring geographic redundancy
154
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
When ping-pong protection is initiated, both servers can refuse to start. To overrule 
the ping-pong protection, perform Procedure 36.
Procedure 36 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.
11.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. 
Configure data replication on each data server at the active site and standby site. 
See Table 20 for the context in which to perform this procedure. 
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.
Note — Starting the servers depends on the system state. If the system 
state indicates healthy, the servers are started automatically.
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.
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 155
 
Before you proceed:
• The servers must be activated.
• You must be able to log in to the servers as amssys.
Procedure 37 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: 
4 Perform one of the following steps:
• 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-
Configuring geographic redundancy
156
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 ]?
7 Type y and press ↵.
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 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)
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 157
 
 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 ]
12 Perform one of the following steps:
• 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 ]
13 Type y and press ↵.
14 Repeat steps 2 to 13 on the data servers at the standby site.
15 Start the servers at the active site. See Procedure 24.
Note — If you have a second data server at the active site, repeat the 
procedure for the second server. 
Configuring geographic redundancy
158
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
16 To verify that theJBoss 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.
17 Start the servers at the standby site. See Procedure 24.
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 38 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.
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.
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 159
 
Result: When a site becomes unreachable, the 5520 AMS will initiate your script.
11.4 Configuring the OSS arbiter
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 39 To configure 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 configuration script, type:
DEMO_IT_infrastructure_integration config ↵
Result: The script prompts you for the IP address of the preferred data server at the active 
site:
Enter the IP address of the preferred data server of active site
3 Enter the IP address and press ↵.
Note — The OSS arbiter is not provided by Nokia.
Caution — The DEMO_IT_infrastructure_integration script is intended 
for demonstration purposes only. Nokia 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.
Configuring geographic redundancy
160
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Result: The script prompts you for the IP address of the non-preferred data server at the 
active site:
Enter the IP address of the non-preferred data server of active site
4 Enter the IP address and press ↵. 
5 If there is only one data server at the active site, 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 data server of standby site
6 Enter the IP address 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 data server of standby site
7 Enter the IP address and press ↵. 
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)?
9 Type y and press ↵.
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 and 10 for each of the other data servers.
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 161
 
The configuration is complete.
Procedure 40 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 
11.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 37 to modify geographic 
redundancy.
Configuring geographic redundancy
162
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 37 Modify geographic redundancy
To perform the procedures in this section, you must be able to log in to the servers 
as amssys.
Procedure 41 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.
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.
Option See
Perform a manual 
switchover
Procedure 41
Disable geographic 
redundancy
Procedure 42
Trigger a forced full 
synchronization
Procedure 43
Note — The server does not allow to switch between active and standby 
sites in a running state. Nokia 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]
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 163
 
• 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 42 To change a geographically redundant installation to two 
independent sites
1 Log in to the data server at either site as amssys. 
2 To run the geographic redundancy configuration script, type:
ams_geo_configure.sh ↵
Result: The script prompts you for the desired change:
Which actions to perform:
[ 1 ] Switch site mode (active→standby) or (standby→active)
 2 Disable geographical redundancy
 3 Force fullsynchronization on next periodic synchronization
 4 Exit
Choice:
3 Type 2 and press ↵.
Result: The script prompts you to confirm:
Note — If geographical redundancy is disabled, the automatic 
switchover will be disabled.
Note — If you are a logged in to the standby server, the switch mode 
option available to the operator is (standby →active).
Configuring geographic redundancy
164
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Are you sure you want to disable geographic redundancy? [ no (default) | 
yes ]
4 Type y and press ↵.
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 ↵
11.5.1 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.
Procedure 43 To trigger a forced full synchronization of shared data
1 Log in to the data server at the active site as amssys.
2 To run the geographic redundancy configuration script, type:
ams_geo_configure.sh ↵
Result: The script prompts you for the desired change:
Which actions to perform:
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.
Installation and Migration Guide Configuring geographic redundancy
Issue: 01 3JL-01001-BTAA-RJZZA 165
 
[ 1 ] Switch site mode (active→standby) 
 2 Disable geographical redundancy
 3 Force full synchronization on next periodic synchronization
 4 Exit
Choice:
3 Type 3 and press ↵.
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.
Configuring geographic redundancy
166
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Updating firewall rules
Issue: 01 3JL-01001-BTAA-RJZZA 167
 
12 Updating firewall rules
12.1 Overview
12.2 Updating firewall rules
12.1 Overview
The ams_updatefirewall script is used to add, show, or remove port(s) used by 5520 
AMS and 5529 Enhanced Applications.
For information about executing the ams_updatefirewall script and the available 
options, see the 5520 AMS Administrator Guide.
12.2 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 the NE ports are open.
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 44 on Red Hat Enterprise Linux systems to update the firewall 
rules. 
Applies to — This chapter applies to Red Hat Enterprise Linux 
systems only.
Updating firewall rules
168
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 44 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 firewall is 
displayed. The following message is displayed:
Do you want to add these ports to the firewall [ no (default) | yes ]?
3 To add the missing ports to the firewall, type y and press ↵.
Result: The missing ports are added to the firewall. The following message is displayed:
Adding ports to the firewall …
Done …
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 169
 
13 Installing the 5520 AMS client
13.1 Client installation overview
13.2 Installing multiple 5520 AMS clients
13.3 Installing a single 5520 AMS client
13.4 Installing a shared 5520 AMS client
13.5 Launching and updating the 5520 AMS client
13.6 Automatic client upgrade during patch and emergency fix installation
13.7 Changing passwords for default users in the 5520 AMS GUI
13.8 Adding a license to the 5520 AMS
13.1 Client installation overview
You have three options for deploying the 5520 AMS client application:
Table 38 Types of client installation
Note
(1) Nokia does not recommend to have multiple installations on the Windows client.
13.1.1 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.
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.
Installing the 5520 AMS client
170
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
13.1.1.1 Shared client installation in Red Hat Enterprise 
Linux
On Red Hat Enterprise Linux servers, a root user and a non root user can install the 
5520 AMS client in the shared configuration. Whereas, if the root user launches or 
starts the client for the first time after the AMS Client installation, the root user cannot 
launch or start the client. So, upon installing the AMS GUI, as a root user in shared 
mode option, “-protect root” is added to amsclient.ini file properties. This enables the 
root user to launch or start the client.
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 installationprogram creates the root user group 
and user account if they do not already exist on the host server. The default root 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.
The following scenarios are applicable for a root user and a non root user in shared 
client installation.
• Shared client installation by a root user
• Restricted mode - As a root user and users of root user group, you can launch the 
5520 AMS client. Only a root user can install and update the Plugins.
• Unrestricted mode - Any user can launch the 5520 AMS client. Only a root user can 
install and update the Plugins.
Note — Nokia recommends that a root user should not 
re-launch the client after installation. This will prevent a root 
user from launching the client. 
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 171
 
• Shared client installation by a non root user
• Restricted mode - As a non root user and users of non root user group, you can 
launch the 5520 AMS client. Only a non root user can install and update the Plugins.
• Unrestricted mode - Any user can launch the 5520 AMS client. Only a non root user 
can install and update the Plugins.
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 Section 13.4.1.
13.1.1.2 Shared client software updates in Red Hat 
Enterprise Linux
For the first login, the updates are triggered automatically. The automatic download 
of updates are enabled for shared installations. The user can apply software 
updates, which are periodically available from the 5520 AMS server, to their own 
GUI, but the core code is still shared. However, these updates do not impact the 
other users GUI.
If you are already logged in, then you must manually trigger software updates.
13.1.1.3 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.
13.1.2 Client installation tasks
Table 39 lists the tasks to install the 5520 AMS client. 
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.
Note — For users to have access to the install and update 
menu items, they must launch the client from the installation 
directory.
Installing the 5520 AMS client
172
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 39 Install the 5520 AMS client
13.2 Installing multiple 5520 AMS clients
If a user tries to install multiple 5520 AMS clients on a Red Hat Enterprise Linux 
operating system as amssys, it results in an error of Out of Memory Exception. To 
prevent this, you can run the ams_update_limit_conf.sh script to bring up multiple 
AMS clients.
13.3 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, 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. 
Task 
#
Task See
1 Install the 5520 AMS client application in single or 
shared configuration.
• Procedure 45 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 46 to install a shared client on a Windows 
server
• Procedure 47 to install a shared client on Red Hat 
Enterprise Linux presentation server.
2 Launch the client and apply software updates 
available from the 5520 AMS server.
Procedure 50
3 Update passwords for the amsftp or amssftp user 
if needed.
Procedure 54
4 Apply license keys. Section 13.8
You have completed the set of client installation tasks.
Note 1 — Nokia 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.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 173
 
From Release 9.7 onwards, authentication is required to download the client 
software from a 5520 AMS application server.
With valid user credentials, you can successfully download the new version of AMS 
client.
Procedure 45 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.7 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:
https://server:8443/ams-client ↵
where:
server is the IP address or DNS name of the 5520 AMS application server.
Result: A login screen appears.
3 Enter the user name and password.
Result: The 5520 AMS Client Distribution page opens with instructions for downloading the 
5520 AMS client.
Installing the 5520 AMS client
174
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4 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.
5 Perform one of the following:
• 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
Enter the path to the OpenJDK 8 installation directory (default = 
/usr/lib/jvm/java-1.8.0-openjdk.x86_64):
The openjdk path is /usr/lib/jvm/java-1.8.0-openjdk.x86_64Do 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
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 175
 
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.
• Perform one of the following steps:
• 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.
13.4 Installing a shared 5520 AMS client
A shared installation is possible in Windows or Red Hat Linux operating systems. 
See Section 13.1.1 for more information about the capabilities, limitations, and 
options available to you for a shared client installation.
Procedure 46 describes how to install a shared client in Windows.
Procedure 47 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 48. 
From Release 9.7 onwards, authentication is required to download the client 
software from a 5520 AMS application server.
With valid user credentials, you can successfully download the new version of AMS 
client.
Procedure 46 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:
• The 5520 AMS server must be installed, activated, and running.
• You need the IP address or DNS name of a 5520 AMS, Release 9.7 application server.
• You need access to a Web browser.
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.
Installing the 5520 AMS client
176
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
4 Open a Web browser and navigate to the client distribution page on the 5520 AMS 
server.Type the following URL:
https://server:8443/ams-client ↵
where:
server is the IP address or DNS name of the 5520 AMS application server.
Result: A login screen appears.
5 Enter the user name and password.
Result: The 5520 AMS Client Distribution page opens with instructions for downloading the 
5520 AMS client.
6 Click the Download Client (Windows PC) link, and save the resulting file to the local system.
7 Navigate to the location where you saved the client installation file and unzip it into the 
directory you created in step 2.
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.
8 By default, the location of the 5520 AMS client user workspace and configuration directories 
is @user.home/5520AMS/9.7. 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.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 177
 
Procedure 47 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:
• The 5520 AMS server must be installed, activated, and running.
• You need the IP address or DNS name of the 5520 AMS, Release 9.7 application server.
• You need access to a Web browser.
• 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. 
2 Open a Web browser and navigate to the client distribution page on the 5520 AMS server. 
Type the following URL:
https://server:8443/ams-client ↵
where:
 server is the IP address or DNS name of the 5520 AMS application server.
Result: A login screen appears.
3 Enter the user name and password.
Result: The 5520 AMS Client Distribution page opens with instructions for downloading the 
5520 AMS client.
4 Click the Download Client (Redhat PC X86_64) link, and save the resulting file to the local 
system.
5 Navigate to the location where you saved the client installation file 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.
6 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:
Installing the 5520 AMS client
178
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Enter the path to the OpenJDK 8 installation directory (default = 
/usr/lib/jvm/java-1.8.0-openjdk.x86_64):
The openjdk path is /usr/lib/jvm/java-1.8.0-openjdk.x86_64
Do you want a single installation used by multiple operators (shared 
installation)? [ yes (default) | no ]
7 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.
8 Perform one of the following steps:
• 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.
9 Perform one of the following steps:
• To accept the default /opt directory, press ↵.
• 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 ↵.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 179
 
Result: The installation proceeds and the client application is put in the directory you 
selected. A log of the installation is created and stored at 
/tmp/ams-client-installation.nnnn.log, where nnnn is a random numerical value.
13.4.1 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 createindividual 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 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.
To use the shared client wrapper in a cluster, perform the following procedures:
• Install the client and wrapper. See Procedure 48 for more information.
• Configure the presentation server to use the wrapper. See Procedure 49 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.
Warning — The use of the client wrapper script creates a 
working environment that is not secure. If your environment 
does not meet the criteria, Nokia does not recommend using 
the client wrapper script. 
Installing the 5520 AMS client
180
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 48 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.
2 Open a Web browser and navigate to the client distribution page on the 5520 AMS server. 
Type the following URL:
https://server:8443/ams-client ↵
where:
server is the IP address or DNS name of the 5520 AMS server.
Result: A login screen appears.
3 Enter the user name and password.
Result: The 5520 AMS Client Distribution page opens with instructions for downloading the 
5520 AMS client.
4 Click the Download Client (Redhat PC X86_64) link, and save the resulting file to the local 
system.
5 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.
6 To run the client installer, type:
filename --sharedunixaccountwrapper ↵
Result: The installer checks for the appropriate operating system, then begins the installation 
process.
The installer prompts you for the client installation type:
Do you want a single installation used by multiple operators (shared 
installation)? [ yes (default) | no ]
7 Press ↵.
Result: The installer prompts you for installation restrictions:
Restrict the usage of software to amssys group? [ no (default) | yes ]
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 181
 
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.
8 Perform one of the following steps:
• 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.
9 Perform one of the following steps:
• To accept the default /opt directory, 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 and stored at 
/tmp/ams-client-installation.nnnn.log, where nnnn is a random numerical value.
Procedure 49 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. 
Installing the 5520 AMS client
182
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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”
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.
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.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 183
 
13.5 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 Help→Install 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 installation, for the first login, the updates are 
triggered automatically. The automatic download of updates are enabled for shared 
installations. If you are already logged in, then you must manually trigger software 
updates as described in Procedure 50.
In a shared Windows installation, only users with write access to the client installation 
directory can download software updates.
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 machinemust 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 — 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.
Installing the 5520 AMS client
184
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 50 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.
Note 1 — 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>/keyst
ore, where ams-client-installation-path is the full path of the 
5520 AMS client.
• Djavax.net.ssl.keystore=<ams-client-installation-path>/keysto
re, where ams-client-installation-path is the full path of the 
5520 AMS client.
Note 2 — To ensure that the 5520 AMS client login happens on 
the last reachable server in a network without any login 
attempts on the other configured networks, you must change 
the following configuration in the amsclient.ini file in the 5520 
AMS installation directory, as below:
-Dignore.rmi.address.cache=false
Enable cache once for each 5520 AMS client after the 
installation / reinstallation, and it cannot be enabled or disabled 
per user on a presentation server.
Set this parameter to true if you want to disable the cache (it is 
disabled by default):
-Dignore.rmi.address.cache=true
Note 3 — If you are installing 5 or more NE plug-ins in the 5520 
AMS GUI, you must increase the allocated memory. In the 
amsclient.ini file, update the Xmx parameter value from 512 MB 
to 1024 MB.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 185
 
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 ↵
Installing the 5520 AMS client
186
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
Result: The 5520 AMS client opens and displays a login window.
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. 
7 Perform one of the following steps:
• 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. 
Note — If you need to start the client in the background, type:
client_dir/ams/ams ↵
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 187
 
8 Perform one of the following steps:
• 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.
• 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:
• In the 5520 AMS GUI menu, choose Help→Install.
Result: The Install/Update window opens.
• Click Search for new features to install, and click Next.
Result: The Install window opens.
• Go to step 10.
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.
9 Perform one of the following steps:
• To download all available updates, click Yes.
• 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.
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 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
Installing the 5520 AMS client
188
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
11 To install the features in the default directory, go to step 12.
Else, change the installation directory for a plug-in:
i Select the plug-in from the list.
Result: The New Update Site window appears.
ii To select a configured location, or add a new location, click Add New and navigate to 
the location in the resulting navigation window.
iii Repeat the above two steps for each plug-in whose installation directory you need to 
change.
12 Click OK in the New Update Site window.
Result: The window closes.
13 Click Finish.
Result: The Verification→Feature Verification window opens.
14 Perform one of the following steps:
• If you have selected multiple features in step 10, click Install All.
• If you have 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.
15 Perform one of the following steps:• 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 — Nokia recommends that you use the default installation 
directory.
Note — Some feature updates may not appear properly until you restart 
the client.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 189
 
Procedure 51 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:
client_dir is the installation directory you chose when you installed the client.
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 52 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:
client_dir is the installation directory you chose when you installed the client.
Result: The 5520 AMS client opens and displays a login window.
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:
client_dir is the installation directory you chose when you installed the client.
Installing the 5520 AMS client
190
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Result: In the GUI login window, the site name is visible in the drop-down list to all other 
users.
Procedure 53 To display hours in the 0 to 24 convention in the 5520 AMS client
Perform this procedure on Windows, 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 system, open the config.ini file and type:
vi config.ini ↵
4 Add the following lines:
osgi.nl=en
country.code=GB 
5 Save and close the file.
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.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 191
 
13.6 Automatic client upgrade during patch and 
emergency fix installation
During a patch or emergency fix installation, the 5520 AMS client is upgraded 
automatically on the 5520 AMS server and all workstations. You can also take a 
backup of the current 5520 AMS GUI software.
13.6.1 Saving the current 5520 AMS GUI
After a successful patch or emergency fix installation, when you log on to the client 
for the first time, the Update Found window appears. Select the Save the current 
5520 AMS GUI software to a backup location before proceeding with upgrade check 
box. The client software is saved in the backup location. 
If the patch or emergency fix does not contain any fix for the 5520 AMS client , then 
the Update Found window does not appear when you log on to the client.
13.6.2 Roll back to an earlier version of the 5520 AMS GUI
If the new patch or emergency fix does not function as intended and are uninstalled, 
then you can use the earlier version of the 5520 AMS client from the backed up 
location.
13.7 Changing passwords for default users in the 
5520 AMS GUI
Use this procedure if you have changed the passwords of the amsftp or amssftp 
users in the 5520 AMS server. Refer 5520 AMS Administrator Guide for more 
information.
Installing the 5520 AMS client
192
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 54 To change a default user password in the 5520 AMS GUI
1 Log in to the 5520 AMS client as an administrator.
2 In the Administration Tree, choose one of the following options: 
• EMS Administration→Configuration→EMS/NE Protocols→File Server 
Credentials→SFTP User
• EMS Administration→Configuration→EMS/NE Protocols→File Server Credentials→FTP 
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. 
13.8 Adding a license to the 5520 AMS
Your license from Nokia 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 39 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.
Caution — Passwords for the amsftp and amssftp users cannot include 
the @ or : symbols.
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 193
 
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 55.
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 56.
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. 
Procedure 55 To add a license key from the 5520 AMS GUI
1 In the Administration Tree, choose EMS Administration→License.
2 Right-click License and choose Create→License. 
Result: The Create License window opens.
3 Perform one of the following steps:
• 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.
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 followingformat: 
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. 
Installing the 5520 AMS client
194
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Result: The licenses are verified and installed. In case an error occurs, no license will be 
installed. See Table 41 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 56 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 40 License installation from the 5520 AMS server
Note
(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 41 for the scenarios in which installation of licenses may fail.
13.8.1 License installation error scenarios
Table 41 lists the scenarios in which a license installation may fail.
To install licenses Command options Command example
From a single file ams_install_license.sh [--force] 
<full path and name of license file> 
ams_install_license.sh --force /var/opt/tmp/license/license.txt
From multiple files ams_install_license.sh [--force] 
<full path and name of license 
file1>, <full path and name of 
license file2>, <full path and name 
of license filen>
ams_install_license.sh --force /var/opt/tmp/license/license.txt, 
/var/opt/tmp/license/license.tar, /var/opt/tmp/license/license.pdf
From multiple files of 
the same file format 
supported by 
wildcard file 
selection pattern
ams_install_license.sh [--force] 
<full path to license file>/*.<file 
extension>
ams_install_license.sh --force /var/opt/tmp/license/*.pdf 
 or
ams_install_license.sh --force /var/opt/tmp/license/9.7*.txt 
Installation and Migration Guide Installing the 5520 AMS client
Issue: 01 3JL-01001-BTAA-RJZZA 195
 
Table 41 License installation error scenarios
Error Scenario The license installation fails with the error message:
If an error occurs while processing 
the license file
Error processing license [txt/pdf/tar] file {file name}
If no license is found or the license 
file is corrupted
License file {file name} corrupted or doesn't contain license 
keys
If a file format other than .pdf, .txt, 
or.tar is uploaded
The uploaded license file format { file name } is not supported
If the path and filename entered in 
the License File field is incorrect
The uploaded license file { file name } doesn't exist
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
Expired license
If you install a license the host ID of 
which does not match the host ID of 
the 5520 AMS server
The hostid in the license does not match the hostid of the 
server(s) {host id present in the license key}
Installing the 5520 AMS client
196
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide 5520 AMS server maintenance
Issue: 01 3JL-01001-BTAA-RJZZA 197
 
14 5520 AMS server maintenance
14.1 Overview
14.1 Overview
In a 5520 AMS cluster configuration, server maintenance can be performed without 
AMS downtime cluster node by cluster node to avoid server downtime during 
maintenance. 
Each physical server in a cluster can function as an Application server (A), Data 
server (D), both Application and Data server (AD), as an arbiter server or even 
presentation server. Maintenance upgrade can be performed in different cluster 
setups such as:
• A+A+A+D+D
• AD+AD
• A+AD+AD
• Arbiter server
• Presentation server
Procedure 57 5520 AMS server maintenance in a cluster
Use the following procedure to perform server maintenance in cluster configurations.
Pre-requisites:
• Ensure that the database is backed up and up-to-date.
• Check the correctness of replication of each application and data server. 
1 Log in to the standby data server and stop the 5520 AMS application. Then perform the 
server maintenance and restart the 5520 AMS application.
2 Log in to the active data server and stop the 5520 AMS application. Ensure that the other 
data server becomes master. Then perform the server maintenance and restart the 5520 
AMS application.
3 Log in to the non-master application server and stop the 5520 AMS application in 
maintenance mode by executing ams_server stop maintenance. Then perform the server 
maintenance and restart the 5520 AMS application.
5520 AMS server maintenance
198
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4 Repeat step 3 for all non-master application servers.
5 Log in to the master application server and stop the 5520 AMS application in maintenance 
mode by executing ams_server stop maintenance. Ensure that the other application server 
becomes master. Then perform the server maintenance and restart the 5520 AMS 
application.
Note — All active client sessions will be disconnected and you will need 
to log in again.
Installation and Migration Guide Migrating to the 5520 AMS, Release 9.7
Issue: 01 3JL-01001-BTAA-RJZZA 199
 
Migrating to the 5520 AMS, Release 
9.7
15 Migrating to the 5520 AMS, Release 9.7
16 Migration scenarios and associated task list
17 Pre-migration tasks
18 Migration tasks
19 Post-migration tasks
Migrating to the 5520 AMS, Release 9.7
200
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Migrating to the 5520 AMS, Release 9.7
Issue: 01 3JL-01001-BTAA-RJZZA 201
 
15 Migrating to the 5520 AMS, 
Release 9.7
15.1 Migration overview
15.2 Installing the 5520 AMS, Release 9.7 on the same server running an 
earlier 5520 AMS release
15.3 Migrating NEs
15.4 Migration dependencies of the data migration script
15.5 Updating software plug-ins to a new version
15.6 External TL1 Gateway migration
15.7 Migration with a customized keystore
15.8 Migrating templates
15.9 Migrating licenses
Migrating to the 5520 AMS, Release 9.7
202
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
15.1 Migration overview
You can migrate a simplex installation, a cluster installation or a geographically 
redundant installation to the 5520 AMS, Release 9.7 from the supported 5520 AMS 
releases. Table 42 lists the supported migration paths, and the data migration 
strategy.
Note 1 — 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.
Note 2 — If you use Nokia 5529 Enhanced Applications in 
addition to the 5520 AMS, see the 5529 Enhanced Applications 
product documentation for migration information specific to the 
application.
Note 3 — In the migration support between operating systems, 
rollback is not supported. For example, the current release 
supports both Red Hat Enterprise Linux versions 6.x in the 
RHEL6 stream and 7.x in the RHEL7 stream. So when the 
upgrade happens from 6.x to 7.x, rollback is not supported.
Note 4 — From release 9.6.07 onwards, full automatic rollback 
might not always be feasible. For information on the supported 
rollback scenarios, see Section 17.6.
Installation and Migration Guide Migrating to the 5520 AMS, Release 9.7
Issue: 01 3JL-01001-BTAA-RJZZA 203
 
Table 42 Supported migration path and data migration strategyMigration path Data migration strategy
From To
5520 AMS, Release 
9.6.0x
5520 AMS, Release 9.7 Data is migrated:
• 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.
5523 AWS NE list data from 5523 AWS is imported 
using the export/import option on the 5520 
AMS, Release 9.7. See Redistributing 
management of NEs.
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.7.
Note — Migrating to the 5520 AMS, Release 9.7 volume 
contains references to the earlier 5520 AMS release. The 
earlier 5520 AMS release may refer to the 5520 AMS, 9.6.0x, 
or 9.6 depending on the earlier release from which data is 
migrated to the 5520 AMS, Release 9.7.
Migrating to the 5520 AMS, Release 9.7
204
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
15.1.1 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 by using the ams_migrate script
• Manual in-place migration 
15.1.1.1 Automated in-place migration
The ams_migrate script can be used to perform an automated in-place migration on: 
a simplex system, an AMS cluster, or geographically redundant systems. The 
automated scripts are run in the background based on the inputs you provide, when 
prompted during the migration process.
For a 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 you to select individual menu options, if you 
want to perform a specific task. For example, you can choose to perform any one of 
the following actions:
• Distribute and install software
• AMS backup
• Activate AMS
Note — Ensure to follow the specific instructions displayed on 
your screen that prompt you during the automated in-place 
migration process.
Note — If prompted at the time of a rollback to the previous 
version of the AMS release, then you must start a second 
session and execute the ams_activate.sh command, as 
instructed by the display on your screen.
Installation and Migration Guide Migrating to the 5520 AMS, Release 9.7
Issue: 01 3JL-01001-BTAA-RJZZA 205
 
• Copy AMS data
• Migrate to the new AMS version
• Configure the AMS license
• Configure SSL
• Rollback to an earlier AMS version
To choose the option:
• At the choose prompt, type the action-option that you want to perform, 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.
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.
From release 9.7, for migration the user must execute the --migrate script from the 
source release software bin directory. For example, 
ams-9.7.0-393857-redhat-x86_64.bin --migrate.
For the detailed sequence of automated in-place migration for simplex, cluster or 
geographically redundant site installations, see Chapter 16.
For the detailed execution of the script, see Procedure 58.
All the actions and messages during the script execution are captured in a log file 
named ams_migration.log.
Note — Ensure to follow the specific instructions displayed on 
your screen that prompt you during script execution.
Note 1 — If the automated in-place migration is unsuccessful, 
navigate to the software bin directory of the new release 
(Release 9.7) and execute the following command to resume 
the migration:
ams_migrate
Note 2 — For automated in-place migration,
• use --migrate script for migration from release 9.6.0 or later 
releases; example, for migration from release 9.6.03 to 9.7.
Migrating to the 5520 AMS, Release 9.7
206
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
15.1.1.2 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 22.2. For information on the manual in-place migration 
procedure, see Procedure 78.
15.1.2 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 16.
Note — If you want to save the site configuration from an earlier 
5520 AMS release, use the same site name.
If you migrate from an earlier 5520 AMS release to the new 
release with different site name, a new site is created with 
default values. The migration preserves the old site 
configuration where you can view the old values and fill the new 
site accordingly post migration.
Note — In case of an out-of-place migration, the password of 
amssftp or amsftp does not match between the 5520 AMS 
server and OS which results in the failure of NE backup, 
restore, LRM and software download. In order to avoid failure 
of NE backup, you must synchronize the amssftp or amsftp 
password manually. You can either update the amssftp or 
amsftp password of the 5520 AMS server through the 5520 
AMS client or change the amssftp or amsftp account password 
through the terminal.
See the 5520 AMS Administrator Guide for more information 
about changing the password for amssftp or amsftp.
Installation and Migration Guide Migrating to the 5520 AMS, Release 9.7
Issue: 01 3JL-01001-BTAA-RJZZA 207
 
15.2 Installing the 5520 AMS, Release 9.7 on the 
same server running an earlier 5520 AMS 
release
You can install the 5520 AMS, Release 9.7 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 beforestarting them for the other.
If you install the 5520 AMS, Release 9.7 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.
15.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.7 will be displayed with an invalid NE 
Type/Release in the 5520 AMS GUI.
If any of the NEs that you migrate has an xVPS agent, Nokia recommends that you 
verify that the VLAN bridges are intact after completing the migration.
15.4 Migration dependencies of the data migration 
script
This section lists the migration dependencies for the data migration script.
15.4.1 Data not migrated from the earlier 5520 AMS release
Table 43 lists the data not migrated from the earlier 5520 AMS release to the 
5520 AMS, Release 9.7.
Note — You can delete the NEs with an invalid NE 
Type/Release from the GUI. See the 5520 AMS User Guide.
Note — When you migrate from the earlier 5520 AMS release 
to the 5520 AMS Release 9.7, it takes around 30 minutes after 
the startup, for the 5520 AMS application to receive traps from 
the managed network elements.
Migrating to the 5520 AMS, Release 9.7
208
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Before performing a migration, record any data listed in Table 43 that you plan to 
reconfigure in the 5520 AMS, Release 9.7. Back up any files containing data listed 
in Table 43, and that you need to preserve following the migration, before uninstalling 
the earlier 5520 AMS release.
Table 43 Data not migrated from the earlier 5520 AMS release to the 
5520 AMS, Release 9.7
15.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 44 lists 
the tasks to update a software plug-in to a new version.
Table 44 Updating a software plug-in to a new version
Data Comments
Cluster switchover script The switchover_hook.sh script is not migrated.
5520 AMS and 5529 Enhanced 
Applications Licenses
The 5520 AMS and 5529 Enhanced Applications licenses are not 
migrated.
Task 
#
Task See
1 Back up 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 26
To stop all servers in a cluster setup, use the ‘ams_cluster stop’ 
command.
Procedure 27
3 Deactivate and uninstall the existing software plug-in.
Uninstalling the existing software plug-in is optional. In case of 
issues during upgrade, you can roll back to the previous software 
plug-in, if it is not uninstalled.
Procedure 20 to deactivate the software 
plug-in.
Procedure 74 to uninstall the software 
plug-in.
4 Install and activate the new software plug-in. Procedure 18 or Procedure 21
5 Start the 5520 AMS.
To start the server in a simplex setup, use the ‘ams_server start’ 
command.
Procedure 24
To start all servers in a cluster setup, use the ‘ams_cluster start’ 
command.
Procedure 25
You have completed the set of tasks required to update a software plug-in to a new version.
Installation and Migration Guide Migrating to the 5520 AMS, Release 9.7
Issue: 01 3JL-01001-BTAA-RJZZA 209
 
15.6 External TL1 Gateway migration
Any External TL1 Gateways migrated from the earlier 5520 AMS release will be 
associated with the current active Site object in the 5520 AMS, Release 9.7.
15.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.7.
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.
15.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.
15.9 Migrating licenses
When migrating from the 5520 AMS release earlier than 9.6, only the ISAM feature 
licenses are migrated.
When migrating from the 5520 AMS Release 9.6 or later, all the licenses are 
migrated.
Migrating to the 5520 AMS, Release 9.7
210
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Installation and Migration Guide Migration scenarios and associated task list
Issue: 01 3JL-01001-BTAA-RJZZA 211
 
16 Migration scenarios and 
associated task list
16.1 Overview of the migration scenarios
16.2 Automated in-place migration from an earlier 5520 AMS release to the 
5520 AMS, Release 9.7
16.3 Out-of-place migration from an earlier 5520 AMS release to the 5520 
AMS, Release 9.7
16.4 Checking the consistency of alarm rules after migration
16.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.7:
• 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.7.
• 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.7.
Before you proceed to perform the migration tasks:
• You need root or amssys access to all servers.
• Ensure to take a backup of the 5520 AMS database.
Based on the migration strategy, Table 45 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.7. 
Migration scenarios and associated task list
212
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Table 45 Migration path and data migration strategy for automated 
in-place and out-of-place migrations
16.2 Automated in-place migration from an earlier 
5520 AMS release to the 5520 AMS, Release 
9.7
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.7 release, see the tasks listed in the Table 47. To perform an 
in-place migration manually, see Appendix 22.
Table 46 Automated in-place migration path and data migration strategy
Table 47 Automated in-place migration for simplex, cluster, and geographical redundant in-
stallations
Migration path Migration strategy See
From
(5520 AMS, 
Release)
To
5520 AMS, 
Release 9.6.0x
5520 AMS, 
Release 9.7
In-place migration Section 16.2
Out-of-place migration Section 16.3
Migration path See
From To
5520 AMS, Release 
9.6.0x
5520 AMS, 
Release 9.7
Table 47
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 in 
the 5520 AMS server.
Procedure 56
3 Transfer the 5520 AMS, Release 9.7 software to the 5520 AMS server. Section 17.2
4 Install the 5520 AMS, Release 9.7 software to the 5520 AMS server.
Note - The 5520 AMS, Release 9.7 software needs to be transferred to a 
single server in the cluster. The ams_migrate script enables automatic 
distribution and installation of the software to other servers in the cluster.
Procedure 58
(1 of 2)
Installation and Migration Guide Migration scenarios and associated task list
Issue: 01 3JL-01001-BTAA-RJZZA 213
 
16.3 Out-of-place migration from an earlier 5520 
AMS release to the 5520 AMS, Release 9.7
Based on the migration strategy,Table 48 lists the task tables for an out-of-place 
migration of a simplex, cluster, and geographically installation to the 5520 AMS, 
Release 9.7. 
Table 48 Out-of-place migration path and data migration strategy
Migration tasks (service affecting)
5 Execute the ams_migrate script.
Note - In a cluster setup after the migration, the active data server and all 
the application servers are automatically started except the standby data 
server. Once the migration is performed successfully, start the standby 
data server manually.
Section 17.4
6 Rollback 
In the event of an unsuccessful migration, the ams_migrate script will 
rollback to the previous active software version on all servers and the 
servers are in stopped state. In a cluster setup, you need to start the 
servers manually. 
Section 17.4
Supported rollback scenarios Section 17.6
Post-migration tasks (non-service affecting)
7 Install the 5520 AMS, Release 9.7 client. Section 18.10
8 Launch the 5520 AMS, Release 9.7 client. Section 18.11
9 (Optional) Import GUI settings. Section 19.3
10 (Optional) If the Release 9.7 is successfully operational, then uninstall the 
earlier 5520 AMS release.
Section 22.5.2
You have completed the set of automated in-place migration tasks.
Task # Task See
(2 of 2)
Migration path See
From To
5520 AMS, Release 
9.6.0x
5520 AMS, 
Release 9.7
Table 49
Table 50
Table 51
Migration scenarios and associated task list
214
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
16.3.1 Out-of-place simplex migration
Table 49 lists the tasks to perform an out-of-place migration from an earlier 
5520 AMS release to the 5520 AMS, Release 9.7, if your original site was configured 
as a simplex setup.
Table 49 Simplex migration - Out-of-place
Task # Task See
Pre-migration tasks
1 Transfer the 5520 AMS, Release 9.7 software to the 5520 AMS server. Section 17.2
2 Install and activate the 5520 AMS Release 9.7 on a new 5520 AMS 
server.
Section 17.4
3 Install and activate the required 5520 AMS NE plug-in Release 9.7 
versions, and 5529 Enhanced Applications and plug-in Release 9.7 
versions that you are migrating from the earlier 5520 AMS release.
Section 17.5
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.7, their persistency 
will not be migrated. These plug-ins cannot be migrated 
later.
Migration tasks
4 (Optional) Migrate the switchover script to the 5520 AMS, Release 9.7 
server.
Section 18.2
5 If you are using a customized keystore, enable SSL. Section 18.3
6 Back up the database of the earlier 5520 AMS release. Section 18.5
7 Transfer the backup file of the earlier 5520 AMS release to the 
5520 AMS, Release 9.7 server.
Section 18.6
8 Copy the data of the earlier 5520 AMS release from the backup file to the 
5520 AMS Release 9.7 directories using the ams_copy_datafiles script.
Section 18.7
9 Start the 5520 AMS, Release 9.7 server. Section 18.8
10 Add licenses for the 5520 AMS installation using the script. Section 18.9
11 Install the 5520 AMS, Release 9.7 client. Section 18.10
12 Launch the 5520 AMS, Release 9.7 client. Section 18.11
13 If you are migrating ONT SIP data from 7342 ISAM FTTU R4.9 or earlier, 
update the anonymous FTP user path.
Section 18.12
Post-migration tasks
14 (Optional) Import GUI settings. Section 19.3
15 (Optional) Delete the former site of the earlier 5520 AMS release. Section 19.4
You have completed the set of migration tasks.
Installation and Migration Guide Migration scenarios and associated task list
Issue: 01 3JL-01001-BTAA-RJZZA 215
 
16.3.2 Out-of-place cluster migration
Table 50 describes the tasks to perform an out-of-place migration from the earlier 
5520 AMS release to the 5520 AMS, Release 9.7, if your original site was configured 
as a cluster. 
Table 50 Cluster migration - Out-of-place
Note — Before shutting down the data servers in a cluster 
record the last active data server. This information is required 
when starting the servers in a cluster.
Task # Task See
Pre-migration tasks
1 Transfer the 5520 AMS, Release 9.7 software to the 5520 AMS servers 
in the cluster.
Section 17.2
2 Perform the following steps to install and activate the 5520 AMS, Release 
9.7 on new hardware:
• 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.
Section 17.4
3 Install and activate the required 5520 AMS NE plug-in Release 9.7 
versions, and 5529 Enhanced Applications and plug-in Release 9.7 
versions that you are migrating from the earlier 5520 AMS release.
Section 17.5
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.7, their persistency 
will not be migrated. These plug-ins cannot be migrated 
later.
Migration tasks
4 (Optional) Migrate the switchover script. Section 18.2
5 If you are using a customized keystore, enable SSL. Section 18.3
6 Back up the database of the earlier 5520 AMS release. Section 18.5
7 Transfer the backup file of the earlier 5520 AMS release to the 
5520 AMS, Release 9.7 servers.
Section 18.6
8 Copy the data of the earlier 5520 AMS release from the backup file to the 
5520 AMS Release 9.7 preferred data servers using the 
ams_copy_datafiles script.
Section 18.7
(1 of 2)
Migration scenarios and associated task list
216
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
16.3.3 Out-of-place geographically redundant migration
Table 51 describes the tasks to perform an out-of-place migration from an earlier 
5520 AMS release to the 5520 AMS, Release 9.7, if your original site was configured 
as a geographically redundant setup. 
Table 51 Geographically redundant migration - Out-of-place
9 Start the following 5520 AMS, Release 9.7 servers (in the following 
order):
• Arbiter server, if applicable.
• Last active 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.
Section 18.8
10 Ensure that the migration is complete, using the ams_server status 
command.
Section 18.8
11 In a cluster setup after migration, all the servers (application and data) are 
started except for the standby data server. 
Section 18.8
12 Add licenses for the 5520 AMS installation using the script. Section 18.9
13 Install the 5520 AMS, Release 9.7 client. Section 18.10
14 Launch the 5520 AMS, Release 9.7 client. Section 18.11
15 If you are migrating ONT SIP data from 7342 ISAM FTTU R4.9 or earlier, 
update the anonymous FTP user path.
Section 18.12
Post-migration tasks
16 (Optional) Import GUI settings. Section 19.3
17 (Optional) Delete the former site of the earlier 5520 AMS release. Section 19.4
You have completed the set of migration tasks.
Task # Task See
(2 of 2)
Task # Task See
Pre-migration tasks
1 Disable geographic redundancy. Section 11.5
2 Transfer the 5520 AMS, Release 9.7 software to the 5520 AMS servers 
in the geographically redundant site.
Section 17.2
(1 of 3)
Installation and Migration Guide Migration scenarios and associated task list
Issue: 01 3JL-01001-BTAA-RJZZA 217
 
3 Perform the following steps on new active and standby sites to install and 
activate the 5520 AMS, Release 9.7:
• 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 additionaldedicated 5520 AMS application 
servers that will be part of your cluster.
• Install and activate the arbiter server, if your cluster includes one.
Note - For a standby site, an installation is recommended instead of 
migration. After installation, sync the standby site with an active site which 
is already migrated.
Section 17.4
4 Install and activate the required 5520 AMS NE plug-in Release 9.7 
versions, and 5529 Enhanced Applications and plug-in Release 9.7 
versions that you are migrating from the earlier 5520 AMS release.
Section 17.5
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.7, their persistency 
will not be migrated. These plug-ins cannot be migrated 
later.
Migration tasks
5 (Optional) Migrate the switchover script. Section 18.2
6 If you are using a customized keystore, enable SSL. Section 18.3
7 Enable geographic redundancy. Section 18.4
8 Back up the database of the earlier 5520 AMS release. Section 18.5
9 Transfer the backup file of the earlier 5520 AMS release to the 5520 AMS, 
Release 9.7 servers in the active site.
Section 18.6
10 Copy the data of the earlier 5520 AMS release from the backup file to the 
5520 AMS, Release 9.7 preferred data server at the active site using the 
ams_copy_datafiles script.
Section 18.7
11 Start the following 5520 AMS, Release 9.7 servers (in the following 
order):
• Arbiter server at the active site, if applicable.
• Preferred data server at the active site.
• One of the application servers at the active site.
The application server that is started first becomes the master application 
server.
Starting the application server triggers the migration.
Section 18.8
12 Ensure that the migration is complete, using the ams_server status 
command.
Section 18.8
Task # Task See
(2 of 3)
Migration scenarios and associated task list
218
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
16.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.
13 Start the following 5520 AMS, Release 9.7 servers (in the following 
order):
• 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.
Section 18.8
14 Add licenses for the 5520 AMS installation at the active and standby site 
using the script.
Section 18.9
15 Install at least one 5520 AMS, Release 9.7 client. Section 18.10
16 Launch the 5520 AMS, Release 9.7 client. Section 18.11
17 If you are migrating ONT SIP data from 7342 ISAM FTTU R4.9 or earlier, 
update the anonymous FTP user path.
Section 18.12
Post-migration tasks
18 (Optional) Import GUI settings. Section 19.3
19 (Optional) Delete the former active and standby sites of the earlier 
5520 AMS release.
Section 19.4
You have completed the set of migration tasks.
Task # Task See
(3 of 3)
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 219
 
17 Pre-migration tasks
17.1 Overview of the pre-migration tasks
17.2 Transferring the 5520 AMS software to the 5520 AMS servers
17.3 Server configuration overview
17.4 Installing the 5520 AMS, Release 9.7 for migration
17.5 Installing the 5520 AMS solution software components for migration
17.6 Rollback scenarios
17.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.7.
For the complete list of tasks to migrate from an earlier 5520 AMS release to the 
5520 AMS, Release 9.7, see Chapter 16.
17.2 Transferring the 5520 AMS software to the 
5520 AMS servers
Pre-requisite: Access to product software packages. See Chapter 6.
Obtain the 5520 AMS, Release 9.7 software file from the Nokia 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.7-999000.
• operating_system is the Red Hat Enterprise Linux operating system.
• architecture is x86_64 for Red Hat Enterprise Linux.
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 backup tasks.
Pre-migration tasks
220
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
For information about downloading the 5520 AMS installation file, see Chapter 6.
Proceed to: Install the 5520 AMS Release 9.7 on the servers. Depending on the type 
of the setup, use the Section 17.4, to install the 5520 AMS, Release 9.7 for migration.
17.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 (AD)
• An Arbiter server (a), if applicable
For the server definitions, see Chapter 3.
17.4 Installing the 5520 AMS, Release 9.7 for 
migration
Pre-requisite: Transferring the 5520 AMS software to the 5520 AMS servers. See 
Section 17.2.
For more information on the 5520 AMS software installation and activation methods, 
see Section 7.1 to install 5520 AMS server software on a simplex, cluster or 
geographically redundant setup, in preparation for migrating to the 5520 AMS, 
Release 9.7 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.7, see Table 30.
• Ensure to perform LDAP authentication based on MD5 algorithm. 
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 221
 
• From release 9.6 onwards, the attribute name of LDAP dictionary file is updated 
to include Nokia; for example, Nokia-AMS-Description. This affects operators 
using LDAP for authorization. It will not affect operators using LDAP only for 
authentication. 
If you are using LDAP for authorization, when upgrading or migrating from the 
5520 AMS release earlier than 9.6 to 9.6.07 or later, to ensure that AMS is 
compatible with the LDAP configuration, update the AMS_USER_DICTIONARY 
parameter setting in the $AMS_SOFTWARE_HOME/conf/ams.conf file. This 
parameter is only available when the new version is activated.
For 5520 AMS to use the LDAP authorization names in release earlier than 9.6, 
you must update the AMS_USER_DICTIONARY parameter setting in the file to 
ALU. The default parameter value is Nokia. In a cluster setup, you need to update 
the configuration file on all the application servers. Restart the server to apply the 
changes.
If you are using LDAP only for authentication and not using it for authorization, no 
update required in the configuration file.
For more information, see LDAP authentication in the 5520 AMS Administrator 
Guide.
• Ensure that there is sufficient disk space for migration. For information on required 
disk space, see the 5520 AMS Solution Planning Guide.
• 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.
• When migratinga geographical redundant setup, do not perform migration on the 
active and standby sites in parallel. Complete the migration in the active site and 
then migrate the standby site.
• In order to complete the upgrade procedure successfully a valid and working 
operator account with superuser privileges must be available. Please verify the 
availability of such an account before starting the procedure.
Note — You can also install additional 5529 Enhanced 
Applications and NE plug-ins in the current 5520 AMS release.
Pre-migration tasks
222
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Use the procedure in this section to install the 5520 AMS, Release 9.7 on a simplex, 
cluster, or geographically redundant setup, in preparation for migration from an 
earlier 5520 AMS release.
For information on server configurations, see Section17.3.
 
Procedure 58 To install the 5520 AMS solution for migration
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 14.
Note 1 — 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.
Note 2 — If the user ‘system’ is already present in the 5520 
AMS, then it is renamed as “system__renamed” after migration.
Note 3 — The parameter values in the *.conf files, available in 
$AMS_SOFTWARE_HOME/conf, change to default values 
after the 5520 AMS migration. You need to configure these 
parameters manually after migration.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 223
 
3 Execute one of the following commands depending on the installation scenario:
Scenario Execute the following command: Result
Migrate all 5520 AMS 
solution components 
without a configuration 
file (recommended)
In the case of automated in-place migration:
./amscore.binary_filename.bin --migrate ↵
where:
amscore.binary_filename.bin is the name of the bin file.
For example:
ams--9.7-redhat-x64-12345.bin --migrate
The migration script displays the following 
confirmation:
Checking OS and version...
OK
[1] Distribute and install 
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 34.
Migrate all 5520 AMS 
solution components 
without a configuration 
file (recommended)
In the case of out-of-place migration:
./installation_filename.bin --activate-force 
--includevapsplugs directory_path ↵
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, the 
absolute path and filename of each .bin file needs to be specified. 
where:
release is the release of the VAP or NE plug-in. An example for is VAP 
is app-idm-1.0_9.7-246228.bin and for NE plug-in is 
plugin-combo-gpon-4.7-1.0_9.7-156320.bin.
The installation software displays the 
following confirmation:
Checking OS and version ... 
OK.
Checking hostname ... OK
Checking SSH (ssh, 
ssh-keygen, ssh-keyscan, scp, 
sftp) ...
The installer prompts you for the location of 
the SSH library:
Enter the path to the SSH 
tools [ /usr/bin (default) ]:
Proceed to step 5.
Migrate only the 5520 
AMS core software 
(excluding other 
solution components)
In the case of out-of-place migration:
./installation_filename.bin --activate-force ↵
Pre-migration tasks
224
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
4 The installer prompts you for the location of the SSH tools.
Enter the path to the SSH tools [ /usr/bin (default) ]:
5 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) ]:
6 The installer prompts you for the location of the OpenJDK8 installation directory.
Enter the path to the OpenJDK 8 installation directory (default = 
/usr/lib/jvm/java-1.8.0-openjdk.x86_64):
If the OpenJDK-8-devel directory path is other than the default directory path, enter the 
directory path.
/usr/local/java/java-1.8.0-openjdk.x86_64
Migrate all 5520 AMS 
solution components 
using a configuration 
file
In the case of out-of-place migration:
./installation_filename.bin -c 
path_and_filename --activate-force 
--includevapsplugs directory_path ↵
where:
path_and_filename is the location and name of the configuration file 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. 
./installation_filename.bin -c 
path_and_filename --includevapsplugs 
directory_path ↵
where:
path_and_filename is the location and name of the configuration file 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. 
The migration proceeds based on the 
settings saved in the configuration file. The 
choices saved in the configuration file are 
displayed. See Table 52 for the migration 
result.
Scenario Execute the following command: Result
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 225
 
7 The installer prompts you for the shell to be used by the amssys user.
• To assign the default shell, press ↵ .
• To assign a shell other than the default value, enter the path and shell. 
Enter the full path and executable file name of the default shell used 
by the amssys user [/bin/sh (default)]:
8 The installer prompts you for the name of the installation site.
Enter the site name that uniquely identifies the cluster (only 
alphanumeric, ‘-’, ‘_’ allowed):
9 Type a name for the site and press ↵.
Result: The installer prompts you to confirm the site name. 
Is this correct [ no (default) | yes ]?
10 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 ]?:
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.
Pre-migration tasks
226
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
11 Perform one of the following:
If then Result
The system is a simplex 
server
press ↵. The following prompts are displayed:
Enter the network interface(s) used for GUI clients 
communication:
Note: Multiple interfaces can be entered using a 
comma separated list eth1, eth2
The GUI client interface(s) is “eth1,eth2”
Is this correct [no (default) | yes ]? yes
Enter the network interface(s) used for NE 
communication:
Note: Multiple interfaces can be entered using a 
comma separated list eth1, eth2
The NE interface(s) is “eth1,eth2”
Is this correct [ no (default) | yes ]? yes
The client interface refers to both GUI and NBI interfaces.
Go to step 17.
The system is member of 
a cluster
type n and 
press ↵.
The installer prompts youfor the server role:
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 12.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 227
 
12 Perform one of the following steps:
If you need to migrate then Result
An application server type 1 and 
press ↵.
The installer prompts you for the network interface used for cluster 
communication:
Enter the network interface used for cluster 
communication:
eth2
The cluster interface is “eth2”
Is this correct [no (default) | yes]? yes
A data server type 2 and 
press ↵.
A combination of 
application and data 
server
type 3 and 
press ↵.
An arbiter server type 4 and 
press ↵.
Pre-migration tasks
228
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
13 Type y and press ↵ to accept the network interfaces or press ↵ for a prompt to modify the 
network interfaces.
If you are migrating then
An application server or a 
combination of 
application and data 
server
The installer prompts you for the multicast IP address for application information:
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 
information [225.1.2.6 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
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 14.
For combination of application and data server, go to step 15.
A data server The installer prompts you for the multicast IP address for server information:
Enter the multicast IP address to exchange server 
information [225.1.2.6 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
Note: Data server IP addresses should be reachable 
via the same network interface as the one used to 
exchange cluster information
Go to step 15.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 229
 
14 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
Is this correct [ no (default) | yes ]? y
where IP addresses is the list of the IP addresses or the DNS name installed on the server.
15 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”?
16 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.
An arbiter server The installer prompts you for the multicast IP address for server information:
Enter the multicast IP address to exchange server 
information [225.1.2.6 (default)]?
Multicast IP address
where:
The multicast IP address is: Multicast IP address you provided.
Is this correct [ no (default) | yes ]? y
Go to step 17.
Caution — The multicast IP address must be the same for all database 
and application server installations.
If you are migrating then
Pre-migration tasks
230
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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.
Perform one of the following steps:
• 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 migrating: Result
An application server The installer prompts you for interfaces to which GUI clients can connect:
Enter the network interface(s) used for GUI clients 
communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The GUI client interface(s) is “eth1,eth2”
Is this correct [no (default) | yes ]? yes
Enter the network interface(s) used for NE communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The NE interface(s) is “eth1,eth2”
Is this correct [ no (default) | yes ]? yes
The client interface refers to both GUI and NBI interfaces.
Go to step 17.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 231
 
17 The installer prompts you for the software installation directory:
In which top directory do you want to install the software [ /opt 
(default) ]?
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 17.
A combination of 
application and 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 server as the preferred data server, type y and press ↵. 
• To configure the server as a non-preferred data server, type n and press ↵. 
The installer prompts you for interfaces to which GUI clients can connect:
Enter the network interface(s) used for GUI clients 
communication:
Note: Multiple interfaces can be entered using a comma separated 
list eth1, eth2
The GUI client interface(s) is “eth1,eth2”
Is this correct [no (default) | yes ]? yes
Enter the network interface(s) used for NE communication:
Note: Multiple interfaces can be entered using a comma separated 
list ethi1, eth2
The NE interface(s) is “eth1, eth2”
Is this correct? [no (default) | yes ]? yes
The client interface refers to both GUI and NBI interfaces.
Go to step 17.
If you are migrating: Result
Pre-migration tasks
232
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
18 Perform one of the following steps:
• To accept the default /opt directory, press ↵.
• To modify the directory, enter the path and press ↵.
19 Perform one of the following steps:
• To accept the default /var/opt directory, press ↵.
• To modify the directory, enter the path and press ↵.
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 migrating: then
A simplex server, data 
server, combination of 
application and data 
server, or application 
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)]
Go to step 19.
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) ]?
Go to step 23.
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.
If you are migrating: then
A simplex server, data 
server, or a combination 
of application and data 
server
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 ?
(This location should be same in all the servers in the cluster)
Go to step 20.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 233
 
20 Perform one of the following steps:
• To accept the default /var/opt directory, press ↵.
• To modify the directory, enter the path and press ↵.
Result: 
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) ]?
(This location should be same in all the servers in the cluster)
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 ?
(This location should be same in all the servers in the cluster)
Go to step 21.
If you are migrating: then
Note — On Red Hat Enterprise Linux systems, to choose an LV, refer 
to the Procedure 10.
Note — The location entered here will be used by the installer to install 
the files designated as shared in an /ams/shared subfolder.
If you are migrating: then
A simplex server, or a 
combination of 
application and data 
server
The installer prompts you for the database installation directory:
In which top directory do you want to put the database storage?
Go to step 21.
A data server The installer prompts you for the database installation directory:
In which top directory do you want to put the database storage?
Go to step 23.
Pre-migration tasks
234
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
22 To accept the default /ams directory, press ↵. 
For simplex server, go to step 24
For application server or combination of application and data server, go to step 23
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 (default)| no]? 
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 ↵.
24 The installer prompts you for the database user password:
Enter the password for database 552xadmin user (no space allowed) [ mysql 
(default) ]:
Perform one of the following steps:
• To use the default password, press ↵.
• To set the database user password, enter the new password and press ↵.
Result: The installer prompts you to confirm the database user password:
Confirm the password for database 552xadmin user:
25 Retype the password and press ↵.
Result: The installer prompts you for the database admin application user password:
Note 1 — 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 2 — During operation, data required by the NE software migration 
tools will be copied to the location you entered here.
Note 1 — 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.
Note 2 — If you choose no, one of the following result can occur.
• the OSS returns an error
• the service request is timed out
• the 5520 AMS client shows exception errors
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 235
 
Enter the password for database admin application user (no space allowed) 
[ mysql (default) ]:
26 Perform one of the following steps:
• To use the default password, press ↵.
• To set the database admin application user password, enter the new password and press 
↵.
Result: The installer prompts you to confirm the database admin application user password:
Confirm the password for database admin application user:
27 Retype the password and press ↵.
Result: The installer prompts you for the database replication user password:
Enter the password for database replication user ( no space allowed) [ 
mysql (default) ]:
28 Perform one of the following steps:
• To use the default password, press ↵.
• To set the database replication password, enter the new password and press ↵.
Result: The installer prompts you to confirm the database replication user password:
Confirm the password for database replication user:
29 Retype the password and press ↵. 
30 On Red Hat Enterprise Linux systems:
If you are migrating: then
Simplex, data server, or 
combination of 
application and data 
server
The installer displays the following message:
Checking LVM Database partition...
OK
Checking packages....
OK
Application server The installer displays the following message:
Checking packages....
OK
Pre-migration tasks
236
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
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 52 Migration result
32 The installer prompts you to activate the product.
Do you want to activate this product [yes (default)/no]?
33 Type y and press ↵.
Result of migration
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, and 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 selected software components, and displays the 
following message:
Installing Patchs/EFs/Apps/Plugs/Vaps...
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: 
Installing application <installation .bin file>
Extracting application content.........................done
Installation Complete!
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 237
 
Table 53 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. 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:
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
For more information on updating the firewall, see Procedure 44.
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:
Activatingapplication <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!
Pre-migration tasks
238
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
34 For automated in-place migration, perform the following steps:
i Type x and press ↵.
ii The installer prompts you to stop the AMS system. 
Is it OK to stop the AMS now [ yes | no (default) ]?
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
Enter the GoldenEMSSwConfig file path [ ignore (default) ]:
Enter the full path to the directory containing the software to be 
installed:
Distribute and install software...
Note: This can take a few minutes...
Done
Activating new release...
*** WARNING ***
Next step will stop the running AMS system and thus the AMS and 
all its related services will not be available.
Go to step ii
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
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 239
 
iii Type ‘yes’ and press ↵.
Result 
Running ams_cluster stop...
All servers are activated.
Done
Copying data files...
Note: This can take a few minutes...
Done
Migrate and full start...
Starting 1st database server...
Starting 1st application server...
Not start the standby data server 10.1.1.121
Done
Pre-migration tasks
240
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
iv The installer prompts you to enter an option on the migration.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 241
 
Result 
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, you must go to the source 
release software bin directory and execute the ams_migrate script and choose 
the appropriate option.
• Choose ‘r’ to rollback to the previous version of the AMS release. When you type 
yes and press enter, the display is as follows:
Rollback...
Running ams_cluster stop... 
Revert chroot configuration of vsftpd and sshd service... 
All servers are activated.
Done. User can start manually the cluster
Note — If prompted at the time of a rollback to the previous version of the 
AMS release, then you must start a second session and execute the 
ams_activate.sh command, as instructed by the display on your screen.
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, you must go to the source 
release software bin directory and execute the ams_migrate script and choose 
the appropriate option.
• Choose ‘r’ to rollback to the previous version of the AMS release. When you type 
yes and press enter, the display is as follows:
Rollback...
Running ams_cluster stop... 
Revert chroot configuration of vsftpd and sshd service... 
All servers are activated.
Done. User can start manually the cluster
Note — If prompted at the time of a rollback to the previous version of the 
AMS release, then you must start a second session and execute the 
ams_activate.sh command, as instructed by the display on your screen.
Pre-migration tasks
242
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
v The installer prompts you to create an ams backup 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]
vi 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): 
vii 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
viii The installer prompts you to confirm the stop sequence.
is it okay to initiate AMS stop sequence [no(default)|yes]:
ix Type ‘yes’ and press ↵.
Result:
Running ams_cluster stop...
x The installer prompts you to activate the 5520 AMS 9.7 release. For more information 
on manually activating the release, refer to the 5520 AMS Administrator Guide.
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
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 243
 
xi Enter ‘y’ and press ↵.
xii 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]:
Result:
Done
Perform data copy...
Note: This can take a few minutes ...
Done
The script performs the migration and 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)]?
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, you must go to the source 
release software bin directory and execute the ams_migrate script and choose 
the appropriate option.
• Choose ‘r’ to rollback to the previous version of the AMS release.
Note — If prompted at the time of a rollback to the previous version of the 
AMS release, then you must start a second session and execute the 
ams_activate.sh command, as instructed by the display on your screen.
Pre-migration tasks
244
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
xiii Enter the path and press ↵.
Result: The migration script executes the ams_install_license script to configure the 
license.
Configure license...
Done
xiv The installer prompts you for enabling the SSL.
Do you want to enable SSL with the default AMS keystore [yes (default) 
| no]?
xv Type yes and press ↵, if you like to enable SSL with the default keystore.
Result: The migrate tool enables SSL using the default keystore shipped with the AMS 
software distribution.
Configure client SSL...
Done
xvi Type No and enter the full path to the keystore file and the keystore passwordin the 
appropriate fields, if you like to enable SSL with a customized keystore. 
Result: The migrate tool enables SSL using the Keystore path and password provided.
xvii To quit, type q and press ↵.
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.
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 17.5.
• If the required plug-ins have been installed during 5520 AMS 
installation, proceed to migrate the switchover_hook.sh script. See 
Section 18.2
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 245
 
17.5 Installing the 5520 AMS solution software 
components for 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.7. See Section 17.4.
• Installing the 5520 AMS, Release 9.7 in a cluster or a geographically redundant 
installation in preparation for migrating to the 5520 AMS, Release 9.7. See 
Section 17.4.
Use Procedure 59 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 15.5. 
You can also install the software components using the ams_install.sh script in the 
non-interactive mode. See Section 7.5 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.7, the 5520 AMS, Release 9.7 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 14.
• You must be able to log in to the 5520 AMS server as amssys.
Applies to — This procedure is applicable for out-of-place 
migration.
Pre-migration tasks
246
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Procedure 59 To install 5520 AMS solution software components for migration
1 Log in to the 5520 AMS server as amssys.
2 To run the installer script, type one of the following commands:
• If the active server is running the 5520 AMS, Release 9.7, type:
ams_install.sh ↵
• If the active server is running a release earlier than Release 9.7, to run the installer from 
5520 AMS, Release 9.7, 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.7-999000.
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)] 
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 247
 
?
5 Perform one of the following steps:
• 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:
Display only the items containing the following text [all items 
(default)] :
6 Perform one of the following steps:
• 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.7 and press ↵, only the software files 
containing 9.7 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: 
7 Perform the following steps: 
i Type the number corresponding to a software 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 ↵.
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.7.
Pre-migration tasks
248
Installation and Migration Guide
3JL-01001-BTAA-RJZZA Issue: 01
 
Result: The menu is presented again, with the numbers for the software components 
you chose in square brackets ([ ]).
ii To deselect an item, type the number again and press ↵.
iii When you have chosen all the software 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 enhanced applications/plug-ins you chose
- Options:
Enter the full path to the directory containing the software to be 
installed: directory
Do you want to activate the software once it is installed [y|n (default)]? 
y or n
Are you sure you want to Install [y|n (default)] ?
where 
directory is the directory you entered in step 4.
y or n is the choice you entered in step 5.
8 Type y and press ↵.
Result: The installation proceeds, displaying success messages for each plug-in.
The script presents the main menu. 
9 To quit, type q and press ↵.
Result: The 5520 AMS software components are installed for migration.
Installation and Migration Guide Pre-migration tasks
Issue: 01 3JL-01001-BTAA-RJZZA 249
 
Proceed to: Depending on the migration path, proceed to the applicable task:
17.6 Rollback scenarios
In a cluster setup after successful migration, you can perform a rollback to the 
previous active release during the following scenarios:
• With geographically redundant setup and a cluster with single data server. For 
information on how to perform a rollback in a geographically redundant setup, see 
Procedure 60 and for a cluster with single data server, see Procedure 61.
• Without the database switchover. For information on how to perform rollback, see 
Procedure 62.
• With database switchover. For information on how to perform rollback, see 
Procedure 63.
Procedure 60 Rollback in geographically redundant setup
In a geographically redundant setup if the migrated setup is having a problem, perform the 
following steps to rollback to the previous active release:
1 Migrate only the geographically redundant active site. If migration is unsuccessful, select the 
rollback option in ams_migrate script and perform rollback in the active site.
Migration path Proceed to See
Out-of-place migration from an 
earlier 5520 AMS release to the 
5520 AMS, Release 9.7
1. Migrate the 
switchover_hook.sh script, if 
the script was modified.
Section 18.2
2. Enable SSL if a 
customized keystore is 
used.
Section 18.3
3. Enable geographical 
redundancy in case of a 
geographical redundancy 
setup.
Section 18.4
4. Back up the database of 
the earlier