Cisco Cisco Prime Network 4.0 Installation Guide

Disable the Cisco Prime Network gateway resource in the VERITAS Cluster Manager 
application.

Login to the gateway and start Prime Network by running “networkctl start“.

Wait until Prime Network gateway and units are up and running before continuing with this 
patch installation.

To copy the DP file to a central location:

Log into the Prime Network gateway server as root user and enter the following command to create a 
new directory outside of the Prime Network home directory and grant user privileges.

% mkdir /ThirdPartyVNEDrivers

% chmod 777 /ThirdPartyVNEDrivers

Grant the directory network-user permissions. (network-user is the UNIX account for the Prime Network 
application.) In this example, network-user is network40.

% chown network40:PN /ThirdPartyVNEDrivers

Using ftp, copy the DP file (PrimeNetwork-4.0-ThirdParty-DP1308.tar) into the newly-created 
directory. In this example, the DP file would exist in the following location:

/ThirdPartyVNEDrivers/PrimeNetwork-4.0-ThirdParty-DP1308.tar

This section provides some general information on the ivne script, which is used to install independent 
device driver files. We recommend that you use the option that is documented in the installation and 
rollback steps provided in this document; the options are described here for your information. For more 
information on the ivne script, see the 

1

Install VNE 
Device Package 
from a local 
directory

Installs device package from a local 
directory on the gateway server.

We recommend that you 
use this option.

You want to install the 
entire Device Package.

2

Install VNE 
Device Package 
from a web 
repository.

Installs device package from a remote host 
such as a web server that is providing 
central support to multiple Prime Network 
gateway servers.

You want to install only 
individual jars files.

The jar files you will install 
do NOT contain support for 
a previously-unsupported 
NE.