Guest

Cisco Prime Network

Cisco Prime Network Quick Start Guide, 4.0

  • Viewing Options

  • PDF (846.5 KB)
  • Feedback
Cisco Prime Network 4.0 Quick Start Guide

Table Of Contents

Table of Contents

Preface

Quick Start Guide Scope

Examples of Deployments Within the Guide's Scope

Related Documentation

Obtaining Documentation and Submitting a Service Request

Installation Requirements

Gateway and Unit Requirements

Example Hardware for One-Server Setup

Example Hardware for Two-Server Setup

Client Requirements

Disk Space and Database Storage Requirements

Ports Requirement

Preparing for the Installation

Installing Prime Network

Install the Gateway

Verify the Gateway Installation

Install the Client

Install the Unit

Verify the Unit Installation

Next Steps

Get a Valid Cisco Prime Network License

Set Up AVMs and VNEs

To Create AVMs

To Add VNEs

Set Up Users and Security

Add Scopes

Add Users

Configure Your Devices for Effective Cisco Prime Network Management

Start Using the Prime Network Vision GUI To Monitor the Network

Log Into Cisco Prime Network Vision

Quick Overview of the Cisco Prime Network Vision GUI

Create a Map for Network Visualization

Fault Management Basics

Appendix A: Device Information Form


Cisco Prime Network 4.0 Quick Start Guide

Released: July 2013
Part No.: OL-29342-01

Table of Contents


1 Preface

The purpose of this Quick Start Guide is to get you up and running with Prime Network 4.0, to the point where you can create a map to visualize your network and you can take advantage of Prime Network's many capabilities to monitor and manage your network elements and services. This guide will lead you through the planning, installation, and post-installation tasks required to get to this point.

The Quick Start Guide does not cover the entire spectrum of installation options. It is intended for small-medium deployments of Prime Network using an embedded database, with no high availability. Details of the assumptions upon which this guide is based are provided in Quick Start Guide Scope, and some examples are provided in Examples of Deployments Within the Guide's Scope. Before proceeding with the installation, perform the pre-installation tasks provided in Preparing for the Installation.


Note This Quick Start Guide does not replace other available Cisco Prime Network documentation, as it contains the minimum subset of information required to get started. For detailed information on any of the subjects mentioned in this guide, please see the Cisco Prime Network 4.0 guides listed in Cisco Prime Network 4.0 Documentation Overview.


Quick Start Guide Scope

This section describes the assumptions upon which the information in this Quick Start Guide is based. If your Prime Network deployment differs from what is described in these assumptions, please contact your Cisco account representative for assistance with planning and installation of Prime Network.


Note The Quick Start Guide is not intended for high scale environments, either at the network element level or the cross-network size. Details about hardware requirements for high scale setups, including database and memory sizing calculations, can be found in the Capacity Planning Guide which can be obtained from your Cisco account representative.


This guide assumes that:

This is a new Prime Network installation, not an upgrade from a previous version.

Prime Network is installed as a standalone application , not as a part of a Prime suite.

Prime Network will be used to manage up to 100 network elements, i.e., a small-medium deployment of Prime Network. See Examples of Deployments Within the Guide's Scope for examples.

The network can be managed by a maximum of one Prime Network gateway and one unit, either co-located on one server or on separate servers.

The Prime Network embedded database (Oracle 11g R2) will be used, not an external database.

Prime Network will run in a production environment with a low rate of database operations:

0-5 actionable events per second. Actionable events are events that can be parsed by Prime Network and can therefore participate in correlation.

Up to 50 incoming events per second

Up to 300 change and configuration management operations persisted in the database.

The default history size will be retained, i.e., 14 days for events. If a longer history period is required, please consult your Cisco account representative.

Telnet and SNMP will be used for device modeling and discovery when adding VNEs to the system, not SSH.

The reader has experience in the Unix environment.

The Quick Start Guide does not cover the following:

Integration

Customization

Package download

Advanced configuration (e.g., polling)

High availability

LDAP

External or remote database

Examples of Deployments Within the Guide's Scope

Following are some examples of Prime Network network setups that fit within the Quick Start Guide scope. If your network setup is significantly larger than the examples below, please refer to the Cisco Prime Network 4.0 Installation Guide or contact your Cisco account representative for assistance with planning and installation of Prime Network.

Example 1

Deployment type: Carrier E Aggregation

Number of Managed Elements: 35 aggregation routers

Possible Device Types: ASR 9000, 7600

Example 2

Deployment type: MPLS Core

Number of Managed Elements: 75, of which 50 core routers (P, PE) and 25 aggregation routers

Possible Device Types for Core: CRS-1, 12k, 76xx, 72xx, 65xx

Possible Device Types for Aggregation: 76xx, 65xx

Example 3

Deployment type: Basic element management functionality, no network level services or topology

Number of Managed Elements: 100 small/medium access routers

Possible Device Types: ME3400, 4900, 3750, generic VNE

Example 4

Deployment type: IP RAN

Number of Managed Elements: 100, of which 5 aggregation devices, 30 cell site devices, 65 layer 2 switches

Possible Device Types for Aggregation: 7600

Possible Device Types for Cell Sites: MWR-2941, MWR2941-DC

Possible Layer 2 Switches: 3400, 3400 ME

Example 5

Deployment type: Carrier E

Number of Managed Elements: 100, of which 95 UPE devices, 5 NPE devices

Possible Device Types for UPE: 3400, 3750

Possible Device Types for NPE: 76xx, ASR 9000

Related Documentation

For list of available Prime Network documents, see the Cisco Prime Network 4.0 Documentation Overview.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, 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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

2 Installation Requirements

This section provides prerequisites and recommendations for the hardware and software you need to support your Prime Network deployment. These recommendations are based on the assumptions and target setup for this Quick Start Guide, as described in Quick Start Guide Scope and Examples of Deployments Within the Guide's Scope. If your network setup is not covered by this guide, please see "Installation Requirements" in the Cisco Prime Network 4.0 Installation Guide.

The recommended hardware options for the target setup are either:

Gateway and unit co-located on one server (one-server setup). This option requires the installation of the gateway software only, as the gateway acts as both gateway and unit.

or

Gateway installed on one server, unit installed on a separate server (two-server setup).

Gateway and Unit Requirements

This section provides the prerequisites for the hardware and software required for the Prime Network gateway and unit in the Quick Start Guide target setups. See Example Hardware for One-Server Setup and Example Hardware for Two-Server Setup, for server recommendations.

The prerequisites are relevant for an embedded database installation, where the Oracle database is installed on the gateway during Prime Network installation and is fully integrated with Prime Network. The gateway and unit is only supported on Linux operating systems.


Note The hardware requirements are provided under the assumption and recommendation that Prime Network 4.0 does not share the hardware with additional applications.


Table 1 Gateway and Unit Hardware and Software Prerequisites 

Item
Specifications

Processor

Intel Xeon 5550

