Installing the Cisco Prime Network 3.8 Gateway With an … · database owner, regardless of whether...

OL-24641-01

C H A P T E R 3
Installing the Cisco Prime Network 3.8 Gateway With an Embedded Database
This chapter explains how to install Cisco Prime Network 3.8 with an embedded Oracle database.

The Cisco Prime Network embedded Oracle 11g 11.2.0.1.0 database is fully integrated with Cisco Prime Network and allows Cisco Prime Network to manage and monitor its data. This solution provides the following benefits:

• A single integrated solution that requires minimal management.

• Easier, faster, and less error-prone installation and upgrades.

Complete the procedures in this chapter only if:

• You want to install Cisco Prime Network with an embedded Oracle database.

• You are not installing a Cisco Prime Network gateway high availability solution. If you are installing a gateway HA solution, proceed to one of the following chapters:

– Chapter 6, “Installing a Cisco Prime Network Gateway and Embedded Database in a Veritas High Availability Configuration.”

– Chapter 8, “Installing a Cisco Prime Network Gateway and Embedded Database in a Red Hat Cluster Suite and Oracle Active Data Guard High Availability Configuration.”

However, because the Cisco Prime Network gateway HA solution installs an embedded database, review the Embedded Database Installation Requirements, page 3-2, before proceeding to those chapters.

Note When you install the Cisco Prime Network embedded database, the Change and Configuration Management component is installed automatically. Change and Configuration Management provides tools that allow you to manage the software and device configuration changes that are made to devices in your network. For more information, see the Cisco Prime Network 3.8 Change and Configuration Management User and Administrator Guide.

This chapter includes:

• Embedded Database Installation Requirements, page 3-2

• Installing an Embedded Database and the Cisco Prime Network Gateway on the Same Server, page 3-6

• Installing an Embedded Database and the Cisco Prime Network Gateway on Separate Servers, page 3-14

• Uninstalling the Embedded Database, page 3-19

3-1Cisco Prime Network 3.8 Installation Guide

http://www.cisco.com/en/US/products/ps11879/products_user_guide_list.html

http://www.cisco.com/en/US/products/ps11879/products_user_guide_list.html

Chapter 3 Installing the Cisco Prime Network 3.8 Gateway With an Embedded Database Embedded Database Installation Requirements

Embedded Database Installation Requirements

Note • The following prerequisites are in addition to the requirements in Hardware and Software Requirements, page 1-1.

• For the exact storage and memory requirements, contact your Cisco account representative to obtain the Cisco Prime Network Capacity Planning Guide, which provides detailed deployment guidelines as you plan your Cisco Prime Network installation.

You can install the embedded database on:

• Solaris SPARC 10 64-bit update 6 or later.

• Red Hat Enterprise Linux Server Release 5.3, 5.4, 5.5, and 5.6, 64-bit or later Server Edition.

Note Cisco Prime Network 3.8 currently does not operate under Red Hat 5.6 unless additional RPMs are installed. For information, see the Cisco Prime Network 3.8 Release Notes.

Note The Cisco Prime Network embedded database is not supported on:

• Red Hat 6

• VMware ESX

Solaris

The Oracle 11g R2 database is built and tested on the Solaris 10 update 6 (u6) operating system (see Oracle bug 9152554). Oracle Global Software Support cannot support anything earlier than Solaris 10 u6. The runtime environment for the Oracle 11g R2 database must use Solaris 10 u6 or later.

To verify that you have the required Solaris version, enter:

# cat /etc/release

In the command output, you should see u6 or later:

Solaris 10 11/06 s10s_u6wos_10 SPARC

If the output shows a Solaris version earlier than 10/08, u6, you must upgrade to u6 or later.

Red Hat

Oracle recommends that you install the Linux operating system with the default software packages (RPMs). Do not customize the RPMs during installation. The following packages, or later versions of them, are required for the Oracle 11g R2 database:

• binutils

• compat-libstdc++-33-3.2.3

• elfutils-libelf

• elfutils-libelf-devel

• gcc-4.1.2


OL-24641-01

http://www.cisco.com/en/US/products/ps11879/prod_release_notes_list.html


• gcc-c++-4.1.2

• glibc-2.5

• glibc-common-2.5

• glibc-devel-2.5

• glibc-headers-2.5

• ksh

• libaio

• libaio-devel

• libgcc-4.1.2

• libstdc++

• libstdc++-devel

• make

• numactl-devel

• sysstat-7.0.2

Note If any of the preceding packages are missing, the installation fails.

To verify that you have the required Linux version, enter:

# cat /etc/redhat-release

In the command output, you should see:

Red Hat Enterprise Linux Server release 5.3 Beta (Tikanga)

To verify that all required RPMs are installed, enter the following command as the root user:

