5620 SAM 5650 CPAM SERVICE AWARE MANAGER CONTROL PLANE ASSURANCE MANAGER 14.0 R R9. Installation and Upgrade Guide

Transcription

1 5620 SAM 5650 CPAM SERVICE AWARE MANAGER CONTROL PLANE ASSURANCE MANAGER Installation and Upgrade Guide 3HE AAAG-TQZZA

2 5620 SAM 5650 CPAM Legal notice 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 Nokia. 2 3HE AAAG-TQZZA

3 5620 SAM 5650 CPAM Contents About this document...8 Part I: Getting started Safety information Structure of safety statements Before you begin Overview...13 General deployment information Introduction To obtain the UUID of a station Upgrading from Release 12.0 R4 or earlier Using hostnames in the management network Deployment in a VM Automated client installation, upgrade, and configuration SAM deployment requirements and restrictions SAM deployment requirements SAM deployment restrictions Using samconfig Overview Introduction Usage instructions RHEL OS configuration Overview...41 OS configuration requirements and restrictions General information OS configuration restrictions OS configuration requirements To prepare disk partitions for 5620 SAM installation To reset the disk partition reserved block counts...44 RHEL OS package groups and packages General information Package installation method Server and database packages HE AAAG-TQZZA 3

4 5620 SAM 5650 CPAM 4.10 Client and client delegate server packages RHEL disk configuration Overview Introduction To configure a 5620 SAM disk partition created after the RHEL OS installation Disk partitioning for trial deployments Disk partitioning for live deployments Configuring SSL security Overview Introduction SSL configuration workflow To prepare a 5620 SAM system for SSL To enable SSL on a main server To enable SSL on an auxiliary server To enable SSL and HTTPS on a Cflowd auxiliary server To enable or disable SSL and HTTPS on an analytics server To enable SSL and HTTPS for an OSS client To enable SSL on a RHEL client delegate server To disable SSL on a single-user GUI client To disable SSL on a RHEL client delegate server To disable SSL on a Windows client delegate server Configuring Small Cell management Overview Introduction To enable Small Cell management...94 Part II: 5620 SAM system deployment SAM installation Overview Introduction General information Standalone 5620 SAM system installation Standalone system installation workflow To install a standalone 5620 SAM system HE AAAG-TQZZA

5 5620 SAM 5650 CPAM Redundant 5620 SAM system installation Redundant system installation workflow To install a redundant 5620 SAM system Auxiliary server installation Auxiliary server installation workflow To install a 5620 SAM auxiliary server To add auxiliary servers to a 5620 SAM system Cflowd auxiliary server installation Cflowd auxiliary server installation workflow To install a 5620 SAM Cflowd auxiliary server To configure Cflowd auxiliary server communication Auxiliary database installation Auxiliary database installation workflow To prepare a station for auxiliary database installation To install the auxiliary database software To add an auxiliary database to a 5620 SAM system To add a station to an auxiliary database Analytics server installation To install and enable a 5620 SAM analytics server SAM upgrade Overview Introduction General information To perform the pre-upgrade tasks Standalone 5620 SAM system upgrade Standalone system upgrade workflow To upgrade a standalone 5620 SAM system Redundant 5620 SAM system upgrade Component references Redundant system upgrade workflow To upgrade a redundant 5620 SAM system Auxiliary server upgrade To upgrade a 5620 SAM auxiliary server Cflowd auxiliary server upgrade To upgrade a 5620 SAM Cflowd auxiliary server HE AAAG-TQZZA 5

6 5620 SAM 5650 CPAM Auxiliary database upgrade To upgrade a 5620 SAM auxiliary database Analytics server upgrade To upgrade a 5620 SAM analytics server SAM conversion to redundancy Overview Introduction General information System conversion to redundancy workflow SAM system conversion to redundancy To convert a standalone 5620 SAM system to a redundant system SAM conversion to IPv Overview Introduction General information System conversion to IPv6 workflow To perform the pre-conversion tasks SAM system conversion to IPv To convert a standalone 5620 SAM system to IPv To convert a redundant 5620 SAM system to IPv SAM uninstallation Overview Introduction SAM system uninstallation workflow To uninstall an analytics server To uninstall a Cflowd auxiliary server To uninstall an auxiliary server To uninstall an auxiliary database To uninstall a main server To uninstall a 5620 SAM database Part III: 5620 SAM client deployment Single-user client deployment Overview HE AAAG-TQZZA

7 5620 SAM 5650 CPAM Introduction General information To install the Oracle JRE on a RHEL station Single-user client installation To install a single-user client using a web browser To install a Windows single-user client using a GUI Single-user client upgrade To upgrade a single-user client Single-user client uninstallation To uninstall a single-user client using a web browser To uninstall a Windows single-user client using the client uninstaller Client delegate server deployment Overview Introduction General information Client delegate server installation To install a client delegate server using a web browser To install a RHEL client delegate server using the yum utility To install a Windows client delegate server using a GUI To add a client delegate server to an existing system Client delegate server upgrade To upgrade a client delegate server Client delegate server uninstallation To uninstall a client delegate server using a web browser To uninstall a RHEL client delegate server using the yum utility To uninstall a Windows client delegate server using a GUI HE AAAG-TQZZA 7

8 5620 SAM 5650 CPAM About this document Purpose The 5620 SAM 5650 CPAM Installation and Upgrade Guide describes 5620 SAM / 5650 CPAM installation, upgrade, and platform modification operations such as system conversion to redundancy and system conversion to IPv6. Safety information For your safety, this document contains safety statements. Safety statements are given at points where risks of damage to personnel, equipment, and operation may exist. Failure to follow the directions in a safety statement may result in serious consequences. Document support How to comment Customer documentation and product support URLs: Customer Documentation Welcome Page Technical support Documentation feedback 8 3HE AAAG-TQZZA

9 5620 SAM 5650 CPAM Part I: Getting started Overview Purpose Contents This part describes how to prepare for 5620 SAM system or system component deployment, and includes important requirements, restrictions, and platform configuration procedures. Chapter 1, Safety information 11 Chapter 2, Before you begin 13 Chapter 3, Using samconfig 33 Chapter 4, RHEL OS configuration 41 Chapter 5, RHEL disk configuration 51 Chapter 6, Configuring SSL security 65 Chapter 7, Configuring Small Cell management 93 3HE AAAG-TQZZA 9

10 5620 SAM 5650 CPAM 10 3HE AAAG-TQZZA

11 5620 SAM 5650 CPAM Safety information 1 Safety information 1.1 Structure of safety statements Overview This topic describes the components of safety statements that appear in this document General structure Safety statements include the following structural elements: CAUTION Lifting hazard SAMPLE Lifting this equipment by yourself can result in injury due to the size and weight of the equipment. Always use three people or a lifting device to transport and position this equipment. [ABC123] Item Structure element Purpose 1 Safety alert symbol Indicates the potential for personal injury (optional) 2 Safety symbol Indicates hazard type (optional) 3 Signal word Indicates the severity of the hazard 4 Hazard type Describes the source of the risk of damage or injury 5 Safety message Consequences if protective measures fail 6 Avoidance message Protective measures to take to avoid the hazard 7 Identifier The reference ID of the safety statement (optional) 3HE AAAG-TQZZA 11

12 Structure of safety statements 5620 SAM 5650 CPAM Signal words The signal words identify the hazard severity levels as follows: Signal word DANGER WARNING CAUTION NOTICE Meaning Indicates an extremely hazardous situation which, if not avoided, will result in death or serious injury. Indicates a hazardous situation which, if not avoided, could result in death or serious injury. Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury. Indicates a hazardous situation not related to personal injury. 12 3HE AAAG-TQZZA

13 5620 SAM 5650 CPAM Before you begin 2 Before you begin 2.1 Overview Purpose This chapter describes the requirements and restrictions that apply to 5620 SAM system deployment, and contains other important information that you must read and understand before you attempt to deploy a 5620 SAM component Contents 2.1 Overview 13 General deployment information Introduction To obtain the UUID of a station Upgrading from Release 12.0 R4 or earlier Using hostnames in the management network Deployment in a VM Automated client installation, upgrade, and configuration SAM deployment requirements and restrictions SAM deployment requirements SAM deployment restrictions 29 3HE AAAG-TQZZA 13

14 Introduction 5620 SAM 5650 CPAM General deployment information 2.2 Introduction Description WARNING System Damage A 5620 SAM system upgrade from a release earlier than 12.0 R5 has special requirements; failure to observe the requirements may seriously degrade the 5620 SAM system and cause the upgrade to fail. To ensure the upgrade success, you must prepare for the upgrade as described in 2.4 Upgrading from Release 12.0 R4 or earlier (p. 17). CAUTION Service Disruption A 5620 SAM system upgrade, conversion to redundancy, or conversion to IPv6 requires a thorough understanding of 5620 SAM system administration and platform requirements, and is supported only under the conditions described in this guide, the 5620 SAM Planning Guide, and the 5620 SAM Release Notice. Such an operation must be planned, documented, and tested in advance on a trial system that is representative of the target live network. Contact technical support to assess the requirements of your 5620 SAM deployment, and for information about the upgrade service, which you are strongly recommended to engage for any type of deployment. This chapter describes the general conditions that apply to 5620 SAM deployment. Before you attempt to deploy or configure a 5620 SAM component, you must comply with the conditions in this chapter and ensure that the 5620 SAM platform is configured as described in the other chapters of Part I: Getting started. Part III: 5620 SAM client deployment contains OS-specific information about single-user GUI client and client delegate server deployment. Guide conventions This guide uses the following terminology: station a discrete processing entity, such as a physical or virtual computer peer an equivalent component in the same 5620 SAM system. For example, the peer main server of the primary main server in a redundant deployment is the standby main server. The term peer is irrespective of the primary or standby role. The figures and associated text in the guide display a typical or default parameter value when appropriate. A default value is acceptable in most deployment environments, but must be validated 14 3HE AAAG-TQZZA

15 5620 SAM 5650 CPAM Introduction against specific requirements, for example, firewall constraints. For more information, see the 5620 SAM Planning Guide and the current 5620 SAM Release Notice, or contact technical support. Platform support You can deploy any 5620 SAM component in a virtual machine, or VM. See the 5620 SAM Planning Guide for VM system requirements, and 2.6 Deployment in a VM (p. 21) for VM deployment requirements and restrictions. A 5620 SAM system comprises the following required components: one standalone main server, or two in a redundant deployment one standalone 5620 SAM database, or two in a redundant deployment one or more single-user GUI clients or client delegate servers A 5620 SAM system may also include one or more of the following components: one or more auxiliary servers one auxiliary database one or more Cflowd auxiliary servers one or more analytics servers The following table lists the supported platforms for each 5620 SAM component type. Table SAM platform support by component 5620 SAM component Mac OS X Microsoft Windows RHEL Main server Auxiliary server Cflowd auxiliary server 5620 SAM database Auxiliary database Analytics server Client delegate server Single-user client samadmin user account 5620 SAM system operation and management require a RHEL user account called samadmin in the sam user group. The initial installation of any of the following components on a station creates the group and account: main server auxiliary server analytics server 3HE AAAG-TQZZA 15

16 To obtain the UUID of a station 5620 SAM 5650 CPAM RHEL client delegate server Only the samadmin user can start a server, stop a server, or run a server script. The initial samadmin password is randomly generated, and must be changed by the root user. samadmin owns all 5620 SAM server processes. The samadmin home directory is one of the following, and is owned by samadmin: on a main server /opt/5620sam/server on an auxiliary server /opt/5620sam/auxserver on an analytics server /opt/5620sam/tomcat on a client delegate server configurable The root user owns some files in the home directory for low-level installation and support functions. Server uninstallation does not remove the samadmin user account, user group, or home directory. Root user privileges are required only for 5620 SAM component installation or upgrade, and for low-level support functions. System migration from obsolete platforms To move a 5620 SAM system from an obsolete platform to RHEL, you must use the platform migration procedure in the installation and upgrade guide for the 5620 SAM release that is installed on the obsolete platform. You can then upgrade the 5620 SAM system, directly or indirectly, depending on the release, to the current 5620 SAM release. For example, the migration of a Release 9.0 R SAM system on Solaris SPARC to RHEL must be performed in the following stages: migration from Solaris SPARC to Solaris x86, using the Release 9.0 R5 migration procedure Solaris x86 system upgrade to a target release that supports RHEL deployment Solaris x86 migration to RHEL, using the migration procedure for the target release if required, an intermediate upgrade to a release that can be upgraded to the current 5620 SAM release upgrade of the RHEL system to the current 5620 SAM release 2.3 To obtain the UUID of a station Description A 5620 SAM license is specific to the UUID of a main server station, and must be provided in the license request. The following steps describe how to obtain the UUID of a station that is to host a 5620 SAM main server. Note: If you are using an Integrated Lights Out Management system, ensure that you obtain the UUID of the intended blade and not the UUID of the ILO module. Note: You must perform this procedure on each station that is to host a main server. 16 3HE AAAG-TQZZA

17 5620 SAM 5650 CPAM Upgrading from Release 12.0 R4 or earlier Steps Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command Log in to the main server station as the root user. Open a console window. Enter the following: # lshal grep system.hardware.uuid tr '[A-Z]' '[a-z]' The UUID is displayed; for example: system.hardware.uuid = 'ef5eb0a2-c816-e111-bbda-38aba9872c41' (string) Record the value for use when you request the 5620 SAM license for the main server. END OF STEPS 2.4 Upgrading from Release 12.0 R4 or earlier Description A 5620 SAM system upgrade from a release earlier than 12.0 R5 involves the migration of all NE configuration backups from the 5620 SAM database to the main-server file system. Depending on factors that are not limited to the following, the migration may take considerable time to complete: number of managed NEs average configuration backup size number of retained backups per NE 5620 SAM deployment type standalone or redundant network latency The migration begins automatically during the standalone or primary main server initialization that follows an upgrade. In a redundant deployment, the migration includes the synchronization of the migrated files between the main servers, which may require hours or days to complete. Note: Main server uninstallation does not delete or otherwise affect the NE configuration backup files. 3HE AAAG-TQZZA 17

18 Using hostnames in the management network 5620 SAM 5650 CPAM Disk space requirements The NE backup migration requires the following separate, mounted disk partition: /opt/5620sam/nebackup The partition size is derived using the number of NEs in the network and a backup size value for each NE type. To assist with the partition sizing, use the following formula to calculate the space required per NE type; see Table 2, Configuration backup file sizes by NE type (p. 18) for the backup size values: data capacity = backup size number of NEs backups per NE 2.5 Note: The formula is a guideline for planning purposes only; the actual size may require adjustment. It is recommended that you use the size of the largest backup per NE type in your network as the backup size, and multiply the result by 2.5, as shown in the formula. This calculation accounts for network and NE backup growth, and accommodates the storage of compressed archive files. Table 2 Configuration backup file sizes by NE type NE type Backup size 1830 PSS 400 kbytes 1830 VWM OSU 128 kbytes 7210 SAS 200 kbytes 7450 ESS, 7710 SR, 7750 MG, 7750 SR, 7950 XRS 1.5 Mbytes 7705 SAR 250 kbytes 9500 MPR 1.5 Mbytes enodeb MIB backup enodeb Full backup OmniSwitch 250 kbytes 1 Mbyte 30 kbytes 2.5 Using hostnames in the management network Description The topology of a 5620 SAM management network may be sufficiently complex to benefit from or require the use of hostnames, rather than fixed IP addresses, for communication between 5620 SAM components. Hostname resolution is of even greater benefit when NAT is used between 5620 SAM clients and a main server that communicates over multiple networks. Note: When the 5620 SAM clients and auxiliary servers use different main server interfaces to communicate with a main server, the clients must use a hostname to reach the main server. 18 3HE AAAG-TQZZA

19 5620 SAM 5650 CPAM Using hostnames in the management network This section provides a configuration example for hostname resolution in a moderately complex 5620 SAM management network that does not include a NAT configuration. Note: Only local hostname resolution is supported. The use of a DNS server for 5620 SAM hostname resolution is not supported. To enable hostname resolution in a 5620 SAM management network, you must do the following: Configure the local /etc/hosts file on each component to ensure that each hostname translates to the correct IP address. During component deployment, specify hostnames instead of IP addresses. Note: Hostnames are case-sensitive. Hostname usage requirements and restrictions When two server components use hostnames to communicate, the /etc/hosts file must contain the following: on a main server: an entry that maps the main server hostname to the IP address of the main server interface that is used for client communication an entry for each auxiliary server that maps the auxiliary server hostname to the IP address of the auxiliary server interface that is used for main server communication an entry for each database that maps the database hostname to the IP address of the database interface that is used for main server to database communication on an auxiliary server: an entry for each main server that maps the main server hostname to the IP address of the main server interface that is used for auxiliary server communication an entry for each auxiliary server that maps the auxiliary server hostname to the IP address of the auxiliary server interface that is used for main server communication an entry for each database that maps the database hostname to the IP address of the database interface that is used for database communication Note: Each main server must map an auxiliary server hostname to the same IP address. Note: A component hostname that you specify in an /etc/hosts file must be the full hostname returned by the hostname command, and not the short form. Note: Depending on the management network topology, the hosts files of various components may map the same main server hostname to different IP addresses in order to reach the correct main server interface. Management network configuration example The following example provides guidance about configuring local hostname resolution for 5620 SAM components in a relatively complex management network. In the example, each main server communicates with multiple networks using separate interfaces, as shown in Figure 1, Management network topology (p. 20). 3HE AAAG-TQZZA 19

20 Using hostnames in the management network 5620 SAM 5650 CPAM Figure 1 Management network topology The client IP addresses are in the n network, and the internal management IP addresses are in the n network. The component hostnames in the example are the following: main servers main_a and main_b 5620 SAM databases db_a and db_b auxiliary servers aux_a and aux_b The same configuration methodology must be applied to all components in the internal management network; for simplicity, the following configuration examples show only the components on one side of the 5620 SAM complex. The /etc/hosts file on station main_a requires the following entries: 20 3HE AAAG-TQZZA

21 5620 SAM 5650 CPAM Deployment in a VM main_a main_b aux_a aux_b db_a db_b localhost The /etc/hosts file on station aux_a requires the following entries: aux_a aux_b main_a main_b db_a db_b localhost The /etc/hosts file on station db_a requires the following entries: db_a db_b localhost 2.6 Deployment in a VM Description The requirements and restrictions below apply to 5620 SAM component deployment in a virtual machine, or VM Deployment is supported in the following virtual environments: KVM Openstack VMware Note: The requirements and restrictions in 5620 SAM deployment requirements and restrictions (p. 25) also apply to VM deployments. Note: Before you deploy a 5620 SAM component in a VMware VM, you must install the latest VMware Tools software. See the 5620 SAM Planning Guide for the hardware virtualization requirements, and for the specific configuration requirements of a supported environment. 3HE AAAG-TQZZA 21

22 Automated client installation, upgrade, and configuration 5620 SAM 5650 CPAM SAM server and database virtualization The following conditions apply to main server, auxiliary server, client delegate server, or database deployments in VMs. The guest OS must be a 5620 SAM-supported version of RHEL 6 Server x A RHEL deployment on VMware requires VMXNET 3 NIC adapters; see the VMware documentation for information Client virtualization The following conditions apply to 5620 SAM single-user GUI client deployment in a VM. You can deploy a VM client in a live network environment only if the client resources are dedicated to the guest OS, and not shared or oversubscribed. The guest OS must be a supported OS version; see the 5620 SAM Planning Guide. The supported connection application for a VMware ESXi Windows platform is Windows Remote Desktop. Additional EMS requirements and restrictions The following conditions apply to a 5620 SAM single-user GUI client or client delegate server in a VM that requires the installation of an additional element manager on the same platform, or is to use an additional NE management interface. You can use two or more NICs to isolate network traffic between the client VM and the managed NEs. Such a configuration may be required when an additional element manager, for example, NEtO, must share the client resources, or when web-based NE management is to be performed from the client station. Additional RAM, disk space, and CPU resources are required to accommodate an element manager that shares a client platform; see the 5620 SAM Planning Guide. 2.7 Automated client installation, upgrade, and configuration Description The following 5620 SAM single-user GUI client and client delegate server software installation methods are available: using a client installation utility, on a supported OS other than RHEL using a web browser that connects to a 5620 SAM main server Each method sets up a basic client environment that includes the 5620 SAM auto-client update utility, which downloads the client software from a 5620 SAM main server and installs it. The 5620 SAM main server must be installed and initialized before you can use a web browser to install the auto-client update utility and client software. You can use the file-based client installer to 22 3HE AAAG-TQZZA

23 5620 SAM 5650 CPAM Automated client installation, upgrade, and configuration install the auto-client update utility, regardless of the main server state, but the main server must be fully initialized before the auto-client update utility can install the client software. See the following chapters for client installation and upgrade information: Chapter 13, Single-user client deployment single-user client deployment Chapter 14, Client delegate server deployment client delegate server deployment The auto-client update utility can also be used for the central management and automatic distribution of client software upgrades and configuration changes. During startup, the client software checks for available updates on a 5620 SAM main server. If a configuration change is available, the client automatically applies it. If a client software upgrade is available, the client applies the upgrade in response to a user prompt Client software upgrades After a 5620 SAM main server is upgraded, a GUI client that connects to the main server automatically detects the release mismatch and attempts an upgrade to the main server release level. During a software upgrade, a 5620 SAM client downloads and installs only the files required for the upgrade. The upgrade process removes previously downloaded local 5620 SAM files that are not required by the updated client software Client configuration changes When the single-user GUI clients or client delegate servers that connect to a main server require a configuration change, an administrator updates the global client configuration stored on a main server. Each client software instance detects the update at the start of the next client session and applies the required configuration changes. See System component configuration procedures in the 5620 SAM System Administrator Guide for information about globally updating client configurations. By default, the client configuration after an automatic update matches the main server configuration, but this behavior is configurable using client startup options. To retain a customized configuration on a client, you can specify that the client does not apply any configuration changes from the main server. If a client configuration change is mandatory and affects the customized configuration, you must allow the update and then manually reapply the custom configuration entries. See Procedures for opening and closing the GUI in the 5620 SAM User Guide for a description of each 5620 SAM client startup option Considerations and restrictions Consider the following before you attempt to use the client auto-update function. When a client detects an error during an auto-update attempt, for example, when the client is unable to connect to the main server, it displays a message about the error. An auto-client update proceeds only when there is sufficient disk space on the client station. Otherwise, the client displays a message and exits. 3HE AAAG-TQZZA 23

24 Automated client installation, upgrade, and configuration 5620 SAM 5650 CPAM When a GUI client tries to connect to a main server that is at an earlier 5620 SAM release than the download server, the client displays a message to this effect, restarts, and tries to connect to the other main server. A client backs up the existing configuration files before it performs a configuration change. 24 3HE AAAG-TQZZA

25 5620 SAM 5650 CPAM 5620 SAM deployment requirements 5620 SAM deployment requirements and restrictions SAM deployment requirements Network requirements CAUTION Service Disruption The use of hostname resolution for GUI and OSS client communication with a 5620 SAM main server in a NAT environment is strongly recommended. When IP addresses are used in a NAT environment, the following conditions apply: All client communication with the main server must use the public IP address of the main server. The NAT firewall must be configured to allow the main server to communicate with itself using the public IP address. The 5620 SAM network requirements apply to the following: management network the network over which the 5620 SAM components communicate with each other managed network and external systems the managed NEs, and systems that are integrated with the 5620 SAM Management network The following requirements apply to the 5620 SAM management network. During a main server installation or upgrade, you must use hostnames to identify the main server interfaces under the following conditions: when the OSS and GUI clients communicate with a main server using multiple IP addresses for the main server when the OSS and GUI clients use different addresses to communicate with a main server through one interface on the main server An auxiliary server must be accessible to each main server and database in a redundant 5620 SAM deployment. Optimally, all components in a deployment are in the same LAN and have high-quality network interconnection. Each station in an auxiliary database must be on the same side of the management LAN, and not geographically dispersed. When two components use hostnames to communicate, the /etc/hosts file on each component station must contain the following: an entry that maps the hostname assigned to the interface on the other component to the IP address used to reach the other component an entry that maps the hostname of the other component station to each IP address used to reach the other component Using NAT adds an extra level of complexity to a 5620 SAM network. The /etc/hosts file on each 3HE AAAG-TQZZA 25

26 5620 SAM deployment requirements 5620 SAM 5650 CPAM component station must contain the correct public and private address entries for reaching other components at the following times: during normal operation after a 5620 SAM component or network component failure Specifying a TCP or UDP port other than the default during an installation or upgrade can affect a firewall configuration. Ensure that you record any changes to default port numbers and make the ports available through the firewalls. When you use hostname to identify a 5620 SAM component, you must use local hostname resolution; the use of DNS is not supported. Note: A component hostname that you specify in an /etc/hosts file must be the full hostname returned by the hostname command, and not the short form. Note: Hostnames are case-sensitive. Managed network and external systems CAUTION Service Disruption If a 5620 SAM system that is to be upgraded manages a device as a GNE, and the new 5620 SAM release supports native management of the device, you must unmanage the device and delete it from the 5620 SAM database before the upgrade. After the upgrade, you can use the 5620 SAM to discover and manage the device natively, rather than as a GNE. CAUTION Management Disruption 5620 SAM enodeb PM statistics collection fails when the enodeb and 5620 SAM real-time clocks are not synchronized. The 5620 SAM and all enodeb devices require a common time-synchronization server that uses a protocol such as NTP. CAUTION Management Disruption A 5620 SAM system that manages 9500 MPR devices requires special configuration for an upgrade from a release earlier than 14.0 R7; otherwise, the upgraded 5620 SAM cannot manage the devices. The procedures in Chapter 9, 5620 SAM upgrade refer to the required pre-upgrade and postupgrade procedures in 9500 MPR migration to revised service model of the 9500 MPR User Guide. 26 3HE AAAG-TQZZA

27 5620 SAM 5650 CPAM 5620 SAM deployment requirements The following requirements apply to the network of 5620 SAM- managed devices and to the external systems with which the 5620 SAM is integrated. Before you upgrade a 5620 SAM system, you must confirm that the new 5620 SAM software release supports the release of each 5620 SAM-managed device. If this is not true, you must perform one of the following before you attempt the upgrade, or service disruption may occur. Upgrade the device to a release that the new 5620 SAM release supports. Use a 5620 SAM client to unmanage the device, remove the device from the managed network, and remove the discovery rule element for the device. Before you upgrade a 5620 SAM system, you must ensure that the new 5620 SAM software is compatible with the software release of each integrated external system. Contact technical support for information about 5620 SAM and external system compatibility. A 5620 SAM system that manages enodeb devices has special disk partitioning requirements. See Chapter 5, RHEL disk configuration for information. A 5620 SAM system upgrade does not preserve 9500 MPR device software images. If you want to retain the images, you must export the images to a remote file system before the upgrade, and import the images to the 5620 SAM after the upgrade. Before the 5620 SAM can manage an enodeb, functions such as PM statistics transfers and network snapshots require configuration; see the 5620 SAM LTE RAN User Guide for specific enodeb management information. Before you can use the 5620 SAM to manage Small Cell NEs, you must perform specific configuration steps on each main and auxiliary server; see Chapter 7, Configuring Small Cell management for information. Note: Enabling Small Cell management on an existing 5620 SAM system involves a system restart, which can be service-affecting. Alternatively, you can configure the function during a system installation or upgrade, before the initial main server startup. If you choose to do this, you must ensure that the associated maintenance period includes time for the Small Cell configuration Platform requirements The following are the 5620 SAM platform requirements. The 5620 SAM platform must meet the minimum requirements described in the 5620 SAM Planning Guide for the current release. The OS release and patch level of all main server, 5620 SAM database, and optional component stations in a 5620 SAM system must be identical SAM deployment in a live network requires a station that has at least two hard disks. A one-disk layout is supported only for lab trials or demonstration purposes. In a redundant 5620 SAM deployment, the main server time zones must match. The hostname of a 5620 SAM component must meet the following criteria. It contains only ASCII alphanumeric and hyphen characters. It does not begin or end with a hyphen. If the hostname is an FQDN, period characters delimit the FQDN components. The FQDN of the hostname does not exceed 63 characters. 3HE AAAG-TQZZA 27

28 5620 SAM deployment requirements 5620 SAM 5650 CPAM The 5620 SAM platform must be dedicated to the 5620 SAM only SAM operation may be adversely affected by the activity of other software on the same platform. The sharing of the 5620 SAM platform is not supported. Before you install or upgrade a redundant 5620 SAM system, you must enable SSH on each main server, auxiliary server, and database station in the system. If the 5620 SAM is to collect statistics on a large scale, as defined in the 5620 SAM Planning Guide, you must use a disk array with the 5620 SAM database to increase performance. See Chapter 5, RHEL disk configuration for information. The 5620 SAM OSS and GUI client real-time clocks must always be synchronized with the main server real-time clock. The use of NTP or an equivalent time protocol is strongly recommended Security requirements Note: The use of sudo to gain root user privileges is supported for 5620 SAM installation, and for any other operation in this guide that requires root user privileges. The Oracle management user requires full read and write permissions on the 5620 SAM database installation directory, /opt/5620sam/samdb, and any specifically created partitions, for example, /opt/5620sam/dbbackup. The user that installs a 5620 SAM single-user GUI nt requires local user privileges only, but must have full access permissions on the client installation directory. The user that opens the client installer must have sufficient file permissions to create the installation directory, or the installation fails Software requirements CAUTION Service Disruption It is strongly recommended that you stage a 5620 SAM upgrade in advance is to ensure upgrade success in a live network. As part of the staging process for an upgrade from Release 13.0 or earlier, you must ensure that the License Point capacity of the new license key is sufficient to accommodate the currently managed equipment in the live network. A 5620 SAM system deployment requires a license file in compressed format with a.zip extension. A license file has the following characteristics. The UUID of the host station is required to generate the license. 2.3 To obtain the UUID of a station (p. 16) describes how to obtain a station UUID. The file can accommodate two system IDs, which enables the use of the same file on redundant main servers, and is recommended. Renaming the compressed file has no effect on the validity of the contained license file, but renaming the contained XML license file renders it invalid. The 5620 SAM server installation utility copies the license file content to a backup location; a change to the license file content or location after an installation or upgrade does not affect the main server operation. 28 3HE AAAG-TQZZA

29 5620 SAM 5650 CPAM 5620 SAM deployment restrictions You must ensure that you have sufficient time to complete a 5620 SAM database upgrade. The time required for a database upgrade depends on the platform resources, database complexity, and tablespace configuration. See the 5620 SAM Planning Guide for database upgrade time estimates. To enable or disable SSL on a single-user GUI client or delegate client, you must uninstall the single-user client or client delegate server software, and then select the appropriate SSL option during the client or client delegate server re-installation. A client cannot connect to a main server that has a different SSL configuration; consequently, the main server cannot update the client SSL configuration SAM deployment restrictions Network restrictions CAUTION Deployment Limitation The use of NAT between 5620 SAM server and database components is not supported. The 5620 SAM supports NAT only between the following: main server and single-user client or client delegate server main or auxiliary server and OSS client main or auxiliary server and managed network Note: If you use SSH X forwarding to perform a procedure in this guide, the su - oracle command fails. In such a scenario, you must log in directly as the Oracle management user to perform the required actions. The following restrictions apply to the network environment in which a 5620 SAM system or componeent is deployed. DNS or NIS name resolution is not supported between 5620 SAM components, and a preexisting name service must not conflict with 5620 SAM address resolution. The restriction also applies to OSS client communication with the 5620 SAM. You cannot use localhost or an alias IP address to identify a component. A 5620 SAM main server listens for GUI and OSS client communication on only one interface unless you specify a hostname for the main server during an installation or upgrade. You cannot use a hostname to identify a database station; 5620 SAM components can use only an IP address to reach a database. All IP communication from a 5620 SAM auxiliary server to a 5620 SAM main server must originate from one IP address, which is the auxiliary server address specified during the main server configuration. A main server rejects communication from an auxiliary server if the auxiliary server uses a source address other than the configured address. During a single-user client installation, you can specify a hostname instead of an IP address to identify a main server. A client upgrade occurs automatically through a connection to a main server named in the client configuration. 3HE AAAG-TQZZA 29

30 5620 SAM deployment restrictions 5620 SAM 5650 CPAM IPv4 and IPv6 All 5620 SAM components must communicate with all other 5620 SAM components using exclusively IPv4 or IPv6. Before you can specify an IPv6 address for a 5620 SAM component, the IPv6 interface must be plumbed and operational. See the OS documentation for information about enabling and configuring an IPv6 interface. A main server can perform network management using both IPv4 and IPv6. Before you use a procedure in Chapter 11, 5620 SAM conversion to IPv6 to convert a 5620 SAM system from IPv4 to IPv6, the system must be at the software release described in this guide Platform restrictions CAUTION Misconfiguration Risk If the RHEL iptables / ip6tables firewall is enabled on a station during a 5620 SAM component installation or upgrade, the operation fails. Before you attempt to deploy a 5620 SAM system, you must disable the RHEL iptables / ip6tables firewall on each station in the system. Also, if you plan to implement a RHEL iptables / ip6tables firewall as part of a 5620 SAM system upgrade, the iptables / ip6tables firewall on each station must be disabled before the upgrade. A 5620 SAM single-user client or client delegate server cannot be installed on the same station as a 5620 SAM server or database. A 5620 SAM single-user client and client delegate server cannot be installed on the same station. An optional system component requires a dedicated station. The sharing of a station by optional components is not supported; attempts to deploy multiple components on one station fail. If you plan to convert a standalone 5620 SAM system to a redundant system and plan to upgrade the system, you must perform the upgrade before the conversion. A 5620 SAM system conversion from IPv4 to IPv6 is not supported during an upgrade or conversion to redundancy Security restrictions The user that starts a 5620 SAM client must be the user that installs the client software, or another user that has read, write, and execute privileges on the client files and directories. A 5620 SAM domain name defines the network-management domain to which a 5620 SAM component belongs, and must be unique to a network. A 5620 SAM component can interact only with other 5620 SAM components in the same 5620 SAM domain. During 5620 SAM system installation, you must specify the same domain name for each component in the system. 30 3HE AAAG-TQZZA

31 5620 SAM 5650 CPAM 5620 SAM deployment restrictions Software restrictions CAUTION Service Disruption A 5620 SAM upgrade does not preserve all non-default settings in configuration files such as nmsserver.xml. If a 5620 SAM configuration file contains non-default settings that you want to retain after an upgrade, contact technical support for assistance before the upgrade. CAUTION Data Loss At the beginning of a 5620 SAM server upgrade, the 5620 SAM installation utility backs up specific configuration and log files to a time-stamped directory under the installation directory, and then deletes specific directories below the installation directory. If you create or modify a file under the main server installation directory, you risk losing the file during a 5620 SAM upgrade unless you first back up the file to a location that is unaffected by the upgrade activity. Note: A 5620 SAM server upgrade applies a default set of file permissions to each directory below the main server installation directory. If you change the file permissions of a directory below the main server installation directory and want the permissions to be in effect after an upgrade, you must re-apply the permissions after the upgrade. Note: After an analytics server upgrade: Scheduled report creation continues, but uses the new report versions, which may differ from the former versions. Saved reports remain available, but lack any new features of the upgraded report versions; it is recommended that you recreate and save the reports. If a report changes significantly between releases, the report may no longer function. See the 5620 SAM Release Notice for limitations regarding specific reports. The 5620 SAM Release Notice contains important release-specific information. Ensure that you read the Release Notice for the current release before you attempt a 5620 SAM installation or upgrade. The 5620 SAM supports the upgrade of a 5620 SAM component that is no more than two major releases older than the current release. For example, you can upgrade a 5620 SAM Release 12.0 system to Release 14.0, but you cannot upgrade a Release 11.0 system directly to Release 14.0; you must first perform an intermediate upgrade to at least Release After an upgrade to an intermediate release, for example, an upgrade from Release 11.0 to Release 12.0 before a final upgrade to Release 14.0, you must allow each 5620 SAM main server to initialize fully before the final upgrade, or the final upgrade fails. A redundant 5620 SAM system upgrade requires a network-management outage and must be performed only during a scheduled maintenance period of sufficient duration for the upgrade. 3HE AAAG-TQZZA 31

32 5620 SAM deployment restrictions 5620 SAM 5650 CPAM You cannot upgrade the 5620 SAM to a release that is chronologically older than the currently installed release. For example, you cannot upgrade from Release 10.0 R8 to 11.0 R1, because Release 11.0 R1 predates Release 10.0 R8. You cannot share an existing Oracle installation with the 5620 SAM, and no other application can use the 5620 SAM Oracle software. You can specify the installation directory for a single-user client or client delegate server, but not for any other type of component. You can deploy a main server without specifying a license file. However, if you do not specify a license file, you cannot start the main server until you import a license. See Software and license configuration procedures in the 5620 SAM System Administrator Guide for information about importing licenses. 32 3HE AAAG-TQZZA

33 5620 SAM 5650 CPAM Using samconfig 3 Using samconfig 3.1 Overview Purpose This chapter describes the 5620 SAM deployment utility called samconfig Contents 3.1 Overview Introduction Usage instructions Introduction General information To deploy or configure most 5620 SAM system components, an operator uses the CLI-based samconfig utility. After you install the samconfig RPM package on a station, you can use the samconfig utility to: Immediately configure and deploy a component on the station. Create component configuration files for subsequent use in other deployments. You can configure and deploy the following components using samconfig: main server 5620 SAM database auxiliary server Cflowd auxiliary server client delegate server Functional description The samconfig utility has a hierarchical menu structure similar to the menu structure of some NEs. The top level is called the root level. The configuration level, which is directly below the root level, contains the objects that you can configure. An object is a parameter, or a functional area that contains parameters. The following commands are available at any menu level: show show the non-default configuration values show-detail show all configuration values 3HE AAAG-TQZZA 33

34 Introduction 5620 SAM 5650 CPAM?, h, or help display a help menu help-detail display a detailed help menu back move to the parent level exit move to the root level, or, from the root level, exit samconfig Root level The root level is the level at which samconfig opens. The root-level prompt includes the module type, as shown below for a main server: <main> The following commands are exclusive to the root level: configure enter the configuration level save filename save the configuration in a file; the default is /opt/5620sam/samconfig/nms/ config/module_config.yyyy-mm-dd_hh-mm-ss.xml apply apply the configuration Configuration level To configure a 5620 SAM component, you must enter the configuration level and specify objects, parameters, and values, as required. To move to the configuration level from the root level, you enter the following: <module> configure The configuration-level prompt is the following: <module configure> The configuration-level help menu lists the configurable objects, which are specific to the module type. The following is a help-menu sample that lists the configurable objects for a main server: ip communications domain [no] license client database mediation [no] aux [no] redundancy [no] ssl - Private IP Address for local server SAM server complex domain name - Absolute path to the 5620 SAM license file + Client Configuration + Database Configuration + Mediation Configuration + Auxiliary Server Configuration + Redundancy Configuration + Security Configuration 34 3HE AAAG-TQZZA

35 5620 SAM 5650 CPAM Introduction [no] oss [no] analytics auxdb [no] aa-stats [no] registry + OSS Configuration + SAM Analytics Server Configuration + Auxiliary Database Configuration + AA Stats Configuration + Registry Configuration Note: The [no] option beside an object means that you can delete or disable the object configuration using the following syntax: no object The following table defines the special characters that may be displayed beside an object or command Table 3 Special characters in samconfig menus Character Meaning + The object has child objects or parameters. - The object does not have child objects or parameters. * The object has one or more mandatory parameters that are not configured. Note: You can save, but not apply a configuration that includes an unconfigured mandatory parameter. Contextual help At the configuration level, or in an object context below the configuration level, you can enter the following to obtain the help information for a specific parameter: parameter? The following example shows the help command and output for the ip parameter of a 5620 SAM database: <db configure> ip? NAME: ip DESCRIPTION: Database IP address accessible to servers Default Value [nnn.nnn.nnn.nnn] Current Value [nnn.nnn.nnn.nnn] USAGE: ip <IP> FORMAT: where IP is a valid Local IPv4 (xxx.xxx.xxx.xxx) or IPv6 formatted address. 3HE AAAG-TQZZA 35

36 Usage instructions 5620 SAM 5650 CPAM VALID VALUES: MANDATORY: nnn.nnn.nnn.nnn true Advance creation of configuration files You can use samconfig to create multiple configuration files for subsequent component deployments on other stations. For example, if you plan to deploy a standalone 5620 SAM system that includes two auxiliary servers, you create the following files using the parameter values required for each component: one main server configuration file one 5620 SAM database configuration file two auxiliary server configuration files You can then copy the files to stations in a staging environment for trial purposes, and then subsequently use the files on the stations in a live system when testing is complete. Note: You can create a configuration file for a component only when the RPM packages that the component requires are installed on the component. For example, an auxiliary server requires the samjre, samconfig, and samauxserver packages. Note: After you specify a license, keystore, or truststore file using samconfig, the associated parameter may display the following: Use Current object File In such a case, before you can apply the file on a different station, you must use samconfig on the new station to specify the license, keystore, or truststore file. 3.3 Usage instructions Opening samconfig Note: Using samconfig requires root user privileges. To invoke samconfig, you enter one of the following: To create and optionally deploy a new component configuration: samconfig -m module To open a saved configuration file: samconfig -f file To deploy a saved configuration: samconfig -f file -apply To display the samconfig version information: samconfig -version 36 3HE AAAG-TQZZA

37 5620 SAM 5650 CPAM Usage instructions where module is one of the following: main main server db 5620 SAM database aux auxiliary server cflowdaux auxiliary server clientdelegate client delegate server file is a configuration file created using samconfig General usage The following steps describe general samconfig usage; see the samconfig man page for comprehensive usage information. Note: samconfig has an auto-complete function; pressing the TAB key in the samconfig CLI has the following effects: at the prompt lists the available options after one or more characters completes a matching option name, or lists the possible matches for further refinement Note: samconfig has a history function; you can cycle through previous commands using the up and down cursor keys, and can search for characters in a previous command by pressing the Page Up key or by entering characters and pressing the Up cursor key.. General usage steps: 1. Enter the following in a console window to open samconfig. # samconfig -m module The root prompt is displayed: <module> 2. To move to the configuration level, enter the following: <module> configure The configuration prompt is displayed: <module configure> 3. Perform one of the following. a. To configure multiple parameters of an object, enter the following: <module configure> object The object configuration prompt is displayed: <module configure object> You can then configure one or more parameters by entering the following: <module configure object> parameter value b. To configure only one parameter of an object, enter the following: 3HE AAAG-TQZZA 37

38 Usage instructions 5620 SAM 5650 CPAM <module configure> object parameter value samconfig moves to the object configuration level after the parameter is set, as shown below: <module configure object> c. To enable a Boolean object, for example, the aa-stats object on a main server, enter the following: <module configure> object d. To disable a Boolean object, for example, the aa-stats object on a main server, enter the following: <module configure> no object 4. To return to the parent level, enter the following: back 5. Repeat steps 3 and 4 to configure additional objects and parameters, as required. 6. Enter the following to exit the configuration level and return to the root level: exit 7. Perform one or more of the following, as required. a. To review only the non-default configuration values, enter the following: <module> show The non-default values are listed. b. To review the entire configuration, enter the following: <module> show-detail The entire configuration is displayed. c. To save the configuration using the default filename, such as when you are configuring a component on the local station, enter the following: <module> save The utility backs up the previous configuration file, if any, and displays the following: Backup of existing file saved as: backup_file Configuration saved as: /opt/5620sam/samconfig/nms/config/module_ config.xml d. To save the configuration to a different file, for example, if you are creating a configuration for component deployment on a separate station, enter the following: <module> save filename Note: If filename does not include a relative or absolute path, the file is saved in the /opt/5620sam/ samconfig/nms/config directory: The following is displayed: Configuration saved as: filename e. To immediately apply the component configuration, enter the following; you can apply a configuration only when the associated component is not running: <module> apply f. To exit samconfig, enter the following: <module> exit 38 3HE AAAG-TQZZA

39 5620 SAM 5650 CPAM Usage instructions samconfig prompts you to save any unsaved configuration changes, as shown below: Finished processing command line inputs... Save changes before exiting? (y/n) If you enter y, the following is displayed: Backup of existing file saved as: backup_file Configuration saved as: /opt/5620sam/samconfig/nms/config/module_ config.xml Usage in procedure steps Some configuration steps in procedures that require samconfig include a table that lists and describes the available parameters in an object context. The table provides additional information and default values, if available. The table layout facilitates the copying and pasting of parameter names into a CLI, and the last term in a table title is the name of the object that contains the parameters; for example, the title of the table in the example below shows that the operator is in the mediation object context. Note: If the parameters are at the top configuration level, the table title describes the parameters as general parameters. Configuration step example The following example uses a procedure step from the standalone main server installation procedure. An operator needs to enable NAT and specify an IPv4 address other than the default for network management; the remaining parameter defaults are deemed acceptable. In an earlier step, the operator enters configure at the samconfig prompt to enter the configuration level. To set the mediation parameters, the operator enters mediation to move to the mediation object, and then the following configuration commands: 1. nat enables NAT; to disable NAT, the no nat form is required 2. snmp-ipv sets the snmp-ipv4 parameter to a non-default value 3. back returns the operator to the parent menu, from which the operator can configure other objects Note: To configure only one parameter of an object, you can combine the object, parameter, and value in one command; for example, configure mediation snmp-ipv The following is the step from the installation procedure 27. Configure the mediation parameters in the following table, and then enter back. Table 4 Standalone main server parameters mediation Parameter nat Description Whether NAT is used between the main server and the managed NEs Default: false 3HE AAAG-TQZZA 39

40 Usage instructions 5620 SAM 5650 CPAM Table 4 Standalone main server parameters mediation (continued) Parameter snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description The IPv4 address that the managed NEs must use to reach the main server Default: IPv4 address of primary network interface The IPv6 address that the managed NEs must use to reach the main server Default: IPv6 address of primary network interface The TCP port on the main server station that the managed NEs must use to reach the main server Default: 162 The SNMP trap log ID associated with the main server Default: HE AAAG-TQZZA

41 5620 SAM 5650 CPAM RHEL OS configuration 4 RHEL OS configuration 4.1 Overview Purpose This chapter describes the RHEL OS configuration requirements and restrictions for 5620 SAM system deployment, and lists the required and optional RHEL packages and package groups for each component type Contents 4.1 Overview 41 OS configuration requirements and restrictions General information OS configuration restrictions OS configuration requirements To prepare disk partitions for 5620 SAM installation To reset the disk partition reserved block counts 44 RHEL OS package groups and packages General information Package installation method Server and database packages Client and client delegate server packages 49 3HE AAAG-TQZZA 41

42 General information 5620 SAM 5650 CPAM OS configuration requirements and restrictions 4.2 General information Description You must comply with the conditions in Chapter 2, Before you begin and the specific requirements in this chapter before you attempt to perform a procedure in this guide on a RHEL station. Note: See the current 5620 SAM Release Notice for the required RHEL version and patch information. Note: It is strongly recommended that you install any OS, driver, or firmware update that your hardware vendor advises for RHEL. 4.3 OS configuration restrictions Description The following are the RHEL OS configuration restrictions for 5620 SAM system components. The 5620 SAM supports the use of RHEL IP bonding only when IP bonding is deployed in an active/backup configuration; see the RHEL documentation for IP bonding information. Note: IP bonding is not supported for a Cflowd auxiliary server. The RHEL SELinux function is not supported; you must disable the function on a station after the OS installation and before you attempt to install a 5620 SAM component. The RHEL TFTP server conflicts with the 5620 SAM TFTP server, and must be disabled on a main or auxiliary server station. Note: It is recommended that you create the 5620 SAM disk partitions during the RHEL OS installation. Each partition created after the OS installation requires additional configuration, as described in 5.3 To configure a 5620 SAM disk partition created after the RHEL OS installation (p. 52). 4.4 OS configuration requirements Description The following are the RHEL OS configuration requirements for 5620 SAM system components. Note: Before you deploy a 5620 SAM component on RHEL in a VM, you must also install the latest VMware Tools software; see the VMware documentation for information. The system locale must be POSIX. The file system type must be ext4. You must choose English (English) as the RHEL OS installation language. 42 3HE AAAG-TQZZA

43 5620 SAM 5650 CPAM To prepare disk partitions for 5620 SAM installation You must select the Create custom layout disk configuration option, and must then create the file system partitions as specified in Chapter 5, RHEL disk configuration. You must specify the required RHEL packages and package groups listed in RHEL OS package groups and packages (p. 46) during the RHEL OS installation. After the OS installation, you must do the following. Configure each ext4 disk partition with the required options for 5620 SAM software deployment; see 4.5 To prepare disk partitions for 5620 SAM installation (p. 43). Reset the reserved block count on each 5620 SAM disk partition; see 4.6 To reset the disk partition reserved block counts (p. 44). The /etc/hosts entry that maps a main or auxiliary server hostname to an external IP address must be listed above the loopback address entry, and optimally is the first line of the file. If OSS clients are to use the registerlogtofile method, you must enable the RHEL FTP, SCP, or SFTP services, as required, and configure each firewall to allow the associated file-transfer traffic between the clients and main servers. Firewall requirements CAUTION Misconfiguration Risk If the RHEL iptables / ip6tables firewall is enabled on a station during a 5620 SAM component installation or upgrade, the operation fails. Before you attempt to deploy a 5620 SAM system, you must disable the RHEL iptables / ip6tables firewall on each station in the system. Also, if you plan to implement a RHEL iptables / ip6tables firewall as part of a 5620 SAM system upgrade, the iptables / ip6tables firewall on each station must be disabled before the upgrade. The following firewall types are supported in a 5620 SAM deployment: external firewall native RHEL firewall implemented using iptables / ip6tables Note: A RHEL kernel firewall must be configured according to the rules in the 5620 SAM Planning Guide, which describes the use of 5620 SAM templates to create RHEL iptables / ip6tables rules. 4.5 To prepare disk partitions for 5620 SAM installation Description The following steps describe how to configure each ext4 disk partition on a station after the RHEL OS installation and before you attempt to install a 5620 SAM component on the station. 3HE AAAG-TQZZA 43

44 To reset the disk partition reserved block counts 5620 SAM 5650 CPAM Steps Log in to the station as the root user. Open a console window. Open the /etc/fstab file using a plain-text editor such as vi. You must modify the entry for each partition that has an ext4 file system. The following is an example ext4 partition entry, which may optionally include the file system UUID: /dev/device mount_point ext4 defaults 1 2 where device is the name of the device associated with the partition mount_point is the partition mount point, for example, /opt/5620sam Perform the following steps for each ext4 partition entry. Note: Only the partition options shown are supported. Note: An entry may include the file system UUID, which is optional. Excluding the UUID does not affect 5620 SAM operation. 1. If the defaults option is shown, remove the option. 2. For a partition in a physical hardware deployment, insert barrier=0,noatime, as shown in the following: /dev/device mount_point ext4 barrier=0,noatime For a partition in a VM deployment, insert noatime, as shown in the following: /dev/device mount_point ext4 noatime Close the console window. END OF STEPS 4.6 To reset the disk partition reserved block counts Description The following steps describe how to ensure that the number of reserved blocks for the root user on each 5620 SAM disk partition is zero. 44 3HE AAAG-TQZZA

45 5620 SAM 5650 CPAM To reset the disk partition reserved block counts Steps Note: You must perform this procedure on each station that hosts one of the following 5620 SAM system components: main server auxiliary server 5620 SAM database Log in to the station as the root user. Open a console window. Enter the following: # mount grep 5620sam The 5620 SAM disk partitions are listed; for example: /dev/sda2 on /opt/5620sam type ext4 (rw,noatime,barrier=0) /dev/sda3 on /opt/5620sam/dbbackup type ext4 (rw,noatime,barrier=0) /dev/sdb1 on /opt/5620sam/samdb/archivelog type ext4 (rw,noatime, barrier=0) Note: The example lists physical disk partitions, which are named sdan; a logical partition is named vdan. 4 5 Enter the following once for each 5620 SAM partition: # tune2fs -m 0 /dev/partition where partition is the partition name Close the console window. END OF STEPS 3HE AAAG-TQZZA 45

46 General information 5620 SAM 5650 CPAM RHEL OS package groups and packages 4.7 General information Description This section lists the RHEL package groups and packages, in addition to a Minimal OS installation, that are required for 5620 SAM deployment. If a required group or package is not installed, a 5620 SAM component deployment fails. Some packages provide basic functions, for example, man and Telnet, but are not required by the 5620 SAM. These optional packages are listed separately. Note: During a RHEL OS installation, you must select the Minimal installation option, and then specify the required package groups and packages listed in this section. Note: The RHEL rpm utility requires hardware driver files in binary format. If the RHEL driver files provided by your server hardware vendor are in source rpm format, you may need to install additional packages in order to compile the files into binary format. See the station hardware documentation for information. The required package groups for each component type are the following: Desktop Desktop Platform Legacy X Window System Compatibility X Window System 4.8 Package installation method Description For ease of administration, it is recommended to use the RHEL yum utility to install packages. The yum syntax is the following: yum -y install package_1 package_2... package_n Note: To install packages using yum, you require a yum repository. The following repository types are available: local repository, which you can create using the RHEL OS installation DVD Internet-based repository, which you can access after you register with the Red Hat Network See the RHEL documentation for information about setting up a yum repository. Note: If a package has dependencies on one or more additional packages that are not listed in a table, the yum utility installs the additional packages. 46 3HE AAAG-TQZZA

47 5620 SAM 5650 CPAM Server and database packages 4.9 Server and database packages Description Table 5, Required packages, server and database (p. 47) lists the packages that are required, in addition to the package groups, for a main server, auxiliary server, Cflowd auxiliary server, analytics server, 5620 SAM database, or auxiliary database. To facilitate the package installation, you can copy the following command block and paste it in a CLI. yum -y install bc.x86_64 binutils.x86_64 compat-libcap1.x86_64 yum -y install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 yum -y install dbus-glib-devel.i686 elfutils-libelf-devel.x86_64 yum -y install elfutils.x86_64 firefox.x86_64 gcc-c++.x86_64 gcc.x86_64 yum -y install glibc-devel.i686 glibc-devel.x86_64 gtk2.i686 yum -y install hal-devel.i686 hdparm.x86_64 irqbalance.x86_64 ksh.x86_64 yum -y install libaio-devel.i686 libaio-devel.x86_64 libaio.i686 yum -y install libaio.x86_64 libgcc.x86_64 libibverbs.x86_64 yum -y install libstdc++-devel.x86_64 libxau.x86_64 libxau.i686 yum -y install libxcb.x86_64 libxcb.i686 libxtst.i686 libxtst.x86_64 yum -y install lsof.x86_64 make.x86_64 numactl-devel.i686 yum -y install numactl-devel.x86_64 openmotif.i686 openssh.x86_64 yum -y install openssh-askpass.x86_64 openssh-clients.x86_64 yum -y install openssh-server.x86_64 rsync.x86_64 sysstat.x86_64 yum -y install tcpdump.x86_64 unzip.x86_64 xorg-x11-proto-devel.noarch yum -y install zip.x86_64 Table 5 Required packages, server and database Package name bc.x86_64 binutils.x86_64 compat-libcap1.x86_64 compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 dbus-glib-devel.i686 elfutils-libelf-devel.x86_64 elfutils.x86_64 firefox.x86_64 gcc-c++.x86_64 gcc.x86_64 glibc-devel.i686 glibc-devel.x86_64 Description GNU's bc (a numeric processing language) and dc (a calculator) A GNU collection of binary utilities Library for getting and setting POSIX.1e capabilities Compatibility standard C++ libraries Compatibility standard C++ libraries Libraries and headers for the D-Bus GLib bindings Development support for libelf A collection of utilities and DSOs to handle compiled objects Mozilla Firefox Web browser C++ support for GCC Various compilers, for example, C, C++, Objective-C, and Java Object files for development using standard C libraries Object files for development using standard C libraries 3HE AAAG-TQZZA 47

48 Server and database packages 5620 SAM 5650 CPAM Table 5 Required packages, server and database (continued) Package name gtk2.i686 hal-devel.i686 hdparm.x86_64 1 irqbalance.x86_64 ksh.x86_64 libaio-devel.i686 libaio-devel.x86_64 libaio.i686 libaio.x86_64 libgcc.x86_64 libibverbs.x86_64 libstdc++-devel.x86_64 libxau.x86_64 libxau.i686 libxcb.x86_64 libxcb.i686 libxtst.i686 libxtst.x86_64 lsof.x86_64 1 make.x86_64 numactl-devel.i686 numactl-devel.x86_64 openmotif.i686 Description The GIMP ToolKit (GTK+), a library for creating GUIs for X Libraries and headers for HAL Utility for displaying and setting hard disk parameters Daemon that evenly distributes IRQ load across multiple CPUs The Original ATT Korn Shell Development files for Linux-native asynchronous I/O access Development files for Linux-native asynchronous I/O access Linux-native asynchronous I/O access library Linux-native asynchronous I/O access library GCC version 4.4 shared support library Core user space library that implements hardware abstracted verbs protocol Header files and libraries for C++ development X authorization file management libary X authorization file management libary X protocol C-language binding library X protocol C-language binding library X.Org X11 libxtst runtime library X.Org X11 libxtst runtime library Provides a utility to list information about open files GNU tool which simplifies the build process for users Development package for building Applications that use numa Development package for building Applications that use numa Open Motif runtime libraries and executables openssh.x86_64 Open source implementation of SSH protocol versions 1 and 2 openssh-askpass.x86_64 openssh-clients.x86_64 openssh-server.x86_64 rsync.x86_64 sysstat.x86_64 tcpdump.x86_64 unzip.x86_64 Passphrase dialog for OpenSSH and X Open-source SSH client application Open source SSH server daemon A program for synchronizing files over a network The sar and iostat system monitoring commands Command-line packet analyzer and network traffic capture; used by technical support for debugging A utility for unpacking zip files 48 3HE AAAG-TQZZA

49 5620 SAM 5650 CPAM Client and client delegate server packages Table 5 Required packages, server and database (continued) Package name xorg-x11-proto-devel.noarch zip.x86_64 Description X.Org X11 Protocol headers A file compression utility Notes: 1. New in Release 14.0 Table 6, Optional packages, server and database (p. 49) lists optional packages for a main server, auxiliary server, Cflowd auxiliary server, analytics server, 5620 SAM database, or auxiliary database. To facilitate the package installation, you can copy the following command block and paste it in a CLI. yum -y install ftp.x86_64 man.x86_64 net-snmp.x86_64 yum -y install net-snmp-utils.x86_64 nfs-utils.x86_64 telnet.x86_64 yum -y install vsftpd.x86_64 Table 6 Optional packages, server and database Package name ftp.x86_64 man.x86_64 net-snmp.x86_64 net-snmp-utils.x86_64 nfs-utils.x86_64 telnet.x86_64 vsftpd.x86_64 Description The standard UNIX FTP (File Transfer Protocol) client A set of documentation tools: man, apropos and whatis The SNMP Agent Daemon and documentation SNMP clients such as snmpget and snmpwalk NFS utilities and supporting clients and daemons for the kernel The client program for the Telnet remote login protocol Very Secure Ftp Daemon 4.10 Client and client delegate server packages Description Table 7, Required packages, 32-bit single-user client (p. 50) lists the individual RHEL packages, in addition to the required package groups, that a single-user client requires on a 32-bit OS installation. To facilitate the package installation, you can copy the following command block and paste it in a CLI. yum -y install compat-libstdc++-33.i686 dbus-glib-devel.i686 yum -y install firefox.i686 glibc.i686 hal-devel.i686 libxtst.i686 yum -y install openmotif.i686 xorg-x11-proto-devel.noarch 3HE AAAG-TQZZA 49

50 Client and client delegate server packages 5620 SAM 5650 CPAM Table 7 Required packages, 32-bit single-user client Package name compat-libstdc++-33.i686 dbus-glib-devel.i686 firefox.i686 glibc.i686 hal-devel.i686 libxtst.i686 openmotif.i686 xorg-x11-proto-devel.noarch Description Compatibility standard C++ libraries Libraries and headers for the D-Bus GLib bindings Mozilla Firefox Web browser Object files for development using standard C libraries Libraries and headers for HAL X.Org X11 libxtst runtime library Open Motif runtime libraries and executables X.Org X11 Protocol headers Table 8, Required packages, 64-bit single-user client and client delegate server (p. 50) lists the individual RHEL packages, in addition to the required package groups, for the following: single-user client on 64-bit OS installation client delegate server To facilitate the package installation, you can copy the following command block and paste it in a CLI. yum -y install firefox.x86_64 irqbalance.x86_64 libxtst.i686 Table 8 Required packages, 64-bit single-user client and client delegate server Package name firefox.x86_64 irqbalance.x86_64 libxtst.i686 Description Mozilla Firefox Web browser Daemon that evenly distributes IRQ load across multiple CPUs X.Org X11 libxtst runtime library 50 3HE AAAG-TQZZA

51 5620 SAM 5650 CPAM RHEL disk configuration 5 RHEL disk configuration 5.1 Overview Purpose This chapter describes the disk configuration and partitioning requirements for 5620 SAM components in trial and live deployments Contents 5.1 Overview Introduction To configure a 5620 SAM disk partition created after the RHEL OS installation Disk partitioning for trial deployments Disk partitioning for live deployments Introduction General information If the 5620 SAM is to perform large-scale statistics collection, you must implement highperformance disk throughput using one of the following: internal disks in a hardware RAID 0 configuration external disks in a hardware RAID 0 or RAID 1+0 configuration SAN storage Note: A 5620 SAM disk subsystem requires read and write caching with fault protection. Note: It is recommended that you create the 5620 SAM disk partitions during the RHEL OS installation. A partition created after the OS installation requires additional configuration, as described in 5.3 To configure a 5620 SAM disk partition created after the RHEL OS installation (p. 52). You can determine the number of disks required for high-performance throughput by submitting a 5620 SAM Platform Sizing Request. See the 5620 SAM Planning Guide for scaling guidelines related to statistics collection. Contact technical support for information about using a disk array. 3HE AAAG-TQZZA 51

52 To configure a 5620 SAM disk partition created after the RHEL OS installation 5620 SAM 5650 CPAM Using RAID with the 5620 SAM CAUTION Service Disruption An improper RAID configuration may result in throughput degradation or failure. A 5620 SAM deployment that includes RAID is supported only when RAID is implemented as described in this guide and in the 5620 SAM Planning Guide. You must strictly follow the RAID specifications in the 5620 SAM Planning Guide for the current release before you attempt to install, upgrade, or convert a 5620 SAM system that uses RAID. Contact technical support for information. A RAID implementation for the 5620 SAM requires a hardware RAID controller that can create and manage the required number of volumes. For optimal performance, a 5620 SAM station requires the recommended number of disks configured in a striping, or RAID 0, volume. A single RAID 0 disk failure can cause a complete file system failure, so for live deployments, disk mirroring using a RAID 1+0 configuration is recommended for greater resiliency and to reduce the recovery time after a disk failure. Note: The use of software RAID is not supported. Note: The installation, administration, or recovery of RAID in a 5620 SAM system is the responsibility of the owner of the system Logical disk management Logical disk implementation is supported using the LVM function according to the 5620 SAM Planning Guide specifications. Note: LVM is supported only for resizing disk partitions, and not for creating software RAID volumes. See the 5620 SAM Planning Guide for information about the LVM features that are supported in a 5620 SAM deployment. Note: Before you use LVM to resize a partition, you must ensure that the throughput and latency of the new configuration are within the allowed 5620 SAM tolerances. See To test 5620 SAM disk performance in the 5620 SAM System Administrator Guide for information about performing the required check. 5.3 To configure a 5620 SAM disk partition created after the RHEL OS installation Description Perform this procedure on each 5620 SAM disk partition that you create after the RHEL OS installation. 52 3HE AAAG-TQZZA

53 5620 SAM 5650 CPAM To configure a 5620 SAM disk partition created after the RHEL OS installation CAUTION Steps Service Disruption This procedure requires a restart of the station that hosts the partition. If a 5620 SAM component is installed on the station, you must perform the procedure only during a scheduled maintenance period Log in to the 5620 SAM station as the root user. Open a console window. Mount the partition; see the RHEL OS documentation for information. Enter the following: # tune2fs -m 0 -o +acl /dev/device where device is the name of the device associated with the partition Open the /etc/fstab file using a plain-text editor such as vi. Perform one of the following. a. For a partition in a physical hardware deployment, add the following entry: /dev/device mount_point ext4 barrier=0,noatime 1 2 b. For a partition in a VM deployment, add the following entry: /dev/device mount_point ext4 noatime 1 2 where device is the name of the device associated with the partition mount_point is the partition mount point, for example, /opt/5620sam Save and close the /etc/fstab file. 3HE AAAG-TQZZA 53

54 Disk partitioning for trial deployments 5620 SAM 5650 CPAM 8 Enter the following to reboot the station: # init 6 END OF STEPS 5.4 Disk partitioning for trial deployments Description CAUTION Service Disruption Each disk partition described in this section must be a mounted partition and not a symbolic link. The 5620 SAM does not support the use of symbolic links to represent partitions. The following disk partitioning schemes are supported only for trial 5620 SAM deployments in a lab environment or for demonstration purposes. Note: See the 5620 SAM Planning Guide or the response to your 5620 SAM Platform Sizing Request for information about the supported disk types. Note: For each database partitioning scheme, the Oracle management user home directory specified by the ORACLE_HOME environment variable is /opt/5620sam/oracle12r1. The following table lists the partitions required for the trial deployment of a collocated 5620 SAM database and main server. Table 9 Trial partitioning scheme, collocated 5620 SAM database and main server Disks required: two 146-Gbyte or two 300-Gbyte Partition Content Size (Gbytes) / Root, including /usr and /var 25 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM software, operating data 50 /opt/5620sam/dbbackup Database backups 35 /opt/5620sam/nebackup NE configuration backups Network-specific 1 /opt/5620sam/samdb Database tablespaces 90 /opt/5620sam/samdb/archivelog Database archive logs 35 /opt/5620sam/server/nms/log 5620 SAM server log files 15 /opt/5620sam/server/xml_output Output of OSSI file export operations HE AAAG-TQZZA

55 5620 SAM 5650 CPAM Disk partitioning for trial deployments Table 9 Trial partitioning scheme, collocated 5620 SAM database and main server (continued) Disks required: two 146-Gbyte or two 300-Gbyte Partition Content Size (Gbytes) /smallcell 2 At operator discretion Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC Customer data; can be partitioned according to customer requirements 16 per 1000 NEs without statistics-collection auxiliary server; otherwise, 3 per per 1000 MS EC NEs plus 1 per 1000 MS HC NEs 3 Remainder Notes: 1. Derived using the formula in 2.4 Upgrading from Release 12.0 R4 or earlier (p. 17) 2. Required only for Small Cell NE management 3. Based on 15-minute statistics collection interval, 7-day retention period The following table lists the partitions required for the trial deployment of a main server in a distributed 5620 SAM system. Table 10 Trial partitioning scheme, main server, distributed system Disks required: one 146-Gbyte Partition Content Size (Gbytes) / Root, including /usr and /var 25 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data 70 /opt/5620sam/nebackup NE configuration backups Network-specific 1 /opt/5620sam/server/nms/log 5620 SAM server log files 15 /opt/5620sam/server/xml_output Output of OSSI file export operations 10 /smallcell 2 At operator discretion Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC Customer data; can be partitioned according to customer requirements 16 per 1000 NEs without statistics-collection auxiliary server; otherwise, 3 per per 1000 MS EC NEs plus 1 per 1000 MS HC NEs 3 Remainder Notes: 1. Derived using the formula in 2.4 Upgrading from Release 12.0 R4 or earlier (p. 17) 2. Required only for Small Cell NE management 3. Based on 15-minute statistics collection interval, 7-day retention period 3HE AAAG-TQZZA 55

56 Disk partitioning for trial deployments 5620 SAM 5650 CPAM The following table lists the partitions required for the trial deployment of a 5620 SAM database in a distributed 5620 SAM system. Table 11 Trial partitioning scheme, 5620 SAM database, distributed system Disks required: two 146-Gbyte Partition Content Size (Gbytes) / Root, including /usr and /var 25 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM database software, operating data 40 /opt/5620sam/dbbackup Database backups 40 /opt/5620sam/samdb Database tablespaces 100 /opt/5620sam/samdb/archivelog Database archive logs 40 /opt/5620sam/samdb/redolog Database redo logs 8 At operator discretion Customer data; can be partitioned according to customer requirements Remainder The following table lists the partitions required for the trial deployment of an auxiliary server that is to collect statistics. Table 12 Trial partitioning scheme, statistics-collection auxiliary server Disks required: one 146-Gbyte minimum, two 146-Gbyte recommended Size (Gbytes) Partition Content One disk Two disks / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data /opt/5620sam/auxserver/nms/log 5620 SAM server log files /opt/5620sam/auxserver/xml_output Output of OSSI file export operations /opt/5620sam/lte 1 Collected enodeb statistics /smallcell 2 At operator discretion Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC Customer data; can be partitioned according to customer requirements 18 per 1000 MS EC NEs, plus 5 per 1000 MS HC NEs 3 Remainder Notes: 1. Required only if enodeb statistics are to be collected 2. Required only for Small Cell NE management 3. Based on 15-minute statistics collection interval, 7-day retention period 56 3HE AAAG-TQZZA

57 5620 SAM 5650 CPAM Disk partitioning for trial deployments The following table lists the partitions required for the trial deployment of an auxiliary server that is to collect call-trace data. Table 13 Trial partitioning scheme, call-trace auxiliary server Disks required: four 146-Gbyte or four 300-Gbyte Size (Gbytes) Partition Content Disks 1 and 2, RAID 0 recommended / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data /opt/5620sam/auxserver/nms/log 5620 SAM server log files At operator discretion Disks 3 and above, RAID 0 mandatory Customer data; can be partitioned according to customer requirements Remainder /opt/5620sam/calltrace Call-trace output 80% of disk /opt/5620sam/debugtrace Call-trace debug output 20% of disk The following table lists the partitions required for the trial deployment of an auxiliary server that is to collect PCMD records. Table 14 Trial partitioning scheme, PCMD auxiliary server Disks required: two 146 Gbyte or 300-Gbyte, plus six 300-Gbyte Size (Gbytes) Partition Content Disks 1 and 2, RAID 0 recommended / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data /opt/5620sam/auxserver/nms/log 5620 SAM server log files At operator discretion Disks 3 and above, RAID 0 mandatory Customer data; can be partitioned according to customer requirements Remainder /opt/5620sam/pcmd_output PCMD output All The following table lists the partitions required for the trial deployment of a Cflowd auxiliary server. 3HE AAAG-TQZZA 57

58 Disk partitioning for trial deployments 5620 SAM 5650 CPAM Table 15 Trial partitioning scheme, Cflowd auxiliary server Disk required: one 146-Gbyte or larger Partition Content Size (Gbytes) / Root, including /usr and /var 25 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM Cflowd auxiliary server software Collected statistics data files Remainder The following table lists the partitions required for the trial deployment of an auxiliary database station. Table 16 Trial partitioning scheme, auxiliary database Disk required: two 300-Gbyte, plus a minimum of six 600-Gbyte Partition Content Size (Gbytes) Disks 1 and 2, RAID 1 / Root, including /usr and /var 40 Swap 16 /opt 5620 SAM auxiliary database software Remainder Disks 3 and above, RAID 1+0 /opt/5620sam/auxdb/data Auxiliary database data All The following table lists the partitions required for the trial deployment of an analytics server. Table 17 Trial partitioning scheme, analytics server Disks required: one 146-Gbyte Partition Content Size (Gbytes) / Root, including /usr and /var 25 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM software, operating data 75 The following table lists the partitions required for the trial deployment of a single-user client or client delegate server on RHEL. Table 18 Trial partitioning scheme, single-user client or client delegate server Disk required: one 146-Gbyte or larger Size (Gbytes) Partition Content 146 >146 / Root, including /usr and /var Swap Equal to RAM, up to HE AAAG-TQZZA

59 5620 SAM 5650 CPAM Disk partitioning for live deployments Table 18 Trial partitioning scheme, single-user client or client delegate server (continued) Disk required: one 146-Gbyte or larger Size (Gbytes) Partition Content 146 >146 /opt/5620sam 5620 SAM client software 5 20 At operator discretion Customer data; can be partitioned according to customer requirements Remainder 5.5 Disk partitioning for live deployments Description CAUTION Service Disruption Each disk partition described in this section must be a mounted partition and not a symbolic link. The 5620 SAM does not support the use of symbolic links to represent partitions. The following disk partitioning schemes are supported for 5620 SAM deployments in a live network environment. Note: See the 5620 SAM Planning Guide or the response to your 5620 SAM Platform Sizing Request for information about the supported disk types. Note: For each database partitioning scheme, the Oracle management user home directory specified by the ORACLE_HOME environment variable is /opt/5620sam/oracle12r1. The following table lists the partitions required for the live deployment of a collocated 5620 SAM database and main server. Table 19 Live partitioning scheme, collocated 5620 SAM database and main server Disks required: four 146-Gbyte or four 300-Gbyte Size (Gbytes) Partition Content (RAID 0) (RAID 0) / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM software, operating data /opt/5620sam/dbbackup Database backups /opt/5620sam/nebackup NE configuration backups Network-specific 1 /opt/5620sam/samdb Database tablespaces /opt/5620sam/samdb/archivelog Database archive logs HE AAAG-TQZZA 59

60 Disk partitioning for live deployments 5620 SAM 5650 CPAM Table 19 Live partitioning scheme, collocated 5620 SAM database and main server (continued) Disks required: four 146-Gbyte or four 300-Gbyte Size (Gbytes) Partition Content (RAID 0) (RAID 0) /opt/5620sam/server/nms/log 5620 SAM server log files /opt/5620sam/server/xml_output Output of OSSI file export operations /smallcell 2 At operator discretion Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC Customer data; can be partitioned according to customer requirements 16 per 1000 NEs without statistics-collection auxiliary server; otherwise, 3 per per 1000 MS EC NEs plus 1 per 1000 MS HC NEs 3 Remainder Notes: 1. Derived using the formula in 2.4 Upgrading from Release 12.0 R4 or earlier (p. 17) 2. Required only for Small Cell NE management 3. Based on 15-minute statistics collection interval, 7-day retention period The following table lists the partitions required for the live deployment of a main server in a distributed 5620 SAM system. Table 20 Live partitioning scheme, main server, distributed system Disks required: two 146-Gbyte, or four 146-Gbyte or 300-Gbyte Size (Gbytes) Partition Content (RAID 0) or 300 (RAID 0) / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data /opt/5620sam/nebackup NE configuration backups Network-specific 1 /opt/5620sam/server/nms/log 5620 SAM server log files /opt/5620sam/server/xml_output Output of OSSI file export operations /smallcell 2 At operator discretion Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC Customer data; can be partitioned according to customer requirements 16 per 1000 NEs without statistics-collection auxiliary server; otherwise, 3 per per 1000 MS EC NEs plus 1 per 1000 MS HC NEs 3 Remainder 60 3HE AAAG-TQZZA

61 5620 SAM 5650 CPAM Disk partitioning for live deployments Notes: 1. Derived using the formula in 2.4 Upgrading from Release 12.0 R4 or earlier (p. 17) 2. Required only for Small Cell NE management 3. Based on 15-minute statistics collection interval, 7-day retention period The following table lists the partitions required for the live deployment of a 5620 SAM database in a distributed 5620 SAM system. Table 21 Live partitioning scheme, 5620 SAM database, distributed system Disks required: four 146-Gbyte or four 300-Gbyte Size (Gbytes) Partition Content (RAID 0) (RAID 0) or greater (RAID 0) / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM software, operating data /opt/5620sam/dbbackup Database backups /opt/5620sam/samdb Database tablespaces /opt/5620sam/samdb/archivelog Database archive logs /opt/5620sam/samdb/redolog Database redo logs At operator discretion Customer data; can be partitioned according to customer requirements Remainder The following table lists the partitions required for the live deployment of an auxiliary server that is to collect statistics. Table 22 Live partitioning scheme, statistics-collection auxiliary server Disks required: four 146-Gbyte or four 300-Gbyte, RAID 0 Partition Content Size (Gbytes) / Root, including /usr and /var 40 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data 180 /opt/5620sam/auxserver/nms/log 5620 SAM server log files 50 /opt/5620sam/auxserver/xml_output Output of OSSI file export operations Remainder (150 minimum; 180 minimum if 5620 SAM system includes auxiliary database) /opt/5620sam/lte 1 Collected enodeb statistics 100 3HE AAAG-TQZZA 61

62 Disk partitioning for live deployments 5620 SAM 5650 CPAM Table 22 Live partitioning scheme, statistics-collection auxiliary server (continued) Disks required: four 146-Gbyte or four 300-Gbyte, RAID 0 Partition Content Size (Gbytes) /smallcell 2 Small Cell management and statistics files; required for management of Small Cell NEs other than 9361 HC and 9961 MS HC 18 per 1000 MS EC NEs, plus 5 per 1000 MS HC NEs 3 Notes: 1. Required only if enodeb statistics are to be collected 2. Required only for Small Cell NE management 3. Based on 15-minute statistics collection interval, 7-day retention period The following table lists the partitions required for the live deployment of an auxiliary server that is to collect call-trace data. Table 23 Live partitioning scheme, call-trace auxiliary server Disks required: four 146-Gbyte or four 300-Gbyte Size (Gbytes) Partition Content Disks 1 and 2, RAID 0 recommended / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM server software, operating data /opt/5620sam/auxserver/nms/log 5620 SAM server log files At operator discretion Disks 3 and above, RAID 0 mandatory Customer data; can be partitioned according to customer requirements Remainder /opt/5620sam/calltrace Call-trace output 80% of disk /opt/5620sam/debugtrace Call-trace debug output 20% of disk The following table lists the partitions required for the live deployment of an auxiliary server that is to collect PCMD records. Table 24 Live partitioning scheme, PCMD auxiliary server Disks required: two 146 Gbyte or 300-Gbyte, plus six 300-Gbyte Size (Gbytes) Partition Content Disks 1 and 2, RAID 0 recommended / Root, including /usr and /var Swap Equal to RAM, up to HE AAAG-TQZZA

63 5620 SAM 5650 CPAM Disk partitioning for live deployments Table 24 Live partitioning scheme, PCMD auxiliary server (continued) Disks required: two 146 Gbyte or 300-Gbyte, plus six 300-Gbyte Size (Gbytes) Partition Content /opt/5620sam 5620 SAM server software, operating data /opt/5620sam/auxserver/nms/log 5620 SAM server log files At operator discretion Disks 3 and above, RAID 0 mandatory Customer data; can be partitioned according to customer requirements Remainder /opt/5620sam/pcmd_output PCMD output All The following table lists the partitions required for the live deployment of a Cflowd auxiliary server. Table 25 Live partitioning scheme, Cflowd auxiliary server Disk required: two 300-Gbyte in RAID 0 configuration Partition Content Size (Gbytes) / Root, including /usr and /var 40 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM Cflowd auxiliary server software 50 /opt/5620sam/dcp_data Collected statistics data files Remainder 1 Notes: 1. A larger disk allows for longer data file retention in the event that the IPDR FTP destination is not available. The following table lists the partitions required for the live deployment of an auxiliary database station. Table 26 Live partitioning scheme, auxiliary database Disk required: two 300-Gbyte, plus a minimum of twelve 600-Gbyte Partition Content Size (Gbytes) Disks 1 and 2, RAID 1 / Root, including /usr and /var 40 Swap 16 /opt 5620 SAM auxiliary database software Remainder Disks 3 and above, 600-Gbyte, RAID 1+0 /opt/5620sam/auxdb/data Auxiliary database data All The following table lists the partitions required for the live deployment of an analytics server. 3HE AAAG-TQZZA 63

64 Disk partitioning for live deployments 5620 SAM 5650 CPAM Table 27 Live partitioning scheme, analytics server Disks required: one 300-Gbyte Partition Content Size (Gbytes) / Root, including /usr and /var 40 Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM software, operating data 100 The following table lists the partitions required for the live deployment of a single-user client or client delegate server on RHEL. Table 28 Live partitioning scheme, single-user client or client delegate server Disk required: one 146-Gbyte or larger Size (Gbytes) Partition Content 146 >146 / Root, including /usr and /var Swap Equal to RAM, up to 16 /opt/5620sam 5620 SAM client software 5 20 At operator discretion Customer data; can be partitioned according to customer requirements Remainder 64 3HE AAAG-TQZZA

65 5620 SAM 5650 CPAM Configuring SSL security 6 Configuring SSL security 6.1 Overview Purpose This chapter describes how to enable or disable SSL security in a 5620 SAM system Contents 6.1 Overview Introduction SSL configuration workflow To prepare a 5620 SAM system for SSL To enable SSL on a main server To enable SSL on an auxiliary server To enable SSL and HTTPS on a Cflowd auxiliary server To enable or disable SSL and HTTPS on an analytics server To enable SSL and HTTPS for an OSS client To enable SSL on a RHEL client delegate server To disable SSL on a single-user GUI client To disable SSL on a RHEL client delegate server To disable SSL on a Windows client delegate server Introduction General information Secure Sockets Layer, or SSL, is a security mechanism for data encryption, client authentication, and message integrity. You can configure SSL to provide secure communication between 5620 SAM main servers and other components. Note: The following 5620 SAM functions require SSL: Lawful Intercept, or LI WebDAV access to enodeb activation data The following figure shows the SSL communication channels between 5620 SAM components. 3HE AAAG-TQZZA 65

66 Introduction 5620 SAM 5650 CPAM Figure SAM communication channels and security OSS application Firewall JMS/SSL HTTPS HTTP User ID/password Firewall 5620 SAM client GUI User ID/ password EJB/SSL User ID/ password JMS/SSL 5620 SAM server Local security data SNMPv3 USM/VACM SNMPv1, v2 community string SSH1/2 or Telnet User ID/password FTP/SCP User ID/password User authorization and User ID/password Database authentication session SSL requests authentication Managed network Databases if redundant 5620 SAM server if redundant RADIUS, TACACS+, SAM-L, or CSA SSL requires a security certificate that is shared among members of a network domain. A certificate from a certification authority, or CA, is used in a live 5620 SAM deployment, but you can locally generate a self-signed certificate for internal use, such as in a lab deployment. Note: You cannot selectively enable SSL on the components of a 5620 SAM system. If SSL is enabled on one component, SSL must be enabled on all other components that support SSL Functional description CAUTION Security Risk Using a self-signed SSL certificate in a live 5620 SAM deployment is an extreme security risk. It is strongly recommended that you use a self-signed SSL security certificate only in a trial deployment in an isolated network. You must import an SSL security certificate to a truststore file on each of the following stations in a 5620 SAM system: main server 66 3HE AAAG-TQZZA

67 5620 SAM 5650 CPAM Introduction OSS client Cflowd auxiliary server After you import the security certificate, you use the 5620 SAM samconfig utility on each main server to enable and configure SSL. A main server then distributes the truststore file to each singleuser GUI client and client delegate server. You must manually copy an associated keystore file to each client, client delegate server, auxiliary server, or analytics server station, after which you can enable SSL on each. Note: You must use the Java Key Store, or JKS, keystore format in a 5620 SAM system. If you have a keystore in a different format, for example, PKCS12, you can use the Java keytool utility to convert the keystore to JKS format. Note: The 5620 SAM does not support the use of multiple private encryption keys. A 5620 SAM main or auxiliary server uses only the first encryption key in a keystore, and ignores additional keys. Note: When SSO is enabled, each main server keystore must contain the SSL certificate of the remote server. Note: The SSL configuration on a 5620 SAM component persists through system upgrades. Note: In a redundant system, the standby main server is an SSL client of the primary main server GUI client and main server communication When SSL is enabled, the client GUI status bar displays a padlock icon, as shown in Figure 3, SSL security icon (p. 67). The icon is also displayed on the following: client GUI login form information form opened using Help About 5620 SAM / 5650 CPAM Figure 3 SSL security icon SSL secures the following client interfaces: single-user GUI client or client delegate server EJB, JMS, and HTTP OSS client JMS and HTTP When a non-ssl single-user GUI client connects to a main server that has SSL enabled, SSL is automatically enabled on the client; no additional user action is required. The same is true for a 3HE AAAG-TQZZA 67

68 Introduction 5620 SAM 5650 CPAM Windows client delegate server. Subsequently, the client or client delegate server uses HTTPS instead of HTTP for server access, and each server URL changes accordingly. Disabling GUI client SSL To disable SSL on a single-user GUI client, you must uninstall the client software, and then install the client software with SSL disabled, as described in 6.11 To disable SSL on a single-user GUI client (p. 88). To disable SSL on a client delegate server, you must reconfigure the client delegate server, as described in 6.12 To disable SSL on a RHEL client delegate server (p. 88) and 6.13 To disable SSL on a Windows client delegate server (p. 90) Updating TLS versions and cipher lists The 5620 SAM includes a tool for managing the supported TLS versions and ciphers used for secure inter-component communication. When a new TLS version is to be supported, or new TLS ciphers are available, you can configure the 5620 SAM to use the new version or ciphers, and remove the support for outdated versions and ciphers. Note: The 5620 SAM uses only TLS ciphers, and not SSL ciphers. See To update the supported 5620 SAM TLS versions and ciphers in the5620 SAM System Administrator Guide for information about using the tool Managing SSL certificate expiry When SSL is configured on a main or auxiliary server, the server checks the expiry date of the SSL certificate in the local keystore during server initialization and once every 24 hours thereafter. If the certificate is to expire within a predefined period, the 5620 SAM raises a warning alarm. If the certificate is expired, the 5620 SAM clears the warning alarm and raises a critical alarm. The default warning period is 30 days from the current date. To change the warning period, contact technical support. The 5620 SAM updates the Last Time Detected value of an expiry warning alarm daily, and raises a new critical alarm daily when a certificate is expired. The alarm information includes the certificate ID, and the expiry date and time. When you replace an expiring or expired certificate with a new and valid certificate, the associated expiry alarms clear. Each type of alarm persists through events such as server switchovers. Note: The Days Remaining value in an expiry alarm is based on the number of complete 24- hour periods until the certificate expiry time. If fewer than 24 hours remain until the expiry, the Days Remaining value is zero, but the 5620 SAM does not raise an alarm about the expired certificate until the actual expiry time. Note: If a keystore contains hierarchical certificates, the 5620 SAM checks the expiry date of each certificate in the hierarchy, starting with the lowest, and uses the earliest expiry date found as the reference point for raising an alarm. 68 3HE AAAG-TQZZA

69 5620 SAM 5650 CPAM SSL configuration workflow SSL certificate renewal The SSL certificate renewal process is the same as the initial configuration process. After you obtain the new keystore and truststore files, you can use the workflow in 6.3 SSL configuration workflow (p. 68) to update the 5620 SAM SSL configuration. 6.3 SSL configuration workflow Description CAUTION Service Disruption An incorrect SSL configuration prevents communication between 5620 SAM components and may seriously affect network management. An operator who performs a procedure in this chapter must have SSL security knowledge and experience. Contact technical support for SSL configuration assistance. CAUTION Service Disruption Configuring SSL in an existing 5620 SAM system requires one of the following, each of which causes a temporary network management outage: standalone system main server shutdown redundant system server activity switch Ensure that you configure SSL in a 5620 SAM system only during a scheduled maintenance period. The following is the sequence of high-level actions that are required to configure SSL in a 5620 SAM system Stages Note: You can use the workflow to perform the initial SSL configuration, or to renew an expired SSL certificate Preconfigure the 5620 SAM system; see 6.4 To prepare a 5620 SAM system for SSL (p. 71). To enable SSL in an existing 5620 SAM system that is not being upgraded, go to Stage 4. If you are performing a 5620 SAM system installation or upgrade, enable SSL, specify the keystore and truststore files for each component, as required, and then go to Stage 12. 3HE AAAG-TQZZA 69

70 SSL configuration workflow 5620 SAM 5650 CPAM 4 In a redundant system, enable SSL on the standby main server; see 6.5 To enable SSL on a main server (p. 74) Enable SSL on each reserved auxiliary server; see 6.6 To enable SSL on an auxiliary server (p. 77). In a redundant system, open a 5620 SAM GUI client to monitor the network during the server activity switch in subsequent steps. In a redundant system, enable SSL on the primary main server; see 6.5 To enable SSL on a main server (p. 74). In a standalone system, enable SSL on the standalone main server; see 6.5 To enable SSL on a main server (p. 74). Enable SSL on each preferred auxiliary server; see 6.6 To enable SSL on an auxiliary server (p. 77). Enable SSL and HTTPS on each analytics server; see 6.8 To enable or disable SSL and HTTPS on an analytics server (p. 82). Enable SSL on each RHEL client delegate server; see 6.10 To enable SSL on a RHEL client delegate server (p. 86). Enable SSL and HTTPS on each OSS client; see 6.9 To enable SSL and HTTPS for an OSS client (p. 86). Enable SSL and HTTPS on each Cflowd auxiliary server; see 6.7 To enable SSL and HTTPS on a Cflowd auxiliary server (p. 80). Open each single-user GUI client to enable SSL and HTTPS automatically via the auto-client update function. 70 3HE AAAG-TQZZA

71 5620 SAM 5650 CPAM To prepare a 5620 SAM system for SSL 6.4 To prepare a 5620 SAM system for SSL Description The following steps describe how to preconfigure the 5620 SAM for SSL communication Steps 1 2 If you have an SSL certificate that you want to use, for example, a new certificate that replaces an expired certificate, go to Step 3. If you have a set of SSL keystore and truststore files, go to Step 10. Note: You must use the Java Key Store, or JKS, keystore format. If your keystore has a different format, for example, PKCS12, you can use the Java keytool utility to convert the keystore to JKS format. Note: Ensure that the keystore that you use contains only one private encryption key. A 5620 SAM main or auxiliary server uses only the first encryption key in a keystore, and ignores additional keys. 3 Use the Java keytool utility on a main server to generate a keystore file. For information about the keytool utility, visit the Oracle website. Note: The keytool utility that you use must be from the same Java version as the Java version that the 5620 SAM uses; see the 5620 SAM Planning Guide for Java version information. Note: The keypass and storepass passwords that you specify must be identical. # keytool -genkey -alias alias -keyalg RSA -keypass password -storepass password -keystore keystore_file -storetype JKS -validity days -dname CN=common_name, OU=org_unit, O=org_name, L=locality, S=state, C=country where alias is a case-insensitive alias that is required for subsequent keytool operations password is the password for the key and keystore keystore_file is the name of the generated keystore file days is the number of days before the SSL key expires; the default is 90 and where the following comprise the X.500 distinguished name: common_name is the main server hostname or IP address org_unit is a department or division name 3HE AAAG-TQZZA 71

72 To prepare a 5620 SAM system for SSL 5620 SAM 5650 CPAM org_name is a company name locality is a city name state is a state or region name country is a country code, for example, US Record the key and keystore password. If you do not require an SSL certificate that is signed by a CA, for example, in a 5620 SAM lab deployment, perform the following steps. 1. Enter the following to export the certificate to a certificate file: # keytool -export -alias alias -keystore keystore_file -storepass password -file certificate_file where alias is the alias specified during keystore generation keystore_file is the source keystore file, for example, /opt/samserver.keystore password is the keystore password certificate_file is the name of the generated certificate file 2. Go to Step 8. Generate a certificate signing request, or CSR. 1. Enter the following: # keytool -certreq -alias alias -keystore keystore_file -file CSR_file -storetype JKS where alias is a case-insensitive alias that is required for subsequent keytool operations keystore_file is the keystore file generated in Step 3 CSR_file is the name of the generated CSR file The following prompt is displayed: Enter keystore password: 2. Enter the keystore password. The following prompt is displayed: Enter key password for <alias> 3. Enter the key password. The utility generates the CSR file. Send the CSR file to a CA for authentication. The CA returns a certificate file that contains a trusted root certificate in a hierarchical certificate chain. 72 3HE AAAG-TQZZA

73 5620 SAM 5650 CPAM To prepare a 5620 SAM system for SSL 8 Enter the following to import the certificate to a truststore file: Note: If the certificate is signed by a CA, you must import the entire CA chain of certificates to the truststore file; see the CA documentation for information about importing trusted certificates. # keytool -import -trustcacerts -alias alias -file certificate_file -keystore truststore_file -storepass password where alias is the keystore alias certificate_file is the self-signed or CA certificate file truststore_file is the truststore file to which you want to import the certificate password is the truststore password 9 If the security certificate is signed by a CA, enter the following to import the certificate from the certificate file to a keystore file: Note: You must import the entire CA chain of certificates into the keystore file; see the CA documentation for information about importing trusted certificates. # keytool -import -trustcacerts -alias alias -file certificate_file -keystore keystore_file -storepass password where alias is the keystore alias certificate_file is the CA certificate file keystore_file is the keystore file to which you want to import the certificate password is the truststore password 10 Copy the keystore and truststore files to each main server in the 5620 SAM system. Note: The keystore file must be in the same location on each main server station, for example, /opt. 11 Copy the keystore file to each auxiliary server station in the 5620 SAM system. Note: The keystore file location on each auxiliary server station must match the keystore file location on each main server station, for example, /opt. END OF STEPS 3HE AAAG-TQZZA 73

74 To enable SSL on a main server 5620 SAM 5650 CPAM 6.5 To enable SSL on a main server Description The following steps describe how to enable SSL on a 5620 SAM main server for communication with other 5620 SAM components. CAUTION Steps Service Disruption Configuring SSL on a 5620 SAM main server requires a main server shutdown and causes a temporary network management outage. Ensure that you perform the procedure only during a scheduled maintenance period. Note: You must perform this procedure on each main server in a redundant 5620 SAM deployment; see 6.3 SSL configuration workflow (p. 69) for information about the order in which the main servers must be configured. Note: You require the following user privileges: root samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 1 Stop the main server. 1. Log in to the main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following: bash$./nmsserver.bash stop 5. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 6. The 5620 SAM main server is stopped when the command displays the following status message: 74 3HE AAAG-TQZZA

75 5620 SAM 5650 CPAM To enable SSL on a main server Application Server is stopped If the command displays a different message, wait five minutes and repeat Step 1 5. Do not proceed until the server is stopped Enter the following to switch to the root user: bash$ su - Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure ssl secure SSL is enabled, and the prompt changes to <main configure ssl>. Configure each parameter in the following table. Table 29 Main server ssl parameters Parameter keystore-file keystore-pass truststore-file truststore-pass Description The absolute path of the SSL keystore file The SSL keystore password The absolute path of the SSL truststore file The SSL truststore password 6 To enable WebDAV access to enodeb activation data on the main server, enter the following: Note: If you intend to manage Small Cell NEs, you must enable WebDAV access. <main configure ssl> webdav WebDAV access is enabled. 7 Enter the following: 3HE AAAG-TQZZA 75

76 To enable SSL on a main server 5620 SAM 5650 CPAM <main configure ssl> back The prompt changes to <main configure> Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. If the configuration is correct, enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. Enter the following to switch back to the samadmin user: # exit 12 Start the main server. 1. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 2. Enter the following: bash$./nmsserver.bash start 3. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. 76 3HE AAAG-TQZZA

77 5620 SAM 5650 CPAM To enable SSL on an auxiliary server If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns one of the following lines of output: on a standalone main server: -- SAM Server is Up on a primary main server: -- Primary Server is UP on a standby main server: -- Standby Server is UP 4. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Close the console window. END OF STEPS 6.6 To enable SSL on an auxiliary server Description The following steps describe how to enable SSL on a 5620 SAM auxiliary server for communication with other 5620 SAM components Steps Note: You require the following user privileges: root samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 1 Stop the auxiliary server. 1. Log in to the auxiliary server station as the root user. 2. Open a console window. 3. Enter the following to switch to the samadmin user: # su - samadmin 3HE AAAG-TQZZA 77

78 To enable SSL on an auxiliary server 5620 SAM 5650 CPAM 4. Enter the following: bash$ cd /opt/5620sam/auxserver/nms/bin 5. Enter the following to stop the auxiliary server: bash$./auxnmsserver.bash auxstop 6. Enter the following to display the auxiliary server status: bash$./auxnmsserver.bash auxappserver_status The command displays a status message. 7. The server is stopped when the command displays the following status message: Auxiliary Server is stopped If the command displays a different message, wait five minutes and return to Step 1 6. Do not proceed until the auxiliary server is stopped Enter the following to switch to the root user: bash$ su - Enter the following: # samconfig -m aux The following is displayed: Start processing command line inputs... <aux> Enter the following: <aux> configure ssl secure SSL is enabled, and the prompt changes to <aux configure ssl>. Configure the parameters in the following table. Table 30 Auxiliary server ssl parameters Parameter keystore-file keystore-pass Description The absolute path of the SSL keystore file The SSL keystore password 6 Enter the following: 78 3HE AAAG-TQZZA

79 5620 SAM 5650 CPAM To enable SSL on an auxiliary server <aux configure ssl> back The prompt changes to <aux configure> Verify the auxiliary server configuration. 1. Enter the following: <aux configure> show-detail The auxiliary server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required. 4. When you are certain that the configuration is correct, enter the following: <aux configure> back The prompt changes to <aux>. If the configuration is correct, enter the following: <aux> apply The configuration is applied. Enter the following: <aux> exit The samconfig utility closes. Enter the following to switch back to the samadmin user: # exit Enter the following to start the auxiliary server: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The auxiliary server starts. Close the console window. END OF STEPS 3HE AAAG-TQZZA 79

80 To enable SSL and HTTPS on a Cflowd auxiliary server 5620 SAM 5650 CPAM 6.7 To enable SSL and HTTPS on a Cflowd auxiliary server Description Steps The following steps describe how to enable SSL and HTTPS on a 5620 SAM Cflowd auxiliary server for secure communication with one or more 5620 SAM main servers and web UI clients. Note: You require root user privileges on the Cflowd auxiliary server station. Note: Command lines use the # symbol to represent the RHEL CLI prompt for the root user. Do not type the leading # symbol when you enter a command Ensure that SSL is enabled on each main server in the 5620 SAM system. Copy the trusted root certificate file from the main server station to the Cflowd auxiliary server station. Use an SSL utility to import the SSL certificate from the certificate file to an SSL truststore file on the Cflowd auxiliary server station. Log in to the Cflowd auxiliary server station as the root user. Open a console window. Enter the following: # cd /opt/5620sam/dcp/bin 7 Enable SSL for communication with the 5620 SAM. 1. Create a backup copy of the dcpctl.sh file and store it in a secure location. 2. Open the dcpctl.sh file using a plain-text editor such as vi. 3. Locate the section that begins with the following line: # SSL configuration 4. Locate the following line in the section: 80 3HE AAAG-TQZZA

81 5620 SAM 5650 CPAM To enable SSL and HTTPS on a Cflowd auxiliary server 8 # J_OPTS_SSL="-Djavax.net.ssl.trustStore=<absolute path of the trust store file>" 5. Remove the leading # symbol. 6. Replace <absolute path of the trust store file> with the absolute path of the truststore file. 7. Save and close the dcpctl.sh file. Enable SSL for communication with web UI clients. 1. Enter the following: # cd /opt/5620sam/jboss-6.4.0/standalone/configuration 2. Create a backup copy of the standalone-5620dcp.xml file and store it in a secure location. 3. Open the standalone-5620dcp.xml file using a plain-text editor such as vi. 4. Locate the following section: <!-- comment the following line when using SSL --> <connector name="http" protocol="http/1.1" scheme="http" socket-binding="http"/> 5. Move the --> to a new line at the section end so that the section reads as follows: <!-- comment the following line when using SSL <connector name="http" protocol="http/1.1" scheme="http" socket-binding="http"/> --> 6. Locate the following section: <!-- uncomment the following lines when using SSL and update password and absolute_path_of_the_cert_key_file as required <connector name="https" scheme="https" protocol="http/1.1" socket-binding="https" enable-lookups="false" secure="true"> <ssl name="https" password="password" protocol="tlsv1,tlsv1.1, TLSv1.2" certificate-key-file="absolute_path_of_the_cert_key_ file"/> </connector> --> 7. Replace absolute_path_of_the_cert_key_file with the absolute path and name of the truststore file. 8. Replace the word password inside the quotation marks with the truststore password. 9. Move the --> line from the end of the section to a new line after the first line; the section now reads as follows: <!-- uncomment the following lines when using SSL and update password and absolute_path_of_the_cert_key_file as required --> 3HE AAAG-TQZZA 81

82 To enable or disable SSL and HTTPS on an analytics server 5620 SAM 5650 CPAM <connector name="https" scheme="https" protocol="http/1.1" socket-binding="https" enable-lookups="false" secure="true"> <ssl name="https" password="password" protocol="tlsv1,tlsv1.1, TLSv1.2" certificate-key-file="keystore_file"/> </connector> where password is the keystore password keystore_file is the absolute file path and name of the SSL truststore file 10. Save and close the standalone-5620dcp.xml file Enter the following: # cd /opt/5620sam/dcp/bin Restart the Cflowd auxiliary server. 1. Enter the following: #./dcpctl.sh stop The following messages are displayed as the Cflowd auxiliary server stops. Stopping 5620 SAM Cflowd Auxiliary Server SAM Cflowd Auxiliary Server is stopped successfully 2. Enter the following: #./dcpctl.sh start The following and status messages are displayed as the Cflowd auxiliary server starts: Starting 5620 SAM Cflowd Auxiliary Server... Data Category: category The Cflowd auxiliary server is started when the following is displayed: 5620 SAM Cflowd Auxiliary Server is started successfully Configure the Cflowd auxiliary server to use HTTPS and SFTP for communication with the main servers, as described in 8.12 To configure Cflowd auxiliary server communication (p. 194). END OF STEPS 6.8 To enable or disable SSL and HTTPS on an analytics server Description The following steps describe how to enable or disable SSL and HTTPS on a 5620 SAM analytics server for secure communication with the main servers and clients. 82 3HE AAAG-TQZZA

83 5620 SAM 5650 CPAM To enable or disable SSL and HTTPS on an analytics server Steps Note: You require root user privileges on the analytics server station. Note: Command lines use the # symbol to represent the RHEL CLI prompt for the root user. Do not type the leading # symbol when you enter a command Log in to the analytics server station as the samadmin user. Open a console window. Enter the following: bash$ cd /opt/5620sam/analytics/bin If you need to disable SSL and HTTPS on the analytics server, go to Step 13. Enabling SSL Ensure that SSL is enabled on each main server in the 5620 SAM system. Copy the SSL certificate file from the main server station to the analytics server station. Enter the following: bash$./analyticsadmin.sh ssl add The script displays the following messages and prompt: Copyright Nokia Inc. All rights reserved This Action requires 5620 SAM Analytic Server Restart. Please type 'YES' to continue Enter YES. The script displays the following messages and prompt: Stopping 5620 SAM Analytics Application Stopping Tomcat Service 3HE AAAG-TQZZA 83

84 To enable or disable SSL and HTTPS on an analytics server 5620 SAM 5650 CPAM Using CATALINA_BASE: /opt/5620sam/tomcat Using CATALINA_HOME: /opt/5620sam/tomcat Using CATALINA_TMPDIR: /opt/5620sam/tomcat/temp Using JRE_HOME: /opt/5620sam/samjre/amd64 Using CLASSPATH: /opt/5620sam/tomcat/bin/bootstrap.jar: /opt/5620sam/tomcat/bin/tomcat-juli.jar Enter SSL Certificate Path: Enter the absolute file path of the SSL certificate file. The script displays the following messages and prompt: /path/certificate_file found. Enter SSL Certificate Password: Enter the SSL certificate password. Messages like the following are displayed as the configuration is applied and the analytics server starts. SSL Config has been updated 5620 SAM Analytic Server SSL configuration has been added Starting 5620 SAM Analytics Application 5620 SAM Analytics Server successfully started! If you are using a self-signed SSL certificate, perform the following steps to add a browser security exception for the main server and the analytics server, in sequence. 1. Use a web browser to open the following URL: where address is the 5620 SAM main server hostname or IP address A security warning page opens and displays information about the self-signed SSL certificate, which is untrusted. 2. Add a security exception. Depending on the browser type and version, you may be able to click a Continue button that adds the security exception automatically, or you may have to configure an advanced setting to add the exception. The browser adds the exception, but access to the Analytics application remains blocked until you perform the following steps. 3. Use a web browser to open the following URL: where address is the analytics server hostname or IP address 84 3HE AAAG-TQZZA

85 5620 SAM 5650 CPAM To enable or disable SSL and HTTPS on an analytics server A security warning page opens and displays information about the self-signed SSL certificate, which is untrusted. 4. Add a security exception. Depending on the browser type and version, you may be able to click a Continue button that adds the security exception automatically, or you may have to configure an advanced setting to add the exception. The browser adds the exception, and access is granted in subsequent connection attempts to the Analytics application. 5. Close the web browser. 12 Go to Step 14. Disabling SSL 13 To disable SSL and HTTPS on the analytics server station, perform the following steps. 1. Enter the following: bash$./analyticsadmin.sh ssl remove The script displays the following messages and prompt: Copyright Nokia Inc. All rights reserved This Action requires 5620 SAM Analytic Server Restart. Please type 'YES' to continue 2. Enter YES. The script displays messages like the following as it stops the analytics server, removes the SSL configuration, and starts the analytics server: Stopping 5620 SAM Analytics Application Stopping Tomcat Service Using CATALINA_BASE: /opt/5620sam/tomcat Using CATALINA_HOME: /opt/5620sam/tomcat Using CATALINA_TMPDIR: /opt/5620sam/tomcat/temp Using JRE_HOME: /opt/5620sam/samjre/amd64 Using CLASSPATH: /opt/5620sam/tomcat/bin/bootstrap.jar: /opt/5620sam/tomcat/bin/tomcat-juli.jar 5620 SAM Analytic Server SSL configuration has been removed Starting 5620 SAM Analytics Application 5620 SAM Analytics Server successfully started! 3HE AAAG-TQZZA 85

86 To enable SSL and HTTPS for an OSS client 5620 SAM 5650 CPAM 14 Close the console window.. END OF STEPS 6.9 To enable SSL and HTTPS for an OSS client Description The following steps describe how to enable SSL and HTTPS on an OSS client for secure communication with one or more 5620 SAM main servers Steps Ensure that SSL is enabled on each main server in the 5620 SAM system. Ensure that the trusted root certificates from the main server station are copied to the OSS client station, as described in 6.4 To prepare a 5620 SAM system for SSL (p. 71). Use an SSL utility to import the SSL certificate from the certificate file to an SSL truststore file on the OSS client station. Modify the URL that each OSS application on the station uses to reach the main server. 1. Change http: to 2. Change the port value in the URL from 8080 to END OF STEPS 6.10 To enable SSL on a RHEL client delegate server Description The following steps describe how to enable SSL on a RHEL client delegate server Steps 1 Log in to the client delegate server station as the root user 86 3HE AAAG-TQZZA

87 5620 SAM 5650 CPAM To enable SSL on a RHEL client delegate server Close each local and remote GUI client session on the station. Open a console window. Enter the following: # samconfig -m clientdelegate The samconfig utility opens, and the following is displayed: Start processing command line inputs... <clientdelegate> Enter the following: <clientdelegate> configure ssl-secure SSL is enabled, and the prompt changes to <clientdelegate configure>. Enter the following: <clientdelegate configure> back The prompt changes to <clientdelegate>. Enter the following: <clientdelegate> apply The configuration is applied. Enter the following: <clientdelegate> exit The configuration is saved, and the samconfig utility closes. Open the local GUI client and a remote client session to verify that the client delegate server and main servers can communicate. END OF STEPS 3HE AAAG-TQZZA 87

88 To disable SSL on a single-user GUI client 5620 SAM 5650 CPAM 6.11 To disable SSL on a single-user GUI client Description Steps Perform this procedure when SSL is no longer enabled on a main server and you need to disable SSL on a single-user GUI client that connects to the main server. Note: If you are not the original installer of the client software, you require the following user privileges on the client station: Mac OS X, Microsoft Windows local administrator RHEL root Close the client GUI if it is open. Uninstall the client software; perform the appropriate procedure in Chapter 13, Single-user client deployment. Install the client software; perform the appropriate procedure in Chapter 13, Single-user client deployment. The 5620 SAM client GUI opens with SSL disabled, the client configuration is updated, and the login form opens. Log in to verify the client operation. END OF STEPS 6.12 To disable SSL on a RHEL client delegate server Description Perform this procedure when SSL is no longer enabled on a main server and you need to disable SSL on a RHEL client delegate server Steps 1 Log in to the client delegate server station as the root user 88 3HE AAAG-TQZZA

89 5620 SAM 5650 CPAM To disable SSL on a RHEL client delegate server Close each local and remote GUI client session on the station. Open a console window. Enter the following: # samconfig -m clientdelegate The samconfig utility opens, and the following is displayed: Start processing command line inputs... <clientdelegate> Enter the following: <clientdelegate> configure ssl-secure SSL is disabled, and the prompt changes to <clientdelegate configure>. Enter the following: <clientdelegate configure> back The prompt changes to <clientdelegate>. Enter the following: <clientdelegate> apply The configuration is applied. Enter the following: <clientdelegate> exit The configuration is saved, and the samconfig utility closes. Open the local GUI client and a remote client session to verify that the client delegate server and main servers can communicate. END OF STEPS 3HE AAAG-TQZZA 89

90 To disable SSL on a Windows client delegate server 5620 SAM 5650 CPAM 6.13 To disable SSL on a Windows client delegate server Description Steps Perform this procedure when SSL is no longer enabled on a main server and you need to disable SSL on a Windows client delegate server that connects to the main server Log in to the station as the user who installed the client software, or as a local administrator. Close each single-user client and remote client session on the station. If the client delegate server was installed using the GUI-based 5620 SAM installer, go to Step 7. Uninstall the single-user client or client delegate server software by performing the appropriate procedure in Chapter 14, Client delegate server deployment. Install the single-user client or client delegate server software by performing the appropriate procedure in Chapter 14, Client delegate server deployment. SSL is disabled. Go to Step 18. Navigate to the directory that contains the 5620 SAM installation software. Double-click on the ClientInstall_SAM R_r_revision.exe file where R_r is the release identifier, in the form MAJOR_minor revision is the revision identifier, such as R1, R3, or another descriptor The 5620 SAM client configuration utility opens. Click Next. The Software License Agreement panel is displayed 90 3HE AAAG-TQZZA

91 5620 SAM 5650 CPAM To disable SSL on a Windows client delegate server 10 Select I accept the terms of the license agreement, and then click Next. The Choose Installation Type panel Perform one of the following. a. Choose Client Installation and Configuration, if you are configuring a single-user client. b. Choose Client Delegate Installation and Configuration, if you are configuring a client delegate server. Click Next. Click Next in each subsequent panel until the Main Server Configuration panel is displayed. Deselect the Enable Secure Communication parameter. Click Install. The reconfiguration begins. When the Installation Complete panel is displayed, select the Start the 5620 SAM Client parameter. Click Done to close the utility. The 5620 SAM client GUI opens with SSL disabled, the client configuration is updated, and the login form opens. Log in to verify the client operation. END OF STEPS 3HE AAAG-TQZZA 91

92 To disable SSL on a Windows client delegate server 5620 SAM 5650 CPAM 92 3HE AAAG-TQZZA

93 5620 SAM 5650 CPAM Configuring Small Cell management 7 Configuring Small Cell management 7.1 Overview Purpose This chapter describes how to configure and enable Small Cell management in a 5620 SAM system Contents 7.1 Overview Introduction To enable Small Cell management Introduction General information You must perform 7.3 To enable Small Cell management (p. 94) to enable 5620 SAM management of the following classes of Small Cell NEs: Small Cell access point all 3G and 4G variants Small Cell Gateway all multi-standard variants See Solution support information in the 5620 SAM Small Cells User Guide for specific devicesupport information. You can choose to perform the configuration at the following times: after a 5620 SAM installation or upgrade, before the standalone or primary main server and the auxiliary servers start when the 5620 SAM system is fully initialized after an installation or upgrade Note: Before you attempt to configure Small Cell management, you must ensure that the ACL flag is enabled on the /smallcell partition, as described in 5.3 To configure a 5620 SAM disk partition created after the RHEL OS installation (p. 52) Migration from SCMS If you plan to migrate from SCMS to 5620 SAM Small Cell management, you must first perform 7.3 To enable Small Cell management (p. 94) to configure the 5620 SAM for Small Cell management; the SCMS and 5620 SAM must share an HDM instance during the migration. See the 5620 SAM SCMS Migration Guide for information about migrating from SCMS to 5620 SAM Small Cell management. 3HE AAAG-TQZZA 93

94 To enable Small Cell management 5620 SAM 5650 CPAM HDM installation and configuration HDM installation and configuration operations are independent of 5620 SAM installation and upgrade activity. After a 5620 SAM system upgrade, however, you must apply the HDM Adaptation Kit from the new 5620 SAM software package to the HDM. See the 5620 SAM Release Notice for information about about the HDM Adaptation Kit for the release, and the 5620 SAM HDM Adaptation Kit User Guide for installation information. See the HDM documentation in the Documentation Center for HDM installation and configuration information. Note: You may need to change the HDM version after a 5620 SAM system installation or upgrade. See HDM configuration in the 5620 SAM Small Cells User Guide for information about configuring an HDM in the 5620 SAM, including connecting the 5620 SAM to an HDM of a different version. Note: After an HDM installation or upgrade, the HDM application server requires tuning based on the recommendations in the Home Device Manager Best Practices Guide. To facilitate HDM and 5620 SAM communication, you must ensure that the net.ipv4.tcp_tw_reuse parameter is set to the value recommended in the Home Device Manager Best Practices Guide. 7.3 To enable Small Cell management Description The following steps describe how to enable and configure the 5620 SAM management of Small Cell NEs. CAUTION Service Disruption This procedure potentially involves a restart of each main server and auxiliary server in a 5620 SAM system, which is service-affecting. Ensure that you perform this procedure only during a scheduled maintenance period. Note: You must perform this procedure on each main and auxiliary server in the 5620 SAM system. Note: Command lines use the following as the CLI prompts: # root user prompt $ fgwuser and ftpuser prompts bash$ samadmin user prompt Do not type the leading # symbol, $ symbol, or bash$ when you enter a command. 94 3HE AAAG-TQZZA

95 5620 SAM 5650 CPAM To enable Small Cell management Steps Log in to the main or auxiliary server as the root user. Open a console window. Perform one of the following. a. On a main server, enter the following: # cd /opt/5620sam/server/nms/config/femto/fsconf b. On an auxiliary server, enter the following: # cd /opt/5620sam/auxserver/nms/config/femto/fsconf If this is the first time that Small Cell management is being configured on the station, go to Step 6. Perform one of the following. a. If you are upgrading the server, perform the following steps. 1. Enter the following: #./fsconf.sh upgrade The script displays messages like the following, and then exits: [ timestamp ]:SAM File Server Upgrading(sam-fileserver-n. n-linux64) [ timestamp ]:updating nms-femto.xml file 2. Go to Step 49 b. If you are replacing a previous Small Cell configuration, for example, after a server uninstallation and re-installation, perform the following steps. 1. Enter the following: #./fsconf.sh uninstall The script displays configuration messages and the following prompt: Are you sure to uninstall SAM File Server(sam-fileserver-n. n-linux64)[yes/no]? 2. Enter yes. The script removes the Small Cell configuration and exits. 3HE AAAG-TQZZA 95

96 To enable Small Cell management 5620 SAM 5650 CPAM Configure SFTP parameters Enter the following: #./fsconf.sh install The script displays configuration messages, and then the following prompt: Install Complete SAM File Server(sam-fileserver-n.n-linux64)(Main+Aux) [yes/no]? Perform one of the following. a. If the 5620 SAM system does not include an auxiliary server, enter the following to install all management components on the main server station: yes b. If the 5620 SAM system includes one or more auxiliary servers, perform the following steps. 1. Enter the following to install only one management component on the station that you are configuring: no The script displays configuration messages, and then the following prompt: Choose SAM File Server type [1 Main/ 2 Aux]? 2. Enter one of the following, depending on the type of server that you are configuring: main server: 1 auxiliary server: 2 The script displays configuration messages, and then the following prompt: Do you have a dedicated interface for smallcell access?[yes/no] Perform one of the following. a. Enter no if the main or auxiliary server has no dedicated interface for Small Cell management. b. Enter yes if the main or auxiliary server has more than one physical network management interface, and one of the interfaces is dedicated to Small Cell NE management. The script displays configuration messages and then exits. The script creates the /smallcell directory and subdirectories, and the following user accounts and groups: fgwuser ftpuser 96 3HE AAAG-TQZZA

97 5620 SAM 5650 CPAM To enable Small Cell management 9 If you answer yes in Step 8, perform the following steps to configure an SSH instance for the dedicated interface. 1. Enter the following: #./femtointerfacehardening.sh The script displays the following prompt: Do you want to configure security hardening feature on this server?[yes/no] 2. Enter yes. The script displays configuration messages, and then the following prompt: Enter the IP over which Femto interacts with SAM: 3. Enter the IPv4 address of the dedicated 5620 SAM management interface. Note: If the Small Cell NEs use IPv4 and IPv6 to communicate over the dedicated interface, the script configures the IPv6 SSH instance automatically. The script displays configuration messages and then exits. Configure SSH for Small Cell file transfers by ftpuser user Enter the following to switch to the ftpuser user: # su - ftpuser Enter the following: $ cd.ssh Record the public encryption key value from the /etc/sftpkeys/id_dsa.pub file on a Small Cell NE. You must paste the value in a subsequent step. Perform one of the following. a. If you enter yes in Step 8 to specify a dedicated 5620 SAM management interface, perform the following steps. 1. Using a plain-text editor such as vi, create a file named alt_authorized_keys. 2. Paste the recorded value from Step 12 into the file. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the alt_authorized_keys file. 4. Enter the following: $ chmod 755 alt_authorized_keys 3HE AAAG-TQZZA 97

98 To enable Small Cell management 5620 SAM 5650 CPAM b. If you enter no in Step 8 to specify the default 5620 SAM management interface, perform the following steps. 1. Using a plain-text editor such as vi, create a file named authorized_keys. 2. Paste the recorded value from Step 12 into the file. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the authorized_keys file. 4. Enter the following: $ chmod 755 authorized_keys Enter the following: $ cd.. Enter the following: $ chmod 755.ssh Enter the following to switch back to the root user: $ exit Enable bulk file transfers for ftpuser user Create a backup copy of the /etc/security/limits.conf file. Open the /etc/security/limits.conf file using a plain-text editor such as vi. Add the following lines to the end of the file: ftpuser soft nofile 4096 ftpuser soft nproc 5000 Save and close the /etc/security/limits.conf file. Enter the following to switch to the ftpuser user: # su - ftpuser 98 3HE AAAG-TQZZA

99 5620 SAM 5650 CPAM To enable Small Cell management Verify the configuration update. 1. Enter the following: $ ulimit -a 2. Ensure that the output includes the following lines: open files (-n) 4096 max user processes (-u) 5000 Enter the following to switch back to the root user: $ exit Generate SSH key for samadmin user Enter the following to switch to the samadmin user: # su - samadmin Enter the following to run the SSH key-generation utility: bash$ ssh-keygen -t rsa The script displays the following prompt on a main server: Enter file in which to save the key (/opt/5620sam/server/.ssh/id_rsa): The script displays the following prompt on an auxiliary server: Enter file in which to save the key (/opt/5620sam/auxserver/.ssh/id_ rsa): Press to accept the default value. The script displays the following prompt: Enter passphrase (empty for no passphrase): Enter a passphrase. The script displays the following prompt: Enter same passphrase again: The utility displays the key fingerprint and randomart image, and then exits. 3HE AAAG-TQZZA 99

100 To enable Small Cell management 5620 SAM 5650 CPAM Propagate SSH key of FGW admin user to samadmin user Enter the following: bash$ cd.ssh Record the SSH public encryption key value from the /home/admin/.ssh/id_rsa.pub file on the FGW. You must paste the value in a subsequent step. Perform one of the following. a. If you enter yes in Step 8 to specify a dedicated 5620 SAM management interface, and the FGW is to use the interface, perform the following steps. 1. Using a plain-text editor such as vi, create a file named alt_authorized_keys. 2. Paste the recorded value from Step 29 into the file. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the alt_authorized_keys file. 4. Enter the following: bash$ chmod 755 alt_authorized_keys b. If you enter no in Step 8 to specify the default 5620 SAM management interface, perform the following steps. 1. Using a plain-text editor such as vi, create a file named authorized_keys. 2. Paste the recorded value from Step 29 into the file. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the authorized_keys file. 4. Enter the following: bash$ chmod 755 authorized_keys Enter the following: bash$ cd.. Enter the following: bash$ chmod 755.ssh Enter the following to switch back to the root user: bash$ exit 100 3HE AAAG-TQZZA

101 5620 SAM 5650 CPAM To enable Small Cell management Propagate SSH keys for FGW file transfers by fgwuser user If you are configuring an auxiliary server, go to Step 49. Enter the following to switch to the fgwuser user: # su - fgwuser Enter the following: $ cd.ssh Record the SSH public encryption key value from the /root/.ssh/id_rsa.pub file on the FGW. You must paste the value in a subsequent step. Perform one of the following. a. If you enter yes in Step 8 to specify a dedicated 5620 SAM management interface, and the FGW is to use the interface, perform the following steps. 1. Using a plain-text editor such as vi, create a file named alt_authorized_keys. 2. Paste the recorded value from Step 37 into the file. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the alt_authorized_keys file. 4. Enter the following: $ chmod 755 alt_authorized_keys b. If you enter no in Step 8 to specify the default 5620 SAM management interface, perform the following steps. 1. Using a plain-text editor such as vi, create a file named authorized_keys. 2. Paste the recorded value from Step 37 into the file. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the authorized_keys file. 4. Enter the following: $ chmod 755 authorized_keys Enter the following: $ cd.. 3HE AAAG-TQZZA 101

102 To enable Small Cell management 5620 SAM 5650 CPAM Enter the following: $ chmod 755.ssh Enter the following to switch back to the root user: $ exit Propagate SSH keys for FGW file transfers by ftpuser user Enter the following to switch to the ftpuser user: # su - ftpuser Enter the following: $ cd.ssh Record the SSH public encryption key value from the /root/.ssh/id_rsa.pub file on the FGW. You must paste the value in a subsequent step. Perform one of the following. a. If you enter yes in Step 8 to specify a dedicated 5620 SAM management interface, and the FGW is to use the interface, perform the following steps. 1. Using a plain-text editor such as vi, open the alt_authorized_keys file. 2. Paste the recorded value from Step 44 on a new line. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the alt_authorized_keys file. 4. Enter the following: $ chmod 755 alt_authorized_keys b. If you enter no in Step 8 to specify the default 5620 SAM management interface, perform the following steps. 1. Using a plain-text editor such as vi, open the authorized_keys file. 2. Paste the recorded value from Step 44 on a new line. Note: Ensure that you remove all line breaks from the pasted text. 3. Save and close the authorized_keys file. 4. Enter the following: $ chmod 755 authorized_keys 102 3HE AAAG-TQZZA

103 5620 SAM 5650 CPAM To enable Small Cell management Enter the following: $ cd.. Enter the following: $ chmod 755.ssh Enter the following to switch back to the root user: $ exit Complete deployment procedure, if required 49 If you are performing this procedure as part of a 5620 SAM system installation, upgrade, or conversion to redundancy procedure in Chapter 8, 5620 SAM installation, Chapter 9, 5620 SAM upgrade, or Chapter 10, 5620 SAM conversion to redundancy, perform the following steps. 1. Return to the installation, upgrade, or conversion procedure and complete the procedure steps. 2. Perform one of the following when the 5620 SAM system initialization is complete. If you are upgrading from 5620 SAM Release 14.0 R4 or earlier, go to Step 52 when the 5620 SAM system is fully initialized. If you are upgrading from 5620 SAM Release 14.0 R5 or later, go to Step 53 when the 5620 SAM system is fully initialized. Restart main or auxiliary server Enter the following to switch to the samadmin user: # su - samadmin Perform one of the following. a. On a main server, enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash force_restart b. On an auxiliary server, enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxforce_ restart The main or auxiliary server restarts. 3HE AAAG-TQZZA 103

104 To enable Small Cell management 5620 SAM 5650 CPAM Specify server interfaces 52 Perform the following steps. Note: You must perform the steps on the first GUI client that opens after the main server starts, and before any FGW or Femto management activity begins. 1. Open a 5620 SAM GUI client. 2. Choose Manage Small Cells Configuration from the 5620 SAM main menu. The Small Cells Configuration form opens. 3. Click on the Small Cells Properties tab. 4. Configure the following parameters; for each parameter, you can specify an IPv4 address, an IPv6 address, or an FQDN, which is recommended: Fileserver Hostname for SC APs address of 5620 SAM server interface for Femto interaction with server file system SC GW OAM link IP Address address of 5620 SAM server interface that is to receive FGW traps Note: If the 5620 SAM system is redundant, you must specify an SC GW OAM link IP Address for each main server in the system. 5. Click OK. 6. Click Yes to confirm the action. The Small Cells Configuration form closes. After you configure the SC GW OAM link IP address, the 5620 SAM sends an SNMP SetRequest message to the SC GW to set the value of one of the following parameters, depending on the SC GW NE release: ipaddressfmsremote (LR15.1 and LR16.1 SC NEs) SpareParameter5 (LR14.2 SC NEs) Note: The SC GW sets the parameter, but does not send a Response message to indicate the outcome of the SetRequest message. As a result, the 5620 SAM retries to set the parameter and a TIMEOUT exception occurs. Configure alarm clearing 53 Perform the following steps. 1. Choose Administration Alarm Settings from the 5620 SAM main menu. The Alarm Settings form opens. 2. Click on the General tab. The 5620 SAM alarm settings are displayed. 3. Select the check box for the Allow Manual Clearing of Automatically Clearing (Self Clearing) Alarms parameter. 4. Save your changes and close the form HE AAAG-TQZZA

105 5620 SAM 5650 CPAM To enable Small Cell management Add dedicated management interface to 5620 SAM system 54 If you enter yes in Step 8 to specify a dedicated 5620 SAM management interface, use a 5620 SAM client GUI to perform the following procedures in the 5620 SAM User Guide, as required: To configure an additional management interface on a main server To configure an additional management interface on an auxiliary server END OF STEPS 3HE AAAG-TQZZA 105

106 To enable Small Cell management 5620 SAM 5650 CPAM 106 3HE AAAG-TQZZA

107 5620 SAM 5650 CPAM Part II: 5620 SAM system deployment Overview Purpose Contents This part describes 5620 SAM system installation, upgrade, conversion to redundancy, and conversion from IPv4 inter-component communication to IPv6. Chapter 8, 5620 SAM installation 109 Chapter 9, 5620 SAM upgrade 219 Chapter 10, 5620 SAM conversion to redundancy 301 Chapter 11, 5620 SAM conversion to IPv6 335 Chapter 12, 5620 SAM uninstallation 379 3HE AAAG-TQZZA 107

108 5620 SAM 5650 CPAM 108 3HE AAAG-TQZZA

109 5620 SAM 5650 CPAM 5620 SAM installation SAM installation 8.1 Overview Purpose This chapter describes how to install and enable the components of a standalone or redundant 5620 SAM system Contents 8.1 Overview 109 Introduction General information 111 Standalone 5620 SAM system installation Standalone system installation workflow To install a standalone 5620 SAM system 114 Redundant 5620 SAM system installation Redundant system installation workflow To install a redundant 5620 SAM system 135 Auxiliary server installation Auxiliary server installation workflow To install a 5620 SAM auxiliary server To add auxiliary servers to a 5620 SAM system 184 Cflowd auxiliary server installation Cflowd auxiliary server installation workflow To install a 5620 SAM Cflowd auxiliary server To configure Cflowd auxiliary server communication 194 Auxiliary database installation Auxiliary database installation workflow To prepare a station for auxiliary database installation To install the auxiliary database software To add an auxiliary database to a 5620 SAM system 203 3HE AAAG-TQZZA 109

110 Overview 5620 SAM 5650 CPAM 8.17 To add a station to an auxiliary database 205 Analytics server installation To install and enable a 5620 SAM analytics server HE AAAG-TQZZA

111 5620 SAM 5650 CPAM General information Introduction 8.2 General information Description CAUTION Support Liability Failure to follow the requirements and restrictions that apply to 5620 SAM system deployment may violate a support agreement SAM software deployment is supported only under the conditions described in Chapter 2, Before you begin. This chapter describes standalone and redundant 5620 SAM system installation, including the installation of the following optional 5620 SAM components: auxiliary server Cflowd auxiliary server auxiliary database analytics server Chapter 13, Single-user client deployment and Chapter 14, Client delegate server deployment describe single-user GUI client and client delegate server installation. Most 5620 SAM component configuration is performed using the samconfig utility. See Chapter 3, Using samconfig for information about using the samconfig utility. Table SAM installation procedures Procedure Purpose 8.4 To install a standalone 5620 SAM system (p. 114) Install the database and server software in a standalone deployment on one or more stations. 8.6 To install a redundant 5620 SAM system (p. 135) Install the database and server software in a redundant deployment. 8.8 To install a 5620 SAM auxiliary server (p. 177) Install the auxiliary server software on a station. 8.9 To add auxiliary servers to a 5620 SAM system (p. 184) 8.11 To install a 5620 SAM Cflowd auxiliary server (p. 191) 8.12 To configure Cflowd auxiliary server communication (p. 194) Add an auxiliary server to an existing 5620 SAM system. Install the Cflowd auxiliary server software on a station. Configure a Cflowd auxiliary server to communicate with 5620 SAM servers and NEs To install the auxiliary database software (p. 201) Install the auxiliary database software on a station. 3HE AAAG-TQZZA 111

112 General information 5620 SAM 5650 CPAM Table SAM installation procedures (continued) Procedure 8.16 To add an auxiliary database to a 5620 SAM system (p. 203) 8.18 To install and enable a 5620 SAM analytics server (p. 212) Purpose Enable communication among the auxiliary database stations, and between the stations and other 5620 SAM components. Install the 5620 SAM analytics server software on a station HE AAAG-TQZZA

113 5620 SAM 5650 CPAM Standalone system installation workflow Standalone 5620 SAM system installation 8.3 Standalone system installation workflow Description The following is the sequence of high-level actions required to install a standalone 5620 SAM system Stages Note: The links in the Install standalone core components (p. 113) stages lead to sections in 8.4 To install a standalone 5620 SAM system (p. 114). Install standalone core components 1 Download the required 5620 SAM installation files and distribute the files to the stations in the system, as required; see Download and distribute 5620 SAM installation files (p. 115). 2 Install the standalone database; see Install standalone database (p. 116). 1. Run a script to prepare for the Oracle software installation. 2. Install the database packages. 3. Create the standalone database. 3 Install the standalone main server; see Install standalone main server (p. 122) 1. Install the main server packages. 2. Create and apply the main server configuration Configure additional main server objects and functions, as required; see Prepare standalone main server for initialization (p. 131). Start the main server; see Start standalone main server (p. 131). Install one or more 5620 SAM single-user GUI clients or client delegate servers; see Install GUI clients (p. 132). 3HE AAAG-TQZZA 113

114 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM Install optional components Install and enable one or more auxiliary servers, if required; see Auxiliary server installation (p. 177). Install and enable one or more Cflowd auxiliary servers, if required; see Cflowd auxiliary server installation (p. 191). Install and enable an auxiliary database, if required; see Auxiliary database installation (p. 198). Install and enable one or more analytics servers, if required; see Analytics server installation (p. 212). 8.4 To install a standalone 5620 SAM system Description The following steps describe how to install a collocated or distributed 5620 SAM database and main server in a standalone configuration. The steps also include information about installing optional 5620 SAM components. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. CAUTION Misconfiguration Risk If the RHEL iptables / ip6tables firewall is enabled on a station, 5620 SAM software installation fails. Before a 5620 SAM system installation, you must ensure that the RHEL iptables / ip6tables firewall on each station is disabled. Note: You require root user privileges on the 5620 SAM database and main server stations. Note: Performing the procedure creates the following user accounts: on the 5620 SAM database station Oracle management on the main server station samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user 114 3HE AAAG-TQZZA

115 5620 SAM 5650 CPAM To install a standalone 5620 SAM system Steps bash$ samadmin user Download and distribute 5620 SAM installation files 1 2 Download the following 5620 SAM installation files: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm samauxserver-sam_r_r_revision-pp.x86_64.rpm, if the system is to include an auxiliary server samclientdelegate-sam_r_r_revision-pp.x86_64.rpm, if the system is to include a client delegate server where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Copy the following files to an empty directory on each main server, database, auxiliary server and client delegate server station: Note: In subsequent steps, the directory is called the 5620 SAM software directory. samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm 3 Perform one of the following. a. In a distributed 5620 SAM system: 1. Copy the following files to the 5620 SAM software directory on the database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh 2. Copy the following file to an empty directory on the main server station: samserver-sam_r_r_revision-pp.x86_64.rpm 3HE AAAG-TQZZA 115

116 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM samneo4j-sam_r_r_revision-pp.x86_64.rpm b. In a collocated 5620 SAM system, copy the following files to the 5620 SAM software directory on the main server and database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm 4 5 If the 5620 SAM system includes one or more auxiliary servers, copy the following file to the 5620 SAM software directory on each auxiliary server station: samauxserver-sam_r_r_revision-pp.x86_64.rpm If the 5620 SAM system includes one or more client delegate servers, copy the following file to the 5620 SAM software directory on each client delegate server station: samclientdelegate-sam_r_r_revision-pp.x86_64.rpm Install standalone database Log in as the root user on the station that is to be the database station. Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 9 Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. Note: If you specify a value other than the default, you must record the value for use when the OracleSw_PreInstall.sh script is run during a software upgrade, or when the Oracle management user information is required by technical support HE AAAG-TQZZA

117 5620 SAM 5650 CPAM To install a standalone 5620 SAM system The following prompt is displayed: This script will prepare the system for a new install/restore of a 5620 SAM Version R.r Rn database. Do you want to continue? [Yes/No]: Enter Yes. The following prompt is displayed: Enter the Oracle dba group name [group]: Enter a group name. Note: To reduce the complexity of subsequent software upgrades and technical support activities, it is recommended that you accept the default. The following messages and prompt are displayed: Creating group group if it does not exist... done Enter the Oracle user name: 12 Enter a username. Note: To reduce the complexity of subsequent software upgrades and technical support activities, it is recommended that you accept the default. The following messages and prompt are displayed: Oracle user [username] new home directory will be [/opt/5620sam/oracle12r1]. Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1.., Checking user username... Adding username... Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Please assign a password to the UNIX user username.. New Password: 3HE AAAG-TQZZA 117

118 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM Enter a password. The following prompt is displayed: Re-enter new Password: Re-enter the password. The following is displayed if the password change is successful: passwd: password successfully changed for username The following message and prompt are displayed: Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... INFO: Completed running Oracle Pre-Install Tasks When the script execution is complete, enter the following to reboot the database station: # init 6 The station reboots. When the reboot is complete, log in as the root user on the station that is to be the 5620 SAM database station. Open a console window HE AAAG-TQZZA

119 5620 SAM 5650 CPAM To install a standalone 5620 SAM system 19 Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Enter the following: # yum install samjre* samconfig* samoracle* samdb* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following: <db> show-detail The database configuration is displayed. To configure one or more parameters, enter the following; otherwise, go to Step 29: <db> configure 3HE AAAG-TQZZA 119

120 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM The prompt changes to <db configure>. 25 As required, configure the general parameters in the following table. Note: The instance parameter is configurable only during database creation. Table 32 Standalone database parameters, general Parameter ip instance Description Database IP address Default: IP address of primary network interface Database instance name, which must: contain 8 or fewer characters consist of ASCII characters only have a letter as the first character Default: samdb1 26 If required, configure one or more passwords parameters in the following table, and then enter back. Note: After you save the configuration, you cannot use samconfig to change a database password; you must use the method described in the 5620 SAM System Administrator Guide. Table 33 Standalone database parameters passwords Parameter user sys Description Database user password Default: available from technical support Oracle SYS user password Default: available from technical support A password must: be between 4 and 30 characters long contain at least three of the following: lower-case alphabetic character upper-case alphabetic character numeric character special character, which is one of the following: # $_ not contain four or more of the same character type in sequence 120 3HE AAAG-TQZZA

121 5620 SAM 5650 CPAM To install a standalone 5620 SAM system not be the same as the user name, or the reverse of the user name not contain a space character 27 If required, enable IP validation to specify the server components that have access to the 5620 SAM database; configure the parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 34 Standalone database parameters ip-validation Parameter main-one remote-servers Description Main-server IP address Configuring the parameter enables IP validation. Default: Comma-separated list of the IP addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers Default: Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to begin the database creation: <db> apply The database creation begins, and messages are displayed as the creation progresses. The following is displayed when the database creation is complete: 3HE AAAG-TQZZA 121

122 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM DONE db configurations updated When the database creation is complete, enter the following: <db> exit The samconfig utility closes. It is recommended that as a security measure, you limit the number of database user login failures that the 5620 SAM allows before the database user account is locked; see 5620 SAM database management procedures in the 5620 SAM System Administrator Guide. Install standalone main server Log in as the root user on the station that is to be the main server station. Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Perform one of the following. a. If the main server and database are on separate stations, enter the following: # yum install samjre* samconfig* samserver* samneo4j* b. If the main server and database are collocated on one station, enter the following: # yum install samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed HE AAAG-TQZZA

123 5620 SAM 5650 CPAM To install a standalone 5620 SAM system Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 37 The initial 5620 SAM server installation on a station creates the samadmin user account and assigns a randomly generated password. If this is the first main, auxiliary, analytics, or client delegate server installation on the station, change the samadmin password. Note: The samadmin password must not contain symbol, or enodeb device management may be compromised. 1. Enter the following: # passwd samadmin The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Confirm Password: 3. Re-enter the password. 4. Record the password and store it in a secure location Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure The prompt changes to <main configure>. Enter the following: 3HE AAAG-TQZZA 123

124 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM <main configure> show-detail The main server configuration is displayed. 41 As required, configure the general parameters in the following table. Table 35 Standalone main server parameters, general Parameter ip domain license Description The main server IP address Default: IP address of primary network interface The 5620 SAM server cluster identifier Default: 5620sam Absolute path of 5620 SAM license zip file You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file, or import a license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. Default: 42 As required, configure the client parameters in the following table, and then enter back. Table 36 Standalone main server parameters client Parameter nat hostname public-ip Description Whether NAT is used between the main server and the GUI clients, OSS clients, and auxiliary servers Default: false The main-server hostname, if the GUI clients, OSS clients, and auxiliary servers are to use a hostname, rather than an IP address, to communicate with the main server You must configure the parameter if the main server is to use multiple interfaces for GUI and OSS client communication. Default: The IP address that the GUI and OSS clients must use to reach the main server The parameter is configurable when the hostname parameter is unconfigured. Default: IP address of primary network interface 124 3HE AAAG-TQZZA

125 5620 SAM 5650 CPAM To install a standalone 5620 SAM system Table 36 Standalone main server parameters client (continued) Parameter jndi-port delegates Description The TCP port on the main server station to use for EJB JNDI messaging to GUI clients It is recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the main server. Default: 1099 A list of the client delegate servers in the 5620 SAM system Use the following list format; a path value is the absolute file path of the client installation location on the client delegate server station: address1;path1,address2;path2...addressn;pathn Note: Before you can install a client delegate server using a browser, the main server configuration must include the client delegate server address and file path. Default: 43 As required, configure the database parameters in the following table, and then enter back. Table 37 Standalone main server parameters database Parameter ip instance user-password backup-dest backup-interval backup-sets Description The IP address that the main server must use to reach the database; mandatory Default: Database instance name Default: samdb1 Database user password Default: available from technical support The backup directory on the database station It is recommended that you specify a directory that can hold at least five times the expected database size, and can accommodate the database growth associated with network growth Default: /opt/5620sam/dbbackup How frequently, in hours, to back up the 5620 SAM database Default: 24 The number of 5620 SAM database backup sets to retain Default: 3 3HE AAAG-TQZZA 125

126 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM 44 If the 5620 SAM system is to include auxiliary servers, configure the aux parameters in the following table, and then enter back. Note: At least one auxiliary server that you specify must be a Preferred auxiliary server. Table 38 Standalone main server parameters aux Parameter stats calltrace pcmd ip-to-auxes preferred-list reserved-list peer-list calltrace-pairs Description If enabled, specifies that one or more auxiliary servers are to be used for statistics collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for call-trace data collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for PCMD record collection Default: false The main server IP address that the auxiliary servers must use to reach the main server Default: Comma-separated list of Preferred auxiliary server IP addresses Default: Comma-separated list of Reserved auxiliary server IP addresses Default: Comma-separated list of Remote Standby auxiliary server IP addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 126 3HE AAAG-TQZZA

127 5620 SAM 5650 CPAM To install a standalone 5620 SAM system Table 38 Standalone main server parameters aux (continued) Parameter pcmd-pairs Description List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 45 As required, configure the mediation parameters in the following table, and then enter back. Note: Some device types do not support an SNMP port value other than 162. Before you configure the snmp-port parameter to a value other than the default, you must ensure that each device type in the managed network supports the port value. Table 39 Standalone main server parameters mediation Parameter nat snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description Whether NAT is used between the main server and the managed NEs Default: false The IPv4 address that the managed NEs must use to reach the main server Default: IPv4 address of primary network interface The IPv6 address that the managed NEs must use to reach the main server Default: IPv6 address of primary network interface The TCP port on the main server station that the managed NEs must use to reach the main server Default: 162 The SNMP trap log ID associated with the main server Default: If required, configure the ssl parameters in the following table, and then enter back. Note: If you intend to manage Small Cell NEs, you must enable the webdav parameter. 3HE AAAG-TQZZA 127

128 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM Table 40 Standalone main server parameters ssl Parameter secure keystore-file keystore-pass truststore-file truststore-pass webdav Description Whether communication between the main server and the GUI clients, OSS clients, and auxiliary servers is SSL-secured Default: false The absolute path of the SSL keystore file The parameter is configurable when the secure parameter is enabled. Default: The SSL keystore password The parameter is configurable when the secure parameter is enabled. Default: The absolute path of the SSL truststore file The parameter is configurable when the secure parameter is enabled. Default: The SSL truststore password The parameter is configurable when the secure parameter is enabled. Default: Whether WebDAV access to enodeb activation data is enabled on the main server Default: false 47 As required, configure the oss parameters in the following table, and then enter back. Note: The parameters are configurable only if the configuration does not include one or more auxiliary servers. Table 41 Standalone main server parameters oss Parameter public-ip corba-3gpp Description The IP address that the OSS clients must use to reach the main server Default: IP address of primary network interface Whether to enable the 5620 SAM 3GPP OSS interface Default: false 128 3HE AAAG-TQZZA

129 5620 SAM 5650 CPAM To install a standalone 5620 SAM system Table 41 Standalone main server parameters oss (continued) Parameter xml-output Description The directory that is to contain the output of OSSI file export operations Default: /opt/5620sam/server/xml_output 48 If the 5620 SAM system includes one or more analytics servers, configure the analytics parameters in the following table, and then enter back. Table 42 Standalone main server parameters analytics Parameter ip-list load-balanced load-balancing method Description A comma-separated list of analytics server IP addresses that are accessible to the main server Default: Whether the 5620 SAM is to perform load balancing among the analytics servers Default: false The load-balancing method to use The parameter is configurable when the load-balanced parameter is set to true. Default: round-robin 49 If the 5620 SAM includes an auxiliary database, configure the auxdb parameters in the following table, and then enter back. Table 43 Standalone main server parameters auxdb Parameter enabled ip-list oam-test-results Description Whether the auxiliary database is enabled in the main server configuration A comma-separated list of the auxiliary database station IP addresses that are accessible to the main server Default: Whether the auxiliary database is to store OAM test results Default: false 3HE AAAG-TQZZA 129

130 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM 50 As required, configure the aa-stats parameters in the following table, and then enter back. Table 44 Standalone main server parameters aa-stats Parameter enabled formats aux-db storage Description Whether the 5620 SAM is to collect AA accounting statistics Default: false AA accounting statistics file formats; the options are the following: ipdr IPDR format ram 5670 RAM format ipdr,ram IPDR and 5670 RAM formats The parameter is configurable when the enabled parameter is set to true. Default: ram Whether the 5620 SAM is to store the statistics in an auxiliary database The parameter is configurable when the enabled parameter is set to true. Default: false 51 If required, configure the registry parameters in the following table, and then enter back. Table 45 Standalone main server parameters registry Parameter enabled ip-list Description Whether the 5620 SAM connects to a registry server Default: false A comma-separated list of the registry server IP addresses that are accessible to the main server Default: 52 Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required HE AAAG-TQZZA

131 5620 SAM 5650 CPAM To install a standalone 5620 SAM system 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main> Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. Prepare standalone main server for initialization If you need to enable Small Cell management, perform 7.3 To enable Small Cell management (p. 94) on the main server station. Create a directory on the main server for backing up the stored NE configurations. 1. Log in as the samadmin user on the main server station. 2. Open a console window. 3. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup Start standalone main server 57 Start the main server. Note: If you did not specify a license file during the installation, you cannot start the main server until you import a license; see Software and license configuration procedures in the 5620 SAM System Administrator Guide for information about importing a license. 1. Log in as the samadmin user on the main server station. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following: bash$./nmsserver.bash start 3HE AAAG-TQZZA 131

132 To install a standalone 5620 SAM system 5620 SAM 5650 CPAM 5. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following line of output: -- SAM Server is UP 6. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed until the server is completely started. 58 Close the console window. Install GUI clients 59 Perform the appropriate procedures in the following chapters to install 5620 SAM single-user GUI clients and client delegate servers, as required: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server END OF STEPS 132 3HE AAAG-TQZZA

133 5620 SAM 5650 CPAM Redundant system installation workflow Redundant 5620 SAM system installation 8.5 Redundant system installation workflow Description The following is the sequence of high-level actions required to install a redundant 5620 SAM system Stages Note: The links in the Install redundant core components (p. 133) stages lead to sections in 8.6 To install a redundant 5620 SAM system (p. 135). Install redundant core components Download the required 5620 SAM installation files and distribute the files to the stations in the system, as required; see Download and distribute 5620 SAM installation files (p. 135). Install the primary database; see Install primary database (p. 137). 1. Run a script to prepare for the Oracle software installation. 2. Install the database packages. 3. Create the primary database. Install the standby database; see Install standby database (p. 143). 1. Run a script to prepare for the Oracle software installation. 2. Install the database packages. 3. Create the standby database. Install the primary main server; see Install primary main server (p. 149). 1. Install the main server packages. 2. Create and apply the primary main server configuration. Configure additional objects and functions, as required; see Prepare primary main server for initialization (p. 161). 3HE AAAG-TQZZA 133

134 Redundant system installation workflow 5620 SAM 5650 CPAM Start the primary main server; see Start primary main server (p. 161). Install a single-user 5620 SAM GUI client or client delegate server; see Install GUI client (p. 162). Reinstantiate the standby database; see Reinstantiate standby database (p. 162). Install the standby main server; see Install standby main server (p. 163). 1. Install the main server packages. 2. Create and apply the standby main server configuration. Configure additional objects and functions, as required; see Prepare standby main server for initialization (p. 175). Start the standby main server; see Start standby main server (p. 175). Install optional components Install and enable one or more auxiliary servers, if required; see Auxiliary server installation (p. 177). Install and enable one or more Cflowd auxiliary servers, if required; see Cflowd auxiliary server installation (p. 191). Install and enable an auxiliary database, if required; see Auxiliary database installation (p. 198). Install and enable one or more analytics servers, if required; see Analytics server installation (p. 212). Install additional single-user 5620 SAM GUI clients and client delegate servers, as required; see Install additional GUI clients (p. 176) HE AAAG-TQZZA

135 5620 SAM 5650 CPAM To install a redundant 5620 SAM system 8.6 To install a redundant 5620 SAM system Description The following steps describe how to install a collocated or distributed 5620 SAM system in a redundant configuration. The steps also include information about installing optional 5620 SAM components. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. CAUTION Steps Misconfiguration Risk If the RHEL iptables / ip6tables firewall is enabled on a station, 5620 SAM software installation fails. Before a 5620 SAM system installation, you must ensure that the RHEL iptables / ip6tables firewall on each station is disabled. Note: You require root user privileges on the 5620 SAM database and main server stations. Note: Performing the procedure creates the following user accounts: on each 5620 SAM database station Oracle management on each main server station samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user Download and distribute 5620 SAM installation files 1 Download the following 5620 SAM installation files: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm samauxserver-sam_r_r_revision-pp.x86_64.rpm, if the system includes auxiliary servers 3HE AAAG-TQZZA 135

136 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level 2 Copy the following files to an empty directory on each main server, database, auxiliary server, and client delegate server station: Note: In subsequent steps, the directory is called the 5620 SAM software directory. samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm Perform one of the following. a. In a distributed 5620 SAM system: 1. Copy the following files to an empty directory on each database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh 2. Copy the following file to each main server station: samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm b. In a collocated 5620 SAM system, copy the following files to an empty directory on each main server and database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm If the 5620 SAM system includes one or more auxiliary servers, copy the following file to the 5620 SAM software directory on each auxiliary server station: samauxserver-sam_r_r_revision-pp.x86_64.rpm If the 5620 SAM system includes one or more client delegate servers, copy the following file to the 5620 SAM software directory on each client delegate server station: samclientdelegate-sam_r_r_revision-pp.x86_64.rpm 136 3HE AAAG-TQZZA

137 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Install primary database Log in as the root user on the primary database station. Open a console window. Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. Note: If you specify a value other than the default, you must record the value for use when the OracleSw_PreInstall.sh script is run during a software upgrade, or when the Oracle management user information is required by technical support. The following prompt is displayed: This script will prepare the system for a new install/restore of a 5620 SAM Version R.r Rn database. Do you want to continue? [Yes/No]: 9 10 Enter Yes. The following prompt is displayed: Enter the Oracle dba group name [group]: Enter a group name. Note: To reduce the complexity of subsequent software upgrades and technical support activities, it is recommended that you accept the default for this parameter. The following messages and prompt are displayed: Creating group group if it does not exist... done Enter the Oracle user name: 11 Enter a username. Note: To reduce the complexity of subsequent software upgrades and technical support activities, it is recommended that you accept the default. The following messages and prompt are displayed: 3HE AAAG-TQZZA 137

138 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Oracle user [username] new home directory will be [/opt/5620sam/oracle12r1]. Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1.., Checking user username... Adding username... Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Please assign a password to the UNIX user username.. New Password: Enter a password. The following prompt is displayed: Re-enter new Password: Re-enter the password. The following is displayed if the password change is successful: passwd: password successfully changed for username The following message and prompt are displayed: Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf HE AAAG-TQZZA

139 5620 SAM 5650 CPAM To install a redundant 5620 SAM system INFO: Completed running Oracle Pre-Install Tasks When the script execution is complete, enter the following to reboot the primary database station: # init 6 The station reboots. When the reboot is complete, log in as the root user on the primary database station. Open a console window. Enter the following: # yum install samjre* samconfig* samoracle* samdb* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> 3HE AAAG-TQZZA 139

140 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Enter the following: <db> show-detail The primary database configuration is displayed. Enter the following: <db> configure The prompt changes to <db configure>. As required, configure the general parameters in the following table. Note: The instance parameter is configurable only during database creation. Table 46 Primary database parameters, general Parameter ip instance Description Primary database IP address Default: IP address of primary network interface Primary database instance name, which must: contain 8 or fewer characters consist of ASCII characters only have a letter as the first character Default: samdb1 24 Configure the redundant parameters in the following table, and then enter back. Note: The instance parameter is configurable only during database creation. Table 47 Primary database parameters redundant Parameter ip Description Standby database IP address Default: 140 3HE AAAG-TQZZA

141 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 47 Primary database parameters redundant (continued) Parameter instance Description Standby database instance name, which must: contain 8 or fewer characters consist of ASCII characters only have a letter as the first character Default: samdb2 25 If required, configure one or more passwords parameters in the following table, and then enter back. Note: After you save the configuration, you cannot use samconfig to change a database password; you must use the method described in the 5620 SAM System Administrator Guide. Table 48 Primary database parameters passwords Parameter user sys Description Database user password Default: available from technical support Oracle SYS user password Default: available from technical support A password must: be between 4 and 30 characters long contain at least three of the following: lower-case alphabetic character upper-case alphabetic character numeric character special character, which is one of the following: # $_ not contain four or more of the same character type in sequence not be the same as the user name, or the reverse of the user name not contain a space character 26 If required, enable IP validation to specify the server components that have access to the 5620 SAM database; configure the parameters in the following table, and then enter back. 3HE AAAG-TQZZA 141

142 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 49 Primary database parameters ip-validation Parameter main-one main-two remote-servers Description IP address of primary main server Configuring the parameter enables IP validation. Default: IP address of standby main server Default: Comma-separated list of the IP addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers Default: Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to begin the database creation: <db> apply The database creation begins, and messages are displayed as the creation progresses. The following is displayed when the database creation is complete: DONE db configurations updated HE AAAG-TQZZA

143 5620 SAM 5650 CPAM To install a redundant 5620 SAM system When the database creation is complete, enter the following: <db> exit The samconfig utility closes. It is recommended that as a security measure, you limit the number of database user login failures that the 5620 SAM allows before the database user account is locked; see 5620 SAM database management procedures in the 5620 SAM System Administrator Guide. Install standby database Log in as the root user on the station that is to be the standby database station. Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 34 Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. Note: If you specify a value other than the default, you must record the value for use when the OracleSw_PreInstall.sh script is run during a software upgrade, or when the Oracle management user information is required by technical support. The following prompt is displayed: This script will prepare the system for a new install/restore of a 5620 SAM Version R.r Rn database. Do you want to continue? [Yes/No]: 35 Enter Yes. The following prompt is displayed: Enter the Oracle dba group name [group]: 3HE AAAG-TQZZA 143

144 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM 36 Enter a group name. Note: The group name must match the group name specified during the primary database installation. The following messages and prompt are displayed: Creating group group if it does not exist... done Enter the Oracle user name: 37 Enter a username. Note: The username must match the username specified during the primary database installation. The following messages and prompt are displayed: Oracle user [username] new home directory will be [/opt/5620sam/oracle12r1]. Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1.., Checking user username... Adding username... Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Please assign a password to the UNIX user username.. New Password: 38 Enter a password. Note: The password must match the password specified during the primary database installation. The following prompt is displayed: Re-enter new Password: 39 Re-enter the password. The following is displayed if the password change is successful: 144 3HE AAAG-TQZZA

145 5620 SAM 5650 CPAM To install a redundant 5620 SAM system passwd: password successfully changed for username The following message and prompt are displayed: Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... INFO: Completed running Oracle Pre-Install Tasks When the script execution is complete, enter the following to reboot the standby database station: # init 6 The station reboots. When the reboot is complete, log in as the root user on the station that is to be the standby database station. Open a console window. Enter the following: # yum install samjre* samconfig* samoracle* samdb* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G 3HE AAAG-TQZZA 145

146 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following: <db> configure type standby The prompt changes to <db configure>. If required, configure the ip parameter; enter the following: Note: The default is the IP address of the primary network interface on the station. <db configure> ip address where address is the IP address of this database Enter the following: <db configure> redundant ip address where address is the IP address of the primary database The prompt changes to <db configure redundant>. Enter the following, and then enter back : 146 3HE AAAG-TQZZA

147 5620 SAM 5650 CPAM To install a redundant 5620 SAM system <db configure redundant> instance instance_name where instance_name is the primary database instance name 51 If required, configure one or more passwords parameters in the following table, and then enter back. Note: After you save the configuration, you cannot use samconfig to change a database password; you must use the method described in the 5620 SAM System Administrator Guide. Table 50 Standby database parameters passwords Parameter user sys Description Database user password; the password must match the password specified during the primary database installation Default: available from technical support Oracle SYS user password; the password must match the password specified during the primary database installation Default: available from technical support 52 If required, enable IP validation to specify the server components that have access to the 5620 SAM database; configure the parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 51 Standby database parameters ip-validation Parameter main-one main-two Description IP address of primary main server Configuring the parameter enables IP validation. Default: IP address of standby main server Default: 3HE AAAG-TQZZA 147

148 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 51 Standby database parameters ip-validation (continued) Parameter remote-servers Description Comma-separated list of the IP addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers Default: Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. Note: The instance value is not set until the database is reinstantiated later in the procedure. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to begin the database creation: <db> apply The database creation begins, and messages are displayed as the creation progresses. The following is displayed when the database creation is complete: DONE db configurations updated. When the database creation is complete, enter the following: <db> exit The samconfig utility closes HE AAAG-TQZZA

149 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Install primary main server Log in as the root user on the station that is to be the primary main server station. Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Perform one of the following. a. If the primary main server and database are on separate stations, enter the following: # yum install samjre* samconfig* samserver* samneo4j* b. If the primary main server and database are collocated on one station, enter the following: # yum install samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! The initial 5620 SAM server installation on a station creates the samadmin user account and assigns a randomly generated password. 3HE AAAG-TQZZA 149

150 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM If this is the first main, auxiliary, analytics, or client delegate server installation on the station, change the samadmin password. Note: The samadmin password must not contain symbol, or enodeb device management may be compromised. 1. Enter the following: # passwd samadmin The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Confirm Password: 3. Re-enter the password. 4. Record the password and store it in a secure location Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure The prompt changes to <main configure>. As required, configure the general parameters in the following table. Table 52 Primary main server parameters, general Parameter ip domain Description The primary main server IP address Default: IP address of primary network interface The 5620 SAM server cluster identifier Default: 5620sam 150 3HE AAAG-TQZZA

151 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 52 Primary main server parameters, general (continued) Parameter license Description Absolute path of 5620 SAM license zip file You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file, or import a license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. Default: 65 As required, configure the client parameters in the following table, and then enter back. Table 53 Primary main server parameters client Parameter nat hostname public-ip jndi-port Description Whether NAT is used between the main servers and the GUI clients, OSS clients, and auxiliary servers Default: false The primary main server hostname, if the GUI clients, OSS clients, and auxiliary servers are to use hostnames, rather than IP addresses, for communication with the main servers You must configure the parameter if the main server is to use multiple interfaces for GUI and OSS client communication. Default: The IP address that the GUI and OSS clients must use to reach the primary main server The parameter is configurable when the hostname parameter is unconfigured. Default: IP address of primary network interface The TCP port on the primary main server station to use for EJB JNDI messaging to GUI clients It is strongly recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the primary main server. Default: HE AAAG-TQZZA 151

152 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 53 Primary main server parameters client (continued) Parameter delegates Description A list of the client delegate servers in the 5620 SAM system Use the following list format; a path value is the absolute file path of the client installation location on the client delegate server station: address1;path1,address2;path2...addressn;pathn Note: Before you can install a client delegate server using a browser, each main server configuration must include the client delegate server address and file path. Default: 66 Configure the database parameters in the following table, and then enter back. Table 54 Primary main server parameters database Parameter ip instance user-password backup-dest backup-interval backup-sets Description The IP address that the primary main server must use to reach the primary database Default: Primary database instance name Default: samdb1 Primary database user password Default: available from technical support The backup directory on the primary database station It is recommended that you specify a directory that can hold at least five times the expected database size, and can accommodate the database growth associated with network growth Default: /opt/5620sam/dbbackup How frequently, in hours, to back up the 5620 SAM database Default: 24 The number of 5620 SAM database backup sets to retain Default: 3 67 If the 5620 SAM system is to include auxiliary servers, configure the aux parameters in the following table, and then enter back. Note: At least one auxiliary server that you specify must be a Preferred auxiliary server HE AAAG-TQZZA

153 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 55 Primary main server parameters aux Parameter stats calltrace pcmd ip-to-auxes preferred-list reserved-list peer-list calltrace-pairs pcmd-pairs Description If enabled, specifies that one or more auxiliary servers are to be used for statistics collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for call-trace data collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for PCMD record collection Default: false The primary main server IP address that the auxiliary servers must use to reach the primary main server Default: Comma-separated list of Preferred auxiliary server IP addresses Default: Comma-separated list of Reserved auxiliary server IP addresses Default: Comma-separated list of Remote auxiliary server IP addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 68 Enter the following: 3HE AAAG-TQZZA 153

154 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM <main> configure redundancy enabled The prompt changes to <main configure redundancy>. 69 Configure the general redundancy parameters in the following table. Table 56 Primary main server parameters redundancy Parameter ip-to-peer rsync-ip Description The primary main server IP address that the standby main server must use for general communication Default: IP address of primary network interface The primary main server IP address that the standby main server must use for data synchronization Default: IP address of primary network interface 70 Configure the database redundancy parameters in the following table, and then enter back. Table 57 Primary main server parameters redundancy, database Parameter ip instance backup-sync Description The IP address that the primary main server must use to reach the standby database Default: The standby database instance name Default: Whether database backup file synchronization is enabled When the parameter is enabled, each 5620 SAM database backup file set is copied to the peer database station after the backup completes. You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth requirements of database backup file synchronization. You must set the parameter to the same value on each main server. Default: false 154 3HE AAAG-TQZZA

155 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 57 Primary main server parameters redundancy, database (continued) Parameter alignment prefer-instance reinstantiation-delay Description Whether automatic database alignment is enabled If automatic database alignment is enabled, a main server and database attempt to assume a common role, primary or standby, after an event such as a server activity switch or database failover. In a geographically dispersed system, the function helps to ensure that a main server communicates with the local database in order to reduce the network latency between the components. For more information about database alignment, see the 5620 SAM System Administrator Guide. Default: false The name of the database instance with which the primary main server is to align The parameter is configurable when the alignment parameter is enabled. Default: The delay, in minutes, between the completion of a database failover and the automatic reinstantiation of the standby database A value of 0 disables automatic database reinstantiation. Default: Configure the peer-server redundancy parameters in the following table, and then enter back. Table 58 Primary main server parameters redundancy, peer-server Parameter ip hostname rsync-ip Description The standby main server IP address that the primary main server uses for general communication Default: The standby main server hostname that the primary main server uses for general communication The parameter is configurable and mandatory when the hostname parameter in Step 65 is configured. Default: The standby main server IP address that the primary main server uses for data synchronization Default: 3HE AAAG-TQZZA 155

156 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 58 Primary main server parameters redundancy, peer-server (continued) Parameter public-ip jndi-port ip-to-auxes snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description The IP address that the GUI and OSS clients must use to reach the standby main server Default: The TCP port on the standby main server station used for EJB JNDI messaging to GUI clients It is recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the standby main server. Default: 1099 The standby main server IP address that the auxiliary servers must use to reach the standby main server You must configure the parameter if the 5620 SAM system includes one or more auxiliary servers. Default: The IPv4 address that the managed NEs must use to reach the standby main server The IPv6 address that the managed NEs must use to reach the standby main server The TCP port on the standby main server station used for SNMP communication with the managed NEs Default: 162 The SNMP trap log ID associated with the standby main server Default: Enter back. The prompt changes to <main configure>. As required, configure the mediation parameters in the following table, and then enter back. Note: Some device types do not support an SNMP port value other than 162. Before you configure the snmp-port parameter to a value other than the default, you must ensure that each device type in the managed network supports the port value HE AAAG-TQZZA

157 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 59 Primary main server parameters mediation Parameter nat snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description Whether NAT is used between the main servers and the managed NEs Default: false The IPv4 address that the managed NEs must use to reach the primary main server Default: IPv4 address of primary network interface The IPv6 address that the managed NEs must use to reach the primary main server Default: IPv6 address of primary network interface The TCP port on the primary main server station that the managed NEs must use to reach the primary main server Default: 162 The SNMP trap log ID associated with the primary main server Default: If required, configure the ssl parameters in the following table, and then enter back. Note: If you intend to manage Small Cell NEs, you must enable the webdav parameter. Table 60 Primary main server parameters ssl Parameter secure keystore-file keystore-pass Description Whether communication between the main servers and the GUI clients, OSS clients, and auxiliary servers is SSL-secured Default: false The absolute path of the SSL keystore file The parameter is configurable when the secure parameter is enabled. Default: The SSL keystore password The parameter is configurable when the secure parameter is enabled. Default: 3HE AAAG-TQZZA 157

158 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 60 Primary main server parameters ssl (continued) Parameter truststore-file truststore-pass webdav Description The absolute path of the SSL truststore file The parameter is configurable when the secure parameter is enabled. Default: The SSL truststore password The parameter is configurable when the secure parameter is enabled. Default: Whether WebDAV access to enodeb activation data is enabled Default: false 75 As required, configure the oss parameters in the following table, and then enter back. Note: The parameters are configurable only if the configuration does not include one or more auxiliary servers. Table 61 Primary main server parameters oss Parameter public-ip corba-3gpp xml-output Description The IP address that the OSS clients must use to reach the primary main server Default: IP address of primary network interface Whether the 5620 SAM 3GPP OSS interface is enabled Default: false The directory in which to store the output of OSS file export operations Default: /opt/5620sam/server/xml_output 76 If the 5620 SAM system includes one or more analytics servers, configure the analytics parameters in the following table, and then enter back 158 3HE AAAG-TQZZA

159 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 62 Primary main server parameters analytics Parameter ip-list load-balanced load-balancing method Description A comma-separated list of analytics server IP addresses that are accessible to the main server Default: Whether the 5620 SAM is to perform load balancing among the analytics servers Default: false The load-balancing method to use The parameter is configurable when the load-balanced parameter is set to true. Default: round-robin 77 If the 5620 SAM includes an auxiliary database, configure the auxdb parameters in the following table, and then enter back. Table 63 Primary main server parameters auxdb Parameter enabled ip-list oam-test-results Description Whether the auxiliary database is enabled in the main server configuration A comma-separated list of the auxiliary database station IP addresses that are accessible to the main server Default: Whether the auxiliary database is to store OAM test results Default: false 78 As required, configure the aa-stats parameters in the following table, and then enter back. Table 64 Primary main server parameters aa-stats Parameter enabled Description Whether the 5620 SAM is to collect AA accounting statistics Default: false 3HE AAAG-TQZZA 159

160 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 64 Primary main server parameters aa-stats (continued) Parameter formats aux-db storage Description AA accounting statistics file formats; the options are the following: ipdr IPDR format ram 5670 RAM format ipdr,ram IPDR and 5670 RAM formats The parameter is configurable when the enabled parameter is set to true. Default: ram Whether the 5620 SAM is to store the statistics in an auxiliary database The parameter is configurable when the enabled parameter is set to true. Default: false 79 If required, configure the registry parameters in the following table, and then enter back. Table 65 Primary main server parameters registry Parameter enabled ip-list Description Whether the 5620 SAM connects to a registry server Default: false A comma-separated list of the registry server IP addresses that are accessible to the main server Default: 80 Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main> HE AAAG-TQZZA

161 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. Prepare primary main server for initialization If you need to enable Small Cell management, perform 7.3 To enable Small Cell management (p. 94) on the primary main server station. Create a directory on the main server for backing up the stored NE configurations. 1. Log in as the samadmin user on the primary main server station. 2. Open a console window. 3. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup Start primary main server 85 Start the primary main server. Note: If you did not specify a license file during the installation, you cannot start the main server until you import a license. See Software and license configuration procedures in the 5620 SAM System Administrator Guide for information about importing a license. 1. Log in as the samadmin user on the main server station. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following: bash$./nmsserver.bash start 5. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. 3HE AAAG-TQZZA 161

162 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following line of output: -- Primary Server is UP 6. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Close the console window. Install GUI client 87 Perform the appropriate procedure in one of the following chapters to install a 5620 SAM single-user GUI client or client delegate server: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server Reinstantiate standby database Open a 5620 SAM GUI client as the admin user. Choose Administration System Information from the 5620 SAM main menu. The System Information form opens. Click Re-Instantiate Standby. Click Yes to confirm the action. The reinstantiation begins, and the GUI status bar displays reinstantiation information. Note: Database reinstantiation takes considerable time if the database contains a large amount of statistics data. You can also use the System Information form to monitor the reinstantiation progress. The Last Attempted Standby Re-instantiation Time is the start time; the Standby Re-instantiation State changes from In Progress to Success when the reinstantiation is complete HE AAAG-TQZZA

163 5620 SAM 5650 CPAM To install a redundant 5620 SAM system 92 When the reinstantiation is complete, close the System Information form. Install standby main server Log in as the root user on the station that is to be the standby main server station. Open a console window. Navigate to the 5620 SAM software directory. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Perform one of the following. a. If the standby main server and database are on separate stations, enter the following: # yum install samjre* samconfig* samserver* samneo4j* b. If the standby main server and database are collocated on one station, enter the following: # yum install samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 3HE AAAG-TQZZA 163

164 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM 98 The initial 5620 SAM server installation on a station creates the samadmin user account and assigns a randomly generated password. If this is the first main, auxiliary, analytics, or client delegate server installation on the station, change the samadmin password. Note: The samadmin password must not contain symbol, or enodeb device management may be compromised. 1. Enter the following: # passwd samadmin The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Confirm Password: 3. Re-enter the password. 4. Record the password and store it in a secure location. 99 Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> 100 Enter the following: <main> configure The prompt changes to <main configure>. 101 As required, configure the general parameters in the following table. Table 66 Standby main server parameters, general Parameter ip domain Description The standby main server IP address Default: IP address of primary network interface The 5620 SAM server cluster identifier Default: 5620sam 164 3HE AAAG-TQZZA

165 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 66 Standby main server parameters, general (continued) Parameter license Description Absolute path of 5620 SAM license zip file You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file, or import a license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. Default: 102 As required, configure the client parameters in the following table, and then enter back. Table 67 Standby main server parameters client Parameter nat hostname public-ip jndi-port Description Whether NAT is used between the main servers and the GUI clients, OSS clients, and auxiliary servers Default: false The standby main server hostname, if the GUI clients, OSS clients, and auxiliary servers are to use hostnames, rather than IP addresses, for communication with the main servers You must configure the parameter if the main server is to use multiple interfaces for GUI and OSS client communication. Default: The IP address that the GUI and OSS clients must use to reach the standby main server The parameter is configurable when the hostname parameter is unconfigured. Default: IP address of primary network interface The TCP port on the standby main server station to use for EJB JNDI messaging to GUI clients It is recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the standby main server. Default: HE AAAG-TQZZA 165

166 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 67 Standby main server parameters client (continued) Parameter delegates Description A list of the client delegate servers in the 5620 SAM system Use the following list format; a path value is the absolute file path of the client installation location on the client delegate server station: address1;path1,address2;path2...addressn;pathn Note: Before you can install a client delegate server using a browser, each main server configuration must include the client delegate server address and file path. Default: 103 Configure the database parameters in the following table, and then enter back. Table 68 Standby main server parameters database Parameter ip instance user-password backup-dest backup-interval backup-sets Description The IP address that the standby main server must use to reach the standby database Default: Standby database instance name You must set this parameter to the same value as the instance parameter in step Step 70. Default: samdb1 Standby database user password Default: available from technical support The backup directory on the primary database station It is recommended that you specify a directory that can hold at least five times the expected database size, and can accommodate the database growth associated with network growth Default: /opt/5620sam/dbbackup How frequently, in hours, to back up the 5620 SAM database Default: 24 The number of 5620 SAM database backup sets to retain Default: If the 5620 SAM system is to include auxiliary servers, configure the aux parameters in the following table, and then enter back. Note: At least one auxiliary server that you specify must be a Preferred auxiliary server HE AAAG-TQZZA

167 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 69 Standby main server parameters aux Parameter stats calltrace pcmd ip-to-auxes preferred-list reserved-list peer-list calltrace-pairs pcmd-pairs Description If enabled, specifies that one or more auxiliary servers are to be used for statistics collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for call-trace data collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for PCMD record collection Default: false The standby main server IP address that the auxiliary servers must use to reach the standby main server Default: Comma-separated list of Preferred auxiliary server IP addresses Default: Comma-separated list of Reserved auxiliary server IP addresses Default: Comma-separated list of Remote auxiliary server IP addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 105 Enter the following: 3HE AAAG-TQZZA 167

168 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM <main> configure redundancy enabled The prompt changes to <main configure redundancy>. 106 Configure the general redundancy parameters in the following table. Table 70 Standby main server parameters redundancy Parameter ip-to-peer rsync-ip Description The standby main server IP address that the primary main server must use for general communication Default: IP address of primary network interface The standby main server IP address that the primary main server must use for data synchronization Default: IP address of primary network interface 107 Configure the database redundancy parameters in the following table, and then enter back. Table 71 Standby main server parameters redundancy, database Parameter ip instance backup-sync Description The IP address that the standby main server must use to reach the primary database Default: Primary database instance name Default: Whether database backup file synchronization is enabled When the parameter is enabled, each 5620 SAM database backup file set is copied to the peer database station after the backup completes. You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth requirements of database backup file synchronization. You must set the parameter to the same value on each main server. Default: false 168 3HE AAAG-TQZZA

169 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 71 Standby main server parameters redundancy, database (continued) Parameter alignment prefer-instance reinstantiation-delay Description Whether automatic database alignment is enabled If automatic database alignment is enabled, a main server and database attempt to assume a common role, primary or standby, after an event such as a server activity switch or database failover. In a geographically dispersed system, the function helps to ensure that a main server communicates with the local database in order to reduce the network latency between the components. For more information about database alignment, see the 5620 SAM System Administrator Guide. Default: false The name of the database instance with which the standby main server is to align The parameter is configurable when the alignment parameter is enabled. Default: The delay, in minutes, between the completion of a database failover and the automatic reinstantiation of the standby database A value of 0 disables automatic database reinstantiation. Default: Configure the peer-server redundancy parameters in the following table, and then enter back. Table 72 Standby main server parameters redundancy, peer-server Parameter ip hostname Description The primary main server IP address that the standby main server must use for general communication Default: The primary main server hostname that the standby main server must use for general communication The parameter is configurable and mandatory when the hostname parameter in Step 102 is configured. Default: 3HE AAAG-TQZZA 169

170 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 72 Standby main server parameters redundancy, peer-server (continued) Parameter rsync-ip public-ip jndi-port ip-to-auxes snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description The primary main server IP address that the standby main server must use for data synchronization Default: The IP address that the GUI clients, OSS clients, and auxiliary servers must use to reach the primary main server Default: The TCP port on the primary main server station used for EJB JNDI messaging to GUI clients It is recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the primary main server. Default: 1099 The primary main server IP address that the auxiliary servers must use to reach the primary main server You must configure the parameter if the 5620 SAM system includes one or more auxiliary servers. Default: The IPv4 address that the managed NEs must use to reach the primary main server The IPv6 address that the managed NEs must use to reach the primary main server The TCP port on the primary main server station used for SNMP communication with the managed NEs Default: 162 The SNMP trap log ID associated with the primary main server Default: Enter back. The prompt changes to <main configure>. 110 As required, configure the mediation parameters in the following table, and then enter back. Note: Some device types do not support an SNMP port value other than 162. Before you configure the snmp-port parameter to a value other than the default, you must ensure that each device type in the managed network supports the port value HE AAAG-TQZZA

171 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 73 Standby main server parameters mediation Parameter nat snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description Whether NAT is used between the main servers and the managed NEs Default: false The IPv4 address that the managed NEs must use to reach the standby main server Default: IPv4 address of primary network interface The IPv6 address that the managed NEs must use to reach the standby main server Default: IPv6 address of primary network interface The TCP port on the standby main server station that the managed NEs must use to reach the standby main server Default: 162 The SNMP trap log ID associated with the standby main server Default: If required, configure the ssl parameters in the following table, and then enter back. Note: If you intend to manage Small Cell NEs, you must enable the webdav parameter. Table 74 Standby main server parameters ssl Parameter secure keystore-file keystore-pass Description Whether communication between the main servers and the GUI clients, OSS clients, and auxiliary servers is SSL-secured Default: false The absolute path of the SSL keystore file The parameter is configurable when the secure parameter is enabled. Default: The SSL keystore password The parameter is configurable when the secure parameter is enabled. Default: 3HE AAAG-TQZZA 171

172 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 74 Standby main server parameters ssl (continued) Parameter truststore-file truststore-pass webdav Description The absolute path of the SSL truststore file The parameter is configurable when the secure parameter is enabled. Default: The SSL truststore password The parameter is configurable when the secure parameter is enabled. Default: Whether WebDAV access to enodeb activation data is enabled Default: false 112 As required, configure the oss parameters in the following table, and then enter back. Note: The parameters are configurable only if the configuration does not include one or more auxiliary servers. Table 75 Standby main server parameters oss Parameter public-ip corba-3gpp xml-output Description The IP address that the OSS clients must use to reach the standby main server Default: IP address of primary network interface Whether the 5620 SAM 3GPP OSS interface is enabled Default: false The directory in which to store the output of OSS file export operations Default: /opt/5620sam/server/xml_output 113 If the 5620 SAM system includes one or more analytics servers, configure the analytics parameters in the following table, and then enter back 172 3HE AAAG-TQZZA

173 5620 SAM 5650 CPAM To install a redundant 5620 SAM system Table 76 Standby main server parameters analytics Parameter ip-list load-balanced load-balancing method Description A comma-separated list of analytics server IP addresses that are accessible to the main server Default: Whether the 5620 SAM is to perform load balancing among the analytics servers Default: false The load-balancing method to use The parameter is configurable when the load-balanced parameter is set to true. Default: round-robin 114 If the 5620 SAM includes an auxiliary database, configure the auxdb parameters in the following table, and then enter back. Table 77 Standby main server parameters auxdb Parameter enabled ip-list oam-test-results Description Whether the auxiliary database is enabled in the main server configuration A comma-separated list of the auxiliary database station IP addresses that are accessible to the main server Default: Whether the auxiliary database is to store OAM test results Default: false 115 As required, configure the aa-stats parameters in the following table, and then enter back. Table 78 Standby main server parameters aa-stats Parameter enabled Description Whether the 5620 SAM is to collect AA accounting statistics Default: false 3HE AAAG-TQZZA 173

174 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM Table 78 Standby main server parameters aa-stats (continued) Parameter formats aux-db storage Description AA accounting statistics file formats; the options are the following: ipdr IPDR format ram 5670 RAM format ipdr,ram IPDR and 5670 RAM formats The parameter is configurable when the enabled parameter is set to true. Default: ram Whether the 5620 SAM is to store the statistics in an auxiliary database The parameter is configurable when the enabled parameter is set to true. Default: false 116 If required, configure the registry parameters in the following table, and then enter back. Table 79 Standby main server parameters registry Parameter enabled ip-list Description Whether the 5620 SAM connects to a registry server Default: false A comma-separated list of the registry server IP addresses that are accessible to the main server Default: 117 Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main> HE AAAG-TQZZA

175 5620 SAM 5650 CPAM To install a redundant 5620 SAM system 118 Enter the following: <main> apply The configuration is applied. 119 Enter the following: <main> exit The samconfig utility closes. Prepare standby main server for initialization 120 If you need to enable Small Cell management, perform 7.3 To enable Small Cell management (p. 94) on the standby main server station. 121 Create a directory on the main server for backing up the stored NE configurations. 1. Log in as the samadmin user on the standby main server station. 2. Open a console window. 3. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup Start standby main server 122 Start the standby main server. Note: If you did not specify a license file during the installation, you cannot start the main server until you import a license. See Software and license configuration procedures in the 5620 SAM System Administrator Guide for information about importing a license. 1. Log in as the samadmin user on the main server station. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following: bash$./nmsserver.bash start 5. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. 3HE AAAG-TQZZA 175

176 To install a redundant 5620 SAM system 5620 SAM 5650 CPAM If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following line of output: -- Standby Server is UP 6. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Close the console window. Install additional GUI clients 124 Perform the appropriate procedures in the following chapters to install additional 5620 SAM single-user GUI clients and client delegate servers, as required: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server END OF STEPS 176 3HE AAAG-TQZZA

177 5620 SAM 5650 CPAM Auxiliary server installation workflow Auxiliary server installation 8.7 Auxiliary server installation workflow Description CAUTION Deployment Restriction A 5620 SAM auxiliary server requires a dedicated station. You cannot install the auxiliary server software on a station if another 5620 SAM component is installed on the station. This section describes how to install a 5620 SAM auxiliary server, and enable the auxiliary server in a 5620 SAM system Stages The following is the sequence of high-level actions required to install and enable an auxiliary server in a 5620 SAM system Perform 8.8 To install a 5620 SAM auxiliary server (p. 177) on the auxiliary server station. Perform 8.9 To add auxiliary servers to a 5620 SAM system (p. 184) to configure the auxiliary server communication with each main server. An auxiliary server can use multiple interfaces for network management. The default networkmanagement interface address is the public IP address of the interface that is used for main server communication. If you need to configure a different or additional network-management interface, see To configure an additional management interface on an auxiliary server in the 5620 SAM System Administrator Guide. 8.8 To install a 5620 SAM auxiliary server Description The following steps describe how to install the 5620 SAM auxiliary server software on a station. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. Note: An auxiliary server is dedicated to only one of the following functions: statistics collection 3HE AAAG-TQZZA 177

178 To install a 5620 SAM auxiliary server 5620 SAM 5650 CPAM Steps call-trace data collection PCMD record collection Note: You require root user privileges on the auxiliary server station. Note: Performing the procedure creates the samadmin user account on the auxiliary server station. Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user Log in as the root user on the station that is to be the auxiliary server station. Download the following 5620 SAM installation files to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samauxserver-sam_r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 5 Enter the following: # yum install samjre* samconfig* samauxserver* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G 178 3HE AAAG-TQZZA

179 5620 SAM 5650 CPAM To install a 5620 SAM auxiliary server Installed size: nn G Is this ok [y/n]: 6 7 Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! The initial 5620 SAM server installation on a station creates the samadmin user account and assigns a randomly generated password. If this is the first main, auxiliary, analytics, or client delegate server installation on the station, change the samadmin password. Note: The samadmin password must not contain symbol, or enodeb device management may be compromised. 1. Enter the following: # passwd samadmin The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Confirm Password: 3. Re-enter the password. 4. Record the password and store it in a secure location. 8 Enter the following: # samconfig -m aux The following is displayed: Start processing command line inputs... <aux> 3HE AAAG-TQZZA 179

180 To install a 5620 SAM auxiliary server 5620 SAM 5650 CPAM Enter the following: <aux> configure The prompt changes to <aux configure>. Enter the following: <aux configure> show-detail The auxiliary server configuration is displayed. If the default ip value is not the correct IP address of the auxiliary server, configure the ip parameter. If the auxiliary server is to perform call-trace data collection, perform the following steps. 1. Enter the following: <aux configure> service type calltrace The prompt changes to <aux configure service>. 2. Enter the following: <aux configure service> calltrace The prompt changes to <aux configure service calltrace>. 3. Configure the parameters in the following table. Parameter ipv4 ipv6 dir debug-dir Description The IPv4 address that the managed NEs must use to reach the auxiliary server Default: The IPv6 address that the managed NEs must use to reach the auxiliary server Default: The absolute file path of the local directory in which to store the collected call-trace files Default: /opt/5620sam/calltrace The absolute file path of the local directory in which to store the collected debug-trace files Default: /opt/5620sam/debugtrace 4. Enter back. The prompt changes to <aux configure service> HE AAAG-TQZZA

181 5620 SAM 5650 CPAM To install a 5620 SAM auxiliary server 5. Enter back. The prompt changes to <aux configure>. 13 If the auxiliary server is to perform PCMD record collection, perform the following steps. 1. Enter the following: <aux configure> service type pcmd The prompt changes to <aux configure service>. 2. Enter the following: <aux configure service> pcmd The prompt changes to <aux configure service pcmd>. 3. Configure the parameters in the following table. Parameter ipv4 ipv6 nat public-ip dir Description The IPv4 address that the managed NEs must use to reach the auxiliary server Default: The IPv6 address that the managed NEs must use to reach the auxiliary server Default: Whether NAT is used between the managed NEs and the auxiliary server Default: false The public IP address that the managed NEs must use to reach the auxiliary server when NAT is enabled The parameter is configurable when the nat parameter is set to true. Default: The absolute file path of the local directory in which to store the collected PCMD CSV files Default: /opt/5620sam/pcmd_output 4. Enter back. The prompt changes to <aux configure service>. 5. Enter back. The prompt changes to <aux configure>. 14 Configure the main-server parameters in the following table, and then enter back. 3HE AAAG-TQZZA 181

182 To install a 5620 SAM auxiliary server 5620 SAM 5650 CPAM Table 80 Auxiliary server parameters main-server Parameter domain ip-one ip-two Description The 5620 SAM server cluster identifier Default: 5620sam The primary main server IP address that the auxiliary server must use to reach the standalone main server, or the primary main server in a redundant system Default: The standby main server IP address that the auxiliary server must use to reach the standby main server in a redundant system Default: 15 Configure the data-sync parameters in the following table, and then enter back. Table 81 Auxiliary server parameters data-sync Parameter local-ip peer-ip Description The IP address of the interface on this station that the other auxiliary server in an auxiliary server pair must use to reach this auxiliary server Default: IP address of primary network interface The IP address of the interface on the other auxiliary server station in an auxiliary server pair that this auxiliary server must use to reach the other auxiliary server Default: 16 If required, configure the ssl parameters in the following table, and then enter back. Table 82 Auxiliary server parameters ssl Parameter secure keystore-file Description Whether communication between the auxiliary server, main servers, and OSS clients is SSL-secured Default: false The absolute path of the SSL keystore file The parameter is configurable when the secure parameter is enabled. Default: 182 3HE AAAG-TQZZA

183 5620 SAM 5650 CPAM To install a 5620 SAM auxiliary server Table 82 Auxiliary server parameters ssl (continued) Parameter keystore-pass Description The SSL keystore password The parameter is configurable when the secure parameter is enabled. Default: 17 As required, configure the oss parameters in the following table, and then enter back. Table 83 Auxiliary server parameters oss Parameter public-ip xml-output Description The IP address that the OSS clients must use to reach the auxiliary server Default: IP address of primary network interface The directory that is to contain the output of OSSI file export operations Default: /opt/5620sam/server/xml_output Verify the auxiliary server configuration. 1. Enter the following: <aux configure> show-detail The auxiliary server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required. 4. When you are certain that the configuration is correct, enter the following: <aux configure> back The prompt changes to <aux>. Enter the following: <aux> apply The configuration is applied. Enter the following: <aux> exit 3HE AAAG-TQZZA 183

184 To add auxiliary servers to a 5620 SAM system 5620 SAM 5650 CPAM The samconfig utility closes If you need to enable Small Cell management using the auxiliary server, perform 7.3 To enable Small Cell management (p. 94) on the auxiliary server station. Start the auxiliary server. 1. Enter the following to switch to the samadmin user. # su - samadmin 2. Enter the following to start the auxiliary server application: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The auxiliary server initializes. Close the open console windows. END OF STEPS 8.9 To add auxiliary servers to a 5620 SAM system Description The following steps describe how to add one or more 5620 SAM auxiliary servers to a 5620 SAM system. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. CAUTION Service Disruption If the 5620 SAM system uses a firewall, before you add a new component to the system you must ensure that the firewall allows the required traffic to pass. See the 5620 SAM Planning Guide for specific firewall configuration information. CAUTION Service Disruption This procedure requires that you restart each main server, which is service-affecting. Perform this procedure only during a scheduled maintenance period. Note: You require the following user privileges: on each main and auxiliary server station root, samadmin 184 3HE AAAG-TQZZA

185 5620 SAM 5650 CPAM To add auxiliary servers to a 5620 SAM system Steps on each database station that has IP validation enabled Oracle management If the 5620 SAM is deployed in a standalone configuration, go to Step 5. Perform Step 5 to Step 16 on the standby main server, which is called Server B. Perform Step 5 to Step 16 on the primary main server, which is called Server A. Note: After you stop the primary main server in Step 7, a server activity switch occurs and Server B begins to manage the network. If required, you can revert to the previous primary and standby roles of Server A and Server B by performing the activity switch described in in Step Go to Step 18. Log in to the main server station as the root user. Open a console window. Perform the following steps to stop the main server application. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following to stop the main server application: bash$./nmsserver.bash stop 4. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 5. The main server is stopped when the command displays the following status message: Application Server is stopped 3HE AAAG-TQZZA 185

186 To add auxiliary servers to a 5620 SAM system 5620 SAM 5650 CPAM If the command displays a different message, wait five minutes and then return to Step 7 4. Do not proceed to the next step until the server is stopped Enter the following to switch back to the root user: bash$ exit Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure aux The prompt changes to <main configure aux>. Configure the parameters in the following table, and then enter back. Note: At least one auxiliary server that you specify must be a Preferred auxiliary server. Table 84 Main server aux parameters Parameter stats calltrace pcmd ip-to-auxes Description If enabled, specifies that one or more auxiliary servers are to be used for statistics collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for call-trace data collection Default: false If enabled, specifies that one or more auxiliary servers are to be used for PCMD record collection Default: false The main server IP address that the auxiliary servers must use to reach the main server Default: 186 3HE AAAG-TQZZA

187 5620 SAM 5650 CPAM To add auxiliary servers to a 5620 SAM system Table 84 Main server aux parameters (continued) Parameter preferred-list reserved-list peer-list calltrace-pairs pcmd-pairs Description Comma-separated list of Preferred auxiliary server IP addresses Default: Comma-separated list of Reserved auxiliary server IP addresses Default: Comma-separated list of Remote auxiliary server IP addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: Enter the following: exit The prompt changes to <main>. Verify the configuration; enter the following: <main> show-detail The main server configuration is displayed. If the configuration is correct, enter the following: <main> apply The configuration is applied. 3HE AAAG-TQZZA 187

188 To add auxiliary servers to a 5620 SAM system 5620 SAM 5650 CPAM Enter the following: <main> exit The samconfig utility closes. Start the main server. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash start 4. Enter the following to display the main server status: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns one of the following lines of output: on a standalone main server: -- SAM Server is Up on a primary main server: -- Primary Server is UP on a standby main server: -- Standby Server is UP 5. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed to the next step until the server is completely started. To revert to the previous primary and standby main server roles in a redundant deployment, perform the following steps. 1. Log in to Server B as the samadmin user. 2. Open a console window. 3. Enter the following to initiate a server activity switch: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash force_restart The server activity switch begins; Server B restarts as the standby main server, and Server A begins to manage the network as the primary main server HE AAAG-TQZZA

189 5620 SAM 5650 CPAM To add auxiliary servers to a 5620 SAM system 4. Log in to Server A as the samadmin user. 5. Open a console window. 6. Enter the following to display the main server status: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following line of output: -- Primary Server is UP 7. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed to the next step until the server is completely started. 18 If IP validation is enabled for database access, perform the following steps on each database station to enable validation of each auxiliary server. Note: In a redundant 5620 SAM system, you must perform the steps on the primary database station first, and then on the standby database station. 1. Log in to the database station as the Oracle management user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/oracle12r1/network/admin 4. Create a backup copy of the sqlnet.ora file. 5. Open the sqlnet.ora file with a plain-text editor, for example, vi. 6. Locate the section that begins with the following: # IP Validation 7. Edit the following lines to read: TCP.VALIDNODE_CHECKING = yes TCP.INVITED_NODES = (aux_server_1,aux_server_2...aux_server_n...) where aux_server_1,aux_server_2...aux_server_n is a comma-separated list of the auxiliary server IP addresses 8. Save and close the sqlnet.ora file. 9. Enter the following command to stop the Oracle database listener: bash$ /opt/5620sam/oracle12r1/bin/lsnrctl stop 10. Enter the following command to start the Oracle database listener: bash$ /opt/5620sam/oracle12r1/bin/lsnrctl start 3HE AAAG-TQZZA 189

190 To add auxiliary servers to a 5620 SAM system 5620 SAM 5650 CPAM 19 Close the open console windows. END OF STEPS 190 3HE AAAG-TQZZA

191 5620 SAM 5650 CPAM Cflowd auxiliary server installation workflow Cflowd auxiliary server installation 8.10 Cflowd auxiliary server installation workflow Description CAUTION Stages Deployment Restriction A 5620 SAM Cflowd auxiliary server requires a dedicated station. You cannot install the Cflowd auxiliary server software on a station if another 5620 SAM component is installed on the station. This section describes how to install and enable a 5620 SAM Cflowd auxiliary server in a standalone or redundant 5620 SAM system. See the 5620 SAM Statistics Management Guide for information about configuring the Cflowd auxiliary server statistics collection. The following is the sequence of high-level actions required to install and enable a Cflowd auxiliary server in a 5620 SAM system Install the Cflowd auxiliary server software; see 8.11 To install a 5620 SAM Cflowd auxiliary server (p. 191). If the 5620 SAM system is secured using SSL, enable SSL on the Cflowd auxiliary server; see 6.7 To enable SSL and HTTPS on a Cflowd auxiliary server (p. 80). Configure the Cflowd auxiliary server communication with the main servers and IPDR target file servers; see 8.12 To configure Cflowd auxiliary server communication (p. 194) To install a 5620 SAM Cflowd auxiliary server Description The following steps describe how to install the 5620 SAM Cflowd auxiliary server software on a station. Note: You require root user privileges on the Cflowd auxiliary server station. 3HE AAAG-TQZZA 191

192 To install a 5620 SAM Cflowd auxiliary server 5620 SAM 5650 CPAM Steps Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command Log in to the Cflowd auxiliary server station as the root user. Download the following 5620 SAM installation files to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm cflowdauxserver-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 5 6 Enter the following: # yum install samjre* cflowdauxserver* samconfig* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nnn M Installed size: nn M Is this ok [y/n]: Enter y. The following is displayed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded 192 3HE AAAG-TQZZA

193 5620 SAM 5650 CPAM To install a 5620 SAM Cflowd auxiliary server Running Transaction The package installation is complete when the following is displayed: Complete! When the package installation is complete, enter the following: # samconfig -m cflowdaux Enter the following: <cflowdaux> configure category category where category is the Cflowd auxiliary server data category, which is one of the following: sys, for system Cflowd statistics data aa, for AA Cflowd statistics data Enter the following: <cflowdaux> apply The configuration is applied. Enter the following: <cflowdaux> exit The samconfig utility closes. Perform one of the following. a. If you are installing a new Cflowd auxiliary server: 1. Open the following file for viewing: /opt/5620sam/jboss-6.4.0/standalone/configuration/dcp/cfdruntime.properties 2. Locate the following line: com.alu.bsx.cfd.collector.uuid=uuid 3. Record the UUID value and store it in a secure location; the value is required for subsequent deployment operations. b. If you are re-installing an existing Cflowd auxiliary server: 1. Open the following file using a plain-text editor such as vi: /opt/5620sam/jboss-6.4.0/standalone/configuration/dcp/cfdruntime.properties 2. Locate the following line: com.alu.bsx.cfd.collector.uuid=uuid 3HE AAAG-TQZZA 193

194 To configure Cflowd auxiliary server communication 5620 SAM 5650 CPAM 3. Replace the UUID value with the value recorded during the previous installation or upgrade. 4. Save and close the file Enter the following to start the Cflowd auxiliary server: # /opt/5620sam/dcp/bin/dcpctl.sh start The Cflowd auxiliary server starts, and displays the following: Starting 5620 SAM Cflowd Auxiliary Server... The Cflowd auxiliary server is started when the following is displayed: 5620 SAM Cflowd Auxiliary Server is started successfully Close the console window. END OF STEPS 8.12 To configure Cflowd auxiliary server communication Description The following steps describe how to configure Cflowd auxiliary server communication with each 5620 SAM main server and target file server Steps 1 2 Use a browser to open one of the following: if SSL is not enabled: if SSL is enabled: where server is the Cflowd auxiliary server IP address or hostname If a login form opens, enter the required user credentials and click OK. Note: The default user credentials are available from technical support. The 5620 SAM Cflowd Auxiliary Server form opens. 3 Click on the Collector Configuration link. The Configuration page is displayed HE AAAG-TQZZA

195 5620 SAM 5650 CPAM To configure Cflowd auxiliary server communication 4 Configure the Collection Port parameter to specify the TCP port on the Cflowd auxiliary server station that is to receive the statistics data from NEs. 5 Click Save Configuration. Configure 5620 SAM parameters Click Configuration View. The Configuration page is displayed. Click on the 5620 SAM Configuration tab. The 5620 SAM Configuration page is displayed. Configure the parameters in the following table. Note: You must ensure that the user specified for the SFTP User Name or FTP User Name parameter has read and write access to each target file server directory named in the 5620 SAM IPDR File Transfer Policy. See the 5620 SAM System Administrator Guide for IPDR File Transfer Policy configuration information. Note: In a redundant 5620 SAM system, you must ensure that you set the Redundant parameter in the 5620 SAM-O Service panel to true. Table 85 Cflowd auxiliary server parameters, 5620 SAM Configuration tab Panel and parameters Description 5620 SAM-O Service User Name Password Use Secure HTTP (HTTPS) Redundant Reconnect Durable Reconnect Attempts Reconnect Delay Connection Timeout Transfer Option The 5620 SAM username for OSS operations The password of the 5620 SAM OSS user Specifies whether HTTPS is used Specifies whether the 5620 SAM system is a redundant deployment Specifies whether the Cflowd auxiliary server attempts to reconnect to the 5620 SAM after a connection failure Specifies whether the 5620 SAM JMS subscription is durable The number of times to attempt to reconnect to the 5620 SAM after a connection failure The time, in seconds, to wait between 5620 SAM reconnection attempts The time, in seconds, to wait for a response to a 5620 SAM connection attempt The method to use for file transfers from a 5620 SAM main server 3HE AAAG-TQZZA 195

196 To configure Cflowd auxiliary server communication 5620 SAM 5650 CPAM Table 85 Cflowd auxiliary server parameters, 5620 SAM Configuration tab (continued) Panel and parameters Description 5620 SAM Primary 5620 SAM Standby (required for redundant system) IP Address/Host name HTTP Port HTTPS Port JNDI Port SFTP Port SFTP User Name SFTP Password FTP Port FTP User Name FTP Password The public IP address or hostname of the main server The TCP port on the main server for non-secured OSS communication The TCP port on the main server for SSL-secured OSS communication The TCP port on the main server for JMS communication The TCP port on the main server for file transfers, if SSL is enabled The username required for SSL-secured file transfers from the main server The password required for SSL-secured file transfers from the main server The TCP port on the main server for file transfers, if SSL is not enabled The username required for non-secured file transfers from the main server The password required for non-secured file transfers from the main server 9 Click Save 5620 SAM Configuration. Configure IPDR file-transfer parameters Click Configuration View. The Configuration page is displayed. Click on the IPDR Configuration tab. The IPDR Configuration page is displayed. Configure the parameters in the following table. Note: If you set the Transfer Protocol parameter to Secure (SFTP), you must set the Port parameter to 22. Table 86 Cflowd auxiliary server parameters, IPDR Configuration tab Panel and parameters Enable Transfer Transfer Protocol IP Address / Host name Description Specifies whether IPDR file transfers to the target file server are enabled Specifies the file-transfer protocol for IPDR transfers to the target file server The IP address or hostname of the target file server 196 3HE AAAG-TQZZA

197 5620 SAM 5650 CPAM To configure Cflowd auxiliary server communication Table 86 Cflowd auxiliary server parameters, IPDR Configuration tab (continued) Panel and parameters Port Location User Password Description The TCP port that the target file server uses to receive IPDR file transfers A descriptive entry that uniquely identifies the location of the target file server The username required for IPDR file transfers to the target file server The password required for IPDR file transfers to the target file server 13 Click Save Configuration. Perform snapshot extraction 14 Click on the Operations tab. The Operations page is displayed. 15 CAUTION Service Disruption The Force Snapshot Extraction option consumes 5620 SAM main server resources. Ensure that you perform the step only during a period of low 5620 SAM system activity. Click Force Snapshot Extraction. The Cflowd auxiliary server extracts the managed network information from a main server specified on the 5620 SAM Configuration tab. 16 Close the browser. END OF STEPS 3HE AAAG-TQZZA 197

198 Auxiliary database installation workflow 5620 SAM 5650 CPAM Auxiliary database installation 8.13 Auxiliary database installation workflow Description CAUTION Stages Deployment Requirement A 5620 SAM auxiliary database requires multiple dedicated stations. You cannot install the auxiliary database software on a station if another 5620 SAM component is installed on the station. Note: You must set CPU speed scaling, or CPUfreq, to performance in the BIOS of each auxiliary database station, or the auxiliary database installation fails. See the RHEL power management documentation for information about enabling the performance CPUfreq governor on a station. Setting CPUfreq to performance effectively disables CPU speed scaling, so may result in greater energy consumption by a station. Deployment options This section describes how to do the following. Install and enable an auxiliary database in a new or existing 5620 SAM system; see Stages (p. 198). Add a new station to an existing auxiliary database; see 8.17 To add a station to an auxiliary database (p. 205). The following is the sequence of high-level actions required to install and enable an auxiliary database in a 5620 SAM system Perform 8.14 To prepare a station for auxiliary database installation (p. 199) on each auxiliary database station. Perform 8.15 To install the auxiliary database software (p. 201). Perform 8.16 To add an auxiliary database to a 5620 SAM system (p. 203) HE AAAG-TQZZA

199 5620 SAM 5650 CPAM To prepare a station for auxiliary database installation 8.14 To prepare a station for auxiliary database installation Description Steps The following steps describe how to configure a station in advance of 5620 SAM auxiliary database software installation. Note: You require root user privileges on the auxiliary database station. Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command Log in to the auxiliary database station as the root user. Download the following 5620 SAM installation files to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm vertica-v.w.x-y.x86_64.rhel6.rpm samauxdb-sam_r_r_revision-pp.x86_64.rpm VerticaSw_PreInstall.sh where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level V.w.x-y is a version number Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Enter the following: #./VerticaSw_PreInstall.sh The script displays configuration messages like the following: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... 3HE AAAG-TQZZA 199

200 To prepare a station for auxiliary database installation 5620 SAM 5650 CPAM INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... Checking Vertica DBA group samauxdb... Adding Vertica DBA group samauxdb... Checking Vertica user samauxdb... Adding Vertica user samauxdb... Changing ownership of the directory /opt/5620sam/samauxdb to samauxdb:samauxdb. Adding samauxdb to sudoers file. Changing ownership of /opt/5620sam/auxdb files. INFO: About to add setting to /etc/rc.d/rc.local... INFO: Completed adding setting to /etc/rc.d/rc.local... 6 If the script instructs you to perform a restart, perform the following steps. 1. Enter the following: # init 6 The station reboots. 2. When the reboot is complete, log in to the station as the root user. 3. Open a console window. 4. Navigate to the directory that contains the 5620 SAM installation files. 7 Enter the following: # yum install samjre* vertica* samauxdb* where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level V.w.x-y is a version number The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: 200 3HE AAAG-TQZZA

201 5620 SAM 5650 CPAM To install the auxiliary database software 8 9 Enter y. The following and a progress indicator are displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! When the package installation is complete, close the console window. END OF STEPS 8.15 To install the auxiliary database software Description The following steps describe how to install and initialize the 5620 SAM auxiliary database software Steps Note: You require root user privileges on each auxiliary database station. Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command Log in to any auxiliary database station as the root user. Open a console window. Enter the following: # cp /opt/5620sam/samauxdb/config/install.config.default /opt/5620sam/samauxdb/config/install.config Open the /opt/5620sam/samauxdb/config/install.config file using a plain-text editor such as vi. 3HE AAAG-TQZZA 201

202 To install the auxiliary database software 5620 SAM 5650 CPAM 5 Edit the following lines in the file to read: hosts=internal_ip1,internal_ip2...internal_ipn subnet=subnet_address export_hosts=internal_ip1[export_ip1],internal_ip2[export_ip2]... internal_ipn[export_ipn] where internal_ip1, internal_ip2...internal_ipn are the IP addresses that the stations use to communicate with each other subnet_address is the address of the subnet that the stations use for external communication export_ip1, export_ip2...export_ipn are the IP addresses that the stations use to communicate with the 5620 SAM servers Note: If the [export_ip] entry for a station is omitted, the station uses the internal_ip address for communication with the 5620 SAM servers. The following is an export_hosts configuration example: export_hosts= [ ], [ ], [ ] Save and close the install.config file. Enter the following: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh install The script sequentially prompts for the root user password of each auxiliary database station. Enter the required password at each prompt. The script installs the software on the station. 9 When the script execution is complete, perform the following steps on each auxiliary database station. 1. Log in to the station as the root user. 2. Open a console window. 3. Enter the following: # /etc/init.d/mcelogd start 4. Enter the following: # /etc/init.d/samauxdbproxy start Messages like the following are displayed: 202 3HE AAAG-TQZZA

203 5620 SAM 5650 CPAM To add an auxiliary database to a 5620 SAM system hh:mm:ss Day mm/dd/yy : Starting 5620 SAM Auxiliary DB Proxy... hh:mm:ss Day mm/dd/yy : Refer to log_file for startup status. 5. Close the console window. END OF STEPS 8.16 To add an auxiliary database to a 5620 SAM system Description The following steps describe how to enable an auxiliary database in a 5620 SAM system and configure the communication with each main server. CAUTION Steps Service Disruption This procedure requires a restart of each main server, which is service-affecting. Perform this procedure only during a scheduled maintenance period. Note: You must perform the procedure on each main server. In a redundant system, you must perform the procedure on the standby main server first. Note: After you perform the procedure: The existing AA statistics data automatically migrates from the 5620 SAM database to the auxiliary database. The auxiliary database begins to store new accounting and performance statistics data. No accounting or performance statistics data migration occurs, and the existing statistics are no longer retrievable. The auxiliary database begins to store new event timeline data. No event timeline data migration occurs, and the existing event timeline data is no longer retrievable. Note: The first performance statistics collection after the data migration does not include periodic counter values because the previous values are not included in the migration Log in to the main server station as the samadmin user. Open a console window. Perform the following steps to stop the main server. 3HE AAAG-TQZZA 203

204 To add an auxiliary database to a 5620 SAM system 5620 SAM 5650 CPAM 1. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 2. Enter the following: bash$./nmsserver.bash stop 3. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 4. The main server is stopped when the command displays the following: Application Server is stopped If the command displays a different message, wait five minutes and then return to Step 3 3. Do not proceed to the next step until the server is stopped Enter the following to switch to the root user: bash$ su - Enter the following: # samconfig -m main Enter the following: <main> configure auxdb enabled ip-list address1,address2,addressn exit where address1, address2...addressn are the IP addresses specified for 5620 SAM server communication in 8.15 To install the auxiliary database software (p. 201). Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. Enter the following to switch back to the samadmin user:: 204 3HE AAAG-TQZZA

205 5620 SAM 5650 CPAM To add a station to an auxiliary database # exit Enter the following to start the main server: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash start The main server creates the required database elements and begins the migration of statistics data, if any, to the auxiliary database. In the event that a statistics migration fails on any auxiliary database station, the migration is retried up to 10 times. If after 10 retries the migration remains unsuccessful, the main server shuts down and displays the following message: Failed to migrate Application Assurance statistics from main database to auxiliary database If the migration fails, you must do the following: 1. Restore the 5620 SAM database. 2. Resolve the cause of the migration failure. 3. Restart the stopped main server. 12 Close the console window. END OF STEPS 8.17 To add a station to an auxiliary database Purpose The following steps describe how to add a new station to an auxiliary database, for example, to accommodate network growth. 1 Add a hostname entry for the new station to the /etc/hosts file on each existing auxiliary database station, and to the /etc/hosts file on the new station. Note: A component hostname that you specify in an /etc/hosts file must be the full hostname returned by the hostname command, and not the short form. Note: Hostnames are case-sensitive. 2 Log in to the new auxiliary database station as the root user. 3HE AAAG-TQZZA 205

206 To add a station to an auxiliary database 5620 SAM 5650 CPAM 3 Download the following 5620 SAM installation files to an empty local directory: Note: The software release must match the software release of the existing auxiliary database. samjre-sam_r_r_revision-pp.x86_64.rpm vertica-v.w.x-y.x86_64.rhel6.rpm samauxdb-sam_r_r_revision-pp.x86_64.rpm VerticaSw_PreInstall.sh where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level V.w.x-y is a version number 4 5 Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 6 Enter the following: #./VerticaSw_PreInstall.sh The script displays output similar to the following: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters... INFO: Completed changing the current values of the kernel parameters... INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... Checking Vertica DBA group samauxdb HE AAAG-TQZZA

207 5620 SAM 5650 CPAM To add a station to an auxiliary database Adding Vertica DBA group samauxdb... Checking Vertica user samauxdb... Adding Vertica user samauxdb... Changing ownership of the directory /opt/5620sam/samauxdb to samauxdb:samauxdb. Adding samauxdb to sudoers file. Changing ownership of /opt/5620sam/auxdb files. INFO: About to add setting to /etc/rc.d/rc.local... INFO: Completed adding setting to /etc/rc.d/rc.local If the script instructs you to perform a restart, perform the following steps. 1. Enter the following: # init 6 The station restarts. 2. Log in to the station as the root user. 3. Open a console window. 4. Navigate to the directory that contains the auxiliary database software. Enter the following: # yum install samjre* vertica* samauxdb* where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level V.w.x-y is a version number The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. 3HE AAAG-TQZZA 207

208 To add a station to an auxiliary database 5620 SAM 5650 CPAM Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! When the package installation is complete, log in to an existing auxiliary database station as the root user. Open a console window. Enter the following: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh addnode internal_ip external_ip where internal_ip is the IP address from which the station communicates with the other auxiliary database stations external_ip is the IP address from which the station communicates with the 5620 SAM servers The script displays the following: Adding hosts(s) hostname to auxiliary database cluster... When you are prompted for the database user password, enter the password. When you are prompted for the root password of the new station, enter the password. 15 CAUTION Installation Failure If the addition of the station to the auxiliary database is interrupted, the installation fails and support intervention may be required. You must answer yes to the prompt described in this step. If the auxiliary database contains a large amount of data, the addition of the station may take 208 3HE AAAG-TQZZA

209 5620 SAM 5650 CPAM To add a station to an auxiliary database considerable time. In such a scenario, the following prompt is displayed: Do you want to continue waiting? (yes/no) [yes] Press to accept the default of yes. Note: The prompt may be displayed several times during the operation When the script execution is complete, open the /opt/5620sam/samauxdb/config/install.config file using a plain-text editor such as vi. Edit the following line in the file to read: hosts=internal_ip1,internal_ip2...internal_ipn,new_internal_ip where internal_ip1,internal_ip2...internal_ipn are the IP addresses of the existing auxiliary database stations new_internal_ip is the IP address from which the new station communicates with the other auxiliary database stations Edit the following line in the file to read: export_hosts=internal_ip1[export_ip1],internal_ip2[export_ip2]...internal_ipn[export_ipn],new_ internal_ip[new_export_ip] where internal_ip1[export_ip1],internal_ip2[export_ip2],internal_ipn[export_ipn] are the IP addresses of the existing auxiliary database stations new_internal_ip is the IP address from which the new station communicates with the other auxiliary database stations new_export_ip is the IP address from which the new station communicates with the 5620 SAM servers Save and close the install.config file. 20 Start the auxiliary database software on the new station. 1. Enter the following: # /etc/init.d/mcelogd start 2. Enter the following: # /etc/init.d/samauxdbproxy start 3HE AAAG-TQZZA 209

210 To add a station to an auxiliary database 5620 SAM 5650 CPAM Messages like the following are displayed: hh:mm:ss Day mm/dd/yy : Starting 5620 SAM Auxiliary DB Proxy... hh:mm:ss Day mm/dd/yy : Refer to log_file for startup status. 3. Close the console window Enter the following on the existing auxiliary database station: #./auxdbadmin.sh distributeconfig The updated auxiliary database configuration is distributed to each auxiliary database station. Enter the following: #./auxdbadmin.sh rebalance You are prompted for the database user password. Enter the password. You are prompted to confirm the rebalance operation. Enter YES. The rebalance operation begins. When the rebalance is complete, the following is displayed: Cluster rebalance completed. Press a key to continue... Press a key. Perform the following steps on each main server station. Note: In a redundant system, you must perform the steps on the standby main server station first. 1. Log in to the main server station as the samadmin user. 2. Open a console window. 3. Enter the following to navigate to the main server configuration directory: bash$ cd /opt/5620sam/server/nms/config 4. Enter the following to make a backup copy of the main server configuration file: bash$ cp nms-server.xml nms-server.xml.backup 5. Open the nms-server.xml file with a plain-text editor, for example, vi. 6. Locate the section that begins with the following tag: 210 3HE AAAG-TQZZA

211 5620 SAM 5650 CPAM To add a station to an auxiliary database <samauxdb 7. Edit the following line in the section to read: ipaddress="address_1,address_2...address_n,new_address" /> where address_1,address_2...address_n are the IP addresses of the existing auxiliary database stations new_address is the IP address from which the new station communicates with the 5620 SAM servers 8. Save and close the nms-server.xml file. 9. If you are configuring the standby main server in a redundant system, enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash force_restart The main server restarts. 10. If you are configuring a standalone main server, or the primary main server in a redundant system, enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash read_config The main server reads the updated configuration file and puts the change into effect. 27 Close the open console windows. END OF STEPS 3HE AAAG-TQZZA 211

212 To install and enable a 5620 SAM analytics server 5620 SAM 5650 CPAM Analytics server installation 8.18 To install and enable a 5620 SAM analytics server Description CAUTION Steps Deployment Restriction A 5620 SAM analytics server requires a dedicated station. You cannot install the analytics server software on a station if another 5620 SAM component is installed on the station. The following steps describe how to install the 5620 SAM analytics server software on a station. Note: You can install a 5620 SAM analytics server only in a 5620 SAM system that includes an operational auxiliary database. See Auxiliary database installation (p. 198) for auxiliary database installation information. Note: You require the following user privileges: on each main server station root on the standalone or primary main server station samadmin on the analytics server station root Note: Performing the procedure creates the samadmin user account in the sam user group on the analytics server station. Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands # root user bash$ samadmin user Install analytics server software 1 Log in as the root user on the station that is to be the analytics server station. 2 Download the following 5620 SAM installation files to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm 212 3HE AAAG-TQZZA

213 5620 SAM 5650 CPAM To install and enable a 5620 SAM analytics server tomcat-sam_r_r_revision-pp.x86_64.rpm samanalytics-r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level 3 4 Open a console window. Navigate to the directory that contains the 5620 SAM installation files: Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 5 6 Enter the following: # yum install samjre* tomcat* samanalytics* For each package, the yum utility resolves any package dependencies and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as the package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Configure analytics server 7 Enter the following to switch to the samadmin user: # su - samadmin 3HE AAAG-TQZZA 213

214 To install and enable a 5620 SAM analytics server 5620 SAM 5650 CPAM Enter the following: bash$ cd /opt/5620sam/analytics/bin Enter the following: bash$./analyticsadmin.sh updateconfig The script displays the following messages and prompt: Copyright Nokia Inc. All rights reserved THIS ACTION UPDATES /opt/5620sam/analytics/config/install.config Please type 'YES' to continue Enter YES. The script displays a series of prompts. At each prompt, enter a parameter value; to accept a default in brackets, press. The following table lists and describes each parameter. Table 87 Parameter 5620 SAM analytics server installation parameters Description Repository Database Primary DB HOST IP Address Repository Database Primary DB Port Repository Database Primary DB Instance Name Secondary DB host Secondary DB Port Repository Database Secondary DB Instance Name Auxiliary DB Host for JNDI Connection The IP address of the primary or standalone 5620 SAM database The TCP port on the primary or standalone 5620 SAM database station that receives database requests The primary or standalone 5620 SAM database instance name The standby 5620 SAM database IP address In a standalone 5620 SAM system, press to leave the parameter unconfigured. The TCP port on the standby 5620 SAM database station that receives database requests The standby 5620 SAM database instance name The IP address of an auxiliary database station If the 5620 SAM system does not include an auxiliary database, press to leave the parameter unconfigured HE AAAG-TQZZA

215 5620 SAM 5650 CPAM To install and enable a 5620 SAM analytics server Table SAM analytics server installation parameters (continued) Parameter Auxiliary DB Backup Node1 JNDI Connection Auxiliary DB Backup Node2 JNDI Connection Auxiliary DB Port for JNDI Connection Description The IP address of an auxiliary database station If the 5620 SAM system does not include an auxiliary database, press to leave the parameter unconfigured. The IP address of an auxiliary database station If the 5620 SAM system does not include an auxiliary database, press to leave the parameter unconfigured. The TCP port on each auxiliary database station that receives database requests 12 Enter the following to install the analytics server software: bash$./analyticsadmin.sh install Note: The analytics server starts automatically after the installation. The following is displayed: Copyright Nokia Inc. All rights reserved Installing 5620 SAM Analytics Server... Does this 5620 SAM Analytics Server require support for SSL? [YES/NO] 13 Perform one of the following. a. Enable SSL on the analytics server. 1. Enter YES. The following prompt is displayed: Enter SSL Certificate Path: 2. Enter the absolute path of the SSL certificate file. Note: The certificate file must be on the local file system. If the path is correct, the following message and prompt are displayed: path/certificate_file found. Enter SSL Certificate Password: 3. Enter the certificate password. The following and status messages are displayed as the installation progresses: SSL Config has been updated b. Do not enable SSL on the analytics server; enter NO. The following status messages are displayed as the installation progresses: 3HE AAAG-TQZZA 215

216 To install and enable a 5620 SAM analytics server 5620 SAM 5650 CPAM Creating Analytics Repository Schema Analytics Repository Schema creation is complete Please wait while 5620 SAM Analytics Server is being installed...this may take a few minutes Deploying 5620 SAM Analytics Server in Tomcat SAM Analytics Server successfully deployed in Tomcat Starting 5620 SAM Analytics Server SAM Analytics Server successfully started! Configuring 5620 SAM Analytics Server... Tracking nn reports... All reports successfully tracked 5620 SAM Analytics Server configured successfully 5620 SAM Analytics Server successfully installed Enter the following to view the analytics server status: bash$./analyticsadmin.sh status The following is displayed: Copyright Nokia Inc. All rights reserved 5620 SAM Analytics Server Version : Release 5620 SAM Analytics Application is running with pid: nnnnn Close the console window. Add analytics server to 5620 SAM system 16 Perform the following steps on each main server station. 1. Log in to the main server as the root user. 2. Open a console window. 3. Enter the following: # samconfig -m main 4. Enter the following: <main> configure analytics ip-list current_list,new_address exit where current_list is a comma-separated list of the current analytics server IP addresses 216 3HE AAAG-TQZZA

217 5620 SAM 5650 CPAM To install and enable a 5620 SAM analytics server 17 new_address is the IP address of the new analytics server that is accessible to the other 5620 SAM components 5. Enter the following: <main> apply The configuration is applied. 6. Enter the following: <main> exit The samconfig utility closes. Perform the following steps on the standalone main server, or the primary main server in a redundant deployment. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash webforce_restart The 5620 SAM web server restarts, and the analytics server is enabled in the 5620 SAM system. 18 Close the open console windows. END OF STEPS 3HE AAAG-TQZZA 217

218 To install and enable a 5620 SAM analytics server 5620 SAM 5650 CPAM 218 3HE AAAG-TQZZA

219 5620 SAM 5650 CPAM 5620 SAM upgrade SAM upgrade 9.1 Overview Purpose This chapter describes how to upgrade the components of a standalone or redundant 5620 SAM system Contents 9.1 Overview 219 Introduction General information To perform the pre-upgrade tasks 221 Standalone 5620 SAM system upgrade Standalone system upgrade workflow To upgrade a standalone 5620 SAM system 231 Redundant 5620 SAM system upgrade Component references Redundant system upgrade workflow To upgrade a redundant 5620 SAM system 253 Auxiliary server upgrade To upgrade a 5620 SAM auxiliary server 281 Cflowd auxiliary server upgrade To upgrade a 5620 SAM Cflowd auxiliary server 284 Auxiliary database upgrade To upgrade a 5620 SAM auxiliary database 291 Analytics server upgrade To upgrade a 5620 SAM analytics server 297 3HE AAAG-TQZZA 219

220 General information 5620 SAM 5650 CPAM Introduction 9.2 General information Description CAUTION Service Disruption A 5620 SAM system upgrade fails unless the requirements and restrictions described in Chapter 2, Before you begin and the 5620 SAM Planning Guide are observed. Performing a 5620 SAM system upgrade requires a thorough understanding of the upgrade restrictions and requirements. It is essential that you plan, document, and test the upgrade procedure in advance on a lab system that is representative of the actual network. Contact technical support to assess the upgrade requirements for your 5620 SAM system. It is strongly recommended that you engage the technical support upgrade service for a system upgrade in a large or complex network. This chapter describes standalone and redundant 5620 SAM system upgrades, and the upgrade of the following optional 5620 SAM components: auxiliary server Cflowd auxiliary server auxiliary database analytics server Chapter 13, Single-user client deployment and Chapter 14, Client delegate server deployment describe single-user GUI client and client delegate server installation and upgrade. The 5620 SAM samconfig utility is used for component configuration and deployment; see Chapter 3, Using samconfig for information about the samconfig utility. Before you attempt a 5620 SAM system upgrade, you must perform 9.3 To perform the preupgrade tasks (p. 221) to collect the required information and ensure that the required conditions are in place. Table SAM upgrade procedures list Procedure Purpose 9.3 To perform the pre-upgrade tasks (p. 221) Prepare a standalone or redundant 5620 SAM system for a software upgrade by ensuring the correct conditions are in place, gathering the required system information, and backing up the configuration files and database. 9.5 To upgrade a standalone 5620 SAM system (p. 231) Upgrade the 5620 SAM database and server software in a standalone configuration on one or more stations. 9.8 To upgrade a redundant 5620 SAM system (p. 253) Upgrade the 5620 SAM database and server software in a redundant deployment HE AAAG-TQZZA

221 5620 SAM 5650 CPAM To perform the pre-upgrade tasks Table SAM upgrade procedures list (continued) Procedure Purpose 9.9 To upgrade a 5620 SAM auxiliary server (p. 281) Upgrade the auxiliary server software on a station in a standalone or redundant 5620 SAM system To upgrade a 5620 SAM Cflowd auxiliary server (p. 284) Upgrade the Cflowd auxiliary server software on a station in a standalone or redundant 5620 SAM system To upgrade a 5620 SAM auxiliary database (p. 291) Upgrade the auxiliary database software To upgrade a 5620 SAM analytics server (p. 297) Upgrade the analytcis server software. 9.3 To perform the pre-upgrade tasks Description NOTICE Special Upgrade Requirement Upgrading from 12.0 R4 or earlier A 5620 SAM system upgrade from a release earlier than 12.0 R5 has special requirements. To ensure the upgrade success, you must prepare for the upgrade, as described in 2.4 Upgrading from Release 12.0 R4 or earlier (p. 17) The following steps describe the actions that you must perform in advance of a standalone or redundant 5620 SAM system upgrade. Note: You require the following user privileges on each main and auxiliary server station: root samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 3HE AAAG-TQZZA 221

222 To perform the pre-upgrade tasks 5620 SAM 5650 CPAM Steps Check firewall configuration 1 CAUTION Misconfiguration Risk If the RHEL iptables / ip6tables firewall is enabled on a station, 5620 SAM software installation fails. Before a 5620 SAM system upgrade, you must ensure that the RHEL iptables / ip6tables firewall on each station is disabled. If you plan to deploy a RHEL iptables / ip6tables firewall for the first time in the 5620 SAM system, ensure that the firewall is disabled before and during the upgrade. You can enable and configure the iptables / ip6tables firewall after the upgrade. Validate database 2 Before you upgrade a 5620 SAM database, you must ensure that the database contains only valid records, or the upgrade fails. Perform the following steps. Note: In a redundant system, you must perform the steps on the primary database station. 1. Log on to the database station as the root user. 2. Download the OracleSw_PreInstall.sh file for the new 5620 SAM release. 3. Navigate to the directory that contains the OracleSw_PreInstall.sh file. 4. Enter the following: #./OracleSw_PreInstall.sh -check The following message is displayed: Logging Oracle pre install checks to log_file In upgrade check mode, this script does not modify the system. About to validate that the database can be upgraded to release. Found the 5620 SAM database installation directory /opt/5620sam/samdb/install. 5. If the validation is successful, the following messages and prompt are displayed: INFO: Database upgrade validation passed. Go to Step If the script detects one or more invalid items, for example, an NE at a release that the new 222 3HE AAAG-TQZZA

223 5620 SAM 5650 CPAM To perform the pre-upgrade tasks 5620 SAM software does not support, an incomplete deployment, or other upgrade restriction, one line like the following is displayed for each item: ERROR: Error message The following is displayed as the script exits. ERROR: The database cannot be upgraded. Please fix the above errors and re-run this script. Remove the upgrade restriction. For example, use a 5620 SAM client to clear an incomplete deployment or upgrade an unsupported NE to a release that the new software supports. 7. Run the script again; go to Step 2 substep 3. Verify database archive log synchronization 3 If the 5620 SAM system is redundant, ensure that no database archive log gap exists between the primary and standby 5620 SAM databases. Note: If you attempt a database upgrade when an archive log gap exists, the upgrade fails. 1. Open a 5620 SAM GUI client. 2. View the Standby DB entry in the GUI status bar. 3. If the entry reads Database archive log gap, you must reinstantiate the standby database. Otherwise, go to Step Choose Administration System Information from the 5620 SAM main menu. The System Information form opens. 5. Click Re-Instantiate Standby. 6. Click Yes to confirm the action. The reinstantiation begins, and the GUI status bar displays reinstantiation information. Note: Database reinstantiation takes considerable time if the database contains a large amount of statistics data. You can also use the System Information form to monitor the reinstantiation progress. The Last Attempted Standby Re-instantiation Time is the start time; the Standby Re-instantiation State changes from In Progress to Success when the reinstantiation is complete. 7. When the reinstantiation is complete, close the System Information form. 3HE AAAG-TQZZA 223

224 To perform the pre-upgrade tasks 5620 SAM 5650 CPAM Back up database 4 CAUTION Data Loss The path of the 5620 SAM database backup directory must not include the 5620 SAM database installation directory, or data loss may occur. Ensure that the backup directory path that you specify does not include /opt/5620sam/samdb. Note: Before the 5620 SAM performs a database backup, it deletes the contents of the specified backup directory. Ensure that the backup directory that you specify does not contain files that you want to retain. You must perform a database backup before you perform a 5620 SAM upgrade. Perform one of the following 5620 SAM System Administrator Guide procedures to back up the 5620 SAM database: To back up the 5620 SAM database from the client GUI To back up the 5620 SAM database from a CLI Perform 9500 MPR migration pre-upgrade tasks 5 CAUTION Management Disruption A 5620 SAM system that manages 9500 MPR devices requires special configuration for an upgrade from a release earlier than 14.0 R7; otherwise, the upgraded 5620 SAM cannot manage the devices. To ensure continued 9500 MPR management after the upgrade, you must perform the procedure described in this step. See 9500 MPR migration to revised service model in the 9500 MPR User Guide for more information. If you are upgrading from a 5620 SAM release earlier than 14.0 R7, and the 5620 SAM system manages one or more 9500 MPR devices, perform To perform pre-upgrade tasks in the 9500 MPR User Guide. Verify compatibility with external systems 6 Ensure that the new 5620 SAM software is compatible with the software release of each external system that connects to the 5620 SAM. Contact technical support for information about 5620 SAM and external system compatibility HE AAAG-TQZZA

225 5620 SAM 5650 CPAM To perform the pre-upgrade tasks Close LogViewer 7 Close the LogViewer utility, if it is open. Validate main server and GUI client firewall configuration 8 Confirm that the firewalls between the main servers and the single-user GUI clients and client delegate servers allow traffic to the HTTP or HTTPS port required for client updates. Otherwise, you cannot install or upgrade a single-user client or client delegate server. See Chapter 6, Configuring SSL security for 5620 SAM HTTP and HTTPS port configuration information. Verify 5620 SAM policy compatibility with managed NEs 9 You must confirm that the new 5620 SAM release supports the software release of each managed NE and pre-provisioned NE, as stated in the 5620 SAM Network Element Compatibility Guide. Perform one of the following for each NE that is at an unsupported release. Note: If a 5620 SAM system that is to be upgraded manages an NE as a GNE, and the new 5620 SAM release supports native management of the device type and release, you must unmanage and delete the GNE from the 5620 SAM before a 5620 SAM system upgrade. After the upgrade, the 5620 SAM can discover and manage the device as a native NE instead of a GNE. a. Upgrade the device software to a release that the new 5620 SAM software supports; see the appropriate device documentation and the 5620 SAM User Guide for information about performing NE software upgrades. b. Remove the NE from the 5620 SAM managed network; see the Discovering devices using the 5620 SAM chapter of the 5620 SAM User Guide for information. 1. Unmanage the NE. 2. Delete the NE from the managed network. 3. Administratively disable or remove the discovery rule element for the NE. c. Delete the pre-provisioned NE using the 5620 SAM Pre-Provisioned NE Manager; see the Self-configuration and discovery chapter of the 5620 SAM LTE RAN User Guide. 3HE AAAG-TQZZA 225

226 To perform the pre-upgrade tasks 5620 SAM 5650 CPAM Back up configuration files 10 CAUTION Service Disruption A 5620 SAM upgrade does not preserve all non-default settings in configuration files such as nms-server.xml. If a 5620 SAM configuration file contains non-default settings that you want to retain after an upgrade, contact technical support for assistance before the upgrade. Note: At the beginning of a 5620 SAM main or auxiliary server upgrade, specific configuration and log files are copied to a directory under the installation directory; the directory name includes a timestamp. The directories below the main server installation directory are then deleted. If you have created or customized a file below the main server installation directory, you risk losing the file unless you creat a backup copy. Make a backup copy of each file that you have created or customized in or below the /opt/ 5620sam/server directory on each main server station, and store the backup files in a secure location that is unaffected by 5620 SAM upgrade activity. 11 If the 5620 SAM system currently manages Small Cell NEs, perform one of the following to back up the Small Cell files. Note: You must back up the files on each main and auxiliary server that has a Small Cell configuration. a. If you are upgrading from Release 12.0 R5 or R6, perform the following steps. 1. Log in to the main or auxiliary server station as the root user. 2. Create the /smallcell/config directory. 3. Copy the following files to the /smallcell/config directory: /opt/5620sam/server/nms/config/nms-femto.xml /opt/5620sam/server/nms/config/femto/fsconf/config/nms-femto.xml.backup /opt/5620sam/server/nms/config/femto/fsconf/config/sshd_config.backup b. If you are upgrading from Release 12.0 R7 or later, perform the following steps. 1. Log in to the main or auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/server/nms/config/femto/fsconf/fsbackup.sh all path where path is the backup directory, and is optional; the default is /smallcell/backup Note: 226 3HE AAAG-TQZZA

227 5620 SAM 5650 CPAM To perform the pre-upgrade tasks The path that you specify must not include a trailing slash (/) character. Clear 5650 CPAM checkpoints 12 A 5620 SAM main server upgrade requires additional time if 5650 CPAM checkpoints are retained. The additional time varies, depending on the platform resources, managed network size, and checkpoint schedule. To reduce the upgrade time, remove the 5650 CPAM checkpoints, as described in the 5620 CPAM User Guide. Gather required information Choose Administration System Information from the 5620 SAM main menu. The System Information form opens. Record the following information: Domain Name Primary Server panel: IP Address Host Name Status Primary Database Server panel: Database Name Instance Name IP Address Host Name If the 5620 SAM is deployed as a redundant system, record the following additional information: Standby Server panel: IP Address Host Name Status Standby Database Server panel: Database Name Instance Name IP Address Host Name 3HE AAAG-TQZZA 227

228 To perform the pre-upgrade tasks 5620 SAM 5650 CPAM 16 If the 5620 SAM system includes one or more auxiliary servers, click on the Auxiliary Services tab. A list of auxiliary servers is displayed. Otherwise, go to Step Perform the following steps for each auxiliary server listed on the form. 1. Select the auxiliary server and click Properties. The auxiliary server properties form opens. 2. Record the following information for use during the upgrade: Host Name Auxiliary Server Type Server Status Public IP address Private IP address, if displayed 3. Close the auxiliary server properties form. Record which auxiliary servers have a check mark in the Selected column. Note: The Selected auxiliary servers are collectively referred to as [Aux1] in 9.8 To upgrade a redundant 5620 SAM system (p. 253); the remaining auxiliary servers are collectively referred to as [Aux2] If the 5620 SAM system includes one or more client delegate servers, click on the Client Delegate Servers tab. Otherwise, go to Step 21. Perform the following steps for each client delegate server listed on the form: 1. Select the client delegate server and click Properties. The client delegate server properties form opens. 2. Record the IP Address value for use during the upgrade. 3. Close the properties form. Close the System Information form. Obtain the following main server information and record it for use during the upgrade: additional main server IP addresses, if NAT or multiple interfaces are used: IP address that each 5620 SAM database must use to reach the main server IP address that the 5620 SAM GUI and OSS clients must use to reach the main server; the public IP address, if NAT is used 228 3HE AAAG-TQZZA

229 5620 SAM 5650 CPAM To perform the pre-upgrade tasks IP address that the auxiliary servers must use to reach the main server private IP address, if NAT is used root user password 23 Obtain the following 5620 SAM database information and record it for use during the upgrade: additional database IP addresses, if NAT or multiple interfaces are used: IP address that each main server uses to reach the database IP address that the auxiliary servers use to reach the database root user password Oracle management user information: username; default at installation is oracle group name; default at installation is dba Oracle database user name; default at installation is samuser Oracle database user password Oracle SYS password Close client sessions Close the open 5620 SAM GUI and OSS client sessions, as required. 1. Open a 5620 SAM GUI client using an account with security management privileges, such as admin. 2. Choose Administration Security 5620 SAM User Security from the 5620 SAM main menu. The 5620 SAM User Security - Security Management (Edit) form opens. 3. Click on the Sessions tab. 4. Click Search. The form lists the open 5620 SAM GUI and OSS client sessions. 5. Identify the GUI session that you are using based on the value in the Client IP column. 6. Select all sessions except for the following: the session that you are using the sessions required to monitor the network during a redundant system upgrade 7. Click Close Session. 8. Click Yes to confirm the action. 9. Click Search to refresh the list and verify that only the required sessions are open. 10. Close the 5620 SAM User Security - Security Management (Edit) form. If the GUI client that you are using is not required for network monitoring during the system upgrade, close the client. END OF STEPS 3HE AAAG-TQZZA 229

230 Standalone system upgrade workflow 5620 SAM 5650 CPAM Standalone 5620 SAM system upgrade 9.4 Standalone system upgrade workflow Description The following is the sequence of high-level actions required to upgrade a standalone 5620 SAM system Stages Note: The links in the Upgrade standalone system (p. 230) stages lead to sections in 9.5 To upgrade a standalone 5620 SAM system (p. 231). Prepare system for upgrade 1 Perform 9.3 To perform the pre-upgrade tasks (p. 221) to prepare the 5620 SAM system for the upgrade. Upgrade standalone system Download the required 5620 SAM installation files and distribute the files to the stations in the system, as required; see Download and distribute 5620 SAM installation files (p. 232). If the 5620 SAM system includes one or more Cflowd auxiliary servers or analytics servers, stop each server; see Stop analytics servers, Cflowd auxiliary servers (p. 233). Prepare the main server for the upgrade; see Stop standalone main server, prepare station for upgrade (p. 234). 1. Stop the main server. 2. Disable automatic main server startup. 3. Verify the local file system resources. Upgrade the 5620 SAM database; see Upgrade standalone 5620 SAM database (p. 235). 1. Stop the 5620 SAM database. 2. Run a script to prepare for the Oracle software installation. 3. Install the required packages. 4. Run the database upgrade script HE AAAG-TQZZA

231 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system 5. Verify and modify the database configuration, as required If the 5620 SAM system includes one or more auxiliary servers, stop the auxiliary servers; see Stop auxiliary servers (p. 241). Upgrade the main server; see Upgrade standalone main server (p. 241). If the 5620 SAM system includes one or more auxiliary servers, upgrade each auxiliary server; see Upgrade auxiliary servers (p. 243). If the 5620 SAM system includes one or more Cflowd auxiliary servers, upgrade each Cflowd auxiliary server; see Upgrade Cflowd auxiliary servers (p. 244). If the 5620 SAM system includes an auxiliary database, upgrade the auxiliary database; see Upgrade auxiliary database (p. 244). If the 5620 SAM system includes one or more auxiliary servers, start each auxiliary server; see Start auxiliary servers (p. 244). Start the main server; see Start main server (p. 244). If the 5620 SAM system includes one or more analytics servers, upgrade each analytics server; see Upgrade analytics servers (p. 245). Upgrade or install the 5620 SAM GUI client software, as required; see Upgrade or install GUI clients (p. 245). 9.5 To upgrade a standalone 5620 SAM system Description The following steps describe how to upgrade a collocated or distributed 5620 SAM database and main server in a standalone deployment. The steps include links to procedures for installing and upgrading optional 5620 SAM components. 3HE AAAG-TQZZA 231

232 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM Steps Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. Note: You require the following user privileges: on each main and auxiliary server station root, samadmin on the 5620 SAM database station root, database_user Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 1 Open at least one 5620 SAM GUI client to monitor the network before the upgrade. Download and distribute 5620 SAM installation files 2 3 Download the following 5620 SAM installation files: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm samauxserver-sam_r_r_revision-pp.x86_64.rpm, if the system includes auxiliary servers where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Copy the following files to an empty directory on each main server, database, and auxiliary server station: Note: In subsequent steps, the directory is called the 5620 SAM software directory. samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm 232 3HE AAAG-TQZZA

233 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system 4 Perform one of the following. a. In a distributed 5620 SAM system: 1. Copy the following files to the 5620 SAM software directory on the database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh 2. Copy the following file to an empty directory on the main server station: samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm b. In a collocated 5620 SAM system, copy the following files to the 5620 SAM software directory on the main server and database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm 5 If the 5620 SAM system includes one or more auxiliary servers, copy the following file to the 5620 SAM software directory on each auxiliary server station: samauxserver-sam_r_r_revision-pp.x86_64.rpm Stop analytics servers, Cflowd auxiliary servers 6 7 If the 5620 SAM system includes one or more analytics servers, stop each analytics server. 1. Log in to the analytics server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/analytics/bin/analyticsadmin.sh stop The following is displayed: Stopping 5620 SAM Analytics Server When the analytics server is completely stopped, the following message is displayed: 5620 SAM Analytics Server is not running If the 5620 SAM system includes one or more Cflowd auxiliary servers, stop each Cflowd auxiliary server. 1. Log in to the Cflowd auxiliary server station as the root user. 3HE AAAG-TQZZA 233

234 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM 2. Open a console window. 3. Navigate to the Cflowd auxiliary server installation directory, which is one of the following: Release 14.0 R5 or earlier /opt/5620sam/dcp-r_rrn, where R_rRn is the software release identifier Release 14.0 R6 or later /opt/5620sam/dcp 4. Enter the following: #./bin/dcpctl.sh stop Output like the following is displayed. Stopping 5620 SAM Cflowd Auxiliary Server SAM Cflowd Auxiliary Server is stopped successfully Stop standalone main server, prepare station for upgrade 8 9 Stop the main server. 1. Log in to the main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following to stop the main server: bash$./nmsserver.bash stop 5. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 6. The main server is stopped when the command displays the following status message: Application Server is stopped If the command displays a different message, wait five minutes and return to Step 8 5. Do not proceed to the next step until the main server is stopped. Disable the automatic main server startup so that the main server does not start in the event of a power disruption during the upgrade. 1. Enter the following to switch to the root user: bash$ su - 2. Enter the following: # cd /etc/init.d 3. Enter the following to rename the main server startup daemon: # mv 5620SAMServerWrapper inactive.5620samserverwrapper 234 3HE AAAG-TQZZA

235 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system 10 If the 5620 SAM system manages more than 3000 NEs, ensure that sufficient inodes are available for the upgrade. 1. Enter the following: # df -i /opt/5620sam/server/nms/bin/depl/mediation The command returns output similar to the following: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda % /opt/5620sam 2. If the IUse% value is greater than 40%, enter the following to remove the mediation files: # rm -r /opt/5620sam/server/nms/bin/depl/mediation Note: The command may take several minutes to complete. Upgrade standalone 5620 SAM database Stop the 5620 SAM database and database proxy. 1. Log in to the database station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following to stop the Oracle proxy: #./S965620SAMOracleProxyWrapper stop 5. Enter the following to stop the 5620 SAM database: #./S95db5620sam stop Do not proceed until the following is displayed: Shutting down Oracle... Done. Perform the following steps to disable the automatic database proxy startup. 1. Enter the following: # cd /etc/init.d 2. Enter the following: # mv 5620SAMOracleProxyWrapper inactive.5620samoracleproxywrapper Navigate to the directory that contains the new 5620 SAM installation files. 3HE AAAG-TQZZA 235

236 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 14 CAUTION Misconfiguration Risk The 5620 SAM software includes a script that configures the Oracle environment. The script is specific to a 5620 SAM release; using a different version may cause the database creation to fail. You must run only the script that is included with the new 5620 SAM software. Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. Note: If you specify a value other than the default, you must record the value for use when the OracleSw_PreInstall.sh script is run during a software upgrade, or when the Oracle management user information is required by technical support. The following prompt is displayed: This script will prepare the system for an upgrade to 5620 SAM Version R.r Rn database. Do you want to continue? [Yes/No]: Enter Yes. The following messages and prompt are displayed: About to validate that the database can be upgraded to release. Found the SAM database installation directory /opt/5620sam/samdb/install. Existing SAM database version = version Enter the password for the "SYS" Oracle user (terminal echo is off): Enter the SYS user password. The script begins to validate the database records, and displays the following: Validating the database for upgrade. Please wait... If the validation is successful, the following messages and prompt are displayed: INFO: Database upgrade validation passed. Creating group group if it does not exist HE AAAG-TQZZA

237 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1... Checking user username... usermod: no changes Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Do you want to change the password for the UNIX user username? [Yes/No]: Go to Step If the database contains an invalid item, for example, an NE at a release that the new 5620 SAM software does not support, the following is displayed and the script exits: ERROR: Unsupported records found in database. Please remove the following unsupported items first: Please remove the following unsupported items first: item_1 item_2.. item_n ERROR: The database cannot be upgraded. Please fix the above errors and re-run this script. Perform the following steps. 1. Use a 5620 SAM client to remove or update the unsupported items, as required. For example, upgrade an unsupported NE to a release that the new software supports. 2. Run the script again; go to Step Perform one of the following. a. Enter No to retain the current password. b. Specify a new password. 1. Enter Yes. The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: 3HE AAAG-TQZZA 237

238 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM Re-enter new Password: 3. Re-enter the password. The following is displayed if the password change is successful: passwd: password successfully changed for username The following message and prompt are displayed: Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to remove kernel parameters set by a previous run of this script from /etc/sysctl.conf INFO: Completed removing kernel parameters set by a previous run of this script from /etc/sysctl.conf INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to remove ulimit parameters set by a previous run of this script from /etc/security/limits.conf INFO: Completed removing ulimit parameters set by a previous run of this script from /etc/security/limits.conf INFO: About to set ulimit parameters in etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... INFO: Completed running Oracle Pre-Install Tasks When the script execution is complete, enter the following to reboot the database station: # init 6 The station reboots. When the reboot is complete, log in to the 5620 SAM database station as the root user HE AAAG-TQZZA

239 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system Open a console window. Enter the following to stop the database: # /etc/rc3.d/s95db5620sam stop Do not proceed until the following is displayed: Shutting down Oracle... Done. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Perform one of the following. a. If the main server and database are on separate stations, enter the following: # yum install samjre* samconfig* samoracle* samdb* b. If the main server and database are collocated on one station, enter the following: # yum install samjre* samconfig* samoracle* samdb* samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 3HE AAAG-TQZZA 239

240 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM 27 Enter the following to upgrade the database: # samupgradedb The following prompt is displayed: Enter the password for the "user" database user (terminal echo is off): 28 Enter the database user password. The following is displayed as the database upgrade begins: Validating... Note: A database upgrade may take considerable time When the upgrade is complete, verify the database configuration. 1. Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> 2. Enter the following: <db> show-detail The database configuration is displayed. 3. Review each parameter to ensure that the value is correct. 4. Configure one or more parameters, if required, and then enter back ; see Chapter 3, Using samconfig for information about using the samconfig utility. 5. If you change one or more parameters, enter the following: <db> apply The configuration is applied. 6. Enter the following: <db> exit The samconfig utility closes. It is recommended that as a security measure, you limit the number of database user login failures that the 5620 SAM allows before the database user account is locked; see 5620 SAM database management procedures in the 5620 SAM System Administrator Guide HE AAAG-TQZZA

241 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system Note: You do not need to perform the step if the database has been configured before the upgrade to limit the user login failures. Stop auxiliary servers 31 If the 5620 SAM system includes one or more auxiliary servers, stop each auxiliary server. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop The 5620 SAM auxiliary server stops. Upgrade standalone main server Log into the main server station as the root user. Open a console window. Ensure that there are no active samadmin user sessions. 1. Enter the following: # who The active user sessions are listed. 2. If the samadmin user is listed, close each samadmin user session; see the RHEL documentation for information about closing user sessions. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 36 If the main server and database are on separate stations, perform the following steps: 1. Enter the following: # yum install samjre* samconfig* samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G 3HE AAAG-TQZZA 241

242 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM Installed size: nn G Is this ok [y/n]: 2. Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following; see Chapter 3, Using samconfig for information about using samconfig: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure The prompt changes to <main configure>. To apply a new or updated 5620 SAM license, enter the following, and then enter back : Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file in this step, or later import the license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. <main configure> license license_file where license_file is the absolute path of the 5620 SAM license zip file 40 Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct HE AAAG-TQZZA

243 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main> Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. If one of the following is true, perform 7.3 To enable Small Cell management (p. 94) on the main server station: You need to enable Small Cell NE management for the first time. The 5620 SAM currently manages Small Cell NEs. If you are upgrading from a 5620 SAM release earlier than 12.0 R5, create a directory on the main server for backing up the stored NE configurations. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup 3. Enter the following to switch back to the root user: bash$ exit Upgrade auxiliary servers 45 If the 5620 SAM system includes one or more auxiliary servers, perform 9.9 To upgrade a 5620 SAM auxiliary server (p. 281) on each auxiliary server station. Note: Do not perform the final step that describes starting the auxiliary server. 3HE AAAG-TQZZA 243

244 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM Upgrade Cflowd auxiliary servers 46 If the 5620 SAM system includes one or more Cflowd auxiliary servers, perform 9.10 To upgrade a 5620 SAM Cflowd auxiliary server (p. 284) on each Cflowd auxiliary server station. Upgrade auxiliary database 47 If the 5620 SAM system includes an auxiliary database, perform 9.11 To upgrade a 5620 SAM auxiliary database (p. 291). Start auxiliary servers 48 If the 5620 SAM system includes one or more auxiliary servers, start each auxiliary server. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following to start the auxiliary server: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The 5620 SAM auxiliary server starts. Start main server 49 Start the main server. Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file, or import a license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following to start the main server: bash$./nmsserver.bash start 4. Enter the following: bash$./nmsserver.bash -s nms_status The command returns server status information HE AAAG-TQZZA

245 5620 SAM 5650 CPAM To upgrade a standalone 5620 SAM system If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following: -- SAM Server is UP 5. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed to the next step until the server is completely started. 50 Close the console window. Upgrade analytics servers 51 If the 5620 SAM system includes one or more analytics servers, perform 9.12 To upgrade a 5620 SAM analytics server (p. 297) on each analytics server station. Upgrade or install GUI clients If you modify the SSL configuration during a main server upgrade, you cannot upgrade a 5620 SAM single-user GUI client or client delegate server that connects to the main server until you uninstall the current client software and install the new client software with the appropriate SSL settings. As required, perform the appropriate uninstallation procedures in the following chapters: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server Perform the appropriate procedures in the following chapters to install or upgrade 5620 SAM single-user GUI clients or client delegate servers, as required: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server 3HE AAAG-TQZZA 245

246 To upgrade a standalone 5620 SAM system 5620 SAM 5650 CPAM Perform 9500 MPR migration post-upgrade tasks 54 CAUTION Management Disruption A 5620 SAM system that manages 9500 MPR devices requires special configuration for an upgrade from a release earlier than 14.0 R7; otherwise, the upgraded 5620 SAM cannot manage the devices. To ensure continued 9500 MPR management after the upgrade, you must perform the procedure described in this step. See 9500 MPR migration to revised service model in the 9500 MPR User Guide for more information. If you are upgrading from a 5620 SAM release earlier than 14.0 R7, and the 5620 SAM system manages one or more 9500 MPR devices, perform To perform post-upgrade tasks in the 9500 MPR User Guide. END OF STEPS 246 3HE AAAG-TQZZA

247 5620 SAM 5650 CPAM Component references Redundant 5620 SAM system upgrade 9.6 Component references Description CAUTION Service Disruption A redundant 5620 SAM system upgrade involves a network management outage. Ensure that you perform the upgrade during a scheduled maintenance period of sufficient duration to accommodate the outage. During a redundant 5620 SAM system upgrade, the primary and standby roles of the main servers and databases reverse, as do the Preferred and Reserved auxiliary server roles. As a result, the use of relative component identifiers such as primary and standby can cause confusion. To clearly identify components during a redundant system upgrade, you can use the figure below. The components on the left manage the network before the upgrade, and the components on the right manage the network after the upgrade. Each component in the figure has an absolute identifier in brackets, for example, [DB1], that clearly identifies the component in the redundant system upgrade workflow and procedure steps. 3HE AAAG-TQZZA 247

248 Redundant system upgrade workflow 5620 SAM 5650 CPAM Figure SAM component reference diagram 9.7 Redundant system upgrade workflow Description The following is the sequence of high-level actions required to upgrade a redundant 5620 SAM system Stages Note: The links in the Upgrade redundant system (p. 249) stages lead to sections in 9.8 To upgrade a redundant 5620 SAM system (p. 253). Prepare system for upgrade 1 Perform 9.3 To perform the pre-upgrade tasks (p. 221) to prepare the 5620 SAM system for the upgrade HE AAAG-TQZZA

249 5620 SAM 5650 CPAM Redundant system upgrade workflow Upgrade redundant system Download the required 5620 SAM installation files and distribute the files to the stations in the system, as required; see Download and distribute 5620 SAM installation files (p. 253). Stop the standby main server; see Stop standby main server [Main2] (p. 254). If the 5620 SAM system includes auxiliary servers, stop the [Aux2] auxiliary servers; see Stop auxiliary servers [Aux2] (p. 255). Disable 5620 SAM redundancy functions; see Disable database redundancy (p. 255). Upgrade the standby database, which becomes the new primary database; see Upgrade standby database [DB2] (p. 256). 1. Stop the 5620 SAM database. 2. Run a script to prepare for the Oracle software installation. 3. Install the database packages. 4. Run the database upgrade script. 5. Verify and modify the database configuration, as required. Upgrade the standby main server; see Upgrade standby main server [Main2] (p. 262). If the 5620 SAM system includes one or more Cflowd auxiliary servers or analytics servers, stop each server; see Stop analytics servers, Cflowd auxiliary servers (p. 264). If the 5620 SAM system includes auxiliary servers, upgrade the [Aux2] auxiliary servers; see Upgrade auxiliary servers [Aux2] (p. 265). Prepare the original primary main server for the upgrade; see Stop original primary main server [Main1], prepare station for upgrade (p. 265). 1. Stop the main server. 2. Disable automatic main server startup. 3. Verify the local file system resources. 3HE AAAG-TQZZA 249

250 Redundant system upgrade workflow 5620 SAM 5650 CPAM Note: This stage marks the beginning of the network management outage If the 5620 SAM system includes one or more Cflowd auxiliary servers, upgrade each Cflowd auxiliary server; see Upgrade Cflowd auxiliary servers (p. 266). If the 5620 SAM system includes auxiliary servers, stop the [Aux1] auxiliary servers; see Stop auxiliary servers [Aux1] (p. 266). If the 5620 SAM system includes an auxiliary database, upgrade the auxiliary database; see Upgrade auxiliary database (p. 267). Stop the original primary database; see Stop original primary database [DB1] (p. 267). Start the new primary main server; see Start new primary main server [Main2] (p. 267). If the 5620 SAM system includes auxiliary servers, start the [Aux2] auxiliary servers; see Start auxiliary servers [Aux2] (p. 268). If the 5620 SAM system includes one or more analytics servers, upgrade each analytics server; see Upgrade analytics servers (p. 269). 18 Note: This stage marks the end of the network management outage. Upgrade or install a 5620 SAM single-user client or client delegate server; see Upgrade or install GUI client (p. 269) Perform sanity testing on the upgraded 5620 SAM system using a 5620 SAM GUI client; see Test upgraded system using GUI client (p. 269). Uninstall the original primary database; see Uninstall original primary database [DB1] (p. 269) HE AAAG-TQZZA

251 5620 SAM 5650 CPAM Redundant system upgrade workflow Install the new standby database; see Install new standby database [DB1] (p. 270). 1. Run a script to prepare for the Oracle software installation. 2. Install the 5620 SAM database packages. 3. Configure the standby database. 4. Verify the database configuration. 5. Run the database upgrade script. Reinstantiate the standby database; see Reinstantiate standby database (p. 275). Upgrade the original primary main server to become the new standby main server; see Upgrade original primary main server [Main1] (p. 275). If the 5620 SAM system includes auxiliary servers, upgrade the [Aux1] auxiliary servers; see Upgrade auxiliary servers [Aux1] (p. 279). If the 5620 SAM system includes auxiliary servers, start the [Aux1] auxiliary servers; see Start auxiliary servers [Aux1] (p. 279). Upgrade or install additional 5620 SAM single-user clients or client delegate servers, if required; see Upgrade or install additional GUI clients (p. 279) Concurrent task execution Some system upgrade operations require considerable time. To reduce the duration of a redundant upgrade, you can perform some actions concurrently. The following table lists the redundant system upgrade workflow tasks in a format that involves two operators, A and B, who perform tasks concurrently when possible. 3HE AAAG-TQZZA 251

252 Redundant system upgrade workflow 5620 SAM 5650 CPAM Table 89 Workflow for concurrent task execution during redundant upgrade System redundancy mode Operator A actions Operator B actions D U P L E X Stage 1 Actions described in 9.3 To perform the pre-upgrade tasks (p. 221) Stage 2 Download and distribute 5620 SAM installation files (p. 253) Stage 3 Stop standby main server [Main2] (p. 254) Stage 4 Stop auxiliary servers [Aux2] (p. 255) Stage 5 Disable database redundancy (p. 255) S I M P L E X Stage 6 Upgrade standby database [DB2] (p. 256) Stage 8 Stop analytics servers, Cflowd auxiliary servers (p. 264) Stage 7 Upgrade standby main server [Main2] (p. 262) Stage 9 Upgrade auxiliary servers [Aux2] (p. 265) O U T A G E S I M P L E X D U P L E X Stage 10 Stop original primary main server [Main1], prepare station for upgrade (p. 265) Stage 11 Upgrade Cflowd auxiliary servers (p. 266) Stage 12 Stop auxiliary servers [Aux1] (p. 266) Stage 13 Upgrade auxiliary database (p. 267) Stage 14 Stop original primary database [DB1] (p. 267) Stage 15 Start new primary main server [Main2] (p. 267) Note: The outage persists until device discovery completes. Stage 18 Upgrade or install GUI client (p. 269) Stage 19 Test upgraded system using GUI client (p. 269) Stage 21 Install new standby database [DB1] (p. 270) Stage 22 Reinstantiate standby database (p. 275) Stage 24 Upgrade auxiliary servers [Aux1] (p. 279) Stage 25 Start auxiliary servers [Aux1] (p. 279) Stage 26 Upgrade or install additional GUI clients (p. 279) Stage 16 Start auxiliary servers [Aux2] (p. 268) Stage 17 Upgrade analytics servers (p. 269) Stage 20 Uninstall original primary database [DB1] (p. 269) Stage 23 Upgrade original primary main server [Main1] (p. 275) 252 3HE AAAG-TQZZA

253 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 9.8 To upgrade a redundant 5620 SAM system Description Steps The following steps describe how to upgrade a collocated or distributed 5620 SAM database and main server in a redundant deployment. The steps include links to procedures for installing and upgrading optional 5620 SAM components. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. Note: You require the following user privileges: on each main and auxiliary server station root, samadmin on each 5620 SAM database station root Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user Download and distribute 5620 SAM installation files 1 2 Download the following 5620 SAM installation files: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm samauxserver-sam_r_r_revision-pp.x86_64.rpm, if the system includes auxiliary servers where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Copy the following files to an empty directory on each main server, database, and auxiliary server station: 3HE AAAG-TQZZA 253

254 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Note: In subsequent steps, the directory is called the 5620 SAM software directory. samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm 3 4 Perform one of the following. a. In a distributed 5620 SAM system: 1. Copy the following files to the 5620 SAM software directory on each database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh 2. Copy the following file to each main server station: samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm b. In a collocated 5620 SAM system, copy the following files to the 5620 SAM software directory on each main server and database station: samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm If the 5620 SAM system includes one or more auxiliary servers, copy the following file to the 5620 SAM software directory on each auxiliary server station: samauxserver-sam_r_r_revision-pp.x86_64.rpm Stop standby main server [Main2] 5 6 Open a 5620 SAM GUI client to monitor the network during the upgrade. Stop the standby main server. 1. Log in to the standby main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following to stop the main server: bash$./nmsserver.bash stop 254 3HE AAAG-TQZZA

255 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 5. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 6. The 5620 SAM main server is stopped when the command displays the following status message: Application Server is stopped If the command displays a different message, wait five minutes and return to Step 6 5. Do not proceed to the next step until the main server is stopped. 7 Disable the automatic main server startup so that the main server does not start in the event of a power disruption during the upgrade. 1. Enter the following to switch to the root user: bash$ su - 2. Enter the following: # cd /etc/init.d 3. Enter the following to rename the main server startup daemon: # mv 5620SAMServerWrapper inactive.5620samserverwrapper Stop auxiliary servers [Aux2] 8 If the 5620 SAM system includes auxiliary servers, stop each appropriate auxiliary server [Aux2]. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop The 5620 SAM auxiliary server stops. Disable database redundancy 9 Disable the 5620 SAM database failover and switchover functions. 1. Log in to the primary main server station [Main1] as the samadmin user. 2. Open a console window. 3. Enter the following to navigate to the main server configuration directory: bash$ cd /opt/5620sam/server/nms/config 4. Make a backup copy of the nms-server.xml file. 5. Open the nms-server.xml file with a plain-text editor, for example, vi. 3HE AAAG-TQZZA 255

256 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM 6. Locate the section that begins with the following tag: <db 7. Locate the following line in the section: host="address" 8. Ensure that the address value in the line is the IP address of database [DB1]. 9. Locate the following line in the section: database="instance_name" 10. Ensure that the instance_name value is the instance name of database [DB1]. 11. Edit the following line in the section that reads: redundancyenabled="true" to read: redundancyenabled="false" 12. Save and close the nms-server.xml file. 13. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash read_config The primary main server puts the change into effect, and database redundancy is disabled. Upgrade standby database [DB2] Stop the standby database and database proxy. 1. Log in to the standby database station [DB2] as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following to stop the Oracle proxy: #./S965620SAMOracleProxyWrapper stop 5. Enter the following to stop the 5620 SAM database: #./S95db5620sam stop Do not proceed until the following is displayed: Shutting down Oracle... Done. Perform the following steps to disable the automatic database proxy startup. 1. Enter the following: # cd /etc/init.d 2. Enter the following: 256 3HE AAAG-TQZZA

257 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system # mv 5620SAMOracleProxyWrapper inactive.5620samoracleproxywrapper 12 Navigate to the directory on the standby database station [DB2] that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 13 CAUTION Misconfiguration Risk The 5620 SAM software includes a script that configures the Oracle environment. The script is specific to a 5620 SAM release; using a different version may cause the database creation to fail. You must run only the script that is included with the new 5620 SAM software. Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. Note: If you specify a value other than the default, you must record the value for use when the OracleSw_PreInstall.sh script is run during a software upgrade, or when the Oracle management user information is required by technical support. The following prompt is displayed: This script will prepare the system for an upgrade to 5620 SAM Version R.r Rn. Do you want to continue? [Yes/No]: Enter Yes. The following messages and prompt are displayed: About to validate that the database can be upgraded to release. Found the SAM database installation directory /opt/5620sam/samdb/install. Existing SAM database version = version Enter the password for the "SYS" Oracle user (terminal echo is off): Enter the SYS user password. The script begins to validate the database records, and displays the following: 3HE AAAG-TQZZA 257

258 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Validating the database for upgrade. Please wait... If the validation is successful, the following messages and prompt are displayed: INFO: Database upgrade validation passed. Creating group group if it does not exist... Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1... Checking user username... usermod: no changes Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Do you want to change the password for the user username? [Yes/No]: Go to Step If the database contains an invalid item, for example, an NE at a release that the new 5620 SAM software does not support, the following is displayed and the script exits: ERROR: Unsupported records found in database. Please remove the following unsupported items first: Please remove the following unsupported items first: item_1 item_2.. item_n ERROR: The database cannot be upgraded. Please fix the above errors and re-run this script. Perform the following steps. 1. Use a 5620 SAM client to remove or update the unsupported items, as required. For example, upgrade an unsupported NE to a release that the new software supports. 2. Run the script again; go to Step Perform one of the following. a. Enter No to retain the current password. b. Specify a new password HE AAAG-TQZZA

259 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 1. Enter Yes. The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Re-enter new Password: 3. Re-enter the password. The following is displayed if the password change is successful: passwd: password successfully changed for user The following message and prompt are displayed: Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to remove kernel parameters set by a previous run of this script from /etc/sysctl.conf INFO: Completed removing kernel parameters set by a previous run of this script from /etc/sysctl.conf INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to remove ulimit parameters set by a previous run of this script from /etc/security/limits.conf INFO: Completed removing ulimit parameters set by a previous run of this script from /etc/security/limits.conf INFO: About to set ulimit parameters in etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... INFO: Completed running Oracle Pre-Install Tasks When the script execution is complete, enter the following to reboot the standby database station [DB2]: # init 6 The station reboots. 3HE AAAG-TQZZA 259

260 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM When the reboot is complete, log in to the standby database station [DB2] as the root user. Enter the following to stop the standby database: # /etc/rc3.d/s95db5620sam stop Do not proceed until the following is displayed: Shutting down Oracle... Done. Navigate to the directory on the standby database station [DB2] that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Perform one of the following. a. If the main server and database are on separate stations, enter the following: # yum install samjre* samconfig* samoracle* samdb* b. If the main server and database are collocated on one station, enter the following: # yum install samjre* samconfig* samoracle* samdb* samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 260 3HE AAAG-TQZZA

261 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 25 Enter the following to upgrade the database: # samupgradedb The following prompt is displayed: Enter the password for the "user" database user (terminal echo is off): 26 Enter the database user password. The following is displayed as the database upgrade begins: Validating... Note: A database upgrade may take considerable time. 27 When the upgrade is complete, verify the database configuration. Note: This database [DB2] is now the primary database. 1. Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> 2. Enter the following: <db> show-detail The database configuration is displayed. 3. Review each parameter to ensure that the value is correct. 4. Configure one or more parameters, if required, and then enter back ; see Chapter 3, Using samconfig for information about using the samconfig utility. 5. If you change one or more parameters, enter the following: <db> apply The configuration is applied. 6. Enter the following: <db> exit The samconfig utility closes. 28 It is recommended that as a security measure, you limit the number of database user login failures that the 5620 SAM allows before the database user account is locked; see 5620 SAM database management procedures in the 5620 SAM System Administrator Guide. 3HE AAAG-TQZZA 261

262 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Note: You do not need to perform the step if the database has been configured before the upgrade to limit the user login failures. Upgrade standby main server [Main2] 29 Log in to the standby main server station [Main2] as the root user. Note: After the upgrade, this main server is the new primary main server Open a console window. Ensure that there are no active samadmin user sessions. 1. Enter the following: # who The active user sessions are listed. 2. If the samadmin user is listed, close each samadmin user session; see the RHEL documentation for information about closing user sessions. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 33 If the main server and database are on separate stations, perform the following steps: 1. Enter the following: # yum install samjre* samconfig* samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: 2. Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded 262 3HE AAAG-TQZZA

263 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following; see Chapter 3, Using samconfig for information about using samconfig: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure The prompt changes to <main configure>. To apply a new or updated 5620 SAM license, enter the following, and then enter back : Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file in this step, or later import the license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. <main configure> license license_file where license_file is the absolute path of the 5620 SAM license zip file The prompt changes to <main configure>. 37 Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. 3HE AAAG-TQZZA 263

264 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. If one of the following is true, perform 7.3 To enable Small Cell management (p. 94) on the main server station: You need to enable Small Cell NE management for the first time. The 5620 SAM currently manages Small Cell NEs. If you are upgrading from a 5620 SAM release earlier than 12.0 R5, create a directory on the main server for backing up the stored NE configurations. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup 3. Enter the following to switch back to the root user: bash$ exit Stop analytics servers, Cflowd auxiliary servers 42 If the 5620 SAM system includes one or more analytics servers, stop each analytics server. 1. Log in to the analytics server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/analytics/bin/analyticsadmin.sh stop The following is displayed: Stopping 5620 SAM Analytics Server When the analytics server is completely stopped, the following message is displayed: 5620 SAM Analytics Server is not running 264 3HE AAAG-TQZZA

265 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 43 If the 5620 SAM system includes one or more Cflowd auxiliary servers, stop each Cflowd auxiliary server. 1. Log in to the Cflowd auxiliary server as the root user. 2. Open a console window. 3. Navigate to the Cflowd auxiliary server installation directory, which is one of the following: Release 14.0 R5 or earlier /opt/5620sam/dcp-r_rrn, where R_rRn is the software release identifier Release 14.0 R6 or later /opt/5620sam/dcp 4. Enter the following: #./bin/dcpctl.sh stop Output like the following is displayed. Stopping 5620 SAM Cflowd Auxiliary Server SAM Cflowd Auxiliary Server is stopped successfully Upgrade auxiliary servers [Aux2] 44 If the 5620 SAM system includes auxiliary servers, perform 9.9 To upgrade a 5620 SAM auxiliary server (p. 281) on each appropriate auxiliary server station [Aux2]. Note: Do not start any auxiliary server immediately after you upgrade the auxiliary server; the startup occurs later in the procedure. Stop original primary main server [Main1], prepare station for upgrade 45 Stop the original primary main server [Main1]. Note: The network management outage begins when you stop the original primary main server [Main1]. 1. Log in to the original primary main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following to stop the main server: bash$./nmsserver.bash stop 5. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 6. The main server is stopped when the command displays the following status message: 3HE AAAG-TQZZA 265

266 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Application Server is stopped If the command displays a different message, wait five minutes and return to Step Do not proceed to the next step until the main server is stopped Disable the automatic main server startup so that the main server does not start in the event of a power disruption during the upgrade. 1. Enter the following to switch to the root user: bash$ su - 2. Enter the following: # cd /etc/init.d 3. Enter the following to rename the main server startup daemon: # mv 5620SAMServerWrapper inactive.5620samserverwrapper If the 5620 SAM system manages more than 3000 NEs, ensure that the main server has enough inodes for the upgrade. 1. Enter the following: # df -i /opt/5620sam/server/nms/bin/depl/mediation The command returns output similar to the following: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda % /opt/5620sam 2. If the IUse% value is greater than 40%, enter the following to remove the mediation files: # rm -r /opt/5620sam/server/nms/bin/depl/mediation Note: The command may take several minutes to complete. Upgrade Cflowd auxiliary servers 48 If the 5620 SAM system includes one or more Cflowd auxiliary servers, perform 9.10 To upgrade a 5620 SAM Cflowd auxiliary server (p. 284) on each Cflowd auxiliary server station. Stop auxiliary servers [Aux1] 49 If the 5620 SAM system includes auxiliary servers, perform the following steps on each [Aux1] auxiliary server station. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window HE AAAG-TQZZA

267 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop The 5620 SAM auxiliary server stops. Upgrade auxiliary database 50 If the 5620 SAM system includes an auxiliary database, perform 9.11 To upgrade a 5620 SAM auxiliary database (p. 291). Stop original primary database [DB1] 51 Stop the original primary database [DB1]. 1. Log in to the original primary database station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following to stop the Oracle proxy: #./S965620SAMOracleProxyWrapper stop 5. Enter the following to stop the 5620 SAM database: #./S95db5620sam stop Do not proceed until the command displays the following message: Done Start new primary main server [Main2] 52 CAUTION Service Disruption The new primary database [DB2] must be upgraded and running before you start the new primary main server [Main2], or the main server initialization may fail. If you perform the new primary main server and database upgrades concurrently, do not perform this step until the database upgrade is complete. 3HE AAAG-TQZZA 267

268 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM CAUTION Service Disruption A 5620 SAM system upgrade is not complete until each main server performs crucial postupgrade tasks during initialization. Before you attempt an operation such as a conversion to IPv6, you must ensure that each main server is completely initialized, or the operation fails. Start the new primary main server [Main2]. Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file, or import a license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. 1. Log in as the samadmin user on the new primary main server station: 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following to start the main server: bash$./nmsserver.bash start 4. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the new main server is not completely started, the following is displayed: Main Server is not ready... The main server is completely started when the command returns the following: -- Primary Server is UP 5. If the command output indicates that the main server is not completely started, wait five minutes and then return to Step Do not proceed to the next step until the main server is completely started. Start auxiliary servers [Aux2] 53 If the 5620 SAM system includes auxiliary servers, atart each appropriate auxiliary server [Aux2]. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/auxserver/nms/bin 4. Enter the following to start the auxiliary server: bash$./auxnmsserver.bash auxstart 268 3HE AAAG-TQZZA

269 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system The auxiliary server starts. Upgrade analytics servers 54 If the 5620 SAM system includes one or more analytics servers, perform 9.12 To upgrade a 5620 SAM analytics server (p. 297) on each analytics server station. Upgrade or install GUI client If you modify the SSL configuration during a main server upgrade, you cannot upgrade a 5620 SAM single-user GUI client or client delegate server that connects to the main server until you uninstall the current client software and install the new client software with the appropriate SSL settings. As required, perform the appropriate uninstallation procedures in the following chapters: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server Perform the appropriate procedures in the following chapters to install or upgrade a 5620 SAM single-user GUI client or client delegate server, as required: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server Test upgraded system using GUI client 57 When the new primary main server [Main2] is started, use the newly installed or upgraded 5620 SAM GUI client to perform sanity testing of the new primary main server and database. See Procedures for opening and closing the GUI in the 5620 SAM User Guide for information about client operation. Note: To back out of the upgrade and return the original primary main server [Main1] and database [DB1] to service, you can do so by stopping the new primary main server [Main2] and database [DB2] and restarting the original primary main server [Main1] and database [DB1]. Uninstall original primary database [DB1] 58 Uninstall the original primary database [DB1]. 3HE AAAG-TQZZA 269

270 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Note: You must use the uninstallation procedure in the 5620 SAM 5650 CPAM Installation and Upgrade Guide for the installed database release, and not the procedure in this guide. For example, if you are upgrading from Release 13.0 R7, you must use the Release 13.0 R7 database uninstallation procedure. Install new standby database [DB1] Log in to the original primary database [DB1] station as the root user. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 61 CAUTION Misconfiguration Risk The 5620 SAM software includes a script that configures the Oracle environment. The script is specific to a 5620 SAM release; using a different version may cause the database creation to fail. You must run only the script that is included with the new 5620 SAM software. Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. The following prompt is displayed: This script will prepare the system for a new install/restore of a 5620 SAM Version R.r Rn database. Do you want to continue? [Yes/No]: Enter Yes. The following prompt is displayed: Enter the Oracle dba group name [group]: Press to accept the default. The following messages and prompt are displayed: Creating group group if it does not exist HE AAAG-TQZZA

271 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system WARNING: Group group already exists locally. Do you want to use the existing group? [Yes/No]: Enter Yes. The following message and prompt are displayed: The user [username] for the group [group] already exists locally. Do you want to use the existing user? [Yes/No]: Enter Yes. The following messages and prompt are displayed: Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1... Checking user username... WARNING: Oracle user with the specified name already exists locally. Redefining the primary group and home directory of user username... usermod: no changes Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Do you want to change the password for the user username? [Yes/No]: Perform one of the following. a. If you did not change the password during the upgrade of the original standby database, enter No. b. If you changed the password during the upgrade of the original standby database, perform the following steps. 1. Enter Yes. The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Re-enter new Password: 3. Re-enter the password. The following is displayed if the password change is successful: passwd: password successfully changed for user The following message and prompt are displayed: 3HE AAAG-TQZZA 271

272 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to remove kernel parameters set by a previous run of this script from /etc/sysctl.conf INFO: Completed removing kernel parameters set by a previous run of this script from /etc/sysctl.conf INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to remove ulimit parameters set by a previous run of this script from /etc/security/limits.conf INFO: Completed removing ulimit parameters set by a previous run of this script from /etc/security/limits.conf INFO: About to set ulimit parameters in etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... INFO: Completed running Oracle Pre-Install Tasks When the script execution is complete, enter the following to reboot the database station: # init 6 The station reboots. When the reboot is complete, log in to the original primary database [DB1] station as the root user. Note: After the upgrade, this database is the new standby database. 70 Open a console window HE AAAG-TQZZA

273 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system 71 Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 72 Perform one of the following. a. If the main server and database are on separate stations, enter the following: # yum install samjre* samconfig* samoracle* samdb* b. If the main server and database are collocated on one station, enter the following: # yum install samjre* samconfig* samoracle* samdb* samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Configure the database as a standby database. 1. Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> 2. Enter the following: <db> configure type standby The prompt changes to <db configure>. 3HE AAAG-TQZZA 273

274 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM 3. Enter the following: <db configure> ip address where address is the IP address of this database 4. Enter the following: <db configure> redundant ip address where address is the IP address of the new primary database [DB2] The prompt changes to <db configure redundant>. 5. Enter the following: <db configure redundant> instance instance_name where instance_name is the instance name of the new primary database [DB2] 6. Enter the following: <db configure redundant> back The prompt changes to <db configure>. 7. Enter the following: <db configure> passwords sys password where password is the SYS user password of the new primary database [DB2] The prompt changes to <db configure passwords>. 8. Enter the following: <db configure passwords> back The prompt changes to <db configure> Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to begin the database creation: <db> apply The database creation begins, and messages are displayed as the creation progresses. The following is displayed when the database creation is complete: 274 3HE AAAG-TQZZA

275 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system DONE db configurations updated. 77 When the database creation is complete, enter the following: <db> exit The samconfig utility closes. Reinstantiate standby database Log in to a 5620 SAM GUI client as the admin user. Choose Administration System Information from the 5620 SAM main menu. The System Information form opens. Click Re-Instantiate Standby. Click Yes to confirm the action. The reinstantiation begins, and the GUI status bar displays reinstantiation information. Note: Database reinstantiation takes considerable time if the database contains a large amount of statistics data. You can also use the System Information form to monitor the reinstantiation progress. The Last Attempted Standby Re-instantiation Time is the start time; the Standby Re-instantiation State changes from In Progress to Success when the reinstantiation is complete. 82 When the reinstantiation is complete, close the System Information form. Upgrade original primary main server [Main1] 83 Log in to the original primary main server station [Main1] as the root user. Note: After the upgrade, this main server is the new standby main server. 84 Open a console window. 3HE AAAG-TQZZA 275

276 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Ensure that there are no active samadmin user sessions. 1. Enter the following: # who The active user sessions are listed. 2. If the samadmin user is listed, close each samadmin user session; see the OS documentation for information about closing user sessions. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set If the main server and database are on separate stations, perform the following steps: 1. Enter the following: # yum install samjre* samconfig* samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: 2. Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> 276 3HE AAAG-TQZZA

277 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system Enter the following: <main> configure The prompt changes to <main configure>. To apply a new or updated 5620 SAM license, enter the following, and then enter back : Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file in this step, or later import the license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. <main configure> license license_file where license_file is the absolute path of the 5620 SAM license zip file Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. If one of the following is true, perform 7.3 To enable Small Cell management (p. 94) on the new standby main server station: You need to enable Small Cell management for the first time. 3HE AAAG-TQZZA 277

278 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM The 5620 SAM currently manages Small Cell NEs If you are upgrading from a 5620 SAM release earlier than 12.0 R5, create a directory on the main server for backing up the stored NE configurations. 1. Log in as the samadmin user on the new standby main server station. 2. Open a console window. 3. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup Start the new standby main server [Main1]. Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file, or import a license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. 1. Log in as the samadmin user on the main server station. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following to start the main server: bash$./nmsserver.bash start 5. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following: -- Standby Server is UP 6. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Close the console window HE AAAG-TQZZA

279 5620 SAM 5650 CPAM To upgrade a redundant 5620 SAM system Upgrade auxiliary servers [Aux1] 98 If the 5620 SAM system includes auxiliary servers, perform 9.9 To upgrade a 5620 SAM auxiliary server (p. 281) on each [Aux1] auxiliary server station. Start auxiliary servers [Aux1] 99 If the 5620 SAM system includes auxiliary servers, perform the following steps on each [Aux1] auxiliary server station. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The 5620 SAM auxiliary server starts. Upgrade or install additional GUI clients 100 If you modify the SSL configuration during a main server upgrade, you cannot upgrade a 5620 SAM single-user GUI client or client delegate server that connects to the main server until you uninstall the current client software and install the new client software with the appropriate SSL settings. As required, perform the appropriate uninstallation procedures in the following chapters: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server 101 Perform the appropriate procedures in the following chapters to install or upgrade 5620 SAM single-user GUI clients or client delegate servers, as required: Chapter 13, Single-user client deployment single-user client Chapter 14, Client delegate server deployment client delegate server 3HE AAAG-TQZZA 279

280 To upgrade a redundant 5620 SAM system 5620 SAM 5650 CPAM Perform 9500 MPR migration post-upgrade tasks 102 CAUTION Management Disruption A 5620 SAM system that manages 9500 MPR devices requires special configuration for an upgrade from a release earlier than 14.0 R7; otherwise, the upgraded 5620 SAM cannot manage the devices. To ensure continued 9500 MPR management after the upgrade, you must perform the procedure described in this step. See 9500 MPR migration to revised service model in the 9500 MPR User Guide for more information. If you are upgrading from a 5620 SAM release earlier than 14.0 R7, and the 5620 SAM system manages one or more 9500 MPR devices, perform To perform post-upgrade tasks in the 9500 MPR User Guide. END OF STEPS 280 3HE AAAG-TQZZA

281 5620 SAM 5650 CPAM To upgrade a 5620 SAM auxiliary server Auxiliary server upgrade 9.9 To upgrade a 5620 SAM auxiliary server Description The following steps describe how to upgrade the 5620 SAM auxiliary server software on a station. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses Steps Note: An auxiliary server is dedicated to only one of the following functions: statistics collection call-trace data collection PCMD record collection Note: You require the following user privileges on the auxiliary server station: root samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 1 Stop the auxiliary server. 1. Log in to the auxiliary server station as the root user. 2. Open a console window. 3. Enter the following to switch to the samadmin user: # su - samadmin 4. Enter the following: bash$ cd /opt/5620sam/auxserver/nms/bin 5. Enter the following to stop the auxiliary server: bash$./auxnmsserver.bash auxstop 6. Enter the following to display the auxiliary server status: bash$./auxnmsserver.bash auxappserver_status The command displays a status message. 7. The server is stopped when the command displays the following status message: Auxiliary Server is stopped 3HE AAAG-TQZZA 281

282 To upgrade a 5620 SAM auxiliary server 5620 SAM 5650 CPAM If the command displays a different message, wait five minutes and return to Step 1 6. Do not proceed until the auxiliary server is stopped Enter the following to switch back to the root user: # exit Ensure that there are no active samadmin user sessions. 1. Enter the following: # who The active user sessions are listed. 2. If the samadmin user is listed, close each samadmin user session; see the RHEL documentation for information about closing user sessions. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 5 6 Enter the following: # yum install samjre* samconfig* samauxserver* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 282 3HE AAAG-TQZZA

283 5620 SAM 5650 CPAM To upgrade a 5620 SAM auxiliary server Enter the following: # samconfig -m aux The following is displayed: Start processing command line inputs... <aux> Verify the auxiliary server configuration. 1. Enter the following: <aux> show-detail The auxiliary server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. If required, modify one or more parameter values, and then enter back ; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <aux> apply The configuration is applied. 5. Enter the following: <aux> exit The samconfig utility closes. If one of the following is true, perform 7.3 To enable Small Cell management (p. 94) on the auxiliary server station: You need to enable Small Cell management using the auxiliary server for the first time. The 5620 SAM currently manages Small Cell NEs using the auxiliary server. Start the auxiliary server, unless otherwise directed as part of a 5620 SAM system upgrade. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the followingr: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The auxiliary server starts. END OF STEPS 3HE AAAG-TQZZA 283

284 To upgrade a 5620 SAM Cflowd auxiliary server 5620 SAM 5650 CPAM Cflowd auxiliary server upgrade 9.10 To upgrade a 5620 SAM Cflowd auxiliary server Description The following steps describe how to upgrade the 5620 SAM Cflowd auxiliary server software on a station Steps Note: You require root user privileges on the Cflowd auxiliary server station. Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command. Note: After you upgrade a Cflowd auxiliary server, you must clear the cache of any browser that you use to configure the Cflowd auxiliary server, or the configuration web UI may not display correctly. Stop Cflowd auxiliary server Log in to the Cflowd auxiliary server station as the root user. Open a console window. Navigate to the Cflowd auxiliary server installation directory, which is one of the following: Release 14.0 R5 or earlier /opt/5620sam/dcp-r_rrn, where R_rRn is the software release identifier Release 14.0 R6 or later /opt/5620sam/dcp Enter the following: #./bin/dcpctl.sh stop A message like the following is displayed: Stopping 5620 SAM DCP server... The Cflowd auxiliary server is stopped when a message like the following is displayed: 5620 SAM DCP server is stopped successfully 284 3HE AAAG-TQZZA

285 5620 SAM 5650 CPAM To upgrade a 5620 SAM Cflowd auxiliary server 5 If you are upgrading from Release 14.0, go to Step 16. Upgrade Release 13.0 server to intermediate release Navigate to the appropriate directory, depending on which Release 13.0 software is currently installed: 13.0 R5 or later /opt/5620sam/jboss-6.4.0/standalone/configuration/dcp-r_rrn 13.0 R4 or earlier /opt/5620sam/jboss-5.1.0/server/5620sam/conf/dcp-r_rrn where R_rRn is the software release identifier Make a backup copy of the following files, which are required after the upgrade, and store the files in a secure location on another station: CfdGlobalPolicy.xml global policy definition that includes the aggregation intervals and counters CfdLocalPolicy.xml collection configuration for managed devices CfdResultsTransfer.properties IPDR file transfer settings CfdSpecialStudyPolicy.xml special-study policy settings CfdUappsPolicy.xml application and protocol filters SamHostInfoCfg.xml 5620 SAM communication settings Enter the following to navigate to the root user home directory: # cd Uninstall the Cflowd auxiliary server; enter one of the following: # /opt/5620sam/dcp-r_rrn/uninstall/uninstall where R_rRn is the software release identifier The uninstallation begins, and a series of progress indicators is displayed. The following is displayed when the uninstallation is complete: Uninstallation Complete. Download the following 5620 SAM Release 14.0 R1, R2, R3, or R5 installation files to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm cflowdauxserver-sam_r_r_revision-pp.x86_64.rpm 3HE AAAG-TQZZA 285

286 To upgrade a 5620 SAM Cflowd auxiliary server 5620 SAM 5650 CPAM where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level 11 Navigate to the directory that contains the installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Enter the following: # yum install samjre* cflowdauxserver* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nnn M Is this ok [y/n]: Enter y. The following and a progress indicator are displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Perform the following steps. 1. Navigate to the /opt/5620sam/jboss-n.n.n/standalone/configuration/dcp-r_rrn directory, where R_rRn is the software release identifier, and n.n.n is the JBOSS version. 2. Replace the following files with the backup copies created in Step 7 : CfdGlobalPolicy.xml CfdLocalPolicy.xml CfdResultsTransfer.properties CfdSpecialStudyPolicy.xml CfdUappsPolicy.xml SamHostInfoCfg.xml 286 3HE AAAG-TQZZA

287 5620 SAM 5650 CPAM To upgrade a 5620 SAM Cflowd auxiliary server 15 Start the Cflowd auxiliary server; enter the following: # cd /opt/5620sam/dcp-r_rrn/bin/dcpctl.sh start where R_rRn is the software release identifier The following is displayed: Starting 5620 SAM DCP server... The Cflowd auxiliary server is started when the following is displayed: 5620 SAM DCP server is started successfully Upgrade 14.0 server Stop the Cflowd auxiliary server. 1. Navigate to the Cflowd auxiliary server installation directory, which is one of the following: Release 14.0 R5 or earlier /opt/5620sam/dcp-r_rrn, where R_rRn is the software release identifier Release 14.0 R6 or later /opt/5620sam/dcp 2. Enter the following: #./dcpctl.sh stop where R_rRn is the software release identifier A message like the following is displayed: Stopping 5620 SAM DCP server... The Cflowd auxiliary server is stopped when a message like the following is displayed: 5620 SAM DCP server is stopped successfully Download the following 5620 SAM installation files for the current release to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm cflowdauxserver-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Navigate to the directory that contains the installation files. 3HE AAAG-TQZZA 287

288 To upgrade a 5620 SAM Cflowd auxiliary server 5620 SAM 5650 CPAM Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Enter the following: # yum install samjre* samconfig* cflowdauxserver* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nnn M Installed size: nn M Is this ok [y/n]: Enter y. The following is displayed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! When the package installation is complete, enter the following: # samconfig -m cflowdaux Enter the following: <cflowdaux> configure category category where category is the Cflowd auxiliary server data category, which is one of the following: sys, for system Cflowd statistics data aa, for AA Cflowd statistics data The prompt changes to <cflowdaux configure>. Enter the following: <cflowdaux configure> back The prompt changes to <cflowdaux> HE AAAG-TQZZA

289 5620 SAM 5650 CPAM To upgrade a 5620 SAM Cflowd auxiliary server Enter the following: <cflowdaux> apply The configuration is applied. Enter the following: <cflowdaux> exit The samconfig utility closes. Delete the contents of the following directories: /opt/5620sam/jboss-6.4.0/standalone/data/dcp/extraction /opt/5620sam/pers/intervals /opt/5620sam/pers/templates Perform one of the following. a. If you are upgrading from Release 14.0 R5 or earlier: 1. Open the following file for viewing: /opt/5620sam/jboss-6.4.0/standalone/configuration/dcp/cfdruntime.properties 2. Locate the following line: com.alu.bsx.cfd.collector.uuid=uuid 3. Record the UUID value and store it in a secure location; the value is required for subsequent deployment operations. b. If you are upgrading from Release 14.0 R6 or later: 1. Open the following file using a plain-text editor such as vi: /opt/5620sam/jboss-6.4.0/standalone/configuration/dcp/cfdruntime.properties 2. Locate the following line: com.alu.bsx.cfd.collector.uuid=uuid 3. Replace the UUID value with the value recorded during the previous installation or upgrade. 4. Save and close the file. Start the Cflowd auxiliary server; enter the following: # /opt/5620sam/dcp/bin/dcpctl.sh start The following is displayed: Starting 5620 SAM Cflowd Auxiliary Server... 3HE AAAG-TQZZA 289

290 To upgrade a 5620 SAM Cflowd auxiliary server 5620 SAM 5650 CPAM The Cflowd auxiliary server is started when the following is displayed: 5620 SAM Cflowd Auxiliary Server is started successfully 29 Close the console window. END OF STEPS 290 3HE AAAG-TQZZA

291 5620 SAM 5650 CPAM To upgrade a 5620 SAM auxiliary database Auxiliary database upgrade 9.11 To upgrade a 5620 SAM auxiliary database Description The following steps describe how to upgrade the 5620 SAM auxiliary database software Steps Note: CPU speed scaling, or CPUfreq, must be set to performance in the BIOS of each auxiliary database station, or the auxiliary database upgrade fails. See the RHEL power management documentation for information about enabling the performance CPUfreq governor on a station. Setting CPUfreq to performance effectively disables CPU speed scaling, so may result in greater energy consumption by a station. Note: An auxiliary database upgrade from Release 14.0 R4 or earlier removes the current performance statistics data values. As a result, the periodic counter values for the first collection after an upgrade are inaccurate. Note: You require root user privileges on each auxiliary database station. Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command. Obtain software, stop database As a safety precaution, back up the auxiliary database; see the 5620 SAM System Administrator Guide for information. Perform steps Step 4 to Step 9 on each auxiliary database station. Perform steps Step 10 to Step 15 on each auxiliary database station. Download the following 5620 SAM installation files to an empty local directory: samjre-sam_r_r_revision-pp.x86_64.rpm vertica-v.w.x-y.x86_64.rhel6.rpm samauxdb-sam_r_r_revision-pp.x86_64.rpm VerticaSw_PreInstall.sh 3HE AAAG-TQZZA 291

292 To upgrade a 5620 SAM auxiliary database 5620 SAM 5650 CPAM where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level V.w.x-y is a version number Log in to the auxiliary database station as the root user. Open a console window. Enter the following: # cd /etc/rc3.d Enter the following commands in sequence: #./S90samauxdb stop #./S99verticad stop #./S99vertica_agent stop #./S90samauxdbproxy stop Enter the following commands in sequence: # chkconfig samauxdb off # chkconfig verticad off # chkconfig vertica_agent off # chkconfig samauxdbproxy off Prepare stations for upgrade 10 Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 11 Enter the following: 292 3HE AAAG-TQZZA

293 5620 SAM 5650 CPAM To upgrade a 5620 SAM auxiliary database 12 #./VerticaSw_PreInstall.sh The script displays configuration messages like the following: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... Checking Vertica DBA group samauxdb... Adding Vertica DBA group samauxdb... Checking Vertica user samauxdb... Adding Vertica user samauxdb... Changing ownership of the directory /opt/5620sam/samauxdb to samauxdb:samauxdb. Adding samauxdb to sudoers file. Changing ownership of /opt/5620sam/auxdb files. INFO: About to add setting to /etc/rc.d/rc.local... INFO: Completed adding setting to /etc/rc.d/rc.local... If the script instructs you to perform a restart, perform the following steps. 1. Enter the following: # init 6 The station reboots. 2. When the reboot is complete, log in to the station as the root user. 3. Open a console window. 4. Navigate to the directory that contains the new 5620 SAM installation files. 13 Enter the following: # yum install samjre* vertica* samauxdb* where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level V.w.x-y is a version number 3HE AAAG-TQZZA 293

294 To upgrade a 5620 SAM auxiliary database 5620 SAM 5650 CPAM The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following and a progress indicator are displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! When the package installation is complete, enter the following to reboot the auxiliary database station: # init 6 The station reboots. Upgrade database When each station reboot is complete, log in to one auxiliary database station as the root user. Open a console window. Enter the following: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh upgrade Enter the following to start the auxiliary database: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh start You are prompted for the database user password HE AAAG-TQZZA

295 5620 SAM 5650 CPAM To upgrade a 5620 SAM auxiliary database Press. Enter the following to display the auxiliary database status: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh status The script displays the following: Copyright 20XX Nokia. Database status Node Host State Version DB host_ip_1 internal_ip_1 STATE version samdb host_ip_2 internal_ip_2 STATE version samdb... host_ip_n internal_ip_n STATE version samdb Output captured in log_file Repeat Step 21 periodically until the STATE of each node is UP. Enter the following: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh upgradedb The following prompt is displayed: Copyright 20XX Nokia. Please enter auxiliary database user password: Enter the database user password. The following prompt is displayed: Please enter database port [5433]: Press. The following prompt is displayed: Please enter auxiliary database dba password : 3HE AAAG-TQZZA 295

296 To upgrade a 5620 SAM auxiliary database 5620 SAM 5650 CPAM 26 Enter the dba password. The following message and prompt are displayed: INFO: Please perform a database backup before proceeding with this option. Do you want to proceed (YES/NO)?: Enter YES. The upgrade begins. When the upgrade is complete, perform the following steps on each auxiliary database station as the root user. 1. Enter the following commands in sequence: # chkconfig samauxdb on # chkconfig verticad on # chkconfig vertica_agent on # chkconfig samauxdbproxy on 2. Enter the following: # /etc/init.d/mcelogd start 3. Enter the following: # /etc/init.d/samauxdbproxy start Messages like the following are displayed: hh:mm:ss Day mm/dd/yy : Starting 5620 SAM Auxiliary DB Proxy... hh:mm:ss Day mm/dd/yy : Refer to log_file for startup status. Close the open console windows. END OF STEPS 296 3HE AAAG-TQZZA

297 5620 SAM 5650 CPAM To upgrade a 5620 SAM analytics server Analytics server upgrade 9.12 To upgrade a 5620 SAM analytics server Description The following steps describe how to upgrade the 5620 SAM analytics server software on a station Steps Note: You require root and samadmin user privileges on the analytics server station. Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands # root user bash$ samadmin user Stop analytics server Log in to the analytics server station as the root user. Open a console window. Download the following 5620 SAM installation files to an empty local directory: Note: You can proceed to the next step as the download begins: samjre-sam_r_r_revision-pp.x86_64.rpm tomcat-sam_r_r_revision-pp.x86_64.rpm samanalytics-r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level 4 Enter the following to switch to the samadmin user: bash$ su - samadmin 3HE AAAG-TQZZA 297

298 To upgrade a 5620 SAM analytics server 5620 SAM 5650 CPAM 5 Enter the following to stop the analytics server: bash$ /opt/5620sam/analytics/bin/analyticsadmin.sh stop The following and other messages are displayed: Stopping 5620 SAM Analytics Application When the analytics server is completely stopped, the following message is displayed: 5620 SAM Analytics Server is not running Install new analytics server packages Enter the following to switch to the root user: bash$ su - Open a console window. Navigate to the directory that contains the 5620 SAM installation files: Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Enter the following: # yum install samjre* tomcat* samanalytics* For each package, the yum utility resolves any package dependencies and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as the package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: 298 3HE AAAG-TQZZA

299 5620 SAM 5650 CPAM To upgrade a 5620 SAM analytics server Complete! Upgrade analytics server Enter the following to switch back to the samadmin user: # su - samadmin Enter the following: bash$ cd /opt/5620sam/analytics/bin Enter the following: bash$./analyticsadmin.sh upgrade The script displays the following messages and prompt: Copyright Nokia Inc. All rights reserved Stopping Analytics Server SAM Analytics Application is not running Starting Analytic Server Upgrade Does this 5620 SAM Analytics Server require support for SSL? [YES/NO] Perform one of the following. a. Enable SSL on the analytics server. 1. Enter YES. The following prompt is displayed: Enter SSL Certificate Path: 2. Enter the absolute path of the SSL certificate file. Note: The certificate file must be on the local file system. If the path is correct, the following message and prompt are displayed: path/certificate_file found. Enter SSL Certificate Password: 3. Enter the certificate password. The following and status messages are displayed as the upgrade progresses: SSL Config has been updated b. Do not enable SSL on the analytics server; enter NO. The following status messages are displayed as the upgrade progresses: 3HE AAAG-TQZZA 299

300 To upgrade a 5620 SAM analytics server 5620 SAM 5650 CPAM Upgrading 5620 SAM Analytics Server...This may take several minutes to complete Updating DB TABLES After upgrade Analytic Server upgrade is completed and starting server Starting 5620 SAM Analytics Application 5620 SAM Analytics Server successfully started! Tracking nn reports... All reports successfully tracked 5620 SAM Analytics Server upgraded successfully Enter the following to view the analytics server status: bash$./analyticsadmin.sh status The following is displayed: Copyright Nokia Inc. All rights reserved 5620 SAM Analytics Server Version : Release 5620 SAM Analytics Application is running with pid: nnnnn Close the console window. END OF STEPS 300 3HE AAAG-TQZZA

301 5620 SAM 5650 CPAM 5620 SAM conversion to redundancy SAM conversion to redundancy 10.1 Overview Purpose This chapter describes the conversion of a standalone 5620 SAM system to a redundant 5620 SAM system Contents 10.1 Overview 301 Introduction General information System conversion to redundancy workflow SAM system conversion to redundancy To convert a standalone 5620 SAM system to a redundant system 305 3HE AAAG-TQZZA 301

302 General information 5620 SAM 5650 CPAM Introduction 10.2 General information Description CAUTION Service Disruption Failure to follow the requirements and restrictions that apply to 5620 SAM system deployment has serious consequences. It is strongly recommended that you engage the upgrade service for a system conversion to redundancy in a large or complex network. Converting a 5620 SAM system to redundancy requires a thorough understanding of the applicable restrictions and requirements. It is essential that you plan, document, and test the conversion in advance in a lab deployment that is representative of the target live network. Contact technical support to assess the conversion requirements of your 5620 SAM system. CAUTION Service Disruption A 5620 SAM system conversion to redundancy fails unless the requirements and restrictions described in Chapter 2, Before you begin and the 5620 SAM Planning Guide are observed, and specific conditions are in place. Before you attempt to perform a procedure in this chapter, the following must be true. The 5620 SAM system is at the release described in this guide; you cannot combine an upgrade and a conversion to redundancy in one operation. If the system to be converted is a newly upgraded system, the system is fully initialized. An upgraded main server performs crucial post-upgrade tasks during initialization. Each 5620 SAM component is running and operational. The RHEL iptables / ip6tables firewall on each station is disabled. CAUTION Service Disruption A 5620 SAM system conversion to redundancy involves a network management outage. You must perform a conversion only during a maintenance period of sufficient duration for the outage. Note: You require a 5620 SAM license file for the new standby main server, or an updated license file that includes the new standby server information. Contact technical support for information about obtaining or updating a 5620 SAM license HE AAAG-TQZZA

303 5620 SAM 5650 CPAM System conversion to redundancy workflow The 5620 SAM samconfig utility is used for component configuration and deployment. See Chapter 3, Using samconfig for information about the samconfig utility System conversion to redundancy workflow Description Stages The following is the sequence of high-level actions required to convert a standalone 5620 SAM system to a redundant system. Each link is a reference to a section in 10.4 To convert a standalone 5620 SAM system to a redundant system (p. 305) Back up the 5620 SAM configuration files; see Back up configuration files (p. 305). Gather the system information required for the conversion; see Gather required information (p. 306). Close the unrequired 5620 SAM client sessions; see Close client sessions (p. 308). Close the LogViewer utility, if it is open; see Close LogViewer utility (p. 308). Back up the 5620 SAM database; see Back up database (p. 308). Stop the main server; see Stop main server (p. 309). Convert the standalone database to a primary database; see Convert standalone database to primary database (p. 310). Convert the standalone server to a primary main server; see Convert standalone main server to primary main server (p. 311). Create an Oracle management user account and configure the associated system parameters on the standby database station; see Prepare new station for standby database installation (p. 316). 3HE AAAG-TQZZA 303

304 System conversion to redundancy workflow 5620 SAM 5650 CPAM Install the standby database; see Install standby database (p. 319). Install the standby main server; see Install standby main server (p. 322). Reinstantiate the standby database; see Reinstantiate standby database (p. 334). Use a 5620 SAM GUI client to perform sanity testing on the newly redundant 5620 SAM system HE AAAG-TQZZA

305 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system 5620 SAM system conversion to redundancy 10.4 To convert a standalone 5620 SAM system to a redundant system Description The following steps describe how to convert a 5620 SAM system in a standalone deployment to a redundant system. This requires the following: Converting the standalone main server and database to a primary main server and database Installing the standby main server and database software Reinstantiating the database on the new standby database station Steps Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. Note: Command-line examples use the following to represent the RHEL CLI prompts: # represents the prompt for the root user bash$ represents the prompt for the samadmin user Do not type the # symbol or bash$ when you enter a command. Note: You require the following user privileges: on the standalone main server station root, samadmin on the station that is to be the standby main server station root on the standalone database station root. Oracle management on the station that is to be the standby database station root Note: The samadmin user account is created on the standby main server station during this procedure. Note: The Oracle management user account is created on the standby database station during this procedure. Back up configuration files 1 Make a backup copy of each file that you have created or customized in or under the /opt/ 5620sam/server/nms and /opt/5620sam/server/jre directories on each server station. Note: At the beginning of a 5620 SAM server conversion, the 5620 SAM installation utility backs up specific configuration and log files to a timestamped directory under the installation directory. The utility then deletes directories under the main server installation directory. If you have created or customized a file under the installation directory, you risk 3HE AAAG-TQZZA 305

306 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM losing the file unless you back up the file before the conversion to a storage location that is unaffected by the conversion. Store the files in a secure location that is unaffected by 5620 SAM conversion activity. 2 If the 5620 SAM system manages Small Cell NEs, perform the following steps to back up the Small Cell files. 1. Log in to the main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/server/nms/config/femto/fsconf/fsbackup.sh all path where path is the directory that is to contain the backup files, and is optional; the default is /smallcell/backup Note: path must not include a trailing slash character (/). Gather required information 3 4 Obtain the following information from the main server station and record it for use during the conversion: hostname, which is one of the following: the hostname specified for the main server station during the previous 5620 SAM software installation or upgrade the local hostname, if an IP address was specified for the main server station during the previous 5620 SAM software installation or upgrade IP addresses IP address that the current and new 5620 SAM databases require to reach the main server IP address that the 5620 SAM GUI and OSS clients require to reach the main server (public IP address, if NAT is used) IP address that 5620 SAM auxiliary servers require to reach the main server private IP address (if NAT is used) root user password Obtain the following information from the database station and record it for use during the conversion: hostname IP addresses 306 3HE AAAG-TQZZA

307 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system IP addresses that the current and new 5620 SAM main servers require to reach the database IP address that the 5620 SAM auxiliary servers to reach the database root user password Oracle database user password Oracle SYS password 5 If the 5620 SAM deployment includes one or more auxiliary servers, perform the following steps. Otherwise, go to Step Open a 5620 SAM GUI client. 2. Choose Administration System Information from the 5620 SAM main menu. The System Information window is displayed. 3. Click on the Auxiliary Services tab. 6 Perform the following steps for each auxiliary server listed on the form: 1. Select an auxiliary server in the list and click Properties. The properties form for the auxiliary server opens. 2. Record the following information for use during the conversion: Host Name Auxiliary Server Type Server Status Public IP address Private IP address, if displayed 3. Close the auxiliary server properties form. 7 8 If the 5620 SAM deployment includes one or more client delegate servers, perform the following steps. Otherwise, go to Step Open a 5620 SAM GUI client. 2. Choose Administration System Information from the 5620 SAM main menu. The System Information window is displayed. 3. Click on the Client Delegate Servers tab. Perform the following steps for each client delegate server listed on the form: 1. Select a client delegate server in the list and click Properties. The properties form for the client delegate server opens. 2. Record the IP Address value for use during the conversion. 3. Close the client delegate server properties form. 3HE AAAG-TQZZA 307

308 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM 9 Close the System Information form, if it is open. Close LogViewer utility 10 CAUTION Service Disruption If the LogViewer utility is running during a 5620 SAM conversion to redundancy, the conversion fails. You must ensure that the LogViewer is closed. Close the LogViewer utility, if it is open. Close client sessions 11 Close the open 5620 SAM GUI and OSS client sessions. 1. Open a 5620 SAM GUI client using an account with security management privileges, such as admin. 2. Choose Administration Security 5620 SAM User Security from the 5620 SAM main menu. The 5620 SAM User Security - Security Management (Edit) form opens. 3. Click on the Sessions tab. 4. Click Search. The form lists the open 5620 SAM GUI and OSS client sessions. 5. Identify the GUI session that you are using based on the value in the Client IP column. 6. Select all sessions except your current session and click Close Session. 7. Click Yes to confirm the action. 8. Click Search to refresh the list and verify that only the current session is open. 9. Close the 5620 SAM User Security - Security Management (Edit) form. Back up database 12 CAUTION Data Loss The path of the 5620 SAM database backup directory must not include the 5620 SAM database installation directory, or data loss may occur. Ensure that the backup directory path that you specify does not include /opt/5620sam/samdb HE AAAG-TQZZA

309 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Note: Before the 5620 SAM performs a database backup, it deletes the contents of the specified backup directory. Ensure that the backup directory that you specify does not contain files that you want to retain. You must perform a database backup before you convert a 5620 SAM system to redundancy. Perform one of the following 5620 SAM System Administrator Guide procedures to back up the 5620 SAM database: To back up the 5620 SAM database from the client GUI To back up the 5620 SAM database from a CLI Stop main server Perform the following steps to stop the main server application. 1. Log in to the main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following to stop the main server application: bash$./nmsserver.bash stop 5. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 6. The main server is stopped when the command displays the following status message: Application Server is stopped If the command displays a different message, wait five minutes and return to Step Do not proceed until the server is stopped. Disable the automatic main server startup so that the main server does not start in the event of a power disruption during the upgrade. 1. Enter the following to switch to the root user: bash$ su - 2. Enter the following: # cd /etc/init.d 3. Enter the following to rename the main server startup daemon: # mv 5620SAMServerWrapper inactive.5620samserverwrapper 3HE AAAG-TQZZA 309

310 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Convert standalone database to primary database Log in to the standalone database station as the root user. Open a console window. Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following, and then enter back. <db> configure redundant ip address where address is the IP address of the new standby database The prompt changes to <db configure redundant>. If required, configure the ip-validation parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analytics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 90 Primary database parameters ip-validation Parameter main-one main-two Description IP address of primary main server Configuring the parameter enables IP validation. Default: IP address of standby main server Default: 310 3HE AAAG-TQZZA

311 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Table 90 Primary database parameters ip-validation (continued) Parameter remote-servers Description Comma-separated list of the IP addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers Default: Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to begin the database conversion: <db> apply The database conversion begins, and messages are displayed as the operation progresses. The following is displayed when the database conversion is complete: DONE db configurations updated. When the database conversion is complete, enter the following: <db> exit The samconfig utility closes. Convert standalone main server to primary main server 23 Log in to the standalone main server station as the root user. 3HE AAAG-TQZZA 311

312 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Open a console window. Ensure that no-one is logged in to the station as the samadmin user. 1. Enter the following: # who The active user sessions are listed. 2. If the samadmin user is listed, close each samadmin user session; see the RHEL documentation for more information. Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure redundancy enabled The prompt changes to <main configure redundancy>. Configure the general redundancy parameters in the following table. Table 91 Primary main server parameters redundancy Parameter ip-to-peer rsync-ip Description The primary main server IP address that the standby main server must use for general communication Default: IP address of primary network interface The primary main server IP address that the standby main server must use for data synchronization Default: IP address of primary network interface 29 Configure the database redundancy parameters in the following table, and then enter back HE AAAG-TQZZA

313 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Table 92 Primary main server parameters redundancy, database Parameter ip instance backup-sync alignment prefer-instance reinstantiation-delay Description The IP address that the primary main server must use to reach the standby database Default: Standby database instance name Default: Whether database backup file synchronization is enabled When the parameter is enabled, each 5620 SAM database backup file set is copied to the peer database station after the backup completes. You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth requirements of database backup file synchronization. You must set the parameter to the same value on each main server. Default: false Whether automatic database alignment is enabled If automatic database alignment is enabled, a main server and database attempt to assume a common role, primary or standby, after an event such as a server activity switch or database failover. In a geographically dispersed system, the function helps to ensure that a main server communicates with the local database in order to reduce the network latency between the components. For more information about database alignment, see the 5620 SAM System Administrator Guide. Default: false The name of the database instance with which the primary main server is to align The parameter is configurable when the alignment parameter is enabled. Default: The delay, in minutes, between the completion of a database failover and the automatic reinstantiation of the standby database A value of 0 disables automatic database reinstantiation. Default: Configure the peer-server redundancy parameters in the following table, and then enter back. 3HE AAAG-TQZZA 313

314 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Table 93 Primary main server parameters redundancy, peer-server Parameter ip hostname rsync-ip public-ip jndi-port ip-to-auxes snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description The standby main server IP address that the primary main server uses for general communication Default: The standby main server hostname that the primary main server uses for general communication The parameter is configurable and mandatory when the hostname parameter in the client level is configured. Default: The standby main server IP address that the primary main server uses for data synchronization Default: The IP address that the GUI and OSS clients must use to reach the standby main server Default: The TCP port on the standby main server station used for EJB JNDI messaging to GUI clients It is recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the standby main server. Default: 1099 The standby main server IP address that the auxiliary servers must use to reach the standby main server You must configure the parameter if the 5620 SAM system includes one or more auxiliary servers. Default: The IPv4 address that the managed NEs must use to reach the standby main server The IPv6 address that the managed NEs must use to reach the standby main server The TCP port on the standby main server station used for SNMP communication with the managed NEs Default: 162 The SNMP trap log ID associated with the standby main server Default: Enter the following: 314 3HE AAAG-TQZZA

315 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system <main configure redundancy> back The prompt changes to <main configure> Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. If one of the following is true, perform 7.3 To enable Small Cell management (p. 94) on the primary main server station: You need to enable Small Cell management for the first time. The 5620 SAM currently manages Small Cell NEs. 36 Start the primary main server. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash start 3HE AAAG-TQZZA 315

316 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM 4. Enter the following: bash$./nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following: -- Primary Server is UP 5. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed until the server is completely started. 37 Close the console window. Enable primary main server automatic startup 38 Enable automatic startup on the primary main server. 1. Enter the following to switch back to the root user: bash$ exit 2. Enter the following: # cd /etc/init.d 3. Enter the following: # mv inactive.5620samserverwrapper 5620SAMServerWrapper Prepare new station for standby database installation Log in as the root user on the station that is to be the standby database station. Copy the following 5620 SAM installation files for the existing release to an empty directory on the station: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samoracle-sam_r_r_revision-pp.x86_64.rpm samdb-sam_r_r_revision-pp.x86_64.rpm OracleSw_PreInstall.sh 316 3HE AAAG-TQZZA

317 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 43 CAUTION Misconfiguration Risk The 5620 SAM software includes a script that configures the Oracle environment. The script is specific to a 5620 SAM release; using a different version may cause the database creation to fail. You must run only the script that is included with the current 5620 SAM software. Enter the following: #./OracleSw_PreInstall.sh Note: A default value is displayed in brackets []. To accept the default, press. The following prompt is displayed: This script will prepare the system for a new install/restore of a 5620 SAM Version R.r Rn database. Do you want to continue? [Yes/No]: Enter Yes. The following prompt is displayed: Enter the Oracle dba group name [group]: Enter a group name. Note: The group name must match the group name specified during the primary database conversion. The following messages and prompt are displayed: Creating group group if it does not exist... done Enter the Oracle user name: 3HE AAAG-TQZZA 317

318 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM 46 Enter a username. Note: The username must match the username specified during the primary database conversion. The following messages and prompt are displayed: Oracle user [username] new home directory will be [/opt/5620sam/oracle12r1]. Checking or Creating the Oracle user home directory /opt/5620sam/oracle12r1.., Checking user username... Adding username... Changing ownership of the directory /opt/5620sam/oracle12r1 to username:group. About to unlock the UNIX user [username] Unlocking password for user username. passwd: Success Unlocking the UNIX user [username] completed Please assign a password to the UNIX user username.. New Password: 47 Enter a password. Note: The password must match the password specified during the primary database conversion. The following prompt is displayed: Re-enter new Password: 48 Re-enter the password. The following is displayed if the password change is successful: passwd: password successfully changed for username The following message and prompt are displayed: Specify whether a 5620 SAM server will be installed on this workstation. The database memory requirements will be adjusted to account for the additional load. Will the database co-exist with a 5620 SAM server on this workstation [Yes/No]: 318 3HE AAAG-TQZZA

319 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system 49 Enter Yes or No, as required. Messages like the following are displayed as the script execution completes: INFO: About to set kernel parameters in /etc/sysctl.conf... INFO: Completed setting kernel parameters in /etc/sysctl.conf... INFO: About to change the current values of the kernel parameters INFO: Completed changing the current values of the kernel parameters INFO: About to set ulimit parameters in /etc/security/limits.conf... INFO: Completed setting ulimit parameters in /etc/security/limits. conf... INFO: Completed running Oracle Pre-Install Tasks 50 When the script execution is complete, enter the following to reboot the station: # init 6 The station reboots. Install standby database When the reboot is complete, log in as the root user on the station that is to be the standby database station. Open a console window. Enter the following: # yum install samjre* samconfig* samoracle* samdb* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test 3HE AAAG-TQZZA 319

320 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following: <db> configure type standby The prompt changes to <db configure>. If required, configure the ip parameter; enter the following: Note: The default is the IP address of the primary network interface on the station. <db configure> ip address where address is the IP address of this database Enter the following: <db configure> redundant ip address where address is the IP address of the primary database The prompt changes to <db configure redundant>. Enter the following, and then enter back : <db configure redundant> instance instance_name where instance_name is the primary database instance name Configure the passwords parameters in the following table, and then enter back. Note: The values must match the primary database values HE AAAG-TQZZA

321 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Note: After you save the configuration, you cannot use samconfig to change a database password; you must use the method described in the 5620 SAM System Administrator Guide. Table 94 Standby database parameters passwords Parameter user sys Description Database user password; the password must match the password specified during the primary database installation Default: available from technical support Oracle SYS user password; the password must match the password specified during the primary database installation Default: available from technical support 61 If required, enable IP validation to specify the server components that have access to the 5620 SAM database; configure the parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 95 Standby database parameters ip-validation Parameter main-one main-two remote-servers Description IP address of primary main server Configuring the parameter enables IP validation. Default: IP address of standby main server Default: Comma-separated list of the IP addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers Default: 62 Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 3HE AAAG-TQZZA 321

322 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db> Enter the following to begin the database creation: <db> apply The database creation begins, and messages are displayed as the creation progresses. The following is displayed when the database creation is complete: DONE db configurations updated. When the database creation is complete, enter the following: <db> exit The samconfig utility closes. Enter the following to reboot the standby database station: # init 6 The station reboots. Install standby main server Log in as the root user on the station that is to be the standby main server station. Perform one of the following. a. If the standby main server and database are being installed on separate stations, copy the following files to an empty directory on the station: samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm b. If the standby main server and database are being installed on the same station, copy the following file to the 5620 SAM software directory on the station: 322 3HE AAAG-TQZZA

323 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system samserver-sam_r_r_revision-pp.x86_64.rpm samneo4j-sam_r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level Open a console window. Ensure that no-one is logged in to the station as the samadmin user. 1. Enter the following: # who The active user sessions are listed. 2. If the samadmin user is listed, close each samadmin user session; see the OS documentation for information about closing user sessions. Navigate to the directory that contains the new 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set Perform one of the following. a. If the main server and database are being installed on separate stations, enter the following: # yum install samjre* samconfig* samserver* samneo4j* b. If the main server and database are being installed on the same station, enter the following: # yum install samserver* samneo4j* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug 3HE AAAG-TQZZA 323

324 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 73 The initial 5620 SAM server installation on a station creates the samadmin user account and assigns a randomly generated password. If this is the first main, auxiliary, analytics, or client delegate server installation on the station, change the samadmin password. Note: The samadmin password must not contain symbol, or enodeb device management may be compromised. 1. Enter the following: # passwd samadmin The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Confirm Password: 3. Re-enter the password. 4. Record the password and store it in a secure location Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure The prompt changes to <main configure>. Enter the following: 324 3HE AAAG-TQZZA

325 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Note: You cannot start a main server unless the main server configuration includes a current and valid license. You can use samconfig to specify the license file in this step, or later import the license, as described in Software and license configuration procedures in the 5620 SAM System Administrator Guide. <main configure> license license_file where license_file is the absolute path of the 5620 SAM license zip file Enter the following: <main configure> redundancy enabled The prompt changes to <main configure redundancy>. Configure the general redundancy parameters in the following table. Table 96 Standby main server parameters redundancy Parameter ip-to-peer rsync-ip Description The standby main server IP address that the primary main server must use for general communication Default: IP address of primary network interface The standby main server IP address that the primary main server must use for data synchronization Default: IP address of primary network interface 79 Configure the database redundancy parameters in the following table, and then enter back. Table 97 Standby main server parameters redundancy, database Parameter ip instance Description The IP address that the standby main server must use to reach the primary database Default: Primary database instance name Default: 3HE AAAG-TQZZA 325

326 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Table 97 Standby main server parameters redundancy, database (continued) Parameter backup-sync alignment prefer-instance reinstantiation-delay Description Whether database backup file synchronization is enabled When the parameter is enabled, each 5620 SAM database backup file set is copied to the peer database station after the backup completes. You must ensure that there is sufficient network bandwidth between the database stations before you enable this parameter. See the 5620 SAM Planning Guide for information about the bandwidth requirements of database backup file synchronization. You must set the parameter to the same value on each main server. Default: false Whether automatic database alignment is enabled If automatic database alignment is enabled, a main server and database attempt to assume a common role, primary or standby, after an event such as a server activity switch or database failover. In a geographically dispersed system, the function helps to ensure that a main server communicates with the local database in order to reduce the network latency between the components. For more information about database alignment, see the 5620 SAM System Administrator Guide. Default: false The name of the database instance with which the standby main server is to align The parameter is configurable when the alignment parameter is enabled. Default: The delay, in minutes, between the completion of a database failover and the automatic reinstantiation of the standby database A value of 0 disables automatic database reinstantiation. Default: Configure the peer-server redundancy parameters in the following table, and then enter back. Table 98 Standby main server parameters redundancy, peer-server Parameter ip Description The primary main server IP address that the standby main server uses for general communication Default: 326 3HE AAAG-TQZZA

327 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Table 98 Standby main server parameters redundancy, peer-server (continued) Parameter hostname rsync-ip public-ip jndi-port ip-to-auxes snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description The primary main server hostname that the standby main server uses for general communication The parameter is configurable and mandatory when the hostname parameter in the client level is configured. Default: The primary main server IP address that the standby main server uses for data synchronization Default: The IP address that the GUI and OSS clients must use to reach the standby main server Default: The TCP port on the primary main server station used for EJB JNDI messaging to GUI clients It is recommended that you accept the default unless another application uses the port, or there is a firewall between the GUI clients and the primary main server. Default: 1099 The primary main server IP address that the auxiliary servers must use to reach the primary main server You must configure the parameter if the 5620 SAM system includes one or more auxiliary servers. Default: The IPv4 address that the managed NEs must use to reach the primary main server The IPv6 address that the managed NEs must use to reach the primary main server The TCP port on the primary main server station used for SNMP communication with the managed NEs Default: 162 The SNMP trap log ID associated with the primary main server Default: Enter the following: <main configure redundancy> back The prompt changes to <main configure>. 3HE AAAG-TQZZA 327

328 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM 82 As required, configure the mediation parameters in the following table, and then enter back. Note: Some device types do not support an SNMP port value other than 162. Before you configure the snmp-port parameter to a value other than the default, you must ensure that each device type in the managed network supports the port value. Table 99 Standby main server parameters mediation Parameter nat snmp-ipv4 snmp-ipv6 snmp-port traplog-id Description Whether NAT is used between the main servers and the managed NEs Default: false The IPv4 address that the managed NEs must use to reach the standby main server Default: IPv4 address of primary network interface The IPv6 address that the managed NEs must use to reach the standby main server Default: IPv6 address of primary network interface The TCP port on the standby main server station that the managed NEs must use to reach the standby main server Default: 162 The SNMP trap log ID associated with the standby main server Default: If required, configure the ssl parameters in the following table, and then enter back. Note: If you intend to manage Small Cell NEs, you must enable the webdav parameter. Table 100 Standby main server parameters ssl Parameter secure keystore-file Description Whether communication between the main servers and the GUI clients, OSS clients, and auxiliary servers is SSL-secured Default: false The absolute path of the SSL keystore file The parameter is configurable when the secure parameter is enabled. Default: 328 3HE AAAG-TQZZA

329 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Table 100 Standby main server parameters ssl (continued) Parameter keystore-pass truststore-file truststore-pass webdav Description The SSL keystore password The parameter is configurable when the secure parameter is enabled. Default: The absolute path of the SSL truststore file The parameter is configurable when the secure parameter is enabled. Default: The SSL truststore password The parameter is configurable when the secure parameter is enabled. Default: Whether WebDAV access to enodeb activation data is enabled Default: false 84 If required, configure the oss parameters in the following table, and then enter back. Note: The parameters are configurable only if the configuration does not include one or more auxiliary servers. Table 101 Standby main server parameters oss Parameter public-ip corba-3gpp xml-output Description The IP address that the OSS clients must use to reach the standby main server Default: IP address of primary network interface Whether the 5620 SAM 3GPP OSS interface is enabled Default: false The directory in which to store the output of OSS file export operations Default: /opt/5620sam/server/xml_output 85 If the 5620 SAM system includes one or more analytics servers, configure the analytics parameters in the following table, and then enter back 3HE AAAG-TQZZA 329

330 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Table 102 Standby main server parameters analytics Parameter ip-list load-balanced load-balancing method Description A comma-separated list of analytics server IP addresses that are accessible to the main server Default: Whether the 5620 SAM is to perform load balancing among the analytics servers Default: false The load-balancing method to use The parameter is configurable when the load-balanced parameter is set to true. Default: round-robin 86 If the 5620 SAM includes an auxiliary database, configure the auxdb parameters in the following table, and then enter back. Table 103 Standby main server parameters auxdb Parameter enabled ip-list oam-test-results Description Whether the auxiliary database is enabled in the main server configuration A comma-separated list of the auxiliary database station IP addresses that are accessible to the main server Default: Whether the auxiliary database is to store OAM test results Default: false 87 As required, configure the aa-stats parameters in the following table, and then enter back. Table 104 Standby main server parameters aa-stats Parameter enabled Description Whether the 5620 SAM is to collect AA accounting statistics Default: false 330 3HE AAAG-TQZZA

331 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system Table 104 Standby main server parameters aa-stats (continued) Parameter formats aux-db storage Description AA accounting statistics file formats; the options are the following: ipdr IPDR format ram 5670 RAM format ipdr,ram IPDR and 5670 RAM formats The parameter is configurable when the enabled parameter is set to true. Default: ram Whether the 5620 SAM is to store the statistics in an auxiliary database The parameter is configurable when the enabled parameter is set to true. Default: false 88 If required, configure the registry parameters in the following table, and then enter back. Table 105 Standby main server parameters registry Parameter enabled ip-list Description Whether the 5620 SAM connects to a registry server Default: false A comma-separated list of the registry server addresses that are accessible to the main server Default: 89 Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. 3HE AAAG-TQZZA 331

332 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. If one of the following is true, perform 7.3 To enable Small Cell management (p. 94) on the standby main server station: You need to enable Small Cell management for the first time. The 5620 SAM currently manages Small Cell NEs. Create a directory on the standby main server for backing up the stored NE configurations. 1. Enter the following to switch to the samadmin user: # su samadmin 2. Enter the following: bash$ mkdir /opt/5620sam/nebackup/backup Start the standby main server. Note: If you did not specify a license file during the installation, you cannot start the main server until you import a license. See Software and license configuration procedures in the 5620 SAM System Administrator Guide for information about importing a license. 1. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 2. Enter the following: bash$./nmsserver.bash start 3. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready HE AAAG-TQZZA

333 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to a redundant system The main server is completely started when the command returns the following line of output: -- Standby Server is UP 4. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed until the server is completely started. 95 If the 5620 SAM system includes one or more Cflowd auxiliary servers, configure the following on each Cflowd auxiliary server, as described in 8.12 To configure Cflowd auxiliary server communication (p. 194): On the 5620 SAM Configuration tab: 5620 SAM Standby panel all parameters 5620 SAM-O Service panel Redundancy parameter, which must be set to true 96 If the 5620 SAM system includes one or more analytics servers, perform the following steps to enable redundancy support on the analytics server. 1. Log in to the analytics server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/analytics/bin 4. Enter the following: bash$./analyticsadmin.sh updateconfig The script displays the following messages and prompt: Copyright Nokia Inc. All rights reserved THIS ACTION UPDATES /opt/5620sam/analytics/config/install.config Please type 'YES' to continue 5. Enter YES. The script displays the first in a series of prompts. 6. At each parameter prompt, perform the associated action in the following table: Parameter prompt Repository Database Primary DB HOST IP Address Repository Database Primary DB Port Repository Database Primary DB Instance Name Secondary DB host Action Press to accept the default. Press to accept the default. Press to accept the default. Enter the standby 5620 SAM database IP address. 3HE AAAG-TQZZA 333

334 To convert a standalone 5620 SAM system to a redundant system 5620 SAM 5650 CPAM Secondary DB Port Enter the TCP port on the standby 5620 SAM database station that receives database requests. Repository Database Secondary DB Instance Name Each subsequent prompt Enter the standby 5620 SAM database instance name. Press to accept the default. 7. Close the console window. Reinstantiate standby database Open a 5620 SAM GUI client as the admin user. Choose Administration System Information from the 5620 SAM main menu. The System Information form opens. Click Re-Instantiate Standby. 100 Click Yes to confirm the action. The reinstantiation begins, and the GUI status bar displays reinstantiation information. Note: Database reinstantiation takes considerable time if the database contains a large amount of statistics data. You can also use the System Information form to monitor the reinstantiation progress. The Last Attempted Standby Re-instantiation Time is the start time; the Standby Re-instantiation State changes from In Progress to Success when the reinstantiation is complete. 101 When the reinstantiation is complete, close the System Information form. 102 Use a 5620 SAM GUI client to perform sanity testing of the newly redundant system. END OF STEPS 334 3HE AAAG-TQZZA

335 5620 SAM 5650 CPAM 5620 SAM conversion to IPv SAM conversion to IPv Overview Purpose This chapter describes the conversion of inter-component communication from IPv4 to IPv6 in a standalone or redundant 5620 SAM system Contents 11.1 Overview 335 Introduction General information System conversion to IPv6 workflow To perform the pre-conversion tasks SAM system conversion to IPv To convert a standalone 5620 SAM system to IPv To convert a redundant 5620 SAM system to IPv HE AAAG-TQZZA 335

336 General information 5620 SAM 5650 CPAM Introduction 11.2 General information Description CAUTION Service Disruption Failure to follow the requirements and restrictions that apply to 5620 SAM system deployment has serious consequences. Converting a 5620 SAM system to IPv6 requires a thorough understanding of the applicable restrictions and requirements. It is essential that you plan, document, and test the conversion procedure in advance in a lab deployment that is representative of the target live network. Contact technical support to assess the conversion requirements of your 5620 SAM system. It is strongly recommended that you engage the technical support upgrade service for a system conversion to IPv6 in a large or complex network. CAUTION Service Disruption A 5620 SAM system conversion to IPv6 fails unless the requirements and restrictions described in Chapter 2, Before you begin and the 5620 SAM Planning Guide are observed, and specific conditions are in place. Before you attempt to perform a procedure in this chapter, the following must be true. Each required IPv6 interface is plumbed and operational; see the RHEL documentation for information about enabling and configuring an IPv6 interface. The 5620 SAM system is at the release described in this guide; you cannot combine an upgrade and a conversion to IPv6 in one operation. If the system to be converted is a newly upgraded system, the system is fully initialized. An upgraded main server performs crucial post-upgrade tasks during initialization. Each 5620 SAM component is running and operational. CAUTION Service Disruption A 5620 SAM system conversion to IPv6 involves a network management outage. You must perform a conversion only during a maintenance period of sufficient duration. The 5620 SAM samconfig utility is used for component configuration and deployment. See Chapter 3, Using samconfig for information about the samconfig utility HE AAAG-TQZZA

337 5620 SAM 5650 CPAM System conversion to IPv6 workflow Before you attempt a 5620 SAM system conversion to IPv6, you must perform 11.4 To perform the pre-conversion tasks (p. 337) to collect the required information and ensure that the required conditions are in place. Table 106 Procedure 5620 SAM IPv6 conversion procedures list Purpose 11.4 To perform the pre-conversion tasks (p. 337) Prepare a standalone or redundant 5620 SAM system for conversion to IPv6 by ensuring the correct conditions are in place, gathering the required information, and backing up the configuration files and database To convert a standalone 5620 SAM system to IPv6 (p. 342) 11.6 To convert a redundant 5620 SAM system to IPv6 (p. 352) Configure a standalone 5620 SAM system to use IPv6 for inter-component communication. Configure a redundant 5620 SAM system to use IPv6 for inter-component communication System conversion to IPv6 workflow Description Stages The following is the sequence of high-level actions required to convert a standalone or redundant 5620 SAM system from IPv4 to IPv6 inter-component communication Perform the pre-conversion tasks; see 11.4 To perform the pre-conversion tasks (p. 337). To convert a standalone 5620 SAM system to IPv6, perform 11.5 To convert a standalone 5620 SAM system to IPv6 (p. 342). To convert a redundant 5620 SAM system to IPv6, perform 11.6 To convert a redundant 5620 SAM system to IPv6 (p. 352). Perform sanity testing of the system using one or more 5620 SAM GUI clients To perform the pre-conversion tasks Description The following steps describe the actions that you must perform in advance of a standalone or redundant 5620 SAM system conversion to IPv6. 3HE AAAG-TQZZA 337

338 To perform the pre-conversion tasks 5620 SAM 5650 CPAM Steps Note: You require the following user privileges: on the main server station and each auxiliary server station root, samadmin on the 5620 SAM database station root Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin Clear failed deployments 1 Clear all outstanding failed deployments; see To view and manage failed deployments in the 5620 SAM User Guide. Back up configuration files 2 3 Make a backup copy of the /opt/5620sam/server/nms/config/nms-server.xml file on each main server station. Copy the file to a secure location that is unaffected by the conversion. Gather required information 4 Obtain and record the following information for each 5620 SAM database: root user password 5 Obtain and record the following information for each main and auxiliary server: root user password samadmin user password Close unrequired clients 6 Close the open 5620 SAM GUI and OSS client sessions HE AAAG-TQZZA

339 5620 SAM 5650 CPAM To perform the pre-conversion tasks 1. Open a 5620 SAM GUI client using an account with security management privileges, such as admin. 2. Choose Administration Security 5620 SAM User Security from the 5620 SAM main menu. The 5620 SAM User Security - Security Management (Edit) form opens. 3. Click on the Sessions tab. 4. Click Search. The form lists the open 5620 SAM GUI and OSS client sessions. 5. Identify the GUI session that you are using based on the value in the Client IP column. 6. Select all sessions except your current session and click Close Session. 7. Click Yes to confirm the action. 8. Click Search to refresh the list and verify that only the current session is open. 9. Close the 5620 SAM User Security - Security Management (Edit) form. Close LogViewer 7 Close the LogViewer utility, if it is open. Verify database archive log synchronization 8 If the 5620 SAM system is redundant, ensure that no database archive log gap exists between the primary and standby 5620 SAM databases. Note: If you attempt a conversion to IPv6 when an archive log gap exists, the conversion fails. 1. In the open client GUI, view the Standby DB entry in the status bar. 2. If the entry reads Database archive log gap, you must reinstantiate the standby database. Otherwise, go to Step Choose Administration System Information from the 5620 SAM main menu. The System Information form opens. 4. Click Re-Instantiate Standby. 5. Click Yes to confirm the action. The reinstantiation begins, and the GUI status bar displays reinstantiation information. Note: Database reinstantiation takes considerable time if the database contains a large amount of statistics data. You can also use the System Information form to monitor the reinstantiation progress. The Last Attempted Standby Re-instantiation Time is the start time; the Standby Re-instantiation State changes from In Progress to Success when the reinstantiation is complete. 6. When the reinstantiation is complete, close the System Information form. 3HE AAAG-TQZZA 339

340 To perform the pre-conversion tasks 5620 SAM 5650 CPAM Verify database alignment 9 If the 5620 SAM system is redundant, ensure that the 5620 SAM database that you want as the primary database is the current primary database. Note: This step may involve a 5620 SAM database switchover, which can take considerable time. 1. In the open client GUI, choose Administration System Information from the 5620 SAM main menu. The System Information form opens. 2. View the IP Address and Hostname values in the Primary Database Server panel and the Preferred DB setting in the Primary Server panel. 3. If the Preferred DB value does not match the IP Address value, perform a database switchover. See the 5620 SAM database management chapter of the 5620 SAM System Administrator Guide for information about performing a database switchover. Back up database 10 CAUTION Data Loss The path of the 5620 SAM database backup directory must not include the 5620 SAM database installation directory, or data loss may occur. Ensure that the backup directory path that you specify does not include /opt/5620sam/samdb. Note: Before the 5620 SAM performs a database backup, it deletes the contents of the specified backup directory. Ensure that the backup directory that you specify does not contain files that you want to retain. You must perform a database backup before you convert a 5620 SAM system to IPv6. Perform one of the following 5620 SAM System Administrator Guide procedures to back up the 5620 SAM database: To back up the 5620 SAM database from the client GUI To back up the 5620 SAM database from a CLI 340 3HE AAAG-TQZZA

341 5620 SAM 5650 CPAM To perform the pre-conversion tasks Update hostname mappings 11 Update the /etc/hosts file on each main server, database, auxiliary server, and client server station, as required, to associate each component hostname with an IPv6 address instead of an IPv4 address. END OF STEPS 3HE AAAG-TQZZA 341

342 To convert a standalone 5620 SAM system to IPv SAM 5650 CPAM 5620 SAM system conversion to IPv To convert a standalone 5620 SAM system to IPv Description The following steps describe how to change the communication between components in a standalone 5620 SAM system from IPv4 to IPv6. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses Steps Note: You require the following user privileges: on each main and auxiliary server station root, samadmin on each 5620 SAM database station root Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user Disable automatic main server startup 1 Prevent the main server from starting in the event of a power disruption during the conversion. 1. Log in to the main server station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/init.d 4. Enter the following: # mv 5620SAMServerWrapper inactive.5620samserverwrapper Stop main server 2 Note: This step marks the beginning of the network management outage. Stop the main server. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: 342 3HE AAAG-TQZZA

343 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to IPv6 bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash stop 4. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 5. The main server is stopped when the following is displayed: Application Server is stopped If the command displays a different message, wait five minutes and return to Step 2 4.Do not proceed until the server is stopped. Stop 5620 SAM database 3 Stop the database. 1. Log in to the 5620 SAM database station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following to stop the Oracle proxy: #./S965620SAMOracleProxyWrapper stop 5. Enter the following to stop the 5620 SAM database: #./S95db5620sam stop Do not proceed until the command displays the following message: Done Configure 5620 SAM database 4 5 Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following: <db> configure ip address 3HE AAAG-TQZZA 343

344 To convert a standalone 5620 SAM system to IPv SAM 5650 CPAM where address is the IPv6 address that the other 5620 SAM components must use to reach the database The prompt changes to <db configure>. 6 If required, configure the ip-validation parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 107 Standalone database parameters ip-validation Parameter main-one remote-servers Description IPv6 address of main server Configuring the parameter enables IP validation. Comma-separated list of the IPv6 addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers 7 8 Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to apply the configuration changes: <db> apply The changes are applied HE AAAG-TQZZA

345 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to IPv6 9 Enter the following: <db> exit The samconfig utility closes. Configure auxiliary servers If the 5620 SAM system includes auxiliary servers, perform Step 11 to Step 23 on each auxiliary server station. Otherwise, go to Step 24. Stop the auxiliary server. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop The auxiliary server stops. Enter the following to switch to the root user: bash$ su - Enter the following: # samconfig -m aux The following is displayed: Start processing command line inputs... <aux> Enter the following: <aux> configure ip address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server The prompt changes to <aux configure>. To enable IPv6 for call-trace data collection, enter the following, and then enter back two times. 3HE AAAG-TQZZA 345

346 To convert a standalone 5620 SAM system to IPv SAM 5650 CPAM <aux configure> service calltrace ipv6 address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server To enable IPv6 for PCMD record collection, enter the following, and then enter back two times. <aux configure> service pcmd ipv6 address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server Enter the following, and then enter back. <aux configure> main-server ip-one address where address is the main server IPv6 address that the auxiliary server must use to reach the main server Enter the following: <aux configure> data-sync local-ip address where address is the IPv6 address of the interface on this station that the peer auxiliary server in an auxiliary server pair must use to reach this auxiliary server The prompt changes to <aux configure data-sync>. Enter the following, and then enter back. <aux configure data-sync> peer-ip address where address is the IPv6 address of the interface on the peer auxiliary server station in an auxiliary server pair that this auxiliary server must use to reach the other auxiliary server If the OSS clients require IPv6 access, enter the following, and then enter back. <aux configure> oss public-ip address where address is the IPv6 address that the OSS clients must use to reach the auxiliary server Verify the auxiliary server configuration. 1. Enter the following: <aux configure> show-detail The auxiliary server configuration is displayed. 2. Review each parameter to ensure that the value is correct HE AAAG-TQZZA

347 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to IPv6 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <aux configure> back The prompt changes to <aux> Enter the following: <aux> apply The configuration is applied. Enter the following: <aux> exit The samconfig utility closes. Configure main server Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure ip address where address is the main server IPv6 address that the database must use to reach the main server The prompt changes to <main configure>. As required, configure the client parameters as described in the following table, and then enter back. 3HE AAAG-TQZZA 347

348 To convert a standalone 5620 SAM system to IPv SAM 5650 CPAM Table 108 Standalone main server parameters client Parameter nat hostname public-ip delegates Description Not applicable to IPv6 If the parameter is enabled, disable the parameter. The main server hostname, if the GUI clients, OSS clients, and auxiliary servers are to use hostnames, rather than IP addresses, for communication with the main server Modify the value if the hostname changes as part of the conversion to IPv6. The IPv6 address that the GUI and OSS clients must use to reach the main server The parameter is configurable and mandatory when the hostname parameter is unconfigured. A list of the client delegate servers, in the following format: address1;path1,address2;path2...addressn;pathn where an address value is a client delegate server IP address a path value is the absolute file path of the client delegate server installation location Replace each IPv4 address with the appropriate IPv6 address Enter the following, and then enter back. <main configure> database ip address where address is the IPv6 address of the database To enable IPv6 for communication with the managed network, enter the following, and then enter back. <main configure> mediation snmp-ipv6 address where address is the main server IPv6 address that the managed NEs must use to reach the main server The prompt changes to <main configure mediation>. 29 To disable IPv4 for communication with the managed network, perform the following steps. 1. Enter the following: <main configure> mediation no snmp-ipv4 2. Enter the following: 348 3HE AAAG-TQZZA

349 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to IPv6 <main configure mediation> no nat 3. Enter the following: <main configure mediation> back 30 Perform one of the following. a. If the 5620 SAM system does not include auxiliary servers, and the OSS clients require IPv6 access, enter the following, and then enter back : <main configure> oss public-ip address where address is the IPv6 address that the OSS clients must use to reach the main server b. If the 5620 SAM system includes auxiliary servers, configure the aux parameters in the following table, and then enter back. Table 109 Standalone main server parameters aux Parameter ip-to-auxes preferred-list reserved-list peer-list calltrace-pairs Description The primary main server IPv6 address that the auxiliary servers must use to reach the main server Default: Comma-separated list of Preferred auxiliary server IPv6 addresses Default: Comma-separated list of Reserved auxiliary server IPv6 addresses Default: Comma-separated list of Remote auxiliary server IPv6 addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN where each Preferred_address,Reserved_address set represents the IPv6 addresses of the Preferred and Reserved auxiliary servers in a call-trace auxiliary server pair If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 3HE AAAG-TQZZA 349

350 To convert a standalone 5620 SAM system to IPv SAM 5650 CPAM Table 109 Standalone main server parameters aux (continued) Parameter pcmd-pairs Description List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN where each Preferred_address,Reserved_address set represents the IPv6 addresses of the Preferred and Reserved auxiliary servers in a PCMD auxiliary server pair If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: To configure IPv6 communication with a registry server, enter the following, and then enter back. <main configure> registry ip-list address1,address2...addressn where address1,address2...addressn are the registry server IPv6 addresses Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. Enter the following: <main> apply The configuration is applied. Enter the following: 350 3HE AAAG-TQZZA

351 5620 SAM 5650 CPAM To convert a standalone 5620 SAM system to IPv6 <main> exit The samconfig utility closes. Start 5620 SAM database 35 Start the database. 1. Log in to the 5620 SAM database station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following to start the 5620 SAM database: #./S95db5620sam start Do not proceed until the command displays the following message: Done 5. Enter the following to start the Oracle proxy: #./S965620SAMOracleProxyWrapper start Start main server Enable the automatic main server startup. 1. Enter the following: # cd /etc/init.d 2. Enter the following: # mv inactive.5620samserverwrapper 5620SAMServerWrapper Start the main server. 1. Log in as the samadmin user on the main server station. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following: bash$./nmsserver.bash start 5. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. 3HE AAAG-TQZZA 351

352 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following: -- Main Server is UP 6. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Start auxiliary servers 38 If the 5620 SAM system includes auxiliary servers, start each auxiliary server. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The auxiliary server starts. END OF STEPS 11.6 To convert a redundant 5620 SAM system to IPv Description The following steps describe how to change the communication between components in a redundant 5620 SAM system from IPv4 to IPv6. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses. Note: You require the following user privileges: on each main and auxiliary server station root, samadmin on each 5620 SAM database station root Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 352 3HE AAAG-TQZZA

353 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv Steps Disable automatic startup, standby main server 1 Prevent the standby main server from starting in the event of a power disruption during the conversion. 1. Log in as the root user on the standby main server station. 2. Open a console window. 3. Enter the following: # cd /etc/init.d 4. Enter the following: # mv 5620SAMServerWrapper inactive.5620samserverwrapper Stop standby main server 2 Stop the standby main server. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash force_stop 4. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 5. The main server is stopped when the following is displayed: Application Server is stopped If the command displays a different message, wait five minutes and return to Step 2 4.Do not proceed until the server is stopped. Stop reserved auxiliary servers 3 If the 5620 SAM system includes auxiliary servers, perform the following steps on each reserved auxiliary server station. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: 3HE AAAG-TQZZA 353

354 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop The auxiliary server stops. Stop standby 5620 SAM database 4 Stop the standby database. 1. Log in to the standby database station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following to stop the Oracle proxy: #./S965620SAMOracleProxyWrapper stop 5. Enter the following to stop the 5620 SAM database: #./S95db5620sam stop Do not proceed until the command displays the following message: Done Disable automatic startup, primary main server 5 Prevent the primary main server from starting in the event of a power disruption during the conversion. 1. Log in to the primary main server station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/init.d 4. Enter the following: # mv 5620SAMServerWrapper inactive.5620samserverwrapper Stop primary main server 6 Stop the primary main server. Note: This step marks the beginning of the network management outage. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 354 3HE AAAG-TQZZA

355 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 3. Enter the following: bash$./nmsserver.bash force_stop 4. Enter the following to display the main server status: bash$./nmsserver.bash appserver_status The command displays a status message. 5. The main server is stopped when the following is displayed: Application Server is stopped If the command displays a different message, wait five minutes and return to Step 6 4.Do not proceed until the server is stopped. Stop preferred auxiliary servers 7 If the 5620 SAM system includes auxiliary servers, perform the following steps on each preferred auxiliary server station. 1. Log in as the samadmin user: 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstop The auxiliary server stops. Stop primary 5620 SAM database 8 Stop the primary database. 1. Log in to the primary database station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/rc3.d 4. Enter the following: #./S965620SAMOracleProxyWrapper stop 5. Enter the following: #./S95db5620sam stop Do not proceed until the command displays the following: Done 3HE AAAG-TQZZA 355

356 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Configure primary 5620 SAM database Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following: <db> configure ip address where address is the IPv6 address of this database The prompt changes to <db configure>. Enter the following, and then enter back : <db configure> redundant ip address where address is the IPv6 address of the peer database If required, configure the ip-validation parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 110 Primary database parameters ip-validation Parameter main-one main-two remote-servers Description IPv6 address of primary main server Configuring the parameter enables IP validation. IPv6 address of standby main server Comma-separated list of the IPv6 addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers 356 3HE AAAG-TQZZA

357 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to apply the configuration changes: <db> apply The changes are applied. Enter the following: <db> exit The samconfig utility closes. Start primary 5620 SAM database 16 Start the primary database. 1. Enter the following: # cd /etc/rc3.d 2. Enter the following to start the 5620 SAM database: #./S95db5620sam start Do not proceed until the command displays the following message: Done 3. Enter the following to start the Oracle proxy: #./S965620SAMOracleProxyWrapper start Configure primary main server 17 Log in as the root user on the primary main server station. 3HE AAAG-TQZZA 357

358 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Open a console window. Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure ip address where address is the main server IPv6 address that each database must use to reach the main server The prompt changes to <main configure>. As required, configure the client parameters as described in the following table, and then enter back. Table 111 Primary main server parameters client Parameter nat hostname public-ip Description Not applicable to IPv6 If the parameter is enabled, disable the parameter. The main server hostname, if the GUI clients, OSS clients, and auxiliary servers are to use hostnames, rather than IP addresses, for communication with the main server Modify the value if the hostname changes as part of the conversion to IPv6. The IPv6 address that the GUI and OSS clients must use to reach the main server The parameter is configurable and mandatory when the hostname parameter is unconfigured HE AAAG-TQZZA

359 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 Table 111 Primary main server parameters client (continued) Parameter delegates Description A list of the client delegate servers, in the following format: address1;path1,address2;path2...addressn;pathn where an address value is a client delegate server IP address a path value is the absolute file path of the client delegate server installation location Replace each IPv4 address with the appropriate IPv6 address Enter the following, and then enter back : <main configure> database ip address where address is the IPv6 address of the prmary database To enable IPv6 for communication with the managed network, enter the following, and then enter back : <main configure> mediation snmp-ipv6 address where address is the main server IPv6 address that the managed NEs must use to reach the main server 24 To disable IPv4 for communication with the managed network, perform the following steps. 1. Enter the following: <main configure> mediation no snmp-ipv4 2. Enter the following: <main configure mediation> no nat 3. Enter the following: <main configure mediation> back The prompt changes to <main configure>. 25 Perform one of the following. a. If the 5620 SAM system does not include auxiliary servers, and the OSS clients require IPv6 access, enter the following, and then enter back : <main configure> oss public-ip address where address is the IPv6 address that the OSS clients must use to reach the main server 3HE AAAG-TQZZA 359

360 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM b. If the 5620 SAM system includes auxiliary servers, configure the aux parameters in the following table, and then enter back. Table 112 Primary main server parameters aux Parameter ip-to-auxes preferred-list reserved-list peer-list calltrace-pairs pcmd-pairs Description The primary main server IPv6 address that the auxiliary servers must use to reach the main server Default: Comma-separated list of Preferred auxiliary server IPv6 addresses Default: Comma-separated list of Reserved auxiliary server IPv6 addresses Default: Comma-separated list of Remote auxiliary server IPv6 addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN where each Preferred_address,Reserved_address set represents the IPv6 addresses of the Preferred and Reserved auxiliary servers in a call-trace auxiliary server pair If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN where each Preferred_address,Reserved_address set represents the IPv6 addresses of the Preferred and Reserved auxiliary servers in a PCMD auxiliary server pair If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 26 Enter the following: 360 3HE AAAG-TQZZA

361 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 <main configure> redundancy enabled The prompt changes to <main configure redundancy> Enter the following: <main configure redundancy> ip-to-peer address where address is the IPv6 address that the peer main server must use to reach this main server for general communication Enter the following: <main configure redundancy> rsync-ip address where address is the IPv6 address that the peer main server must use to reach this main server for data synchronization Enter the following, and then enter back : <main configure redundancy> database ip address where address is the IPv6 address of the standby database Configure the peer-server redundancy parameters in the following table, and then enter back. Table 113 Primary main server parameters redundancy, peer-server Parameter ip rsync-ip public-ip ip-to-auxes Description The IPv6 address that this main server must use to reach the peer main server for general communication Default: The IPv6 address that this main server must use to reach the peer main server for data synchronization Default: The IPv6 address that the GUI and OSS clients must use to reach the peer main server Default: The IPv6 address that the auxiliary servers must use to reach the peer main server You must configure the parameter if the 5620 SAM system includes one or more auxiliary servers. Default: 3HE AAAG-TQZZA 361

362 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Table 113 Primary main server parameters redundancy, peer-server (continued) Parameter snmp-ipv6 Description The IPv6 address that the managed NEs must use to reach the peer main server Configure the parameter only if you need to enable IPv6 for communication with managed NEs Enter the following: <main configure redundancy> back The prompt changes to <main configure>. To configure IPv6 communication with a registry server, enter the following, and then enter back. <main configure> registry ip-list address1,address2...addressn where address1,address2...addressn are the registry server IPv6 addresses Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes HE AAAG-TQZZA

363 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 Configure preferred auxiliary servers If the 5620 SAM system does not include auxiliary servers, go to Step 52. Otherwise, perform Step 37 to Step 50 on each preferred auxiliary server station. Log in as the root user. Open a console window. Enter the following: # samconfig -m aux The following is displayed: Start processing command line inputs... <aux> Enter the following: <aux> configure ip address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server The prompt changes to <aux configure>. To enable IPv6 for call-trace data collection, enter the following, and then enter back two times. <aux configure> service calltrace ipv6 address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server To enable IPv6 for PCMD record collection, enter the following, and then enter back two times. <aux configure> service pcmd ipv6 address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server 3HE AAAG-TQZZA 363

364 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM 43 Enter the following: <aux configure> main-server ip-one address where address is the IPv6 address that the auxiliary server must use to reach the primary main server The prompt changes to <aux configure main-server> Enter the following, and then enter back : <aux configure main-server> ip-two address where address is the IPv6 address that the auxiliary server must use to reach the standby main server Enter the following: <aux configure> data-sync local-ip address where address is the IPv6 address of the interface on this station that the peer auxiliary server in an auxiliary server pair must use to reach this auxiliary server The prompt changes to <aux configure data-sync>. Enter the following, and then enter back : <aux configure data-sync> peer-ip address where address is the IPv6 address of the interface on the peer auxiliary server station in an auxiliary server pair that this auxiliary server must use to reach the other auxiliary server If the OSS clients require IPv6 access, enter the following, and then enter back : <aux configure> oss public-ip address where address is the IPv6 address that the OSS clients must use to reach the auxiliary server The prompt changes to <aux configure oss>. Verify the auxiliary server configuration. 1. Enter the following: <aux configure> show-detail The auxiliary server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility HE AAAG-TQZZA

365 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 4. When you are certain that the configuration is correct, enter the following: <aux configure> back The prompt changes to <aux> Enter the following: <aux> apply The configuration is applied. Enter the following: <aux> exit The samconfig utility closes. Start preferred auxiliary servers 51 If the 5620 SAM system includes auxiliary servers, perform the following steps on each preferred auxiliary server station. 1. Log in as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The auxiliary server starts. Enable automatic startup, primary main server 52 Enable the automatic startup of the primary main server. 1. Log in as the samadmin user on the primary main server station. 2. Open a console window. 3. Enter the following: # cd /etc/init.d 4. Enter the following: # mv inactive.5620samserverwrapper 5620SAMServerWrapper Start primary main server 53 Start the primary main server. 3HE AAAG-TQZZA 365

366 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Note: The primary main server startup marks the end of the network management outage. 1. Enter the following on the standby main server station: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash start 4. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following line of output: -- Primary Server is UP 5. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed until the server is completely started. Configure standby 5620 SAM database Log in as the root user on the standby database station. Open a console window. Enter the following: # samconfig -m db The following is displayed: Start processing command line inputs... <db> Enter the following: <db> configure type standby The prompt changes to <db configure> HE AAAG-TQZZA

367 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv Enter the following: <db configure> ip address where address is the IPv6 address of this database Enter the following: <db configure> redundant ip address where address is the IPv6 address of the prmary database The prompt changes to <db configure redundant>. Enter the following, and then enter back : <db configure redundant> instance instance_name where instance_name is the prmary database instance name Enter the following, and then enter back : <db configure> passwords sys password where password is the database SYS user password The prompt changes to <db configure passwords>. If required, configure the ip-validation parameters in the following table, and then enter back. Note: When you enable IP validation on a 5620 SAM system that includes auxiliary servers, Cflowd auxiliary servers, or analtyics servers, you must configure the remote-servers parameter; otherwise, the servers cannot reach the database. Table 114 Standby database parameters ip-validation Parameter main-one main-two Description IPv6 address of standby main server Configuring the parameter enables IP validation. IPv6 address of primary main server 3HE AAAG-TQZZA 367

368 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Table 114 Standby database parameters ip-validation (continued) Parameter remote-servers Description Comma-separated list of the IPv6 addresses of each of the following components that must connect to the database: auxiliary servers Cflowd auxiliary servers analytics servers Verify the database configuration. 1. Enter the following: <db configure> show-detail The database configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <db configure> back The prompt changes to <db>. Enter the following to apply the configuration changes: <db> apply The changes are applied. Enter the following: <db> exit The samconfig utility closes. Start standby 5620 SAM database 66 Start the standby database. 1. Enter the following: # cd /etc/rc3.d 2. Enter the following to start the 5620 SAM database: #./S95db5620sam start 368 3HE AAAG-TQZZA

369 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 Do not proceed until the command displays the following message: Done 3. Enter the following to start the Oracle proxy: #./S965620SAMOracleProxyWrapper start Configure standby main server Log in to the standby main server station as the root user. Open a console window. Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure ip address where address is the main server IPv6 address that each database must use to reach the main server The prompt changes to <main configure>. As required, configure the client parameters as described in the following table, and then enter back. Table 115 Standby main server parameters client Parameter nat hostname Description Not applicable to IPv6 If the parameter is enabled, disable the parameter. The main server hostname, if the GUI clients, OSS clients, and auxiliary servers are to use hostnames, rather than IP addresses, for communication with the main server Modify the value if the hostname changes as part of the conversion to IPv6. 3HE AAAG-TQZZA 369

370 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Table 115 Standby main server parameters client (continued) Parameter public-ip delegates Description The IPv6 address that the GUI and OSS clients must use to reach the main server The parameter is configurable and mandatory when the hostname parameter is unconfigured. A list of the client delegate servers, in the following format: address1;path1,address2;path2...addressn;pathn where an address value is a client delegate server IP address a path value is the absolute file path of the client delegate server installation location Replace each IPv4 address with the appropriate IPv6 address Enter the following, and then enter back : <main configure> database ip address where address is the IPv6 address of the standby database To enable IPv6 for communication with the managed network, enter the following, and then enter back : <main configure> mediation snmp-ipv6 address where address is the main server IPv6 address that the managed NEs must use to reach the main server 74 To disable IPv4 for communication with the managed network, perform the following steps. 1. Enter the following: <main configure mediation> no snmp-ipv4 2. Enter the following: <main configure mediation> no nat 3. Enter the following: <main configure mediation> back 75 Perform one of the following. a. If the 5620 SAM system does not include auxiliary servers, and the OSS clients require IPv6 access, enter the following, and then enter back : 370 3HE AAAG-TQZZA

371 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 <main configure> oss public-ip address where address is the IPv6 address that the OSS clients must use to reach the main server b. If the 5620 SAM system includes auxiliary servers, configure the aux parameters in the following table, and then enter back. Table 116 Standby main server parameters aux Parameter ip-to-auxes preferred-list reserved-list peer-list calltrace-pairs pcmd-pairs Description The primary main server IPv6 address that the auxiliary servers must use to reach the main server Default: Comma-separated list of Preferred auxiliary server IPv6 addresses Default: Comma-separated list of Reserved auxiliary server IPv6 addresses Default: Comma-separated list of Remote auxiliary server IPv6 addresses Default: List of Preferred and Reserved call-trace auxiliary server pairs, in the following format; configurable when the calltrace parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN where each Preferred_address,Reserved_address set represents the IPv6 addresses of the Preferred and Reserved auxiliary servers in a call-trace auxiliary server pair If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: List of Preferred and Reserved PCMD auxiliary server pairs, in the following format; configurable when the pcmd parameter is enabled: Preferred_address1,Reserved_address1 Preferred_address2, Reserved_address2...Preferred_addressN,Reserved_addressN where each Preferred_address,Reserved_address set represents the IPv6 addresses of the Preferred and Reserved auxiliary servers in a PCMD auxiliary server pair If a pair includes no Reserved auxiliary server, specify the pair as shown below without the comma separator: Preferred_address Default: 3HE AAAG-TQZZA 371

372 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM Enter the following: <main configure> redundancy enabled The prompt changes to <main configure redundancy>. Enter the following: <main configure redundancy> ip-to-peer address where address is the IPv6 address that the peer main server must use to reach this main server for general communication Enter the following: <main configure redundancy> rsync-ip address where address is the IPv6 address that the peer main server must use to reach this main server for data synchronization Enter the following, and then enter back : <main configure redundancy> database ip address where address is the IPv6 address of the primary database Configure the peer-server redundancy parameters in the following table, and then enter back. Table 117 Standby main server parameters redundancy, peer-server Parameter ip rsync-ip public-ip Description The IPv6 address that this main server must use to reach the peer main server for general communication Default: The IPv6 address that this main server must use to reach the peer main server for data synchronization Default: The IPv6 address that the GUI and OSS clients must use to reach the peer main server Default: 372 3HE AAAG-TQZZA

373 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 Table 117 Standby main server parameters redundancy, peer-server (continued) Parameter ip-to-auxes snmp-ipv6 Description The IPv6 address that the auxiliary servers must use to reach the peer main server You must configure the parameter if the 5620 SAM system includes one or more auxiliary servers. Default: The IPv6 address that the managed NEs must use to reach the peer main server Configure the parameter only if you need to enable IPv6 for communication with managed NEs Enter the following: <main configure redundancy> back The prompt changes to <main configure>. To configure IPv6 communication with a registry server, enter the following, and then enter back. <main configure> registry ip-list address1,address2...addressn where address1,address2...addressn are the registry server IPv6 addresses Verify the main server configuration. 1. Enter the following: <main configure> show-detail The main server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility. 4. When you are certain that the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. Enter the following: <main> apply The configuration is applied. 3HE AAAG-TQZZA 373

374 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM 85 Enter the following: <main> exit The samconfig utility closes. Configure reserved auxiliary servers If the 5620 SAM system does not include auxiliary servers, go to Step 101. Otherwise, perform Step 87 to Step 99 on each reserved auxiliary server station. Log in as the root user. Enter the following: # samconfig -m aux The following is displayed: Start processing command line inputs... <aux> Enter the following: <aux> configure ip address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server The prompt changes to <aux configure>. To enable IPv6 for call-trace data collection, enter the following, and then enter back two times. <aux configure> service calltrace ipv6 address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server To enable IPv6 for PCMD record collection, enter the following, and then enter back two times. <aux configure> service pcmd ipv6 address where address is the auxiliary server IPv6 address that the managed NEs must use to reach the auxiliary server 374 3HE AAAG-TQZZA

375 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 92 Enter the following: <aux configure> main-server ip-one address where address is the standby main server IPv6 address that the auxiliary server must use to reach the main server The prompt changes to <aux configure main-server> Enter the following, and then enter back : <aux configure main-server> ip-two address where address is the primary main server IPv6 address that the auxiliary server must use to reach the main server Enter the following: <aux configure> data-sync local-ip address where address is the IPv6 address of the interface on this station that the peer auxiliary server in an auxiliary server pair must use to reach this auxiliary server The prompt changes to <aux configure data-sync>. Enter the following and then enter back : <aux configure data-sync> peer-ip address where address is the IPv6 address of the interface on the peer auxiliary server station in an auxiliary server pair that this auxiliary server must use to reach the other auxiliary server If the OSS clients require IPv6 access, enter the following, and then enter back : <aux configure> oss public-ip address where address is the IPv6 address that the OSS clients must use to reach the auxiliary server Verify the auxiliary server configuration. 1. Enter the following: <aux configure> show-detail The auxiliary server configuration is displayed. 2. Review each parameter to ensure that the value is correct. 3. Configure one or more parameters, if required; see Chapter 3, Using samconfig for information about using the samconfig utility.. 4. When you are certain that the configuration is correct, enter the following: 3HE AAAG-TQZZA 375

376 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM <aux configure> back The prompt changes to <aux> Enter the following: <aux> apply The configuration is applied. Enter the following: <aux> exit The samconfig utility closes. Start reserved auxiliary servers 100 If the 5620 SAM system includes auxiliary servers, perform the following steps on each reserved auxiliary server station. 1. Log in as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ /opt/5620sam/auxserver/nms/bin/auxnmsserver.bash auxstart The auxiliary server starts. Enable automatic startup, standby main server 101 Enable the automatic startup of the standby main server. 1. Log in to the standby main server station as the root user. 2. Open a console window. 3. Enter the following: # cd /etc/init.d 4. Enter the following: # mv inactive.5620samserverwrapper 5620SAMServerWrapper Start standby main server 102 Start the standby main server. 1. Enter the following to switch to the samadmin user: 376 3HE AAAG-TQZZA

377 5620 SAM 5650 CPAM To convert a redundant 5620 SAM system to IPv6 # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash start 4. Enter the following: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information. If the main server is not completely started, the first line of status information is the following: Main Server is not ready... The main server is completely started when the command returns the following line of output: -- Standby Server is UP 5. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed until the server is completely started. Configure GUI client, test 5620 SAM system 103 If the GUI clients and client delegate servers currently use hostnames to communicate with the main servers, go to Step Configure at least one existing GUI client or client delegate server for IPv6 communication with the main servers; perform one or more of the following, as required. Note: Ensure that you specify only IPv6 addresses in URLs and GUI-based installer panels. a. Configure a single-user GUI client; perform the appropriate installation procedure in Chapter 13, Single-user client deployment. Note: You must use the original installation method to configure the client software; for example, GUI-based or web-based. b. Configure a Windows client delegate server; perform the appropriate installation procedure in Chapter 14, Client delegate server deployment. c. Configure a RHEL client delegate server. 1. Log in as the root user on the client delegate server station. 2. Open a console window. 3. Enter the following: # samconfig -m clientdelegate 3HE AAAG-TQZZA 377

378 To convert a redundant 5620 SAM system to IPv SAM 5650 CPAM The following is displayed: Start processing command line inputs... <clientdelegate> 4. Enter the following: <clientdelegate> configure server main-one address where address is the primary main server IPv6 address The prompt changes to <clientdelegate configure server>. 5. Enter the following: <clientdelegate configure server> main-two address where address is the standby main server IPv6 address 6. Enter the following: <clientdelegate configure server> exit The prompt changes to <clientdelegate>. 7. Verify the configuration; enter the following: <clientdelegate> show-detail The client delegate server configuration is displayed. 8. If the configuration is correct, enter the following: <clientdelegate> apply The configuration is applied. 9. Enter the following: <clientdelegate> exit The samconfig utility closes. 105 Use a 5620 SAM GUI client to perform sanity testing of the 5620 SAM system. END OF STEPS 378 3HE AAAG-TQZZA

379 5620 SAM 5650 CPAM 5620 SAM uninstallation SAM uninstallation 12.1 Overview Purpose This chapter describes how to uninstall the software components of a standalone or redundant 5620 SAM system Contents 12.1 Overview Introduction SAM system uninstallation workflow To uninstall an analytics server To uninstall a Cflowd auxiliary server To uninstall an auxiliary server To uninstall an auxiliary database To uninstall a main server To uninstall a 5620 SAM database Introduction Description This chapter describe how to uninstall the following 5620 SAM components: main server 5620 SAM database auxiliary database auxiliary server Cflowd auxiliary server analytics server The following chapters describe GUI client uninstallation: Chapter 13, Single-user client deployment Chapter 14, Client delegate server deployment Note: The uninstallation of a 5620 SAM component does not remove any associated RHEL iptables chains. 3HE AAAG-TQZZA 379

380 5620 SAM system uninstallation workflow 5620 SAM 5650 CPAM Complete 5620 SAM system uninstallation SAM system uninstallation workflow (p. 380) describes how to install a complete 5620 SAM system. A complete 5620 SAM system uninstallation has the following requirements. No 5620 SAM component is running when the uninstallation begins. You must uninstall the 5620 SAM components in the reverse order of the installation. Table SAM uninstallation procedures list Procedure Purpose 12.4 To uninstall an analytics server (p. 381) Remove the 5620 SAM analytics server software To uninstall a Cflowd auxiliary server (p. 383) Remove the 5620 SAM Cflowd auxiliary server software To uninstall an auxiliary server (p. 385) Remove the 5620 SAM auxiliary server software To uninstall an auxiliary database (p. 387) Remove the 5620 SAM auxiliary database software To uninstall a main server (p. 389) Remove the 5620 SAM main server software To uninstall a 5620 SAM database (p. 391) Remove the 5620 SAM database software SAM system uninstallation workflow Description Stages The following is the sequence of high-level actions required to uninstall a standalone or redundant 5620 SAM system Uninstall the single-user GUI clients; see Chapter 13, Single-user client deployment. Uninstall the client delegate servers; see Chapter 14, Client delegate server deployment. If the system includes one or more analytics servers, perform 12.4 To uninstall an analytics server (p. 381) HE AAAG-TQZZA

381 5620 SAM 5650 CPAM To uninstall an analytics server 4 If the system includes one or more Cflowd auxiliary servers, perform 12.5 To uninstall a Cflowd auxiliary server (p. 383) on each Cflowd auxiliary server If the system includes one or more auxiliary servers, perform 12.6 To uninstall an auxiliary server (p. 385). If the system includes an auxiliary database, perform 12.7 To uninstall an auxiliary database (p. 387). Uninstall each main server; perform 12.8 To uninstall a main server (p. 389). Uninstall each 5620 SAM database; perform 12.9 To uninstall a 5620 SAM database (p. 391) To uninstall an analytics server Description The following steps describe how to remove the 5620 SAM analytics server software from a station Steps Note: You require samadmin user privileges on the analytics server station. Note: bash$ in a command line represents the samadmin user prompt, and is not to be included in a typed command Log in to the analytics server station as the samadmin user. Open a console window. Enter the following: bash$ /opt/5620sam/analytics/bin/analyticsadmin.sh uninstall The script displays the following messages and prompt: Copyright (c) XX Nokia. All rights reserved THIS ACTION WILL ERASE 5620 SAM Analytics Application INSTALLATION 3HE AAAG-TQZZA 381

382 To uninstall an analytics server 5620 SAM 5650 CPAM Please type 'YES' to continue Enter YES. The analytics server stops, and the following is displayed: Stopping 5620 SAM Analytics Application 5620 SAM Analytics Application is not running The analytics server software uninstallation begins. The uninstallation is complete when the script execution is complete. Enter the following: # yum remove samanalytics The yum utility resolves any package dependencies, and displays the following prompt: Installed size: nnn M Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction When the package removal is complete, the following is displayed: Complete! Enter the following: # yum remove tomcat The yum utility resolves any package dependencies, and displays the following prompt: Installed size: nnn M Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test 382 3HE AAAG-TQZZA

383 5620 SAM 5650 CPAM To uninstall a Cflowd auxiliary server Transaction Test Succeeded Running Transaction When the package removal is complete, the following is displayed: Complete! Enter the following: # yum remove samjre The yum utility resolves any package dependencies, and displays the following prompt: Installed size: nnn M Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction When the package removal is complete, the following is displayed: Complete! Remove any files and directories that remain in the analytics server installation directory. Close the console window. END OF STEPS 12.5 To uninstall a Cflowd auxiliary server Description The following steps describe how to remove the 5620 SAM Cflowd auxiliary server software from a station. Note: You require root user privileges on the Cflowd auxiliary server station. Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command. 3HE AAAG-TQZZA 383

384 To uninstall a Cflowd auxiliary server 5620 SAM 5650 CPAM Steps Log in to the Cflowd auxiliary server station as the root user. Open a console window. Enter the following: # /opt/5620sam/dcp/bin/dcpctl.sh stop The Cflowd auxiliary server stops, and the following is displayed: Stopping 5620 SAM Cflowd Auxiliary Server SAM Cflowd Auxiliary Server is stopped successfully Enter the following commands in sequence to remove the 5620 SAM packages: # yum remove cflowdauxserver # yum remove samconfig # yum remove samjre After you enter a command, the yum utility resolves any dependencies and displays the following prompt: Installed size: nn M Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Uninstalling the 5620 SAM package... As each package removal completes, the following is displayed: Complete! Return to Step 4 as required to remove the next package in the sequence HE AAAG-TQZZA

385 5620 SAM 5650 CPAM To uninstall an auxiliary server 7 8 Remove any files and directories that remain in the /opt/5620sam/dcp directory. Close the console window. END OF STEPS 12.6 To uninstall an auxiliary server Description The following steps describe how to remove the 5620 SAM auxiliary server software from a station Steps Note: In a redundant 5620 SAM system, you must uninstall the auxiliary servers in the following order: reserved auxiliary servers of primary main server preferred auxiliary servers of primary main server Note: You require the following user privileges on the auxiliary server station: root samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 1 Stop the auxiliary server. 1. Log in to the auxiliary server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/auxserver/nms/bin 4. Enter the following: bash$./auxnmsserver.bash auxstop 5. Enter the following to display the auxiliary server status: bash$./auxnmsserver.bash auxappserver_status The command displays a status message. 6. The server is stopped when the command displays the following status message: 3HE AAAG-TQZZA 385

386 To uninstall an auxiliary server 5620 SAM 5650 CPAM Auxiliary Server is stopped If the command displays a different message, wait five minutes and return to Step 1 5.Do not proceed to the next step until the server is stopped Enter the switch to the root user: bash$ su - Enter the following commands in sequence to remove the 5620 SAM packages: # yum remove samauxserver # yum remove samconfig # yum remove samjre After you enter a command, the yum utility resolves any dependencies and displays the following prompt: Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Uninstalling the 5620 SAM package... As each package removal completes, the following is displayed: Complete! Return to Step 3 as required to remove the next package in the sequence. When all packages are removed, enter the reboot the auxiliary server station: # init 6 The station reboots HE AAAG-TQZZA

387 5620 SAM 5650 CPAM To uninstall an auxiliary database 7 Remove any files and directories that remain in the auxiliary server installation directory. END OF STEPS 12.7 To uninstall an auxiliary database Description CAUTION Steps Data Loss Performing this procedure permanently erases all auxiliary database data. Before you perform this procedure, ensure that you have a backup of the auxiliary database, if the data is of value. The following steps describe how to delete a 5620 SAM auxiliary database and remove the auxiliary database software from all auxiliary database stations. Note: You require the following user privileges on each auxiliary database station: root dba user Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command Log in to an auxiliary database station as the root user. Open a console window. Enter the following: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh uninstall The script displays the following messages and prompt: Copyright (c) XX Nokia. All rights reserved THIS ACTION WILL ERASE YOUR DATABASE Please type 'YES' to continue 3HE AAAG-TQZZA 387

388 To uninstall an auxiliary database 5620 SAM 5650 CPAM Enter YES. You are prompted for the dba password. Enter the password. The following messages are displayed as the database is stopped and the database objects are removed from each station: Stopping auxiliary database... Dropping auxiliary database... Removing data and catalog directories from all nodes When the script execution is complete, enter the following: # /opt/5620sam/samauxdb/bin/auxdbadmin.sh unconfigure The script displays the following, which includes the location of an auxiliary database configuration backup file: Copyright (c) XX Nokia. All rights reserved Cluster unconfigured. Old configurations file: /opt/vertica/config/admintools.conf.unconfigured.nnnnnnnnnn Copy the backup file to another station for safekeeping in the event that you need to restore the auxiliary database configuration. Perform the following steps on each auxiliary database station. 1. Log in to the station as the root user. 2. Open a console window. 3. Enter the following to remove the auxiliary database packages: # yum erase vertica samauxdb samjre The yum utility resolves any package dependencies and displays the following prompt: Remove 3 Package(s) Installed size: nnn M Is this ok [y/n]: 4. Enter y. The packages are removed. 5. When all packages are removed, enter the following to reboot the station: # init 6 The station reboots: 388 3HE AAAG-TQZZA

389 5620 SAM 5650 CPAM To uninstall a main server 6. After the reboot, remove the /opt/5620sam/samauxdb directory and contents. END OF STEPS 12.8 To uninstall a main server Description CAUTION Steps Service Disruption This procedure requires that you stop the 5620 SAM server and database software, which is service-affecting. Perform this procedure only during a scheduled maintenance period. The following steps describe how to remove the 5620 SAM main server software from a station. Note: To avoid a server activity switch in a redundant 5620 SAM system, you must uninstall the main servers in the following order: standby main server primary main server Note: You require the following user privileges on the main server station: root samadmin Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands: # root user bash$ samadmin user 1 Stop the main server. 1. Log in to the main server station as the samadmin user. 2. Open a console window. 3. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 4. Enter the following: bash$./nmsserver.bash stop 5. Enter the following to display the main server status: 3HE AAAG-TQZZA 389

390 To uninstall a main server 5620 SAM 5650 CPAM bash$./nmsserver.bash appserver_status The command displays a status message. 6. The main server is stopped when the command displays the following status message: Application Server is stopped If the command displays a different message, wait five minutes and return to Step 1 5.Do not proceed to the next step until the server is stopped Enter the following on the main server station to switch to the root user: bash$ su - Open a console window. Enter the following commands in sequence to remove the 5620 SAM packages: # yum remove samneo4j # yum remove samserver # yum remove samconfig # yum remove samjre After you enter a command, the yum utility resolves any dependencies and displays the following prompt: Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Uninstalling the 5620 SAM package... As each package removal completes, the following is displayed: Complete! Return to Step 4 as required to remove the next package in the sequence HE AAAG-TQZZA

391 5620 SAM 5650 CPAM To uninstall a 5620 SAM database 7 8 When all packages are removed, enter the following to reboot the main server station: # init 6 The station reboots. Remove any files and directories that remain in the main server installation directory. END OF STEPS 12.9 To uninstall a 5620 SAM database Description The following steps describe how to remove the 5620 SAM database software from a station. Note: You require root user privileges on the 5620 SAM database station Steps Log in to the database station as the root user. Open a console window. Perform one of the following. a. If the database and main server are collocated on one station, enter the following commands in sequence: Note: The yum utility stops the database before removing the software. # yum remove samdb # yum remove samoracle b. If the database and main server are on separate stations, enter the following commands in sequence: Note: The yum utility stops the database before removing the software. # yum remove samdb # yum remove samoracle # yum remove samconfig # yum remove samjre 3HE AAAG-TQZZA 391

392 To uninstall a 5620 SAM database 5620 SAM 5650 CPAM After you enter a command, the yum utility resolves any package dependencies and displays the following prompt: Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Uninstalling the 5620 SAM package... As each package removal completes, the following is displayed: Complete! Return to Step 3 as required to remove the next package in the sequence. When all packages are removed, enter the following to reboot the database station: # init 6 The station reboots. Remove any files and directories that remain in the Oracle and database installation directories. END OF STEPS 392 3HE AAAG-TQZZA

393 5620 SAM 5650 CPAM Part III: 5620 SAM client deployment Overview Purpose This part describes how to deploy a 5620 SAM single-user GUI client or client delegate server. Contents Chapter 13, Single-user client deployment 395 Chapter 14, Client delegate server deployment 425 3HE AAAG-TQZZA 393

394 5620 SAM 5650 CPAM 394 3HE AAAG-TQZZA

395 5620 SAM 5650 CPAM Single-user client deployment 13 Single-user client deployment 13.1 Overview Purpose This chapter describes 5620 SAM single-user GUI client installation, upgrade, and uninstallation Contents 13.1 Overview 395 Introduction General information To install the Oracle JRE on a RHEL station 397 Single-user client installation To install a single-user client using a web browser To install a Windows single-user client using a GUI 404 Single-user client upgrade To upgrade a single-user client 413 Single-user client uninstallation To uninstall a single-user client using a web browser To uninstall a Windows single-user client using the client uninstaller 419 3HE AAAG-TQZZA 395

396 General information 5620 SAM 5650 CPAM Introduction 13.2 General information Description The procedures in this chapter describe single-user GUI client deployment operations in a standalone or redundant 5620 SAM system. You must comply with the general requirements in Chapter 2, Before you begin, and any specific requirements in this chapter, before you attempt to deploy a single-user GUI client Platform requirements Single-user GUI client deployment is supported on the following platforms: Mac OS X Microsoft Windows RHEL Note: Web-based single-user client installation requires a specific Oracle JRE on the client station. See the 5620 SAM Planning Guide for information about the required JRE version for the OS type. The following are the security requirements that apply to single-user client deployment: Installation, upgrade, and uninstallation require only local user privileges. Only the user that installs the client software, or a user with sufficient privileges, such as root or a local administrator, can start a single-user client. Uninstallation must be performed by the user that installs the client software, or by a user with sufficient privileges, such as root or a local administrator. Microsoft Windows The following are the supported Windows versions for single-user clients: Note: Before you attempt to install the single-user client software on Windows 2012, 8, 8.1, or 10 using the GUI-based installer, you must enable Windows 7 compatibility for the installer executable file. See the OS documentation for information about setting compatibility modes. Windows Server 2008 R2 Windows Server 2012 Windows 7, 32- and 64-bit editions Windows 8 Enterprise, 64-bit edition Windows 8.1 Enterprise, 64-bit edition Windows 10 Pro, 32- and 64-bit editions 396 3HE AAAG-TQZZA

397 5620 SAM 5650 CPAM To install the Oracle JRE on a RHEL station RHEL Web-based single-user client installation on RHEL requires an Oracle JRE; other JREs such as OpenJDK are not supported To install the Oracle JRE on a RHEL station (p. 397) describes how to install the required Oracle JRE. See the 5620 SAM Planning Guide for the following RHEL single-user client platform specifications: supported OS release and patch level supported Oracle JRE version See Chapter 4, RHEL OS configuration for the RHEL OS configuration and package information. Table 119 Procedure Single-user GUI client deployment procedures Purpose 13.3 To install the Oracle JRE on a RHEL station (p. 397) 13.4 To install a single-user client using a web browser (p. 400) 13.5 To install a Windows single-user client using a GUI (p. 404) Install the required Oracle JRE for web-based single-user GUI client or client delegate server deployment on a RHEL station. Use a web browser to install the single-user GUI client software. Use a file-based utility to install the single-user GUI client software on a Microsoft Windows station To upgrade a single-user client (p. 413) Upgrade the single-user GUI client software To uninstall a single-user client using a web browser (p. 416) 13.8 To uninstall a Windows single-user client using the client uninstaller (p. 419) Use a web browser to remove the single-user GUI client software. Use an OS utility to remove the single-user GUI client software from a Microsoft Windows station To install the Oracle JRE on a RHEL station Description Steps The following steps describe how to install the required Oracle JRE on a RHEL station for webbased single-user client or client delegate server deployment. Note: You require root user privileges on the client or client delegate server station. Note: A leading # symbol in a CLI command represents the RHEL prompt for the root user; do not include the leading # symbol when you type a command. 1 2 Log in to the client or client delegate server station. Download the required Oracle JRE package from 3HE AAAG-TQZZA 397

398 To install the Oracle JRE on a RHEL station 5620 SAM 5650 CPAM Note: See the 5620 SAM Planning Guide to determine which JRE version the client software requires. Note: The packages must be in rpm format. Download only a file that has an rpm extension; for example: jre-version-linux-i586-rpm, for a 32-bit RHEL OS jre-version-linux-x64-rpm, for a 64-bit RHEL OS where version is the Java version identifier, such as 8u40, which represents version 8, update Open a console window. Enter the following to install the JRE package: # /bin/rpm -ivh path/filename where path is the absolute path to the downloaded file filename is the name of the downloaded file Enter the following commands in sequence to install the Java component: # alternatives --install /usr/bin/java java /usr/java/jrer.r.r_ nn/bin/java 1 # alternatives --set java /usr/java/jrer.r.r_nn/bin/java where R.r.r is the Java release identifier, for example, nn is the JRE update identifier, for example, 40 Enter the following commands in sequence to install the javaws component: # alternatives --install /usr/bin/javaws javaws /usr/java/jrer.r.r_ nn/bin/javaws 1 # alternatives --set javaws /usr/java/jrer.r.r_nn/bin/javaws where R.r.r is the Java release identifier, for example, nn is the JRE update identifier, for example, 40 Perform one of the following. a. Enter the following commands in sequence to install the 32-bit Mozilla browser plug-in: 398 3HE AAAG-TQZZA

399 5620 SAM 5650 CPAM To install the Oracle JRE on a RHEL station # alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so libjavaplugin.so /usr/java/jrer.r.r_nn/lib/i386/libnpjp2.so 1 # alternatives --set libjavaplugin.so /usr/java/jrer.r.r_ nn/lib/i386/libnpjp2.so where R.r.r is the Java release identifier, for example, nn is the JRE update identifier, for example, 40 b. Enter the following commands in sequence to install the 64-bit Mozilla browser plug-in: # alternatives --install /usr/lib64/mozilla/plugins/libjavaplugin.so libjavaplugin.so.x86_64 /usr/java/jrer.r.r_nn/lib/amd64/libnpjp2.so 1 # alternatives --set libjavaplugin.so /usr/java/jrer.r.r_ nn/lib/amd64/libnpjp2.so where R.r.r is the Java release identifier, for example, nn is the JRE update identifier, for example, 40 8 Close the console window. END OF STEPS 3HE AAAG-TQZZA 399

400 To install a single-user client using a web browser 5620 SAM 5650 CPAM Single-user client installation 13.4 To install a single-user client using a web browser Description The following steps describe how to install the single-user GUI client software using a web browser Steps Note: Before you perform the procedure, you must ensure that the correct Oracle JRE version is installed on the client station. See the 5620 SAM Planning Guide for information. Note: The main server to which the client connects must be running when you perform this procedure. Note: You require local user privileges on the client station Log in to the client station. Verify that you have the required access permissions to create the client installation directory; see your system administrator for information about access permissions. Use a browser on the client station to open one of the following URLs: if SSL is not enabled on the main server if SSL is enabled on the main server where server is the main server IP address or hostname The following page is displayed: 400 3HE AAAG-TQZZA

401 5620 SAM 5650 CPAM To install a single-user client using a web browser Figure SAM Client page 4 Click Install or Launch 5620 SAM Client. A form like the following is displayed. Figure 6 Opening samclientdesktop.jnlp 5 6 Perform the following steps. 1. Select the Open it with option. 2. Click Choose and use the form that opens to specify the javaws file of a supported Oracle JRE. 3. Click OK. If a security message is displayed, click Run. 3HE AAAG-TQZZA 401

402 To install a single-user client using a web browser 5620 SAM 5650 CPAM 7 If the Java setup utility shown in Figure 7, Java Setup - Welcome (p. 401) opens, the installed Java version requires an update. Click Install. Otherwise, go to Step 9. Figure 7 Java Setup - Welcome The setup utility displays installation progress, as shown in Figure 8, Java Setup Progress (p. 402). Figure 8 Java Setup Progress 8 When the panel shown in Figure 9, Java Setup - Complete (p. 403) is displayed, the Java setup is complete. Click Close HE AAAG-TQZZA

403 5620 SAM 5650 CPAM To install a single-user client using a web browser Figure 9 Java Setup - Complete 9 10 If a security message is displayed, click Run. Perform the following steps when the panel shown in Figure 10, Install 5620 SAM (p. 403) is displayed. Figure 10 Install 5620 SAM 1. Select the check box to accept the terms of the license agreement. 3HE AAAG-TQZZA 403

404 To install a Windows single-user client using a GUI 5620 SAM 5650 CPAM 2. If required, specify a client installation location other than the default. 3. Click OK. The client installation begins, and the following panel is displayed. The panel uses separate bars to indicate the overall and current task progress. When the installation is complete, the client login form opens. 11 Log in to the client GUI. Note: The default login credentials are the following: Login Name admin Password 5620Sam! END OF STEPS 13.5 To install a Windows single-user client using a GUI Description The following steps describe how to install the single-user GUI client software on a Microsoft Windows station using the 5620 SAM GUI-based installation utility. Note: Before you attempt to install the single-user client software on Windows 2012, 8, 8.1, or 10 using the GUI-based installer, you must enable Windows 7 compatibility for the installer executable file. See the OS documentation for information about setting compatibility modes. Note: The main server to which the client connects must be running when you perform this procedure HE AAAG-TQZZA

405 5620 SAM 5650 CPAM To install a Windows single-user client using a GUI Steps Note: You require local user privileges on the client station Log in to the client station. Verify that you have the required access permissions to create the client installation directory; see your system administrator for information about access permissions. Navigate to the directory that contains the installation software. Double-click on ClientInstall_SAM_R_r_revision.exe where R_r is the release identifier, in the form MAJOR_minor revision is the revision identifier, such as R1, R3, or another descriptor The splash screen shown in Figure 11, 5620 SAM installer (p. 404) opens. Figure SAM installer 5 The client installer opens, as shown in Figure 12, Introduction (p. 406). The left pane lists the installation steps. The right pane displays the current step. Click Next. 3HE AAAG-TQZZA 405

406 To install a Windows single-user client using a GUI 5620 SAM 5650 CPAM Figure 12 Introduction 6 Review and accept the terms of the license agreement shown in Figure 13, Software License Agreement (p. 406). Click Next. Figure 13 Software License Agreement 7 Select Client Installation and Configuration, as shown in Figure 14, Choose Installation Type (p. 407). Click Next HE AAAG-TQZZA

407 5620 SAM 5650 CPAM To install a Windows single-user client using a GUI Figure 14 Choose Installation Type 8 Specify a base directory in which to install the software, as shown in Figure 15, Specify the Base Directory for 5620 SAM Client Files (p. 407). Click Next. Figure 15 Specify the Base Directory for 5620 SAM Client Files 9 As shown in Figure 16, Checking Build Compatibility (p. 408), the installer indicates which software release is to be installed. Verify the information. Click Next. 3HE AAAG-TQZZA 407

408 To install a Windows single-user client using a GUI 5620 SAM 5650 CPAM Figure 16 Checking Build Compatibility 10 Perform one of the following. a. Configure the single-user client for a standalone system. 1. Ensure that the Redundancy Supported parameter is not selected, as shown in Figure 17, Main Server Configuration (p. 409). 2. Configure the Server IP Address/Hostname parameter using the IP address or hostname that the client must use to reach the main server. 3. Select the Enable Secure Communication parameter if SSL is enabled on the main server. 4. Click Install HE AAAG-TQZZA

409 5620 SAM 5650 CPAM To install a Windows single-user client using a GUI Figure 17 Main Server Configuration b. Configure the single-user client for a redundant system. 1. Select the Redundancy Support parameter shown in Figure 17, Main Server Configuration (p. 409).. 2. Configure the Server IP Address/Hostname parameter using the IP address or hostname that the client must use to reach the primary main server. 3. Configure the Server Two IP Address/Hostname parameter using the IP address or hostname that the client must use to reach the standby main server. 4. Select the Enable Secure Communication parameter if SSL is enabled on the main servers. 5. Click Install. The next panel displays installation progress, as shown in Figure 18, Installing 5620 SAM Client (p. 410) 3HE AAAG-TQZZA 409

410 To install a Windows single-user client using a GUI 5620 SAM 5650 CPAM Figure 18 Installing 5620 SAM Client 11 When the installation is complete, as shown in Figure 19, Installation Complete (p. 410), configure the Start the 5620 SAM Client parameter to specify whether you want the client to start immediately after the installation. Figure 19 Installation Complete 410 3HE AAAG-TQZZA

411 5620 SAM 5650 CPAM To install a Windows single-user client using a GUI 12 Click Done to close the installer. If you specified that the client is to start, the client update utility displays the panel shown in Figure 20, Updating... (p. 410), which uses separate bars to indicate the overall and current task progress. Figure 20 Updating... When the update is complete, the client login form opens. 13 If you specified not to start the client immediately after the installation, you can start the client later by double-clicking on the 5620 SAM Client App desktop icon. Note: You must be logged in to the station as the user that installed the client. The client update utility displays the panel shown in Figure 20, Updating... (p. 411), which uses separate bars to indicate the overall and current task progress. When the update is complete, the client login form opens. 14 Log in to the client GUI. Note: The default login credentials are the following: Login Name admin 3HE AAAG-TQZZA 411

412 To install a Windows single-user client using a GUI 5620 SAM 5650 CPAM Password 5620Sam! END OF STEPS 412 3HE AAAG-TQZZA

413 5620 SAM 5650 CPAM To upgrade a single-user client Single-user client upgrade 13.6 To upgrade a single-user client Description The following steps describe how to upgrade the single-user GUI client software Steps Note: The main server to which the client connects must be upgraded and running when you perform this procedure. Note: If you are not the original installer of the client software, you require the following user privileges on the client station: Mac OS X, Microsoft Windows local administrator RHEL root Log in to the client station. Close the client GUI, if it is open. Perform one of the following. a. Double-click the 5620 SAM client desktop icon. b. Use a web browser. 1. Open one of the following URLs: if SSL is not enabled on the main server if SSL is enabled on the main server where server is the main server IP address or hostname 3HE AAAG-TQZZA 413

414 To upgrade a single-user client 5620 SAM 5650 CPAM The following page is displayed. 2. Click Install or Launch 5620 SAM Client. The client update utility detects the new software on the main server and displays the following panel: 4 5 Click Yes to begin the upgrade. If a security message informs you that the upgrade is blocked, cancel the upgrade and go to Step 3 b. Otherwise, the following panel is displayed; separate bars indicate the current and overall task progress HE AAAG-TQZZA

415 5620 SAM 5650 CPAM To upgrade a single-user client Figure 21 Updating... When the upgrade is complete, the client login form opens. 6 Log in to the client GUI. END OF STEPS 3HE AAAG-TQZZA 415

416 To uninstall a single-user client using a web browser 5620 SAM 5650 CPAM Single-user client uninstallation 13.7 To uninstall a single-user client using a web browser Description The following steps describe how to remove the single-user GUI client software from a station using a web browser Steps Note: The uninstallation method must match the installation method. You can use this procedure to uninstall only a single-user client installed using a web browser. For example, if a single-user client installation on Windows is performed using the GUI-based 5620 SAM installer, you must perform 13.8 To uninstall a Windows single-user client using the client uninstaller (p. 419) to uninstall the client. Note: The main server to which the client connects must be running when you perform this procedure. Note: If you are not the original installer of the client software, you require the following user privileges on the client station: Mac OS X, Microsoft Windows local administrator RHEL root Log in to the client station. Close the client GUI, if it is open. Use a browser on the client station to open one of the following URLs: if SSL is not enabled on the main server if SSL is enabled on the main server where server is the main server IP address or hostname The following page is displayed HE AAAG-TQZZA

417 5620 SAM 5650 CPAM To uninstall a single-user client using a web browser Figure SAM Client page 4 Click on the Uninstall 5620 SAM Client link. The form shown in Figure 23, Opening samclient_uninstall.jnlp (p. 417) is displayed. Figure 23 Opening samclient_uninstall.jnlp 5 Perform the following steps. 1. Select the Open it with option. 2. Click Choose and use the form that opens to specify the javaws file of a supported Oracle JRE. 3. Click OK. 3HE AAAG-TQZZA 417

418 To uninstall a single-user client using a web browser 5620 SAM 5650 CPAM 6 7 If a security message is displayed, click Run. The client uninstaller opens, as shown in Figure 24, Uninstall... (p. 417). Click Yes to begin the uninstallation. Figure 24 Uninstall... The following progress indicator panel is displayed: Figure 25 Uninstall HE AAAG-TQZZA

419 5620 SAM 5650 CPAM To uninstall a Windows single-user client using the client uninstaller 8 The uninstallation is complete when the panel in Figure 26, Uninstall... (p. 418) is displayed. Click OK to close the uninstaller. Figure 26 Uninstall... 9 Remove any files that remain in the client installation directory. END OF STEPS 13.8 To uninstall a Windows single-user client using the client uninstaller Description The following steps describe how to remove the single-user GUI client software from a Microsoft Windows station using the Windows program uninstallation utility. Note: The uninstallation method must match the installation method. You can use this procedure to uninstall only a Windows single-user client installed using the GUI-based 5620 SAM installer. If a client installation is web-based, you must perform 13.7 To uninstall a single-user client using a web browser (p. 416) to uninstall the client. Note: If you are not the original installer of the client software, you require local administrator privileges on the client station. 3HE AAAG-TQZZA 419

420 To uninstall a Windows single-user client using the client uninstaller 5620 SAM 5650 CPAM Steps Log in to the client station. Close the client GUI, if it is open. Perform the following steps. 1. Click on Start Control Panel. The Control Panel window opens. 2. Under the Programs category, click on Uninstall a Program. The Programs and Features window opens. 3. Right-click on 5620 SAM Client and select Uninstall/Change. 4. If a security warning is displayed, click Continue. The following splash screen is displayed: 4 The client installer opens, as shown in Figure 27, Uninstall 5620 SAM Client (p. 419). The left pane lists the uninstallation steps. The right pane displays the current step. Click Uninstall HE AAAG-TQZZA

421 5620 SAM 5650 CPAM To uninstall a Windows single-user client using the client uninstaller Figure 27 Uninstall 5620 SAM Client 5 As shown in Figure 28, Warning (p. 421), a warning is displayed. Ensure that the conditions are true, and then click Continue with the uninstall process. Figure 28 Warning 6 The uninstaller removes the software, as shown in Figure 29, Uninstall 5620 SAM Client (p. 422). 3HE AAAG-TQZZA 421

422 To uninstall a Windows single-user client using the client uninstaller 5620 SAM 5650 CPAM Figure 29 Uninstall 5620 SAM Client 7 When the uninstallation is complete, as shown in Figure 30, Uninstall Complete (p. 422), click Done to close the uninstaller. Figure 30 Uninstall Complete 422 3HE AAAG-TQZZA

423 5620 SAM 5650 CPAM To uninstall a Windows single-user client using the client uninstaller 8 9 Close the Programs and Features window. Remove any files that remain in the client installation directory. END OF STEPS 3HE AAAG-TQZZA 423

424 To uninstall a Windows single-user client using the client uninstaller 5620 SAM 5650 CPAM 424 3HE AAAG-TQZZA

425 5620 SAM 5650 CPAM Client delegate server deployment 14 Client delegate server deployment 14.1 Overview Purpose This chapter describes 5620 SAM client delegate server installation, upgrade, and uninstallation Contents 14.1 Overview 425 Introduction General information 426 Client delegate server installation To install a client delegate server using a web browser To install a RHEL client delegate server using the yum utility To install a Windows client delegate server using a GUI To add a client delegate server to an existing system 447 Client delegate server upgrade To upgrade a client delegate server 452 Client delegate server uninstallation To uninstall a client delegate server using a web browser To uninstall a RHEL client delegate server using the yum utility To uninstall a Windows client delegate server using a GUI 460 3HE AAAG-TQZZA 425

426 General information 5620 SAM 5650 CPAM Introduction 14.2 General information Description This chapter describes client delegate server deployment in a standalone or redundant 5620 SAM system. You must comply with the general requirements in Chapter 2, Before you begin and the specific requirements in this chapter before you attempt to deploy a client delegate server Platform requirements Client delegate server deployment is supported only on the following platform types: RHEL Microsoft Windows If the 5620 SAM system uses a firewall, you must ensure that the firewall allows traffic to pass between the remote client stations and a client delegate server. See the 5620 SAM Planning Guide for firewall configuration information. RHEL Web-based client delegate server installation on RHEL requires an Oracle JRE; other JREs such as OpenJDK are not supported To install the Oracle JRE on a RHEL station (p. 397) describes how to install the Oracle JRE. A remote station that connects to a RHEL client delegate server requires X.11 or native X display redirection. X-window emulation software is not supported. See the 5620 SAM Planning Guide for the OS release and patch level requirements of a client delegate server on RHEL. See Chapter 4, RHEL OS configuration for the RHEL OS configuration and package information. Microsoft Windows The following are the supported Windows client delegate server platforms: Note: Before you attempt to install the client delegate server software on Windows 2012, 8, or 8.1 using the GUI-based installer, you must enable Windows 7 compatibility for the installer executable file. See the OS documentation for information about setting compatibility modes. Windows Server 2008 R2 Windows Server Security requirements Adding a client delegate server to an existing 5620 SAM system requires root and samadmin user privileges on each main server station HE AAAG-TQZZA

427 5620 SAM 5650 CPAM General information RHEL Client delegate server deployment requires root user privileges. Microsoft Windows Client delegate server deployment requires local administrator privileges. Table 120 Procedure Client delegate server deployment procedures Purpose 14.3 To install a client delegate server using a web browser (p. 428) 14.4 To install a RHEL client delegate server using the yum utility (p. 434) 14.5 To install a Windows client delegate server using a GUI (p. 440) 14.6 To add a client delegate server to an existing system (p. 447) Install the client delegate server software on a RHEL or Microsoft Windows station from a web page. Install the client delegate server software on a RHEL station using the RHEL yum utility. Install the client delegate server software on a Microsoft Windows station using the GUI-based 5620 SAM installation utility. Add a new client delegate server to an existing 5620 SAM system To upgrade a client delegate server (p. 452) Upgrade the client delegate server software on a RHEL or Microsoft Windows station To uninstall a client delegate server using a web browser (p. 455) 14.9 To uninstall a RHEL client delegate server using the yum utility (p. 458) To uninstall a Windows client delegate server using a GUI (p. 460) Remove the client delegate server software from a RHEL or Microsoft Windows station using a web page. Remove the client delegate server software from a RHEL station using the RHEL yum utility. Remove the client delegate server software from a Microsoft Windows station using the GUI-based 5620 SAM uninstallation utility. 3HE AAAG-TQZZA 427

428 To install a client delegate server using a web browser 5620 SAM 5650 CPAM Client delegate server installation 14.3 To install a client delegate server using a web browser Description The following steps describe how to install the client delegate server software on a RHEL or Microsoft Windows station from a web page Steps Note: Before you perform the procedure, the client delegate server address and installation directory must be configured on each main server during installation or upgrade, or as described in 14.6 To add a client delegate server to an existing system (p. 447). Note: The main server to which the client delegate server connects must be running and operational when you perform the procedure. Note: You require the following user privileges on the client delegate server station: RHEL root Windows local administrator 1 2 Log in to the client delegate server station. Use a browser on the station to open one of the following URLs: if SSL is not enabled on the main server if SSL is enabled on the main server where server is the main server IP address or hostname The following page is displayed: Figure SAM Client Delegate page 428 3HE AAAG-TQZZA

429 5620 SAM 5650 CPAM To install a client delegate server using a web browser 3 Click Install or Launch 5620 SAM Client Delegate. A form like the following is displayed. Figure 32 Opening samclientdelegate_install.jnlp Perform the following steps. 1. Select the Open with option. 2. Click Choose and use the form that opens to specify the javaws file of a supported Oracle JRE. 3. Click OK. If a security message is displayed, click Run. If the Java setup utility shown in Figure 33, Java Setup - Welcome (p. 430) opens, the installed Java version requires an update. Click Install. Otherwise, go to Step 8 3HE AAAG-TQZZA 429

430 To install a client delegate server using a web browser 5620 SAM 5650 CPAM Figure 33 Java Setup - Welcome The setup utility displays installation progress, as shown in Figure 34, Java Setup Progress (p. 430). Figure 34 Java Setup Progress 7 When the panel shown in Figure 35, Java Setup - Complete (p. 431) is displayed, the Java setup is complete. Click Close HE AAAG-TQZZA

431 5620 SAM 5650 CPAM To install a client delegate server using a web browser Figure 35 Java Setup - Complete 8 9 If a security message is displayed, click Run. Perform the following steps when the panel shown in Figure 36, Install 5620 SAM (p. 431) is displayed. Figure 36 Install 5620 SAM 1. Select the check box to accept the terms of the license agreement. 3HE AAAG-TQZZA 431

432 To install a client delegate server using a web browser 5620 SAM 5650 CPAM 2. Click OK. The client delegate server installation begins, and the following panel is displayed. The panel uses separate bars to indicate the overall and current task progress. When the installation is complete, the client login form opens. 10 Log in to ensure that the GUI opens and is correctly displayed. Note: The default client login credentials are the following: Login Name admin Password 5620Sam! Configure remote client access on RHEL client delegate server A client delegate server installation on RHEL creates a RHEL user group named sam. A user that opens a remote client session must belong to the sam user group. Add each user that requires client access to the sam user group. As required, preserve the GUI preferences of each RHEL single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the RHEL_home/5620SAM/guiPreference directory to the same directory on the client delegate server station, where RHEL_home is the RHEL user home directory HE AAAG-TQZZA

433 5620 SAM 5650 CPAM To install a client delegate server using a web browser 13 As required, preserve the GUI preferences of each Windows single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the Win_home\5620SAM\guiPreference directory to the following directory on the client delegate server station: RHEL_home/5620SAM/guiPreference where Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable RHEL_home is the RHEL user home directory 14 Perform the following steps on each station that is to open a client GUI session through the client delegate server. 1. Open a remote login session on the client delegate server. 2. Configure display redirection from the client delegate server station to the current station. 3. Enter the following to open a client session: path/nms/bin/nmsclient.bash where path is the client delegate server installation location The client login form opens. Configure remote client access on Windows client delegate server As required, preserve the GUI preferences of each Windows single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the Win_home\5620SAM\guiPreference directory to the same directory on the client delegate server station, where Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable. As required, preserve the GUI preferences of each RHEL single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the RHEL_home/5620SAM/guiPreference directory to the following directory on the client delegate server station: 3HE AAAG-TQZZA 433

434 To install a RHEL client delegate server using the yum utility 5620 SAM 5650 CPAM Win_home\5620SAM\guiPreference where RHEL_home is the RHEL user home directory Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable 17 Perform the following steps on each station that is to open a client GUI session through the client delegate server. 1. Open a Windows remote desktop session on the client delegate server station. 2. Double-click on the 5620 SAM Client Delegate desktop icon. The client login form opens. Verify remote client operation 18 Log in to the client GUI to verify the client connectivity and operation. Note: The default login credentials are the following: Login Name admin Password 5620Sam! END OF STEPS 14.4 To install a RHEL client delegate server using the yum utility Description The following steps describe how to install the client delegate server software on a RHEL station using the RHEL yum utility Steps Note: The main server to which the client connects must be running when you perform this procedure. Note: You require root user privileges on the client delegate server station. Note: A leading # symbol in a CLI command represents the RHEL prompt for the root user; do not include the leading # symbol when you type a command. 1 Log in to the client delegate server station HE AAAG-TQZZA

435 5620 SAM 5650 CPAM To install a RHEL client delegate server using the yum utility 2 Download the following 5620 SAM installation files to an empty directory on the client delegate server station. samjre-sam_r_r_revision-pp.x86_64.rpm samconfig-sam_r_r_revision-pp.x86_64.rpm samclientdelegate-sam_r_r_revision-pp.x86_64.rpm where R_r is the 5620 SAM release identifier, in the form MAJOR_minor revision is the 5620 SAM revision identifier, such as R1, R3, or another descriptor p is the patch level 3 4 Open a console window. Navigate to the directory that contains the 5620 SAM installation files. Note: Ensure that the directory contains only the installation files, and that the execute permission on each file is set. 5 6 Enter the following: # yum install samjre* samconfig* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: Enter y. The following is displayed, along with the installation status as each package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! 3HE AAAG-TQZZA 435

436 To install a RHEL client delegate server using the yum utility 5620 SAM 5650 CPAM 7 8 Perform one of the following. a. Install the software in the default location of /opt/5620sam/client. 1. Enter the following: # yum install samclientdelegate* The yum utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/n]: 2. Enter y. The following is displayed, along with the installation status as the package is installed. Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction The package installation is complete when the following is displayed: Complete! b. Install the software in a non-default location; enter the following: # rpm -i - prefix= install_dir samclientdelegate* where install_dir is the absolute path of the installation location The rpm utility resolves any package dependencies and installs the package. The initial 5620 SAM server installation on a station creates the samadmin user account and assigns a randomly generated password. If this is the first main, auxiliary, analytics, or client delegate server installation on the station, change the samadmin password. 1. Enter the following: # passwd samadmin The following prompt is displayed: New Password: 2. Enter a password. The following prompt is displayed: Confirm Password: 3. Re-enter the password. 4. Record the password and store it in a secure location HE AAAG-TQZZA

437 5620 SAM 5650 CPAM To install a RHEL client delegate server using the yum utility Enter the following: # samconfig -m clientdelegate The following is displayed: Start processing command line inputs... <clientdelegate> Enter the following: <clientdelegate> configure The prompt changes to <clientdelegate configure>. To enable SSL security between the client delegate server and each main server, enter the following: <clientdelegate configure> ssl-secure Enter the following: <clientdelegate configure> server main-one address where address is the standalone or primary main server IP address or hostname that the client delegate server must use to reach the main server The prompt changes to <clientdelegate configure server>. If the 5620 SAM system is redundant, enter the following: <clientdelegate configure server> main-two address where address is the standby main server IP address or hostname that the client delegate server must use to reach the main server Enter the following: <clientdelegate configure server> exit The prompt changes to <clientdelegate>. Verify the configuration; enter the following: <clientdelegate> show-detail The client delegate server configuration is displayed. 3HE AAAG-TQZZA 437

438 To install a RHEL client delegate server using the yum utility 5620 SAM 5650 CPAM If the configuration is correct, enter the following: <clientdelegate> apply The configuration is applied. Enter the following: <clientdelegate> exit The samconfig utility closes. Perform client software auto-update As the root user, start the local client to invoke the auto-client update, which completes the installation. 1. Enter the following: # path/nms/bin/nmsclient.bash where path is the client delegate server installation location, typically /opt/5620sam/client Click Yes to begin the update. As shown in Figure 37, Updating... (p. 437), the next panel uses separate bars to indicate the current and overall task progress. Figure 37 Updating HE AAAG-TQZZA

439 5620 SAM 5650 CPAM To install a RHEL client delegate server using the yum utility When the update is complete, the client GUI login form opens. 20 Log in to ensure that the GUI opens and is correctly displayed. Note: The default client login credentials are the following: Login Name admin Password 5620Sam! Configure remote client access A client delegate server installation on RHEL creates a RHEL user group named sam. A user that opens a remote client session must belong to the sam user group. Add each user that requires client access to the sam user group. As required, preserve the GUI preferences of each RHEL single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the RHEL_home/5620SAM/guiPreference directory to the same directory on the client delegate server station, where RHEL_home is the RHEL user home directory. As required, preserve the GUI preferences of each Windows single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the Win_home\5620SAM\guiPreference directory to the following directory on the client delegate server station: RHEL_home/5620SAM/guiPreference where Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable RHEL_home is the RHEL user home directory Perform the following steps on each station that is to open a client GUI session through the client delegate server. 1. Open a remote login session on the client delegate server. 3HE AAAG-TQZZA 439

440 To install a Windows client delegate server using a GUI 5620 SAM 5650 CPAM 2. Configure display redirection from the client delegate server station to the current station. 3. Enter the following to open a client session: path/nms/bin/nmsclient.bash where path is the client delegate server installation location, typically /opt/5620sam/client The client login form opens. 4. Log in to ensure that the GUI opens and is correctly displayed. Note: The default client login credentials are the following: Login Name admin Password 5620Sam! END OF STEPS 14.5 To install a Windows client delegate server using a GUI Description The following steps describe how to install the client delegate server software on a Microsoft Windows station using the GUI-based 5620 SAM installation utility Steps Note: The main server to which the client delegate server connects must be running when you perform this procedure. Note: You require local administrator privileges on the client delegate server station Log in to the client delegate server station. Navigate to the directory that contains the installation software. Double-click on ClientInstall_SAM_R_r_revision.exe where R_r is the release identifier, in the form MAJOR_minor revision is the revision identifier, such as R1, R3, or another descriptor The splash screen shown in Figure 38, 5620 SAM installer (p. 441) opens HE AAAG-TQZZA

441 5620 SAM 5650 CPAM To install a Windows client delegate server using a GUI Figure SAM installer 4 The client installer opens, as shown in Figure 39, Introduction (p. 441). The left pane lists the installation steps. The right pane displays the current step. Click Next. Figure 39 Introduction 5 Review and accept the terms of the license agreement shown in Figure 40, Software License Agreement (p. 442). Click Next. 3HE AAAG-TQZZA 441

442 To install a Windows client delegate server using a GUI 5620 SAM 5650 CPAM Figure 40 Software License Agreement 6 Select Client Delegate Installation and Configuration, as shown in Figure 41, Choose Installation Type (p. 442). Click Next. Figure 41 Choose Installation Type 7 Specify a base directory in which to install the software, as shown in Figure 42, Specify the Base Directory for 5620 SAM Client Files (p. 443). Click Next HE AAAG-TQZZA

443 5620 SAM 5650 CPAM To install a Windows client delegate server using a GUI Figure 42 Specify the Base Directory for 5620 SAM Client Files 8 As shown in Figure 43, Checking Build Compatibility (p. 443), the installer indicates which software release is to be installed. Verify the information. Click Next. Figure 43 Checking Build Compatibility 9 Perform one of the following. a. Configure the client delegate server for a standalone system. 3HE AAAG-TQZZA 443

444 To install a Windows client delegate server using a GUI 5620 SAM 5650 CPAM 1. Ensure that the Redundancy Support parameter is not selected, as shown in Figure 44, Main server configuration (p. 443). 2. Configure the Server IP Address parameter using the IP address or hostname that the client delegate server must use to reach the main server. 3. Select the Enable Secure Communication parameter, if SSL is enabled on the main server. 4. Click Install. Figure 44 Main server configuration b. Configure the client delegate server for a redundant system. 1. Select the Redundancy Support parameter shown in Figure 44, Main server configuration (p. 444). 2. Configure the Server IP Address parameter using the IP address or hostname that the client delegate server must use to reach the primary main server. 3. Configure the Server Two IP Address parameter using the IP address or hostname that the client delegate server must use to reach the standby main server. 4. Select the Enable Secure Communication parameter if SSL is enabled on the main servers. 5. Click Install. The next panel displays installation progress, as shown in the following figure HE AAAG-TQZZA

445 5620 SAM 5650 CPAM To install a Windows client delegate server using a GUI Figure 45 Installing 5620 SAM Client 10 When the installation is complete, ensure that the Start the 5620 SAM Client parameter is selected, as shown in Figure 46, Installation Complete (p. 445). Figure 46 Installation Complete 3HE AAAG-TQZZA 445

446 To install a Windows client delegate server using a GUI 5620 SAM 5650 CPAM 11 Click Done to close the installer. The client update utility displays the panel shown in Figure 47, Updating... (p. 445), which uses separate bars to indicate the overall and current task progress. Figure 47 Updating... When the update is complete, the client login form opens. 12 Click Cancel to close the login form. Configure remote client access 13 As required, preserve the GUI preferences of each Windows single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the Win_home\5620SAM\guiPreference directory to the same directory on the client delegate server station, where Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable HE AAAG-TQZZA

447 5620 SAM 5650 CPAM To add a client delegate server to an existing system 14 As required, preserve the GUI preferences of each RHEL single-user client user that is migrating to the client delegate server. 1. Log in to the single-user client station as the user that installed the client, or as a user that has read access to the client files and directories. 2. Copy all files in the RHEL_home/5620SAM/guiPreference directory to the following directory on the client delegate server station: Win_home\5620SAM\guiPreference where RHEL_home is the RHEL user home directory Win_home is the Windows user home directory, which is defined in the USERPROFILE environment variable Open a Windows remote desktop session on the client delegate server station. Double-click on the 5620 SAM Client App desktop icon. The client login form opens. Log in to ensure that the GUI opens and is correctly displayed. Note: The default client login credentials are the following: Login Name admin Password 5620Sam! END OF STEPS 14.6 To add a client delegate server to an existing system Description CAUTION Service Disruption This procedure requires a restart of each main server in the 5620 SAM system, which is serviceaffecting. Perform this procedure only during a scheduled maintenance period. The following steps describe how to add a new client delegate server to an existing 5620 SAM system. Note: You require the following user privileges on each main server station: 3HE AAAG-TQZZA 447

448 To add a client delegate server to an existing system 5620 SAM 5650 CPAM Steps root samadmin Note: CLI commands use the following to represent the CLI prompt: # the prompt for the root user bash$ the prompt for the samadmin user Do not type the # symbol or bash$ when you enter a command If the system is deployed in a standalone configuration, go to Step 7. Perform Step 7 to Step 19 on the standby main server. Perform Step 7 to Step 19 on the primary main server. Perform Step 20 on the primary main server station. When the primary main server is fully operational, perform Step 20 on the standby main server station. Go to Step 21. Log in to the main server station as the root user. Open a console window. Perform the following steps to stop the main server. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: 448 3HE AAAG-TQZZA

449 5620 SAM 5650 CPAM To add a client delegate server to an existing system bash$./nmsserver.bash stop 4. Enter the following to display the server status: bash$./nmsserver.bash appserver_status The command displays a status message. 5. The server is stopped when the command displays the following status message: Application Server is stopped If the command displays a different message, wait five minutes and then return to Step 9 4. Do not proceed until the server is stopped Enter the following to switch back to the root user: bash$ exit Enter the following: # samconfig -m main The following is displayed: Start processing command line inputs... <main> Enter the following: <main> configure client The prompt changes to <main configure client>. Enter the following: <main configure client> show The client configuration of the main server is displayed. The delegates parameter lists the current client delegate servers. Enter the following: <main configure client> delegates current_list,new_address;path where current_list is the comma-separated list of client delegate servers in the current main server configuration new_address is the IP address or hostname of the new client delegate server 3HE AAAG-TQZZA 449

450 To add a client delegate server to an existing system 5620 SAM 5650 CPAM path is the absolute file path of the client installation location on the client delegate server station Enter the following: <main configure client> back The prompt changes to <main configure>. Enter the following: <main configure> show-detail The main server configuration is displayed. If the configuration is correct, enter the following: <main configure> back The prompt changes to <main>. Enter the following: <main> apply The configuration is applied. Enter the following: <main> exit The samconfig utility closes. Start the main server. 1. Enter the following to switch to the samadmin user: # su - samadmin 2. Enter the following: bash$ cd /opt/5620sam/server/nms/bin 3. Enter the following: bash$./nmsserver.bash start 4. Enter the following to display the server status: bash$ /opt/5620sam/server/nms/bin/nmsserver.bash -s nms_status The command returns server status information HE AAAG-TQZZA

451 5620 SAM 5650 CPAM To add a client delegate server to an existing system If the server is not completely started, the first line of status information is the following: Main Server is not ready... The server is completely started when the command returns the one of the following messages: on a standalone main server: -- SAM Server is Up on a primary main server: -- Primary Server is UP on a standby main server: -- Standby Server is UP 5. If the command output indicates that the server is not completely started, wait five minutes and then return to Step Do not proceed until the server is completely started. 21 Close the open console windows. END OF STEPS 3HE AAAG-TQZZA 451

452 To upgrade a client delegate server 5620 SAM 5650 CPAM Client delegate server upgrade 14.7 To upgrade a client delegate server Description The following steps describe how to upgrade the client delegate server software on a RHEL or Microsoft Windows station Steps Note: The main server to which the client delegate server connects must be upgraded and running when you perform this procedure. Note: You require the following user privileges on the client delegate server station: RHEL root Windows local administrator Close each remote client GUI session that the client delegate server hosts. Log in to the client delegate server station. Close the local client GUI, if it is open. If you are upgrading a Release 14.0 RHEL client delegate server installed using the yum utility, perform the following steps. 1. Perform 14.9 To uninstall a RHEL client delegate server using the yum utility (p. 458). 2. Perform Step 1 to Step 10 of 14.3 To install a client delegate server using a web browser (p. 428). 3. Go to Step 7. Double-click on the client delegate server desktop icon HE AAAG-TQZZA

453 5620 SAM 5650 CPAM To upgrade a client delegate server Figure 48 Upgrade prompt 6 Click Yes to begin the upgrade. As shown in Figure 49, Updating... (p. 453), the next panel uses separate bars to indicate the current and overall task progress. Figure 49 Updating... When the upgrade is complete, the client login form opens. 3HE AAAG-TQZZA 453

454 To upgrade a client delegate server 5620 SAM 5650 CPAM 7 Log in to ensure that the GUI opens and is correctly displayed. END OF STEPS 454 3HE AAAG-TQZZA

455 5620 SAM 5650 CPAM To uninstall a client delegate server using a web browser Client delegate server uninstallation 14.8 To uninstall a client delegate server using a web browser Description The following steps describe how to remove the client delegate server software from a RHEL or Microsoft Windows station using a web browser Steps Note: The uninstallation method must match the installation method. You can use this procedure to uninstall only a client delegate server installed using a web browser. If a client delegate server is installed on Windows using the GUI-based 5620 SAM installer, you must perform To uninstall a Windows client delegate server using a GUI (p. 460) to uninstall the client delegate server. If a client delegate server is installed on RHEL using yum, you must perform 14.9 To uninstall a RHEL client delegate server using the yum utility (p. 458) to uninstall the client delegate server. Note: The main server to which the client delegate server connects must be running when you perform this procedure. Note: If you are not the original installer of the client software, you require the following user privileges on the client station: RHEL root Windows local administrator Log in to the client delegate server station. Close the local client GUI, if it is open. Use a browser on the station to open one of the following URLs: if SSL is not enabled on the main server if SSL is enabled on the main server where server is the main server IP address or hostname The following page is displayed. 3HE AAAG-TQZZA 455

456 To uninstall a client delegate server using a web browser 5620 SAM 5650 CPAM Figure SAM Client Delegate page 4 Click on the Uninstall 5620 SAM Client Delegate link. The form shown in Figure 51, Opening samclientdelegate_uninstall.jnlp (p. 456) is displayed. Figure 51 Opening samclientdelegate_uninstall.jnlp 5 Perform the following steps. 1. Select the Open with option. 2. Click Choose and use the form that opens to specify the javaws file of a supported Oracle JRE. 3. Click OK HE AAAG-TQZZA

457 5620 SAM 5650 CPAM To uninstall a client delegate server using a web browser 6 7 If a security message is displayed, click Run. The client uninstaller opens, as shown in Figure 52, Uninstall... (p. 456). Click Yes to begin the uninstallation. Figure 52 Uninstall... The following progress indicator panel is displayed: Figure 53 Uninstall... 3HE AAAG-TQZZA 457

458 To uninstall a RHEL client delegate server using the yum utility 5620 SAM 5650 CPAM 8 The uninstallation is complete when the panel in Figure 54, Uninstall... (p. 457) is displayed. Click OK to close the uninstaller. Figure 54 Uninstall... 9 Remove any files that remain in the client delegate server installation directory. END OF STEPS 14.9 To uninstall a RHEL client delegate server using the yum utility Description The following steps describe how to remove the client delegate server software from a RHEL station using the RHEL yum utility. Note: The uninstallation method must match the installation method. You can use this procedure to uninstall only a client delegate server installed using the RHEL yum utility. If a client delegate server installation is web-based, you must perform 14.8 To uninstall a client delegate server using a web browser (p. 455) to uninstall the client delegate server. Note: You require root user privileges on the client delegate server station. Note: A leading # symbol in a CLI command represents the CLI prompt; do not include the leading # symbol when you type a command HE AAAG-TQZZA

459 5620 SAM 5650 CPAM To uninstall a RHEL client delegate server using the yum utility Steps Close each remote client GUI session that the client delegate server hosts. Log in to the client delegate server station. Close the local client GUI, if it is open. Open a console window. Note: Ensure that the current working directory is not a directory below the client installation directory. 5 Perform one of the following. a. If the client delegate server is installed in the default directory of /opt/5620sam/client, perform the following steps. 1. Enter the following commands in sequence to remove the 5620 SAM packages: # yum remove samclientdelegate # yum remove samconfig # yum remove samjre After you enter a command, the yum utility resolves any dependencies and displays the following prompt: Installed size: nn G Is this ok [y/n]: 2. Enter y. The following is displayed: Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Uninstalling the 5620 SAM package... As each package removal completes, the following is displayed: Complete! 3. Return to Step 5 2 as required to remove the next package in the sequence. b. If the client delegate server is installed in a non-default directory, enter the following: 3HE AAAG-TQZZA 459

460 To uninstall a Windows client delegate server using a GUI 5620 SAM 5650 CPAM # rpm -e samclientdelegate Uninstalling the 5620 SAM Client Delegate... Uninstall logs were backed up to log_file Removing install_dir installation directory (including all contents) When the installation is complete, enter the following to reboot the client delegate server station: # init 6 The station reboots. Remove any files and directories that remain in the client delegate server installation directory. END OF STEPS To uninstall a Windows client delegate server using a GUI Description The following steps describe how to remove the client delegate server software from a Microsoft Windows station using the GUI-based 5620 SAM uninstallation utility Steps Note: The uninstallation method must match the installation method. You can use this procedure to uninstall only a Windows client delegate server installed using the GUI-based 5620 SAM installer. If a client delegate server installation is web-based, you must perform 14.8 To uninstall a client delegate server using a web browser (p. 455) to uninstall the client delegate server. Note: You require local administrator privileges on the client delegate server station Close each remote client GUI session that the client delegate server hosts. Log in to the client delegate server station. Close the local client GUI, if it is open HE AAAG-TQZZA

461 5620 SAM 5650 CPAM To uninstall a Windows client delegate server using a GUI 4 Perform the following steps. 1. Click on Start Control Panel. The Control Panel window opens. 2. Under the Programs category, click on Uninstall a Program. The Programs and Features window opens. 3. Right-click on 5620 SAM Client and choose Uninstall/Change. 4. If a security warning is displayed, click Continue. The splash screen shown in the following figure opens. 5 The client uninstaller opens, as shown in Figure 55, Uninstall 5620 SAM Client (p. 460). The left pane lists the uninstallation steps. The right pane displays the current step. Click Uninstall. 3HE AAAG-TQZZA 461

462 To uninstall a Windows client delegate server using a GUI 5620 SAM 5650 CPAM Figure 55 Uninstall 5620 SAM Client 6 As shown in Figure 56, Warning (p. 462), a warning is displayed. Ensure that the conditions are true, and then click Continue with the uninstall process. Figure 56 Warning The uninstaller removes the software, as shown in Figure 58, Uninstall Complete (p. 463) HE AAAG-TQZZA

463 5620 SAM 5650 CPAM To uninstall a Windows client delegate server using a GUI Figure 57 Uninstall 5620 SAM Client 7 When the uninstallation is complete, as shown in Figure 58, Uninstall Complete (p. 463), click Done to close the uninstaller. Figure 58 Uninstall Complete 3HE AAAG-TQZZA 463