Installation Guide for Cisco Virtual Network Data Server 2€¦ · The Cisco implementation of TCP header compre ssion is an adaptation ... Scorec ard, iQuick Study, LightStr eam,

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Installation Guide for Cisco Virtual Network Data ServerRelease 2.1

Customer Order Number: Text Part Number: OL-14565-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Installation Guide for Cisco Virtual Network Data Server© 2007 Cisco Systems, Inc. All rights reserved.

iInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

C O N T E N T S

Preface vii

Planning Your Installation 1-1

Installation Workflows 1-1

First-Time Installation 1-2

Update Installation 1-2

Upgrading Licenses 1-3

Registering Cisco Virtual Network Data Server 1-4

Registration Information 1-4

Selecting Host Computers 1-5

Product Licensing 1-5

Restricted and Unrestricted Licenses 1-6

Selecting the License Type 1-6

Floating Mode 1-6

How Licensing Types and Modes Affect Who Can Use a License 1-7

Licensing Requirements 1-8

Licensing Examples 1-8

System Requirements 2-1

Cisco Virtual Network Data Server: System Requirements 2-1

Supported Platforms 2-1

Required System Patches 2-2

Windows and Linux System Configuration 2-3

Supported Web Browsers 2-3

Contents

iiInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

Other Requirements 2-4

Installing Cisco Virtual Network Data Server on Windows 3-1


Account Permissions 3-2

Notes on Installing Data Storage Server 3-2


First-Time Cisco VNDS Installation (Windows) 3-3

Update Cisco VNDS Installation—Standard (Windows) 3-4

Update Cisco VNDS Installation—With an Existing Oracle Database (Windows) 3-4

Important Update Information 3-5

Database Contents 3-6

Migration of Product Configuration 3-6

Preparing for an Update Installation 3-7

Device and Platform Info Table 3-8

Group Data 3-9

Utilization Data 3-11

Authentication and User Accounts 3-12

Notification Settings 3-13

Verifying the Database Password 3-14

Installing Cisco Virtual Network Data Server 3-16

Verifying the Data Storage Server Configuration 3-28

Verifying the Cisco VNDS Software Installation 3-30

Finalizing the Update 3-32

Collecting Oracle Database Access Information 3-33

Configuring Cisco VNDS to Use the Oracle Database 3-35

Configuring the Oracle Database for Cisco VNDS 3-38

Modifying Oracle Database Parameters 3-42

iiiInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

Contents

Verifying the Oracle Configuration for Cisco VNDS 3-43

Locating an Oracle Database Net Service Name 3-45

Installation Troubleshooting 3-48

Troubleshoot Installation of Cisco VNDS Software 3-48

Troubleshoot Installation of Data Storage Server (PostgreSQL) 3-50

Manually Install Data Storage Server (PostgreSQL) 3-52

Configure PostgreSQL Database for Cisco VNDS 3-53

Installing Cisco Virtual Network Data Server on Linux 4-1


Account Permissions 4-2


First-Time Cisco VNDS Installation (Linux) 4-2

Update Cisco VNDS Installation—Standard (Linux) 4-3

Update Cisco VNDS Installation—With an Existing Oracle Database (Linux) 4-4

Important Update Information 4-5

Database Contents 4-5

Migration of Product Configuration 4-5

Preparing for an Update Installation 4-6

Device and Platform Table Info 4-7

Group Data 4-8

Authentication and User Accounts 4-9

Notification Settings 4-10

Verifying that the Host Meets Minimum System Requirements 4-12

Verifying the Database Password 4-13

Installing Cisco Virtual Network Data Server 4-15

Licensing Notes 4-26

Verifying Data Storage Server Configuration 4-27

Contents

ivInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

Verifying the Cisco VNDS Software Installation 4-29

Finalizing the Update 4-32

Collecting Oracle Database Access Information 4-33

Configuring Cisco VNDS to Use the Oracle Database 4-35

Configuring the Oracle Database for Cisco VNDS 4-38

Modifying Oracle Database Parameters 4-41

Verifying the Oracle Configuration for Cisco VNDS 4-43

Locating an Oracle Database Net Service Name 4-45

Managing Licenses 5-1

Using the License Manager 5-2

Adding a License 5-3

Obtaining a Username and Password 5-3

Preparing the License Directory 5-4

Upgrading a License 5-4

Getting an Upgrade Authorization 5-5

Adding a Module to the Product Options List 5-6

Deregistering a License 5-7

Refreshing a License 5-7

License Operations 5-8

Adding a License (Express Method) 5-8

Adding a License (Browser Method) 5-9

Deregistering a License (Express Method) 5-12

Deregistering a License (Browser Method) 5-13

Technical Support for Licensing Operations 5-16

Uninstalling Cisco Virtual Network Data Server 6-1

Removing Cisco VNDS Oracle Database Contents (Optional) 6-1

Uninstalling Cisco VNDS (Windows) 6-3

vInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

Contents

Uninstalling Cisco VNDS on Windows (Standard) 6-4

Removing All Cisco VNDS Elements (Advanced) 6-5

Removing Prior Cisco VNDS Release After Software Update (Windows) 6-7

Uninstalling Cisco VNDS (Linux) 6-8

Uninstalling a License Server 6-9

Uninstalling the Data Storage Server 6-11

Known Issues A-1

Contents

viInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

viiInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

Preface

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Preface

viiiInstallation Guide for Cisco Virtual Network Data Server

OL-14565-01

C H A P T E R

1-1Installation Guide for Cisco Virtual Network Data Server

OL-14565-01

1Planning Your Installation

The installation package for Cisco Virtual Network Data Server solution comprises the application software, Readme, and Installation Guide (this document). It is provided on a single DVD.

We strongly recommend that you review the Readme document. It contains important information about new features, enhancements, and significant changes from the previous release of Cisco VNDS. You can download the latest version of the Readme at http://www.cisco.com/en/US/products/ps6363/prod_release_notes_list.html.

Installation WorkflowsThere are two possible workflows for installing Cisco VNDS, depending on your situation:

• First-Time Installation, page 1-2—Use this workflow to install Cisco VNDS for the first time.

• Update Installation, page 1-2—Use this workflow to update from Cisco VNDS 2.0.x to the current release.

Note If you are using Release 1.x software, you must update to Release 2.0 and register that product before you update to Release 2.1. To update from Release 1.1, see the Installation Guide for Cisco Virtual Network Data Server 2.0 at http://www.cisco.com/en/US/products/ps6363/prod_installation_guides_list.html.

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

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

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

Chapter 1 Planning Your Installation Installation Workflows


OL-14565-01

For additional information regarding software updates, known issues, and support information, please visit the Cisco Solutions Quick Support page (http://www.opnet.com/support/cisco_qsp.html).

First-Time InstallationYou should perform a first-time installation only if no prior version of Cisco VNDS is installed on your computer. Table 1-1 lists the phases of the installation process.

Note We recommend that you do the steps in the order listed in this table.

Update InstallationYou should perform an update installation only if a 2.0.x version of Cisco VNDS exists on your computer and you want to update it to the current version.

Table 1-1 First-Time Installation: Workflow

Description Reference

Step 1 Register your Cisco Network Analysis product

Registering Cisco Virtual Network Data Server, page 1-4

Step 2 Determine the host computers Selecting Host Computers, page 1-5

Step 3 Determine licensing options Product Licensing, page 1-5

Step 4 Verify system requirements System Requirements, page 2-1

Step 5 Install Cisco Virtual Network Data Server Installing Cisco Virtual Network Data Server on Windows, page 3-1

Installing Cisco Virtual Network Data Server on Linux, page 4-1

Step 6 Add a Virtual Network Data Server license Adding a License, page 5-3

http://www.opnet.com/support/cisco_qsp.html


OL-14565-01

Chapter 1 Planning Your Installation Upgrading Licenses

Note If Release 2.0 is installed and you want to carry forward your product settings, you must update to Release 2.0.1 or 2.0.2 before you update to the current version.

Note We recommend that you perform the steps in the order listed in Table 1-2.

Upgrading LicensesIf you have a Restricted license and want to upgrade it to an Unrestricted license, refer to the “Upgrading a License” section on page 5-4.

Table 1-2 Update Installation: Workflow


Step 1 Verify system requirements System Requirements, page 2-1

Step 2 Install the current release of Cisco VNDS Installing Cisco Virtual Network Data Server on Windows, page 3-1

Installing Cisco Virtual Network Data Server on Linux, page 4-1

Step 3 Refresh licenses Refreshing a License, page 5-7

Step 4 Remove the previous Cisco VNDS installation (optional)

Removing Prior Cisco VNDS Release After Software Update (Windows), page 6-7

Uninstalling Cisco VNDS (Linux), page 6-8

Chapter 1 Planning Your Installation Registering Cisco Virtual Network Data Server


OL-14565-01

Registering Cisco Virtual Network Data ServerBefore you can install Cisco VNDS, you must register your product. After you register your product, you will receive an e-mail with a username, password, and group ID number. You will need this information when you install your product licenses (as described in the “Adding a License” section on page 5-3.)

Note If you are updating from Release 1.x, make sure you registered Cisco VNDS 2.0 when you updated to that release.

Note If you previously registered Cisco VNDS 2.0 or later, you do not need to register again. For Cisco VNDS 2.1, continue using the same credentials.

Note By accessing or using the products in this package, you agree that your use of such products is governed by the terms and conditions of the Cisco Systems, Inc. Software License and any applicable supplemental license agreement.

To review the terms of the Software License before accessing or using the products, read the copy in the Cisco Information Packet that accompanies the product or online at:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/cetrans.htm

To obtain the license activation credentials, log on to one of the websites listed below and follow the registration instructions. The Product Authorization Key (PAK) attached to your Software License Claim Certificate is required for the registration process. After registering, retain your Claim Certificate for future reference.

Registration InformationUse this URL if you are a registered user of Cisco.com:

http://www.cisco.com/go/license

Use this URL if you are not a registered user of Cisco.com:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/cetrans.htm

http://www.cisco.com/go/license


OL-14565-01

Chapter 1 Planning Your Installation Selecting Host Computers

http://www.cisco.com/go/license/public

You should receive the activation credentials and additional installation instructions through e-mail within one hour of registration. If you experience problems with the registration websites or if you have additional questions, contact the licensing department through e-mail at [email protected], or open a service request over the telephone by using one of these numbers:

• Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)

• EMEA: +32 2 704 55 55

• USA: 1 800 553-2447

You can find a complete list of Cisco TAC contacts at this URL:

http://www.cisco.com/techsupport/contacts

Selecting Host ComputersBefore installing Cisco Virtual Network Data Server, select the computers where you want to install the software. The host computer must meet the system requirements described in the System Requirements chapter.

After you complete this step, return to the “Installation Workflows” section on page 1-1.

Product LicensingCisco VNDS requires a corresponding license to be installed and available to that program. On startup, the program contacts a License Server and requests a license; if it does not obtain a license, the program does not start. The License Server is a daemon/process that runs on the host where a license is installed; it handles license requests from component programs. See the “Licensing Examples” section on page 1-8 for more information.

After you determine the licensing configuration you want, return to the “Installation Workflows” section on page 1-1.

http://www.cisco.com/go/license/public

http://www.cisco.com/techsupport/contacts

Chapter 1 Planning Your Installation Product Licensing


OL-14565-01

Restricted and Unrestricted LicensesYou can buy either Restricted or Unrestricted versions of the Cisco VNDS program licenses. This distinction determines the scope of authorized users:

• A Restricted license confines the user of a program to one IP network by default subnet class. This means that the licensed program can be used only if the License Server is in the same classful IP network. IP network connectivity between the program and server is required.

• An Unrestricted license offers the most flexibility for organizations that operate multiple IP networks (as defined by default subnet class). Users can access licenses from within the same classful IP network as the License Server as well as from up to 100 additional IP networks. These networks must be specified to the licensing department before the license is installed.

Selecting the License TypeWhen you install a component program, the installer asks you to specify the licensing mode. The options are:

• Floating/Local (“Serve licenses from a license server on this computer”)—If you select this option, the program will request a license from a License Server running on the local computer.

• Floating/Remote (“Access licenses from a remote server”)—If you select this option, the program will request a license from a License Server running on a remote computer. (The installer also prompts you for the host name of the remote server.)

Floating mode enables multiple users to share a license for Design and Analysis. The following section describes Floating mode in more detail.

Floating ModeFloating mode enables multiple users to share a license for Cisco VNDS. On startup, the program communicates with the License Server automatically and “checks out” a license. When the program closes, it returns the license to the


OL-14565-01


License Server. Then the license is available for another Cisco VNDS user to start the program and check out the license. In Floating mode, the license is not “node-locked,” but can “float” to different computers.

Note Multiple users cannot share the same Cisco VNDS license concurrently. Multiple concurrent Cisco VNDS sessions require an equivalent number of program licenses.

Although the Cisco VNDS license server must use Floating mode, its license is not shared among multiple users. Cisco Virtual Network Data Server operates automatically, “consuming” its license continually. System administrators do not need a license to log in to and operate the system.

How Licensing Types and Modes Affect Who Can Use a LicenseTable 1-3 illustrates how the different license modes and restriction types determine which applications can use a specific license.

Table 1-3 Licensing Types and Modes

License Mode Used by Installed Program

Restriction Type of Installed License Client Applications That Can Use the License on the License Server

Applications on the Same Host as the License Server

Applications in the Same Classful IP1 Network as the License Server

1. Classful IP network refers to the classic “A”, “B”, and “C” IP network classes. For example, if the License Server is installed on a workstation that has a class “B” IP network address, then all workstations with the same class “B” address as the License Server are considered to be on the same classful IP network as the License Server.

Applications in a Different Classful IP Network from the License Server

Floating Restricted Yes Yes No

Floating Unrestricted Yes Yes Yes



OL-14565-01

Licensing RequirementsNote the following requirements:

• You must add the corresponding license as described in the “Adding a License” section on page 5-3. Installing a program and specifying the licensing options does not install the license itself.

• If you specify Floating (remote) licensing for a program, the specified License Server must be accessible (via a TCP/IP network) to that program, as described in the “Restricted and Unrestricted Licenses” section on page 1-6.

Licensing ExamplesThis section shows some examples of how you can install and configure licenses in your network.

In Table 1-4, all licenses are installed on one host (VNDS_client), which acts as the only License Server in the network. The local Cisco VNDS program uses Floating/Local mode, while the remote programs use Floating/Remote mode. This type of setup is recommended; because there is only one License Server, it is easier to manage your licenses and configure programs.

Table 1-4 Licensing Example 1

LOCAL HOST CONFIGURATION

LICENSING OPTION SETTINGS FOR INSTALLED PROGRAM

Installed Program Host Name Licenses Installed on HostLicense Server

License Mode

Cisco Audit and Analysis AA_client_1 — VNDS_client Floating / Remote

Cisco Audit and Analysis AA_client_2 — VNDS_client Floating / Remote

Cisco VNDS VNDS_client(License Server)

Cisco VNDSCisco Audit and Analysis

(local host) Floating / Local


OL-14565-01


In Table 1-5, the Cisco Audit and Analysis program is installed on AA_client_1 and two other hosts. Each installation requests a license from AA_client_1. (Keep in mind that if only one license is installed on the host, only one Cisco Audit and Analysis session can run at a time.) The two other programs are installed on separate hosts which also act as License Servers.





License Mode

Cisco Audit and Analysis AA_client_1 (License Server)

Cisco Audit and Analysis (local host) Floating / Local

Cisco Audit and Analysis AA_client_2 — AA_client Floating / Remote

Cisco Audit and Analysis AA_client_3 — AA_client Floating / Remote


Cisco VNDS (local host) Floating / Local



OL-14565-01

In Table 1-6, the programs are installed on separate hosts with their respective licenses. Cisco Audit and Analysis uses Standalone mode, while Cisco VNDS request licenses from local License Servers.

In Table 1-7, each program has its license installed on the same computer and uses Floating/Local mode.





License Mode

Cisco Audit and Analysis AA_client_1 Cisco Audit and Analysis (local host)

Standalone


Cisco VNDS (local host)

Floating / Local





License Mode

Cisco Audit and Analysis

Cisco VNDS

CAS_client(License Server)

Cisco Audit and Analysis

Cisco VNDS

(local host)

(local host)

Floating / LocalFloating / Local

C H A P T E R


OL-14565-01

2System Requirements

This chapter describes the system requirements for the individual components in Cisco Virtual Network Data Server. We recommend that, before you start to install Cisco VNDS, you verify that your computer hardware and software meet the requirements outlined in this chapter.

Cisco Virtual Network Data Server: System Requirements

Supported Platforms

Vendor Series1

1. Cisco VNDS is supported on the English-language version of each operating system.

Microsoft2

2. Cisco VNDS is not supported on 64-bit editions of Windows operating systems, nor on Windows 2003 Web Edition.

Windows Server 20033

Windows XP Professional

Windows 2000 Server

Windows 2000 Professional

Red Hat Red Hat Enterprise Linux ES 4 (v2.6 Kernel)

Chapter 2 System Requirements Cisco Virtual Network Data Server: System Requirements


OL-14565-01

Required System Patches

To determine the service pack installed on your Windows system, run winver.exe:

Step 1 Select Run from the Windows Start menu.

Step 2 Type in the command winver and click OK. The About Windows window appears and shows the version and service pack level installed.

3. Cisco VNDS is supported on Windows Server 2003 instances running in virtual machines hosted by VMware ESX Server versions 2.0 and 3.0. Although Cisco VNDS is supported under VMware, we most strongly recommend deploying on a dedicated machine to ensure more predictable performance and to lower the cost of maintenance.

System requirements in terms of memory, CPU, and disk space for the Cisco VNDS running in a virtual machine instance within VMware are the same as those for a dedicated server. Resources (including CPU, disk, and memory) within VMware must be statically allocated for the virtual machine instance to meet the system requirements identified for dedicated servers. Even with static allocation of VMware resources, however, you might experience significant and unpredictable performance degradation because certain resources such as the memory and disk I/O subsystems are shared among other virtual machines hosted on the VMware server and cannot easily be statically allocated to Cisco VNDS.

Vendor OS Patch Number/Name

Microsoft Windows 2000 Server Service Pack 2 minimum

Windows XP Professional N/A

Windows Server 2003 N/A


OL-14565-01

Chapter 2 System Requirements Supported Web Browsers

Windows and Linux System Configuration

Note Cisco VNDS does not operate on machines with the Intel Itanium processor. To check the processor used by your Windows computer, right-click on the My Computer desktop icon and choose Properties.

Supported Web BrowsersOne of the following web browsers is required:

• Mozilla Firefox 2.0 and later

• Microsoft Internet Explorer 6.0 and later

Processor1

1. A dual-processor configuration is recommended.

RAM2

2. Cisco VNDS performance will improve with more available memory as network size increases.

Disk3

3. The actual amount of disk space required depends on network size and data-retention practices.

FSB4

4. Front-Side Bus (FSB) speed affects the speed of data transfer to and from the Cisco VNDS database; faster bus speeds will improve Cisco VNDS performance.

Windows Dual Core Intel Xeon 30704MB Cache, 2.66 GHz (minimum)

3 GB 250 GB 1066 MHz

Dual Processor, Dual Core Intel Xeon Model 51604MB Cache, 3.0 GHz (recommended)

4 GB 500 GB 1333 MHz

Linux Quad Core Intel Xeon X32302x4MB Cache, 2.66 GHz (minimum)

3 GB 250 GB 1066 MHz

Dual Processor, Quad Core Intel Xeon Model X53552x4MB Cache, 2.66 GHz (recommended)

4 GB 500 GB 1333 MHz

Chapter 2 System Requirements Other Requirements


OL-14565-01

Other RequirementsCisco VNDS 6.0 installs its own Data Storage Server and no longer requires Oracle to provide data storage. If you have Oracle, you can configure Cisco VNDS to use it, subject to the following restrictions:

• Cisco VNDS requires a dedicated Oracle database installation and dedicated database instance that cannot be shared with other applications. The preferred configuration includes a dedicated Oracle database installation local to the system on which Cisco VNDS is installed.

• A shared Oracle instance where applications other than Cisco VNDS share/access the database or database instance are NOT supported.

• An Oracle database that is running on a system physically remote from or on a separate LAN from the Cisco VNDS system is NOT supported.

Table 2-1 Requirements for Oracle Database1

1. Contact Oracle Corporation for information about Oracle 9i and 10g installation and system requirements.

Platform Supported Version Required Database Character Set2

2. The supported national character set is: AL16UTF16. For international customers: Cisco VNDS 6.0 might not operate correctly when used with Oracle databases that have been configured with international, or Unicode (AL32UTF8), database character sets.

Windows Oracle 9i Release 2 (version 9.2.0.1 or higher)

Oracle 10g Release 2 (version 10.2.0.1 or higher)

WE8MSWIN1252

Linux Oracle 9i Release2 (version 9.2.0.1 or higher)