rpm -q binutils compat-libstdc++-33-3.2.3 elfutils-libelf elfutils-libelf-devel gcc-4.1.2 gcc-c++-4.1.2 glibc glibc-common glibc-devel glibc-headers ksh libaio libaio-devel libgcc-4.1.2 libstdc++ libstdc++-devel make numactl-devel sysstat-7.0.2 --qf '%{name}.%{arch}\n'|sort

If the embedded database mount points contained in networkdata/archive logs and control files are set outside the local disks, for example, on a SAN, make corresponding entries in /etc/vfstab so the mount points are available to Solaris during a reboot.

Embedded Database Memory RequirementsFor the installation phase, the database memory requirements are:

• Swap space:

– Solaris—500 MB

– Linux—150 MB

• At least 4 GB of RAM

For the runtime phase, the database memory requirements are:

• Swap space:

– Solaris—Equal to the size of RAM, up to 16 GB


OL-24641-01


– Linux—Two times the size of RAM, up to 32 GB

• Table 3-1 lists the runtime phase RAM requirements.

Embedded Database Storage RequirementsFor the installation phase, the database storage requirements are:

• 1 GB of space in the /tmp directory.

• 6 GB of space for software files in the home directory of the database’s OS user (usually /export/home/oracle).

For the run-time phase, the storage is required for the data file, redo logs, archive log, and backup file:

• 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.

• Online redo logs are a set of files that contain records of changes made to data. Redo log files should not reside on the same disk as the data files. For online redo log files on Solaris servers, prepare a dedicated file system mounted on a mount point with the forcedirectio option. For example, for the file system /dev/dsk/c0t1d0s6, the entry in /etc/vfstab should look like the following:

/dev/dsk/c0t1d0s6 /dev/rdsk/c0t1d0s6 /directio ufs 1 yes forcedirectio

For Linux, use ext3 and mount with the default mount options.

The redo logs are created under the directory that you specify during installation.

• An archive log is a member of an online redo log that has been archived by the Oracle database. Archived log files should not reside on the same disk as the data files. The archived redo log files can be applied to a database backup for media recovery. The archive logs are created under the directory that you specify during installation.

Note If the embedded database mount points for networkdata/archive logs/control files are set outside the local disks (for example, on a storage area network), make corresponding entries in /etc/vfstab so Solaris can access the mount points during reboots. If this is not done, the embedded database and gateway will not start.

• A backup file stores a copy the database data, which can be used to reconstruct data. Backup files should not reside on the same disk as the data files. The backup files are created under the directory that you specify during installation.

Table 3-2 provides the run-time embedded database storage requirements.

Table 3-1 Database Memory During Runtime

Deployment Configuration Minimum RAM Requirements

Proof of concept (1 actionable event per second) 8 GB

Small (up to 5 actionable events per second) 8 GB

Medium (up to 20 actionable events per second) 16 GB

Large (up to 50 actionable events per second) 16 GB

High scale (up to 100 actionable events per second) 24 GB

High scale (up to 200 actionable events per second) 24 GB


OL-24641-01


Your system administrator must:

• Back up the archive logs to tape daily.

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

Embedded Database Port RequirementsPort 1102 must be available for SSH communication between the Cisco Prime Network owner and the database owner, regardless of whether the Cisco Prime Network gateway and the embedded database are installed separately or on the same server.

If you are installing the embedded database and the Cisco Prime Network gateway on separate servers, the following additional ports must be available on the remote server:

• 22 (the default SSH port).