Software

Red Hat Enterprise Linux Server Release 5.5, 5.6, 5.7 and 5.8 64-bit Server Edition (with or without VMware ESX version 5), English language).

For installation using the wizard, the following software must also be installed :

Xclient on the local machine from where you plan to launch the wizard.

Java Runtime Environment 1.6 or later on the server where you plan to install Prime Network. This is required to invoke the wizard.

Database Requirements

The following packages, or later versions of them, are required for the Oracle 11g R2 database:

binutils-2.17.50.0.6

compat-libstdc++-33-3.2.3

elfutils-libelf-0.125

elfutils-libelf-devel-0.125

gcc-4.1.2

gcc-c++-4.1.2

glibc-2.5-24

glibc-common-2.5

glibc-devel-2.5

glibc-headers-2.5

ksh-20060214

libaio-0.3.106

libaio-devel-0.3.106

libgcc-4.1.2

libgomp-4.1.2

libstdc++-4.1.2

libstdc++-devel-4.1.2

make-3.81

sysstat-7.0.2

Memory (RAM)

Gateway: 32 GB RAM (this covers both gateway and database memory requirements)

Unit: 32 GB RAM

Gateway and unit on the same server: 64 GB RAM

Memory-to-CPU ratio:

Gateway—At least 4 threads. Each Intel Xeon 5550 has 8 threads.

Unit (VNE)—At least 4 threads and up to 32 GB RAM (a ratio of 32 GB to 4 threads).

Swap space

Twice the size of the physical memory, up to 16 GB

Required Configuration

Domain Name System (DNS) must be enabled on the Prime Network gateway, unit, and client.

For time zone, use GMT (with 0 offset) on the Prime Network servers because Prime Network stores events in the database in Greenwich Mean Time (GMT) format. The Prime Network client converts events to the time zone that is configured on the client workstation.


Example Hardware for One-Server Setup

For a one-server setup where the gateway, unit, and database are co-located (with no LDOM partitioning), an example is:

Cisco UCS C210 M1 General-Purpose Rack-Mount Server with:

2 Xeon 5550 processors

Red Hat Enterprise Linux Server Release 5.3 64-bit

64 GB RAM

No VMWare

Example Hardware for Two-Server Setup

For a two-server setup, you could choose to use one server with two virtual partitions, or two separate machines, as in the examples below:

Two Cisco UCS C210 M1 General-Purpose Rack-Mount servers (one for the gateway and one for the unit) with:

1 Xeon 5550 processor

Red Hat Enterprise Linux Server Release 5.8 64-bit

32 GB RAM

No VMWare

Cisco UCS C240 M3 High-Density Rack Server which will run two vmware instances similar to:

Xeon E5-2690 Processor

32GB RAM

Red Hat Enterprise Linux Server Release 5.8 64-bit

Client Requirements

Table 2 Cisco Prime Network Client Minimum Installation Prerequisites 

Item
Specifications
Minimum Hardware Requirements

IBM PC or PC-compatible workstation

Pentium IV, 2.66-GHz or later

1 GB RAM

2 GB of free disk space

512 MB of free nonvirtual memory per running instance

Screen

Minimum screen resolution of 1024 x 768 pixels

True color (32-bit) setting

The minimum browser dimensions that Prime Network supports to successfully view the network discovery tool, is 900 x 600.

Minimum Software Requirements

Operating system

Windows 2000, Windows XP, Windows Vista, or Windows 7

Citrix XenApp 5 with the Citrix Hotfix patch CTX120923, available at http://support.citrix.com/article/CTX120923

Note The Citrix Hotfix patch requires an upgraded Citrix License Server (version 11.6.1). A single Citrix server supports multiple Citrix clients, each of which can run Prime Network clients. If you are using Prime Network with Citrix and cannot establish an SSL connection see Cisco Prime Network 4.0 Installation Guide.

Java Runtime Environment (JRE)

For installing the Prime Network client using the Java Web Start technology, use:

· 32-bit JRE for a 32-bit operating system

· 64-bit JRE for a 64-bit operating system

Internet Connection

Requirement

1.5 MB/s bandwidth (to download)

Supported browsers

Microsoft Internet Explorer 8 on Windows 7

Microsoft Internet Explorer 9 supported in IE8 Capability Mode

Firefox 7.0 on Windows XP

Google Chrome 12, 13, and 14

Apple Safari 5.1

Prime Network Operations Report1 is supported on the browsers listed below.

For Windows 7:

Internet Explorer 9 with 32 bit JRE

Mozilla Firefox 17 with 32 bit JRE

Chrome 22 with 64 bit JRE

For Windows XP:

Chrome 22 with 32 bit JRE

Mozilla Firefox 17 with 32 bit JRE

Internet Explorer 9 with 64 bit JRE

Network Discovery is supported on the following browsers.

IE 8/92

Firefox3

Google Chrome

1 Operation Report is available only if you have a valid license. Please see Cisco Prime Network 4.0 Installation Guide for details on Installing Operations Report.

2 Network Discovery might not display properly and Discovery Profile page might take longer than usual to load.

3 VCB, Network Discovery, and CCM might not be able to connect in Firefox if the gateway IP address is a raw IPv6 address..


Disk Space and Database Storage Requirements

Before installing Cisco Prime Network, please verify that the disk space and storage requirements for the installation and for the database are fulfilled:

Table 3 Minimum Disk Space Required for Cisco Prime Network Installation 

Directory
Minimum Required Disk Space

/ (root)

1 GB

Cisco Prime Network installation directory (default is /export/home/pn user)

5 GB

/tmp

1 GB

Oracle user home directory. The default is /export/home/oracle

6 GB


Table 4 Oracle Database Storage Requirements1

Item
Minimum Required Disk Space
Location Recommendations

Data files

92 GB

Internal or external disk.

Redo logs

6 GB

Redo log files should not reside on the same disk as the data files.

On a Linux server, use ext3 and mount with the default mount options.

Archive logs

110 GB

Archive log files should not reside on the same disk as the data files.

Data files backup

138 GB

Data files backup should not reside on the same disk as the data files.

1 These database storage sizes are for up to 5 actionable events per second profile.



Note The system administrator must back up the archive logs to tape daily and must transfer the data files backups to external storage.


Ports Requirement

The following ports are used by Prime Network and must be open prior to installation or the installation process will fail:

Table 5 Ports Used by Prime Network1  

Port
Protocol
Direction
Usage

21 and 22

TCP

Gateway > Remote FTP/SFTP Server

Exporting CCM configurations to remote FTP server

21 and 22

TCP

Gateway > Network Elements

Transferring images to Network Elements

23

TCP

Unit > Network Elements

Telnet collector

25

TCP

Gateway > SMTP Server

SMTP port that is optional for an external database, but recommended for an embedded database

25

TCP

Database > SMTP server

SMTP port that is recommended for an embedded database