Oracle 10g Release 2 (version 10.2.0.1 or higher)

WE8ISO8859P1

C H A P T E R


OL-14565-01

3Installing Cisco Virtual Network Data Server on Windows

This chapter describes how to install the Cisco Virtual Network Data Server (Cisco VNDS) software on Windows.

Note Release 2.1 of Cisco Virtual Network Data Server installs version 6.0 of the Cisco VNDS software. Release 2.0.2 used Cisco VNDS version 4.5 and Release 2.0.1 used Cisco VNDS version 4.0.3.

System RequirementsThe host PC for Cisco Virtual Network Data Server must meet minimum system requirements. These requirements are documented in Cisco Virtual Network Data Server: System Requirements, page 2-1.

Caution If the host system does not meet minimum requirements, do not install Cisco Virtual Network Data Server.

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Account Permissions


OL-14565-01

Account PermissionsThe account used to install Cisco VNDS 6.0 software on a Windows host must have full administrative privileges. Additional permissions might be required to perform specific steps in your installation; these permissions are described in the relevant procedures.

Notes on Installing Data Storage ServerThe following requirements must be met in order for the Cisco VNDS installer to successfully install the Data Storage Server on a Windows host:

• The installer must be able to create the dssowner user account on the Cisco VNDS host system. Ensure that the password you specify for this account meets policy restrictions on the Cisco VNDS host system.

• The “Secondary Logon” (or equivalent) Windows service must be started on the Cisco VNDS host system. For Windows 2000, this service might be named “RunAs Service”.

• The root installation directory that you specify for the Data Storage Server must be a local NTFS disk drive.

• The dssowner user must have read/execute permissions for cmd.exe on the Cisco VNDS host system.

• The dssowner user must have read permissions to the root drive of the PostgreSQL database directory on the Cisco VNDS host system.

• If you use remote desktop to install Cisco VNDS, you must connect to the Cisco VNDS host using a console session.

Installation WorkflowsThis chapter covers the installation scenarios you might encounter with Cisco Virtual Network Data Server on Windows. The procedures you must follow depend upon whether this is an initial Cisco VNDS installation or an update to an existing installation.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Installation Workflows

Cisco VNDS includes an embedded Data Storage Server. If the host system does not already have the Data Storage Server installed, it will be installed with the Cisco VNDS software.

If you are updating Cisco Virtual Network Data Server and you have an existing Oracle installation and database instance dedicated for Cisco VNDS, you can configure Cisco VNDS 6.0 to use that dedicated Oracle installation. If you are updating and do not have a dedicated Oracle installation and database instance, you should use Cisco VNDS’s Data Storage Server.

Select the installation workflow appropriate for your circumstances. Follow the procedures in that workflow to install or update Cisco Virtual Network Data Server.

• First-Time Cisco VNDS Installation (Windows), page 3-3

• Update Cisco VNDS Installation—Standard (Windows), page 3-4

• Update Cisco VNDS Installation—With an Existing Oracle Database (Windows), page 3-4

If you run into trouble during installation of Cisco VNDS, consult the “Installation Troubleshooting” section on page 3-48.

First-Time Cisco VNDS Installation (Windows)If you are installing Cisco Virtual Network Data Server for the first time, follow the workflow in Table 3-1.

Table 3-1 Cisco VNDS First-Time Installation: Workflow


Step 1 Install the Cisco VNDS software. Installing Cisco Virtual Network Data Server, page 3-16

Step 2 Verify the Data Storage Server configuration. Verifying the Data Storage Server Configuration, page 3-28

Step 3 Verify the Cisco VNDS software installation. Verifying the Cisco VNDS Software Installation, page 3-30

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Installation Workflows


OL-14565-01

Update Cisco VNDS Installation—Standard (Windows)If you are updating a previous installation of the Cisco Virtual Network Data Server software and will be using the Data Storage Server provided with Cisco VNDS, follow the workflow in Table 3-2.

Update Cisco VNDS Installation—With an Existing Oracle Database (Windows)

If you are updating a previous installation of the Cisco Virtual Network Data Server software and want to continue using a dedicated installation of Oracle for Cisco VNDS, follow the workflow in Table 3-3. (If you do not have a dedicated Oracle installation, follow the Update Cisco VNDS Installation—Standard (Windows) workflow.)

Note Shared Oracle installations are not supported.

Table 3-2 Cisco VNDS Update Installation: Workflow


Step 1 Read the update information. Important Update Information, page 3-5

Step 2 Prepare to migrate information from the previous installation.

Preparing for an Update Installation, page 3-7

Step 3 Verify the database password. Verifying the Database Password, page 3-14


Step 5 Verify the Data Storage Server configuration. Verifying the Data Storage Server Configuration, page 3-28


Step 7 Finish migrating information from the previous installation.

Finalizing the Update, page 3-32


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Important Update Information

The account you use to configure Cisco VNDS to use Oracle must have the following properties:

• Full administrative privileges

• ORA_DBA privileges

• Full control access over the Oracle installation directory tree

Important Update InformationThis section covers the following topics:

• Database Contents, page 3-6

Table 3-3 Cisco VNDS Update Installation for Existing Oracle Database: Workflow







Step 5 Collect Access Information for the Oracle Database.

Collecting Oracle Database Access Information, page 3-33

Step 6 Configure Cisco VNDS to Use Oracle. Configuring Cisco VNDS to Use the Oracle Database, page 3-35

Step 7 Configure the Oracle Database for Cisco VNDS.

Configuring the Oracle Database for Cisco VNDS, page 3-38

Step 8 Verify the Oracle Configuration for Cisco VNDS.

Verifying the Oracle Configuration for Cisco VNDS, page 3-43




Chapter 3 Installing Cisco Virtual Network Data Server on Windows Important Update Information


OL-14565-01

• Migration of Product Configuration, page 3-6

Database Contents

Note The network topology and configuration data in the Cisco VNDS database cannot be retained during a software update. You must recreate the network topology and configuration after you update.

The contents of the Cisco VNDS database cannot be retained during a software update. However, you can preserve certain data by exporting it to text files prior to the software update. See the “Preparing for an Update Installation” section on page 3-7 for more information.

Migration of Product Configuration

Caution Do not rename or uninstall the existing Cisco VNDS release until after your update is complete and you have migrated product configuration. If a Cisco VNDS 4.0.3 or 4.5 installation is detected by the installer, you will have the option to migrate Cisco VNDS configuration settings from the existing software installation to the new 6.0 installation.

When the Cisco VNDS 6.0 installer detects an existing Cisco VNDS 4.0.3 or 4.5 installation, it offers to migrate the Cisco VNDS configuration to the new installation. The installer provides update assistance by

• migrating product settings such as adapter resources, schedule, and other project properties from your previous installation to your new installation.

• copying text files from your previous Cisco VNDS installation directory to the Cisco VNDS 6.0 installation directory. If you want the installer to automatically copy the device info file to your new installation, you must perform the “Exporting Device and Platform Info Table to a Text File” procedure on page 3-8.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Preparing for an Update Installation

• offering to export utilization data to text files for subsequent import into Cisco VNDS 6.0. (This option is only available if you choose to perform product migration.) Because these files can be very large, the installer does not try to copy exported utilization data files to the Cisco VNDS 6.0 installation directory. After you update, you must import your network topology before you import the exported utilization data using the Generic Interface Utilization Import adapter.

Although some configuration might be required in your Cisco VNDS 6.0 installation after the installer completes, product migration minimizes the amount of post-installation configuration. If you are not satisfied with the product settings after the installer performs migration of product configuration, the default product settings can be restored in your Cisco VNDS 6.0 installation.

Recommendations when migrating:

• Install Cisco VNDS 6.0 to use the same temp directory that you used for your previous installation.

• After you update, double-check settings for any adapters for which you had created additional cloned servers.

Note See the Readme to learn about release-specific product migration issues.

Note If you will not migrate product configuration, you should use the same database password that you used in your previous installation—otherwise you will have to reenter encrypted passwords in Cisco VNDS 6.0 after your update is complete. This applies to passwords in an exported device info file as well as passwords defined in adapter resources.

Preparing for an Update Installation

Caution Do not configure the database for use by Cisco VNDS 6.0 until you have exported data that you want to preserve.



OL-14565-01

This section covers the following topics:

• Device and Platform Info Table, page 3-8

• Group Data, page 3-9

• Utilization Data, page 3-11

• Authentication and User Accounts, page 3-12

• Notification Settings, page 3-13

Device and Platform Info Table

Caution You must export Device and Platform Info table to a text file if you want to preserve the device entries when you update to Cisco VNDS 6.0. Do not preserve the Device and Platform Info table unless you run Cisco VNDS’s direct collection adapters.

The Device and Platform Info table must be exported to a file if you want to retain the device entries when you update to Cisco VNDS 6.0. Export the Device and Platform Info table if you use the following adapters:

• Device Config File Collection

• Device MIB Configuration Import

• Device MIB MPLS TE Import

• MIB-Based Interface Utilization Import

Follow this procedure to export the Device and Platform Info table to a text file.

Exporting Device and Platform Info Table to a Text File

Step 1 Open the Management Console.

Step 2 Select the Device Info File tab.

Step 3 Note the value of the Device Info File Location property.

The default value for this property is <install_dir>\input\DeviceInfo\deviceInfo.txt

Step 4 Open the Device and Platform Info window, as follows:


OL-14565-01


From the Cisco VNDS Control Panel menu bar, choose Configuration > Open Device and Platform Info.

The Device and Platform info window appears.

Step 5 Click the Export button.

Step 6 Move to the directory specified in the Device Info File Location property and enter the filename specified in the Device Info File Location property (for example: deviceInfo.txt).

Step 7 When the export is complete, verify that the device info file you exported is stored in the path and filename specified by the Device Info File Location property.

Note Import the device info file into your Cisco VNDS 6.0 project after you complete your update. This file is copied automatically to your Cisco VNDS 6.0 installation if you perform product migration during installation.

Group Data

Caution You must export group data to a text file if you want to preserve it when you upgrade to Cisco VNDS 6.0.

When you export group data, three files named grp_list.txt, grp_mbrs.txt, and subgrp_mbrs.txt are written to the directory from which you run the export command. These files contain the groups, group members, and subgroups, respectively.

The procedure that you will follow depends on the version of Cisco VNDS currently installed and the database it is configured to use:

• Exporting Group Data to Files (Cisco VNDS 4.x with Oracle), page 3-10

• Exporting Group Data to Files (Cisco VNDS 4.5 with PostgreSQL), page 3-10

If you use an Oracle database for a Cisco VNDS 4.0.3 or 4.5 software installation, use the following procedure to export group data.



OL-14565-01

Exporting Group Data to Files (Cisco VNDS 4.x with Oracle)

Step 1 Open a command prompt and move to the Cisco VNDS 4.0.3 or 4.5 installation directory: C:\Cisco\VNDServer\<version>_<build>.

Step 2 Enter the following commands:

vnes_grp_list_export.bat <DB account> <DB password>

vnes_grp_mbrs_export.bat <DB account> <DB password>>

vnes_subgrp_mbrs_export.bat <DB account> <DB_password>

where <DB account> is the account used by the Cisco VNDS 4.x installation to access the Oracle database and <DB password> is the password for that account.

Files are written to the current directory as:

grp_list.txt

grp_mbrs.txt

subgrp_mbrs.txt

If you use a PostgreSQL database for a Cisco VNDS 4.5 software installation, use the following procedure to export group data.

Exporting Group Data to Files (Cisco VNDS 4.5 with PostgreSQL)

Step 1 Open a command prompt and move to the following directory in the Cisco VNDS 4.5 installation directory: <install_dir>\database\postgresql.

Step 2 Enter the following command:

<DSS_bindir>\psql -U dssuser -d vnes -f group_export.sql

where <DSS_bindir> is the bin directory for the PostgreSQL installation. For example, C:\Cisco\DSS\PostgreSQL\8.2\bin.

You are prompted to enter the password for the dssuser account.

Step 3 Enter the password for the dssuser account.


grp_list.txt

grp_mbrs.txt


OL-14565-01


subgrp_mbrs.txt

To use the exported files in the Cisco VNDS 6.0 installation, copy them to the new installation and configure the ASCII Generic Data Import adapter to import the group data files. After you have created a network topology in Cisco VNDS 6.0, use the ASCII Generic Data Import adapter to import group data. Refer to the online documentation for more information regarding use of the ASCII Generic Data Import adapter.

Utilization Data

Caution You must export utilization data if you want to preserve it when you update to Cisco VNDS 6.0. You can manually export this data before you update (using the following procedure) or let the installer offer the option to export it if you choose to perform product migration from a Cisco VNDS 4.0.3 or 4.5 installation.

Use the following procedure to export utilization data. This procedure is not required if you will migrate product configuration during installation.

Exporting Interface Utilization Data to Files

Note The export of utilization data might take a significant amount of time to complete. The amount of time required depends on the amount of interface utilization data.

Step 1 Open a command prompt and move to the Cisco VNDS 4.0.3 or 4.5 installation directory: C:\Cisco\VNDServer\<version>_<build>.


vnes.bat [/path <output_dir>] EXP_UTIL

where [/path <output_dir>] is an optional argument specifying the output directory for the exported utilization files. For example:

vnes.bat /path C:\\CISCO\util EXP_UTIL



OL-14565-01

Files are written to the specified output directory.

To use the exported files in the Cisco VNDS 6.0 installation, copy them to the new installation. After you have created a network topology in Cisco VNDS 6.0, run the Generic Interface Utilization Import adapter to import the utilization data files. Refer to the online documentation for more information regarding use of the Generic Interface Utilization Import adapter.

Authentication and User AccountsNeither authentication settings nor local user accounts migrate when you update. Use the following procedure to record authentication settings.

Recording Authentication Settings

Step 1 Log into the Management Console as a user with administrative privileges.

Step 2 Select the Users page.

Step 3 Note user names and the roles for each.

Note This step is not required if you will manually migrate local user accounts after you update. Do not uninstall the previous release until after you successfully migrate.

Choose a username from the Select User pull-down menu to view the roles configured for that user.

Step 4 Click on the Server link.

Step 5 If RADIUS or TACACS+ is selected, note the Authentication Server settings:

• Server Host

• Server Port

• Shared Secret:

• Auth Type:

• Message Trace


OL-14565-01


• Timeout

After you update, you can perform a manual procedure to migrate local user accounts. After you have migrated local user accounts, you can configure authentication parameters if you use remote authentication, as described in the “Creating Local User Accounts and Configuring Authentication” procedure on page 3-33.

Notification SettingsThe Notification settings do not migrate when you perform an update installation. Use the following procedure to record Notification settings.

Recording Notification Settings


Step 2 Select the Notification page.

Step 3 Write down the values of the following properties:

• Selected notifications

Note The Selected notifications list is set to Cisco VNDS 6.0 defaults after the software update. When you are ready to resume automated operation, you must set the Selected notifications list to your desired values using the Management (Mgmt) page in the Web Console. Because new software might contain additional notification types, examine the available notification types when deciding which notifications you want to receive in your 6.0 installation.

• Email Recipients

– To

– Cc

• Email Parameters

– SMTP Server

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Database Password


OL-14565-01

– SMTP Port

– Sender

– Subject prefix

– SMTP Username

– SMTP Password

Note You can enter the values for Email Recipients and Email Parameters in the Cisco VNDS 6.0 installer or configure these properties after the update is complete.

The installer provides the opportunity for you to enter values for Email Recipients and Email Parameters; however, you must still configure Selected notifications after the update is complete.

Verifying the Database PasswordYou must enter the database password when you run the Cisco VNDS 6.0 installer. Before you start the installer, verify that you have the correct password.

Depending on which database you have, use one of the following procedures to verify the password:

• Verifying Database Password (PostgreSQL), page 3-14

• Verifying Database Password (Oracle), page 3-15

Verifying Database Password (PostgreSQL)

Use this procedure if your Cisco VNDS software installation uses the Cisco VNDS Data Storage Server (PostgreSQL).

Step 1 Choose Start > Programs > PostgreSQL 8.2 > Command Prompt.

A command prompt opens.

Step 2 Enter the psql command to connect to the database.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Database Password

• If the Data Storage Server listens on the default port, enter the following command:

psql -U dssuser -d vnes

• If you chose a non-default listening port for the Data Storage Server when you installed Cisco VNDS, enter the following command:

psql -U dssuser -d vnes -p <port>

You are prompted for the password.


A welcome message is displayed.

Note If you are unable to determine the password for the database, contact Technical Support to obtain assistance in resetting the password for the dssuser account to a known value.

Step 4 Type \q at the vnes=> prompt to quit psql.

Verifying Database Password (Oracle)

Use this procedure if your Cisco VNDS software installation uses an Oracle database.

Step 1 Open a command prompt.

Step 2 Navigate to the Cisco VNDS installation directory. For example: C:\Cisco\VNDServer\<version>_<build>.

Step 3 Verify that you can login into Oracle using the Cisco VNDS database user account.

• For a local Oracle database installation, enter the following command:

sqlplus <user name>/<password>

Use the database user name and password from Table 3-4 on page 3-34. For example, if the Cisco VNDS database user name and password are dbuser and pwd respectively, enter:

sqlplus dbuser/pwd

• For a remote Oracle database, enter the following command:

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Installing Cisco Virtual Network Data Server


OL-14565-01

sqlplus <user name>/<password>@<DB TNS Service Name>

Use the database user name, password, and TNS Service Name from Table 3-4 on page 3-34. For example, if the Cisco VNDS database user name and password are dbuser and pwd respectively, and the Database TNS Service Name is o92adata, enter:

sqlplus dbuser/pwd@o92adata

An Oracle banner, and a Connected To: message appears.

Note If you are unable to log in using the Cisco VNDS user account, consult Oracle documentation or contact Oracle Technical Support to obtain assistance in resetting the password for the Cisco VNDS user account to a known value.

Step 4 Type quit at the SQL> prompt to exit.

Installing Cisco Virtual Network Data ServerUse the following procedure to install the Cisco Virtual Network Data Server software.

Caution If you have a non-Cisco installation of PostgreSQL 8.2 installed on the host on which you will install Cisco VNDS 6.0, you must remove it before you install Cisco VNDS 6.0 or the installation of Cisco VNDS’s Data Storage Server will fail.

Installing Cisco VNDS Software (Windows)

Step 1 Log into the host as Administrator or as a user with full administrative privileges. If you are not logged in with the proper privileges, log off and then log on with an appropriate account.


OL-14565-01


Note Export the Device and Platform Info table from the Cisco VNDS database if you are updating Cisco VNDS and you use the Device Config File Collection, Device MIB Configuration Import, Device MIB MPLS TE Import, or MIB-based Interface Utilization Import adaptors. See the “Preparing for an Update Installation” section on page 3-7.

Step 2 (Update only) If Cisco VNDS is already installed on the host PC and you are updating to a new release, perform the following steps to make sure that Cisco VNDS is shut down and all processes are stopped.

a. Stop Cisco VNDS operation:

Choose Services > Stop Services from the Virtual Network Data Server Control Panel menu bar.

b. Exit Cisco VNDS:

Choose File > Exit from the Control Panel menu bar.

c. Open a command prompt and move to the Cisco VNDS installation directory (C:\Cisco\VNDServer\<version>_<build>), then enter the following command:

vnes.bat /svc_cmd stop ALL

d. Open the Windows Task Manager and select the Processes tab. If an op_monitor process is running, stop the process.

e. Use a License Manager to see if your Cisco VNDS license is still held. If the license is still held by Cisco VNDS, use the License Manager to revoke the license.

f. Go to Step 4.

Caution Do not rename or uninstall the existing Cisco VNDS release. If a Cisco VNDS 4.0.3 or 4.5 installation is present, you will have the option to migrate configuration settings from that installation to the Cisco VNDS 6.0 installation. If you uninstall the previous release before you migrate the product configuration, you must manually configure Cisco VNDS 6.0 after you update.

Step 3 (First-time installation only) If this is a first-time installation of Cisco VNDS, perform the following steps.

a. Open the Windows Service Manager.



OL-14565-01

b. Verify that the Secondary Logon service is running. For a host running Windows 2000 Professional or Windows 2000 Server, verify that the RunAs service is running.

Note If the service is not running, start it. Installation of the Data Storage Server will fail if the Secondary Logon service (or RunAs service) is not running. After Cisco VNDS installation is complete, the service can be stopped.

c. Close the Windows Service Manager.

Step 4 Start the installer:

Note If the Windows Services window is open, close it before you proceed.

Caution Virus scanning software and other security applications might prevent successful installation of Cisco VNDS software, the Cisco VNDS Data Storage Server, or both. We recommend that you disable such applications on the host system before you start the Cisco VNDS installer. You can re-enable them after successful installation of the software.

a. Insert the Cisco Virtual Network Data Server installation DVD into the DVD drive of the host PC. If the installer does not start automatically, use Start > Run to execute one of the following programs on the DVD:

