Guest

Cisco Prime Central

Cisco Prime Central Quick Start Guide, 1.2

  • Viewing Options

  • PDF (729.7 KB)
  • Feedback

Table of Contents

Cisco Prime Central 1.2 Quick Start Guide

Preface

Related Documentation

Obtaining Documentation and Submitting a Service Request

Installation Requirements

Prime Central Server Requirements

Additional Requirements

Installed Red Hat RPM Packages

Prime Central Protocols and Ports

Port Exposure Categories

Sample Remediation Policy Script

Embedded Database Requirements

Database Memory

Ports and Files

Dual-Server Installation

Security

Prime Central Client Browser Requirements

Component Version Requirements

Extracting the PrimeCentral.img.iso Image

Installing Prime Central

Installing Prime Central in a Single-Server Setup

Preparing the Server for Installation

Installing Prime Central on the Server

Installing Prime Central in a Dual-Server Setup

Preparing Both Servers for Installation

Installing the Prime Central Portal

Installing the Prime Central Integration Layer

Pathname, Group Name, Username, and Password Constraints

Verifying the Prime Central Installation

Checking the Prime Central Version

Installing Prime Central Silently

Sample install.properties Files

Verifying the Silent Installation

Installing Prime Central Fault Management

Preparing the Server for Installation

Installing Prime Central Fault Management on the Server

Installing Prime Central Fault Management Silently

Sample PrimeFM_install.properties File

Manually Registering Fault Management to Retrieve Alarm Data

Installing the Gateways Used with Prime Central

Troubleshooting the Installation

Prime Central Log Files

Troubleshooting the Prime Central Installation

Configuring Applications as Suite Components

Integration Process

Contents of the DMIntegrator.prop File

DMIntegrator.sh Script Usage

Integrating Cisco InTracer with Prime Central

Integrating Prime Network with Prime Central

Integrating the Prime Network Integration Layer with Prime Central

Integrating Prime Network in a High Availability Configuration with Prime Central

Integrating the Prime Network Integration Layer in a High Availability Configuration with Prime Central

Integrating Prime Optical and the Prime Optical Integration Layer with PrimeCentral

Integrating Prime Performance Manager with Prime Central

Integrating Prime Provisioning with Prime Central

Upgrading Prime Central

Before You Begin

Upgrading to Prime Central 1.2

Upgrading Prime Central Silently

Verifying the Upgrade

Upgrading to Prime Central Fault Management 1.2

Upgrading Prime Central Fault Management Silently

Uninstalling Prime Central

Uninstalling Prime Central in an Embedded Database Configuration

Uninstalling Prime Central in an External Database Configuration

Uninstalling Prime Central Silently

Uninstalling Prime Central Fault Management

Uninstalling Prime Central Fault Management Silently

Unregistering an Application from Prime Central

Unregistering Cisco InTracer

Unregistering Prime Network

Unregistering the Prime Network Integration Layer

Unregistering Prime Optical

Unregistering the Prime Optical Integration Layer

Unregistering Prime Performance Manager

Unregistering Prime Provisioning

Next Steps

Starting and Stopping the Prime Central Components

Backing Up and Restoring the Embedded Database

Backing Up and Restoring the Fault Management Database

Backing Up the Fault Management Database Manually

Restoring the Fault Management Database Manually

Quick Start Guide

Preface

This guide explains how to install Cisco Prime Central 1.2.

The primary audience for this guide is network operations personnel and system administrators. This guide assumes that you are familiar with the following products and topics:

  • Basic internetworking terminology and concepts
  • Network topology and protocols
  • Microsoft Windows 7 and Windows XP
  • Red Hat Enterprise Linux administration
  • Oracle database administration
  • Telecommunication Management Network (TMN) architecture model

Related Documentation

See the Cisco Prime Central 1.2 Documentation Overview for a list of Prime Central guides.

See also the documentation for the following suite components:


Note We sometimes update the documentation after original publication. Therefore, you should review the documentation on Cisco.com for any updates.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html .

Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

Installation Requirements

This section explains what is required to install Prime Central 1.2.

Prime Central Server Requirements

Table 1 lists the Prime Central server system requirements.

 

Table 1 Database, OS, and Hardware Requirements

Minimum Requirement
Notes
Database

One of the following:

  • External Oracle 11gR2 database
  • Embedded Oracle 11gR2 database

Memory
  • 16 GB of RAM
  • 10 GB of swap space

Disk Space

Prime Central:

  • 20 GB of free space in the Prime Central installation folder
  • 6 GB of free space in the /tmp directory

External database: 22 GB for the data files

A data file is a physical file on disk that contains data structures such as tables and indexes. The optimal location is an external disk array (preferably RAID 10). The data files are created under the directory that you specify during installation.

Embedded database:

  • 1 GB of space in the /tmp directory
  • 5 GB of space for software files in the home directory of the database’s OS user (by default, /export/home/oracle)
  • 22 GB for the data files
  • 6 GB for the redo logs
  • 110 GB for the archive logs
  • 1.5 times the size of the database for the backup files

Redo logs are files that contain records of changes made to data. Redo logs should not reside on the same disk as the data files.

An archive log is a member of a redo log that has been archived by the Oracle database. Archive logs should not reside on the same disk as the data files. Archive logs can be applied to a database backup for media recovery.

A backup file stores a copy of the database data, which can be used to reconstruct data. Backup files should not reside on the same disk as the data files.

Data files, redo logs, archive logs, and backup files are created under the directories that you specify during installation.

Your system administrator must:

  • Back up the archive logs to tape daily.
  • Back up the database backups to external storage, such as to tape.

Prime Central Fault Management:

  • 50 GB of free space in the Prime Central installation folder
  • 15 GB of free space in the /tmp directory

Upgrade from Prime Central 1.1, 1.1.0.1, or 1.1.0.2 to 1.2:

The server must have at least ( size of the current installation directory + 7 GB) of free space in the folder where Prime Central 1.1 is installed.

Example: If Prime Central 1.1 is installed in the /opt/primecentral folder and that folder is 10 GB, you must have at least 17 GB of free space in the /opt folder before upgrading.

Upgrade from Prime Central Fault Management 1.1 to 1.2:

The server must have at least ( size of the current installation directory + 5 GB) of free space in the folder where Prime Central Fault Management 1.1 is installed.

Example: If Prime Central Fault Management 1.1 is installed in the /opt/primecentral/faultmgmt folder and that folder is 15 GB, you must have at least 20 GB of free space in the /opt/primecentral folder before upgrading.

64-Bit Operating System Platform

Red Hat Enterprise Linux 5.8 with x86_64 bit

  • If you are upgrading from Prime Central 1.x to 1.2, you must first upgrade the server with Red Hat Enterprise Linux 5.5 to 5.8.
  • Prime Central Fault Management requires the kernel-headers OS library. When installing RHEL, choose the Software Development option to ensure that the kernel-headers library is installed.
Hardware

One of the following:

  • Cisco Unified Computing System (UCS) B-series blade or C-series rackmountable server, bare metal or with VMware ESXi 4.1 or 5.0
  • Equivalent third-party vendor hardware platform

Use the following minimum hardware resources for the individual Prime Central and Fault Management servers:

  • 16 GB of RAM
  • 2 CPUs
  • 100 GB hard disk space

Before installing Red Hat Enterprise Linux 5.8, ESXi 4.1, or ESXi 5.0 for Prime Central, verify your hardware compatibility. See the Cisco UCS hardware compatibility list at http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html .

Red Hat RPM Packages

For Prime Central Fault Management, the installer automatically installs the Red Hat RPM Package Manager (RPM) packages listed in Table 2 .

If any of the RPM packages are missing, the Fault Management installer automatically installs them. No user intervention is required.

For Prime Central, the following packages must be present in the system path:

  • perl 5.8.6 or later
  • top
  • unzip

Red Hat Services and Components

The following Red Hat services and components (usually present as part of the Red Hat installation) are required:

  • /usr/bin/scp—Secure copy tool.
  • /usr/sbin/sshd—SSH daemon.
  • /usr/bin/ssh—SSH.
  • /usr/bin/ssh-keygen—Tool to generate, manage, and convert authentication keys.

Additional Requirements

  • All PCs must have access to the Prime Central server hostname.
  • Clocks must be synchronized on Prime Central and all attached Prime application servers.
  • When you install Prime Central, Prime Central Fault Management, or any suite components, Domain Name System (DNS) must be enabled on the hosts. Otherwise, Prime Central components cannot communicate, and clients cannot launch Prime Central.

If the hosts do not have DNS access, or if their hostnames are not registered in the DNS, you must add those hostnames (with the correct IP addresses) to your local hosts file (/etc/hosts on Linux; ${Windows}\System32\drivers\etc\hosts on Windows).

  • If DNS is not available, the Prime Central server and the Prime Central integration layer must include in their /etc/hosts file the following entries for Prime Network, Prime Optical, Prime Performance Manager, and Prime Provisioning:

application-IP-address fully-qualified-application-hostname application-hostname

For example, if Prime Optical is installed on the “my-server” workstation with IP address 209.165.200.225, the following entry must exist in the /etc/hosts file on the Prime Central portal and the Prime Central integration layer:

209.165.200.225 my-server.cisco.com my-server

Installed Red Hat RPM Packages

Table 2 lists the Red Hat RPM packages installed by the Prime Central installer.

 

Table 2 Installed Red Hat RPM Packages

compat-db.i386

libgcc.i386

compat-db.x86_64

libgcc.x86_64

compat-glibc.i386

libXft.i386

compat-glibc.x86_64

libXft.x86_64

compat-glibc-headers.x86_64

libXmu.i386

compat-libstdc++-296.i386

libXmu.x86_64

compat-libstdc++-33.i386

libXp.i386

compat-libstdc++-33.x86_64

libXp.x86_64

elfutils.x86_64

libXpm.i386

elfutils-libs.x86_64

libXpm.x86_64

gtk2.i386

libXtst.i386

gtk2.x86_64

libXtst.x86_64

gtk2-engines.i386

openmotif22.i386

gtk2-engines.x86_64

openmotif22.x86_64

kernel-headers.x86_64

pam.i386

ksh.x86_64

pam.x86_64

Prime Central Protocols and Ports

Table 3 lists the protocols and ports that Prime Central uses.

 

Table 3 Prime Central Protocols and Ports

Port No.
Exposure
Protocol
Used by...
The system administrator should...
Prime Central Portal

1107

Public

SSH

Internal services for SSH communication

Apply a rate-limiting policy.

1108

Public

TCP

Embedded Oracle database

Apply a rate-limiting policy.

1199

Private

TCP

RMI service

Only allow access to this port from localhost.

1521

Public

TCP

Oracle database server listener

Apply a rate-limiting policy.

8005

Private

TCP

Tomcat shutdown

Only allow access to this port (or its equivalent) from the Prime Central portal, unless remote shutdown is required.

8009

Private

TCP

Apache JServ Protocol (AJP)

Disable this port if it is not in use.

8090

Private

TCP

Discovery service

Only allow access to this port from localhost.

8443

Public

TCP

Default HTTPS port; subject to change during installation

Apply a rate-limiting policy and make this port available to all users who need to access the Prime Central portal.

Prime Central Integration Layer

1099– 1103

Private

TCP

Karaf JMX RMI registry (Prime Central integration layer management)

Allow a dynamic range from 1099 to the number of integration layer registrations; for example, 1103. Set aside a range of 10 ports.

8101– 8105

Private (localhost)

TCP

Karaf SSH shell

Allow a dynamic range from 8101 to the number of integration layer registrations; for example 8105. Set aside a range of 10 ports.

9020

Private/Public

TCP

Alarm management northbound interface (NBI)

Only allow access to this port from localhost, unless alarm management NBI access is required. If so, enable access from the alarm management client machines and apply a rate-limiting policy.

9110

Private/Public

TCP

Multi-Technology Operations System Interface (MTOSI) WS-SOAP NBI

Only allow access to this port from localhost, unless MTOSI NBI access is required. If so, enable access from the MTOSI client machines and apply a rate-limiting policy.

9220

Private/Public

TCP

3GPP NBI

Only allow access to this port from localhost, unless 3GPP NBI access is required. If so, enable access from the 3GPP client machines and apply a rate-limiting policy.

32768– 61000

Private/Public

TCP

Ephemeral ports

Only allow access to this port from localhost, unless Prime Central uses a dual-server (distributed) installation. If so, enable access from the Prime Central portal and apply a rate-limiting policy.

44444 – 44448

Private

TCP

Karaf JMX RMI server (Prime Central integration layer management)

Allow a dynamic range from 44444 to the number of integration layer registrations; for example 44448. Set aside a range of 10 ports.

61615

Private/Public

TCP

Java Message Service (JMS) Secure Sockets Layer (SSL) transport

Only allow access to this port from localhost, unless Prime Central uses a dual-server (distributed) installation with JMS SSL transport. If so, enable access from the Prime Central portal and apply a rate-limiting policy.

61616

Private/Public

TCP

JMS NIO transport

Only allow access to this port from localhost, unless Prime Central uses a dual-server (distributed) installation with JMS NIO transport. If so, enable access from the Prime Central portal and apply a rate-limiting policy.

Fault Management Component

1162

Public

TCP/UDP

Fault Management

Allow applications to use this port to send SNMP traps to the Prime Central Fault Management component.

2000

Private

TCP

Fault Management

Only allow access to this port from localhost.

4100

Private

TCP

Fault Management

Only allow access to this port from localhost.

4200

Private

TCP

Fault Management

Only allow access to this port from localhost.

4300

Private

TCP

Fault Management

Only allow access to this port from localhost.

4400

Private

TCP

Fault Management

Only allow access to this port from localhost.

5435

Private

TCP

Fault Management

Only allow access to this port from localhost.

9043

Private

TCP

Fault Management

Only allow access to this port from localhost.

9060

Private

TCP

Fault Management

Only allow access to this port from localhost.

9080

Private

TCP

Fault Management

Only allow access to this port from localhost.

16310

Private

TCP

Fault Management

Only allow access to this port from localhost.

16311

Public

TCP

Fault Management

Allow Prime Central to use this port to display the Alarm Browser and Alarm Report portlets.

16312

Private

TCP

Fault Management

Only allow access to this port from localhost.