Note If you do not want to receive e-mail notifications, you do not have to configure the SMTP server. If you decide to configure the SMTP server, keep port 25 open on both the gateway and the database server (if they are different).


69

UDP

Network Elements > Gateway

Transferring images to and from Network Elements

69

UDP

Network Elements > Unit

Default TFTP server on Prime Network units

AVM 83, which is the TFTP server used by Change and Configuration Management


Note To use AVM 83, you must disable the default TFTP server such that the port is free and available. Otherwise, Change and Configuration Management operations will fail.


123

UDP

Unit > Gateway

NTP synchronization between gateway and units

123

UDP

Gateway > NTP Server 1

NTP synchronization for gateway

161

1161

UDP, Linux only

Unit > Network Elements

For Units with VNEs, these ports are used for SNMP polling by the VNEs.

For Units with AVM100, you need these ports only if you use SNMP V3 for engine discovery.

161

1161

UDP, Linux only

Network Elements > Unit

Note For 161 (UDP), if AVM100 resides on the gateway, the Network Elements sends to the Gateway.

For Units with AVM100, if you use SNMP V3

162

1162

UDP, Linux only

Network Elements > Unit

Note For 162 (UDP), if AVM100 resides on the gateway, the Network Elements sends to the Gateway.

For Units with AVM100, these ports are used for traps.

162

1162

UDP, Linux only

Unit > Network Elements

SNMP V3 inform replies

162

TCP/UDP

Gateway > Northbound NMS

EPM MIB notifications

514

UDP

Network Elements > Unit

Note If AVM100 resides on the gateway, the Network Elements sends to the Gateway.

Syslogs


Note If port 514 is occupied when you install Cisco Prime Network, you are prompted to make the port available. However, you are given the option to continue with port 514 occupied, and the installation completes successfully.


1101

TCP

Unit > Gateway

Prime Network user exclusive bidirectional hardened SSH connection for system administration operations

1101

TCP

Gateway > Unit

1102

TCP

Gateway > Database Server

Prime Network user exclusive bidirectional hardened SSH connection for system administration operations.


Note This SSH port is mandatory only for an embedded database.


1102

TCP

Database Server > Gateway

Prime Network user exclusive bidirectional hardened SSH connection for system administration operations.


Note This SSH port is mandatory only for an embedded database.


1311

TCP

Client > Gateway

Prime Network monitoring system (SSL over HTTP)

1521

TCP

Client > Database Server

Prime Network Events database access

1521

TCP

Unit > Database Server

Event persistency

1521

TCP

Gateway > Database Server

Gateway persistency services

42605

TCP

WEB UI Server/Tomcat > Compliance Audit Engine

Compliance Audit Engine Connection Port

6080

TCP

Client > Gateway

HTTP for web access and web-start. Used to download the client from the gateway server, client updates (jar files), and online help files.

6081

TCP

Client > Gateway

HTTP over SSL for web access and web services such as Cisco Prime Network Operations Reports

6081

TCP

Unit > Gateway

HTTP over SSL for unit configuration. Key exchange during unit configuration.

8000

TCP

Unit > Unit or Gateway > Gateway

Local Management over HTTP

8009

TCP

Unit > Unit or Gateway > Gateway

Tomcat server AJP connector port, used for Change and Configuration Management

8011

TCP

Unit > Unit or Gateway > Gateway

Local Management over HTTP

8043

HTTPS

Client > Gateway

Secure HTTP port for Change and Configuration Management web clients

8080

HTTP

Client > Gateway

HTTP port for Change and Configuration Management web clients

Note By default, this port is disabled and the secure 8043 HTTP port is enabled for Change and Configuration Management client. To use 8080 for Change and Configuration Management client, you must enable it manually. For more information, see Cisco Prime Network 4.0 User Guide.

8099

TCP

Unit > Gateway

Local Management over HTTP

9002

TCP

Internal gateway

Prime Network BQL - a local port only

9003

SSL

Client > Gateway

Prime Network BQL over SSL

9005

TCP

Client > Gateway

Web GUI server port, used for Change and Configuration Management

9009

TCP

Client > Gateway

Web GUI AJP connector port, used for Change and Configuration Management

9080

TCP

Client > Gateway

Web GUI HTTP connector port, used for Change and Configuration Management

9443

TCP

Client > Web GUI server

Web GUI HTTPS connector port, used for Change and Configuration Management

9390

TCP

Gateway > Unit

Transport internal processes.

9490

TCP

Unit > Gateway

Secured SSL transport

9770 and 9771

TCP

Client > Gateway

Prime Network Vision, Administration, Events

9875

TCP

Client > Gateway

Spring JMX console port, used for Change and Configuration Management

1 If any of the ports (except for port 514) are unavailable, the installation fails.


3 Preparing for the Installation

To make Prime Network installation and setup as quick and seamless as possible, you need to plan your deployment in advance and perform the following pre-installation tasks:

Read the Cisco Prime Network 4.0 Release Notes.

Verify that the devices you intend to manage with Prime Network are supported, using the Cisco Prime Network Supported Cisco VNEs.

Review the installation requirements described in Installation Requirements.

Open the required ports. See Ports Requirement

4 Installing Prime Network

This section provides step-by-step instructions for installing the Prime Network gateway, unit, and client software:

Install the Gateway

Install the Client

Install the Unit


Note If you have a one-server setup, you need to install the gateway only. There is no need to install the unit because the gateway acts as both gateway and unit.


Install the Gateway

Installation of the gateway consists of two parts:

1. Installation of the gateway software on the designated server. This part should take between 10 and 20 minutes.

2. Configuring the gateway which takes up to an hour.

To install and configure the Cisco Prime Network gateway:


Step 1 From one of the installation DVDs, launch the installer.bin file using the X client.

Step 2 Enter the following details:

a. Gateway hostname or IP address.

b. Gateway username and password.

The install wizard launches and the Introduction window is displayed.

Figure 1 Prime Network Install Wizard

Step 3 Click Next. The Installation Setup window is displayed.

Step 4 In the Installation Setup window, do the following:

a. Enter the name of the user account (pn user) for the Cisco Prime Network application.

b. Select the Prime Network server type as Gateway.

Step 5 Click Next. The NTP Configuration window is displayed.

Step 6 Select Yes if the NTP is configured on the servers.

Step 7 Click Next. The Installation Directory window is displayed.


Note The default installation location is /export/home/pn user, where pn user is the operating system user account (username in Step 4) for the Prime Network application.


Step 8 To change the default installation location, click Choose... and choose the preferred installation directory.

Step 9 After choosing the required directory, click OK, or click Cancel to return to the default installation location.

Step 10 Click Next to accept the installation directory location.

Step 11 In the Gateway Installation window, do the following:

a. Select the standalone installation mode to install a standalone gateway.

b. Enter the gateway IP address for communication with the units, as shown in Figure 2.

Figure 2 Gateway Installation Window

