Cisco Prime Network Installation Guide, 5.2

Database installation on a remote server.

yes/no

This guide assumes that the database will be installed locally on the gateway server.

If you want to install the embedded database on a remote server, enter yes. The next few prompts will ask you to enter the remote server details (IP address, username and password to connect to the remote server, and OS root user password (if not provided earlier).

Note If the IP address you enter is not the default one, the database installation software updates the hostname in the database listener’s files. Verify that /etc/hosts is updated with the correct IP address and hostname. If more than one hostname is attached to the selected IP address, the first hostname is used.

Selecting a single interface for the database services.

Note This prompt appears only if more than one interface is detected during the network-conf process.

NIC to use for database connection

Because Prime Network 5.2 supports dual NICs, the installation may detect that the server is configured with multiple NICs. Specify the NIC to use for the database connection.

OS root user password

Unix root password

Prime Network uses the root password to set machine-level settings and to execute scripts.

OS username

—

The username of the Unix database user. The default is oracle.

OS user home directory

Path to the Oracle user home directory

OS user home directory by default is /export/home/oracle.

The directory must have a minimum of 6 GB of disk space for oracle binaries, and should not reside under Prime Network user home directory.

Removing previous installation of Oracle.

yes

Default is yes. If you already have Oracle installed with the same user and home directory, enter yes to remove it before installing the new database.

If you enter no, the installation will quit.

Selecting Prime Network database profile.

The number corresponding to the estimated profile.

Select from 1-7 based on the actionable events per second.

For more information on database profiles, see Creating an External Oracle Database.

Database’s datafiles location

Path to the directory containing the datafiles.

Location of the database datafiles (/export/home/oracle/oradata/anadb by default).

Redo logs location

Path to the directory containing the redo files.

Location of the redo logs. They should not be on the same disk as the data files. Example: /export/home/oracle/redo.

Note Use ext3 partition mounted with the default mount options.

Prime Network to run automatic database backups?

yes

The default is yes.

If you entered no at this prompt, you can enable automatic backups later with the emdbctl --enable_backup command. See the Cisco Prime Network 5.2 Administrator Guide. for information on the emdbctl utility.

Destination for archive logs

Path to the directory containing the archive logs.

Location of the archive logs. They should not reside on the same disk as the data files.

Destination for backup files

Path to the directory containing the backup files.

Location of the backup files. They should not reside on the same disk as the data files.

SMTP server IP/hostname

Company e-mail server IP address or host name.

Port 25 must be available. You must have SMTP server access from the gateway in order to receive e-mail notifications.

If you enter an invalid server, you can change the SMTP server later using emdbctl -set_smtp_server as described in the Cisco Prime Network 5.2 Administrator Guide.

Note Prime Network validates the SMTP server only on installations where the gateway and embedded database reside on the same server.

Selecting a single interface for Prime Network backend services.

Note This prompt appears only if more than one interface is detected during the network-conf process.

The number corresponding with the IP address of the back-end interface to be used for gateway-to-unit communication.

Because Prime Network 5.2 supports dual NICs, the installation may detect that the server is configured with multiple NICs. Specify the NIC to use for back-end services (such as transport, http, and so on) for gateway-to-unit communication. Dual NICs let you isolate the northbound interface from the back-end interface.

Installing Prime Network as part of a Prime suite of products.

no

Default is no. If you enter yes, additional prompts on suite installation appears, as shown in Prime Suite Prompts.

Note If you use Prime Network in suite mode, you must additionally install the Prime Network Integration Layer (PN-IL). Integration of Prime Network should have been done before installing the operations report. See Installing the Prime Network Integration Layer. Refer to the Cisco Prime Central Quick Start Guide to see how to integrate and configure the PN-IL in suite mode. Once the Prime Network is integrated to Prime Central, the Prime Network and the PN-IL status should be up in the Prime Central portal.

E-mail ID for receiving alerts

username@company-name.com

E-mail address to receive notification when database errors occur. You can enter a single email address or a comma separated list of email addresses.

Disabling Low and Medium strength Ciphers

yes/no

Choose either one of the following option:

• no —No change happens in Prime Network security configurations.
• yes —Disables Low and Medium strength Ciphers.

If you disable Low and Medium strength Ciphers, you must ensure that all network connections are using High Strength Ciphers before disabling.

Note The standalone script updateciphers.pl and the install flows do not allow to set the cipher strength to low and medium. The updateciphers.pl script only allows to configure the setting to High (not visa-versa) after the restart of services.

Starting the Prime Network gateway at the end of the installation.

yes

Default is yes. If you enter no, you can start Prime Network later using the procedure in Starting the Prime Network Gateway.

Prime Central database server IP address

IP Address

After providing these inputs, Prime Network will be launched in suite mode. To integrate Prime Network with Prime Central, see Cisco Prime Central Quick Start Guide.

Prime Central database SID

primedb

Prime Central database username

username

Prime Central database password

password

Prime Central database port

port number

Password for all built-in users (root, bosenable, bosconfig, bosusermngr, web monitoring user)

The password that will be used to access the various Prime Network system components.

The three login levels defined to connect to the Prime Network shell.This password will also be used as the database schemas password.

You can change the password for each of these users at a later stage. See the Cisco Prime Network 5.2 Administrator Guide for changing the passwords.

The password must:

• Contain at a minimum 9 characters.
• Contain both upper and lower case letters.
• Start with a letter.
• Contain at least one number.
• Contain at least one of the allowed special characters: ~!#%^ (no other special characters to be used)
• Not contain the username or the username in reverse.
• Not contain cisco, cisco in reverse, or any variation.
• Not repeat the same character three or more times.

Prime Network to install the database?

no

After you enter no, the setup will configure the Prime Network default schema. You can manually create the database schemas, as described in Manually Creating Prime Network Database Schemas.

Oracle server IP address/host name

IP address/hostname

Oracle admin username

username

Default is system.

Oracle admin password

password

Password for the database administrator.

Allowing Prime Network to auto-configure the database

yes

If you enter yes, the pnuser database is configured automatically with the following default values:

• Port 1521
• SID: mcdb
• No encryption
• Prime Network-created users

The pnuser _ep (Event Archive) schema uses the same settings.

If you enter no, alternative database server is used to install EP schema. You need to provide the Port number, SID and whether you require an encrypted connection to the database server. If you select encrypted connection, enter the values as shown in Table 6-4 . If you have manually created the database schemas, as described in Manually Creating Prime Network Database Schemas, you need to provide these schemas details.

Selecting a single interface for the database services.

Note This prompt appears only if more than one interface is detected during the network-conf process.

NIC to use for database connection

Because Prime Network 5.2 supports dual NICs, the installation may detect that the server is configured with multiple NICs. Specify the NIC to use for the database connection.

Installing Prime Network as part of a Prime suite of products.

no

Default is no. If you enter yes, additional prompts on suite installation appear, as shown in Prime Suite Prompts.

Note If you use Prime Network in suite mode, you must install the Prime Network Integration Layer (PN-IL). See Installing the Prime Network Integration Layer. Refer to the Cisco Prime Central Quick Start Guide to see how to integrate and configure the PN-IL in suite mode.

Starting Prime Network at the end of the installation.

yes

Default is yes. If your enter no, you can start Prime Network later using the procedure in Starting the Prime Network Gateway.

Prime Central database server IP address

IP address

These prompts appears if you decided to install Prime Network as part of the suite.

Prime Central database SID

primedb

Prime Central database username

username

Prime Central database password

password

Prime Central database port

port number

Oracle’s listener port

port-number

Default is 1521

Oracle’s SID

SID

Prime Central Database SID

Encrypted connection for database

yes

Default is yes.

Type of encryption method

Enter option (1-3)

Number corresponding to the encryption method you would like to use.

Type of encryption algorithm

Enter option (1-9)

Number corresponding to the encryption algorithm you would like to use.

PRIME_NETWORK_HOME

Note At the command line, enter $PRIME_NETWORK_HOME for this variable. For compatibility with previous Cisco Active Network Abstraction releases, this variable was not changed.

/export/home/ pnuser

JAVA_HOME

PRIME_NETWORK_HOME /java

NCCM_HOME

PRIME_NETWORK_HOME /NCCMComponents

XMP_HOME

PRIME_NETWORK_HOME /XMP_Platform.

reg

Changes the directory to $PRIME_NETWORK_HOME /Main/registry

main

Changes the directory to $ PRIME_NETWORK_HOME /Main

logs

Changes the directory to $PRIME_NETWORK_HOME /Main/logs

Main/bosconfig

Prime Network configuration files (syntax of the commands, supported errors, and the connection configuration)

Main/bosconfig/bos_shell_scripts

User-created scripts

Main/data

Drools configuration files and user-defined scripts.

Main/logs

Log output files ( AVM-ID.out; for example, 0.out or 11.out)

Main/registry

Local copy of registry files

Main/registry/ConfigurationFiles

Golden source (master registry) configuration files in the Prime Network gateway

Main/registry/templates

Registry file templates used by the Prime Network gateway for global system changes

local/scripts

Scripts on the gateway and units

Main/scripts

Scripts on the gateway and units

Third_Party

Third-party files

Main/unix

UNIX maintenance scripts and utilities

Main/reportfw/rptdocument

Reports

Main/drivers

VNE driver files

prime_integrator

Integrating Prime Network into Prime Central

NCCMComponents

Configuration and Change Management (CCM)

XMP_Platform

Contains XMP platform components used by CCM

pentaho

Operations Reports

avm[1-999]

Main application

Main/registry/Avm[NUM].xml

8000+AVM number for secured XML RPC

2000+AVM number for local management

2000-3000, 8000-9000 (TCP)

Java, Perl, Tcsh

Inner protocol

sheer_secured daemon

Secured connectivity between gateway and unit

local/sheer_secured/sheer_config

1101 (TCP)

—

—

SSH

webserver daemon

Serves the client Web Start and the diagnostics tool with graphs

utils/apache/conf/ sheer.conf

1311 (TCP)

—

—

HTTP

Machine interface

BQL machine- to-machine interface

—

9002 (TCP)

—

Java

—

Secure machine interface

Secured (SSL) BQL machine-to- machine interface

—

9003 (TCP)

—

Java

—

Transport switch

Gateway/unit internal message bus.

—

9390 (TCP)

—

Java

—

Client Applications Transport

Client/gateway message bus.

This PTP connection is secured by SSL.

—

9771 (TCP)

—

Java

—

Problem Swap file entry error

Solution Increase the swap file size in two ways:

Enter the keyword “-override_swap” along with the installation command.

To enable it at boot time:

Edit /etc/fstab to include the following entry:

Problem Error in deploying fetch_expect or RRDs or Embedded database (on RHEL 5.8)

Solution Remove the “=” symbol from the following file:

Problem Host file entry error

Solution Check the host file for local host entry:

Problem SMTP TIME OUT Error (on both RHEL 5.8 & 6.5)

This occurs when there is SMTP time out error.

Solution

1. Get to the following file:

/etc/opt/quest/vas/vas.conf

2. Edit the following entry:

Problem COMPACT LSB error

Solution While installing any RPM, update the LSB core with the following command:

Problem It is time consuming to install multiple RPMs individually

Solution To install Multiple RPM’s simultaneously:

1. Create a txt file and copy all the RPM names.

2. Enter the following command:

where, “rpm.txt” is name of the text file that you created.

During installation or upgrade you may encounter the following errors:

Problem Unable to establish master SSH connection: master process exited unexpectedly at reader PrimeNetwork::DB::Oracle::_ssh

This occurs when master process exited unexpectedly at reader PrimeNetwork::DB::Oracle::_ssh

Solution Check whether the Openssh or Openssl got installed and updated.

Solution Failed to backup the database with the following error

ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted

ORA-06512: at "SYS.DBMS_ISCHED", line 198

ORA-06512: at "SYS.DBMS_SCHEDULER", line 594

ORA-06512: at line 1 (DBD ERROR: OCIStmtExecute). ABORTING. ***

Solution

Enable the backup and give proper permission to the folder for both backup and archive, which are under Oracle home folder.

Problem Error: Failed on creating inventory logical tables

This occurs when there is a SQL syntax error.

Problem Failed to copy ssh keys from gateway error (during unit adding)

Check the following:

• proxy settings and file permissions of /$PRIME_NETWORK_HOME/local/ana_secured and /$PRIME_NETWORK_HOME/
• RHEL version. If the RHEL version is 6.5, make sure the openssl rpm is updated (to 57 version).

• Make sure that firewall is configured properly or in stopped state.

Problem Prime Network failed to start with the following error:

This unit (10.104.63.97) is not connected to 10.104.63.96 gateway anymore.

Check if both Unit and GW got installed on the same directory path. For example, either in /export/home or /home.

Problem Unable to launch the CCM application

Check for the following:

• Web server should be up
• Tomcat should be up
• dmctl status

Problem Receiving the following error entries:

Unzipping p23054354_121010_Linux-x86-64.zip on the database server

Stopping the database and listener

/export/home/anaoracle/product/12.2.0/db_1/bin/dbshut: line 160: /export/home/oracle/product/12.1.0/db_1/shutdown.log: Permission denied

Installing p23054354_121010_Linux-x86-64.zip on the database server. This may take a while

Starting the database and listener

touch: cannot touch `/export/home/oracle/product/12.2.0/db_1/startup.log': Permission denied

chmod: changing permissions of `/export/home/oracle/product/12.2.0/db_1/startup.log': Operation not permitted

/export/home/anaoracle/product/12.2.0/db_1/bin/dbstart: line 346: /export/home/oracle/product/12.2.0/db_1/startup.log: Permission denied

This occurs when there is no proper permission to ivne-drivers.tar file & oracle home folder.

Solution Check the permissions of copied ivne-drivers.tar file and oracle home folder.

Problem Unit AVM failed / unreachable to start the Prime Network after Rollback

Solution Check if the hostname entry on /etc/hosts is appropriate.

Problem Receiving errors during XMP platform and Web server installation process.

Solution Make sure all the Required RPMs for Oracle Database 12c got installed. Ensure that two mandatory RPMS; libXext-1.1 (x86_64) and libXtst-1.0.99.2 (x86_64) are installed properly.

Problem The following ports are unreachable on the PN Gateway (ipadd): 6081, 9490, 1101”.while adding unit with gateway. (using either ipv4 or ipv6 address)

Solution

Make sure that:

• Ports such as 6081, 9490, 1101 are in listening state.
• iptables (for both ipv4 and ipv6) got turned off.
• Selinux got disabled or in permissive mode.

Problem Compliance engine status is down

Solution Check the ComplianceService.log under:

Solution Check the DB ip address entry in the following folder path:

Problem Compliance Engine not starting:

.

Before upgrading to 5.2, take the backup file “nccmDatabase.properties” that is located in:

Problem Could not open '/tmp/ana_db_properties.properties' for reading No such file or directory

Solution Check the oracle 12c files permissions.

Problem Unit servers shows Virtual IP address during Network configuration.

Figure 6-1 Unit Servers

Solution This occurs when either gateway or Unit server is not installed on the same directory. For example:/export/home/pnuser.

Make sure to install the Unit servers with the same directory path in which the Gateway is installed.

Problem Receiving errors ending with number 256.

Figure 6-2 Errors ending with 256

Solution This occurs when the oracle is not uninstalled properly.