• 1521 (the database's listener port).

The installation prompts you for an SMTP server and an e-mail address to receive e-mail notifications of database errors. Port 25 should be available to receive e-mail notifications, and the UNIX sendmail utility should be configured in advance.

Additional Embedded Database RequirementsFor remote embedded database installations:

• Perl version 5.8.6 or later must be installed on the root user.

• The installation script copies the Oracle installation files to the remote server under the home directory of the user connecting to the workstation through 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 over consumption might cause the server to crash.

In addition to the list of UNIX shells required for Cisco Prime Network (see UNIX Services and Components Used by Cisco Prime Network, page 1-12), the embedded database also requires BASH (/bin/bash & /usr/bin/bash)

Verify that /etc/hosts includes the machine’s local hostname and IP address. For example:

Good /etc/hosts::1 localhost 127.0.0.1 localhost IP-address sh-nv210-266 loghost

Table 3-2 Run Time Embedded Database Storage Requirements

Deployment Configuration Data File (GB) Redo Logs (GB) Archive Logs (GB) Backup File (GB)

One actionable event per second. 28 6 22 22

Up to five actionable events per second. 92 6 138 111

Up to 20 actionable events per second. 340 6 440 510





OL-24641-01

Chapter 3 Installing the Cisco Prime Network 3.8 Gateway With an Embedded Database Installing an Embedded Database and the Cisco Prime Network Gateway on the Same Server

Bad /etc/hosts# Do not remove the following line, or various programs# that require network functionality will fail.127.0.0.1 localhost.localdomain localhost::1 localhost6.localdomain6 localhost6

You can install the Cisco Prime Network 3.8 embedded database on an IPv4-only server or on a dual stack server (IPv4 and IPv6). You cannot install the embedded database on an IPv6-only server.

SecurityCisco Prime Network connects to the database using an Oracle encryption feature. By default, connections between the Cisco Prime Network server (gateway and units) and the embedded database are encrypted. You can change the default encryption after installation by editing the registry.

Installing an Embedded Database and the Cisco Prime Network Gateway on the Same Server

Complete the following steps to install an embedded database on the same server as the Cisco Prime Network gateway:

Step 1 Insert “Disk 1: New Install” in the DVD drive.

Step 2 Open a Telnet or SSH session to the gateway and log in as the user root.

Step 3 Back up and remove the old version of the gateway (if an older version exists).

Step 4 To change to the CD directory, enter:

cd /cdrom/cdrom0/Server

Step 5 To install the Cisco Prime Network gateway, enter:

perl ./install.pl -user network-user

where network-user is the operating system user account for the Cisco Prime Network application, created when Cisco Prime Network is installed. In the following example, network-user is set to network38.

For example, if the name of the user is network38, enter:

perl ./install.pl -user network38

The network-user must start with a letter and contain only the characters shown in brackets: [A-Z a-z 0-9 -].

Note The network-user cannot contain a [.] character. For example, network38 is permitted, but network3.8 is not.

The gateway is installed in the default directory /export/home/network-user. In this example, the installation directory is /export/home/network38.


OL-24641-01


To change the installation directory, add the -dir [desired directory] switch at the end of the perl ./install.pl -user network-user 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 Appendix A, “Folders Created in Cisco Prime Network.”

The following output is displayed:

------------------------------------------------------------------------------ Initiating install------------------------------------------------------------------------------

- 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 OS type [OK]- 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]- Erasing user bos [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]


OL-24641-01


------------------------------------------------------------------------------ Installing Prime Network------------------------------------------------------------------------------