c. Enter the Prime Network application password and re-enter the password to confirm.

d. Select Embedded Database and click Next. The Embedded Database window is displayed. The following table lists the fields and values to enter.

Table 6 Embedded Database Fields 

Prompt
Enter..
Notes

Database Server

Server hostname/IP address.

 

Install database on remote server

No

This Quick Start Guide assumes that the database will be installed locally on the gateway server. If you decide to install the database on a remote server, you need to specify the IP address of the remote server.

Server root password

password

 

Database OS User

username

Unix user of the database. The default is oracle.

Database Zip Files Path

Path to the directory containing the zip files

Location where the database zip files are located.

Database OS user Home Directory

Path to the Oracle user home directory. The default is /export/home/oracle.

The directory must have a minimum of 6 GB of disk space for oracle binaries.

Data files path

Path to the directory containing the datafiles.

The locations of the database datafiles.

Redo Logs path

Path to the redo logs.

The locations of the redo logs, archive and backup files should not reside on the same disk as the data files.

Use ext3 and mount with the default mount options.

Would you like to enable Database auto-backup?

Yes/No

The default is yes. If you entered no at this prompt, you can enable automatic

backups later with the ./emdbctl --enable_backup command.

See the Cisco Prime Network 4.0 Administrator Guide for information on the emdbctl utility.

Select a database profile (RAM sizes are the minimal requirement for the database)

The number corresponding to the estimated profile.

Select from the available list based on the RAM size available or desired actionable events per second. For more information on these database profile, see Cisco Prime Network 4.0 Installation Guide.

Archive Logs path

Path to the directory containing the archive logs.

The locations of the redo logs, archive and backup files should not reside on the same disk as the data files.

Backup files path

Path to the directory containing the backup files.

This directory must have three times the amount of free disk space as the database size. The locations of the redo logs, archive and backup files should not reside on the same disk as the data files.

SMTP Server IP Address/Hostname

company-email-server-address

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

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

Email for Receiving Alerts

username@company-name.com

E-mail address to receive notification when database errors occur.


e. Click Next. The Pre-Installation Summary window is displayed.

Step 12 Click Install to start the installation, or click Previous to modify values on any of the previous windows.

Step 13 When the installation is complete, click Finish.

The following logs are available:

Installation logs at /var/adm/cisco/prime-network/logs/.

Embedded database configuration logs at NETWORKHOME/local/scripts/embedded_oracle.

Configuration logs at NETWORKHOME/Main/logs.

Step 14 A prompt appears to start the gateway. Click Yes to start the gateway or No to start later.


Note If the gateway is started for the first time, launching the gateway will take around 15 minutes.



Verify the Gateway Installation

If you did not start the gateway at the end of the installation process, use this procedure to launch the gateway and check the status of all processes.


Step 1 Log in to the Prime Network gateway machine OS shell as the super user.

su - root
 
   

Step 2 Enter the super user password.

enter root password: XXXX
 
   

Step 3 Launch the gateway by entering the following command:

su - pn user
networkctl start
 
   

The gateway might take a while to load.

Step 4 If the gateway is up, the output shows the status of each process and the number of exceptions found in the total number of log file lines for that process. For example, [OK 0/xx] means 0 exceptions found in the xx log file lines that were checked.

The output shows the following gateway processes are up and running:

AVM 100—Prime Network Event Collector (AEC) process.

AVM 0—High availability/switch process.

AVM 11—The database connection. When the database operates normally, AVM 11 is up and running. If there are any database problems, AVM 11 is down.

AVM 25—Event persistence.

AVM 41—Compliance Engine Status

AVM 77—Prime Network web server status.

AVM 83—Internal use; used as a TFTP server by Change and Configuration Management.

AVM 84—Report management.

AVM 99—Management process.

Webserver daemon—Client connection process.

Secured connectivity daemon.


Note Check the log files for each AVM if there are any problems. The log files are located under NETWORKHOME/ main/logs.



Install the Client

The client installation wizard guides you step-by-step through the process for installing the Prime Network client which includes Prime Network Administration, Vision, and Events clients.


Step 1 Use either of the following options to begin the client installation:

Insert "Disk 1: New Install" in your DVD drive. The client installation wizard launches automatically and the Welcome window is displayed.

If the client installation wizard does not launch automatically, browse to the DVD directory and launch the client CiscoPrimeNetwork.exe.

Open a web browser and download the client installation executable from http://gateway-IP-address:6080/ana/services/install/index.html, where gateway-IP-address is the IP address of the newly installed gateway. After the download is complete, launch the CiscoPrimeNetwork.exe. The client installation wizard launches and the Welcome window is displayed.


Note The web browser option is available only if the gateway is up.


Step 2 Click Next. The Destination Location window is displayed. The default installation location is C:\Cisco Systems\Prime_Network\.


Note For Windows 7 only: We recommend that you do not install the Prime Network GUI clients in the Program Files folder. Only Windows Administrators can run the GUI clients if they are installed in that folder.


Step 3 To change the default installation location, click Browse and choose the preferred installation directory.

Step 4 After choosing the required directory, click OK , or click Cancel to return to the default installation location.

Step 5 Click Next to accept the installation directory location. The Select Components window is displayed.

Step 6 In the Select Components window, do the following:

a. Make sure that the JAVA Runtime check box is checked.

b. Select all the available installation options (Prime Network Vision, Prime Network Events, Prime Network Administration).


Note The Activation and Workflow features are only supported for upgrades. New installations of Prime Network will not include these features. For upgrade information, see Cisco Prime Network 4.0 Installation Guide.


c. Click Next.

Step 7 In the Select Program Manager Group window, click Next to accept the default program manager group. If you want to change the default program manager group, enter your preference and then click Next.


Note Cisco Prime Network is the default Program Manager group. Cisco Prime Network overwrites any existing icons. You should add a version number to the Program Manager group; for example, Cisco Prime Network 4.0.


Step 8 In the Start Installation window, click Next to start the installation. The Installing window is displayed.

Step 9 When the installation is complete, choose the options displayed in the final installation window, according to your preference:

Create "Quick Launch" icons—Create a Quick Launch icon for Prime Network Vision and Prime Network Administration on the Quick Launch toolbar.

Launch Prime Network Vision—Immediately launch Prime Network Vision.

Step 10 Click Finish.


After the client installation is finished, use Cisco Prime Network Administration to complete the deployment of Cisco Prime Network. For information, see the Cisco Prime Network 4.0 Administrator Guide.

Install the Unit

This section tells you how to install the Prime Network unit using the install wizard. To install the unit using the wizard:


Step 1 Launch the installer (install.bin) using the X client and enter the following details:

a. Gateway hostname or IP address.

b. Gateway username and password.

The install wizard launches and the Introduction window is displayed.

Step 2 Click Next. The Installation Setup window is displayed.

Step 3 In the Installation Setup window, do the following:

a. Enter the name of the user account (pn user) for the Cisco Prime Network application.