cnps-vnds-2.1-win-K9.exe

or

cnps-sp-vnds-2.1-win-K9.exe

The installer displays an Introduction panel.

b. Click Next.

If an existing Cisco VNDS software installation is detected:

• A Notice reminds you to stop services and exit Cisco VNDS. Click Yes to continue or No to cancel the installation.


OL-14565-01


• A Warning notifies you that contents of the Cisco VNDS database cannot be retained during a software upgrade. Click Yes to continue or No to cancel the installation.

If Cisco VNDS’s Data Storage Server is not detected, it will be installed. A Warning is displayed. Continue with Step 5.

If a supported version of Cisco VNDS’s Data Storage Server was installed during a previous installation of Cisco VNDS software, it will be used. The Specify the Data Storage Server password panel is displayed. Go to Step 9.

Step 5 Read the Warning about installing Cisco VNDS using Remote Desktop.

• If you are using Remote Desktop to access the PC on which you will install Cisco VNDS and you are not in Console mode, click Cancel to cancel the installation. Reconnect to the system using Remote Desktop in Console mode before you run the installer.

• If you are connected to the Cisco VNDS host using Remote Desktop in Console mode or you are not using Remote Desktop to connect to the Cisco VNDS host, click OK to continue the installation.

A Note about Cisco VNDS’s Data Storage Server appears.

Step 6 Read the important information about the Data Storage Server and the accounts that the installer creates on the Cisco VNDS host.

Note If you click OK in this step, PostgreSQL will be installed to a default location on the C: drive and configured to use the default listening port. In addition, accounts will be configured with default passwords.

• Click Edit if you want to specify your own passwords for the accounts that Cisco VNDS creates or to customize the Data Storage Server listening port or installation directory. Follow this path if any of the following conditions apply to your installation:

– The Data Storage Server must be installed on a local NTFS-formatted disk drive with a minimum of 15 GB of disk space available. If the default install path does not meet these requirements, choose a different location when you do Step 7.

– If the default listening port for the Data Storage Server (port 5432) is used by another application, choose a different port when you do Step 7.



OL-14565-01

– The password for the dssowner operating system account must meet the policy restrictions of the Cisco VNDS host system. If the default password does not meet requirements for the host system, specify an acceptable password when you do Step 8.

– If you are updating from a previous version of Cisco VNDS, set the dssuser password in Step 9 to the same value as the database password that Cisco VNDS used to access Oracle in your previous installation.

Continue with Step 7.

• Click OK if you want to accept the default values displayed in the Note about Data Storage Server. (The operating system account and Data Storage Server accounts that the installer creates will have the password of CisCo123 if you accept this selection.) Go to Step 10.

Step 7 The installer prompts you for the following Data Storage Server values:

• Location—path to the Data Storage Server parent installation directory. The PostgreSQL software and data directory are installed in this parent directory.

Note The Data Storage Server must be installed on a local NTFS-formatted disk drive. Make sure you have a minimum of 15 GB of disk space available for the Data Storage Server data directory. Additional disk space might be required depending on the amount of data you store in Cisco VNDS.

• Port—port on which the Data Storage Server listens.

Note If the default listening port for the Data Storage Server (5432) is used by another application, choose a different port for the Data Storage Server to listen on.

Enter values in the Specify Data Storage Server Information panel or click Next to accept the default values.

The Specify Data Storage Server User Information panel appears.

Step 8 You are prompted to enter passwords for the dssowner and dssadmin accounts:

• dssowner—the Windows operating system user account that will run the PostgreSQL Windows service.


OL-14565-01


Note Ensure that the password for the dssowner operating system account meets policy restrictions on the Cisco VNDS host system.

• dssadmin—the administrator account for the Data Storage Server (PostgreSQL).

Enter and confirm the passwords. If you want to use the default password (CisCo123) for one or both of these accounts, enter it in the password confirmation text field(s). Click Next to continue.

The Specify the Data Storage Server password panel appears.

Step 9 You are prompted to enter the password for the dssuser account. This is the account Cisco VNDS will use to access the Data Storage Server.

Note You will need this password when you update to future versions of Cisco VNDS.

Note If you are updating from a previous Cisco VNDS installation, set the dssuser password to the same password that Cisco VNDS used to access the database in your previous installation. Verify the password if you have not already done so (see Verifying the Database Password, page 3-14).

Enter and confirm the password. If you want to use the default password (CisCo123), enter it in the password confirmation text field. Click Next to continue.

The Select Licensing Type panel appears.

Step 10 Specify the licensing scheme.

Note As you proceed, write down the license settings for future reference.

The Select Licensing Type panel provides a choice between remote and local licensing:

• Access licenses from a remote server

• Serve licenses from a license server on this computer



OL-14565-01

If you choose to serve licenses from a license server on this computer, a license server is installed with the Cisco VNDS software. See the Readme for information about the License Server installed with this version of Cisco VNDS.

Note The specified license server must have a valid license for Cisco VNDS before you can run the software.

a. Choose the licensing type, then click Next.

• If you selected remote licensing, the installer displays the Enter Server Name and Port panel. Go to Step 10b.

• If you selected local licensing, the Enter Port panel appears. Go to Step 10c.

b. The installer prompts you for the server name and port.

• Type the hostname of the remote license server in the Server field.

• Type the port (port_a, port_b, or port_c) used by the remote license server in the Port field.

• Click Next.

The installer prompts you for the Cisco VNDS installation path. Go to Step 11.

c. The installer prompts you for the port used by the local license server (port_a, port_b, or port_c).

Click Next to accept the default value.

The installer prompts you for the Cisco VNDS installation path.

Step 11 Specify the Cisco VNDS installation directory.

Caution When selecting or creating the installation directory for Cisco VNDS, make sure that the directory name DOES NOT contain embedded spaces.

a. Type an installation path in the panel’s path field or use the file browser to select an installation path. The path you enter is the parent directory for the installation. The installer appends \VNDServer\<version>_<build> to the path you choose.

b. Click Next.


OL-14565-01


The installer prompts you for the path to use for the Cisco VNDS temporary directory.

Step 12 Specify the Cisco VNDS temporary (temp) directory.

Caution When selecting or creating the temp directory for Cisco VNDS, make sure that the directory name DOES NOT contain embedded spaces.

a. Type a temp directory path in the panel’s path field or use the file browser to select a path. The path you specify is the full path to this directory.

Note If you are updating, we recommend that you choose the same temp directory that you used in your previous installation.

b. Click Next.

The installer prompts you for the path to use for the Cisco VNDS config file archive directory.

Step 13 Specify the Cisco VNDS config file archive directory.

Caution When selecting or creating the config file archive directory for Cisco VNDS, make sure that the directory name DOES NOT contain embedded spaces.

a. Type an archive directory path in the panel’s path field or use the file browser to select a path. The path you specify is the full path to this directory.

b. Click Next.

The Configure Virtual Network Data Server panel appears.

Step 14 The installer prompts you for the following information:

• Virtual Network Data Server Name

• Virtual Network Data Server ID (0-1022)

• Virtual Network Data Server Address

a. Type the primary IP address of the host in the Virtual Network Data Server Address field.



OL-14565-01

Note The primary IP address is required for all Cisco VNDS installations. To obtain the IP address, open a command prompt and run the ipconfig command.

b. Fill in additional fields if this Cisco VNDS will participate in an n-tier hierarchy.

Note Each instance of Cisco VNDS that participates in a hierarchical configuration must have a unique server ID. If you want to change the server ID post-installation, you must clean the database and remove any existing data contained in it.

c. Click Next.

The installer displays the Configure Virtual Network Data Server Client Connectivity panel.

Step 15 Specify the Virtual Network Data Server Client Connectivity Port.

Type a port number and click Next (or only click Next to accept default port 3100).

Note The Client Connectivity port is the port on which the Live Update Service runs. If you enter a non-default port, Cisco VNDS clients might be unable to communicate with Cisco VNDS until you make a corresponding change in the client’s VND Server LUS Port preference.

The installer prompts you to configure the web server.

Step 16 Specify the web server parameters.

The installer allows you to specify the following:

• Virtual Network Data Server HTTP Port (default port is 9190)

• Virtual Network Data Server HTTPS Port (default port is 8543)

• Keystore Directory

Note Write down the web server connectivity settings for future use.


OL-14565-01


Fill in each field, then click Next (or only click Next to accept the default values).

The installer prompts you to set the Web Server administrator password.

Step 17 Specify the password for the administrator (admin) user account for the Cisco VNDS Web Console.

Type a password into the password fields, then click Next (or only click Next to accept default password cisco).

Note You will need the admin password for initial login to the Cisco VNDS Web Console, because local authentication is configured by default. After you log into the Web Console as the admin user, you can change the admin password or the authentication scheme.

The installer prompts you to configure email notification parameters.

Step 18 If you want to begin receiving email notification as soon as you start Cisco VNDS services, configure email notifications at this time. If you choose not to specify values in the installer, you can configure Notification when you are ready to begin automated operation by using the Management (Mgmt) page in the Web Console.

Note If you are updating your Cisco VNDS installation, you can enter the values that you recorded using the “Recording Notification Settings” procedure on page 3-13. After the software installation is complete, however, you should review and configure the Selected notification conditions , because this list is set to the release 6.0 defaults during the update.

a. Enter the sender, recipients, and subject prefix for Cisco VNDS email notifications, or leave these fields empty if you want to configure Notification post-installation.

b. Click Next to proceed.

The installer prompts you for email server settings.

c. Enter the SMTP Server, Port, User Name, and Password, or leave these fields empty if you want to configure Notification post-installation.

d. Click Next to proceed.



OL-14565-01

An installation progress panel shows status messages as Cisco VNDS installation progresses. Installation normally finishes in several minutes.

• If an existing Cisco VNDS 4.0.3 or 4.5 installation is detected, the installer displays the Migrate Virtual Network Data Server product configuration? panel. Go to Step 19.

• If you are installing on a host that does not have Cisco VNDS 4.0.3 or 4.5 software installed, the installer displays the Web Services Note panel when installation is complete. Go to Step 22.

Step 19 Specify whether the installer should migrate the configuration settings from the previous (Cisco VNDS 4.5) installation.

• To migrate previous settings, perform the following steps:

– Select Yes in the Migrate Virtual Network Data Server product configuration? panel, then click Next.

A Confirm dialog box appears. It provides the path of the previous installation (from which it will migrate product configuration) and lists the actions that will be performed during product configuration migration.

– Click Yes to continue with migration. (If you do not want to proceed with migration, click No and go to Step 22.)

The progress is displayed as the installer migrates settings.

When migration of product configuration is complete, the Export interface utilization data? panel appears.

• To install without migrating the previous product configuration, perform the following steps:

– Select No in the Migrate Virtual Network Data Server product configuration? panel, then click Next.

– Read the confirmation notice that appears.

– Click OK to confirm your decision and go to Step 22. (Click Previous to go back to the Migrate Virtual Network Data Server product configuration? panel.)

Caution If you chose not to migrate product configuration, but want to preserve the Device and Platform Info table, groups, or utilization data, you must export this information before you configure the database for use with Cisco VNDS 6.0. You


OL-14565-01


can migrate adapter resources and text files after installation is complete as long as you do not uninstall or delete files from the previous release installation directory.

Step 20 Specify whether the installer should export interface utilization data from the project in the previous installation.

Note The export of utilization data might take a significant amount of time to complete.The amount of time required depends on the amount of interface utilization data.

• Select Yes to export interface utilization data from the Cisco VNDS database.

Progress displays as Cisco VNDS exports utilization data. When the export of interface utilization data is complete, the Migration Complete dialog appears.

• Select No if you do not want to export interface utilization data from the Cisco VNDS database.

The Migration Complete dialog appears.

Step 21 Read the Migration Complete dialog.

This dialog summarizes the actions performed and provides the location of migration logs. Click OK to continue.

The Web Services Note panel appears.

Step 22 Read the Web Services Note, then click Next.

The installer displays the Install Complete panel.

Step 23 Click Done to exit the installer.

Step 24 (Update only) If Cisco VNDS and the Data Storage Server (PostgreSQL) are already installed on the host system and you are updating to a new release, you must configure the PostgreSQL database for Cisco VNDS 6.0 software.

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Data Storage Server Configuration


OL-14565-01

Caution This script removes all data in the PostgreSQL database. DO NOT configure the PostgreSQL database for the new version of Cisco VNDS until you have successfully exported data that you want to preserve. See the “Preparing for an Update Installation” section on page 3-7 and contact Technical Support for assistance, if needed.

a. Open a command prompt and move to the Cisco VNDS 6.0 installation directory: C:\Cisco\VNDServer\<version>_<build>.

b. Enter the following command:

vnes.bat CLEANALLDB

A Warning dialog appears.

c. Click Yes to continue.

Step 25 Return to the workflow you are following and continue with the next step.

Caution Do not attempt to start Cisco VNDS until you complete all steps in the installation workflow.

Verifying the Data Storage Server ConfigurationPerform this procedure on the Cisco VNDS host to verify that you can connect to the Data Storage Server through the dssuser account and that the Data Storage Server is properly configured for use by Cisco VNDS.

Verifying Data Storage Server Configuration (Windows)

Step 1 Choose Start > Programs > PostgreSQL 8.2 > Command Prompt.

A command prompt opens.

Step 2 Verify that you can interface to the Data Storage Server using psql.

a. Enter the psql command to connect to the database.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Data Storage Server Configuration






b. Enter the password for the dssuser account.

A welcome message appears.

Note Contact Technical Support for assistance if an error message appears.

c. Type \q at the vnes=> prompt to quit psql.

Step 3 Test the Data Storage Server database configuration.

a. Stay in the command prompt and move to the Cisco VNDS installation directory. (C:\Cisco\VNDServer\<version>_<build>)


vnes.bat DBAUTOTEST

Tests are run to verify that the dssuser account can perform needed operations in the Data Storage Server.

Output is written to the command prompt and a separate Java window opens to display a summary of results.

Step 4 Review the DBAUTOTEST results. Figure 3-1 illustrates a successful result.

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Cisco VNDS Software Installation


OL-14565-01

Figure 3-1 Example of Successful DBAUTOTEST Results (PostgreSQL)

Caution Do not proceed until all tests pass.

• If any of the database tests fail, contact Technical Support (as described in the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page vii) and provide the DBAUTOTEST results.

• When all DBAUTOTEST commands and tests pass, return to the workflow you are following and continue with the next step.

Verifying the Cisco VNDS Software InstallationPerform the following procedure to verify that the Cisco VNDS software is installed correctly.

Verifying the Cisco VNDS Installation (Windows)

Step 1 Verify that the license server specified during installation has a valid license available.

Note Do not proceed until you have verified that the appropriate license is available.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Cisco VNDS Software Installation

Step 2 Open the Cisco Virtual Network Data Server Control Panel from the Program Group shortcut, as follows:

Start > Programs > Cisco Virtual Network Data Server 2.1 > Virtual Network Data Server

Within a minute, the Cisco Virtual Network Data Server Control Panel appears.

Step 3 Start Cisco VNDS services from the Control Panel by clicking the Start Services button on the tool bar.

A progress dialog appears and, within a few minutes, service start-up completes.

Step 4 Verify communication with the Cisco VNDS Web Server via HTTP.

a. Open the Web Console:

From the Control Panel menu bar, choose Configuration > Open Management Web Console.

The Web Console login page appears.

b. Verify that you can log in to the admin account using the password that you set during Cisco VNDS software installation.

c. Log out of the Web Console.

d. Close the browser window.

Step 5 Stop Cisco VNDS services from the Control Panel by clicking the Stop Services button on the tool bar.

A progress dialog box appears and, within a few minutes, services stop.

Note Some Cisco VNDS services continue to run in the background. Perform the “Shutting Down Cisco VNDS Using the Command Line (Windows)” procedure on page 3-32 if you want to completely shut down Cisco VNDS.

If the Control Panel fails to open, services fail to start or stop, or error dialog boxes appear, there is a problem with the installation. Review the Readme for known issues and workarounds. Contact Technical Support for assistance if problems persist.

Return to the workflow you are following and continue with the next step.

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Finalizing the Update


OL-14565-01

Shutting Down Cisco VNDS Using the Command Line (Windows)

Use this procedure to shut down Cisco VNDS running on Windows.

Step 1 Stop Cisco VNDS services.

Step 2 Close all open Cisco VNDS windows and exit the Control Panel.


Step 4 Move to the Cisco VNDS installation directory (C:\Cisco\VNDServer\<version>_<build>).



Finalizing the UpdateAfter you have successfully completed the “Verifying the Cisco VNDS Installation (Windows)” procedure on page 3-30, perform the following actions to complete your update:

1. Import Device and Platform Info, if exported from the previous installation.

2. Import Network Topology by running the appropriate adapters.

3. Import Device Groups, if exported from the previous installation.

4. Import Utilization Data, if exported from the previous installation.

5. Configure Notification settings using information from the “Recording Notification Settings” procedure on page 3-13.

6. Create local user accounts and configure authentication. See the “Creating Local User Accounts and Configuring Authentication” procedure on page 3-33.

7. Resume automated operation.

Use the following procedure to configure authentication settings and create local user accounts.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Collecting Oracle Database Access Information

Creating Local User Accounts and Configuring Authentication

Step 1 Log into the Web Console using the admin user account.

Step 2 Open the Users page of the Web Console.

Step 3 Create local user accounts. (Contact technical support for instructions on migrating local user accounts.)

If you do not migrate user accounts, create them manually using the information from the “Recording Authentication Settings” procedure on page 3-12. We suggest setting a default password and notifying users to change it after initial login.

Step 4 Configure Authentication, if needed.

If you use remote authentication, click on the Server link in the Users page and configure it with settings from the “Recording Authentication Settings” procedure on page 3-12.

Note Make sure that at least one local Cisco VNDS user account with the “admin” role has a matching user account (user names must match) on the remote authentication server before you switch to remote authentication.

Collecting Oracle Database Access InformationBefore you configure Cisco VNDS to use an Oracle database, you must collect the database access information listed in Table 3-4.

Print Table 3-4 and use it to write down the database access information for later reference. You will need information from this table when you do the Configuring Cisco VNDS to Use the Oracle Database (Windows) procedure and again when you do the Configuring the Oracle Database for Cisco VNDS (Windows) procedure.

The Oracle database administrator can supply the database access information that you need. (Also see the “Locating an Oracle Database Net Service Name” section on page 3-45 for assistance in locating the Oracle Database Net Service name.)

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Collecting Oracle Database Access Information


OL-14565-01

When you have collected the needed information, continue with the “Configuring Cisco VNDS to Use the Oracle Database” section on page 3-35.

Note The Database Account User Name in Table 3-4 is the account used by Cisco VNDS to access network data stored in the database.

Caution DO NOT use SYS or SYSTEM for the Database Account User Name.

Table 3-4 Database Access Information Worksheet

Access Item Value Description

Database TNS Service Name (alias for Database GDN)

The TNS Net Service name used for the local or remote database. See Locating an Oracle Database Net Service Name, page 3-45, for instructions on locating the service name.

Database SID The database SID.

Database hostname The IP address or fully qualified domain name for the database host. Needed only for remote databases.

Oracle Home (installation) directory

The Oracle installation directory on the database host. Needed only for remote databases.

Oracle Oradata Parent directory

The parent directory to the Oracle oradata directory on the database host. Needed only for remote databases.

Database account user name

User name for the account used to access the database. DO NOT use the Oracle SYS or SYSTEM accounts.

Database account password

Password for the account used to access the database.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Configuring Cisco VNDS to Use the Oracle Database

Configuring Cisco VNDS to Use the Oracle DatabasePerform the following procedure to configure the Cisco VNDS 6.0 software to use an existing dedicated Oracle database.

Configuring Cisco VNDS to Use the Oracle Database (Windows)

Step 1 Log into the host PC as a user with the following privileges:

• Administrator or a user with full administrative privileges

• ORA_DBA privileges

• full control access over the Oracle installation directory tree

If you are not logged in with the proper privileges, log off and then log on with an appropriate account.

Step 2 If Cisco VNDS is running, exit the product and shut it down:

a. Stop Cisco VNDS operation by choosing Services > Stop Services from the Cisco Virtual Network Data Server Control Panel.

b. Exit Cisco VNDS by choosing File > Exit from the Control Panel.

c. Open a command prompt and move to the Cisco VNDS installation directory (C:\Cisco\VNDServer\<version>_<build>).

d. Enter the following command:


Step 3 Start the conversion program (pg2oracle.exe):

a. Insert the Cisco VNDS installation DVD into the DVD drive of the host PC.

b. Run the pg2oracle.exe program.

The program displays an Introduction panel.

Step 4 Click Next.

Step 5 Determine your Oracle installation scenario in Table 3-5 on page 3-36 and follow instructions for that scenario.

