Installing a Cisco Prime Network Gateway Using an External Oracle Database
This chapter provides procedures to install a single Cisco Prime Network gateway that will use the external Oracle database. Before you start this chapter, you must complete Chapter 4 "Creating and Configuring an Oracle Database." To install Cisco Prime Network with an embedded database, go to Chapter 3 "Installing the Cisco Prime Network 3.8 Gateway With an Embedded Database."
Note•If you are upgrading to Cisco Prime Network 3.8 from an earlier version, the installation is different from installing Cisco Prime Network for the first time. See Chapter 12 "Upgrading to Cisco Prime Network 3.8."
•For information on redundancy or multiple installations of the gateway, contact your Cisco account representative.
This chapter includes:
•Before You Begin
•Cisco Prime Network Gateway Installation Overview
•Installing the Cisco Prime Network Gateway
•Changes Resulting from the Installation
•Verifying the Cisco Prime Network Gateway Installation
Before You Begin
Note If you are installing Cisco Prime Network on a gateway that has a previous version of Cisco Prime Network installed, you must delete all the files that belong to the network-user (for example, network38) from /tmp directory before you begin the Cisco Prime Network 3.8 installation. To locate the list of files, enter:
Then, to delete each file in the list, enter:
Before starting the gateway installation, verify that:
•The "Disk 1: New Install" DVD is available. (See Installation DVDs.)
•The servers that are going to be installed comply with the minimum system requirements specified in Chapter 1 "Installation Prerequisites."
•The customer-supplied Oracle database is installed on the gateway. For more information, see Chapter 4 "Creating and Configuring an Oracle Database."
•The / (root) directory has at least 1 GB of disk space available.
•The Cisco Prime Network installation directory has at least 5 GB of disk space available. By default, Cisco Prime Network is installed in /export/home.
•The /tmp directory has at least 100 MB of disk space available.
•The network-user home directory is not mounted directly.
•You are about to install the correct Cisco Prime Network version and build. Enter the ./install.pl -version command, which returns the following output:
–Build date and time
–Version and build number
Cisco Prime Network install version 3.8-874, built on Thu Apr 1 05:34:03 IDT 2010
BID: SOL_NETWORK3.8_IL_20100401_0504 BST: dev.ana3.8 BU: cwadmin
Cisco Prime Network Gateway Installation Overview
Figure 7-1 presents the gateway installation workflow and the tasks in the order in which they should be performed.
Figure 7-1 Cisco Prime Network Gateway Installation Workflow
1. Install the Cisco Prime Networkgateway. See Installing the Cisco Prime Network Gateway.
2. Launch the gateway. See Launching the Gateway.
3. Verify the gateway installation. See Verifying the Cisco Prime Network Gateway Processes.
4. Install the Cisco Prime Network management tool. See Changes Resulting from the Installation.
Note Only a user with root privileges on the UNIX system can install the gateway.
Cisco Prime Network Users and Passwords
When you run the Cisco Prime Network configuration script (network-conf), the following user prompts are displayed:
•network-user—The Cisco Prime Network user. This user-defined user is created at installation and used to manage Cisco Prime Network during and after the installation.
•Root password—The UNIX root password used to set the time server on the gateway and the units.
•bosenable, bosconfig, and bosusermngr password—The three login levels defined to connect to the Cisco Prime Network shell.
•Apache server username and password—User-defined account for connecting to the Cisco Prime Network web-based diagnostics tool. The tool provides the operational status of gateways, units, and individual AVMs, including Java heap, dropped messages, CPU usage, and other status information.
Note The network-user and password is defined during installation. The default password for root, bosenable, bosconfig, bosusermngr, and web monitoring users is set during installation. To change the password, see the Cisco Prime Network 3.8 Administrator Guide.
•Oracle sid—See Chapter 4 "Creating and Configuring an Oracle Database."
•Oracle admin username—The default value is system.
•Oracle admin password—Password for the database's administrator user.
•Location of the data files—Oracle data files' location. The Cisco Prime Network database data files should reside where all of the other data files are located. The location can be under the $ORACLE_HOME directory or under any other preallocated, mounted directory that has oracle:oinstall or oracle:dba permissions. Before installing Cisco Prime Network, confirm the absolute path and location of the Oracle data files with your database administrator.
•Oracle Listener port—TCP port number on which the Oracle Net listener listens for connections. The default port is 1521.
Installing the Cisco Prime Network Gateway
This procedure describes how to install the Cisco Prime Network gateway and the optional Change and Configuration Management component, which does not require a separate license.
Note•The server installation script checks for existing packages and removes them in a preinstallation phase.
•If you want to install Change and Configuration Management separately from the gateway installation, you can do so later using the setup_xmp_nccm.cmd command.
•Change and Configuration Management does not support encrypted databases. Change and Configuration Management can be installed on a Cisco Prime Network installation that uses an encrypted connection to the database, but the connection used by Change and Configuration Management will not be encrypted.
To install the Cisco Prime Network gateway:
Step 1 Verify that "Disk 1: New Install" is in the DVD drive.
Step 2 Open a Telnet or SSH session to the gateway and log in as the user root.
Step 3 Confirm that system requirements such as disk space are satisfied. For more information, see Hardware and Software Requirements.
Step 4 Back up and remove the old version of the gateway (if an older version exists).
Step 5 To change to the CD directory, enter:
Step 6 To install the Cisco Prime Network gateway, enter:
perl ./install.pl -user network-user
The username is the user-defined Cisco Prime Network OS user. The username must start with a letter and contain only the characters shown in brackets: [A-Z a-z 0-9 -]. For example, if the name of the user is network38, enter:
perl ./install.pl -user network38
The gateway is installed in the default directory /export/home/name.
To change the installation directory, add the -dir [desired directory] switch at the end of the perl ./install.pl -user name command; for example, perl install.pl -user network38 -dir /opt/network38.
The installation of the gateway starts. The installation procedure is automatic and requires no user input.
Note The installation might take a while. For information on the Cisco Prime Network environment created during installation, see "Folders Created in Cisco Prime Network."
The following output is displayed:
- writing verbose log to /var/adm/cisco/prime-network/logs/verbose-time-stamp
- writing log to /var/adm/cisco/prime-network/logs/install-log-time-stamp
Pre install verifications
- Checking for minimal swap file size [OK]
Note (Solaris only) If the verification check hangs at the preceding line, restart the Solaris picl service:
svcadm disable picl
svcadm enable picl
After the picl service restarts, rerun the install.pl script.
- Checking if root's ppid belongs to user network38 [OK]
- Validating disk space needed on root directory [OK]
- Checking if all needed OS components exist and are executable [OK]
- Checking machine's perl version [OK]
- Checking for old packages for backward compatability [NO]
- Checking if previous version of Prime Network is already installed [YES]
- Uninstalling setup on Prime Network user: network38
- Removing Prime Network's cronjobs [OK]
- Killing all unix user network38 processes [OK]
- Erasing user network38 using userdel -r [OK]
- Removing user network38 home directory [OK]
- Removing temporary files [OK]
- Disable service: svc:/system/udp2icmp:udp2icmp [OK]
- Disable service: svc:/system/redirectUdp162:redirectUdp162 [OK]
- Disable service: svc:/system/redirectUdp514:redirectUdp514 [OK]
- Removing user network38 from /etc/cron.d/cron.allow [OK]
- Removing webserver and ana_secured from /etc/hosts.allow [OK]
- Erasing scripts dir /var/adm/cisco/prime-network/scripts [OK]
- Erasing registry dir /var/adm/cisco/prime-network/reg/network38 [OK]
- Validating availability of ports. This might take some time. [OK]
- Checking if unix user network38 is taken [OK]
- Validating destination directory /export/home/network38
- Checking directory consistency [OK]
- Creating Prime Network's home directory [OK]
- Adding unix user network38 [OK]
- Adding unix user bos [OK]
- Checking for encapsulated data file [OK]
- Unpacking encapsulated data [OK]
- Making sure main files are in unix mode [OK]
- Setting files permissions [OK]
- Setting files owner [OK]
- Creating installation registry [OK]
- Generating /var/adm/cisco/prime-network/reg/network38/uninstall.pl [OK]
- Deploying OS independent components
- Deploying bos_commands [OK]
- Deploying clean_tmp [OK]
- Deploying os_dependent_cleaner [OK]
- Deploying resolve_home [OK]
- Deploying secure_daemon [OK]
- Deploying webserver [OK]
- Deploying solaris dependent components
- Deploying ActivePerl-126.96.36.1991-RAW [OK]
- Deploying embedded_oracle [OK]
- Deploying fetch_ssh_daemon [OK]
- Deploying java_link [OK]
- Deploying os_services [OK]
- Setting usermod for priv ports (Solaris) for user network38 [OK]
- Updating bos commands [OK]
Step 7 After the installation is complete, you will be prompted to configure Prime Network. Enter yes to continue to Step 13 or no to configure later using the network-conf command.
Installation completed, would you like to configure Prime Network now? (yes/no)?
Step 8 If you installed Cisco Prime Network on Linux, verify that ports are redirected by entering the following as the root user:
The result should contain the following rows:
REDIRECT udp -- anywhere anywhere udp dpt:snmptrap redir ports 1161
REDIRECT udp -- anywhere anywhere udp dpt:snmptrap redir ports 1162
REDIRECT udp -- anywhere anywhere udp dpt:syslog redir ports 1514
REDIRECT udp -- anywhere anywhere udp dpt:tftp redir ports 1069
If not, enter the following:
iptables -t nat -A PREROUTING -p udp --dport 161 -j REDIRECT --to-port 1161
iptables -t nat -A PREROUTING -p udp --dport 162 -j REDIRECT --to-port 1162
iptables -t nat -A PREROUTING -p udp --dport 514 -j REDIRECT --to-port 1514
iptables -t nat -A PREROUTING -p udp --dport 69 -j REDIRECT --to-port 1069
Step 9 network-conf requires a database system password to create database schemas. If you want to create the database schemas manually, complete Creating Cisco Prime Network 3.8 Database Schemas Manually before continuing to Step 10.
Step 10 To enable the network-user_admin user to run maintenance tasks—such as gathering statistics—on the other Cisco Prime Network database schemas, complete the following substeps:
a. As the Oracle UNIX user, use SQL*Plus to log into user sys as sysdba.
b. Enter one of the following commands:
–If the network-user_admin user does not exist, enter:
SQL> grant execute on dbms_lock to system with grant option;
–If the network-user_admin user already exists, enter:
SQL> grant execute on dbms_lock to network-user_admin with grant option;
c. Verify that your database contains the temporary TEMP tablespace, which is required by the new Prime Network admin database user. If this tablespace does not exist, you have two options:
–Create this TEMP tablespace.
–Manually add the new admin database user as described in Creating Cisco Prime Network 3.8 Database Schemas Manually.
Step 11 After logging in as the new user (network-user), enter the following command:
Note•The database and listener must be up before you run the network-conf script.
•Do not rerun the network-conf script after AVMs or units are added. Rerunning the network-conf script could cause problems with the Cisco Prime Network registry.
•The network-conf script creates:
–Three data files for each user tablespace (NETWORK_TABLESPACE, DWE_TABLESPACE, and EP_TABLESPACE) with an initial size of 1024 MB and auto-extend set to 256 MB.
–An additional data file for the network-user_admin user (ADMIN_TABLESPACE) with an initial size of 100 MB and auto-extend set to 100 MB. The maximum size is 500 MB.
–Three data files for temporary tablespaces with an initial size of 100 MB and auto-extend set to 5 MB.
Step 12 The first time you log in, you are prompted to change the default password. It is recommended that you do so. To change the default user password, enter:
where network-user is the operating system user account for the Cisco Prime Network application, created when Cisco Prime Network is installed.
Step 13 At the Prime Network Configuration Utility screen, choose Set machine as Prime Network gateway. Use the down arrow key to choose a machine as the gateway, then press Enter.
Prime Network Configuration Utility
1 Set machine as Prime Network unit.
2 Set machine as Prime Network gateway.
Step 14 The configuration utility configures the system by running various procedures; for example:
- Is NTP configured on this machine? (yes/no) [default yes]
- Writing log to /export/home/network38/Main/network-conf-time-stamp.log
- Killing all Java/Perl process belonging to user network38 [OK]
- Updating current time to /export/home/network38/Main/unix/define.sql [OK]
- Creating the system's property file (Main/.ana) [OK]
- Creating registry encryption key [OK]
- Setup is updating the configuration directories, this might take a while
- Extracting ~/Main/registry/templates/127.0.0.1.tar.gz [OK]
- Updating ~/Main/registry/ConfigurationFiles/127.0.0.1/mmvm.xml [OK]
- Updating xmls in directory ConfigurationFiles/127.0.0.1/ [OK]
- Cloning directory 127.0.0.1/ to 0.0.0.0/ [OK]
- Updating registry leaf baseavm/services/filesys/homedir [OK]
- Removing old SSH keys if exist
- GW SSH keys generated successfully.
a. You are prompted to enter the password for the OS root user (for example, admin):
- Enter the password for OS root user: password
b. The configuration utility extracts the contents of the ivne-drivers.tar file to the appropriate folder:
- Extracting ivne-drivers.tar into /export/home/network38/Main/drivers [OK]
c. You are prompted to set all Cisco Prime Network system built-in account passwords. Enter the requested password at each prompt:
+ Prime Network is installed with 5 built-in users (root, bosenable, bosconfig,
bosusermngr, web monitoring user) to be used for logging into the various system
You will now define a password for all built-in users. The password must:
- Contain at least eight alphanumeric characters.
- Contain both upper and lower case letters.
- Contain at least one number.
- Contain at least one special character.
- Not contain '@' or '/' or '!' or '()'
- Enter the password for all built-in users: password
- Enter the password again for verification: password
The password that you enter for the system root password will also be used as the database schemas password. The password must meet the specified requirements: it must be at least eight alphanumeric characters containing upper and lower case letters; it must contain one number and one special character; it cannot cannot contain `@', forward slash `/', exclamation `!' or bracket `( )' characters. If you enter a restricted characters, the installation will fail.
- Creating web monitoring tool user 'admin'.
Note The web monitoring tool user is created automatically with "admin" as the username. The password is the same as the root password.
You can change the passwords at a later stage - see Admin Guide.
d. You are prompted to enter the database details:
+ Prime Network can run with a pre-configured database or it can install the database
Would you like Prime Network to install the database? (yes,no) [default no]
+ Setup will now configure the Prime Network default schemas:
- Enter Oracle server IP address or host name: [Default: IP-address]
- Enter Oracle's admin username: [Default: system]
- Enter Oracle's admin password:
+ Would you like Prime Network to auto-configure the database? (yes/no) [Default: yes]
Note If you enter yes, the database is configured automatically with the following default values: port 1521, SID: MCDB, no encryption, and Prime Network-created users. The Event Processing (EP) schema uses these same values.
- Overwriting scheme netework38 tables
- Completed dropping 110 of 110 DB objects.
- Overwriting scheme network38_dwe tables
- Completed dropping 20 of 20 DB objects.
- Dropping network38_admin's DB objects
- Completed dropping 3 of 3 DB objects.
- creating Prime Network tables...
- creating admin database objects...
- Configuring the Event Processing (EP) schema
- Overwriting scheme network38_ep tables
- Completed dropping 5 of 5 DB objects.
e. The installer then installs the Change and Configuration Management application:
+ Prime Network is bundled with Configuration and Image Management runtime, setup will
now install the XMP platform and these components.
- Installing the XMP Platform. Please wait.
- Installing the Change and Configuration components. Please wait.
Checking for running servers.
00:00 Check complete. No servers running.
03:02 Done creating schema.
Getting Application Context
- Updating gateway bsm registry with Change and Configuration Management data
Note Installation of Change and Configuration Management will be aborted, if your Oracle account is locked during the installation process. You must unlock the account and then run the setup_xmp_nccm.cmd command to install the Configuration and Image Management components.
f. Cisco Prime Network 3.8 supports dual network interface cards (NICs). You are prompted to specify the NIC to use for Cisco Prime Network back-end services (such as transport, xmlrpc, and so on) for gateway-to-unit communication. Dual NICs let you isolate the northbound interface from the back-end interface. If your gateway uses dual NICs, select the back-end interface for gateway-to-unit communication.
+ Multiple network interfaces detected on host. Please select a single interface for
Prime Network backend services
Enter option: (1-2) [Default: 1 (IP-address-1) ]
+ Done setting license functional state tier to NAS
Unpacking the data stream to ana_nsa.tar...
Extracting tar file ana_nsa.tar...
Installing Carrier Ethernet Services for Gateway...
Prime Network Install directory is /export/home/network38
Installing service activation scripts...
Installing resource activation scripts...
Installing Prime Network Activation metadata...
Installing Prime Network Activation help...
Set up Prime Network Activation registries...
- Updating DM properties file.
g. The installer asks if Cisco Prime Network is installed as part of the Cisco Prime IP-NGN Suite:
+ Is Prime Network being installed as part of the Prime IP-NGN Suite?
If you answer yes, additional questions are displayed:
- Enter the Cisco Prime Central database server IP address:
- Enter the Cisco Prime Central database SID:
- Enter the Cisco Prime Central database username:
- Enter the Cisco Prime Central database password:
- Enter the Cisco Prime Central database port:
Provide the Cisco Prime Central database server IP address, SI, username, password and port. After providing this information, Cisco Prime Network will be launched in "suite mode." See the Cisco Prime Network Quick Install Guide for more information.
+ Log was written to /export/home/network38/Main/logs/network-conf-1309268033.log
+ Log was written to /export/home/network38/Main/network-conf-time-stamp.log
+ Done setting the machine as gateway.
+ Would you like to start Prime Network? (Y,N) [default Y]
The installation logs are available at /var/adm/cisco/network/logs/.
The configuration logs are available at ANAHOME/Main/.
Using a Remote Database for the Gateway Installation
The following example shows the database parameters for a remote database installation that uses an encrypted connection:
+ Setup will now ask for Oracle's parameters and admin credentials
- Would you like to connect to a remote Oracle server? (yes/no) [Default: no] yes
- Enter Oracle server IP address: IP-address
- Does your Database require encrypted connection? (yes/no) [Default: no] yes
- What type of encryption method would you like to use:
Enter option: (1-3) [Default: Required]
- What type of encryption algorithm would you like to use:
- Enter Oracle's listener port [Default: 1521] port-number
- Enter Oracle's SID: SID
- Enter Oracle's admin username: [Default: system] username
- Enter Oracle's admin password: password
- Enter the location of the data files: location; for example,
Creating Cisco Prime Network 3.8 Database Schemas Manually
Step 1 Log into the database as the system user.
Step 2 Enter the following commands to create the Cisco Prime Network 3.8 database schemas. You can choose any name for the usernames and filenames. The password must be identical for the schemas.
create tablespace network-user datafile 'file-location/network-user.dbf' size 1024M
autoextend on next 256M;
create temporary tablespace network-user_temp tempfile
'file-location/network-user_temp.dbf' size 100m autoextend on next 5m maxsize 2000m;
create user network-user identified by "default-password" default tablespace network-user
temporary tablespace network-user_temp;
grant connect to network-user;
grant resource to network-user;
grant SELECT_CATALOG_ROLE to network-user;
GRANT CREATE VIEW TO network-user WITH ADMIN OPTION;
create tablespace network-user_dwe datafile 'file-location/network-user_dwe.dbf' size
1024M autoextend on next 256M;
create temporary tablespace network-user_dwe_temp tempfile
'file-location/network-user_dwe_temp.dbf' size 100m autoextend on next 5m maxsize 2000m;
create user network-user_dwe identified by "default-password" default tablespace
network-user_dwe temporary tablespace network-user_dwe_temp;
grant connect to network-user_dwe;
grant resource to network-user_dwe;
grant SELECT_CATALOG_ROLE to network-user_dwe;
GRANT CREATE VIEW TO network-user_dwe WITH ADMIN OPTION;
create tablespace network-user_ep datafile 'file-location/network-user_ep.dbf' size 1024M
autoextend on next 256M;
create temporary tablespace network-user_ep_temp tempfile
'file-location/network-user_ep_temp.dbf' size 100m autoextend on next 5m maxsize 2000m;
create user network-user_ep identified by "default-password" default tablespace
network-user_ep temporary tablespace network-user_ep_temp;
grant connect to network-user_ep;
grant resource to network-user_ep;
grant SELECT_CATALOG_ROLE to network-user_ep;
GRANT CREATE VIEW TO network-user_ep WITH ADMIN OPTION;
create tablespace network-user_xmp datafile 'file-location/network-user_xmp.dbf' size
1024M autoextend on next 256M;
create temporary tablespace network-user_xmp_temp tempfile
'file-location/network-user_xmp_temp.dbf' size 100m autoextend on next 5m maxsize 2000m;
create user network-user_xmp identified by "default-password" default tablespace
network-user_xmp temporary tablespace network-user_xmp_temp;
grant connect to network-user_xmp;
grant resource to network-user_xmp;
grant SELECT_CATALOG_ROLE to network-user_xmp;
GRANT CREATE VIEW TO network-user_xmp WITH ADMIN OPTION;
create tablespace network-user_admin datafile 'file-location/network-user_admin.dbf' size
100M autoextend on next 100M maxsize 500m;
create user network-user_admin identified by "default-password" default tablespace
network-user_admin temporary tablespace network-user_temp profile default;
GRANT RESOURCE TO network-user_admin;
GRANT DBA TO network-user_admin;
GRANT CONNECT TO network-user_admin;
GRANT SELECT ANY DICTIONARY TO network-user_admin;
GRANT ANALYZE ANY TO network-user_admin;
GRANT SELECT ANY TABLE TO network-user_admin;
GRANT EXECUTE ON DBMS_LOCK TO network-user_admin WITH GRANT OPTION;
ALTER USER network-user_admin QUOTA UNLIMITED ON network-user_admin;
Updating the Database Host in the Registry for NAT
If you use network address translation (NAT) with the Cisco Prime Network Events client, update the database host in the Prime Network registry to contain the hostname instead of the IP address. Complete the following steps after the Cisco Prime Network 3.8 gateway installation is complete and the system is up and running.
Note If you already use a hostname instead of an IP address, you do not have to repeat this procedure.
Step 1 Before changing the hostname, verify that the Windows client workstations have the correct Domain Name System (DNS) mapping.
Step 2 From ~/Main, enter the following commands:
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/persistency/nodes/main/Host database-server-hostname
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/persistency/nodes/ep/Host database-server-hostname
Step 3 Enter the following command to restart the Cisco Prime Network system:
Launching the Gateway
You are ready to launch the gateway after you have installed the server system and the gateway software.
Step 1 You should already be logged into the gateway as network-user (where network-user is the operating system user account for the Cisco Prime Network application, created when Cisco Prime Network is installed). If not, enter:
Step 2 To launch the gateway, enter the initialization command:
The gateway begins loading. The process might take a while to complete.
Verifying the Cisco Prime Network Gateway Processes
The status command verifies that the following gateway processes are up and running:
•AVM 100—Prime Network Event Collector (AEC) process.
•AVM 0—High availability/switch process.
•AVM 11—The database connection. When the database operates normally, AVM 11 is up and running. If there are any database problems, AVM 11 is down.
•AVM 25—Event persistence.
•AVM 77—Change and Configuration Management process (if installed).
•AVM 83—Internal use; used as a TFTP server by Change and Configuration Management.
•AVM 84—Report management.
•AVM 99—Management process.
•webserver daemon—Client connection process.
•secured connectivity daemon.
To check the status of all processes and daemons, enter:
The output lists all processes. For each AVM process that is checked, the status command displays, in brackets, the number of exceptions found in the total number of log file lines for that process. For example, the information for AVM 0 is [OK 0/39]; that is, 0 exceptions in the 39 log file lines that were checked:
.-= Welcome to server-name, running Cisco Prime Network gateway (v3.8 (build number)) =-.
+ Checking for services integrity:
- Checking if host's time server is up and running [OK]
- Checking if webserver daemon is up and running [OK]
- Checking if secured connectivity daemon is up and running [OK]
- Checking XMP runtime DM [UP]
+ Detected AVM99 is up, checking AVMs
- Checking for AVM83's status [OK 0/22]
- Checking for AVM0's status [OK 0/39]
- Checking for AVM100's status [OK 0/119]
- Checking for AVM25's status [OK 0/28]
- Checking for AVM11's status [OK 1/141]
- Checking for AVM84's status [OK 0/29]
Changes Resulting from the Installation
The installation script makes the following changes on the Cisco Prime Network gateway:
•Environment Variables Defined
Environment Variables Defined
The installation script automatically defines the environment variables listed in Table 7-1.
Table 7-1 Environment Variables Defined by the Installation Script
Note ANAHOME refers to the Cisco Prime Network home directory. At the command line, enter $ANAHOME. For compatibility with previous Cisco Active Network Abstraction releases, this variable was not changed.
Note The ANAHOME variable content /export/home/network-user changes according to the gateway installation directory. For details, see Installing the Cisco Prime Network Gateway.
Do not change permissions on the /export/home/
network-user directory. If the permissions are set too loose, SSH communication problems can occur, and the Cisco Prime Network gateway might not start.
The installation script automatically defines the aliases listed in Table 7-2.
Table 7-2 Aliases Defined by the Installation Script
Changes the directory to ~/Main/registry
Changes the directory to ~/Main
Changes the directory to ~/Main/logs
Verifying the Cisco Prime Network Gateway Installation
See the following sections to verify the installation of the gateway:
•Cisco Prime Network Database Configuration
•Cisco Prime Network Version Information
•Drools Rules Configuration
•Graph Mechanism Configuration
•Cisco Prime Network Configuration Directories
Cisco Prime Network Database Configuration
To confirm that the Cisco Prime Network database is running, available, and configured correctly:
Step 1 On the server where Oracle is installed, enter the following command as the Oracle UNIX user:
The username is network-user, and the password is the same as the root built-in user password.
Step 2 Confirm that the SQL client can connect to the database.
The following prompt appears:
SQL*Plus: Release 10.2.0.3.0 - Production on Wed Oct 7 11:10:06 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
If Failure Occurs
A test failure indicates a database error. Contact your local database administrator and repeat the test.
Cisco Prime Network Version Information
Use this procedure to view the version of Cisco Prime Network installed on the server and to verify that the major components of the Cisco Prime Network system are located correctly and are running.
Note This test also checks additional characteristics of the installation, such as directories and classes.
If there are any files missing or problems with the configuration, this check fails.
Step 1 On the gateway, enter:
Step 2 Confirm that the correct version of Cisco Prime Network has been installed.
The following is an example of the message that should be displayed:
.-= Welcome to server-name, running Cisco Prime Network gateway (v3.8 (build number)) =-.
Drools Rules Configuration
To confirm that the Drools rules file was created correctly:
Step 1 On the server, verify that the ~/Main/data directory exists.
Step 2 Confirm that the directory contains the post.drl file.
The Drools rules file exists in the ~/Main/data directory.
If Failure Occurs
Rerun the installation.
Graph Mechanism Configuration
To confirm that the graph mechanism is working correctly:
Step 1 Open a web browser on a PC client connected to the server.
Step 2 The graph mechanism, also known as the diagnostic web page, is enabled by default. You can disable or enable the diagnostic web page:
•To disable the diagnostic web page, enter diagnostic_framework.cmd disable.
•To enable the diagnostic web page, enter diagnostic_framework.cmd enable.
Step 3 Enter the following URL to connect to the Cisco Prime Network graph:
Note The username and password for the graphs were configured during installation.
The graphs open in the web browser.
Cisco Prime Network Configuration Directories
To confirm that the Cisco Prime Network Golden Source configuration directories are installed on the gateway:
Step 1 On the server, browse to the directory ~/Main/registry/ConfigurationFiles.
Step 2 Verify that the directory contains the following subdirectories:
•The subdirectory 127.0.0.1 exists.
•The subdirectory 0.0.0.0 exists.
If Failure Occurs
Verify that the webserver daemon is up and running, and then enter the status command on the gateway as shown in Figure 7-2.
Figure 7-2 Status Command on the Cisco Prime Network Gateway
After you have verified the successful installation of the gateway, you can install the units. See Chapter 9 "Installing a Cisco Prime Network Unit."
Note A Cisco Prime Network base license must be registered and activated within 120 days of installation or upgrade. If there are no valid license files on the gateway server, Cisco Prime Network acts as an evaluation version. This means that it has full functionality for 120 days after installation, and then it expires and UI connections will be disallowed. For Cisco Prime Network licensing information, see the Cisco Prime Network 3.8 Administrator Guide.