Note You must enter the same username that you used when you installed the gateway. (If the gateway and unit have different usernames, the unit will not start.)


b. Select the Prime Network server type as Unit.

Step 4 Click Next. The NTP Configuration window is displayed.

Step 5 Select Yes if the NTP is configured on the servers.

Step 6 Click Next. The Installation Directory window is displayed.

Step 7 To change the default installation location in the Installation Directory window, click Choose... and select the preferred installation directory.


Note The default installation location is /export/home/pn user, where pn user is the operating system user account (username in Step 3) for the Prime Network application.


Step 8 After choosing the required installation directory, click OK , or click Cancel to return to the default installation location.

Step 9 Click Next. The Unit Installation window is displayed, as shown in Figure 3.

Figure 3 Unit Installation Window

Step 10 Enter the fields in the Unit Installation window, as shown in Table 7.

Table 7 Unit Installation Fields

Field
Enter..
Notes

Gateway IP Address

IP address of the gateway

Please make sure that the gateway is up and running.

Unit IP Address

IP address of the unit

-

Prime Network Application Admin User

The username for the Prime Network administrator.

Prime Network internal admin user, username and password used for secure communication with the gateway.

Prime Network Application Admin Password

The password for the Prime Network administrator.

Select the unit's work mode

Select Active Unit or Standby Unit as required.

-

Unit Unique Name

Name of the unit.

-

Units's Protection Group

Enter the protection group for the unit.

-

Prime Network Main Schema Database IP address accessible from Prime Network Unit

IP address of the Prime Network main schema database.

This is required in case of incase of incompatible Gateway/Database interface types.

Prime Network EP Schema Database IP address accessible from Prime Network Unit

IP address of the Prime Network EP schema database.

-


After entering the information at the prompts, a connection is made to the gateway to retrieve SSH keys. If the SSH keys are not retrieved automatically within 60 seconds, the following message is displayed: "Connection to gateway-IP-address failed. 60 seconds timeout exceeded." To resolve this issue, verify that the unit can reach port 6081 on the gateway and then run network-conf again.


Note If more than one IP address is defined on the unit server, Prime Network automatically chooses the IP address of the network interface card (NIC) that acts as a default route to the gateway. If required, you can use the choose_nic.pl tool to change the NIC.


Step 11 Click Next. The system configuration might take some time. The Pre-installation summary appears.

Step 12 Click Install to start the Unit installation.

Step 13 When the installation is complete, click Finish.

Step 14 A prompt appears to start the unit. Click Yes to start the unit or No to start later.



When the unit is installed, the new unit is displayed in the Prime Network Administration navigation tree and content area. It is automatically registered in the registry and a transport uplink between the unit and the gateway is created. The gateway starts the unit automatically, if the unit is reachable.

The unit is displayed as Down at first but the status changes to Up after a few minutes.