Note Cisco Virtual Network Data Server can operate with either a local or remote Oracle database. If a local database is present (on the same host), you have the option of using this database. You can also choose to use a remote database (on a



OL-14565-01

different host). In either case, the program displays a panel that requests database access information. If a local database is not found, but an Oracle client installation is detected, the program displays a panel requesting access information about the remote database.

Table 3-5 Oracle Installation Scenarios

Scenario Oracle Installation Instructions

1 • An Oracle installation is not present on the host PC.

• A message box indicates that Oracle cannot be found.

• Abort the Oracle installation. Click OK to cancel.

• Use the Data Storage Server provided with Cisco VNDS. Follow the workflow Update Cisco VNDS Installation—Standard (Windows), page 3-4, beginning with Step 5.

2 • An Oracle database installation is present on the host PC.

• If more than one Oracle installation is found on the host PC, the program asks which Oracle you want to use. Select the radio button for the correct Oracle installation and click Next.

• A panel appears and asks if you want Cisco VNDS to use the local database.

• Select Yes to use the local database and go to Step 6.

• Select No to use a remote database, and go to Step 7.

3 • An Oracle client installation is present on the host PC.

• If more than one Oracle installation is found on the host PC, the program asks you which Oracle you want to use. Select the radio button for the correct Oracle installation and click Next.

• A panel appears stating that a local Oracle client is detected 1.

• If the Oracle installation is a Client, select the Client radio button. Click OK and go to Step 7.

• If the Oracle installation is really a local database server, select the Server radio button. Enter the Database SID from Table 3-4 on page 3-34. Click OK and go to Step 6.

1. Depending upon how Oracle is installed and databases are created, what appears to be a Client installation might really be a Server.


OL-14565-01


Note If you are working with a local database, use Step 6. If you are working with a remote database, use Step 7.

Step 6 (Local database only) Specify values for the account Cisco VNDS will use to access the local Oracle database:

• Local Database TNS Service Name

• Local Database User Name

• Local Database Password

• Confirm Password

Note Set the database password to the same password that was entered for the dssuser account during installation of Cisco VNDS. Update Table 3-4 on page 3-34 with this password.

Fill in each field with the information collected in Table 3-4 on page 3-34 and click Next. Go to Step 8.

Step 7 (Remote database only) Specify remote database access information.

a. The program prompts you for the following database access information:

• Remote Database TNS Service Name

• Remote Database SID

• Remote Database Hostname

• Remote Oracle Home Directory

• Remote Oracle Oradata Parent Directory

Fill in each field with the information collected in Table 3-4 on page 3-34 and click Next.

The program prompts you for additional remote database access information.

b. Specify values for the account Cisco VNDS will use to access the Oracle database.

• Remote Database User Name

• Remote Database Password

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Configuring the Oracle Database for Cisco VNDS


OL-14565-01


Note Set the database password to the same password that was entered for the dssuser account during installation of Cisco VNDS. Update Table 3-4 on page 3-34 with this password.

Fill in each field with the information collected in Table 3-4 on page 3-34 and click Next.

Step 8 The Conversion Complete panel appears. Click Done to exit the program.

Configuring the Oracle Database for Cisco VNDSWhen you configure Cisco Virtual Network Data Server to use an Oracle database, that database must be configured for use by Cisco VNDS. This involves running an SQL script named setup_accounts.sql that creates tablespaces for the database and a Cisco VNDS database account. This SQL script is run on the host system for the Oracle database.

Caution Do not modify the setup_accounts.sql script. This can cause the installation to fail or prevent Cisco VNDS from operating correctly.

Perform the following procedure to configure the Oracle database.

Caution If you want to preserve Device and Platform Info, utilization data, or device groups from your Cisco VNDS 4.0.3 or 4.5 installation when you update to Cisco VNDS 6.0, DO NOT configure the Oracle database for the new version of Cisco VNDS until you have successfully exported any needed data to text files, as described in the “Preparing for an Update Installation” section on page 3-7.


OL-14565-01


Configuring the Oracle Database for Cisco VNDS (Windows)

Note Use this procedure if the Oracle database is installed on a Windows host. If the Oracle database is installed on a Linux or Unix host, use the “Configuring the Oracle Database for Cisco VNDS (Linux)” procedure on page 4-38.

Step 1 If the Oracle database and Cisco VNDS are located on the same host system, open a command prompt and move to the Cisco VNDS installation directory (<install_dir>\Cisco\VNDServer\<version>_<build>).

Stay in the command prompt on the Cisco VNDS host system and continue to the next step.

Step 2 Log into Oracle using the system account.


sqlplus system/<system password>

For example, if the password for the system account is magic, enter:

sqlplus system/magic


sqlplus system/<system password>@<DB TNS Service Name>

For example, if the Database TNS Service Name is o92adata and the password for the system account is magic, enter:

sqlplus system/magic@o92adata

Step 3 Enter the following command at the SQL> prompt:

@setup_accounts.sql

A message banner appears to inform you how much free disk space is required on the disk that hosts the database.

Note If you do not have sufficient disk space available to run this script, free up sufficient disk space before proceeding. If you want to cancel the script, type Ctrl-C or close the command prompt.

Step 4 Press Enter to continue.

A message banner displays a notification about Device and Platform Info.



OL-14565-01

• For Oracle9i, continue with Step 5.

• For Oracle10g, go to Step 6.

Note In 4.0 and later versions of Cisco VNDS, the Device and Platform Info is stored in the database. To preserve this information, you must export the Device and Platform Info table to a file. If you are upgrading from an existing 4.0.3 or 4.5 installation, export the Device and Platform Info table before you proceed. If you want to cancel the script, type Ctrl-C or close the command prompt.


When configuring an Oracle 9i database, the setup_accounts script analyzes database parameters, database parameter settings, and whether the parameters meet recommended settings. A log of database analysis results is saved to <vnds_install>\analyzedb.<timestamp>.log.

Note If all parameters meet recommended settings, no further action is required. If one or more parameters do not meet recommended settings, a recommendation is made that you run the dbparamchg.sql script after this procedure is completed. Running the dbparamchg.sql script will improve data import performance with large networks (but also increase Oracle memory requirements).


A list of database names is displayed. If you have a database dedicated only to Cisco VNDS, one entry appears.

Step 7 Verify the database instance name.

Note If the database is located on a Solaris or Linux system, the database instance name is case-sensitive and must match the name of the database directory located under the oradata directory (for example, /uo1/app/oracle/oradata) on the database host. Look in the oradata directory to ensure that the database instance name you enter is a case-sensitive match.


OL-14565-01



The setup_accounts script prompts you for the database instance name.

Step 9 Enter the database instance name obtained in Step 7.

The setup_accounts script prompts you for the user password.

Step 10 Enter the same database user account password that was entered during Cisco VNDS installation and written down in Table 3-4 on page 3-34.

A message appears to inform you that the Cisco VNDS database user account and all data will be deleted by this script.


The setup_accounts SQL script configures the Oracle database for use by Cisco VNDS and sets up the user account. After the script finishes, the Oracle account information for Cisco VNDS is the database user name and password from Table 3-4 on page 3-34. A log of script actions is saved to <vnds_install>\setup_accounts.<timestamp>.log.

Note When you run this script for the first time, several SQL error messages appear. You can ignore these messages. The messages are the result of the script trying to remove Cisco VNDS table and user accounts that do not exist prior to this script being run for the first time.

Step 12 Type quit at the SQL> prompt to exit sqlplus.

If the setup_accounts script recommended changing your database settings during Step 5 and you agree with the recommended changes, go to the “Modifying Oracle Database Parameters” section on page 3-42 at this time.

If you do not need to change your database settings or you choose not to change them, go to the “Verifying the Oracle Configuration for Cisco VNDS” section on page 3-43 to verify that Oracle is configured correctly for use with Cisco VNDS.

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Modifying Oracle Database Parameters


OL-14565-01

Modifying Oracle Database ParametersPerform the “Modifying Oracle Database Parameters (Windows)” procedure on page 3-42 on the Oracle 9i database host to modify database parameters. The database parameter changes improve Cisco VNDS performance when working with large networks and will increase Oracle memory requirements.

Do not modify database parameters for Oracle 10g unless instructed to do so by Technical Support.

Note Work with your Oracle Database Administrator to run this script.

Modifying Oracle Database Parameters (Windows)


• For a local Oracle database installation, enter the following text in the command window:


For example, if the password for the system account is magic, type:


• If the Oracle database is not on the same host system as Cisco VNDS, enter the following text in the command window:


For example, if the database is remote with a TNS Service Name of o92adata and the Oracle system password is magic, type:



@dbparamchg.sql

A message is displayed that shows the path to the Oracle spfile that contains the parameters for your database.

Step 3 Make a backup copy of the spfile at the path specified by the message seen in the previous step.

Step 4 Press Enter as many times as needed to step through the information messages produced by this script.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Oracle Configuration for Cisco VNDS

When the script is done, a list of the changed parameters and their new settings appears, with a reminder to restart the Oracle DB service for the changes to take effect.


Step 6 Use the Windows Service Manager to stop and restart the Oracle database service:

a. From the desktop, select Start > Settings > Control Panel > Administrative Tools > Services to open the Windows Service Manager.

b. Select the service named OracleService<DB SID>.

c. Right-click on the service and select Stop from the menu.

d. After the Service Control progress dialog completes, right-click on the service and select Start from the menu to restart the service.

Step 7 If the Oracle database service fails to restart, restore the original spfile for the database and repeat Step 6 to recover.

Continue with the “Verifying the Oracle Configuration for Cisco VNDS” section on page 3-43 to verify that you can connect to the database through the Cisco VNDS account.

Verifying the Oracle Configuration for Cisco VNDSPerform the following procedure on the Cisco VNDS host to verify that you can connect to the database through the Cisco VNDS account.

Verifying the Oracle Configuration (Windows)


Step 2 Move to the Cisco VNDS installation directory (C:\Cisco\VNDServer\<version>_<build>).

Step 3 Verify that you can log into Oracle using the Cisco VNDS database user account.

• For a local Oracle database, enter the following command:


Chapter 3 Installing Cisco Virtual Network Data Server on Windows Verifying the Oracle Configuration for Cisco VNDS


OL-14565-01

Use the user name and password from Table 3-4 on page 3-34. For example, if the Cisco VNDS user name and password are dbuser and pwd respectively, enter:

sqlplus dbuser/pwd



Use the database user name, password, and TNS Service Name from Table 3-4 on page 3-34. For example, if the Database TNS Service Name of o92adata and the Cisco VNDS user name and password are dbuser and pwd respectively, enter:


Step 4 If Oracle configuration was not successful, error messages are displayed indicating that login has been denied.

Reconfigure the Oracle database and verify again.

Step 5 If configuration of the Oracle account for Cisco VNDS was successful, an Oracle banner and a Connected To: message appear.


Step 7 Test the Oracle database configuration.

a. Enter the following command:

vnes.bat DBAUTOTEST

The script runs tests to verify that the Cisco VNDS account can perform needed operations in Oracle.

Output is written to the command prompt and a separate Java window opens to display a summary of results.

b. Review the DBAUTOTEST results and verify that all tests pass. Figure 3-2 shows a successful result.


OL-14565-01

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Locating an Oracle Database Net Service Name

Figure 3-2 Example of Successful DBAUTOTEST Results (Oracle)


If any of the database tests fail, contact Technical Support (as described in “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page vii) and provide the DBAUTOTEST results.

When all database tests pass, continue with your installation workflow.

Locating an Oracle Database Net Service NameThis section provides assistance for locating an Oracle Database Net Service Name in a tnsnames.ora file.

Note Cisco VNDS uses the Oracle Net service name to connect to an Oracle database. This is true whether Cisco VNDS uses a local or remote Oracle database.

The database service name is located in the tnsnames.ora file. The location of this file varies by Oracle version:

• Oracle 9i: <oracle install dir>\ora92\network\Admin

• Oracle 10g: <oracle install dir>\product\10.2.0\db_1\NETWORK\ADMIN



OL-14565-01

A sample file is shown in Figure 3-3. In this sample file, there are three entries. The O92ML23 entry represents the database service name. Each entry has a <net service name> = () structure. The text string preceding the “=” is the service name. In this example, you use O92ML23 as the service name when you configure Cisco VNDS to use an Oracle database.

Note The tnsnames.ora file has entries for several Oracle Net services. Contact the database administrator if you are unsure of the service name that Cisco VNDS should use when connecting to the Oracle database.


OL-14565-01


Figure 3-3 Sample tnsnames.ora File

# TNSNAMES.ORA Network Configuration File: D:\oracle\ora92\NETWORK\ADMIN\tnsnames.ora# Generated by Oracle configuration tools.

092ML23 =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = mlpc23)(PORT = 1521))(ADDRESS = (PROTOCOL = IPC)(Key = EXTPROC0))

)(CONNECT_DATA =

(SERVER = DEDICATED)(SERVICE_NAME = o92ml23)

))

INST1_HTTP =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = mlpc23)(PORT = 1521))

)(CONNECT_DATA =

(SERVER = SHARED)(SERVICE_NAME = MOD0SE)(PRESENTATION = http://HRService)

))

EXTPROC_CONNECTION_DATA =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))

)(CONNECT_DATA =

(SID = PLSExtProc)(PRESENTATION = R0)

))

Chapter 3 Installing Cisco Virtual Network Data Server on Windows Installation Troubleshooting


OL-14565-01

Installation TroubleshootingThis section contains troubleshooting assistance for installation issues you might encounter when installing Cisco VNDS on Windows. It also contains procedures for manually installing and configuring PostgreSQL for use by the Cisco VNDS software.

• Troubleshoot Installation of Cisco VNDS Software, page 3-48

• Troubleshoot Installation of Data Storage Server (PostgreSQL), page 3-50

• Manually Install Data Storage Server (PostgreSQL), page 3-52

• Configure PostgreSQL Database for Cisco VNDS, page 3-53

Note Failure during the installation of the Data Storage Server does not indicate an issue with the installation of the Cisco VNDS software itself. Unless the Cisco VNDS installer hangs or aborts, the installation of the Cisco VNDS software completed successfully.

Troubleshoot Installation of Cisco VNDS SoftwareThe configuration of the host system might cause the installer to hang or abort around the time the splash screen would normally appear. If you see this happen, try the steps described in the following procedure.

Troubleshooting Cisco VNDS Installation

Step 1 Ensure that you are logged on as a user with full administrative privileges.

Step 2 Disable any virus scan software that is be running.

Step 3 If you are running Dell OpenManager on the system, disable OpenManager.

Step 4 If you are running PC Anywhere on the system, disable PC Anywhere.

Step 5 If you are running another remote access application, disable the application.

Step 6 If you are trying to remotely drive the installation, try running the installer while directly accessing the system. Do not try to run the installer via a remote access session.


OL-14565-01


Step 7 Copy the installer executable (setup.exe) to the system’s disk and execute the installer locally. Verify that the installer file size matches the original file you copied.

Step 8 Check the version of DirectX.

a. In the Start > Run dialog, type dxdiag.

A DirectX Diagnostic Tool window opens.

b. Check the DirectX Version near the bottom of the window.

c. If the version is older than 9.0.c, upgrade DirectX to version 9.0.c or newer.

Step 9 Disable hardware acceleration for your video card.

Step 10 Reboot the system and try to run the installer again.

• After installation completes, re-enable any applications you disabled to get through the installation.

Note If installation is unsuccessful after performing the steps in this procedure, collect installer debug information as described in the “Collecting Installer Debug Information” procedure on page 3-49. Provide the debug information when you contact Technical Support.

Use the following procedure to collect installer debug information.

Collecting Installer Debug Information

Step 1 Start the installer and immediately press and hold the CTRL key.

When the initial installer progress dialog reaches 100% completion, a console window will appear. Installer output messages are displayed to this window.

Step 2 Capture the output (using copy/paste or screen captures) and forward it to Technical Support.



OL-14565-01

Note You might need to do this twice. On the first try, set the console window properties to support 999 lines in the display buffer. Save and check the “Modify shortcut...” radio button. Run the installer again in debug mode. You should be able to capture all output now.

Troubleshoot Installation of Data Storage Server (PostgreSQL)The configuration of the host system might cause installation of PostgreSQL to fail. When this occurs, the installer displays an error dialog indicating that it encountered a Data Storage Server installation problem. Troubleshoot this event using the steps in the “Troubleshooting PostgreSQL Installation” procedure on page 3-50.

After you identify and resolve the issue(s) that are interfering with the PostgreSQL installation, manually install and configure PostgreSQL for Cisco VNDS.

Troubleshooting PostgreSQL Installation

Step 1 Ensure that you are logged on as a user with full administrative privileges.

Step 2 Check the host to determine if a non-Cisco version of PostgreSQL is already installed on the host. If a non-Cisco version of PostgreSQL is present, uninstall it.

Step 3 Ensure that the drive on which PostgreSQL is being installed is a local NTFS drive with adequate space. (A minimum of 200 MB is required for successful PostgreSQL installation, although a minimum of 15 GB is recommended for storage of network data).

Step 4 If you are using Remote Desktop Connection, ensure that you are connected to the remote host using a console session.

Step 5 Ensure that the dssowner account was successfully created.

• Policy restrictions configured on the host PC might interfere with the creation of this OS account. This can be the case when the password specified in the installer is not complex enough to satisfy security policy.


OL-14565-01


• The dssowner account is a local account that is not part of a domain. Ensure this is permitted on the host.

Step 6 Ensure that the “Secondary Logon” Windows service is started.

On Windows 2000 machines, this service might be named the “RunAs Service”.

Step 7 Ensure that the dssowner user has read/execute permissions for cmd.exe.

a. Open a command window and enter the following command:

runas /user:dssowner "cmd /k echo Test"

b. When prompted, enter the password for dssowner.

When the command executes successfully, a new command window opens running as dssowner.

• If this succeeds, there is no permission issue with the “cmd” executable.

• On failure, access is denied. To resolve this, give read/execute permission to the dssowner user to the “cmd” executable.

Step 8 Ensure that the dssowner user has read permissions leading all the way to the Data Storage Server (DSS) install directory.

a. Enter the following command in command window:

runas /user:dssowner "cmd"

b. When prompted, enter the password for dssowner.

When the command executes successfully, a new command window opens running as dssowner.

c. In this new command window that is running as dssowner (opened in the previous step), use the cd command to change directories to the PostgreSQL database directory.

For example, if you specified C:\Cisco as the root directory for the Data Storage Server, you would enter the following command:

cd C:\Cisco\DSS\PostgreSQL\8.2\data

When the command executes successfully, you can successfully change directories while running as the dssowner and list the contents of the directory.

• If this succeeds there are no read permission issues leading up to the PostgreSQL database directory.



OL-14565-01

• On failure, access is denied. To resolve this, give read permissions to the dssowner user account for the root drive of the PostgreSQL database directory.

Note If these steps do not resolve the issue, contact Technical Support and provide the following log: <install_dir>\InstallLogs\installer_debug_final.log.

Manually Install Data Storage Server (PostgreSQL)

Note Manual installation of PostgreSQL is only necessary if the Cisco VNDS installer cannot successfully install it. See the “Troubleshooting PostgreSQL Installation” procedure on page 3-50 for troubleshooting steps.

After you have identified and resolved the issue(s) that caused installation of PostgreSQL to fail, install PostgreSQL using the “Installing PostgreSQL Manually” procedure on page 3-52.

Note Do NOT rerun the Cisco VNDS 6.0 installer, because doing so results in multiple installations of the Cisco VNDS 6.0 software.

Installing PostgreSQL Manually

Step 1 Open a command window.

Step 2 Change directories to <DSS_rootdir>\DSS\installers\postgres-8.2.3. For example: C:\Cisco\DSS\installers\postgres-8.2.3.

Step 3 Enter the command to run the postgreSQL installer.


OL-14565-01


Note We recommend you copy and paste the command from the log to reduce the opportunity of mistyping this lengthy command and to ensure that the values match those entered in the Cisco VNDS installer.

Look in the installer log (<install_dir>\InstallLogs\installer_debug_final.log) to find the exact command that the installer attempted to run. Search the installer log for “postgres-installer.bat”.

The command will be in the following syntax:

postgres-installer.bat /rootdir <DSS_rootdir>\DSS /os_user dssowner /os_passwd <dssowner_pwd> /db_user dssadmin /db_passwd <dssadmin_pwd> /port <port> /action install

where:

• <DSS_rootdir> is the directory specified in the Cisco VNDS installer for the Data Storage Server. The default is C:\Cisco.

• <dssowner_pwd> is the password specified in the Cisco VNDS installer for the dssowner OS user.

• <dssadmin_pwd> is the password specified in the Cisco VNDS installer for the PostgreSQL Administrator user (dssadmin).

• <port> is the port specified in the Cisco VNDS installer on which the PostgreSQL service listens.

Step 4 Perform the “Configuring PostgreSQL Database for Cisco VNDS” procedure on page 3-53 to configure the PostgreSQL database.