16313

Public

TCP

Fault Management

Allow the Prime Central integration layer to use this port to send user management and suite monitoring requests to the Prime Central Fault Management component.

16314

Private

TCP

Fault Management

Only allow access to this port from localhost.

16315

Private

TCP

Fault Management

Only allow access to this port from localhost.

16316

Private

TCP

Fault Management

Only allow access to this port from localhost.

16318

Private

TCP

Fault Management

Only allow access to this port from localhost.

16320

Private

TCP

Fault Management

Only allow access to this port from localhost.

16321

Private

TCP

Fault Management

Only allow access to this port from localhost.

16322

Private

TCP

Fault Management

Only allow access to this port from localhost.

16323

Private

TCP

Fault Management

Only allow access to this port from localhost.

16324

Private

TCP

Fault Management

Only allow access to this port from localhost.

Port Exposure Categories

The ports listed in Table 3 belong to the following exposure categories:

  • Private—These ports should not be accessible from outside workstations. Administrators should restrict access to localhost (127.0.0.1). Administrators can use firewall software such as Linux iptables to implement access restrictions.
  • Public—These ports might need to be accessible from outside workstations. To protect against external security threats, administrators should restrict access to these ports to only those workstations that need explicit access. As additional precaution against denial of service (DoS) attacks, administrators should apply rate-limiting policies. Administrators can use firewall software such as Linux iptables to implement access restrictions and rate-limiting policies. Whenever possible, if the set of source addresses is known, restrict all other access.

In some cases, the packet source is not known ahead of time; for example, the HTTPS port that clients use to communicate with the Prime Central portal.

In some cases, the packet source is known ahead of time; for example, a distributed Prime Central installation, where the Prime Central portal must communicate with the Prime Central integration layer.

  • Ephemeral—These ports are similar to public ports, except that their port numbers are not fixed. Depending on the Prime Central deployment scenario, ephemeral ports might require public exposure. If so, administrators should restrict access to these ports to only those workstations that need explicit access. As additional precaution against denial of service (DoS) attacks, administrators should apply rate-limiting policies. Administrators can use firewall software such as Linux iptables to implement access restrictions and rate-limiting policies.

In some cases, the packet source is not known ahead of time; for example, the HTTPS port that clients use to communicate with the Prime Central portal.

In some cases, the packet source is known ahead of time; for example, a distributed Prime Central installation, where the Prime Central portal must communicate with the Prime Central integration layer.

  • Restricted—It is recommended that administrators restrict access to all other ports. Administrators can use firewall software such as Linux iptables to implement access restrictions.

Sample Remediation Policy Script

The following sample script shows how a system administrator can implement a remediation policy by using the built-in Linux iptables firewall feature.

#!/bin/bash
 
FWCONF=/etc/init.d/iptables
FW=/sbin/iptables
 
#Start firewall
$FWCONF save
$FWCONF start
 
#Remove any previous rules:
$FW -F
$FW -X
$FW -P INPUT ACCEPT
$FW -P FORWARD ACCEPT
$FW -P OUTPUT ACCEPT
 
#Drop invalid packets
$FW -A INPUT -m state --state INVALID -j LOG --log-prefix "DROP INVALID " --log-ip-options --log-tcp-options
$FW -A INPUT -m state --state INVALID -j DROP
 
#Permit rules
 
#Allow local packets (category 1 packets)
$FW -A INPUT -i lo -j ACCEPT
 
#Allow icmp/esp/ah packets
$FW -A INPUT -p icmp --icmp-type any -j ACCEPT
$FW -A INPUT -p esp -j ACCEPT
$FW -A INPUT -p ah -j ACCEPT
 
#Allow any tcp traffic to port <allowed-port> with rate-limiting to <rate> packets/second (category 2a packets)
$FW -A INPUT -s 0/0 -d 0/0 -j ACCEPT --protocol tcp --dport <allowed-port> -m hashlimit --hashlimit <rate>/second
 
#Allow tcp traffic from source address <source-IP> to a port <allowed-port> with rate-limiting to <rate> packets/second (category 2b packets)
$FW -A INPUT -s <source-IP>/32 -d 0/0 -j ACCEPT --protocol tcp --dport <allowed-port> -m hashlimit --hashlimit <rate>/second
 
#Allow any tcp traffic to ephemeral ports with rate-limiting to <rate> packets/second (category 3a packets)
$FW -A INPUT -p tcp --dport 32768:6100 -m hashlimit --hashlimit <rate>/second
 
#Allow tcp traffic from source address <source-IP> to ephemeral ports with rate-limiting to <rate> packets/second (category 3b packets)
$FW -A INPUT -s <source-IP>/32 -p tcp --dport 32768:6100 -m hashlimit --hashlimit <rate>/second
 
#Allow established connections
$FW -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
$FW -A INPUT -p tcp --dport ssh -j ACCEPT
 
#Drop everything else (category 4 packets)
$FW -A INPUT -j DROP
 
#Save firewall rules.
$FWCONF save

Embedded Database Requirements

This section lists the requirements to install an embedded database for use with Prime Central. These requirements are in addition to those in Prime Central Server Requirements.

You can install the embedded database on Red Hat Enterprise Linux 5.8.

During the installation, the installer automatically installs the following RPM software packages:

  • binutils.x86_64
  • compat-libstdc++-33.i386
  • compat-libstdc++-33.x86_64
  • elfutils-libelf-devel.i386
  • elfutils-libelf-devel.x86_64
  • elfutils-libelf.i386
  • elfutils-libelf.x86_64
  • gcc-c++.x86_64
  • gcc.x86_64
  • glibc-common.x86_64
  • glibc-devel.i386
  • glibc-devel.x86_64
  • glibc-headers.x86_64
  • glibc.i686
  • glibc.x86_64
  • ksh.x86_64
  • libaio-devel.i386
  • libaio-devel.x86_64
  • libaio.i386
  • libaio.x86_64
  • libgcc.i386
  • libgcc.x86_64
  • libstdc++-devel.i386
  • libstdc++-devel.x86_64
  • libstdc++.i386
  • libstdc++.x86_64
  • make.x86_64
  • numactl-devel.i386
  • numactl-devel.x86_64
  • sysstat.x86_64

The following components (usually installed as part of Red Hat) must be present in the system path:

  • /bin/sh
  • /bin/tcsh
  • gunzip
  • perl 5.8.6 or later
  • tar

Database Memory

Installation Phase

For the installation phase, the database memory requirements are:

  • Swap space: 150 MB
  • RAM: At least 4 GB

Runtime Phase

For the runtime phase, the database swap space requirement is two times the size of RAM, up to 32 GB.

Ports and Files

The following ports and files are required:

  • Port 1108 must be available for SSH communication between the Prime Central owner and the database owner. The port must also be open on the embedded database server, if it is installed separately.
  • The /etc/hosts file must include the workstation’s local hostname and IP address.

Example of a correct entry in the /etc/hosts file:

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
IP-address myserver.domain.com myserver
 

Example of an incorrect entry in the /etc/hosts file (without the server IP address information):

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
 
  • The hostname --fqdn command must return the hostname with the fully qualified domain name. For example:
sh-nv210-266.cisco.com
 
  • The /etc/nsswitch.conf file must not have NIS or NIS+ for password, group, shadow, or services. For example:
passwd: files
shadow: files
group: files
services: files

Dual-Server Installation

If you are installing the embedded database and Prime Central on separate servers, note the following additional prerequisites for the remote server:

  • Perl 5.8.6 or later must be installed on the root user.
  • The following ports must be available:

22 (the default SSH port)

1108 (for SSH communication between the Prime Central owner and the database owner)

1521

The installation script copies the Oracle installation files to the remote server under the home directory of the user connecting to the workstation via SSH. The home directory must have at least 4 GB of space available for the installation files. This is especially important if the home directory is root (/), because overconsumption might cause the server to crash.

Security

Prime Central connects to the database using an Oracle encryption feature. By default, connections between Prime Central and the embedded database are encrypted.

Prime Central Client Browser Requirements

Table 4 lists the client browsers and the Citrix XenApp deployment that Prime Central 1.2 supports. You must enable cookies and caching in your browser. Mozilla Firefox is the recommended browser.


Note Prime Central does not support the Internet Explorer Compatibility View and might not display or function correctly if it is enabled. If you are using Internet Explorer 8 or 9, be sure that Compatibility View is disabled.

 

Table 4 Supported Client Browsers

Certified Citrix Setup
Operating System
Mozilla Firefox Version
Microsoft Internet Explorer Version

Citrix Presentation Server 4.5 XenApp 5.0, installed on a Windows 2003 (SP2) server

Windows XP (32 and 64 bit)

Firefox 17

Internet Explorer 8

Firefox 17 Extended Support Release (ESR)

Firefox 20

Windows 7 (32 and 64 bit)

Firefox 17

Internet Explorer 8

Firefox 17 ESR

Firefox 20

Internet Explorer 9

Component Version Requirements

You can install a suite component in standalone mode or with Prime Central. If you want to install it with Prime Central, your suite component must be the version listed in the Cisco Prime Central 1.2 Release Notes .

Extracting the PrimeCentral.img.iso Image

If you ordered Prime Central electronically, this section explains how to extract the Prime Central .iso image. (If you did not order Prime Central electronically, skip this section.)


Note This procedure references the ImDisk utility, but you can choose any utility that opens .iso files.


Step 1 Download and install the ImDisk utility for Windows.

Step 2 Do one of the following, depending on where you are installing Prime Central:

    • If you are installing on the same machine where you downloaded the Prime Central image, skip to Step 3.
    • If you want to move the Prime Central image to another machine for installation, obtain a USB drive of at least 32 GB and copy the PrimeCentral.img.iso image file to it. Then, insert that USB drive into the USB port on your Windows server.

Step 3 Go to the Control Panel and click ImDisk Virtual Disk Driver .

Step 4 On the ImDisk Virtual Disk Driver GUI, click Mount new .

Step 5 In the Mount new virtual disk dialog box, do the following:

a. Browse to the PrimeCentral.img.iso file and select it.

b. Select the desired drive.

c. In the Device type area, choose Harddisk volume .

d. In the Image file access area, choose Virtual disk drive accesses image file directly .

e. Click OK .

Upon successful completion, the mounted virtual drive appears in the IMdisk window.

Step 6 Open the Computer folder and confirm that the drive is available:

 

Step 7 Continue to the relevant installation section:


 

Installing Prime Central

You can install the following Prime Central 1.2 components on the same or separate servers:

  • Database—Can be installed as an external or an embedded Oracle 11g database.
  • Prime Central portal—Provides a single sign-on and a multitenant common administrative interface for all applications within the suite.
  • Prime Central integration layer (IL)— Performs back-end mediation and enables information exchange between the various components.
  • Fault Management—Locates, diagnoses, and reports network problems.

Installing Prime Central in a Single-Server Setup

Installing the database, Prime Central portal, and Prime Central integration layer on the same server is a two-part process:

1. Prepare the server for installation.

2. Install Prime Central.


Note During the installation, the variables that you define must adhere to the constraints described in Pathname, Group Name, Username, and Password Constraints.

Preparing the Server for Installation

Before you install Prime Central, you must first connect to the server and, if using X server, verify the display settings.


Step 1 Use one of the following to connect to the server where you want to install Prime Central:

Step 2 As the root user, launch a terminal on the server where you want to install Prime Central. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended, but you can also use the Bash shell.

    • To start the C shell, enter:

/bin/csh

    • To start the Bash shell, enter:

/bin/bash

 

If you are using X server, continue to Step 3.

If you are using VNC, skip to Step 5.

Step 3 Set the DISPLAY variable:

setenv DISPLAY hostname-or-IP-address:0.0
 

Step 4 Verify that the display is set correctly:

echo $DISPLAY
 

In the command output, you should see:

hostname-or-IP-address:0.0
 

Step 5 Set the ulimit value.

If using a C shell, enter:

limit descriptors 1048576
 

In the command output, you should see:

# limit descriptors
descriptors 1048576
 

If using a Bash shell, enter:

ulimit -n 1048576
 

In the command output, you should see:

# ulimit –n
1048576
 

Step 6 (For an external database only; not applicable to an embedded database) If you are using a local or remote external database, create the following directory under ORACLE_HOME for the Prime Service Inventory (PSI) integration, and make the owner oracle:

ORACLE_HOME/oradata/PSI
 


 

Installing Prime Central on the Server


Step 1 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the Base Application folder.

Step 2 Change file permissions and ownership:

chmod 755 *
 

Step 3 From the Base Application folder, run the installer:

./primecentral_v1.2.bin
 

Step 4 In the Welcome window, click Next .


Tip You can also press the Tab key + space bar to activate the Next (or Previous) button.

Step 5 In the License Agreement window, read the license agreement, click the I accept the terms of the License Agreement radio button, and click Next .

Step 6 In the Install Type window, click the Single-Server Install radio button; then, click Next .

Step 7 In the Validating Environment window, review the information for accuracy; then, click Next .

Step 8 In the Server Information window, confirm that the fully qualified domain name (FQDN) of the local server is correct; if not, enter the correct FQDN. (Be sure to use the hostname of the server where Prime Central will be mounted.) Then, click Next .

Step 9 In the Choose Install Folder window, specify where to install Prime Central. The “o” (other or world) UNIX users must have at least execute permissions on the installation directory path. Then, click Next .

Step 10 In the OS User Information window, provide the information required to create an OS user to start and stop processes. The username is primeusr and cannot be changed. Then, click Next .

Step 11 In the Admin User Information window, enter the password for the admin user who will be used for the first system login. The username is centraladmin and cannot be changed. Then, click Next .

Step 12 In the Install Mode window, specify one of the following installation modes:

    • Simple Install—Click Next ; then, continue to Step 13.
    • Advanced Install—Click Next ; in the Advanced Configuration window, enter the desired port numbers and configuration values for the third-party servers; then, click Next . (For port descriptions, see Table 3 .)

Step 13 In the Validating Port Configuration window, review the information for accuracy; then, click Next .

Step 14 In the Database Type window, specify one of the following database types; then, click Next :

Embedded Database:

a. In the Embedded DB Information window, enter the required information for your local or remote embedded database; then, click Next . (For details about the fields in this window, see Table 5 .)

