Cisco Cisco Prime Network 3.10 Installation Guide
Page 4 of 10
Prime Network 3.10.0 VNE Device Package Installation Guide
% chmod –R 777 VNEDP
5 Using the ivne Script
This section provides some general information on the ivne script, which is used to install VNE Device
packages. For more information on the ivne script, see the
packages. For more information on the ivne script, see the
#
Option
Description
Use this when…
1
Install VNE Device
Package from a
local directory
Package from a
local directory
Installs device packages from the
downloaded device package tar on the
gateway server
downloaded device package tar on the
gateway server
You want to install the entire
Device Package or individual jar
files.
Device Package or individual jar
files.
2
Install VNE Device
Package from a
Web Repository
Package from a
Web Repository
Installs device packages from a remote
host such as a web server that is providing
central support to multiple Cisco Prime
Network gateway servers.
host such as a web server that is providing
central support to multiple Cisco Prime
Network gateway servers.
In case , you have multiple gateway
server to deploy the DP and use
web server as central location
server to deploy the DP and use
web server as central location
3
List the installed DP
drivers and the
driver jars files.
drivers and the
driver jars files.
Lists the drivers that exist in the
$PRIME_NETWORK_HOME/Main/drivers
directory on the gateway server.
$PRIME_NETWORK_HOME/Main/drivers
directory on the gateway server.
You want to see the DP installed
and the driver jars contained in the
DP.
and the driver jars contained in the
DP.
4
Uninstall a Device
Package (DP)
Package (DP)
Uninstalling the Device packages from g/w
and unit servers
and unit servers
When you want to permanently
remove the DP which are no longer
in use
remove the DP which are no longer
in use
Q Quit
Exits the ivne script.
You want to quit the script.
You can install the entire DP with all the jar files it contains. All jar files use the following naming
convention:
convention:
Vendor-JarType-VNEJarVersion.jar
JarType can be Modules, Commons, or device-specific. For example:
Cisco-100xx-v4.0.0.0.jar
Cisco-45xx-v4.0.0.0.jar
Cisco-49xx-v4.0.0.0.jar
Cisco-Modules-v4.0.0.0.jar
Cisco-Commons-v4.0.0.0.jar
Cisco-45xx-v4.0.0.0.jar
Cisco-49xx-v4.0.0.0.jar
Cisco-Modules-v4.0.0.0.jar
Cisco-Commons-v4.0.0.0.jar