Configure PostgreSQL Database for Cisco VNDSPerform the following procedure to configure the PostgreSQL database for Cisco VNDS.

Configuring PostgreSQL Database for Cisco VNDS




OL-14565-01

Step 2 Change directories to <install_dir>\database\postgresql. For example, if the Cisco VNDS software is installed in C:\Cisco, then you would navigate to the following directory: C:\Cisco\VNDServer\<version>_<build>\database\postgresql.


setup_accounts.bat

Step 4 When prompted, enter the PostgreSQL installation directory (<DSS_rootdir>\DSS\PostgreSQL\8.2). For example, C:\Cisco\DSS\PostgreSQL\8.2.

Step 5 When prompted for the Cisco VNDS database user name, enter:

dssuser

Step 6 When prompted for the Cisco VNDS database password, enter the password for the dssuser account. You must enter the same password that you entered in the Cisco VNDS installer.

Step 7 When prompted for the PostgreSQL Administrator user, enter:

dssadmin

Step 8 When prompted for the PostgreSQL Administrator user password, enter the password for the dssadmin account.

Note You must enter the same password that you entered in the Cisco VNDS installer.

Messages print indicating that the script is dropping Cisco VNDS database objects. If this is the first time you are configuring PostgreSQL, you will see error messages during this stage because the tables and user do not yet exist. This is normal.

Messages print indicating that the dssuser role, table spaces, database, and schema are created.


setup_accounts.bat /pg_home <DSS_rootdir>\DSS\PostgreSQL\8.2 DB_PARAMS_CHANGE

For example:

setup_accounts.bat /pg_home C:\Cisco\DSS\PostgreSQL\8.2 DB_PARAMS_CHANGE


OL-14565-01


Step 10 Return to workflow you are following and continue with the next step.

Caution Do not attempt to start Cisco VNDS until you complete all steps in your installation roadmap.



OL-14565-01

C H A P T E R


OL-14565-01

4Installing Cisco Virtual Network Data Server on Linux

This chapter describes how to install the Cisco Virtual Network Data Server (Cisco VNDS) software on Linux.

Note Release 2.1 of Cisco Virtual Network Data Server installs version 6.0 of the Cisco VNDS software. Release 2.0.2 used Cisco VNDS version 4.5 and Release 2.0.1 used Cisco VNDS version 4.0.3.

System Requirements The host PC for Cisco Virtual Network Data Server must meet minimum system requirements. These requirements are documented in Cisco Virtual Network Data Server: System Requirements, page 2-1.

Caution If the host system does not meet minimum requirements, do not install Cisco Virtual Network Data Server.

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Account Permissions


OL-14565-01

Account PermissionsYou must be logged in as root to install Cisco VNDS 6.0 software on a Linux host. During the installation of Cisco VNDS, you will specify a user account and group that will own the Cisco VNDS directory and files. Any member of the specified group will be able to run Cisco VNDS.

Additional permissions might be required to perform specific steps in your installation; these permissions are described in the relevant procedures.

Installation WorkflowsThis chapter covers the installation scenarios you might encounter with Cisco Virtual Network Data Server on Linux. The procedures you must follow depend upon whether this is an initial Cisco VNDS installation or an update.

Cisco VNDS 6.0 includes an embedded Data Storage Server. If the host system does not already have a Cisco VNDS Data Storage Server installed, it will be installed with the Cisco VNDS software.

Select the installation workflow appropriate for your circumstances. Follow the procedures in that workflow to install or update Cisco VNDS.

• First-Time Cisco VNDS Installation (Linux), page 4-2

• Update Cisco VNDS Installation—Standard (Linux), page 4-3

• Update Cisco VNDS Installation—With an Existing Oracle Database (Linux), page 4-4

Note If you are updating and do not have a dedicated Oracle installation and database instance, you should use the standard installation and Cisco VNDS’s Data Storage Server.

First-Time Cisco VNDS Installation (Linux)If you are installing Cisco Virtual Network Data Server for the first time, follow the workflow in Table 4-1.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Installation Workflows

Update Cisco VNDS Installation—Standard (Linux)If you are updating a previous installation of the Cisco Virtual Network Data Server software and will be using the Data Storage Server provided with Cisco VNDS, follow the workflow in Table 4-2.

Table 4-1 Cisco VNDS First-Time Installation: Workflow



Step 2 Verify the Data Storage Server configuration. Verifying Data Storage Server Configuration, page 4-27


Table 4-2 Cisco VNDS Update Installation: Workflow







Step 5 Verify the Data Storage Server configuration. Verifying Data Storage Server Configuration, page 4-27




Chapter 4 Installing Cisco Virtual Network Data Server on Linux Installation Workflows


OL-14565-01

Update Cisco VNDS Installation—With an Existing Oracle Database (Linux)

If you are updating a previous installation of the Cisco Virtual Network Data Server software and want to continue using a dedicated installation of Oracle for Cisco VNDS, follow the workflow in Table 4-3. If you do not have a dedicated Oracle installation, follow the Update Cisco VNDS Installation—Standard (Linux) workflow instead.

Note Shared Oracle installations are not supported.

Table 4-3 Cisco VNDS Update Installation for Existing Oracle Database: Workflow







Step 5 Collect Access Information for the Oracle Database.

Collecting Oracle Database Access Information, page 4-33

Step 6 Configure Cisco VNDS to Use Oracle. Configuring Cisco VNDS to Use the Oracle Database, page 4-35

Step 7 Configure the Oracle Database for Cisco VNDS.

Configuring the Oracle Database for Cisco VNDS, page 4-38

Step 8 Verify the Oracle Configuration for Cisco VNDS.

Verifying the Oracle Configuration for Cisco VNDS, page 4-43





OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Important Update Information

Important Update InformationThis section covers the following topics:

• Database Contents, page 4-5

• Migration of Product Configuration, page 4-5

Database Contents

Note The network topology and configuration data in the Cisco VNDS database cannot be retained during a software update. You must recreate the network topology and configuration after you update.

The contents of the Cisco VNDS database cannot be retained during a software update. However, you can preserve certain data by exporting it to text files prior to the software update. See the “Preparing for an Update Installation” section on page 4-6 for more information.

Migration of Product Configuration

Caution Do not rename or uninstall the existing Cisco VNDS release until after your update is complete and you have migrated product configuration. If a Cisco VNDS 4.0.3 or 4.5 installation is detected by the installer, you will have the option to migrate Cisco VNDS configuration settings from the existing software installation to the new 6.0 installation.

When the Cisco VNDS 6.0 installer detects an existing Cisco VNDS 4.0.3 or 4.5 installation, it offers to migrate the Cisco VNDS configuration to the new installation. The installer provides update assistance by

• migrating product settings such as adapter resources, schedule, and other project properties from your previous installation to your new installation.

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Preparing for an Update Installation


OL-14565-01

• copying text files from your previous Cisco VNDS installation directory to the Cisco VNDS 6.0 installation directory. If you want the installer to automatically copy the device info file to your new installation, you must perform the “Exporting Device and Platform Info Table to a Text File” procedure on page 4-7.

Although some configuration might be required in your Cisco VNDS 6.0 installation after the installer completes, product migration minimizes the amount of post-installation configuration. If you are not satisfied with the product settings after the installer performs migration of product configuration, the default product settings can be restored in your Cisco VNDS 6.0 installation.

Recommendations when migrating:

• Install Cisco VNDS 6.0 to use the same temp directory that you used for your previous installation.

• After you update, double-check settings for any adapters for which you had created additional cloned servers.

Note See the Readme to learn about release-specific product migration issues.

Note If you will not migrate product configuration, you should use the same database password that you used in your previous installation—otherwise you will have to reenter encrypted passwords in Cisco VNDS 6.0 after your update is complete. This applies to passwords in an exported device info file as well as passwords defined in adapter resources.

Preparing for an Update Installation

Caution Do not configure the database for use by Cisco VNDS 6.0 until you have exported data that you want to preserve.

This section covers the following topics:

• Device and Platform Table Info, page 4-7


OL-14565-01


• Group Data, page 4-8

• Authentication and User Accounts, page 4-9

• Notification Settings, page 4-10

Device and Platform Table Info

Caution You must export Device and Platform Info table to a text file if you want to preserve the device entries when you update to Cisco VNDS 6.0. Do not preserve the Device and Platform Info table unless you run Cisco VNDS’s direct collection adapters.

The Device and Platform Info table must be exported to a file if you want to retain the device entries when you update to Cisco VNDS 6.0. Export the Device and Platform Info table if you use the following adapters:

• Device Config File Collection

• Device MIB Configuration Import

• Device MIB MPLS TE Import

• MIB-Based Interface Utilization Import

Follow this procedure to export the Device and Platform Info table to a text file.

Exporting Device and Platform Info Table to a Text File


Step 2 Select the Device Info File tab.

Step 3 Note the value of the Device Info File Location property.

The default value for this property is:

<install_dir>\input\DeviceInfo\deviceInfo.txt

Step 4 Open the Device and Platform Info window, as follows:

From the Cisco VNDS menu bar, choose Configuration > Open Device and Platform Info.

The Device and Platform info window appears.



OL-14565-01

Step 5 Click the Export button.

Step 6 Move to the directory specified in the Device Info File Location property and enter the filename specified in the Device Info File Location property (for example: deviceInfo.txt).

Step 7 When the export is complete, verify that the device info file you exported is stored in the path and filename specified by the Device Info File Location property.

Note Import the device info file into your Cisco VNDS 6.0 project after you complete your update. This file is copied automatically to your Cisco VNDS 6.0 installation if you perform product migration during installation.

Group Data

Caution You must export group data to a text file if you want to preserve it when you upgrade to Cisco VNDS 6.0.

When you export group data, three files named grp_list.txt, grp_mbrs.txt, and subgrp_mbrs.txt are written to the directory from which you run the export command. These files contain the groups, group members, and subgroups, respectively.

Note If you use an Oracle database for your Cisco VNDS 4.0.3 or 4.5 software, you cannot export group data.

If you use a PostgreSQL database for a Cisco VNDS 4.5 software installation, use the following procedure to export group data.

Exporting Group Data to Files (Cisco VNDS 4.5 with PostgreSQL)



OL-14565-01


Step 2 Move to the following directory in the Cisco VNDS installation: <install_dir>\database\postgresql

For example: /opt/cisco/VNDServer/<version>_<build>/database/postgresql


psql -U dssuser -d vnes -f group_export.sql

You are prompted to enter the password for the dssuser account.



grp_list.txt

grp_mbrs.txt

subgrp_mbrs.txt

To use the exported files in the Cisco VNDS 6.0 installation, copy them to the new installation and configure the Ascii Generic Data Import adapter to import the group data files. After you have created a network topology in Cisco VNDS 6.0, use the Ascii Generic Data Import adapter to import group data. Refer to the online documentation for more information regarding use of the Ascii Generic Data Import adapter.

Authentication and User AccountsNeither authentication settings nor local user accounts migrate when you update. Use the following procedure to record authentication settings.

Recording Authentication Settings

Step 1 Log into the Management Console as a user with administrative privileges.

Step 2 Select the Users page.

Step 3 Note user names and the roles for each.



OL-14565-01

Note This step is not required if you will manually migrate local user accounts after you update. Do not uninstall the previous release until after you successfully migrate.

Choose a username from the Select User pull-down menu to view the roles configured for that user.

Step 4 Click on the Server link.

Step 5 If RADIUS or TACACS+ is selected, note the Authentication Server settings:

• Server Host

• Server Port

• Shared Secret:

• Auth Type:

• Message Trace

• Timeout

After you update, you can perform a manual procedure to migrate local user accounts. After you have migrated local user accounts, you can configure authentication parameters if you use remote authentication, as described in the “Creating Local User Accounts and Configuring Authentication” procedure on page 4-33.

Notification SettingsThe Notification settings do not migrate when you perform an update installation. Use the following procedure to record Notification settings.

Recording Notification Settings


Step 2 Select the Notification page.

Step 3 Write down the values of the following properties:


OL-14565-01


• Selected notifications

Note The Selected notifications list is set to Cisco VNDS 6.0 defaults after the software update. When you are ready to resume automated operation, you must set the Selected notifications list to your desired values using the Management (Mgmt) page in the Web Console. Because new software might contain additional notification types, examine the available notification types when deciding which notifications you want to receive in your 6.0 installation.

• Email Recipients

– To

– Cc

• Email Parameters

– SMTP Server

– SMTP Port

– Sender

– Subject prefix

– SMTP Username

– SMTP Password

Note You can enter the values for Email Recipients and Email Parameters in the Cisco VNDS 6.0 installer or configure these properties after the update is complete.

The installer provides the opportunity for you to enter values for Email Recipients and Email Parameters; however, you must still configure Selected notifications after the update is complete.

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying that the Host Meets Minimum System Requirements


OL-14565-01

Verifying that the Host Meets Minimum System Requirements

Use the following procedure to check host parameters and verify that the host meets minimum system requirements for Cisco Virtual Network Data Server 6.0.

Verifying that the Host Meets Minimum System Requirements (Linux)

Step 1 Log into the Cisco VNDS host as root or switch users to root.

Use the su - <user> command when switching users. For example:

su - root


Step 3 Check the host against the minimum requirements given in the “Cisco Virtual Network Data Server: System Requirements” section on page 2-1:

a. Check the version of Red Hat Enterprise Linux (RHEL) by entering the following command:

cat /etc/redhat-release

b. Check the kernel by entering the following command:

uname -a

c. Check the processor by entering the following commands:

cd /procmore cpuinfo

d. Check the RAM by entering the following command:

more meminfo

e. Check available disk space by entering the following command:

df -h


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying the Database Password

Verifying the Database PasswordYou must enter the database password when you run the Cisco VNDS 6.0 installer. Before you start the installer, verify that you have the correct password.

Depending on which database you have, use one of the following procedures to verify the password:

• Verifying Database Password (PostgreSQL), page 4-13

• Verifying Database Password (Oracle), page 4-14

Verifying Database Password (PostgreSQL)

Use this procedure if your Cisco VNDS software installation uses the Cisco VNDS Data Storage Server (PostgreSQL).


Step 2 Change directories to the Data Storage Server installation directory by entering the following command:

cd /usr/bin

Step 3 Enter the psql command to connect to the database.







A welcome message is displayed.

Note If you are unable to determine the password for the database, contact Technical Support to obtain assistance in resetting the password for the dssuser account to a known value.

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying the Database Password


OL-14565-01

Step 5 Type \q at the vnes=> prompt to quit psql.

Verifying Database Password (Oracle)

Use this procedure if your Cisco VNDS software installation uses an Oracle database.

Step 1 Log into the database host as oracle or switch users to oracle.


su - oracle


• For a local Oracle database installation enter the following command:


Use the database user name and password from Table 4-4 on page 4-34. For example, if the Cisco VNDS database user name and password are dbuser and pwd respectively, enter:

sqlplus dbuser/pwd

• For a remote Oracle database enter the following command:


Use the database user name, password, and TNS Service Name from Table 4-4 on page 4-34. For example, if the Cisco VNDS database user name and password are dbuser and pwd respectively, and the Database TNS Service Name is o92adata, enter:


An Oracle banner, and a Connected To: message appears.

Note If you are unable to log in using the Cisco VNDS user account, consult Oracle documentation or contact Oracle Technical Support to obtain assistance in resetting the password for the Cisco VNDS user account to a known value.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Installing Cisco Virtual Network Data Server


Installing Cisco Virtual Network Data ServerUse the following procedure to install the Cisco Virtual Network Data Server software.

Caution The installer will uninstall any non-Cisco installation of PostgreSQL 8.2 (and its components) detected on the host system.

Installing Cisco VNDS Software (Linux)

Step 1 Log into the Cisco VNDS host as root or switch users to root.


su - root

Note You must use the root account to install Cisco VNDS.

Caution Export the Device and Platform Info table from the Cisco VNDS database if you are updating Cisco VNDS and you use the Device Config File Collection, Device MIB Configuration Import, Device MIB MPLS TE Import, or MIB-based Interface Utilization Import adaptors. See the “Preparing for an Update Installation” section on page 4-6.

Step 2 (Update only) If Cisco VNDS is already installed on the host PC and you are updating to a new release, perform the following steps to make sure that Cisco VNDS is shut down and all processes are stopped.

a. Log into the Cisco VNDS host as a user who has permission to run the Cisco VNDS software or switch to such a user account. Use the su - <user> command when switching users.



OL-14565-01

Note This user must be a member of the group specified during installation of Cisco VNDS software.

b. Move to the Cisco VNDS installation directory (/opt/cisco/VNDServer/<version>_<build>).

c. Enter the following command to determine if any Cisco VNDS processes are running:

ps -aef | grep '\.conf'

d. Stop any Cisco VNDS processes that are running by moving to the Cisco VNDS installation directory and entering the following command:

./vnes.sh -c stop ALL

e. Use the License Manager from one of the following products to see if your Cisco VNDS license is still held.

• Cisco Configuration Assurance Solution

• Cisco Configuration Assurance Solution–Service Provider

• Cisco Network Planning Solution

• Cisco Network Planning Solution–Service Provider

If the license is still held by Cisco VNDS, use the License Manager to revoke the license.

Caution Do not rename or uninstall the existing Cisco VNDS release. If a Cisco VNDS 4.0.3 or 4.5 installation is present, you will have the option to migrate configuration settings from that installation to the Cisco VNDS 6.0 installation. If you uninstall the previous release before you migrate the product configuration, you must manually configure Cisco VNDS 6.0 after you update.

Step 3 Start the installer:

a. Insert the Cisco Virtual Network Data Server installation DVD into the DVD drive of the host PC.

b. Open a command window and move to the folder that corresponds to the DVD drive (for example, /media/cdrecorder), then enter one of the following commands:

./cnps-vnds-2.1-lin-K9.bin


OL-14565-01


or

./cnps-sp-vnds-2.1-lin-K9.bin

The installer displays an Introduction panel.

c. Click Next.

If Cisco VNDS’s Data Storage Server is not detected, it will be installed. A Warning is displayed. Continue with Step 4.

If a supported version of Cisco VNDS’s Data Storage Server was installed during a previous installation of Cisco VNDS software, it will be used. The Specify the Data Storage Server password panel appears. Go to Step 8.

Step 4 Read the Warning about existing PostgreSQL installations.

Caution Any existing non-Cisco installations of PostgreSQL will be uninstalled.

Click OK to continue or Cancel to cancel the installation.

A Note about Cisco VNDS’s Data Storage Server appears.

Step 5 Read the important information about the Data Storage Server and the accounts that the installer creates on the Cisco VNDS host.

• Click Edit if you want to specify your own passwords for the accounts that Cisco VNDS creates or customize the Data Storage Server listening port or data directory. Follow this path if any of the following conditions apply to your installation:

– On a Linux host, the Data Storage Server data directory is installed to a different path than the Data Storage Server software. The default path to the data directory for the Data Storage Server is /var/lib. The installer appends /dss/pgsql/8.2/data to this path. If you want to change this path, choose a different location when you do Step 6.

Note The Data Storage Server root installation directory is /usr/bin. This path is fixed and cannot be modified.

– If the default listening port for the Data Storage Server (port 5432) is used by another application, choose a different port when you do Step 6.



OL-14565-01

– If you are updating from a previous version of Cisco VNDS, set the dssuser password in Step 8 to the same value as the database password that Cisco VNDS used to access the database in your previous installation.

Continue with Step 6.

• Click OK if you want to accept the default values displayed in the Note about Data Storage Server. (The operating system account and Data Storage Server accounts that the installer creates will have the password of CisCo123 if you accept this selection.) Go to Step 9.

Step 6 The installer prompts you for the following Data Storage Server values:

• Location—path to the data directory for the Data Storage Server.

Note Make sure you have a minimum of 15 GB of disk space available for the Data Storage Server data directory. Additional disk space might be required depending on the amount of data you store in Cisco VNDS.

• Port—port on which the Data Storage Server listens.

Note If the default port (5432) is used by another application, choose a different port for the Data Storage Server to listen on.

Enter values in the Specify Data Storage Server Information panel or click Next to accept the default values.

The Specify Data Storage Server User Information panel appears.

Step 7 You are prompted to enter passwords for the dssowner and dssadmin accounts:

• dssowner—the Linux operating system user account that will run the Data Storage Server (PostgreSQL) service.

• dssadmin—the Administrator account for the Data Storage Server (PostgreSQL).

Enter and confirm the passwords. If you want to use the default password (CisCo123) for one or both of these accounts, enter it in the password confirmation text field(s). Click Next to continue.

The Specify the Data Storage Server password panel appears.


OL-14565-01


Step 8 You are prompted to enter the password for the dssuser account. This is the account Cisco VNDS will use to access the Data Storage Server.

Note You will need this password when you update to future versions of Cisco VNDS.

Note If you are updating from a previous Cisco VNDS installation, set the dssuser password to the same password that Cisco VNDS used to access the database in your previous installation. Verify the password if you have not already done so (see Verifying the Database Password, page 4-13).