- Adding unix user network38 [OK]- Adding unix user bos [OK]- Checking for encapsulated data file [OK]- Unpacking encapsulated data [OK]- Extracting files [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 bundles [OK]- Deploying clean_tmp [OK]- Deploying crontab [OK]- Deploying nccm [OK]- Deploying os_dependent_cleaner [OK]- Deploying resolve_home [OK]- Deploying secure_daemon [OK]- Deploying webserver [OK]- Deploying solaris dependent components- Deploying ActivePerl-5.8.6.811-RAW [OK]- Deploying embedded_oracle [OK]- Deploying fetch_ssh_daemon [OK]- Deploying java_link [OK]- Deploying os_services [OK]- Deploying xmp_dm [OK]- Setting usermod for priv ports (Solaris) for user network38 [OK]- Updating bos commands [OK]

Step 6 After the installation is complete, you will be prompted to configure Prime Network. Enter yes to continue to Step 10 or no to configure later using the network-conf command.

Installation completed, would you like to configure Prime Network now? (yes/no)?

Step 7 Before configuring Cisco Prime Network on the gateway, as the Cisco Prime Network user, copy the Oracle installation .zip files from the installation DVD to the embedded_oracle directory. To do this:

a. Eject “Disk 1: New Install.”

b. Insert one of the following DVDs in the DVD drive:

– Disk 3: Database Binaries for Solaris

– Disk 4: Database Binaries for Linux

c. For Solaris, copy the following .zip files from “Disk 3: Database Binaries for Solaris” to ANAHOME/local/scripts/embedded_oracle:

– solaris.sparc64_11gR2_database_1of2.zip


d. For Linux, copy the following .zip files from “Disk 4: Database Binaries for Linux” to ANAHOME/local/scripts/embedded_oracle:

– linux.x64_11gR2_database_1of2.zip



OL-24641-01


Step 8 Log in as the new network-user. 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:

passwd network-user

Step 9 Enter the following command to configure Prime Network:

network-conf

Step 10 Enter the appropriate response at the installer prompts. In the following sample output (when installing on Solaris), user entries are shown in bold font. Variables that you must enter are shown in italics; for example, password.

Welcome to Cisco Prime Network

The system is not configured, please run network-conf????????????????????????????????????????????????????? Prime Network Configuration Utility ?????????????????????????????????????????????????????

?????????????????????????????????????????????????????1?Set machine as Prime Network unit. ??2?Set machine as Prime Network gateway. ??q?Quit ?????????????????????????????????????????????????????

+ Is NTP configured on this machine? (yes/no) yes- Writing log to /export/home/network38/Main/logs/network-conf-1309268033.log- Killing all Java/Perl process belonging to user network38 [OK]- Updating current time to /export/home/network38/Main/unix/define.sql [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]- Setting SSL keys [OK]- Removing old SSH keys if exist- Generating SSH keys- GW SSH keys generated successfully.- Enter the password for OS root user:rootpassword- Extracting ivne-drivers.tar into /export/home/network38/Main/drivers [OK]+ 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 components. 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:built-inuserpassword - Enter the password again for verification:built-inuserpassword- Creating web monitoring tool user 'admin'. You can change the passwords at a later stage - see Admin Guide.+ Prime Network can run with a pre-configured database or it can install the database for you.

a. At the prompt to install the database, enter yes:

- Would you like Prime Network to install the database? [yes,no] [default no] yes- Verifying the embedded database zip files exist [OK]

b. If you have already copied the database installation.zip files in Step 7, press Enter:


OL-24641-01


+ About to install Prime Network embedded database- Installing ActivePerl Enterprise v5.10.1.1007.1

c. At the prompt to install the database on a remote server, enter no:

- Would you like to install the database on a remote server? [yes,no] no

d. Cisco Prime Network 3.8 supports dual NICs. If the installation detects that the server is configured with multiple NICs, you are prompted to specify the one to use for the database connection:

- Multiple network interfaces were detected on this host. Please select a single interface for the database:

1. IP-address-12. IP-address-2Enter option: (1-2)

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

e. You are prompted to enter user and database details:

- Enter the password for OS root user: password- Enter a name for the OS user of the database [oracle] - Enter the home directory of the user (oracle) [/export/home/oracle] - If the database is already installed on IP-address under /export/home/oracle, would you like to remove it? [yes]- How would you estimate your database profile (in terms of required database RAM)? 1. 1 actionable event per second(requires a minimum 8 GB) 2. Up to 5 actionable events per second (requires minimum 8 GB) 3. Up to 20 actionable events per second(requires minimum 16 GB) 4. Up to 50 actionable events per second (requires minimum 16 GB) 5. Up to 100 actionable events per second(requires minimum 24 GB)6. Up to 200 actionable events per second(requires minimum 24 GB) Enter option: (1-6) - Enter the location for the database's datafiles [/export/home/oracle/oradata/anadb]

Note On a Solaris server, create the redo logs on a disk mounted as UFS with the forcedirectio option.

- Enter the location for the redo logs: path

f. You are prompted to configure automatic database backups:

- Would you like Prime Network to run automatic database backups [yes,no]?

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

If you entered yes at the preceding prompt, specify the automatic backup destinations:

- Enter the destination for the archive logs: [/export/home/oracle/arch] - Enter the destination for the backup files: [/export/home/oracle/backup] - Enter your SMTP server IP/Hostname: company-email-server-address- Checking if all needed OS components exist and executable [OK]


OL-24641-01

http://www.cisco.com/en/US/products/ps11879/products_installation_and_configuration_guides_list.html

http://www.cisco.com/en/US/products/ps11879/products_installation_and_configuration_guides_list.html


- About to remove the current database installation- Verifying user oracle exists [NO USER]- Checking if zip files exist [OK]- Checking user 'oracle' doesn't exists [OK]- Checking if /export/home/oracle exists [OK]- Creating directory '/export/home/oracle' [OK]- Adding UNIX user 'oracle' [OK]- Adding user 'oracle' to group 'oinstall' [OK]- Setting /export/home/oracle ownership to oracle:oinstall [OK]- Extracting /export/home/network38/local/scripts/embedded_oracle/solaris.sparc64_11gR2_database_1of2.zip [OK]- Extracting /export/home/network38/local/scripts/embedded_oracle/solaris.sparc64_11gR2_database_2of2.zip [OK]- Creating /export/home/oracle/.cshrc [OK]- Installing the database binaries- Configuring the network services- Configuring the database- Executing post DB creation tasks- Installing patches- Installing RDA- Enable and start cron jobs- Initializing Prime Network SSH daemon+ Prime Network Setup will now configure the default schemas:- creating Prime Network tables...- creating dwe tables...- creating admin database objects...+ Setup will now configure the Event Processing (EP) schema: - Setting local EP done.+ Updating persistency+Prime Network is bundled with XMP web server, setup will now install the XMP platform and assocaited components.+ Updating persistency- Installing the Change and Configuration Management components. Please wait.- Starting Web Server.- Shutting down Web Server.- Updating gateway bsm registry with Change and Configuration Management data (avm-77)Prime Network Web Server and associated components installation completed.+Multiple network interfaces detected on host. Please select a single interface for Prime Network backend services

1. IP-address-12. IP-address-23. IP-address-34. IP-address-4

Enter option: (1-4)

+ Done setting license functional state tier to NAS- Installing NSA [OK]- Updating DM properties file.

g. If you want to install Prime Network with the Prime IP-NGN Suite, enter yes at the following prompt:

+Is Prime Network being installed as part of the Prime IP-NGN Suite? [yes,no][default no]

Note If you install Prime Network in standalone mode and later decide to integrate with the Prime Central suite, see the Cisco Prime Central 1.0 Quick Start Guide, section “Configuring the Prime Network, Prime Optical, and Prime Fulfillment Servers as Suite Components.”


OL-24641-01

http://www.cisco.com/en/US/products/ps11754/prod_installation_guides_list.html


- Enter the Cisco Prime Central database Server IP Address: ipaddress- Enter the Cisco Prime Central database SID: SID- Enter the Cisco Prime Central database User Name: username- Enter the Cisco Prime Central database password:password- Enter the Cisco Prime Central database port:port number+ Log was written to /export/home/network38/Main/network-conf-1309437070.log

+ Done setting the machine as gateway.

step h starts here:

h. At the end of the network-conf script, you are prompted to enter an e-mail address to receive e-mail notifications of different database errors:

+ Executing post embedded database installation tasks- Enter an email for receiving alerts: [email protected] Reading registry parameters- Enabling email notifications & Prime Network events for ORA errors- Enabling DB administration functions

(If automatic database backups are configured, the following prompt appears.)

- Increase amount of Prime Network backups

The installation log is available at ANAHOME/local/scripts/embedded_oracle/ana_embedded_oracle.log.

Step 11 After the installation is complete, complete the Running the add_emdb_storage.pl Utility, page 3-12 procedure to add the required data files and online redo logs.

Running the add_emdb_storage.pl UtilityUse the add_emdb_storage.pl script to add database files according to the database size you estimate you will need. You are prompted to provide the database profile, the estimated database capacity and the history size for events and workflows. This enables the script to calculate the maximum size of the database, and to create the data files, temp files, and redo logs. See Table 3-2 on page 3-5 for information on database sizing.

Before You Begin

If you need assistance estimating the database size, contact your Cisco representative. The representative can provide the Memory Assessment Tool to help you with the sizing.

Step 1 Log into the Cisco Prime Network gateway as network-user. (network-user is the UNIX account for the Cisco Prime Network application, created when Cisco Prime Network is installed; for example, network38.)

Step 2 Change directories to ANAHOME/Main/scripts/embedded_db and enter the following command:

# ./add_emdb_storage.pl

If you are installing the embedded database as part of the Red Hat Cluster Suite (RHCS) Oracle Active Data Guard (ADG) gateway high availability, you must add the -ha flag:

# ./add_emdb_storage.pl-ha


OL-24641-01


Note Adding the -ha flag is important for the RHCS/ADG gateway HA. See the Chapter 8, “Installing a Cisco Prime Network Gateway and Embedded Database in a Red Hat Cluster Suite and Oracle Active Data Guard High Availability Configuration,” for more information.

Step 3 Enter the appropriate response at the prompts:

- Retrieving registry information & initializing connection- How would you estimate your DB profile?-----------------------------------------1) 1 actionable events per second (POC/LAB deployment)2) Up to 5 actionable events per second 3) Up to 20 actionable events per second 4) Up to 50 actionable events per second 5) Up to 100 actionable events per second 6) Up to 200 actionable events per second (1 - 6) [default 1]- Insert the event archiving size in days. Prime Network default archive is 14 days: [default 14] - Insert the workflow archiving size in days. Prime Network default archive is 7 days: [default 7]