b. In the Prime Central DB User Information window, enter the password for the database user that will be created for Prime Central. The username is primedba and cannot be changed. Then, click Next .


Note Be sure to note down the database user password for future reference. For example, if you decide to register an application with Prime Central, you will need this password.

External Database:

a. In the Database Information window, enter the required information for your preinstalled local or remote external database; then, click Next .

b. In the Database File Directory window, specify where to store database data files. The directory you choose must exist, must be owned by the oracle user, and must not contain any data files. Then, click Next .

Step 15 Verify that the information in the Pre-Installation Summary window is correct; then, click Install .

It might take 30 minutes or longer to install Prime Central, depending on your system performance and whether you are using an embedded or external database.

Step 16 In the Install Complete window, click Done .

If the installation fails, see Troubleshooting the Installation.


 

Explanation of Fields in the Embedded DB Information Window

The following table describes the required information for your local or remote embedded database.

 

Table 5 Fields in the Embedded DB Information Window

Field
Description

Oracle User

The default username is oracle .

Oracle Home Directory

The installer creates /export/home/oracle by default. If you want to use a different directory, choose one that is not already present on the server.

Data Files Location

The default is /export/home/oracle/oradata/primedb.

Redo Files Location

The default is /export/home/oracle/redo.

Enable backups on the database

Check this optional check box to enable backups on the Oracle database.

Archive Log Location

(Required if “Enable backups on the database” is checked) The default is /export/home/oracle/arch.

Backup Destination

(Required if “Enable backups on the database” is checked) The default is /export/home/oracle/backup.

Install database on remote server

Check this optional check box to install the embedded database on a remote server. The SSH user and password are used to establish an SSH connection between Prime Central and the remote database server.

Remote SSH User

(Required if “Install database on remote server” is checked) The remote SSH user’s home directory cannot be the / directory.

Remote SSH User Password

(Required if “Install database on remote server” is checked) Enter the password for the remote SSH user. The password cannot contain a percent sign (%).

Server IP Address

Enter the IP address of the server where the database will be installed.

Root Password

Enter the root password for the server where the database will be installed. The password cannot contain a percent sign (%).

Installing Prime Central in a Dual-Server Setup

Installing the Prime Central portal and Prime Central integration layer on separate servers—called a distributed or dual-server installation—is a three-part process:

1. Prepare both servers for installation.

2. Install the Prime Central portal.

3. Install the Prime Central integration layer.


Note • You must install the Prime Central portal before installing the Prime Central integration layer.

 

Preparing Both Servers for Installation

Before you install the Prime Central portal and the Prime Central integration layer on separate servers, you must first connect to each server and, if using X server, verify the display settings.

Do the following on both servers:


Step 1 Use one of the following to connect to the server:

Step 2 As the root user, launch a terminal on the server. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended, but you can also use the Bash shell.

    • To start the C shell, enter:

/bin/csh

    • To start the Bash shell, enter:

/bin/bash

 

If you are using X server, continue to Step 3.

If you are using VNC, skip to Step 5.

Step 3 Set the DISPLAY variable:

setenv DISPLAY hostname-or-IP-address:0.0
 

Step 4 Verify that the display is set correctly:

echo $DISPLAY
 

In the command output, you should see:

hostname-or-IP-address:0.0
 

Step 5 Set the ulimit value.

If using a C shell, enter:

limit descriptors 1048576
 

In the command output, you should see:

# limit descriptors
descriptors 1048576
 

If using a Bash shell, enter:

ulimit -n 1048576
 

In the command output, you should see:

# ulimit –n
1048576
 

Step 6 (For an external database only; not applicable to an embedded database) If you are using a local or remote external database, create the following directory under ORACLE_HOME for the PSI integration, and make the owner oracle:

ORACLE_HOME/oradata/PSI
 


 

Installing the Prime Central Portal


Step 1 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the Base Application folder.

Step 2 Change file permissions and ownership:

chmod 755 *
 

Step 3 From the Base Application folder, run the installer:

./primecentral_v1.2.bin
 

Step 4 In the Welcome window, click Next .

Step 5 In the License Agreement window, read the license agreement, click the I accept the terms of the License Agreement radio button, and click Next .

Step 6 In the Install Type window, click the Distributed Install radio button; then, click Next .

Step 7 In the Distributed Install Components window, click the Portal radio button; then, click Next .

Step 8 In the Validating Environment window, review the information for accuracy; then, click Next .

Step 9 In the Server Information window, confirm that the FQDN of the local server is correct; if not, enter the correct FQDN. Then, click Next .

Step 10 In the Choose Install Folder window, specify where to install the Prime Central portal. The “o” (other or world) UNIX users must have at least execute permissions on the installation directory path. Then, click Next .

Step 11 In the OS User Information window, provide the information required to create an OS user to start and stop processes. The username is primeusr and cannot be changed. Then, click Next .

Step 12 In the Admin User Information window, enter the password for the admin user who will be used for the first system login. The username is centraladmin and cannot be changed. Then, click Next .

Step 13 In the Install Mode window, specify one of the following installation modes:

    • Simple Install—Click Next ; then, continue to Step 14.
    • Advanced Install—Click Next ; in the Advanced Configuration window, enter the desired port numbers and configuration values for the third-party servers; then, click Next . (For port descriptions, see Table 3 .)

Step 14 In the Validating Port Configuration window, review the information for accuracy; then, click Next .

Step 15 In the Database Type window, specify one of the following database types; then, click Next :

Embedded Database:

a. In the Embedded DB Information window, enter the required information for your local or remote embedded database; then, click Next . (For details about the fields in this window, see Table 5 .)

b. In the Prime Central DB User Information window, enter the password for the database user that will be created for Prime Central. The username is primedba and cannot be changed. Then, click Next .


Note Be sure to note down the database user password for future reference. For example, if you decide to register an application with Prime Central, you will need this password.

External Database:

a. In the Database Information window, enter the required information for your preinstalled local or remote external database; then, click Next .

b. In the Database File Directory window, specify where to store database data files; then, click Next . The directory you choose must exist, must be owned by the oracle user, and must not contain any data files. For a remote server, the Oracle database file directory must be present on the remote server where Oracle is installed.

For example, the database file directory /dbdata owned by the oracle user is as follows:

drwxr-xr-x 2 oracle oinstall 512 Dec 8 14:04 dbdata

 

Step 16 Verify that the information in the Pre-Installation Summary window is correct; then, click Install .

It might take 30 minutes or longer to install the Prime Central portal, depending on your system performance and whether you are using an embedded or external database.

Step 17 In the Install Complete window, click Done .

If the installation fails, see Troubleshooting the Installation.


 

Installing the Prime Central Integration Layer


Step 1 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the Base Application folder.

Step 2 Change file permissions and ownership:

chmod 755 *
 

Step 3 From the Base Application folder, run the installer:

./primecentral_v1.2.bin
 

Step 4 In the Welcome window, click Next .

Step 5 In the License Agreement window, read the license agreement, click the I accept the terms of the License Agreement radio button, and click Next .

Step 6 In the Install Type window, click the Distributed Install radio button; then, click Next .

Step 7 In the Distributed Install Components window, click the Integration Layer radio button; then, click Next .

Step 8 In the Validating Environment window, review the information for accuracy; then, click Next .

Step 9 In the Database Information window, enter the following Prime Central database connection information; then, click Next :

    • Server IP address or hostname.
    • Port—The default is 1521.
    • SID—The default is primedb .
    • Prime database user—The username is primedba and cannot be changed.
    • Prime database password.

Step 10 To scale the integration layer to support multiple application instances and provide the option of high availability, Prime Central 1.2 uses a distributed integration layer architecture.

In the Integration Layer Profile window, specify one or both of the following integration layer profiles:

    • Prime Central integration layer: Messaging —Installs a separate JMS broker to enable the integration layer messaging framework to be configured as a JMS cluster for messaging service high availability. Click Next ; in the confirmation popup window, click one of the following:

Yes —To change the connection transport type, request timeout, or reconnect delay. In the Integration Layer–JMS Data window, make the desired changes; then, click Next .

No —To use the default values for connection transport type, request timeout, and reconnect delay. Then, continue to Step 11.

    • Prime Central integration layer: Core —Installs the integration layer core components. Click Next ; then, continue to Step 11.

Step 11 In the Server Information window, confirm that the FQDN is correct; if not, enter the correct FQDN. Then, click Next .

Step 12 In the Choose Install Folder window, specify where to install the Prime Central integration layer. The “o” (other or world) UNIX users must have at least execute permissions on the installation directory path. Then, click Next .

Step 13 In the OS User Information window, provide the information required to create an OS user to start and stop processes. The username is primeusr and cannot be changed. Then, click Next .

Step 14 In the Install Mode window, specify one of the following installation modes:

    • Simple Install—Click Next ; then, continue to Step 15.
    • Advanced Install—Click Next ; in the Advanced Configuration window, enter the desired port numbers and configuration values for the third-party servers; then, click Next . (For port descriptions, see Table 3 .)

Step 15 In the Validating Port Configuration window, review the information for accuracy; then, click Next .

Step 16 Verify that the information in the Pre-Installation Summary window is correct; then, click Install .

It might take 10 minutes or longer to install the Prime Central integration layer, depending on your system performance and whether you are using an embedded or external database.

Step 17 In the Install Complete window, click Done .

If the installation fails, see Troubleshooting the Installation.


 

Pathname, Group Name, Username, and Password Constraints

During the Prime Central installation, the variables that you define must adhere to the constraints listed in Table 6 .

 

Table 6 Pathname, Group Name, and Password Constraints

Variable
Constraints
Choose Install Folder Window

Installation directory pathname