Enter and confirm the password. If you want to use the default password (CisCo123), enter it in the password confirmation text field. Click Next to continue.

The Select Licensing Type panel appears.

Step 9 Specify licensing type. (See the “Licensing Notes” section on page 4-26.)

Note As you proceed, write down the license settings for future reference.

The installer prompts you for the type of licensing to use. The Select Licensing Type panel provides the following choices:

• Access licenses from a remote server

• Serve licenses from a new license server on this computer

• Serve licenses from an existing license server on this computer

Caution The specified license server must have a valid license for Cisco VNDS before you can run the software.

a. Choose the licensing type, then click Next.

• If you selected remote licensing, the installer displays the Enter Server Name and Port panel. Go to Step 9b.



OL-14565-01

• If you selected local licensing, the Enter Port panel appears. Go to Step 9c.

b. The installer prompts you for the server name and port.

• Type the hostname of the remote license server in the Server field.

• Type the port (port_a, port_b, or port_c) used by the remote license server in the Port field.

• Click Next.

The installer prompts you for the Cisco VNDS installation path. Go to Step 10.

c. The installer prompts you for the port used by the local license server (port_a, port_b, or port_c).

You should accept the default value. Click Next.

The installer prompts you for the Cisco VNDS installation path.

Step 10 Specify the Cisco VNDS installation directory.

Caution When selecting or creating the installation directory for Cisco VNDS, make sure that the directory name DOES NOT contain embedded spaces.

a. Type an installation path in the panel’s path field or use the file browser to select an installation path. The path you enter is the parent directory for the installation. The default is /opt/cisco. The installer appends /VNDServer/<version>_<build> to the path you choose.

b. Click Next.

The installer displays the Enter File Ownership panel.

Step 11 Specify user and group ownership for the Cisco VNDS installation directory. The installer prompts you for the following information:

• User Name

• Group Name


OL-14565-01


Note The user must be a member of the specified group. The user will be the owner of the Cisco VNDS installation directory. Any user that is a member of the specified group will have appropriate permission to run the Cisco VNDS software.

a. Type a valid user name and group name into the appropriate fields.

b. Click Next.

The installer prompts you for the path to use for the Cisco VNDS temporary directory.

Step 12 Specify the Cisco VNDS temporary (temp) directory. This directory holds temporary working files for the product.

Caution When selecting or creating the temp directory for Cisco VNDS, make sure that the directory name DOES NOT contain embedded spaces.

a. Type a temp directory path in the panel’s path field or use the file browser to select a path. The path you specify is the full path to this directory.

Note Make sure that the specified directory has appropriate write permissions. The group specified in Step 11 must be able to write to this directory.

Note If you are updating, we recommend that you choose the same temp directory that you used in your previous installation.

b. Click Next.

The installer prompts you for the path to use for the Cisco VNDS config file archive directory.

Step 13 Specify the Cisco VNDS config file archive directory. This directory holds collected device configuration files that have been archived by the product.



OL-14565-01

Caution When selecting or creating the config file archive directory for Cisco VNDS, make sure that the directory name DOES NOT contain embedded spaces.

a. Type an archive directory path in the panel’s path field or use the file browser to select a path. The path you specify is the full path to this directory.

b. Click Next.

The Configure Virtual Network Data Server panel appears.

Step 14 The installer presents the following fields:

• Virtual Network Data Server Name

• Virtual Network Data Server ID (0-1022)

• Virtual Network Data Server Address

a. Type the primary IP address of the host in the Virtual Network Data Server Address field.

Note The primary IP address is required for all Cisco VNDS installations.

b. Fill in additional fields if this Cisco VNDS will participate in an n-tier hierarchy.

Note Each instance of Cisco VNDS that participates in a hierarchical configuration must have a unique server ID. If you want to change the server ID post-installation, you must clean the database and remove any existing data contained in it.

c. Click Next.

The installer displays the Configure Virtual Network Data Server Client Connectivity panel.

Step 15 Specify the Cisco VNDS Client Connectivity Port.

Type a port number and click Next (or only click Next to accept the default port, 3100).


OL-14565-01


Note The Client Connectivity port is the port on which Cisco VNDS’s Live Update Service runs. If you enter a non-default port, Cisco VNDS clients might not be able to communicate with Cisco VNDS until you make a corresponding change in the client’s Cisco VNDS LUS Port preference.

The installer prompts you to configure the web server.

Step 16 Specify web server parameters.

The installer allows you to specify the following:

• Virtual Network Data Server HTTP Port (default port is 9190)

• Virtual Network Data Server HTTPS Port (default port is 8543)

• Keystore Directory

Note Write down the web server connectivity settings for future use.

Fill in each field, then click Next (or only click Next to accept the default values).

The installer prompts you to set the Web Server administrator password.

Step 17 Specify the password for the administrator (admin) user account for the Virtual Network Data Server Web Console.

Type a password into the password fields, then click Next (or only click Next to accept default password cisco).

Note You will need the admin password for initial login to the Cisco VNDS Web Console, because local authentication is configured by default. After you log into the Web Console as the admin user, you can change the admin password and authentication scheme.

The installer prompts you to configure email notification parameters.

Step 18 If you want to begin receiving email notification as soon as you start Cisco VNDS services, configure email notifications at this time. If you choose not to specify values in the installer, you can configure Notification when you are ready to begin automated operation by using the Management (Mgmt) page in the Web Console.



OL-14565-01

Note If you are updating your Cisco VNDS installation, you can enter the values that you recorded using the “Recording Notification Settings” procedure on page 4-10. After the software installation is complete, however, you should review and configure the Selected notification conditions , because this list is set to 6.0 defaults during the update.

a. Enter the sender, recipients, and subject prefix for Cisco VNDS email notifications, or leave these fields empty if you want to configure Notification post-installation.

b. Click Next to proceed.

The installer prompts you for email server settings.

c. Enter the SMTP Server, Port, User Name, and Password, or leave these fields empty if you want to configure Notification post-installation.

d. Click Next to proceed.

An installation progress panel shows status messages as Cisco VNDS installation progresses. Installation normally finishes in several minutes.

• If an existing Cisco VNDS 4.0.3 or 4.5 installation is detected, the installer displays the Migrate Virtual Network Data Server product configuration? panel. Go to Step 19.

• If you are installing on a host that does not have Cisco VNDS 4.0.3 or 4.5 software installed, the installer displays the Web Services Note panel when installation is complete. Go to Step 21.

Step 19 Specify whether the installer should migrate configuration settings from the previous installation.

• To migrate previous settings, perform the following steps:

– Select Yes in the Migrate Virtual Network Data Server product configuration? panel, then click Next.

A confirmation dialog box appears. It provides the path of the previous installation (from which it will migrate product configuration) and lists the actions that will be performed during product configuration migration.

– Click Yes to continue with migration.


OL-14565-01


The installer displays progress as it migrates settings. When complete, the Migration Complete dialog appears. Go to Step 20.

• To install without migrating the previous product configuration, perform the following steps:

– Select No in the Migrate Virtual Network Data Server product configuration? panel, then click Next.

– Read the confirmation notice that appears.

– Click OK to confirm your decision and go to Step 21. (Click Previous to go back to the Migrate Virtual Network Data Server product configuration? panel.)

Caution If you chose not to migrate product configuration, but want to preserve the Device and Platform Info table or groups, you must export this information before you configure the database for use with Cisco VNDS 6.0. You can migrate adapter resources and text files after installation is complete as long as you do not uninstall or delete files from the previous release installation directory.

Step 20 Read the Migration Complete dialog.

This dialog summarizes the actions performed and provides the location of migration logs. Click OK to continue.

The Web Services Note panel appears.

Step 21 Read the Web Services Note, then click Next.

The installer displays the Install Complete panel.

Step 22 Click Done to exit the installer.

Step 23 (Update only) If Cisco VNDS and the Data Storage Server (PostgreSQL) are already installed on the host system and you are updating to a new release, you must configure the PostgreSQL database for Cisco VNDS 6.0 software.



OL-14565-01

Caution This script removes all data in the PostgreSQL database. DO NOT configure the PostgreSQL database for the new version of Cisco VNDS until you have successfully exported data that you want to preserve. See the “Preparing for an Update Installation” section on page 4-6 and contact Technical Support for assistance, if needed.

a. Log into the Cisco VNDS host as a user who has permission to run the Cisco VNDS software or switch to such a user account. Use the su - <user> command when switching users.

b. Open a command prompt and move to the Cisco VNDS 6.0 installation directory (/opt/cisco/VNDServer/<version>_<build>).

c. Enter the following command:

./vnes.sh CLEANALLDB

A Warning dialog appears.

d. Click Yes to continue.


Caution Do not attempt to start Cisco VNDS until you complete all steps in the installation workflow.

Licensing NotesYou must specify a licensing type for the Cisco VNDS software during installation. The installer provides the following options:

• Access licenses from a remote server—Selecting this option results in the Cisco VNDS software obtaining a license from a remote host.

• Serve licenses from a new license server on this computer—Selecting this option results in a license server being installed with the Cisco VNDS installation. See the Readme for information about the License Server


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying Data Storage Server Configuration

installed with this version of Cisco VNDS. Use the command ./vnes.sh LS to start the license server. The license server program must be manually restarted when the server reboots.

• Serve licenses from an existing license server on this computer—Selecting this option configures Cisco VNDS to use a license server that is already installed on the host as part of an existing Cisco software installation. No license server is installed by this installer.

Note The specified license server must have a valid Cisco VNDS license before you can run the software.

Verifying Data Storage Server ConfigurationPerform this procedure on the Cisco VNDS host to verify that you can connect to the Data Storage Server through the dssuser account and that the Data Storage Server is properly configured for use by Cisco VNDS.

Verifying Data Storage Server Configuration (Linux)

Step 1 Log into the Cisco VNDS host as a user that has permission to run Cisco VNDS, or switch to such a user account. Use the su - <user> command when switching users.

Note This user must be a member of the group specified during installation of Cisco VNDS. Do not attempt to run the software using the root account.


Step 3 Change directories to the Data Storage Server installation directory by entering the following command:

cd /usr/bin

Step 4 Verify that you can interface to the Data Storage Server using psql.

a. Enter the psql command to connect to the database:

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying Data Storage Server Configuration


OL-14565-01






b. Enter the password for the dssuser account.

A welcome message appears.

Note Contact Technical Support for assistance if an error message appears.

c. Type \q at the vnes=> prompt to quit psql.

Step 5 Test the Data Storage Server database configuration.

a. Stay in the command prompt and move to the Cisco VNDS installation directory (for example, /opt/cisco/VNDServer/<version>_<build>).


./vnes.sh DBAUTOTEST

Tests are run to verify that the dssuser account can perform needed operations in the Data Storage Server.

Output is written to the command window and a separate Java window opens to display a summary of results.

Step 6 Review the DBAUTOTEST results and verify that all tests passed. Figure 4-1 illustrates a successful result.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying the Cisco VNDS Software Installation

Figure 4-1 Example of Successful DBAUTOTEST Results (PostgreSQL)


• If any of the database tests fail, contact Technical Support (as described in the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page vii) and provide the DBAUTOTEST results.

• When all DBAUTOTEST tests pass, return to the workflow you are following and continue with the next step.

Verifying the Cisco VNDS Software InstallationPerform the following procedure to verify that the Cisco VNDS software is installed correctly.

Note Run Cisco VNDS software using any user account that is a member of the Cisco VNDS group specified during the software installation. Do not attempt to run the software using the root account.



OL-14565-01

Verifying the Cisco VNDS Installation (Linux)

Step 1 Verify that the license server specified during installation has a valid license available.

Note Do not proceed until you have verified that the appropriate license is available.


Caution Do not run the software using the root account. Run Cisco VNDS from any user account that is a member of the group specified during installation.

Step 3 Open the Cisco VNDS Control Panel, as follows:

a. Open a command window and move to the Cisco VNDS installation directory (for example: /opt/cisco/VNDServer/<version>_<build>).


./vnes.sh CP

Within a minute, the Cisco VNDS Control Panel appears.

Step 4 Start Cisco VNDS services from the Control Panel by clicking the Start Services button on the tool bar.

A progress dialog appears and, within a few minutes, service start-up completes.

Step 5 Verify communication with the Cisco VNDS Web Server via HTTP.

a. Start the Cisco VNDS Web Service by entering the following command:

./vnes.sh -c start WS

Note You must manually start the Web Service before you can access the Web Console.

a. Open the Web Console:


OL-14565-01


From the Control Panel menu bar, choose Configuration > Open Management Web Console.

The Web Console login page appears.

b. Verify that you can log in to the admin account using the password that you set during Cisco VNDS software installation.

c. Log out of the Web Console.

d. Close the browser window.

Step 6 Stop Cisco VNDS services from the Control Panel by clicking the Stop Services button on the tool bar.

A progress dialog box appears and, within a few minutes, services stop.

Note Some Cisco VNDS services continue to run in the background. Perform the “Shutting Down Cisco VNDS Using the Command Line (Linux)” procedure on page 4-31 if you want to completely shut down Cisco VNDS.

Note If the Control Panel fails to open, services fail to start or stop, or error dialog boxes appear, there is a problem with the installation. Review the Readme for known issues and workarounds. Contact Technical Support for assistance if problems persist.


Shutting Down Cisco VNDS Using the Command Line (Linux)

Use this procedure to shut down Cisco VNDS running on Linux.

Step 1 Log into the Cisco VNDS host as a user that has permission to run the Cisco VNDS software, or switch to such a user account. Use the su - <user> command when switching users.

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Finalizing the Update


OL-14565-01

Caution Do not run the software using the root account. Run Cisco VNDS from any user account that is a member of the group specified during installation.

Step 2 Stop Cisco VNDS services.

Step 3 Close all open Cisco VNDS windows and exit the Control Panel.

Step 4 Move to the Cisco VNDS installation directory (for example, /opt/cisco/VNDServer/<version>_<build>).



Finalizing the UpdateAfter you have successfully completed the “Verifying the Cisco VNDS Installation (Linux)” procedure on page 4-30, perform the following actions to complete your update:

1. Import Device and Platform Info table, if exported from the previous installation.

2. Import your Network Topology by running the appropriate adapters.

3. Import Device Groups, if exported from the previous installation.

4. Configure Notification settings using information from the “Recording Notification Settings” procedure on page 4-10.

5. Create local user accounts and configure authentication. See the “Creating Local User Accounts and Configuring Authentication” procedure on page 4-33.

6. Resume automated operation.

Use the following procedure to configure authentication settings and create local user accounts.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Collecting Oracle Database Access Information

Creating Local User Accounts and Configuring Authentication

Step 1 Log into the Web Console using the admin user account.

Step 2 Open the Users page of the Web Console.

Step 3 Create local user accounts. (Contact technical support for instructions on migrating local user accounts.)

If you do not migrate user accounts, create them manually using the information from the “Recording Authentication Settings” procedure on page 4-9. We suggest setting a default password and notifying users to change it after initial login.

Step 4 Configure Authentication, if needed.

If you use remote authentication, click on the Server link in the Users page and configure it with settings from the “Recording Authentication Settings” procedure on page 4-9.

Note Make sure that at least one local Cisco VNDS user account with the “admin” role has a matching user account (user names must match) on the remote authentication server before you switch to remote authentication.

Collecting Oracle Database Access InformationBefore you configure Cisco VNDS to use the Oracle database, you must collect the database access information listed in Table 4-4.

Print Table 4-4 and use it to write down the database access information for later reference. You will need information from this table when you do the Configuring Cisco VNDS to Use the Oracle Database (Linux) procedure and again when you do the Configuring the Oracle Database for Cisco VNDS (Linux) procedure.

The Oracle database administrator can supply the database access information that you need. (Also, see the “Locating an Oracle Database Net Service Name” section on page 4-45 for assistance in locating the Oracle Database Net Service name.)

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Collecting Oracle Database Access Information


OL-14565-01

When you have collected the needed information, continue with the “Configuring Cisco VNDS to Use the Oracle Database” procedure on page 4-35.

Note The Database Account User Name in Table 4-4 is the account used by Cisco VNDS to access network data stored in the database.

Caution DO NOT use SYS or SYSTEM for the Database Account User Name.

Table 4-4 Database Access Information Worksheet

Access Item Value Description

Database TNS Service Name (alias for Database GDN)

The TNS Net Service name used for the local or remote database. See Locating an Oracle Database Net Service Name, page 4-45, for instructions on locating the service name.

Database SID The database SID.

Database hostname The IP address or fully qualified domain name for the database host. Needed only for remote databases.

Oracle Home (installation) directory

The Oracle installation directory on the database host. Needed only for remote databases.

Oracle Oradata Parent directory

The parent directory to the Oracle oradata directory on the database host. Needed only for remote databases.

Database account user name

User name for the account used to access the database. DO NOT use the Oracle SYS or SYSTEM accounts.

Database account password

Password for the account used to access the database.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Configuring Cisco VNDS to Use the Oracle Database

Configuring Cisco VNDS to Use the Oracle DatabasePerform the following procedure to configure the Cisco VNDS 6.0 software to use an existing dedicated Oracle database.

Configuring Cisco VNDS to Use the Oracle Database (Linux)


Note This user must be a member of the group specified during installation of Cisco VNDS. Do not attempt to run the software using the root account.

Step 2 If Cisco VNDS is running, exit the product and shut it down:

a. Stop Cisco VNDS operation by choosing Services > Stop Services from the Cisco VNDS Control Panel menu bar.

b. Exit Cisco VNDS by choosing File > Exit from the Control Panel menu bar.

c. Open a command prompt and move to the Cisco VNDS installation directory (for example: /opt/cisco/VNDServer/<version>_<build>).

d. Enter the following command:


Step 3 Make sure the Oracle database is running, as follows.

Enter the following command on the database host:

ps -aef | grep ora_

You should see a number of processes with the following naming convention:

ora_<process>_<sid>

If the Oracle database is not running, contact your database administrator to start the database.

Note Do not proceed until you have confirmed that the database is running.

Step 4 Stay in the command window and move to the following directory:



OL-14565-01

<vnds_install>/misc

Step 5 Switch users to root. Use the su - <user> command when switching users. For example:

su - root

Note You must use the root account to configure Cisco VNDS software to use an Oracle database.

Step 6 Start the conversion program (pg2oracle.bin):

a. Insert the Cisco VNDS installation DVD into the DVD drive of the host PC.

b. Run the pg2oracle.bin program.

The program displays an Introduction panel.

Step 7 Click Next.

The installer displays the Specify database type panel.

Step 8 Specify parameters that describe the Oracle installation that Cisco VNDS will use. The installer prompts you for the following:

• Choose whether the database is local or remote

• Choose whether you are using a 32-bit or 64-bit Oracle

Make your selections, then press Next.

The installer displays the Specify an Oracle database panel.

Step 9 Specify the Oracle database that Cisco VNDS will use. The installer prompts you for the following database access information:

• Database TNS Service Name

• Database SID

• Database Hostname

• Local Oracle Installation Directory

• Base Directory for Database

Fill in each field with the information collected in Table 4-4 on page 4-34, then click Next.

The installer displays the Specify account information for the Oracle database panel.


OL-14565-01


Step 10 Specify values for the account Cisco VNDS will use to access the Oracle database.

• Database User Name

• Database Password


Note Set the database password to the same password that was entered for the dssuser account during installation of Cisco VNDS. Update Table 4-4 on page 4-34 with this password if it is different from the value that was previously recorded.

Fill in each field with the information collected in Table 4-4 on page 4-34, then click Next.

• If you specified a local database in Step 8, the installer displays its progress while the conversion is performed. Go to Step 12.

• If you specified a remote database in Step 8, the installer displays the Choose the Oracle version panel. Continue with Step 11.

Step 11 Specify the Oracle version for the remote database. The choices are

• Oracle9i

• Oracle10g

Choose the appropriate Oracle version, then click Next to continue.

The installer displays its progress while the conversion is performed.

Step 12 The Conversion Complete panel appears. Click Done to exit the program.

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Configuring the Oracle Database for Cisco VNDS


OL-14565-01

Configuring the Oracle Database for Cisco VNDSWhen you configure Cisco Virtual Network Data Server to use an Oracle database, that database must be configured for use by Cisco VNDS. This involves running an SQL script named setup_accounts.sql that creates tablespaces for the database and a Cisco VNDS database account. This SQL script is run on the host system for the Oracle database.

Caution Do not modify the setup_accounts.sql script. This can cause the installation to fail or prevent Cisco VNDS from operating correctly.

Perform the following procedure on the database host to configure the Oracle database for Cisco VNDS.

Caution If you want to preserve the Device and Platform Info table or device groups from your Cisco VNDS 4.0.3 or 4.5 installation when you update to Cisco VNDS 6.0, DO NOT configure the Oracle database for the new version of Cisco VNDS until you have successfully exported any needed data to text files, as described in the “Preparing for an Update Installation” section on page 4-6.