Note If you enter incorrect values—such as the wrong database profile estimate—you can rerun the script with different inputs.

• If you encounter any errors, messages similar to the following examples are displayed.

• If there is not enough disk space to create the additional database files or redo logs:

- There isn't enough space on the current disks to create an additional of6144 MB. Please enter a new location for creating the remainingDB files. Before you continue:1. Verify user <os-db-user> has writing permissions on the new locationor run the following command as the OS root user:chown -R <os-db-user>:oinstall <path>2. Verify the new location is mounted as UFS with 'forcedirectio'option

New location:

Enter another location.

• If the files or redo logs cannot be created for any reason, you will see an error message and the following prompt:

- How would you like to continue?---------------------------------1) Retry 2) Skip (move to the next in list)3) Abort (1 - 3) [default 1]

For example, if the correct permissions were not set, you would see the following.

Failed to add datafile for network38:-1119: ORA-01119: error in creating database file '/2del/network38_DATA11.dbf'ORA-27040: file create error, unable to create fileLinux-x86_64 Error: 13: Permission denied


OL-24641-01

Chapter 3 Installing the Cisco Prime Network 3.8 Gateway With an Embedded Database Installing an Embedded Database and the Cisco Prime Network Gateway on Separate Servers

The menu choices provide with you with an opportunity to fix the permissions and retry creating the file or log.

• On Solaris, verify the new location is mounted as UFS with 'forcedirectio' option.

The log file is located in ANAHOME/Main/logs/emdb/add-storage-time-stamp.log.

Installing an Embedded Database and the Cisco Prime Network Gateway on Separate Servers

