ISON Installation Intro Guide

18/04/20231 © Nokia 2015 - iSON Manager Installations – Lundsten

Confidential

iSON Manager 15.2 Installation Guide

• Anukool Phuruangurt

• 10 Sep 2015


Confidential

Content

1. Pre-requirements

2. OIPE – OoD Installation Parameter Editor

3. ViiS – Virtual Installation Server

4. VDC – vmware Virtual Data Center

5. DCA – Deployment Controller Automation

6. Installation verification


Confidential

iSon Manager Installation Pre-requirements

• Functional Overview

• Architecture

• Hardware

• Installation ID

• Licenses (iSON & NetAct)

• Optimizer


Confidential

Functional overview of iSON Manager


Confidential

iSON Manager 2.5 Architecture – non HA


Confidential

iSON Manager 15.2 Small Configuration Exsample


Confidential

iSON Manager 15.2 UR1 Architecture – HA


Confidential

iSON Manager 15.2 Configuration options


Confidential

iSON Manager 15.2 Hardware requirementsDescription Small Medium (HA) Large (HA)

Blades

2x G8 2p6c/64GB

+1x G8 2p6c/96 for OR

6x G8 2p6c/96GB


6x G8 2p6c/96GB


NW size (WCDMA+LTE cells)

~10.000 ~50.000 ~100.000

Total vCPU

22/34 (min/max*):16(DB+JBoss+Portal) +3(ViiS+vCenter)+3(Map server)+12 (OR/SAfE) / option

68/80 (min/max*):54(DB+JBoss+Portal)+8 (LVS) +3(ViiS+vCenter)+3(Map server)+12(OR/SAfE) / option

68/80 (min/max*):54(DB+JBoss+Portal) +8 (LVS)+3(ViiS+vCenter)+3(Map server)+12(OR/SAfE) / option

Total vRAM49/107GB(min/max*)

334/382GB(min/max*)

336/384GB(min/max*)

Concurrent users

30 active users 60 active users 60 active users


Confidential

iSON Manager 15.2 Hardware requirements

Primary storage**

EMC VNX Small

opt.1: VNX Small - VNX5200 - 3x100GB SSD SSF + 9x600GB SAS SFF + 13x1TB NL_SAS SFF

opt.2: VNX Small+ - VNX5300 - 13x300GB SAS LFF + 7x2TB NL SAS LFF + 5x100GB SSD LFF

EMC VNX Medium

opt.1: VNX Medium - VNX5200 - 5x100GB SSD SSF+ 13x600GB SAS SFF + 19x1TB NL_SAS SFF

opt.2: VNX Medium - VNX5300 - 17x300GB SAS LFF+ 9x2TB NL SAS LFF+ 2x100GB SSD LFF

EMC VNX Large

opt.1: VNX Large - VNX5200 - 5x100 or 5x 200GB SSD SSF + 17x600GB SAS SFF + 27x1TB NL_SAS SFF

opt.2: VNX Large - VNX5300 - 25x300GB SAS LFF + 13x2TB NL SAS LFF + 5x100GB SSD LFF


Confidential

iSON Manager Installation ID

• Before starting to define installation parameters one needs to know the installation ID of the system that is about to be setup.

• Information regarding this can be found from the Installation pre-req documents, i.e.: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D528904770

”

Target IDs are generated by OBS-SW-Installations (RES/Tampere) – team on

request (Sw-Installations, Bso (NSN - Global)). All new clusters and

installations will get Target IDs (8 digits that is, 201xxxxx). Target ID is

required while ordering licenses and doing the installation.

”

https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D528904770


Confidential

iSON Manager – NetAct Optimizer Requirements

• Not all Optimizer builds have the scope service available – this needs to be checked:

• Supported Optimizer version is 3.1 CD3- # rpm -qa | grep -i opt

- C_OPTZ-5.25-111726

- S_OPTS-5.25-111726

- Or higher version of 5.25 – not 5.27.xyz

• Verify the scope service availability by pointing any browser to - https://<NetAct_LB_FQDN>/optimizer/services/scopes

• This should

- Ask for credentials

- List available scopes from Optimizer


Confidential

Content

1. Pre-requirements







Confidential

iSON Manager Deployment

iSON ViiS image

vmplayer

VirtualMachine

VirtualMachine

Virtual Data Center

Vmware tools ViiS VM

VirtualMachine

iSON Manager SW

product_copy.sh

OIPE

DCA

NOLS


Confidential

Ood installation – Installation overview

SW Repositories

Hypervisor

VMVM

VM

VMVM

NetAct vCenter

Deploy iSON

Deploy VI

Move ViiS to VI VM

DCA

5

61

2

3

5System ready6

Manual task

Mostly automatic task

Automatic task

4

VSE