Note Remote procedure call (RPC) services (such as Prime Network SSH and Local Management over HTTP must be enabled in the gateway so that the gateway and the unit can communicate.


Right-click on the unit and select Properties to view memory allocation information for the unit, and other unit properties.

Figure 4 Unit Properties Dialog


Verify the Unit Installation

Follow the steps below to verify that the unit was installed properly. If there are any problems, rerun the installation.


Step 1 Open a Telnet or SSH session to the Prime Network unit machine and login as the super user.

ssh <IP address of the machine>
su - root
 
   

Step 2 Enter the super user password.

enter root password: XXXX
 
   

Step 3 Change user as prime network user (pn user), using the following command:

su - pn user
 
   

Step 4 Check the status of all processes and daemons by entering the following command:

status
 
   

The output shows the status of each process and the number of exceptions found in the total number of log file lines for that process. For example, [OK 0/39] means 0 exceptions found in the 39 log file lines that were checked.

Step 5 In the ~/Main directory, confirm that:

a. The scheme subdirectory exists and contains the correct scheme files.

b. The scripts and UNIX subdirectories were created correctly.

c. The registry directory exists and contains the necessary files.

Step 6 Check that the golden source was configured correctly on the server:

a. Open the ~/Main/registry/avm99.xml file.

b. Confirm that the file contains an entry for the key parent, which is the value of the IP address of the gateway.

Step 7 Verify that the unit can access the gateway using SSH. On the Unit, run the following command:

ssh GW_IP 'echo $ANA_MODE'
 
   

Where:

GW_IP is the Gateway IP or the virtual IP if the Gateway is a cluster (RHCS) node

The output returned should be gateway.

Step 8 Verify that the gateway can access the unit using SSH. On the Gateway, run the following command:

ssh UNIT_IP 'echo $ANA_MODE'
 
   

Where:

UNIT_IP is the Unit IP

The output returned should be unit.


5 Next Steps

After you have installed Prime Network, you must perform the following tasks:

Get a Valid Cisco Prime Network License

Set Up AVMs and VNEs

Set Up Users and Security

Configure Your Devices for Effective Cisco Prime Network Management

Start Using the Prime Network Vision GUI To Monitor the Network

Get a Valid Cisco Prime Network License

You must activate a valid Prime Network license within 120 days of installation. Until you activate the license, you will be running an evaluation version of Prime Network, with full functionality. After 120 days, this evaluation version will expire and if Prime Network is closed, it will not restart.

Prime Network software must be registered via Cisco.com in order to obtain a license file (*.lic). The license file will be sent to you by e-mail and must be installed on the Prime Network gateway server.


Note The license file is bound to the server credentials that are provided during license generation. The license file will only be usable on that server only and cannot be ported from one server to another.


For any licensing issues, please contact your Cisco account representative or send an e-mail to ask-ana-licensing@cisco.com for assistance. For further details on different licensing and type of licensing installed, see Cisco Prime Network 4.0 Administrator Guide.

To obtain the license file:


Step 1 Go to the licensing web page at http://www.cisco.com/go/license and enter your Cisco.com user credentials to start the Product License Registration process. If you are not a registered Cisco.com user, create an account and log in.

Step 2 Enter the Product Authorization Key (PAK number) that appears at the bottom of the Software License Claim Certificate you received with your Prime Network package. The PAK number is a unique, automatically generated identification key that represents the specific software and hardware covered by the license. An example PAK number is ANA-3X-JAB-XXXXXX. Click Submit after entering the PAK number.

Step 3 Enter the hostname and host ID of the Prime Network gateway server.


Note If you do not know the host ID, log into the Prime Network gateway server and enter the command hostid.


Step 4 Fill in the rest of the requested information, including your e-mail address, and submit the request.

Your license file and user information will be sent within an hour to the e-mail address you specified. If you do not receive an e-mail within one hour, contact your Cisco account representative or send an e-mail to ask-ana-licensing@cisco.com for assistance.


Caution Do not edit the contents of the .lic file in any way. The contents of the file are signed and must remain intact.

Step 5 Copy the license file to the $FLEXNET_HOME/licenses directory in the Prime Network gateway server.

# cp licensefile.lic $FLEXNET_HOME/licenses
 
   

Step 6 Read and activate the license with the license manager.

# liccontrol reread

Note If you know that licenses are installed but they were not found when using the liccontrol command, contact your Cisco account representative. The license file may be corrupted.


Step 7 Apply the license to the Prime Network gateway process (which runs on AVM 11):

# networkctl -avm 11 restart
 
   

Step 8 Enter the following status command to verify that the license is loaded:

status
 
   

The output should include the following:

- Checking if license server is up and running                     [LOADED]

Set Up AVMs and VNEs

AVMs are Java processes (independent JVMs) with their own dedicated memory. AVMs are mostly used to provide the necessary distribution support platform for executing and monitoring multiple VNEs.

Each VNE is a virtual representation of a single network element. VNEs are distributed between the AVMs.

The distribution of VNEs to AVMs depends mainly on the VNE memory footprint. A single AVM may hold tens of smaller VNEs (U-PE, access, CEs) or fewer very large VNEs (Aggregation, PE, P).

Follow these general guidelines for AVMs and VNEs:

Allocate 1.5 GB per AVM.

Assign VNEs with similar device types to the same AVM. This will reduce the AVMs memory consumption.

You should have up to 13 AVMs with 1.5 GB each for your entire setup. (This guideline assumes your setup meets the assumptions and caveats described in Quick Start Guide Scope.)

Following are more specific guidelines for AVM-VNE distribution based on the Examples of Deployments Within the Guide's Scope for the Quick Start Guide setup:

Table 8 AVM-VNE Distribution Examples

Supported Deployment Option Example
Number and Type of Devices
AVM-VNE Distribution

Carrier E Aggregation

36 aggregation routers (Vikings and 7600 routers)

12 AVMs with 3 VNEs each

MPLS Core

50 core routers (CRS, GSR, 7600, 7200, 6500)

25 aggregation devices (7600, 6500)

5 AVMs with 10 core router devices each

7 AVMs with 4 aggregation devices each

Basic EMS

100 small/medium access routers (ME3400, 4900, 3750, generic VNEs)

2 AVMs with 50 VNEs each

If using generic VNEs: 10 AVMS, each with 10 VNEs

IP RAN

5 aggregation routers (7600)

30 cell site devices (MWR2941)

65 layer 2 switches (ME3400)

2 AVMs with 2 and 3 aggregation routers respectively

1 AVM with 30 cell site devices

2 AVMs with 30 and 35 switches

Carrier E

5 NPE devices (7600, Viking)

95 UPE switches (3400, 3750)

2 AVMs with 2 and 3 NPEs each

2 AVMs with 45 and 50 UPEs each


Use the following procedures to create AVMs and assign VNEs:

To Create AVMs

To Add VNEs

To Create AVMs

You can add AVMs to units or directly to a gateway (in a one-server setup). The AVM must have a unique ID between 101-999 (AVMs 1-100 are reserved by Cisco Prime Network). Every AVM requires a dedicated TCP port which is created using the following naming convention:

AVM-ID + 2000

For example, if you created AVM 711, it would use port 2711. The appropriate TCP port must be available or the AVM creation will fail.

Each AVM has its own log in NETWORKHOME/Main/logs.


Note Before you add AVMs, confirm that AVM 0, AVM 99, and AVM 100 are running on the gateway. For more information on the status of AVMs, see "Getting AVM Status and Property Information (Including Reserved AVMs)" in the Cisco Prime Network 4.0 Administrator Guide.


To create an AVM:


Step 1 In Prime Network Administration, expand the Prime Network Servers branch.

Step 2 Right-click the unit (or gateway) on which the AVM will be created, and select New AVM. The New AVM dialog is displayed. It provides the following pre-populated information for the AVM:

The parent unit's IP address, in the Prime Network Unit field.

The available memory on the unit.

The allocated memory for the AVM (default is 256 MB).

Figure 5 New AVM Dialog

Step 3 Enter a unique ID for the AVM in the ID field. The ID can be a number between 101-999.

Step 4 Enter a name for the AVM in the Key field. This key will be used as the AVM's unique identifier and display name in Prime Network Administration. If you do not enter a key, the default ID+time_stamp is used.

Step 5 Change the maximum allocated memory in the Allocated Memory field. The recommended size for the Quick Start Guide setup is 1536 MB (1.5 GB).

Step 6 Check the Activate on creation check box to load the AVM, change its administrative status to Up, to ensure that the AVM is loaded on subsequent restarts of the unit.

Step 7 Click OK. The new AVM is added to the selected unit and is activated. The AVM can now host VNEs.


To Add VNEs

To manage your network elements (NEs) with Cisco Prime Network, you must add VNEs to the system. Each VNE represents a single NE. Adding a VNE involves specifying identifying information and defining the communication protocols the VNE will use to communicate with the NE. When the VNE loads, Prime Network starts investigating the NE and automatically builds a live model of it, including its physical and logical inventory, its configuration, and its status. For detailed information about adding and managing VNEs, see Cisco Prime Network 4.0 Administrator Guide.

For the purposes of this Quick Start Guide, we assume the following:

The default Telnet protocol (not SSH) will be used for network element access (reachability) and modeling.

ICMP will not be enabled.

The default polling values will be used to determine polling intervals.

No additional IP addresses other than the management IP address will be monitored for events.

Before you begin to add VNEs:

1. Make sure that the devices to be managed by Prime Network are configured according to the prerequisites. See Configure Your Devices for Effective Cisco Prime Network Management.

2. All VNEs either use reduced polling or regular polling. For information on changing VNE polling settings, see Changing VNE Polling Settings in Cisco Prime Network 4.0 Administrator Guide.


Tip Place devices of the same type together in an AVM to reduce the memory consumption of the VNEs.


3. To speed up the procedure for adding VNEs to Prime Network, prepare the following information in advance:

a. Device management IP address

b. SNMPv1 or v2: read and write community strings

c. SNMPv3: The username and, optionally, the authentication or privacy configuration.

d. Telnet port number and login sequence.

e. XML: Protocol use, port, login sequence

f. HTTP: Version, port number, URL to connect to device, authentication credentials

g. TL1: Port, user, password (used by Change and Configuration Management only)

h. vCenter: Port, vCenter server address, authentication credentials (although this tab only appears after adding a UCS devices only, you will need this information)

4. Consider which VNE scheme to specify for your VNEs (Product, IPcore, EMS, or Default scheme). The VNE scheme determines the network element information that is collected by a VNE and populated in its model. You should choose the scheme based on the device's role in the network. If you want to designate a router as a core Provider or Provider Edge device in an MPLS VPN network, use IPCore, otherwise you can use Product. For details, see "Choosing a VNE Scheme (Check Technologies and Device Types)" in the Cisco Prime Network 4.0 Administrator Guide.

5. Make sure that the status of the AVM to which you will be adding VNEs is Up.

To add VNEs to an AVM:


Step 1 Navigate to the required AVM in the navigation tree.

Step 2 Right-click the AVM, then choose New VNE. The New VNE dialog box is displayed.

Step 3 In the General tab, specify the following mandatory information in the relevant fields:

a. VNE name, which will server as a unique identifier for the VNE.

b. Device management IP address of the network element.

c. In most cases, you should be able to use the default values for the other fields. For a full description of all the fields in this tab, see "VNE Properties Reference" in the Cisco Prime Network 4.0 Administrator Guide. You can change these settings at a later stage, if necessary, by right-clicking the VNE and selecting Properties.

Step 4 In the SNMP tab, enter SNMP credentials. For a full description of all the fields in this tab, see "VNE Properties Reference" in the Cisco Prime Network 4.0 Administrator Guide.

Step 5 In the Telnet/SSH tab, check the Enable checkbox and enter Telnet prompt information, as follows:

a. In the Prompt field, enter the prompt expected from the device.

b. In the Run field, enter the response to the expected prompt.


Note Click Mask if you do not want your entries to be displayed in clear text. The Confirm field will be enabled so that you can confirm your Run entry.


c. Click Add. The prompt-run sequence line is added to the table.

d. Continue to add lines as necessary, ending with a line that includes only the prompt.

For examples of how to enter the Telnet login sequence, see "Telnet and SSH Login Sequences: Notes and Examples" in the Cisco Prime Network 4.0 Administrator Guide.


Note Telnet is the default protocol used for network element access (reachability) and modeling. The assumption in this guide is that you will not be using SSH for this purpose. It is also assumed that you will not be using ICMP polling.


Step 6 Click OK to create the VNE.



Timesaver For similar VNEs, use the Clone VNE feature. Add the first VNE, then right-click on it and select Clone VNE. Specify the VNE name and IP address; other definitions are copied from the source VNE and you can change them if necessary.


Set Up Users and Security

Cisco Prime Network uses two methods to control user access and security:

Security access roles determine the actions a user can perform in the GUI clients

Scopes determine which devices a user can access, and the actions they can perform on those devices.

When you create a user in the system, you assign one user access role and one or more scopes to the user.

Prime Network provides five predefined security access roles that can be assigned to users:

Viewer—Read-only access to Prime Network Vision to view devices, links, events and inventory.

Operator—Can perform most day-to-day business operations, such as managing alarms, manipulating maps, viewing network-related information, and managing business tags.

OperatorPlus—Can manage the alarm lifecycle, in addition to the functions available to the Operator.

Configurator—Can perform tasks and tests related to configuration and activation of services, through Command Builder, Configuration Archive, NEIM, and activation commands.

Administrator—Full access to all devices and system functions. Only the Administrator has access to Prime Network Administration and Prime Network Events.

For details about the tasks available for the different user roles and scopes, see "Controlling Device Access and Authorization Using Device Scopes" and "Managing User Accounts and Authentication" in the Cisco Prime Network 4.0 Administrator Guide.

Add Scopes

Scopes are groups of network elements. Using scopes, you can determine the devices to which users have access. Each scope has a security level that determines which actions the user can take on the devices in the scope.

It is useful to create scopes before creating users so that the scopes will be readily available for assigning to the users. You can also create scopes on-the-fly during the user creation process.

To create a scope:


Step 1 Right-click on Scopes in the Prime Network Administration navigation tree, and select New Scope.

Step 2 Enter a unique identifying name for the scope in the Scope field.

Step 3 Specify the devices to include in the scope by selecting the required devices from the Available Devices list and then moving them to the Selected Devices list.


Tip You can use the Ctrl or Shift keys to select multiple devices.


Step 4 Click OK. The scope is created and is displayed in the content area.


Add Users

You need to create a user account for each person who will be accessing the Prime Network GUI. This involves defining the username and password and other user account settings, assigning a user role, and assigning scopes.

To create a user account:


Step 1 Right-click on Users in the Prime Network Administration navigation tree, and select New User. The New User wizard is launched. For detailed information about all the fields in the New User wizard, see "Creating User Accounts and Assigning Default Permissions" in the Cisco Prime Network 4.0 Administrator Guide.

Step 2 In the General Settings area, enter a unique identifying name for the user in the User Name field, and enter a password in the Password and Confirm Password fields. Follow these guidelines for creating a valid password:

At least 8 characters long, but not more than 20 characters.

Must contain at least 3 of the following: lowercase letters, uppercase letters, digits, and special characters.

Must not contain the user name.

Must not contain the words Cisco or Prime Network.

Step 3 Click Next.

Step 4 In the Prime Network User Role area, select the relevant user role for this user.


Tip When you select a radio button, a description of that role is displayed on the right.


Step 5 In the Device Security area, assign one or more scopes to define the user's device access rights, as follows:

a. Click Add. The Add Scope dialog is displayed.

b. Select the required scope(s) in the Available Scopes area.

c. Select a security level for the selected scope(s). This determines what actions the user will be able to perform on the devices in the scope.

d. Click OK. The scopes appear in the list of assigned scopes.


Tip Click Edit if you want to change the scope's security level.



Note If the scope you need does not exist, click New Scope to create it. You will then be able to assign it to the user.


Step 6 Click Next if you want to change the User Account settings, or click Finish to create the user account. The user account appears in the Users table.


Configure Your Devices for Effective Cisco Prime Network Management

Before adding your devices to the system, you need to run some commands on each device so that Prime Network can model the devices accurately and perform management tasks, such as processing syslogs, traps, logging, and so on. This section lists the device configuration prerequisites.

Please see "Configuring Devices So They Can Be Properly Modeled and Managed by Prime Network" in the Cisco Prime Network 4.0 Administrator Guide for details.

Table 9 Device Configuration Prerequisites 

Required Configuration
To be configured on...
Details

Configure devices to send SNMP traps

All Cisco devices to be managed by Prime Network

See "Configuring Devices So They Can Be Properly Modeled and Managed by Prime Network" in the Cisco Prime Network 4.0 Administrator Guide.

Configure devices to send syslogs

All Cisco devices to be managed by Prime Network

"Configuring Devices So They Can Be Properly Modeled and Managed by Prime Network," in the Cisco Prime Network 4.0 Administrator Guide.

Configure devices to forward events to the server hosting the Prime Network Event Collector

All Cisco devices to be managed by the Prime Network

For traps:

snmp-server community public RO  
snmp-server host <IP> public
 
        

For syslogs:

logging <IP> 
 
        

where <IP> is the IP address of the server hosting the Event Collector (usually the gateway).

Enable XML

IOS-XR devices

Prime Network VNEs use XML mode to communicate with IOS XR devices. Enable XML command:

xml agent tty

Configure Virtual Device Contexts (VDCs)

Devices running Nexus operating system

In the default VDC for the Nexus device, the vdc combined-hostname command must be configured.


Start Using the Prime Network Vision GUI To Monitor the Network

After installing and setting up Prime Network, you can start creating maps and monitoring your network elements in Prime Network Vision. This section contains the following subsections:

Log Into Cisco Prime Network Vision

Quick Overview of the Cisco Prime Network Vision GUI

Create a Map for Network Visualization

Fault Management Basics

Log Into Cisco Prime Network Vision

To log into Prime Network Vision:


Step 1 Choose Start > Programs > Cisco Prime Network > Cisco Prime Network Vision.The Prime Network Vision Login dialog box is displayed.

Step 2 Enter your username and password.

Step 3 In the Host field, enter the IP address (as specified during gateway installation) or the hostname of the Cisco Prime Network gateway server.

Step 4 Click OK. The Cisco Prime Network Vision window appears empty when it is opened for the first time.


Quick Overview of the Cisco Prime Network Vision GUI

Prime Network Vision is the main GUI application used to visualize the network through network and service maps, to view device physical and logical inventories and connectivity, and to manage device configuration and software images.

Prime Network Vision enables you to:

View network inventory and multiple-layer connectivity.

Troubleshoot, monitor, and manage network elements (NEs).

Model and view network maps, maintaining up-to-date topological information on device connections, traffic, and routes.

Figure 6 shows the Cisco Prime Network Vision window. The window includes a tree-and-branch representation of the network elements on the left, and a map view representation of the network elements, links, and logical entities such as VLAN, VPNs and other entities that comprise the network on the right.

Map view icons are displayed in aggregated or expanded view. Any icon that has a + in the upper right corner is closed aggregation. Double-clicking it expands the aggregation. Right-clicking and selecting Show Thumbnail displays the aggregation contents within the parent map. Anything that has a green frame around it and a - (minus sign) in the upper right corner is an open aggregation. Almost all the items in the upper right corner of Figure 6 are aggregations as indicated by the + symbol. Aggregations can contain other aggregations.

Bell icons displayed in different colors can be attached to network element icons. These are alarm severity badges. The color indicates the highest severity alarm raised for the network element. Beneath the severity badges are the management state badges. The management state indicates the state or mode of the VNE managing a network element and the communication with it. This enables you to determine the accuracy of the network information and the availability of VNEs to carry out network operations.

For a list of all icons and buttons displayed in Cisco Prime Network Vision, see "Icon and Button Reference" in the Cisco Prime Network 4.0 User Guide.

Figure 6 Cisco Prime Network Vision Primary Window with an Open Map

1

Menu bar—The functionality that a user can access depends on the user role and the security level of the scopes assigned to the user. The menus are context-sensitive and the options vary depending on your selection in the application. See "Prime Network Vision Window" in the Cisco Prime Network 4.0 User Guide for details.

2

Toolbar—The toolbar is context-sensitive and the options vary depending on your selection in the application. See "Cisco Prime Network Vision Toolbar" in the Cisco Prime Network 4.0 User Guide for details.

3

Inventory and map tabs—The inventory tabs enables you to access many Prime Network Vision features and functions without opening a map. See "Prime Network Vision Inventory Tabs" in the Cisco Prime Network 4.0 User Guide for details.

4

Map view content pane. The content pane displays three views: map, list and links. For details, see "Content Pane: Map, List, and Links Views" in the Cisco Prime Network 4.0 User Guide.

Map view—Topological view of managed elements.

List view—Tabular view of managed elements contained in the map.

Links view—Tabular view of links and link aggregations.

5

Status bar—Displays the view's current connection status and status of any issued commands. The memory utilization bar in the status bar displays the amount of memory used by the client. By default, if memory utilization exceeds 60%, it is colored yellow, and if it exceeds 80%, it is colored red.

6

Ticket pane—Displays tickets relating to all the network elements in the map.

7

Switch between the tickets and the latest events pane.

8

Navigation pane—Displays a tree-and-branch representation of the network elements and aggregations defined for the loaded map.


Create a Map for Network Visualization

Prime Network Vision enables you to create multiple network maps to represent specific network views. Views can cover specific network segments, customer networks, or any other mix of network elements desired. When you create a map, it is available to other users if they have sufficient access and security privileges.

The network maps provide a graphic display of active faults and alarms, and serve as an easy access point for activating services.

To create a new map:


Step 1 Choose File > New Map in the main menu. The Create Map dialog box is displayed.

Step 2 Enter a name for the new map and click OK.

Step 3 Add elements to your new map. Choose File > Add to Map or click the down arrow next to the Add to Map icon in the main toolbar. Choose the type of element you want to add to the map, for example, network element, VPN, VPLS, VLAN, and so on.

Figure 7 Select Element Type

Step 4 In the Add Element dialog box, either select Show All to display all available elements of that type, or run a search for specific elements.


Note If a network element is not included in your scope, it is displayed with the locked device icon.


Figure 8 Select Elements to Add to Map

Step 5 Select the elements that you want to add to the map. You can select and add multiple elements by pressing Ctrl while selecting individual network elements or by pressing Ctrl +Shift to select a group of elements.

Step 6 Click OK. The elements are displayed in the navigation pane and in the map. In addition, any associated tickets are displayed in the ticket pane.


Fault Management Basics

Prime Network analyzes and manages faults through event collection, identification, and correlation. After identifying the event, and associating it to the right device component represented in the VNE, Prime Network groups the events related to it, then uses the virtual network model to inspect the fault and perform correlation to find the root cause and create a ticket.

An event is a distinct incident that occurs at a specific point in time, for example, a port status change, connectivity loss, device unreachable, etc. Examples of events include:

Port status change

Connectivity loss (for example, BGP Neighbor Loss) between routing protocol processes on peer routers

Device reset

Device becoming unreachable by the management station

An event is a possible symptom of a fault, which is an error, failure, or exceptional condition in the network.

In Prime Network Vision and Prime Network Events, an icon appears for each ticket or event in the Prime Network (based on the severity). Events have an associated severity, and each severity is represented by a specific color—Critical (red), Major (orange), Minor (yellow), Warning (light blue), Cleared/Normal (green), Information (medium blue), and Indeterminate (dark blue). For more details about event status indicators, see "Prime Network Events Window" in the Cisco Prime Network 4.0 User Guide.

The lifecycle of a fault scenario is called an alarm. An alarm is characterized by a sequence of related events, such as port-down and port-up. A ticket represents an attention-worthy root alarm whose type is marked as ticketable.

For details about tracking faults and working with tickets in Prime Network, see "Tracking Faults using Cisco Prime Network Events" and "Working with Tickets in Cisco Prime Network Vision" in the Cisco Prime Network 4.0 User Guide.

Appendix A: Device Information Form

You can print this table and use it to organize your AVM-VNE distribution and list the information you will need when creating VNEs.

VNE Name
Device Type
AVM
Management IP Address
SNMP Credentials
Telnet Port and Login