Complete the following steps to install an embedded database on a separate server from the Cisco Prime Network gateway:

Step 1 Insert “Disk 1: New Install” in the DVD drive.

Step 2 Open a Telnet or SSH session to the gateway and log in as the user root.

Step 3 Back up and remove the old version of the gateway (if an older version exists).

Step 4 To change to the CD directory, enter:

cd /cdrom/cdrom0/Server

Step 5 To install the Cisco Prime Network gateway, enter:

perl ./install.pl -user network-user

where network-user is the operating system user account for the Cisco Prime Network application, created when Cisco Prime Network is installed.

The network-user 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

Note The network-user cannot contain a [.] character. For example, network38 is permitted, but network3.8 is not

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.

Note Do not place a forward slash (“/”) after the Prime Network home directory.

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 Appendix A, “Folders Created in Cisco Prime Network.”


OL-24641-01


The following output is displayed:

------------------------------------------------------------------------------ Initiating install------------------------------------------------------------------------------

- 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 OS type [OK]- 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]- Erasing user bos [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]

------------------------------------------------------------------------------ Installing Prime Network------------------------------------------------------------------------------

- Adding unix user network38 [OK]- Adding unix user bos [OK]- Checking for encapsulated data file [OK]- Unpacking encapsulated data [OK]- Extracting files [OK]- Making sure main files are in unix mode [OK]- Setting files permissions [OK]- Setting files owner [OK]- Creating installation registry [OK]


OL-24641-01


- Generating /var/adm/cisco/prime-network/reg/network38/uninstall.pl[OK]- Deploying OS independent components- Deploying bos_commands [OK]- Deploying bundles [OK]- Deploying clean_tmp [OK]- Deploying crontab [OK]- Deploying nccm [OK]- Deploying os_dependent_cleaner [OK]- Deploying resolve_home [OK]- Deploying secure_daemon [OK]- Deploying webserver [OK]- Deploying solaris dependent components- Deploying ActivePerl-5.8.6.811-RAW [OK]- Deploying embedded_oracle [OK]- Deploying fetch_ssh_daemon [OK]- Deploying java_link [OK]- Deploying os_services [OK]- Deploying xmp_dm [OK]- Setting usermod for priv ports (Solaris) for user network38 [OK]- Updating bos commands [OK]

Step 6 After the installation is complete, you will be prompted to configure Prime Network. Enter yes to continue to Step 10 or no to configure later using the network-conf command.

Installation completed, would you like to configure Prime Network now? (yes/no) [yes]?

Step 7 Before configuring Cisco Prime Network on the gateway, as the Cisco Prime Network user, copy the Oracle installation .zip files from the installation DVD to the embedded_oracle directory. To do this:

a. Eject “Disk 1: New Install.”

b. Insert one of the following DVDs in the DVD drive:

– Disk 3: Database Binaries for Solaris

– Disk 4: Database Binaries for Linux

c. For Solaris, copy the following .zip files from “Disk 3: Database Binaries for Solaris” to ANAHOME/local/scripts/embedded_oracle:



d. For Linux, copy the following .zip files from “Disk 4: Database Binaries for Linux” to ANAHOME/local/scripts/embedded_oracle:



Step 8 Log in as the new network-user. 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:

passwd network-user

Step 9 Enter the following command:

network-conf

Step 10 Enter the appropriate response at the installer prompts. In the following sample output (when installing on Solaris), user entries are shown in bold font. Variables that you must enter are shown in italics; for example, password.

+ Prime Network can run with a pre-configured database or it can install the database for you.


OL-24641-01


a. At the prompt to install the database, enter yes:

- Would you like Prime Network to install the database? [yes,no] [default no] yes- Verifying the embedded database zip files exist [OK]+ About to install Prime Network embedded database- Installing ActivePerl Enterprise v5.10.1.1007.1

b. At the prompt to install the database on a remote server, enter yes:

- Would you like to install the database on a remote server? [yes,no] yes- Enter the server's IP address: IP-address

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

c. You are prompted to enter user details:

- Enter the username to connect via ssh to the remote server: username- Enter the password for the OS admin user: password- Enter the password for OS root user: password

d. If the installation detects that the gateway server is configured with multiple NICs, you are prompted to specify the one with which the database server will synchronize its date:

- Please select a single interface to be used as the Prime Network gateway IP: 1. IP-address-1 2. IP-address-2 Enter option: (1-2)

e. You are prompted to enter database details:

- Enter a name for the OS user of the database [oracle]- Enter the home directory of the user (oracle) [/export/home/oracle]

If the installer detects a previous embedded database installation, the following prompt appears:

- Would you like to remove the database currently installed under /export/home/oracle? [yes]- How would you estimate your database profile (in terms of required database RAM)? 1. 1 actionable event per second (requires a minimum 8 GB) 2. Up to 5 actionable events per second (requires a minimum 8 GB) 3. Up to 20 actionable events per second (requires minimum 16 GB) 4. Up to 50 actionable events per second (requires minimum 16 GB) 5. Up to 100 actionable events per second (requires minimum 24 GB) 6. Up to 200 actionable events per second (requires minimum 24 GB) Enter option: (1-6)

- Enter the location for the database's datafiles [/export/home/oracle/oradata/anadb]

Note On a Solaris server, create the redo logs on a disk mounted as UFS with the forcedirectio option.

- Enter the location for the redo logs: path

f. You are prompted to configure automatic database backups:

- Would you like Prime Network to run automatic database backups [yes,no]?


OL-24641-01


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

If you entered yes at the preceding prompt, specify the automatic backup destinations:

- Enter the destination for the archive logs: [/export/home/oracle/arch] - Enter the destination for the backup files: [/export/home/oracle/backup]

- Enter your SMTP server IP/Hostname: company-email-server-address

- Checking remote server 'IP-address' [OK]- Uploading installation files to remote server 'IP-address'. This might take a while..- Installing the database on IP-address. This might take a while..- Checking if all needed OS components exist and executable [OK]- About to remove the current database installation- Verifying user oracle exists [NO USER]- Checking if zip files exist [OK]- Checking user 'oracle' doesn't exists [OK]- Checking if /export/home/oracle exists [OK]- Creating directory '/export/home/oracle' [OK]- Adding UNIX user 'oracle' [OK]- Adding user 'oracle' to group 'oinstall' [OK]- Setting /export/home/oracle ownership to oracle:oinstall [OK]- Extracting - /export/home/admin/ORA/solaris.sparc64_11gR2_database_1of2.zip [OK]- Extracting - /export/home/admin/ORA/solaris.sparc64_11gR2_database_2of2.zip [OK]- Creating /export/home/oracle/.cshrc [OK]- Installing the database binaries- Configuring the network services- Configuring the database- Executing post DB creation tasks- Synchronizing time server with Prime Network gateway- Installing patches- Installing RDA- Enable and start cron jobs- Initializing Prime Network SSH daemon** Installation finished successfullyCISCO_ORACLE_INSTALL_ENDED

g. At the end of the network-conf script, you are prompted to enter an e-mail address to receive e-mail notifications of different database errors:

+ Done setting the machine as gateway.

+ Executing post embedded database installation tasks- Enter an email for receiving alerts: [email protected] Reading registry parameters- Enabling email notifications & Prime Network events for ORA errors- Enabling DB administration functions

(If automatic database backups are configured, the following prompt appears.)

- Increase amount of Prime Network backups

The installation log is available at ANAHOME/local/scripts/embedded_oracle/network_embedded_oracle.log and on the remote server at SSH-user-home-directory/ORA/network_embedded_oracle.log.


OL-24641-01

http://www.cisco.com/en/US/products/ps11879/prod_maintenance_guides_list.html

http://www.cisco.com/en/US/products/ps11879/prod_maintenance_guides_list.html

Chapter 3 Installing the Cisco Prime Network 3.8 Gateway With an Embedded Database Uninstalling the Embedded Database

Step 11 After the installation is complete, complete the Running the add_emdb_storage.pl Utility, page 3-12 procedure to add the required data files and online redo logs.

Step 12 Continue with the following topics:

• Updating the Database Host in the Registry for NAT, page 7-12

• Changes Resulting from the Installation, page 7-14

• Verifying the Cisco Prime Network Gateway Installation, page 7-15

• What’s Next?, page 7-18

Uninstalling the Embedded DatabaseDepending on your configuration, complete one of the following procedures to uninstall the embedded database:

• Uninstalling an Embedded Database Installed on the Same Server as the Cisco Prime Network Gateway (Local Database), page 3-19

• Uninstalling an Embedded Database Installed on a Server Separate from the Cisco Prime Network Gateway (Remote Database), page 3-20

Uninstalling an Embedded Database Installed on the Same Server as the Cisco Prime Network Gateway (Local Database)

Complete the following steps to uninstall an embedded database that is installed on the same server as the Cisco Prime Network gateway. This procedure assumes that network-user (the UNIX user account for the Cisco Prime Network application, created when Cisco Prime Network is installed) is network38.

Step 1 Log into the Solaris server as the root user and enter the following command to change the directory:

cd /var/adm/cisco/prime-network/reg/network38


./uninstall.pl

Step 3 At the following prompt, enter yes:

This will uninstall Prime Network user network38?(yes/no): yes

The uninstallation begins. The following output is displayed:

------------------------------------------------------------------------------ Initiating uninstall------------------------------------------------------------------------------