1. Setting up ViiS2. Setting up VMware infra3. Moving ViiS to VMware infra4. Software copy5. Installing NetAct software6. Manual tasks


Confidential

iSON Manager – Installation Workflow I

• Filling in the installation parameter values using OIPE (OoD Installation Parameter Editor tool)

• Set up the Virtual Installation Server.

• Copy the installation parameter files to ViiS.

• Set up the Virtualized Infrastructure: - Create PXE-boot configurations for hosts

- Installing the Hypervisors on physical hosts

- Create the Virtual Data Center (VDC) and virtual machines (VMs)

- Transfer the Installation Server to the VDC


Confidential

iSON Manager – Installation Workflow 2

• Copy the iSON Manager software to ViiS.

• Install the operating system (RHEL 6.4 - 64) on VM nodes.

• Prepare iSON VMs for the iSON Manager software installation from the Installation Server: - Create the DCA configuration files using the parameters collected in step 3

- Delivering SSH keys and YUM repositories to all iSON VM nodes

- Merging XML files and creating the installation DCA stack for the iSON Manager installation

• Installing iSON Manager software to the iSON VMs : - Executing the DCA stack

- Installation verification

- Post-installation tasks


Confidential

OIPE – OoD Installation Parameter Editor - Setup

OIPE requires Java - JRE6, any version.


Confidential

OIPE – OoD Installation Parameter Editor - Setup

• Select the Linux or Windows version:


Confidential

OIPE – OoD Installation Parameter Editor – New configuration

• Check what content the customer will use / has ordered before creating a new OIPE configuration!

• Then select File New configuration

• Then define the virtual machine configuration - small/medium/large

• Check amount of physical hosts

• Select correct iSON content packs

• OK


Confidential

OIPE – OoD Installation Parameter Editor - VMs

• Define VM names, IPs

and disk sizes- Change hostnames!

• Verify vRAM and VCPU values


Confidential

OIPE – OoD Installation Parameter Editor – Dynamic Attributes

• Define all mandatory values

• And PRODUCT_NAME:

”iSON Manager”


Confidential

Content

1. Pre-requirements







Confidential

ViiS – Virtual Installation Server

• vmplayer• ESXi• DNS• PXE• SW


Confidential

ViiS – Virtual Installation Server - vmplayer

• Next play your VM from your vmplayer

• Note

Installation Server does not start if Virtualization is not enabled on the machine. To enable the Virtualization, refer to the BIOS document.


Confidential

ViiS – Virtual Installation Server - vmplayer

• Log in to the Installation Server as root user. The default password is nasroot.


Confidential

Content

1. Pre-requirements



4. VDC – VMware Virtual Data Center




Confidential

VDC – vmware Virtual Data Center setup

• VSE Configuration files are validated by executing:

# /opt/vse/bin/vse validate_vconf /var/${SYSTEMNAME}_vmware_vconf.yml

# /opt/vse/bin/vse validate_vconf /var/sprintlab264_vmware_vconf.yml

checking file existence /var/sprintlab264_vmware_vconf.yml