The installation directory pathname cannot:

  • Exceed 100 characters.
  • Contain non-ASCII characters.
  • Contain special shell characters (; & ( ) | < > ' " ` $ *).
  • Contain whitespace characters (<newline>, <space>, <tab>).
User Information Windows (OS User, Admin User, Prime Central Database User, Fault Management Application User)

OS user group name

The OS user group name must:

  • Contain from 1 to 8 alphanumeric characters.
  • Begin with a letter (a-z, A-Z).
  • Contain at least one lowercase letter (a-z).
  • Not contain any special characters except hyphen (-) or underscore (_).

Fault Management application username

The Fault Management application username must:

  • Contain from 1 to 8 alphanumeric characters.
  • Begin with a letter (a-z, A-Z).
  • Contain at least one lowercase letter (a-z).
  • Not contain any special characters except hyphen (-) or underscore (_).

All user passwords

Except where noted, the following constraints apply to all user passwords:

  • Character count:

Prime Central database user passwords only—8 to 12 characters.

All other user passwords—8 to 32 characters.

  • Alphanumeric characters:

At least one uppercase letter (A-Z).

At least one lowercase letter (a-z).

At least one number (0-9).

No character repeated three or more times.

Does not contain the username or the username in reverse.

Does not contain cisco, ocsic, or any variation.

  • Special characters:

All user passwords—At least one special character from the following:

~ @ # % ^ * ( ) _ - + = | { [ } ] : ; < , > . /

No other special characters are allowed.

Prime Central database user only—At least one special character is required, but the password cannot begin with a special character.

Verifying the Prime Central Installation


Step 1 As the primeusr user, log into the Linux server with the primeusr password that you specified during the installation.

Step 2 Verify that the Prime Central portal is running:

# portalctl status
 

In the output, you should see:

Prime Central Platform Status
Started
 

Step 3 Open a web browser and log into the Prime Central portal at https:// server-hostname : https-port-number , where:

    • server-hostname is the hostname of the newly installed Prime Central server.
    • https-port-number is the SSL port number that was configured during installation.

Step 4 Enter the username centraladmin and the admin user password that you specified during the installation.


 

Checking the Prime Central Version


Step 1 As the primeusr user, log into the Prime Central server.

Step 2 On the command line, enter:

version
 

The following is an example of the output of the version command:

# version
Running Integration Layer(PC-IL-CORE,PC-IL-JMS) + Platform (v 1.2.0.0 (build number)) with Patch(0.0.0.0)
 

Note If you reinstall a new build on an existing server, or if you install or uninstall applications, be sure to open a new browser window with a clear cache.


 

Installing Prime Central Silently

You can install Prime Central without user interaction. In a silent installation, no messages or prompts appear on-screen, and interactive dialogs are not displayed. Information and answers that you would normally provide are read from a properties file.

A silent installation allows for unattended product installations based on the values that are provided in the silent installation properties file.


Step 1 As the root user, launch a terminal on the server where you want to silently install Prime Central. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

Step 2 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the local folder where the drive is mounted.

Step 3 Create an install.properties file based on the samples provided in Sample install.properties Files. Depending on the input that you provide, Prime Central will be installed in either a single-server setup or a dual-server (distributed) setup.


Caution Be careful to enter correct values in the install.properties file. The silent installation does not perform any validation on the values you enter.

Step 4 Save your changes to the install.properties file.

Step 5 Change file permissions:

chmod 755 *
 

Step 6 Run the installer:

./primecentral_v1.2.bin -i silent -f install.properties
 

The silent installation log files are available in the installation-directory /install/logs/ folder.


 

Sample install.properties Files

The following examples show a typical install.properties file for each of the following scenarios:


Caution The values shown in the following examples are for illustrative purposes only. Be careful to enter actual values that are appropriate for your operating environment.

Example 1 Installing Prime Central in a Single-Server Setup with a Local Embedded Database

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Single-Server Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=Embedded Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=
SUITEFW_DB_SYSTEM_PASSWD=
SUITEFW_DB_SYSTEM_USER=system
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=
SUITEFW_DBF_FILES_DIR=
 
### Embedded Database
 
SUITEFW_EMBEDDED_REMOTE=0
SUITEFW_EMBEDDED_ROOT_PASSWD=poPPee
SUITEFW_EMBEDDED_HOST_IP=209.165.201.30
SUITEFW_EMBEDDED_DBPROFILE=2
SUITEFW_EMBEDDED_SMTP=self
SUITEFW_EMBEDDED_SSH_USER=
SUITEFW_EMBEDDED_SSH_USER_PASSWORD=
SUITEFW_EMBEDDED_ORACLE_HOME=/export/home/oracle
SUITEFW_EMBEDDED_ORACLE_USER=oracle
SUITEFW_EMBEDDED_DATAFILES=/export/home/oracle/oradata/primedb
SUITEFW_EMBEDDED_REDO=/export/home/oracle/redo
SUITEFW_EMBEDDED_BACKUP=1
SUITEFW_EMBEDDED_ARCHIVE=/export/home/oracle/arch
SUITEFW_EMBEDDED_BACKUP_DEST=/export/home/oracle/backup
 
########## Install Mode ##########
 
SUITEFW_BOTH_INSTALL_MODE=Simple Install
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
#SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE

Example 2 Installing Prime Central in a Single-Server Setup with a Remote Embedded Database

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Single-Server Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=Embedded Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=
SUITEFW_DB_SYSTEM_PASSWD=
SUITEFW_DB_SYSTEM_USER=system
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=
SUITEFW_DBF_FILES_DIR=
 
### Embedded Database
 
SUITEFW_EMBEDDED_REMOTE=1
SUITEFW_EMBEDDED_ROOT_PASSWD=poPPee123
SUITEFW_EMBEDDED_HOST_IP=209.165.200.254
SUITEFW_EMBEDDED_DBPROFILE=2
SUITEFW_EMBEDDED_SMTP=self
SUITEFW_EMBEDDED_SSH_USER=test
SUITEFW_EMBEDDED_SSH_USER_PASSWORD=Admin123~
SUITEFW_EMBEDDED_ORACLE_HOME=/export/home/oracle
SUITEFW_EMBEDDED_ORACLE_USER=oracle
SUITEFW_EMBEDDED_DATAFILES=/export/home/oracle/oradata/primedb
SUITEFW_EMBEDDED_REDO=/export/home/oracle/redo
SUITEFW_EMBEDDED_BACKUP=1
SUITEFW_EMBEDDED_ARCHIVE=/export/home/oracle/arch
SUITEFW_EMBEDDED_BACKUP_DEST=/export/home/oracle/backup
 
########## Install Mode ##########
 
SUITEFW_BOTH_INSTALL_MODE=Simple Install
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
#SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE

Example 3 Installing Prime Central in a Single-Server Setup with an External Database

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Single-Server Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=External Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=209.165.200.225
SUITEFW_DB_SYSTEM_PASSWD=manager
SUITEFW_DB_SYSTEM_USER=system
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=service-name
SUITEFW_DBF_FILES_DIR=/export/home/oracle/prime_test
 
########## Install Mode ##########
 
SUITEFW_BOTH_INSTALL_MODE=Simple Install
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
#SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE

Example 4 Installing the Prime Central Portal in a Dual-Server Setup with a Local Embedded Database

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Distributed Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=Portal
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=Embedded Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=
SUITEFW_DB_SYSTEM_PASSWD=
SUITEFW_DB_SYSTEM_USER=system
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=
SUITEFW_DBF_FILES_DIR=
 
### Embedded Database
 
SUITEFW_EMBEDDED_REMOTE=0
SUITEFW_EMBEDDED_ROOT_PASSWD=poPPee
SUITEFW_EMBEDDED_HOST_IP=209.165.201.30
SUITEFW_EMBEDDED_DBPROFILE=2
SUITEFW_EMBEDDED_SMTP=self
SUITEFW_EMBEDDED_SSH_USER=
SUITEFW_EMBEDDED_SSH_USER_PASSWORD=
SUITEFW_EMBEDDED_ORACLE_HOME=/export/home/oracle
SUITEFW_EMBEDDED_ORACLE_USER=oracle
SUITEFW_EMBEDDED_DATAFILES=/export/home/oracle/oradata/primedb
SUITEFW_EMBEDDED_REDO=/export/home/oracle/redo
SUITEFW_EMBEDDED_BACKUP=1
SUITEFW_EMBEDDED_ARCHIVE=/export/home/oracle/arch
SUITEFW_EMBEDDED_BACKUP_DEST=/export/home/oracle/backup
 
########## Install Mode ##########
 
SUITEFW_BOTH_INSTALL_MODE=Simple Install
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
#SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE

Example 5 Installing the Prime Central Portal in a Dual-Server Setup with a Remote Embedded Database

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Distributed Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=Portal
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=Embedded Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=
SUITEFW_DB_SYSTEM_PASSWD=
SUITEFW_DB_SYSTEM_USER=system
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=
SUITEFW_DBF_FILES_DIR=
 
### Embedded Database
 
SUITEFW_EMBEDDED_REMOTE=1
SUITEFW_EMBEDDED_ROOT_PASSWD=poPPee123
SUITEFW_EMBEDDED_HOST_IP=209.165.200.254
SUITEFW_EMBEDDED_DBPROFILE=2
SUITEFW_EMBEDDED_SMTP=self
SUITEFW_EMBEDDED_SSH_USER=test
SUITEFW_EMBEDDED_SSH_USER_PASSWORD=Admin123~
SUITEFW_EMBEDDED_ORACLE_HOME=/export/home/oracle
SUITEFW_EMBEDDED_ORACLE_USER=oracle
SUITEFW_EMBEDDED_DATAFILES=/export/home/oracle/oradata/primedb
SUITEFW_EMBEDDED_REDO=/export/home/oracle/redo
SUITEFW_EMBEDDED_BACKUP=1
SUITEFW_EMBEDDED_ARCHIVE=/export/home/oracle/arch
SUITEFW_EMBEDDED_BACKUP_DEST=/export/home/oracle/backup
 
########## Install Mode ##########
 
SUITEFW_BOTH_INSTALL_MODE=Simple Install
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
#SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE

Example 6 Installing the Prime Central Portal in a Dual-Server Setup with an External Database

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Distributed Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=Portal
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=External Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=209.165.200.225
SUITEFW_DB_SYSTEM_PASSWD=manager
SUITEFW_DB_SYSTEM_USER=system
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=service-name
SUITEFW_DBF_FILES_DIR=/export/home/oracle/prime_test
 
########## Install Mode ##########
 
SUITEFW_BOTH_INSTALL_MODE=Simple Install
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
#SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE

Example 7 Installing the Prime Central Integration Layer in a Dual-Server Setup

Installer_UI=silent
 
########## Basic ##########
 
USER_INSTALL_DIR=/opt/primecentral
SUITEFW_INSTALL_TYPE=Distributed Install
SUITEFW_DISTRIBUTED_INSTALL_TYPE=Integration Layer
SUITEFW_BOTH_SERVER_HOSTNAME=prime-dev.cisco.com
 
########## OS User (primeusr is fixed, do not change it) ##########
 
SUITEFW_OS_USER=primeusr
SUITEFW_OS_GROUP=primegrp
SUITEFW_OS_PASSWD=Admin123~
SUITEFW_OS_TYPE=Linux
 
########## Application Admin user (centraldmin) password ###
 
SUITEFW_ADMIN_USER_PASSWD=Admin123~
 
########## DATABASE ##########
 
SUITEFW_DB_TYPE=External Database
 
### Database User (primedba is fixed. do not change it) ###
 
SUITEFW_DB_USER=primedba
SUITEFW_DB_USER_PASSWD=Admin123~
 
### External Database
 
SUITEFW_DB_HOST_IP_ADDRESS=198.51.100.1
SUITEFW_DB_SYSTEM_PASSWD=Admin123~
SUITEFW_DB_SYSTEM_USER=primedba
SUITEFW_DB_PORT=1521
SUITEFW_DB_SID=service-name
SUITEFW_DBF_FILES_DIR=/export/home/oracle/prime_test
 
### Portal
 
SUITEFW_PORTAL_HTTPS_PORT=8443
SUITEFW_PORTAL_HTTP_PORT=8080
SUITEFW_PORTAL_AJP_PORT=8009
SUITEFW_PORTAL_SHUTDOWN_PORT=8005
 
### IL
 
SUITEFW_IL_MTOSI_PORT=9110
SUITEFW_IL_CONNECTION_TRANSPORTTYPE=nio
SUITEFW_IL_CONNECTION_PORT=61616
SUITEFW_IL_NIO_TRANSPORT_PORT=61616
SUITEFW_IL_SSL_TRANSPORT_PORT=61615
SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 
 
### IL Profiles
# needed for distributed - IL
SUITEFW_IL_PROFILES=PC-IL-JMS PC-IL-CORE
 

Verifying the Silent Installation


Step 1 Open a web browser and log into the Prime Central portal at https:// server-hostname : https-port-number , where:

    • server-hostname is the hostname of the newly installed Prime Central server.
    • https-port-number is the SSL port number that was configured during installation.

Step 2 Enter the username centraladmin and the admin user password that you specified for the silent installation.

If you cannot log into the Prime Central portal, check the silent installation log files in the installation-directory /install/logs/ folder. If the installation failed, the log files contain errors and exceptions that you can use for troubleshooting.


 

Installing Prime Central Fault Management

Installing the Prime Central Fault Management component—which has its own installation binary—is a two-part process:

1. Prepare the server for installation.

2. Install the Prime Central Fault Management component.


Note During the installation, the variables that you define must adhere to the constraints described in Pathname, Group Name, Username, and Password Constraints.

Preparing the Server for Installation

Before you install the Prime Central Fault Management component, you must first connect to the server and, if using X server, verify the display settings.


Step 1 Use one of the following to connect to the server where you want to install Prime Central Fault Management:

Step 2 As the root user, launch a terminal on the server where you want to install Prime Central Fault Management. The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

If you are using X server, continue to Step 3.

If you are using VNC, you are finished; continue to Installing Prime Central Fault Management on the Server.

Step 3 Set the DISPLAY variable:

setenv DISPLAY hostname-or-IP-address:0.0
 

Step 4 Verify that the display is set correctly:

echo $DISPLAY
 

In the command output, you should see:

hostname-or-IP-address:0.0
 

Step 5 Update the /etc/hosts file on the server:

# IP-address FQDN hostname
 

For example:

192.168.1.170 fm-server.cisco.com fm-server
 

Step 6 Save the /etc/hosts file; then, run the following tests:

# hostname -a
fm-server
# hostname -f
fm-server.cisco.com
# hostname -i
192.168.1.170
# ipcalc -h 192.168.1.170
HOSTNAME=fm-server.cisco.com
 

If any of the tests return incorrect results, check the /etc/hosts file for typos. Check also the /etc/sysconfig/network file and verify that the HOSTNAME entry contains your server’s FQDN (fm-server.cisco.com in this example).

Step 7 Move (or remove) all *.log files from the /tmp folder.

Step 8 Verify that the RPM packages listed in Table 2 have been installed:

rpm -q compat-db compat-glibc compat-glibc-headers compat-libstdc++-296 compat-libstdc++-33 elfutils elfutils-libs gtk2 gtk2-engines kernel-headers ksh libgcc libXft libXmu libXp libXpm libXtst openmotif22 pam --qf "%{name}/%{version}/%{release}/%{arch}\n"
 


 

Installing Prime Central Fault Management on the Server


Step 1 Insert the Cisco Prime Central 1.2 USB, navigate to the Fault Management folder, and locate the FM1.2Build.tar.gz file.

Step 2 Use SSH to connect to the server.

Step 3 Copy the FM1.2Build.tar.gz file to the server.

Step 4 Distribute the file:

# tar -zxf FM1.2Build.tar.gz
# cd Disk1/InstData/VM
# chmod 755 primefm_v1.2.bin
 

Step 5 Run the installer:

#./primefm_v1.2.bin
 

Step 6 In the Introduction window, click Next .

Step 7 In the License Agreement window, read the license agreement, click the I accept the terms of the License Agreement radio button, and click Next .

Step 8 In the Environment Validation window, review the information for accuracy; then, click Next .

Step 9 In the Server Information window, confirm that the FQDN is correct; if not, enter the correct FQDN. Then, click Next .

Step 10 In the UNIX OS User Information window, provide the information required to create a UNIX OS user to start and stop processes; then, click Next .

    • The username is primeusr and cannot be changed.
    • The group name is ncoadmin and cannot be changed.

Step 11 In the App User Information window, enter the username and password for the Prime Central Fault Management application user; then, click Next .

Step 12 In the Database Information window, enter the following database connection information; then, click Next :

    • Server IP address or hostname.
    • Port—The default is 1521.
    • SID—The default is primedb .
    • Prime database username—The default is primedba .
    • Prime database password.

Step 13 In the Choose Install Folder window, specify where to install the Fault Management server; then, click Next . The default directory depends on whether you are installing the Fault Management component on the same server as Prime Central:

    • If you entered the IP address of the Prime Central server in Step 12, the installation directory defaults to /opt/primecentral/faultmgmt.
    • If you entered an IP address in Step 12 that is not the Prime Central server IP address, the installation directory defaults to /opt/primeusr/faultmgmt.

Step 14 In the Install Mode window, specify one of the following installation modes:

    • Simple Install—Click Next ; then, continue to Step 15.
    • Advanced Install—Click Next ; in the Advanced Configuration window, enter the desired port numbers for the Fault Management database server, gateway, and web server; then, click Next . (For port descriptions, see Table 3 .)

Step 15 Verify that the information in the Pre-Installation Summary window is correct; then, click Install .

Step 16 Confirm that both the Prime Central portal and the Prime Central integration layer are running on the Prime Central server.

It might take 90 minutes or longer to install Prime Central Fault Management, depending on your system performance.

Step 17 In the Install Complete window, click Done .

The installation log files are available in the installation-directory /install/logs/ folder.

Step 18 Complete the installation by logging into the Prime Central integration layer as the primeusr user and entering the following commands to restart it:

itgctl stop
itgctl start
 


 

Installing Prime Central Fault Management Silently


Step 1 As the root user, launch a terminal on the server where you want to silently install Prime Central Fault Management. The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

Step 2 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the local folder where the drive is mounted.

Step 3 Create a PrimeFM_install.properties file based on the sample provided in Sample PrimeFM_install.properties File.

The silent properties file is the same whether you are installing the Fault Management component on the same server as Prime Central, or on a separate server. If you are installing the Fault Management component on the same server as Prime Central, the OS user primeusr is already created. Therefore, when you create the PrimeFM_install.properties file, be sure to enter the correct password for the OS user primeusr.


Caution If you are installing the Fault Management component on the same server as Prime Central, you must install it as faultmgmt in a subdirectory immediately underneath Prime Central (for example, /opt/primecentral/faultmgmt).

Caution Be careful to enter correct values in the PrimeFM_install.properties file. The silent installation does not perform any validation on the values you enter.

Step 4 Save your changes to the PrimeFM_install.properties file.

Step 5 Change file permissions:

chmod 755 *
 

Step 6 Run the installer:

./primefm_v1.2.bin -i silent -f PrimeFM_install.properties
 

The silent installation log files are available in the installation-directory /install/logs/ folder.


 

Sample PrimeFM_install.properties File

The following example shows a typical PrimeFM_install.properties file for Prime Central Fault Management.


Caution The values shown in the following example are for illustrative purposes only. Be careful to enter actual values that are appropriate for your operating environment.

Note the following:

  • For the PRIMEFM_OS_USER parameter, the value primeusr is fixed; do not change it.
  • For the PRIMEFM_OS_GROUP and PRIMEFM_PA_GROUP parameters, the value ncoadmin is fixed; do not change it.
  • For the PRIMEFM_INSTALL_TYPE parameter, if you enter Simple Install , the default port values will be used. If you want to use different ports, enter Advanced Install .

Example 8 Sample PrimeFM_install.properties File when Installing Prime Central Fault Management

##########User Information###########
PRIMEFM_OS_USER=primeusr
PRIMEFM_OS_GROUP=ncoadmin
PRIMEFM_OS_PASSWD=Prime123@
PRIMEFM_PA_USER=primefm_pa
PRIMEFM_PA_GROUP=ncoadmin
PRIMEFM_PA_PASSWD=Prime123@
PRIMEFM_APP_USER=primefm
PRIMEFM_APP_USER_PASSWD=Prime123@
# Fully qualified hostname of the FM Server
PRIMEFM_SERVER_HOSTNAME=fm-server.cisco.com
#########Prime Central Database Information##########
PRIMEFM_DB_HOST_IP_ADDRESS=209.165.200.225
PRIMEFM_DB_PORT=1521
PRIMEFM_DB_SID=primedb
PRIMEFM_DB_SYSTEM_USER=primedba
PRIMEFM_DB_SYSTEM_PASSWD=Prime123@
##########User Install Directory#########
USER_INSTALL_DIR=/opt/primecentral/faultmgmt
##########Install Type##########
PRIMEFM_INSTALL_TYPE=Simple Install
#########Port Information##############
PRIMEFM_DB_SERVER_PORT=4100
PRIMEFM_GATEWAY_PORT=4300
PRIMEFM_PROXY_PORT=4400
PRIMEFM_PROCESS_AGENT_PORT=4200
PRIMEFM_SNMP_PROBE_PORT=1162
PRIMEFM_WEB_SERVER_PORT=16310
PRIMEFM_CORR_HTTP_PORT=9080
PRIMEFM_CORR_ADMIN_PORT=9060
PRIMEFM_CORR_DB_PORT=5435
PRIMEFM_CORR_CLI_PORT=2000

Manually Registering Fault Management to Retrieve Alarm Data

If an application is integrated with Prime Central but is not up and running when the Fault Management component is installed, you must manually register with the application if you want to receive alarms immediately. (Within 10 minutes of the Fault Management installation, an automatic cron job starts alarm retrieval.)

To bypass the 10-minute waiting period and begin receiving alarms immediately:


Step 1 As the primeusr user, log into the Prime Central Fault Management server.

Step 2 After the application is integrated with Prime Central, go to the installation-directory /prime_integrator/scripts folder and enter:

./DMRegistration.sh
 

Note The Fault Management component does not retrieve alarm data for Prime Provisioning or Cisco InTracer.


 

Installing the Gateways Used with Prime Central

You can install IBM Tier 1 and Tier 2 gateways that are available for use with Prime Central through a separately purchased license. The gateways have their own installation binary.


Note The following steps do not apply to the data source adaptors (DSAs) that are included in the Prime Central base application.


Step 1 Insert the Cisco Prime Central 1.2 USB drive into the USB port, navigate to the Gateways folder, and unzip the PC_Gateways.zip file.

Step 2 From the list of files displayed in the PC_Gateways/Tier1 or PC_Gateways/Tier2 folder, copy the desired file to the workstation on which you want to install the gateway.

Step 3 Uncompress (unzip) the file:

gunzip filename
 

Step 4 Extract the .tar archive contents:

tar -xvf filename
 

Step 5 Open the README.txt file that is packaged with the gateway. Follow the gateway installation steps as outlined in the README file.


 

Troubleshooting the Installation

If your Prime Central installation fails, you can check the log files to locate the problem and take the appropriate action.


Step 1 Check the following log files in the installation-directory /install/logs/ folder:

    • DBUserAction.log
    • ExitCode.log
    • installXMP.log
    • startXMP.log

Table 7 describes these and other log files to scan for information. Table 8 lists specific errors you might encounter and possible solutions.

Step 2 Uninstall Prime Central as explained in Uninstalling Prime Central.

Step 3 Restart the installation.


 

Prime Central Log Files

 

Table 7 Prime Central Log Files

Log File
Description

CreateOSGroup.log

Output and errors during OS user and group creation.

CreateOSUser.log

dbPasswdEncryption.log

Output and errors during the database and admin user password encryption process.

DBUserAction.log

Output and errors during database user and schema creation.

ExitCode.log

Exit codes for important installation actions. You can determine installation status from the exit codes.

insertESB-PC-IL-COMMON.log

Output and errors while persisting Prime Central integration layer information to the suite database.

insertESB-PC-IL-CORE.log

insertESB-PC-IL-JMS.log

insertESB.log

Output and errors while persisting Prime Central portal information to the suite database.

insertPortal.log

installESB-PC-IL-CORE.log

Output and errors during the Prime Central integration layer installation.

installESB-PC-IL-JMS.log

installXMP.log

Output and errors during XMP installation.

prime_embedded_oracle.log

Embedded database installation information.

  • The local server log file is saved in installation-directory /local/scripts/embedded_oracle.
  • The remote server log files are saved in two locations:

Local server: installation-directory /local/scripts/embedded_oracle.

Remote server: SSH-user-home-directory /ORA.

primecentral_uninstall.log

Uninstallation console output that is saved to /tmp.

psiintegration.log

Output and errors during the PSI integration.

startXMP.log

Output and errors during XMP startup. If an error is noted during XMP startup, check the installation-directory /XMP_Platform/logs/Startup.log file.

Note Installation console output is captured and stored in installation-directory/install/logs/primecentral_install.log.

UNINSTALL_LOG_ time-stamp

Uninstallation information that is time stamped and saved in /var/adm/Cisco/uninstall; for example, /var/adm/Cisco/uninstall /UNINSTALL_LOG_102711-123237.

Troubleshooting the Prime Central Installation

Table 8 offers additional troubleshooting steps to help solve installation-related problems.

 

Table 8 Troubleshooting the Prime Central Installation

Problem
Solution

An embedded database installation fails with the following error in the installation-directory /local/scripts/prime_embedded_oracle.log file:

Removing user 'oracle'
ERROR: Failed removing user 'oracle', please remove it manually by running 'userdel oracle'. ABORTING. ***
 

If you try to remove the oracle user manually, the following errors are generated:

# userdel oracle
userdel: error deleting password entry
userdel: error deleting shadow password entry

In the /etc/nsswitch.conf file, remove the nis entry from passwd, shadow, group, and services. Then, remove the oracle user.

The installation validation fails with an insufficient disk space error, even though the disk partition used to create the installation directory has more than 20 GB of free space.

Do the following:

1. To see if the installer is running on a non-English locale and therefore cannot parse the command outputs, enter:

# env | grep LANG
LANG=it_IT.UTF-8
 

2. Change the locale to en_US.UTF-8 and retry the installation.

An embedded database installation fails with the following errors in the installation-directory /local/scripts/ prime_embedded_oracle.log file:

Checking Temp space: must be greater than 120 MB. Actual 28037 MB Passed
Checking swap space: must be greater than 150 MB. Actual 4095 MB Passed
Database closed.
Database dismounted.
ORACLE instance shut down.
File created.
ORA-27102: out of memory
Linux-x86_64 Error: 28: No space left on device
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Real Application Testing options
0
'*** ERROR: Failed to execute the post installation tasks. Check log for more details. ABORTING. ***'
'*** ERROR: Installation failed. ABORTING. ***'

Verify that the available free memory on the system meets the Oracle installation requirements.

An embedded database installation fails with the following error in the installation-directory /local/scripts/ prime_embedded_oracle.log file:

'*** ERROR: Failed to enable automatic backups. Check log for more details. ABORTING. ***'

Verify that the available disk space meets the Oracle installation requirements.

An embedded database installation fails with the following errors in the installation-directory /local/scripts/ prime_embedded_oracle.log file:

Running (su - oracle -c "/export/home/oracle/product/11.2.0/db_1/bin/netca /silent /responsefile /export/home/oracle/tmp_prime/netca.rsp") euid: 0
'*** ERROR: Failed to run netca (256)'
Wed Aug 21 14:43:59 PDT 2013 Oracle Net Configuration Assistant
Parsing command line arguments:
Parameter "silent" = true
Parameter "responsefile" = /export/home/oracle/tmp_prime/netca.rsp
Parameter "log" = /export/home/oracle/tmp_prime/netca.log
Done parsing command line arguments.
Oracle Net Services Configuration:
LISTENER: The information provided for this listener is currently in use by other software on this computer.
Default local naming configuration complete.
Created net service name: primedb
Profile configuration complete.
Check the trace file for details: /export/home/oracle/cfgtoollogs/netca/trace_OraDb11g_home1-1108242PM4358.log
Oracle Net Services configuration failed. The exit code is 1

Verify that the /etc/hosts format is correct; for example:

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
10.10.10.10 core.domain.com core
 
 

An embedded database installation fails with the following errors in the installation-directory /local/scripts/prime_embedded_oracle.log file:

ORA-27102: out of memory
Linux-x86_64 Error: 28: No space left on device
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Real Application Testing options
0
*** ERROR: Failed to execute the post installation tasks. Check log for more details. ABORTING. ***

Verify that your system meets the requirements listed in Embedded Database Requirements.

Database connection errors are generated while installing the Prime Central integration layer in a dual-server setup.

Do the following:

1. Verify that the Prime Central integration layer can access the suite database server.

2. Verify that the database is up and running.

3. If there is a firewall on the suite database server that prevents external connections, disable it by entering the following commands as the root user:

service iptables save
service iptables stop
chkconfig iptables off

An embedded database installation fails with the following errors in the installation-directory /local/scripts/prime_embedded_oracle.log file:

ERROR: Failed to run netca (256) UnsatisfiedLinkError exception loading native library: njni11
java.lang.UnsatisfiedLinkError: /export/home/oracle/product/11.2.0/db_1/lib/libnjni11.so: libclntsh.so.11.1: cannot open shared object file: No such file or directory
Error: jniGetOracleHome
Oracle Net Services configuration failed. The exit code is 1
. ABORTING. ***

Verify that the correct Oracle system packages are installed in libaio-devel, libaio, and glibc-devel. For example, this problem occurs if glibc-devel-2.5.49 (x86_64) is not installed on the x86_64 system. To verify that the correct Oracle system packages are installed, enter:

rpm -qa --queryformat "%{NAME}-%{VERSION}.%{RELEASE} (%{ARCH})\n" | sort > /tmp/rpmlist.txt

An embedded database installation fails because the /etc/oratab file contains an extra user at the bottom of the file, as shown in the following example:

# This file is used by ORACLE utilities. It is created by # root.sh and updated by the Database Configuration Assistant # when creating a database.
 
# A colon, ':', is used as the field terminator. A new line # terminates the entry. Lines beginning with a pound sign, '#', # are comments.
#
# Entries are of the form:
# $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home # directory of the database respectively. The third field # indicates to the dbstart utility that the database should, # "Y", or should not, "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
orcl:/opt/oracle/app/oracle/product/11.2.0/dbhome_5:N

Verify that the /etc/oratab file does not contain any users except for the primedb user. (Because the installation failed, the primedb user might not be present.) If /etc/oratab contains any user other than the primedb user, delete the extra user. Then, rerun the installation.

The Prime Central installation fails after installing the database. As part of the failed installation, the installer copies the /var/.com.zerog.registry.xml file to the system. If you later try to reinstall Prime Central, the presence of the /var/.com.zerog.registry.xml file prevents you from performing any subsequent installations.

Do the following:

1. Uninstall Prime Central (if the uninstall folder exists).

2. If the uninstall folder does not exist, do the following as the root user:

a. Check for any users:

su - primeusr
 

b. If any users exist, remove them:

userdel primeusr
 

c. Delete the /var/.com.zerog.registry.xml file manually.

3. Reinstall Prime Central.

The Prime Central installation quits with an error message about viewing the prime_embedded_oracle.log file on both the local and remote machines. However, no log files exist at the specified locations.

Look at the primecentral_install.log file for exceptions or errors that relate to zip, unzip, or open files. (The primecentral_install.log file is located under /tmp/ or installation-directory /install/logs/.) The root cause of this problem is that the ulimit value was not set to ulimit -n 1048576.

While registering an application with Prime Central, you receive error messages similar to the following:

********* Running DMIntegrator on hostname at Thu Dec 19 06:26:52 PDT 2013 **********
 
- Initializing
- Checking property file
- Validating Java
- Setting ENVIRONMENT
- User Home Directory: /opt/CiscoTransportManagerServer
- Extracting DMIntegrator.tar
mkdir: Failed to make directory "DMIntegrator"; File exists
- Setting Java Path
mkdir: Failed to make directory "lib"; File exists
- JAVA BIN : /opt/jdk1.6.0_24/bin/java -classpath /opt/CiscoTransportManagerServer/prime_integrator/DMIntegrator/lib/*:/opt/CiscoTransportManagerServer/prime_integrator/DMIntegrator/lib
- Creating Data Source
- Encrypting DB Passwd
- Created /opt/CiscoTransportManagerServer/prime_integrator/datasource.properties
- PRIME_DBSOURCE: /opt/CiscoTransportManagerServer/prime_integrator/datasource.properties
- Checking DB connection parameters
 
@@@@ Aborting Due to: Database connection error. Please verify DB connection parameters. Exiting. @@@@@@@

Add the entry dns next to “hosts:” in the /etc/nsswitch.conf file.

Installation of the Fault Management component fails.

Do the following:

1. Add the following line to the /etc/hosts file:

IP-address FQDN loghost
 

2. To verify that you have the correct FQDN, enter:

hostname --fqdn
 

Uninstall and then reinstall Prime Central Fault Management. When the installer prompts you for the FQDN, use the one that you configured in the /etc/hosts file.

Installation or upgrade of the Fault Management component fails with the following error message:

Failed to upgrade CAP, please check the installation log for problems and try again.

Do the following:

1. Uninstall Prime Central Fault Management.

2. Move (or remove) all *.log files from the /tmp folder.

3. Reinstall Prime Central Fault Management.

Configuring Applications as Suite Components

You can integrate an existing installation of the following applications with Prime Central:

  • Cisco InTracer
  • Prime Network, including the Prime Network integration layer
  • Prime Optical, including the Prime Optical integration layer
  • Prime Performance Manager
  • Prime Provisioning

This section assumes that you have already installed the application in standalone mode, and now you want it to join the Prime Carrier Management suite.

Integration Process

When you install an individual application, it contains the following files, which the Prime Central portal and Prime Central integration layer require to identify and route to the application:

  • DMIntegrator.sh—Wrapper script to invoke the API to register the application with the Prime Central platform.
  • DMIntegrator.tar—Tar bundle that contains the libraries required to register the application.

The application integration (also known as registration ) process is as follows:

1. The DMIntegrator.sh and DMIntegrator.tar files integrate the application with Prime Central. (These files are bundled with the application installers.)

2. The DMIntegrator.prop file is generated when the application is installed. (This file contains information to populate the application in the Prime Central database and is provided as input to the DMIntegrator.sh script.)

3. The DMIntegrator.sh script runs in interactive or silent mode:

Interactive mode—You are prompted for database information such as username, password, IP address, service name, and so on.

Silent mode—Database information is passed as CLI arguments to the DMIntegrator.sh script.

These modes are useful for both:

Standalone application integration

Seamless installation as a suite component

4. The DMIntegrator.sh script calls the DMSwitchToSuite.sh script, which switches between the standalone application installer and the integrated application installer.

5. The application installer installs the application in either standalone or integrated mode. In integrated mode, the application installer calls the DMIntegrator.sh script to make the integration seamless.

Note the following:

  • Once Prime Provisioning is integrated with Prime Central, it cannot be reverted to standalone mode, even after unregistering Prime Provisioning.
  • The DMIntegrator.sh, DMIntegrator.tar, and DMIntegrator.prop files reside in the application-installation-directory /prime_integrator/ folder on the application server.
  • The DMIntegrator.sh file generates the following output, which is available in the application-installation-directory /prime_integrator/ folder:

datasource.properties—Contains connection information for the Prime Central database; the password is encrypted.

dmid.xml—Contains a unique ID that the application uses to update its information in the Prime Central database.

pc.xml—Contains the name of the Prime Central server with which the application integrates.

  • If Prime Network is installed on an IPv6-only gateway, you cannot integrate it with Prime Central.

Contents of the DMIntegrator.prop File

The DMIntegrator.prop file is generated by entering environment values for each application. The file contains the following name-value pairs:

TYPE={cfm | cit | ful | net | opt | ppm}
DISPLAY={Fault Management | CIT | Prime Network | Prime Optical | Prime Performance Manager | Prime Provisioning}
HOSTNAME=
DESCRIPTION=
VERSION=
PATCH=
DB_VERSION=
DB_LOCATION=
DB_SID=
DB_PORT=
DB_TYPE=
INSTALL_DATE_TIME=
INSTALL_LOCATION=
OS_USERNAME=
SWITCH_TO_SUITE_LOC=
PROTOCOL_PORT_PAIR=<name:value,name:value,name:value,...>
BUILD_NUMBER=
 

where:

  • DISPLAY is the application.
  • SWITCH_TO_SUITE_LOC is the location of the DMSwitchToSuite.sh script on the application.
  • PROTOCOL_PORT_PAIR is a comma-separated pair of protocols and ports relevant to the application.
  • BUILD_NUMBER is the build number of the installed application.

DMIntegrator.sh Script Usage

The DMIntegrator.sh script shows the following usage:

./DMIntegrator.sh [-n] prop-file server-hostname service-name db-user db-password db-port
./DMIntegrator.sh [-a] prop-file server-hostname service-name db-user db-password db-port
./DMIntegrator.sh [-i] prop-file
 

where:

  • -n is for noninteractive, single application instance registration
  • -a is for noninteractive, multiple application instance registration
  • -i is for interactive mode for both single and multiple application instance registration

For example:

./DMIntegrator.sh -a DMIntegrator.prop db-server db-sid db-user db-password db-port
 

where:

  • db-server—Prime Central database server hostname or IP address.
  • db-sid—Prime Central database service name ( primedb for an embedded database; user provided for an external database).
  • db-user—Prime Central database user ( primedba for an embedded or external database).
  • db-password—Prime Central database user password.
  • db-port—Prime Central database port number ( 1521 for an embedded database; user provided for an external database).

Note The DMIntegrator.sh script output is available in the DMIntegrator.log file.

Integrating Cisco InTracer with Prime Central


Step 1 As the application user, shut down Cisco InTracer.

Step 2 Verify that the JAVA_HOME environment variable points to Java 1.6, which the DMIntegrator.sh script requires.

Step 3 Verify that the /usr/bin/scp secure copy tool is present on the Cisco InTracer server.

Step 4 Under the Cisco InTracer home folder, create a prime_integrator folder (if it does not already exist) and copy the following files to it:

    • DMIntegrator.prop
    • DMIntegrator.sh
    • DMIntegrator.tar

Step 5 Verify that permissions are correct.

Step 6 Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

$ ./DMIntegrator.sh
 

Step 7 As the primeusr user, log into the Prime Central integration layer and restart it:

a. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

itgctl list

 

b. Note down the ID of the integration layer instance with the “PC-IL-CORE” profile.

c. Stop the PC-IL-CORE profile instance:

itgctl stop ID

 

d. Restart the integration layer:

itgctl start ID

 

Step 8 Start Cisco InTracer.

Step 9 After Cisco InTracer is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.


 

Integrating Prime Network with Prime Central


Step 1 As the application user, shut down Prime Network:

networkctl stop
 

Step 2 Verify that the JAVA_HOME environment variable points to Java 1.6, which the DMIntegrator.sh script requires:

java -version
 

Step 3 Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

$ ./DMIntegrator.sh
 

Step 4 Start Prime Network:

networkctl start
 

Step 5 After Prime Network is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.

Step 6 Restart the Prime Central integration layer so that it recognizes the recently added Prime Network server:

itgctl stop
itgctl start
 

Step 7 Now that Prime Network is integrated with Prime Central, you must also integrate the Prime Network integration layer. Continue to Integrating the Prime Network Integration Layer with Prime Central.


 

Integrating the Prime Network Integration Layer with Prime Central


Step 1 As the Prime Network user, log into the Prime Network gateway:

ssh root@Prime-Network-host-IP-address
su - prime
 

Note In this example, prime is the Prime Network user.

Step 2 Disable the Prime Network integration layer health checker by entering the following command on the Prime Network gateway server:

$PRIMEHOME/local/scripts/il-watch-dog.sh disable
 

Step 3 Stop the Prime Network integration layer:

$PRIMEHOME/bin/itgctl stop
 

Step 4 Change directories to the $PRIMEHOME/integration directory:

cd $PRIMEHOME/integration
 

Step 5 Run the DMIntegrator script. (For usage details, see DMIntegrator.sh Script Usage.)

./DMIntegrator.sh -a ILIntegrator.prop Prime-Central-DB-hostname db-SID db-user db-password port
 

Step 6 Reload the user profile:

source $HOME/.cshrc
 

Step 7 Enable the Prime Network integration layer health checker by entering the following command on the Prime Network gateway server:

$PRIMEHOME/local/scripts/il-watch-dog.sh enable
 

Step 8 Start the Prime Network integration layer:

$PRIMEHOME/bin/itgctl start
 


 

Integrating Prime Network in a High Availability Configuration with Prime Central

If Prime Network is installed in a local redundancy, Red Hat Cluster Suite (RHCS) high availability (HA) configuration, you can integrate it with Prime Central. However, if Prime Network is installed in a geographic redundancy HA configuration, you cannot integrate it with Prime Central.


Step 1 As the application user, shut down Prime Network.

Step 2 Verify that the JAVA_HOME environment variable points to Java 1.6, which the DMIntegrator.sh script requires.

Step 3 Verify that the /usr/bin/scp secure copy tool is present on the Prime Network server.

Step 4 Under the Prime Network home folder, create a prime_integrator folder (if it does not already exist) and copy the following files to it:

    • DMIntegrator.prop
    • DMIntegrator.sh
    • DMIntegrator.tar

Step 5 Verify that permissions are correct.

Step 6 In the DMIntegrator.prop file, change the HOSTNAME value to ana-cluster-ana .

Step 7 Add the hostname ana-cluster-ana to the /etc/hosts file on the Prime Central machine.

Step 8 Repeat Step 7 on the client workstation. If you are using a Windows workstation, use the C:\Windows\system32\drivers\etc\hosts file.

Step 9 Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

$ ./DMIntegrator.sh
 

Note For the database IP address or hostname, use the virtual IP address of the HA server.

Step 10 As the Prime Network user, run the jars script:

a. Enter:

cd ~/prime_integrator/PN_PC_Integration/

perl runPrimeCentralUpgrade.pl

 

b. When prompted, enter the Prime Central IP address, Prime Central root username and password, and the system’s Prime Central username (usually primeusr).

Step 11 If you are reintegrating the same Prime Network instance with a different COM-URI, you must restart the Prime Central portal. (The COM-URI is the Prime Network identifier and can be found in the Prime Central portal > Suite Monitoring portlet.) To do so, log into the Prime Central portal as the primeusr user and enter:

portalctl stop
portalctl start
 

Step 12 Start Prime Network.

Step 13 After Prime Network is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.


 

Integrating the Prime Network Integration Layer in a High Availability Configuration with Prime Central

If the Prime Network integration layer is installed in a local redundancy RHCS HA configuration, you can integrate it with Prime Central. However, if the Prime Network integration layer is installed in a geographic redundancy HA configuration, you cannot integrate it with Prime Central.


Step 1 Log into the Prime Network cluster node:

ssh root@IP-address
 

Step 2 As the root user, freeze the “ana” service, if it is not yet frozen:

clusvcadm -Z ana
 

Step 3 Switch users to the Prime Network application user (in this example, prime ):

su - prime
 

Step 4 Stop the Prime Network integration layer:

$PRIMEHOME/bin/itgctl stop
 

Step 5 Change directories to the $PRIMEHOME/integration directory:

cd $PRIMEHOME/integration
 

Step 6 In the ILIntegrator.prop file, change the HOSTNAME value to ana-cluster-ana .

Step 7 Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

./DMIntegrator.sh -a ILIntegrator.prop Prime-Central-hostname service-name db-user db-password db-port
 

Note For the database IP address or hostname, use the virtual IP address of the HA server.

Step 8 Reload the user profile:

source $HOME/.cshrc
 

Step 9 Log out from the Prime Network application user and, as the root user, unfreeze the “ana” service:

exit
clusvcadm -U ana
 


 

Integrating Prime Optical and the Prime Optical Integration Layer with Prime Central


Step 1 As the application user, shut down Prime Optical:

opticalctl stop
 

Step 2 Under the application home folder, change directories to the /bin directory:

cd /opt/CiscoTransportManagerServer/bin
 

Step 3 Run the CPOIntegrator.sh script:

CPOIntegrator.sh -a prop-file server-hostname service-name db-user db-password port-number
 

For example:

CPOIntegrator.sh -a DMIntegrator.prop prime-server primedb primedba Test456@ 1521
 

Note The DMIntegrator.prop file is located in the /opt/CiscoTransportManagerserver/prime_integrator folder by default. (If you want to use a different properties file, you must indicate its complete path.)

Step 4 Start Prime Optical:

opticalctl start
 


 

Integrating Prime Performance Manager with Prime Central


Tip Integrate Prime Performance Manager with Prime Central after you integrate the Fault Management component and each instance of Prime Network with Prime Central.


Step 1 As the root user, log into the Prime Performance Manager gateway server and navigate to the Prime-Performance-Manager-gateway-installation-directory /bin directory.

Step 2 Enter:

./ppm primecentralintegration
 

Step 3 Enter the appropriate responses at the prompts:

    • Database Host—Enter the Prime Central database server hostname or IP address.
    • Database SID [primedb]—Enter the Prime Central database service name, which is primedb by default.
    • Database User [primedba]—Enter the Prime Central database username, which is primedba by default.
    • Database Password [*****]—Enter the Prime Central database user password; for example, Test456@ .
    • Database Port [1521]—Enter the Prime Central database port number, which is 1521 by default.

Step 4 Restart Prime Performance Manager for the changes to take effect.

Step 5 As the primeusr user, log into the Prime Central integration layer and restart it:

a. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

itgctl list

 

b. Note down the ID of the integration layer instance with the “PC-IL-CORE” profile.

c. Stop the PC-IL-CORE profile instance:

itgctl stop ID

 

d. Restart the integration layer:

itgctl start ID

 

Step 6 If you are reintegrating Prime Performance Manager after a previous integration, you must unregister it from Prime Central before you reintegrate it. See Unregistering Prime Performance Manager.

Step 7 After Prime Performance Manager is integrated with Prime Central, use the Prime Central portal to create new users. (Any users that existed before the integration are removed during the integration.)

Step 8 If you install a Prime Network instance after Prime Performance Manager is integrated with Prime Central, enter the following commands to integrate Prime Performance Manager with Prime Network:

/opt/CSCOppm-gw/bin/sgmInventoryImportUtility.sh -installCrossLaunchPoints
/opt/CSCOppm-gw/bin/sgmInventoryImportUtility.sh -installTrapSupport
 

Step 9 If Prime Performance Manager is configured to send alarms directly to the Prime Central Fault Management server, verify that an upstream OSS host is configured correctly in the System Event Editor of Prime Performance Manager.

Step 10 If you install the Fault Management component after Prime Performance Manager is integrated with Prime Central, enter the following command and select Fault Management as the trap destination to integrate it with Prime Performance Manager:

./ppm setpctrapdestination
 

For example:

# ./ppm setpctrapdestination
 
Trap destinations registered with Prime Central:
 
1. Prime Central Fault Management (hostname) 2. Prime Network (hostname-1) 3. Prime Network (hostname-2) 4. Prime Network (hostname-3)
 
Enter trap destination: [1, 2, 3, 4] 1, 2, 3
 


 

Integrating Prime Provisioning with Prime Central


Step 1 As the application user, shut down Prime Provisioning.

Step 2 Verify that the JAVA_HOME environment variable points to Java 1.6, which the DMIntegrator.sh script requires.

Step 3 Verify that the /usr/bin/scp secure copy tool is present on the Prime Provisioning server.

Step 4 Under the Prime Provisioning home folder, create a prime_integrator folder (if it does not already exist) and copy the following files to it:

    • DMIntegrator.prop
    • DMIntegrator.sh
    • DMIntegrator.tar

Step 5 Verify that permissions are correct.

Step 6 Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

$ ./DMIntegrator.sh
 

Step 7 As the primeusr user, log into the Prime Central integration layer and restart it:

a. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

itgctl list

 

b. Note down the ID of the integration layer instance with the “PC-IL-CORE” profile.

c. Stop the PC-IL-CORE profile instance:

itgctl stop ID

 

d. Restart the integration layer:

itgctl start ID

 

Step 8 If you are reintegrating Prime Provisioning with a different COM-URI, you must restart the Prime Central portal. (The COM-URI is the Prime Provisioning identifier and can be found in the Prime Central portal > Suite Monitoring portlet.) To do so, log into the Prime Central portal as the primeusr user and enter:

portalctl stop
portalctl start
 

Step 9 Start Prime Provisioning.

Step 10 After Prime Provisioning is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.


 

Upgrading Prime Central

You can upgrade from:

  • Prime Central 1.1 to 1.2
  • Prime Central 1.1.0.1 to 1.2
  • Prime Central 1.1.0.2 to 1.2

The upgrade to Prime Central 1.2 does the following automatically:

  • Backs up the embedded database, if present.
  • Stops the Prime Central portal and Prime Central integration layer.
  • Backs up the previous installation directory.
  • Upgrades the Prime Central portal and Prime Central integration layer.
  • Starts the Prime Central portal and Prime Central integration layer.

Note You must upgrade Prime Central before upgrading the Fault Management component.

Before You Begin

  • If you are using an external database, you must back it up manually. You must also create the following directory under ORACLE_HOME for the PSI integration, and make the owner oracle:
ORACLE_HOME/oradata/PSI
 
  • If you are using an embedded (local or remote) database, it is recommended (but not required) that you back it up manually before upgrading.
  • You must upgrade the server with Red Hat Enterprise Linux 5.5 to 5.8 before upgrading Prime Central.
  • The upgrade steps are the same for both single- and dual-server setups. In a dual-server setup, complete the following procedure on the Prime Central portal server first; then, repeat the procedure on the Prime Central integration layer server.

Upgrading to Prime Central 1.2


Step 1 Use one of the following to connect to the server where you want to upgrade Prime Central:

Step 2 As the root user, launch a terminal on the server where you want to upgrade Prime Central. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

If you are using X server, continue to Step 3.

If you are using VNC, skip to Step 5.

Step 3 Set the DISPLAY variable:

setenv DISPLAY hostname-or-IP-address:0.0
 

Step 4 Verify that the display is set correctly:

echo $DISPLAY
 

In the command output, you should see:

hostname-or-IP-address:0.0
 

Step 5 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the local folder where the drive is mounted.

Step 6 Change file permissions and ownership:

chmod 755 *
 

Step 7 Begin the upgrade:

./primecentral_v1.2.bin
 

Step 8 In the Welcome window, click Next .

If you are upgrading to Prime Central 1.2 on the same server where the earlier Prime Central version was installed, the following dialog box is displayed:

A previous installation exists on the system.
 

Step 9 Click OK .

If you are using an external database, the following dialog box is displayed:

You must back up the database manually before continuing.
 

Step 10 Confirm that your database backup succeeded; then, click Continue .

Step 11 In the Advanced Configuration window, make any desired changes to the port numbers, timeout value, or reconnect delay; then, click Install . (For port descriptions, see Table 3 .)

Step 12 In the Upgrade Complete window, click Done .

It might take 20 to 30 minutes or longer to complete the upgrade, depending on your system performance and whether you are using an embedded or external database.

The log files are available in installation-directory /install/logs and installation-directory /upgrade/1.1.0.0-1.2.0.0/upgrade.log.


 

Upgrading Prime Central Silently

You can upgrade Prime Central without user interaction. In a silent upgrade, no messages or prompts appear on-screen, and interactive dialogs are not displayed. Information and answers that you would normally provide are read from a properties file.

A silent upgrade allows for unattended product upgrades based on the values that are provided in the properties file.


Note The silent upgrade steps are the same for both single- and dual-server setups. In a dual-server setup, complete the following procedure on the Prime Central portal server first; then, repeat the procedure on the Prime Central integration layer server.


Step 1 As the root user, launch a terminal on the server where you want to silently upgrade to Prime Central 1.2. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

Step 2 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the local folder where the drive is mounted.

Step 3 Change file permissions:

chmod 755 *
 

Step 4 If you are upgrading an external database, add the following property (with the oracle home directory as the value) to the install.properties file:

SUITEFW_EMBEDDED_ORACLE_HOME=/export/home/oracle
 

Step 5 Begin the silent upgrade:

./primecentral_v1.2.bin -i silent -f install.properties
 

Step 6 (Optional) The silent upgrade uses the following default values for the request timeout, 3GPP port, alarm management port, and reconnect delay. You can change these values as desired:

SUITEFW_IL_REQUEST_TIMEOUT=135000
SUITEFW_IL_3GPP_PORT=9220
SUITEFW_IL_ALARM_MGMT_PORT=9020
SUITEFW_IL_RECONNECT_DELAY=10
 

When the silent upgrade completes, the log files are available in installation-directory /install/logs and installation-directory /upgrade/1.1.0.0-1.2.0.0/upgrade.log.


 

Verifying the Upgrade

To verify the upgrade, log into the Prime Central server as the primeusr user and enter:

version
 

The output should show:

# version
Running Integration Layer(PC-IL-CORE,PC-IL-JMS) + Platform (v 1.2.0.0 (build number)) with Patch(0.0.0.0)

Upgrading to Prime Central Fault Management 1.2

You can upgrade from:

  • Prime Central Fault Management 1.1 to 1.2
  • Prime Central Fault Management 1.1.0.1 to 1.2
  • Prime Central Fault Management 1.1.0.2 to 1.2

For Prime Central Fault Management servers that just meet the minimum server requirements specified in this guide, you must update the timeout value in the soap.client.props file before upgrading. Do the following:

1. Enter the following commands:

# su – primeusr
# vim ~/faultmgmt/tipv2/profiles/TIPProfile/properties/soap.client.props
 

2. Change the value of the com.ibm.SOAP.requestTimeout parameter to 3600 .


Step 1 Move (or remove) all *.log files from the /tmp folder.

Step 2 Use one of the following to connect to the server where you want to upgrade Prime Central Fault Management:

Step 3 As the root user, launch a terminal on the server where you want to upgrade Prime Central Fault Management. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

If you are using X server, continue to Step 4.

If you are using VNC, skip to Step 6.

Step 4 Set the DISPLAY variable:

setenv DISPLAY hostname-or-IP-address:0.0
 

Step 5 Verify that the display is set correctly:

echo $DISPLAY
 

In the command output, you should see:

hostname-or-IP-address:0.0
 

Step 6 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the local folder where the drive is mounted.

Step 7 Change file permissions and ownership:

chmod 755 *
 

Step 8 From the Fault Management folder, begin the upgrade:

./primefm_v1.2.bin
 

Step 9 In the Introduction window, click Next .

If you are upgrading to Prime Central Fault Management 1.2 on the same server where 1.1 was installed, the following dialog box is displayed:

A previous installation exists on the system.
 

Step 10 Click OK to proceed with the upgrade.

Step 11 Verify that the information in the Pre-Installation Summary window is correct; then, click Install .

The upgrade process is automatic and requires no user input.

Step 12 In the Upgrade Complete window, click Done .

It might take 90 minutes or longer to upgrade Prime Central Fault Management, depending on your system performance.

The log files are available in the installation-directory /faultmgmt/upgrade/1.1.0.0-1.2.0.0/logs folder.

Step 13 During the upgrade, if any components fail to start, do the following as the primeusr user:

a. Enter the fmctl status command to determine whether all components are up and running.

b. Restart Prime Central Fault Management:

fmctl stop

fmctl start

 


 

Upgrading Prime Central Fault Management Silently

You can upgrade Prime Central Fault Management without user interaction. In a silent upgrade, no messages or prompts appear on-screen, and interactive dialogs are not displayed. Information and answers that you would normally provide are read from a properties file.


Step 1 As the root user, launch a terminal on the server where you want to silently upgrade to Prime Central Fault Management 1.2. (If you logged in as a nonroot user, enter the su - command to become the root user.)

The C shell (csh) is recommended. To start the C shell, enter:

/bin/csh
 

Step 2 Insert the Cisco Prime Central 1.2 USB drive into the USB port and navigate to the local folder where the drive is mounted.

Step 3 Change file permissions:

chmod 755 *
 

Step 4 From the Fault Management folder, begin the silent upgrade:

./primefm_v1.2.bin -i silent -f fm-install.properties
 

For example, if your silent properties file is named PrimeFM_install.properties, enter:

./primefm_v1.2.bin -i silent -f PrimeFM_install.properties
 

The silent upgrade log files are available in the installation-directory /faultmgmt/upgrade/1.1.0.0-1.2.0.0/logs folder.

Step 5 During the upgrade, if any components fail to start, do the following as the primeusr user:

a. Enter the fmctl status command to determine whether all components are up and running.

b. Restart Prime Central Fault Management:

fmctl stop

fmctl start

 


 

Uninstalling Prime Central

You can use the GUI to uninstall the various Prime Central components, or you can uninstall them silently.

Uninstalling Prime Central in an Embedded Database Configuration

If you installed an embedded database, it is uninstalled automatically when you uninstall Prime Central.

The following procedure removes all files from the installation directory. This procedure also removes the database and its contents. Database backups are not removed if they reside in a different directory from the installation directory.

If you upgrade Prime Central and then uninstall it, the /opt/primecentral_backup_1.2.0.0 folder is removed during uninstallation.


Note If you installed the Fault Management component in the same directory as Prime Central, you must uninstall the Fault Management component before uninstalling Prime Central. See Uninstalling Prime Central Fault Management.


Step 1 Depending on how you installed Prime Central, use one of the following to connect to the server where you want to uninstall Prime Central:

Step 2 As the root user, launch a terminal on the server where you want to uninstall Prime Central. (If you logged in previously as a nonroot user, enter the su – command to become the root user.)

Step 3 Enter:

cd /var/adm/cisco/uninstall/Uninstall_Prime_Central/
./Uninstall_Prime_Central
 

Step 4 Verify that the information in the Uninstall Prime Central window is correct; then, click Uninstall .

Step 5 In the Uninstall Complete window, click Done .

The uninstallation log files are available at /var/adm/cisco/uninstall/UNINSTALL_LOG_ time-stamp .


 

Uninstalling Prime Central in an External Database Configuration


Note • In a dual-server setup, you must uninstall the Prime Central integration layer before uninstalling the Prime Central portal. Perform the following steps on the integration layer server first; then, repeat them on the Prime Central portal server.

    • If you installed the Fault Management component in the same directory as Prime Central, you must uninstall the Fault Management component before uninstalling Prime Central. See Uninstalling Prime Central Fault Management.

 


Step 1 Depending on how you installed Prime Central, use one of the following to connect to the server where you want to uninstall Prime Central:

Step 2 As the root user, launch a terminal on the server where you want to uninstall Prime Central. (If you logged in previously as a nonroot user, enter the su – command to become the root user.)

Step 3 Enter:

cd /var/adm/cisco/uninstall/Uninstall_Prime_Central/
./Uninstall_Prime_Central
 

Step 4 Verify that the information in the Uninstall Prime Central window is correct; then, click Next .

Step 5 In the Database Information window, enter the database system password and confirm the following information for your preinstalled Oracle database server. Except for the password, the values are prepopulated with the information that you entered during installation:

    • Host IP address—The default is the IP address of the database server.
    • Port—The default is 1521.
    • Service name—The SID of the database server.
    • System user—The database system username.
    • System password—Enter the database system password.

Step 6 Click Uninstall .

Step 7 In the Uninstall Complete window, click Done .

The uninstallation log files are available at /var/adm/cisco/uninstall/UNINSTALL_LOG_ time-stamp .


 

Uninstalling Prime Central Silently


Step 1 Navigate to the /var/adm/cisco/uninstall/Uninstall_Prime_Central directory.

The uninstall folder contains the installvariables.properties file.

Step 2 Run the silent uninstallation:

./Uninstall_Prime_Central
 

The uninstallation log files are available at /var/adm/cisco/uninstall/UNINSTALL_LOG_ time-stamp .


 

Uninstalling Prime Central Fault Management

When you uninstall the Fault Management component, its subcomponents (except for the backup folder) are also uninstalled.


Step 1 Depending on how you installed the Fault Management component, use one of the following to connect to the server where you want to uninstall Prime Central:

Step 2 As the root user, launch a terminal on the server where you want to uninstall Prime Central Fault Management. (If you logged in previously as a nonroot user, enter the su – command to become the root user.)

Step 3 Enter:

cd /var/adm/cisco/uninstall/Uninstall_Prime_Central_Fault_Management
./Uninstall_Prime_Central_Fault_Management
 

Step 4 Verify that the information in the Uninstall Prime Central Fault Management window is correct; then, click Uninstall .

Step 5 In the Uninstall Complete window, click Done .

The uninstallation log files are available at /var/adm/cisco/uninstall/PrimeFM-uninstall.log- time-stamp .

Step 6 If the Fault Management uninstallation hangs without creating a log file, the RSA key entry might be missing from the ~/.ssh/known_hosts file. Do the following to generate the RSA key and add it to the server:

a. As the root user, enter the following command, where IP-address and hostname are the IP address and hostname of the server where Prime Central Fault Management is installed:

ssh_key=' /usr/bin/ssh-keyscan -t rsa IP-address hostname '

 

b. To add the RSA key entry to the ~/.ssh/known_hosts file, enter:

echo "$ssh_key" >> ~/.ssh/known_hosts

Step 7 Remove Prime Central Fault Management from the Prime Central portal:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring.

b. In the Suite Monitoring portlet, click the Prime Central tab.

c. Click the Prime Central Fault Management radio button and click Remove.

d. At the confirmation prompt, click OK.

Step 8 As the primeusr user, log into the Prime Central integration layer and restart it:

itgctl stop
itgctl start
 


 

Uninstalling Prime Central Fault Management Silently


Step 1 Navigate to the /var/adm/cisco/uninstall/Uninstall_Prime_Central_Fault_Management directory.

The uninstall folder contains the installvariables.properties file.

Step 2 Run the silent uninstallation:

./Uninstall_Prime_Central_Fault_Management -i silent
 

The uninstallation log files are available at /var/adm/cisco/uninstall/PrimeFM-uninstall.log- time-stamp .

Step 3 Remove Prime Central Fault Management from the Prime Central portal:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring.

b. In the Suite Monitoring portlet, click the Prime Central tab.

c. Click the Prime Central Fault Management radio button and click Remove.

d. At the confirmation prompt, click OK.

Step 4 As the primeusr user, log into the Prime Central integration layer and restart it:

itgctl stop
itgctl start
 


 

Unregistering an Application from Prime Central

You can completely unregister an application from Prime Central.


Note • To reintegrate an application with Prime Central, see Configuring Applications as Suite Components.

    • When you unregister an application from Prime Central, the application loses all users that were created in suite mode.
    • Unregistering an application from Prime Central does not return it to standalone mode.

 

Unregistering Cisco InTracer


Step 1 On the Cisco InTracer server, do the following:

a. Navigate to the directory where the Cisco InTracer server is installed.

b. Stop the Cisco InTracer server:

./ipmssys stop

 

c. Enter the following commands, where Cisco-InTracer-installation-directory is the directory where the Cisco InTracer server is installed:

rm -rf Cisco-InTracer-installation-directory /prime_local

rm -f Cisco-InTracer-installation-directory /prime_integrator/dmid.xml

 

Step 2 On the Prime Central portal, do the following:

a. As the primeusr user, log into the Prime Central server with the primeusr password that you specified during installation.

b. Change directories to the installation-directory /install/scripts folder.

c. Enter:

./dmRemoveUtil

 

d. At the following prompts, enter your Prime Central administrative username and password:

Enter Prime Central admin username:

Enter Prime Central admin user password:

 

e. At the following prompt, enter the unique Cisco InTracer ID, which is available in the Cisco-InTracer-installation-directory /prime_integrator/dmid.xml file:

Enter ID of the DM to be deleted:

 

For example, if the Cisco InTracer ID is cit://cit:4 , the script usage is as follows:

primeusr@prime-dev= [~/install/scripts]# ./dmRemoveUtil

Enter Prime Central admin username:

centraladmin

Enter Prime Central admin user password:

Enter ID of the DM to be deleted:

4

 


Note The dmRemoveUtil script output is available in the installation-directory/install/logs/dmRemoveUtil.log file.

Step 3 As the primeusr user, log into the Prime Central integration layer and restart it:

a. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

itgctl list

 

b. Note down the ID of the integration layer instance with the “PC-IL-CORE” profile.

c. Stop the PC-IL-CORE profile instance:

itgctl stop ID

 

d. Restart the integration layer:

itgctl start ID

 


 

Unregistering Prime Network


Step 1 On the Prime Network gateway server, do the following:

a. Stop the Prime Network gateway server:

networkctl stop

 

b. Enter:

cd $PRIME_NETWORK_HOME/Main ; runRegTool.sh localhost set suite-integ/enabled false

cd $PRIME_NETWORK_HOME/Main ; runRegTool.sh localhost set authentication/loginMethod/implClass <old implClass; for example, com.sheer.metromission.authentication2.LocalAuthenticationService>

cd $PRIME_NETWORK_HOME/Main ; runRegTool.sh localhost get avm11/services/authentication

 

c. If the output is not null, enter:

cd $PRIME_NETWORK_HOME/Main ; runRegTool.sh localhost set avm11/services/authentication/loginMethod/implClass <old implClass; for example, com.sheer.metromission.authentication2.LocalAuthenticationService>

 

d. Copy the following files to the $PRIME_NETWORK_HOME/Main/registry/ConfigurationFiles/127.0.0.1 directory:

$PRIME_NETWORK_HOME/Main/registry/suite-integ.xml

$PRIME_NETWORK_HOME/Main/registry/authentication.xml

$PRIME_NETWORK_HOME/Main/registry/avm11.xml

e. Enter:

rm -rf $PRIME_NETWORK_HOME/prime_local

rm -f $PRIME_NETWORK_HOME/prime_integrator/dmid.xml

 

f. Start Prime Network:

cd $PRIME_NETWORK_HOME/Main

networkctl start

 

Step 2 On the Prime Central portal, do the following:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring .

b. In the Suite Monitoring portlet, click the Applications tab.

c. Click the Prime Network radio button and click Remove .

d. At the confirmation prompt, click OK .

e. Remove the following directories from the ~/SHARED/cxl/jnlps directory:

administrationnet <application-ID>

crosslaunchernet <application-ID>

dcdebuggernet <application-ID>

eventsnet <application-ID>

regeditnet <application-ID>

servicedesignernet <application-ID>

visionnet <application-ID>

workflownet <application-ID>


Note <application-ID> is the number that identifies the application. Each directory contains a jnlp.xml file. As defined in netnet.xml, if additional applications are defined in netnet, the preceding list changes.

f. Remove the following file from the ~/SHARED/cxl/jnlps directory:

netnet <application-ID> .xml

Step 3 As the primeusr user, log into the Prime Central integration layer and restart it:

itgctl stop
itgctl start
 


 

Unregistering the Prime Network Integration Layer

In a suite environment, it is not recommended to unregister the Prime Network integration layer. However, if you must unregister (for troubleshooting, for example), complete the following steps:


Step 1 Remove the Prime Network integration layer from the Prime Central portal:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring .

b. In the Suite Monitoring portlet, click the Prime Central tab.

c. Click the Prime Network Integration Layer radio button and click Delete .

d. At the confirmation prompt, click OK .

Step 2 Disable the Prime Network integration layer health checker:

a. On the Prime Network gateway server, enter:

vi $PRIME_NETWORK_HOME/local/cron/every_3_minutes.cmd

 

b. In the cron job, comment out the following line:

cd $PRIME_NETWORK_HOME/local/scripts/integration_layer ; perl il_watchdog.pl

 

Step 3 Stop the Prime Network integration layer:

itgctl stop
 

Step 4 Delete the dmid.xml file:

rm $PRIMEHOME/integration/dmid.xml
 

Unregistering the Prime Network integration layer is a temporary measure. When troubleshooting is complete, reintegrate the Prime Central integration layer to restore normal operation in a suite environment and allow other applications to resume communication with Prime Network.


 

Unregistering Prime Optical


Step 1 On the Prime Optical server, enter:

opticalctl stop
 

Step 2 On the Prime Central portal, do the following:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring .

b. In the Suite Monitoring portlet, click the Applications tab.

c. Click the Prime Optical radio button and click Remove .

d. At the confirmation prompt, click OK .

e. Enter the following commands, where <application-ID> is the number that identifies the application:

rm -f ~/SHARED/cxl/jnlps/optopt <application-ID> .xml

rm -rf ~/SHARED/cxl/jnlps/optopt <application-ID>

 

Step 3 As the primeusr user, log into the Prime Central integration layer and restart it:

itgctl stop
itgctl start
 


 

Unregistering the Prime Optical Integration Layer


Step 1 From the Prime Central menu, choose Administration > System > Suite Monitoring .

Step 2 In the Suite Monitoring portlet, click the Prime Central tab.

Step 3 Click the Prime Optical Integration Layer radio button and click Delete .

Step 4 At the confirmation prompt, click OK .


 

Unregistering Prime Performance Manager


Step 1 As the root user, log into the Prime Performance Manager gateway server and navigate to the Prime-Performance-Manager-gateway-installation-directory /bin directory.

Step 2 Enter:

./ppm primecentralintegration remove
 

Step 3 Restart Prime Performance Manager for the changes to take effect.

Step 4 On the Prime Central portal, do the following:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring .

b. In the Suite Monitoring portlet, click the Applications tab.

c. Click the Prime Performance Manager radio button and click Remove .

d. At the confirmation prompt, click OK .

Step 5 As the primeusr user, log into the Prime Central integration layer and restart it:

a. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

itgctl list

 

b. Note down the ID of the integration layer instance with the “PC-IL-CORE” profile.

c. Stop the PC-IL-CORE profile instance:

itgctl stop ID

 

d. Restart the integration layer:

itgctl start ID

 


 

Unregistering Prime Provisioning


Step 1 On the Prime Central portal, do the following:

a. From the Prime Central menu, choose Administration > System > Suite Monitoring .

b. In the Suite Monitoring portlet, click the Applications tab.

c. Click the Prime Provisioning radio button and click Remove .

d. At the confirmation prompt, click OK .

e. Enter:

rm -rf ~/XMP_Platform/tomcat-7.0.23/webapps/srsummary-portlet

rm -rf ~/XMP_Platform/tomcat-7.0.23/webapps/devicesrcount-portlet

 

Step 2 Navigate to the Prime Provisioning installation directory and restart the Prime Provisioning server:

./prime.sh stop
./prime.sh start

 

Step 3 As the primeusr user, log into the Prime Central integration layer and restart it:

a. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

itgctl list

 

b. Note down the ID of the integration layer instance with the “PC-IL-CORE” profile.

c. Stop the PC-IL-CORE profile instance:

itgctl stop ID

 

d. Restart the integration layer:

itgctl start ID

 


 

Next Steps

You can start and stop the Prime Central components and set up a backup schedule.

Starting and Stopping the Prime Central Components

As the primeusr user, enter the commands shown in Table 9 to start and stop the various Prime Central components.

 

Table 9 Commands to Start, Stop, and Restart the Prime Central Components

Action
Command
Prime Central Portal

Start

portalctl start

Note If the Prime Central server reboots, you must start the Prime Central portal and Prime Central integration layer manually by using the portalctl start and itgctl start commands.

Stop

portalctl stop

Restart

portalctl stop

portalctl start

Note If you restart Oracle, you must restart the Prime Central portal.

Obtain status

portalctl status

Enable debug logging

portalctl start log

Note The log location is $XMP_HOME/logs/startup.log.

Prime Central Integration Layer

Start

itgctl start

Stop

itgctl stop

Restart

itgctl stop

itgctl start

Note If you restart Oracle, you must restart the Prime Central integration layer.

Obtain status

itgctl status

List instances

itgctl list

Note This command lists all running integration layer instances and their profiles; for example, “PC-IL-CORE.”

Fault Management

Start

fmctl start

Stop

fmctl stop

Obtain status

fmctl status

Backing Up and Restoring the Embedded Database

As the primeusr user, enter the commands shown in Table 10 to back up and restore the Prime Central embedded database.

 

Table 10 Commands to Back Up and Restore the Database

Action
Command

Start

emdbctl --start

Stop

emdbctl --stop

Enable backups

emdbctl --enable_backup

Back up the database

emdbctl --backup

Restore the database

emdbctl --restore

Obtain database status

emdbctl --db_status

Note the following:

  • Shut down the Prime Central portal and the Prime Central integration layer before restoring the database. Restart them after the database restore is complete.
  • By default, the option to enable backups is checked during installation. If you uncheck it during installation but later decide to enable automatic backups, you must enter the emdbctl --enable_backup command to do so.
  • An automatic backup runs daily at 4:00 a.m. A full backup runs every Saturday; incremental backups run on all other days.
  • By default, Prime Central saves eight database backups to ORACLE_HOME/backup. Your system administrator must back up the database backups and archive directories to tape daily.
  • The emdbctl --restore command prompts you to enter a date and time to restore a database backup. The format is MM - DD - YYYY HH : MI ; for example, 07-30-2013 03:34. If you enter a date in the wrong format, or if the backup cannot be restored for the date and time entered, the database will instead be restored to the most recent possible date and time.

Backing Up and Restoring the Fault Management Database

Prime Central Fault Management alarms are stored in the Fault Management database. These same alarms are also forwarded and stored on the Prime Central Oracle database. Both the Prime Central and Fault Management databases are automatically backed up daily. By default, the Fault Management backups are saved in $NCHOME/omnibus/backup/NCOMS/. You can create a cron job that periodically copies the backups to an offsite location.

If a manual backup is required, you can back up and restore the data manually.

Backing Up the Fault Management Database Manually


Step 1 Log into the Fault Management server and then stop it:

fmctl stop
 

Step 2 Choose a backup location within the primeusr directory structure (for example, ~/omnibus-backup/):

mkdir -p backup-location/db
cp -r $NCHOME/omnibus/db/NCOMS/* backup-location/db
 

Step 3 Back up the miscellaneous files, if they were changed manually:

mkdir -p backup-location/misc
cp -r $NCHOME/omnibus/etc backup-location/misc
 

Step 4 Back up the log files:

cp -r $NCHOME/omnibus/log backup-location/misc
 

Step 5 Start the Fault Management server:

fmctl start
 


 

Restoring the Fault Management Database Manually


Step 1 Stop the Fault Management server:

fmctl stop
 

Step 2 Restore the previously saved database files:

rm -rf $NCHOME/omnibus/db/NCOMS/*
cp backup-location/db/* $NCHOME/omnibus/db/NCOMS
 

Step 3 Restore the miscellaneous files, if they were backed up:

cp -r backup-location/misc/etc $NCHOME/omnibus

Tip If you receive any “permission denied” errors, you can safely ignore them.

Step 4 Start the Fault Management server:

fmctl start