- writing verbose log to /var/adm/cisco/prime-network/logs/verbose-uninstall-time-stamp- writing log to /var/adm/cisco/prime-network/logs/uninstall-log-time-stamp- Checking OS type [OK]- About to uninstall Prime Network's database - Retrieving registry parameters ..- Checking if all needed OS components exist and executable [OK]- About to remove the current database installation - Verifying user oracle exists [EXISTS]


OL-24641-01


- Removing oracle cron jobs [OK] - About to shutdown the database [OK] - Removing '/export/home/oracle' [OK] - Removing user 'oracle' [OK]- Successfully removed the database [OK]CISCO_ORACLE_INSTALL_ENDED[OK]..

Step 4 If the uninstallation fails, the following error message is returned:

*** ERROR: Failed to uninstall Prime Network's internal database ***Try to uninstall the database separately, by executing as OS user 'root'cd <network-home-dir>/local/scripts ; perl uninstall_ana_db.pl <network-user> <network-home-dir>Once done, hit the 'Enter' key to continue or 'Ctrl C' to quit

Do the following:

a. As the root user, enter the following commands:

cd Network-home-directory/local/scripts perl uninstall_ana_db.pl network-user Network-home-directory

b. Press the Enter key to continue with the Cisco Prime Network uninstallation.

Uninstalling an Embedded Database Installed on a Server Separate from the Cisco Prime Network Gateway (Remote Database)

Complete the following steps to uninstall an embedded database that is installed separately from the Cisco Prime Network gateway. This procedure assumes that network-user (the UNIX user account for the Cisco Prime Network application, created when Cisco Prime Network is installed) is network38.

Step 1 Log into the Solaris server as the root user and enter the following command to change the directory:

cd /var/adm/cisco/prime-network/reg/network38


./uninstall_ana.pl

Step 3 At the following prompt, enter yes:

This will uninstall Prime Network user neetwork38?(yes/no): yes

Step 4 The following output is displayed. Enter the appropriate response at the installer prompts. In the following sample output, user entries and variables are shown in italics; for example, password.

------------------------------------------------------------------------------ Initiating uninstall------------------------------------------------------------------------------

- writing verbose log to /var/adm/cisco/prime-network/logs/verbose-uninstall-time-stamp- writing log to /var/adm/cisco/prime-network/logs/uninstall-log-time-stamp- Checking OS type [OK]- About to uninstall Prime Network's database - Retrieving registry parameters .. - Installing perl ..


OL-24641-01


|-----------------------------------------------------------------|| This system is for the use of authorized users only. || Individuals using this computer system without authority, or in || excess of their authority, are subject to having all of their || activities on this system monitored and recorded by system || personnel. || || In the course of monitoring individuals improperly using this || system, or in the course of system maintenance, the activities || of authorized users may also be monitored. || || Anyone using this system expressly consents to such monitoring || and is advised that if such monitoring reveals possible || evidence of criminal activity, system personnel may provide the || evidence of such monitoring to law enforcement officials. ||-----------------------------------------------------------------|

Welcome to Prime Network

----------------------------------------------------------------------------------.-= 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 if license server is up and running [NO LICENSE] - Checking XMP runtime DM [UP]+ Detected AVM99 is up, checking AVMs - Checking for AVM66's status [DISABLED] - Checking for AVM11's status [OK 0/519] - Checking for AVM83's status [OK 0/109] - Checking for AVM100's status [OK 0/72] - Checking for AVM0's status [OK 0/79] - Checking for AVM25's status [OK 0/126] - Checking for AVM78's status [OK 0/109] - Checking for AVM84's status [OK 0/45]

- Enter the username to connect via ssh to the remote server: username - Enter the password for the OS admin user: password - Enter the password for OS root user: password- Checking remote server 'IP-address' [OK]- Removing the database from IP-address. This might take a while..- Checking if all needed OS components exist and executable [OK]- About to remove the current database installation - Verifying user oracle exists [EXISTS] - Removing oracle cron jobs [OK] - About to shutdown the database [OK] - Removing '/export/home/oracle' [OK] - Removing user 'oracle' [OK]- Successfully removed the database [OK]CISCO_ORACLE_INSTALL_ENDED [OK]..

Step 5 If the remote uninstallation fails, the following error message is returned:

*** ERROR: Failed to uninstall Prime Network's internal database ***Try to uninstall the database separately, by executing as OS user 'root'cd <network-home-dir>/local/scripts ; perl uninstall_ana_db.pl <network-user> <network-home-dir>Once done, hit the 'Enter' key to continue or 'Ctrl C' to quit


OL-24641-01


Do the following:

a. As the root user, enter the following commands:

cd Network-home-directory/local/scripts perl uninstall_ana_db.pl network-user Network-home-directory

b. Press the Enter key to continue with the Cisco Prime Network uninstallation.


OL-24641-01

Installing the Cisco Prime Network 3.8 Gateway With an … · database owner, regardless of whether...

Documents

Transcript of Installing the Cisco Prime Network 3.8 Gateway With an … · database owner, regardless of whether...