I, [2015-05-05T09:48:47.543412 #2314] INFO -- : Syntax of configuration file validated sucessfully!!

I, [2015-05-05T09:48:47.543738 #2314] INFO -- : Checking vMotion configuration...

I, [2015-05-05T09:48:47.543930 #2314] INFO -- : vMotion configuration check succeeded.

I, [2015-05-05T09:48:47.543977 #2314] INFO -- : No DRS rules defined at vconf to validate!

I, [2015-05-05T09:48:47.544015 #2314] INFO -- : No DRS Groups defined at any vm to validate

I, [2015-05-05T09:48:47.544051 #2314] INFO -- : No DRS Groups defined at any host to validate

I, [2015-05-05T09:48:47.544085 #2314] INFO -- : No storage DRS Groups to validate

I, [2015-05-05T09:48:47.544186 #2314] INFO -- : Vconf sanity check OK!

---cut---

I, [2015-05-05T09:48:47.603346 #2314] INFO -- : Vconf configuration file /var/sprintlab264_vmware_vconf.yml is valid

Vconf configuration file /var/sprintlab264_vmware_vconf.yml is valid

vse_installer operation validate_vconf SUCCESSFUL


Confidential


• To enable passwordless access to hypervisors, execute:

# /opt/misserver/scripts/ssh_setup_authorization.sh -c /var/${SYSTEMNAME}_cluster_info.txt --rpwd <esx_root_password> -e

• To ensure that both hardware and system clock in ESXi hosts will match to time in Installation Server, execute:

# /opt/misserver/scripts/sync_esxi_time.sh -ci_file /var/${SYSTEMNAME}_cluster_info.txt

Note: On ESXI the default time zone is UTC


Confidential


• To run VSE Installer to deploy Virtual Data Center (VDC), and to create virtual infrastructure, execute:

#/opt/misserver/scripts/install_vcenter_and_create_infra.sh -system_name ${SYSTEMNAME}

• Allocate another 30-45 minutes for this script to finish


Confidential

Content

1. Pre-requirements







Confidential

Installation verification

• Database• Frontend• Backend


Confidential

Installation verification – Database node(s)

• To verify the installation of PostgreSQL database:

1. Log in to the Database node (DBNode vm3 in a three node setup, vm3,vm4 in HA setup) as root user, by executing: ssh <dbnode IP Address>

2. # ll /opt/oodee/pgsql

3. # ll /opt/ood/db/data

4. To check if postgresql service is running, execute:

# service postgresql status

pg_ctl: server is running (PID: 1757)

/opt/oodee/pgsql/bin/postgres "-D" "/opt/ood/db/data"


Confidential


5. To verify if postgresql is running on port 5432, execute:

# lsof -P | grep -i list | grep 5432

postmaste 2250 postgres 3u IPv4 20246 0t0 TCP *:5432 (LISTEN)

6. Log in to postgresql database and enter:

a. # su – postgres

b. $ cd /opt/oodee/pgsql/bin

c. $ sh psql -U postgres

d. Enter the password (default password= postgres)

e. Type \c ood

The following message appears: “You are now connected to database "ood" as user "postgres".”

f. Exit: \q


Confidential


• In case of HA, check if pgpool is running by executing command:

# /etc/init.d/pgpool status

• Expected Outcome:

pgpool is running


Confidential

Installation verification – Frontend node(s)

• To verify installation of Tomcat service and Liferay portal:

1. Log in to Portal node (PORTALNODE, vm4 on a three node environment, in case of HA vm5,vm6) as root user, by executing: ssh <portalnode ip address>

2. # ll /opt/oodee/apache-tomcat/

3. To check if tomcat service is running, execute:

# service tomcat status

Expected outcome

Tomcat is running

PID is 2281


Confidential


4. To verify that tomcat is started on port 8080, execute:

# lsof -P | grep -i list | grep :8080

java 15293 tomcat 47u IPv6 966664 0t0 TCP *:8080 (LISTEN)

5. In the address field of your internet browser, enter the following URL: http://<portalnodeIP>:8080 Liferay login page appears.


Confidential


6. In case of HA, in the address field of your internet browser, enter the following URL: http://<LB_VIP>:8080 Liferay login page appears.

7. Log in with username and password as test/test or admin/admin respectively.


Confidential

Installation verification – Backend node(s)

To verify the installation of JBoss Enterprise Application Server:

1. Log in to the Backend node (BACKENDNODE, vm5 on a three node environment . Incase of HA vm7,vm8) as root user, by executing:

# ssh <backendnode ip address>

2. # ll /opt/oodee/jboss-eap/

3. To check if Jboss is running, execute:

# service jboss-as-domain status

Expected outcome

jboss-as is running (pid 26599)


Confidential


4. To verify that Jboss Application Server is listening on port 9080, execute:


java 26795 jboss-as 54u IPv4 415336 0t0 TCP *:9080 (LISTEN)

5. To verify that Jboss Admin application is listening on port 9943, execute:


java 26612 jboss-as 86u IPv4 414790 0t0 TCP *:9943 (LISTEN)


Confidential


6. In the address field of your internet browser, enter the following URL: https://<JBOSS_NODE_IPADDRESS>:9943

The JBoss Admin Application appears.

7. Incase of HA, in the address field of internet browser, enter the following url:

https://<JBOSS_PRIMARY_NODE_IP>:9943

The JBoss Admin Application appears.

8. Log in with username and password as jbossadmin /admin_123 respectively.


Confidential

Installation – Encrypting the installation configuration files

• The script prompts for the following:

- The password for encrypting zip file twice, this password must be stored for future usage.

- The ood user password of the nodes, where the zip is transferred to.

- Delete these files? (y/n):

• From security point of view answer yes – to make upcoming upgrades easier, answer no.

- The encryption script creates an encrypted ZIP archive from the cluster configuration files. The archive is stored on the installation server, and on all the cluster nodes.


Confidential

Installation – Encrypting the installation configuration files

• The encrypted archive is stored on the installation server, in the following directory: - /var/builds/hosts/<systemname>/configuration_files_<sy stemname>_<date>_<time>.zip

• The encrypted archive is stored on all the cluster nodes, in the following directory: - /opt/ood/install/conf/configuration_files_<systemname>_<date>_<time>.zip

• If the installation server contents are lost, the archive can be decrypted with the same password, and the configuration files can be restored back to the installation server.


Confidential

ISON Installation Intro Guide

Documents

Transcript of ISON Installation Intro Guide