Configuring the Oracle Database for Cisco VNDS (Linux)

Note Use this procedure if the Oracle database is installed on a Linux host. If the Oracle database is installed on a Windows host, use the “Configuring the Oracle Database for Cisco VNDS (Windows)” procedure on page 3-39.

Step 1 Log into the database host PC as oracle or switch users to the oracle account.


su - oracle

Step 2 (Remote database only) Copy the SQL scripts from the Cisco VNDS installation directory to a directory on the database host where the oracle user has execute permission. The SQL scripts have a file extension of .sql.

Step 3 Move to the directory on the database host that contains the SQL scripts.


OL-14565-01


Stay in the command window on the database host (as oracle) and continue with the next step.




For example, if the password for the system account is magic, enter:




For example, if the Database TNS Service Name is o92adata and the password for the system account is magic, enter:



@setup_accounts.sql

A message banner appears to inform you how much free disk space is required on the disk that hosts the database.

Note If you do not have sufficient disk space available to run this script, free up sufficient disk space before proceeding. If you want to cancel the script, type Ctrl-C or close the command window.


A message banner displays a notification about Device and Platform Info. Review this warning.

• For Oracle9i, continue with Step 7.

• For Oracle10g, go to Step 8.



OL-14565-01

Note In 4.0 and later versions of Cisco VNDS, the Device and Platform Info is stored in the database. To preserve this information, you must export the Device and Platform Info table to a file. If you are updating from an existing 4.0.3 or 4.5 installation, export Device and Platform Info table before you proceed. If you want to cancel the script, type Ctrl-C or close the command window.

Step 7 (Oracle 9i only) Press Enter to continue.

When configuring an Oracle 9i database, the setup_accounts script analyzes database parameters and displays a message banner with a list of database parameters, database parameter settings, and whether the settings meet recommended values. A log of database analysis results is saved to <vnds_install>/analyzedb.<timestamp>.log.

Note If all parameters meet recommended settings, no further action is required. If one or more parameters do not meet recommended settings, a recommendation is made that you run the dbparamchg.sql script after this procedure is completed. Running the dbparamchg.sql script will improve data import performance with large networks (but also increase Oracle memory requirements).


A list of database names is displayed. If you have a database dedicated only to Cisco VNDS, one entry appears.

Step 9 Verify the database instance name.

Note If the database is located on a Solaris or Linux system, the database instance name is case-sensitive and must match the name of the database directory located under the oradata directory (for example, /uo1/app/oracle/oradata) on the database host. Look in the oradata directory to ensure that the database instance name you enter is a case-sensitive match.


The setup_accounts script prompts you for the database instance name.


OL-14565-01


Step 11 Enter the database instance name obtained in Step 9.

The setup_accounts script prompts you for the user password.

Step 12 Enter the same database user account password that was entered during Cisco VNDS installation and written down in Table 4-4 on page 4-34.

A message appears to inform you that the Cisco VNDS database user account and all data will be deleted by this script.


The setup_accounts SQL script configures the Oracle database for use by Cisco VNDS and sets up the user account. After the script finishes, the Oracle account information for Cisco VNDS is the database user name and password from Table 4-4 on page 4-34. A log of script actions is saved to <vnds_install>/setup_accounts.<timestamp>.log.

Note When you run this script for the first time, several SQL error messages appear. You can ignore these messages. The messages are the result of the script trying to remove Cisco VNDS table and user accounts that do not exist prior to this script being run for the first time.


If the setup_accounts script recommended changing your database settings during Step 7 and you agree with the recommended changes, go now to the “Modifying Oracle Database Parameters” section on page 4-41.

If you do not need to change your database settings or you choose not to change them, go to the “Verifying the Oracle Configuration for Cisco VNDS” section on page 4-43 to verify that Oracle is configured correctly for use with Cisco VNDS.

Modifying Oracle Database ParametersPerform the following procedure on the Oracle 9i database host to modify database parameters. The database parameter changes improve Cisco VNDS performance when working with large networks (but will increase Oracle memory requirements).



OL-14565-01

Do not modify database parameters for Oracle 10g unless instructed to do so by Technical Support.

Note Work with your Oracle Database Administrator to run this script.

Modifying Oracle Database Parameters (Linux)

Step 1 Log into the database host as oracle or switch users to the oracle account.


su - oracle


Step 3 Move to the Cisco VNDS installation directory or the directory where you copied the Cisco VNDS SQL scripts.

Stay in the command window on the database host (as oracle) and continue with the next step.


• For a local Oracle database installation, enter the following command in the command window:


For example, if the password for the system account is magic, type:


• If the Oracle database is not on the same host system as Cisco VNDS, enter the following command in the command window:


For example, if the TNS Service Name is o92adata and the password for the system account is magic, type:



@dbparamchg.sql

A message is displayed that shows the path to the Oracle spfile that contains the parameters for your database.

Step 6 Make a backup copy of the spfile at the path specified in the previous step.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying the Oracle Configuration for Cisco VNDS

Step 7 Press Enter as many times as needed to step through the information messages produced by this script.

When the script is done, a list of the changed parameters and their new settings appears with a reminder to restart the Oracle DB service for the changes to take effect.


Step 9 Stop and restart the Oracle database service.

Step 10 If the Oracle database service fails to restart, restore the original spfile for the database and repeat Step 9 to recover.

Continue with the “Verifying the Oracle Configuration for Cisco VNDS” section on page 4-43 to verify that you can connect to the database through the Cisco VNDS account.

Verifying the Oracle Configuration for Cisco VNDSPerform the following procedure on the Cisco VNDS host to verify that you can connect to the database through the Cisco VNDS database user account.

Verifying the Oracle Configuration (Linux)

Step 1 Log into the database host as oracle or switch users to the oracle account.


su - oracle




Use the database user name and password from Table 4-4 on page 4-34. For example, if the Cisco VNDS database user name and password are vnds and pwd, respectively, enter:

sqlplus vnds/pwd


Chapter 4 Installing Cisco Virtual Network Data Server on Linux Verifying the Oracle Configuration for Cisco VNDS


OL-14565-01


Use the database user name and password from Table 4-4 on page 4-34. For example, if the Database TNS Service Name is o92adata and the Cisco VNDS database username and password are dbuser and pwd, respectively, enter:


Step 3 If Oracle configuration was not successful, error messages are displayed indicating that login has been denied.

Reconfigure the Oracle database and verify again.

Step 4 If configuration of the Oracle account for Cisco VNDS was successful, an Oracle banner and a Connected To: message appear.


Step 6 Test the Oracle database configuration.

a. Switch users to a user with permission to run Cisco VNDS.

Use the su - <user> command when switching users. For example, if vnds_user is a user account that is a member of the group that has permission to run Cisco VNDS, enter:

su - vnds_user

b. Move to the Cisco VNDS installation directory (for example: /opt/cisco/VNDServer/<version>_<build>).

c. Enter the following command:

./vnes.sh DBAUTOTEST

Tests run to verify that the Cisco VNDS account can perform needed operations in Oracle. Output is written to the command window and a separate Java window opens to display a summary of results.

d. Review the DBAUTOTEST results and verify that all tests passed. Figure 4-2 shows a successful result.


OL-14565-01

Chapter 4 Installing Cisco Virtual Network Data Server on Linux Locating an Oracle Database Net Service Name

Figure 4-2 Example of Successful DBAUTOTEST Results (Oracle)


If any of the database tests fail, contact Technical Support (as described in “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page vii) and provide the DBAUTOTEST results.

When all database tests pass, continue with your installation workflow.

Locating an Oracle Database Net Service NameThis section provides assistance for locating an Oracle Database Net Service Name in a tnsnames.ora file.

Note Cisco VNDS uses the Oracle Net service name to connect to an Oracle database. This is true whether Cisco VNDS uses a local or remote Oracle database.

The database service name is located in the tnsnames.ora file. The location of this file varies by Oracle version:

• Oracle 9i: <oracle install dir>/ora92/network/Admin

• Oracle 10g: <oracle install dir>/product/10.2.0/db_1/NETWORK/ADMIN



OL-14565-01

A sample file is shown in Figure 4-3. In this sample file, there are three entries. The O92ML23 entry represents the database service name. Each entry has a <net service name> = () structure. The text string preceding the “=” is the service name. In this example, you use O92ML23 as the service name when you configure Cisco VNDS to use an Oracle database.

Note The tnsnames.ora file has entries for several Oracle Net services. Contact the database administrator if you are unsure of the service name that Cisco VNDS should use when connecting to the Oracle database.


OL-14565-01


Figure 4-3 Sample tnsnames.ora File

# TNSNAMES.ORA Network Configuration File: D:/oracle/ora92/NETWORK/ADMIN/tnsnames.ora# Generated by Oracle configuration tools.

092ML23 =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = mlpc23)(PORT = 1521))(ADDRESS = (PROTOCOL = IPC)(Key = EXTPROC0))

)(CONNECT_DATA =

(SERVER = DEDICATED)(SERVICE_NAME = o92ml23)

))

INST1_HTTP =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = mlpc23)(PORT = 1521))

)(CONNECT_DATA =

(SERVER = SHARED)(SERVICE_NAME = MOD0SE)(PRESENTATION = http://HRService)

))

EXTPROC_CONNECTION_DATA =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))

)(CONNECT_DATA =

(SID = PLSExtProc)(PRESENTATION = R0)

))



OL-14565-01

C H A P T E R


OL-14565-01

5Managing Licenses

To start a program such as Virtual Network Data Server, you must have a valid license for that program installed on the local or a remote computer.

This chapter describes the following operations:

• Adding a License, page 5-3—Perform this workflow if you have purchased an initial or additional license and want to add it.

• Upgrading a License, page 5-4—Perform this workflow if you have already added a Restricted license and want to upgrade it to an Unrestricted license.

• Deregistering a License, page 5-7—Perform this workflow if you need to deregister a license.

Note Licenses (that is, the License Manager) must reside on a host that is accessible to the component program at startup. This can be the local host where the component program is installed or a remote host. For more information about licensing options, see the “Product Licensing” section on page 1-5.

Chapter 5 Managing Licenses Using the License Manager


OL-14565-01

Using the License ManagerYou can see which licenses and license servers are installed on your network by using the License Manager. You can also perform license operations from the License Manager using the following procedure.

Note A License Manager can access the licenses and license servers on any host of the same IP network.

Step 1 Log on to a computer that has at least one of the following products installed:

• Cisco Application Analysis Solution


• Cisco Configuration Assurance Solution–SP


• Cisco Network Planning Solution–SP

Step 2 Start the License Manager for the installed product.

On a Windows host:

• Choose Start > Programs > <solution_name> 2.1 > License Manager.

On a Linux host:

• Log into a user account.

• Enter the command: op_license_manager

Step 3 In the License Manager, select the license(s) or license server you want to act on, then click on the correct operation button on the right.

Note The License Manager might show some child windows that prompt you for additional information, such as which product modules to use. You do not need to specify these options to use the License Manager; generally you can click OK to accept the default settings and close the child window.


OL-14565-01

Chapter 5 Managing Licenses Adding a License

Adding a LicenseTable 5-1 shows the workflow for adding your licenses.

Obtaining a Username and PasswordTo add a license, you must have a valid username, password, and group ID. To obtain this information, you must register your Cisco VNDS product. Instructions for doing this are listed on the Software License Claim Certificate that is included in your product installation package. For more information, see the “Registering Cisco Virtual Network Data Server” section on page 1-4.

After your registration is confirmed, you will receive an email with a username, password, and Group ID number. You will need this information when you add the component licenses as described in the following sections.

Table 5-1 Adding a License: Workflow


Step 1 Obtain a username and password (if you have not done so already)

Obtaining a Username and Password, page 5-3

Step 2 Prepare the license directory (first-time Linux installations only)

Preparing the License Directory, page 5-4

Step 3 Add program license(s) using one of the following methods for each license:

• Express method Adding a License (Express Method), page 5-8

• Browser method (if Express method does not work)

Adding a License (Browser Method), page 5-9

• Contact technical support (if Express and Browser methods do not work)

Technical Support for Licensing Operations, page 5-16

Note You must repeat the Add License procedure for every computer on which you want to add a license. In this case, you must do the add-license operation twice—once for each computer.

Chapter 5 Managing Licenses Upgrading a License


OL-14565-01

After you obtain a username and password, you can add your licenses as described in the “Adding a Component License (Express Method)” procedure on page 5-8 or the “Adding a Component License (Browser Method)” procedure on page 5-10.

Preparing the License DirectoryDo this procedure only if this is a first-time Linux installation and you chose one of the following options when prompted to specify the type of licensing system:

• Standalone

• Floating -- serve licenses from this computer

Setting Permissions for the License Directory

Step 1 Verify that you are logged in as root on the host where you want to install the licenses.

Step 2 Verify that the opt/OPNET_license directory exists:

• Enter the following command to see if the directory exists:

ls /opt

• If the OPNET_license directory is not listed in the output, create the directory by entering the following command:

mkdir /opt/OPNET_license

Step 3 Set permissions on the directory by entering the following command:

chmod 777 /opt/OPNET_license


Upgrading a LicenseTable 5-2 shows the workflow for upgrading your licenses. For information about different grades of licenses, see the “Product Licensing” section on page 1-5.


OL-14565-01


Getting an Upgrade AuthorizationBefore you can upgrade a license, you must obtain authorization. To obtain an authorization, do the following:

Step 1 Go to the following URL:

Table 5-2 Upgrading a License: Workflow


Step 1 Obtain an upgrade authorization Getting an Upgrade Authorization, page 5-5

Step 2 Deregister the original (Restricted) license using one of the following methods:

• Express method Deregistering a License (Express Method), page 5-12


Deregistering a License (Browser Method), page 5-13



Step 3 Add the upgraded (Unrestricted) version of the original license using one of the following methods:

• Express method Adding a License (Express Method), page 5-8

• Browser method Adding a License (Browser Method), page 5-9



Note You must perform both procedures—that is, deregister the Restricted license and add the Unrestricted license—before you can use Unrestricted licensing mode. Also, keep in mind that after you deregister your current (Restricted) license, you will be unable to use the software until you register the updated (Unrestricted) license.



OL-14565-01


Step 2 Follow the My PAKS link to see the Product Authorization Keys you have added already. Note the PAK of the product that you want to upgrade from Restricted to Unrestricted.

Step 3 Go to one of the URLs listed in the“Registration Information” section on page 1-4.

Step 4 Follow the instructions on the licensing page. You must submit the Product Authorization Key for both the new license and the original license that you want to upgrade.

After you submit the requested information, you will receive an authorization by e-mail to proceed with the upgrade (go to Step 2 of Upgrading a License, page 5-4).

Adding a Module to the Product Options ListAfter you add a license for a product module, you must update your Product Options list so that the program requests the module license on startup.

Adding a Module to the Product Options List

Step 1 Start the program to which the product module applies.

Step 2 In the main program window, choose License > Product Modules.

Step 3 In the Select Product Modules, select the checkbox for the module you have added. Then click OK.

Step 4 For the change to take effect, you must exit and restart the program.



OL-14565-01

Chapter 5 Managing Licenses Deregistering a License

Deregistering a LicenseTable 5-3 shows the workflow for deregistering licenses.

Refreshing a LicenseAfter installing an update to the Cisco Virtual Network Data Server software, you must refresh your licenses by contacting technical support as described in the “Technical Support for Licensing Operations” section on page 16.

Table 5-3 Deregistering a License: Workflow


Step 1 Deregister a program license(s) using one of the following methods for each license:

• Express method Deregistering a License (Express Method), page 5-12


Deregistering a License (Browser Method), page 5-13



Chapter 5 Managing Licenses License Operations


OL-14565-01

License Operations

Adding a License (Express Method)The following procedure is the quickest and easiest way to add a license. This method requires that your computer be able to communicate directly with the license-registration server over the Internet, either directly or using a proxy server.

Note The Express method can fail due to firewall restrictions, socket or proxy errors, or transaction time-outs. If you cannot add the license using this method, try the Browser method (as described in Adding a License (Browser Method), page 5-9).

Adding a Component License (Express Method)

Step 1 Log on to a computer that has at least one of the following programs installed:






Step 2 Start the License Manager for the installed program.

On a Windows host:


On a Linux host:



Step 3 In the License Manager, click on the green dot that represents the license server on the computer where you want to add the license. (The license server computer might not be the same as your local computer.)

Click on the Add License button on the right side of the box.


OL-14565-01


Step 4 When prompted to select the transaction method, click Express. This method is easiest and fastest.

Step 5 Enter the Username, Password, and Group ID that you received when you registered your product (as described in the “Obtaining a Username and Password” section on page 5-3).

Step 6 If the computer uses a proxy server, click on Specify Proxy button and fill in the information.

Step 7 The next screen shows a list of available licenses. To select one license, click on it. To select multiple licenses, control-click or drag on the licenses.

Note Select only the licenses you want to add to the computer of the license server you have selected. (If you also want to add other licenses to a different computer, you must repeat this procedure for that computer.)

Step 8 After you select the licenses you want to add, click on the Add License button at the bottom. A progress window might appear while the license is added to your computer. A window should then appear and say that the license operation succeeded.

Step 9 When the operation is complete, the Select Product Modules box might appear. This allows you to select the modules you want to use. (In most cases, you should select all available modules.)

Step 10 To start using the program, exit the License Manager and start the program.

Adding a License (Browser Method)Before using the Browser method, try the Express method. With the Express method, there is no need to exchange codes and you can add many licenses to your computer in one operation. Use this procedure if the Express method fails or you prefer to use the Browser method.

Note If you still cannot add your licenses using this method, see the “Technical Support for Licensing Operations” section on page 5-16.



OL-14565-01

Adding a Component License (Browser Method)








On a Windows host:


On a Linux host:



Step 3 License Manager: Click on the green dot that represents the license server on the computer where you want to add the license. (The license server computer might not be the same as your local computer.)

Click Add License on the right side of the window.

Step 4 License Manager: When prompted, click Browser. The following events should now occur:

• The License Manager launches your Web browser and points it to the Cisco Solutions Quick Support page.

• The License Manager shows a transaction code and a hostname.

Step 5 Web browser: Enter the Username and Password that you received when you registered your product (as described in the “Obtaining a Username and Password” section on page 5-3).

If your browser fails to launch, start it manually and navigate to the following URL:


Then follow the My Licenses link in the browser window.



OL-14565-01


Step 6 Web browser: Click Perform license operations, then select Add License (add_permits) and click Next. Back in the License Manager, a dialog box containing a Transaction Code and Hostname field should appear.

Step 7 Web browser: Copy the Transaction Code and Hostname from the License Manager into the corresponding fields in the browser. You can either copy/paste the text or type it manually.

Note Make sure there are no extra spaces before or after the code or hostname.

Step 8 Web browser: Click Next.

Step 9 Web browser: When the Select the starting license number page appears, select the lowest license ID that you want to add to your computer. If you want to add only one license, select that license.

Step 10 Web browser: When the Select the ending license number page appears, select the highest license ID that you want to add to your computer. If you want to add only one license, select that license. The confirmation page appears.

Step 11 Web browser: When the License Registration Confirmation page appears, check that the information is correct, then click Get Approval Code. The approval code appears.

Step 12 License Manager: Click Next and enter the approval code that appears in the web browser.

Note This code can be very long, so make sure you copy the entire approval code.

Step 13 License Manager: After you enter the approval code, click Next.

Step 14 License Manager: If the Select Product Modules license window appears, click OK. Then click File > Exit to close the License Manager.

Step 15 To start using the program, exit the License Manager and start the program.



OL-14565-01

Deregistering a License (Express Method)The following procedure is the quickest and easiest way to deregister a license. This method requires that your computer be able to communicate directly with the license-registration server over the Internet, either directly or using a proxy server.

Note The Express method can fail due to firewall restrictions, socket or proxy errors, or transaction time-outs. If you cannot deregister the license using this method, try the Browser method (as described in the “Deregistering a License (Browser Method)” section on page 5-13).

Deregistering a Component License (Express Method)








On a Windows host:


On a Linux host:



Step 3 In the License Manager, expand the license file by clicking on the + sign next to the License file folder icon. Make sure the license you want to deregister is available (green).


OL-14565-01


Note If a license is represented by a “white page” icon, that license is currently in use. If you want to deregister a license that is in use, quit the component that is using it, then choose File > Refresh Server Information in the License Manager.

Step 4 Select the license you want to deregister by clicking on it. To select one license, click on it. To select multiple licenses, control-click or drag on the licenses.

Step 5 Click Deregister License on the right side of the License Manager window.

Step 6 When prompted to select the transaction method, click Express. This method is easiest and fastest.

Step 7 When the Authentication window appears, enter your Username, Password, and Group ID in the appropriate fields.

Step 8 If the computer uses a proxy server, click Specify Proxy; when the Specify proxy server information window appears, fill in the requested information and click OK.

Step 9 Click OK in the Authentication window.

• A progress window might appear while the license is deregistered from your computer.

• A window should then appear to indicate that the operation succeeded.

Deregistering a License (Browser Method)Before using the Browser method, try the Express method. With the Express method, there is no need to exchange codes and you can add many licenses to your computer in one operation. Use this procedure if the Express method fails or you prefer to use the Browser method.

Note If you still cannot deregister your licenses using this method, see the “Technical Support for Licensing Operations” section on page 5-16.



OL-14565-01

Deregistering a Component License (Browser Method)








On a Windows host:


On a Linux host:



Step 3 License Manager: Expand the appropriate license file by clicking on the + sign next to the License file folder icon. Make sure the license you want to deregister is available (green).

Note If a license is represented by a “white page” icon, that license is currently in use. If you want to deregister a license that is in use, quit the component that is using it, then choose File > Refresh Server Information in the License Manager.

Step 4 License Manager: Select the license you want to deregister by clicking on it. To select one license, click on it. To select multiple licenses, control-click or drag on the licenses.

Step 5 License Manager: Click Deregister License.

Step 6 License Manager: When prompted, click on the Browser button.

Step 7 The License Manager launches your Web browser and points it to the Cisco Solutions Quick Support page. If your browser fails to launch, start it manually and navigate to the following URL:




OL-14565-01


Step 8 Web browser: Log in with your username and password. Then click on My Licenses.

Step 9 Web browser: Follow the Perform license operations link, then select Deregister License (delete_permits) and click Next.

Back in the License Manager, a dialog box containing a Transaction Code and Hostname field should appear.

Step 10 Web browser: Copy the Transaction Code and Hostname from the License Manager into the browser window, then click Next. You can either paste the text or type it manually.

Note Make sure there are no extra spaces before or after the text you enter.

Step 11 Web browser: When the Select the starting license number page appears, select the lowest license ID that you want to deregister from your computer. If you want to deregister only one license, select that license.

Step 12 Web browser: When the Select the ending license number page appears, select the highest license ID that you want to deregister from your computer. If you want to deregister only one license, select that license.

Step 13 Web browser: When the License Registration Confirmation page appears, check that the information is correct, then click Get Approval Code. The approval code appears.

Step 14 License Manager: Click Next and enter the approval code that appears in the browser.

Note This code can be very long, so make sure you copy the entire approval code.

Step 15 License Manager: Click Next. The confirmation code appears.

Step 16 Web browser: Enter the confirmation code that appears in the License Manager, then click Next.

The confirmation code is saved in the Session Log, which is available from the Help menu in the License Manager.

Chapter 5 Managing Licenses Technical Support for Licensing Operations


OL-14565-01

Step 17 License Manager: click Done. The license is deregistered and you can now add it to another computer.

Technical Support for Licensing OperationsIf you cannot manage your licenses using the Express or Browser methods, or if you have additional questions or problems regarding your licenses, you can do the following:

• Go to the Cisco Solutions Quick Support page:


• Contact technical support as described in the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page vii

http://www.opnet.com/support/cisco_qsp.html)

C H A P T E R


OL-14565-01

6Uninstalling Cisco Virtual Network Data Server

Use the procedures in this chapter to uninstall the Cisco VNDS software:

• Removing Cisco VNDS Oracle Database Contents (Optional), page 6-1

• Uninstalling Cisco VNDS (Windows), page 6-3

• Uninstalling Cisco VNDS (Linux), page 6-8

• Uninstalling a License Server, page 6-9

• Uninstalling the Data Storage Server, page 6-11

Removing Cisco VNDS Oracle Database Contents (Optional)

If you want to completely remove the tablespace files and user account for Cisco VNDS 6.0 from a local Oracle database, perform the “Removing Cisco VNDS Oracle Database Contents” procedure on page 6-2. You do not need to perform this procedure if you are updating the Cisco VNDS installation.

Caution Perform this procedure only if you are permanently removing Cisco VNDS from a system AND want to remove the Oracle database contents as well as the product installation.

Chapter 6 Uninstalling Cisco Virtual Network Data Server Removing Cisco VNDS Oracle Database Contents (Optional)


OL-14565-01

Note If you choose to perform this procedure, you must do it before you remove the Cisco VNDS installation.

Removing Cisco VNDS Oracle Database Contents

Step 1 Log into the Cisco VNDS host using an account with administrator and ORA_DBA privileges.

Step 2 Stop services and exit the Control Panel.

Step 3 Open a command window and use the cd command to set the working directory to the Cisco VNDS installation directory. An example installation directory might be:

• Windows: C:\Cisco\VNDServer\6.0.2_<build_number>

• Linux: /opt/cisco/VNDServer/6.0.2_<build_number>

Step 4 Stop all Cisco VNDS background services/daemons by entering the following command:

• Windows: vnes.bat /svc_cmd stop ALL

• Linux: vnes.sh -c stop ALL

Step 5 Type: sqlplus system/<password>

A Connected to: banner message appears if you succeed in logging into Oracle.

Step 6 To get a list of database instance names, type: select name from v$database;

A list (probably just one item) of database names known to Oracle appears. If more than one name appears, work with your DBA to identify which one is used for Cisco VNDS.

Step 7 While still in sqlplus, type: @drop_accounts.sql <dbname>

where the <dbname> is the one identified in the previous step.

• Progress messages appear as the user account and tablespace files are deleted.

• When done, the database instance still exists, but the tables and account used by Cisco VNDS no longer exist.


OL-14565-01

Chapter 6 Uninstalling Cisco Virtual Network Data Server Uninstalling Cisco VNDS (Windows)

Note ALL network project data written to the Oracle database by Cisco VNDS is deleted by this procedure.

Uninstalling Cisco VNDS (Windows)This section includes the following procedures for removing Cisco VNDS from a Windows host computer.

Use the “Uninstalling Cisco VNDS on Windows (Standard)” procedure on page 6-4 to uninstall the current release. If you wish to completely remove all traces of the current release from a computer, first perform the “Uninstalling Cisco VNDS on Windows (Standard)” procedure on page 6-4, then continue with the “Removing All Cisco VNDS Elements (Advanced)” procedure on page 6-5.

To uninstall the previous version of Cisco VNDS after you update to the current release, perform “Removing Prior Cisco VNDS Release After Software Update (Windows)” procedure on page 6-7.

Procedure Description

Uninstalling Cisco VNDS on Windows (Standard), page 6-4

Procedure for uninstalling Cisco VNDS 6.0.

Removing All Cisco VNDS Elements (Advanced), page 6-5

Procedure for removing residual elements of the Cisco VNDS 6.0 installation (such as top-level Windows Registry keys and Program Group shortcuts).

Perform this procedure ONLY if you need to completely remove everything installed or generated by Cisco VNDS 6.0.

Removing Prior Cisco VNDS Release After Software Update (Windows), page 6-7

Procedure for removing Cisco VNDS 4.5 following successful installation of Cisco VNDS 6.0 and migration of product configuration.



OL-14565-01

Uninstalling Cisco VNDS on Windows (Standard)Perform the following procedure to remove the Cisco VNDS 6.0 software from your Windows computer.

Step 1 Log into the Cisco VNDS host using an account with administrator privileges.

Step 2 Stop services and exit the Control Panel.

Step 3 Open a command window and use the cd command to set the working directory to the Cisco VNDS installation directory. An example installation directory is:

C:\Cisco\VNDServer\6.0.2_<build_number>

Step 4 Stop all Cisco VNDS background services by entering the following command:


Step 5 Open the Windows Control Panel from the Start menu: Start > Settings > Control Panel.

Step 6 In the Windows Control Panel, double-click Add/Remove Programs.

Step 7 Scroll down the list of installed programs, select the entry for Cisco Virtual Network Data Server 2.1, and click Remove.

The Windows uninstaller removes the following items:

• Windows services

• Most Windows Registry entries

• Most Program Group shortcut entries

• Most of the installation directory

Step 8 Delete the remnants of the corresponding installation directory. For example, the installation directory might be:


After you complete this procedure, the following items remain:

• top-level Windows Registry entry for the release

• top-level Program Group shortcut for the release

• Cisco VNDS temporary directory


OL-14565-01


• Cisco VNDS archive directory

• Jre directory

Removing All Cisco VNDS Elements (Advanced)If you want to completely remove all traces of Cisco Virtual Network Data Server 6.0 from a computer, first perform the “Uninstalling Cisco VNDS on Windows (Standard)” procedure on page 6-4, then use the “Removing All Cisco VNDS Elements (Advanced)” procedure on page 6-5 to remove residual components of the installation.

Note Perform this procedure ONLY if you need to completely remove everything installed or generated by Cisco VNDS 6.0.

Removing All Cisco VNDS Elements

Step 1 Perform the “Uninstalling Cisco VNDS on Windows (Standard)” procedure on page 6-4 if you have not already done so.


Note If you have another Cisco VNDS release that you want to keep and it uses the same parent directory, skip Step 3.

Step 3 Delete the temporary directory. Typical temporary directory: C:\op_admin\temp\vne.

Note If you have another Cisco VNDS release that you want to keep and it uses the same archive directory, skip Step 4.

Step 4 Delete the archive directory. Typical archive directory: C:\op_admin\archive.



OL-14565-01

Note If you have another Cisco VNDS release that you want to keep and it is installed to the same parent directory (for example C:\Cisco), skip Step 5. Otherwise, you’ll remove the Jre used by a release you want to keep.

Step 5 Delete the Java Jre directory (if it remains). This directory is located under the parent install directory. Typical Jre directory: C:\Cisco\Jre.

Step 6 Delete the top-level Program Group shortcut for the release. All users have a shortcut. Delete the Cisco Virtual Network Data Server 2.0 shortcut from:

C:\Documents and Settings\All Users\Start Menu\Programs

Step 7 Start regedit: From the Windows Start menu, choose Run; then enter regedit and click OK.

Caution Be very careful when you edit the system registry. Incorrect changes to the registry can cause your Windows system to become unstable. You might want to create a backup before editing the registry.

Step 8 In the Windows Registry Editor, find and select the registry key for the software being removed. Example registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\OPNET Technologies\Cisco VND Server 6.0.2

Step 9 Select Delete from the menu to delete the entry.

Step 10 Verify that the uninstaller entry in the Registry has been removed. Remove the entry if it still exists in the Registry at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\

Uninstall

Example entry:

Cisco Virtual Network Data Server 2.1

Step 11 Verify that any services installed by Virtual Network Data Server are gone. Remove the following services if they still exist in the Registry at the following location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

-OPNETVNESxxx


OL-14565-01


-OPNETVnesxxx

Where xxx is AdapterServer, BootstrapService, and so on.

Step 12 Exit the Windows Registry Editor.

At this point, Virtual Network Data Server is completely removed from your system. If you also want to remove the Data Storage Server, go to the “Uninstalling the Data Storage Server” section on page 6-11.

Removing Prior Cisco VNDS Release After Software Update (Windows)

Perform this procedure if you want to remove Cisco VNDS 2.0.2 (Cisco VNDS 4.5) after you have installed Cisco VNDS 2.1 (Cisco VNDS 6.0) and migrated your product configuration.

If you want to remove Cisco VNDS 2.0.2 (Cisco VNDS 4.5) completely from a computer that has not been updated to the current release, refer to the Installation Guide for Cisco Virtual Network Data Server 2.0.2.

Caution Do not run the Windows uninstaller for a previous Cisco VNDS release after you have updated to the current software release. Doing so may impact the current release.

Removing a Prior Cisco VNDS Release After Update

Step 1 Delete the Cisco VNDS 4.5 install directory. Typical default install directory:


Step 2 Delete the following Program Group shortcuts from the Program Group menu for the appropriate Cisco Network Analysis product (Cisco Configuration Assurance Solution, Cisco Network Planning Solution, etc.):

• Virtual Network Data Server

• Open Virtual Network Data Server File Log Viewer

Example Program Group menus for Cisco Network Analysis products:

Chapter 6 Uninstalling Cisco Virtual Network Data Server Uninstalling Cisco VNDS (Linux)


OL-14565-01

C:\Documents and Settings\All Users\Start Menu\Programs\Cisco Configuration Assurance Solution 2.0.2

C:\Documents and Settings\All Users\Start Menu\Programs\Cisco Network Planning Solution 2.0.2 - SP

Step 3 If the Program Group menu for the appropriate Cisco Network Analysis product is now empty, delete the menu.


Step 4 In the Windows Registry Editor, find and select the registry key for the software being removed. Example registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\OPNET Technologies\Cisco Virtual Network Data Server 2.0\OPNET VNE Server 4.0.2.

Step 5 Select Delete from the menu to delete the entry.

Step 6 Remove the uninstaller entry in the Registry at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

Example entry name:

Cisco Virtual Network Data Server 2.0 Virtual Network Data Server

Step 7 Exit the Windows Registry Editor.

Uninstalling Cisco VNDS (Linux)Perform the following procedure to remove the Cisco VNDS software from your Linux computer.

Step 1 Shut down the Cisco VNDS software by doing the “Shutting Down Cisco VNDS Using the Command Line (Linux)” procedure on page 4-31.

Step 2 Log into the Cisco VNDS host as root or switch users to root. Use the su - <user> command when switching users. For example:

su - root


OL-14565-01

Chapter 6 Uninstalling Cisco Virtual Network Data Server Uninstalling a License Server

Step 3 Remove the Cisco VNDS processes by entering the following command:

./vnes.sh -c remove ALL

Step 4 Delete the Cisco VNDS installation directory:

a. Change directories to go up one level.


rm -rf <vnds_install_dir>

where <vnds_install_dir> is the full path of the Cisco VNDS installation directory.

Step 5 At this point, the following items remain:

• Cisco VNDS temporary directory

• Cisco VNDS archive directory

• Jre directory

If you want to completely remove all traces of Cisco VNDS 6.0 from the host, remove these directories using the rm -rf command.

Uninstalling a License ServerThis section describes how to uninstall a license server from the Cisco VNDS host.

Note If you installed a local license server with Cisco VNDS 2.1 (Cisco VNDS 4.5), refer to the Installation Guide for Cisco Virtual Network Data Server 2.1 for instructions on removing it.

If you installed a local license server with Cisco VNDS 2.1 (Cisco VNDS 6.0), use one of the following procedures to remove it.

• Uninstalling a License Server (Windows), page 6-10

• Uninstalling a License Server (Linux), page 6-11

Chapter 6 Uninstalling Cisco Virtual Network Data Server Uninstalling a License Server


OL-14565-01

Uninstalling a License Server (Windows)

Caution Do not uninstall the license server until another license server can be set up elsewhere. You must deregister licenses and move them to the new license server then redirect all impacted solution components to the new license server before you uninstall the old license server.

Step 1 Deregister all active licenses for the license server. Use the “Deregistering a License” procedure on page 5-7.

Step 2 Open the Windows Control Panel from the Start menu:

Start > Settings > Control Panel

Step 3 In the Windows Control Panel, double-click Add/Remove Programs.

Step 4 Scroll down the list of installed programs, select the entry for OPNET License Server 14.0, and click Remove.

Step 5 (Optional) Remove the license directory (for example: C:\OPNET_license dir).


Step 6 (Optional) Verify that the registry key has been removed. In the Windows Registry Editor, find and select the registry key for the software being removed. Example registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\OPNET Technologies\OPNET License Server 12.0\12.0.A

If the entry exists, select Delete from the menu to remove it.


OL-14565-01

Chapter 6 Uninstalling Cisco Virtual Network Data Server Uninstalling the Data Storage Server

Uninstalling a License Server (Linux)

Caution Do not uninstall the license server until another license server can be set up elsewhere. You must deregister licenses and move them to the new license server then redirect all impacted solution components to the new license server before you uninstall the old license server.

Step 1 Deregister all active licenses for the license server.

Step 2 Open a command window and use the cd command to set the working directory to the license server installation directory (for example, /usr/bin/OPNET/12.0.A/).

Step 3 Enter the following command to delete the contents of the license server installation directory:

rm -rf *

Step 4 Remove the startup folder by entering the following command:

rm /etc/rc3.d/S99opnet_lic_server

Step 5 (Optional) Remove the license directory (/opt/OPNET_license).

Uninstalling the Data Storage ServerUse one of these procedures to completely remove the Data Storage Server from a host computer system.

• Uninstalling the Data Storage Server (Windows), page 6-12

• Uninstalling the Data Storage Server (Linux), page 6-12



OL-14565-01

Uninstalling the Data Storage Server (Windows)

Caution Perform this procedure only if you are permanently removing Cisco VNDS from a system AND want to remove the PostgreSQL database contents as well as the product installation.


Step 2 Remove the database program:

a. Open the Windows Control Panel from the Start menu: Start > Settings > Control Panel.

b. In the Windows Control Panel, double-click Add/Remove Programs.

c. Scroll down the list of installed programs, select the entry for PostgreSQL 8.2, and click Remove.

d. Close the Add/Remove Programs window.

Step 3 Delete the Windows user account named dssowner.

If Windows does not automatically remove the account directory (C:\Documents and Settings\dssowner), delete it manually.

Step 4 Delete the Data Storage Server installation directory. The default location of the DSS directory is C:\Cisco\DSS.

Uninstalling the Data Storage Server (Linux)

Caution Perform this procedure only if you are permanently removing Cisco VNDS from a system AND want to remove the PostgreSQL database contents as well as the product installation.

Step 1 Login as root or switch users to root. Use the su - root command when switching users.

Step 2 Change directories to /var/lib/dss/installers/postgres-8.2.3.



OL-14565-01


./postgres-installer.sh /rootdir <postgres_data_dir_root> /remove_data /remove_os_user /action remove

where <postgres_data_dir_root> is the path to the PostgreSQL data directory (for example: /var/lib).

Step 4 (Optional) Remove the postgres installers by entering the following command:

rm -rf /var/lib/dss



OL-14565-01

A-1Installation Guide for Cisco Virtual Network Data Server

OL-14565-01

A P P E N D I X AKnown Issues

We highly recommend that you check, after installation and on a regular basis, for software updates and maintenance information of any software, documentation, model, or other components on http://www.cisco.com/techsupport.

You can search for additional online information regarding known product issues and workarounds on the Cisco Solutions Quick Support page (http://www.opnet.com/support/cisco_qsp.html).

http://www.opnet.com/support/cisco_qsp.html)

http://www.cisco.com/techsupport

Appendix A Known Issues

A-2Installation Guide for Cisco Virtual Network Data Server

OL-14565-01

IN-1Installation Guide for Cisco Virtual Network Data Server

OL-14565-01

I N D E X

A

Add License operation

workflow 5-3

C

Collecting Oracle Database Access Information 3-33, 4-33

D

Database Net Service Name

locating in tnsnames.ora 3-45, 4-45

Data Storage Server

verifying configuration (Linux) 4-27

verifying configuration (Windows) 3-28

Deregister License operation

Browser method 5-14, 5-15

Express method 5-12

workflow 5-7

F

Floating license mode

local ("serve licenses from this computer") 1-6

remote ("serve licenses from remote computer") 1-6

I

installation workflows for Linux 4-2

installation workflows for Windows 3-2

installing Virtual Network Data Server 3-16, 4-15

L

license

deregister (workflow) 5-7

License Manager

"white page" icon in 5-13

using 5-2

License Server

Refresh Server Information operation 5-13

licensing

Index


OL-14565-01

Add License operation (workflow) 5-3

deregister

Browser method 5-14

Express method 5-12

example scenarios 1-8

local vs. remote 1-6

refreshing a license 5-7

troubleshooting licensing operations 5-16

upgrade authorization, obtaining 5-5

upgrading from Restricted to Unrestricted (workflow) 5-4

username/password, obtaining 5-3

O

Oracle

supported versions 2-4

Oracle, installing (Linux)

configuring the Oracle database 4-38

database, worksheet for database access 4-34

database parameters, modifying 4-41

modifying database parameters 4-42

verifying 4-29, 4-30, 4-43

Oracle, installing (Windows)

configuring the Oracle database 3-39

database, worksheet for database access 3-34

database parameters, modifying 3-42

modifying Database parameters 3-42

verifying 3-30, 3-43

P

password, obtaining 5-3

T

technical assistance

for licensing operations 5-16

tnsnames.ora 3-45, 4-45

U

Upgrade License operation

authorization, obtaining 5-5

workflow 5-4

username, obtaining 5-3

V

Virtual Network Data Server

software version 3-1, 4-1

VNDS, installing (Linux)

initial VNDS installation 4-2

update installation (from previous VNDS version) 4-3, 4-4

workflows, overview 4-2

VNDS, installing (Windows)


OL-14565-01

Index

initial VNDS installation 3-3

upgrade installation (from previous VNDS version) 3-4

workflows, overview 3-3

W

Windows system configuration 2-3

workflow

VNDS first-time installation 3-3

VNDS update installation (Oracle) 3-4

VNDS update installation (standard) 3-4

Index


OL-14565-01