Cisco Cisco Prime Network 4.2 Installation Guide
15
Step 2
Click Next. The Destination Location window is displayed. Click Browse to change the installation directory, if you do
not want to use the default, then click Next.
not want to use the default, then click Next.
Note
The default installation location is C:\Cisco Systems\Prime Network\. If you are installing on Windows 7, 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.
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
In the Select Components window, select the clients you want to install (Vision, Events, and/or Administration) and
click Next.
click Next.
Step 4
If you want to change the default Program Manager group, enter your preference and 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, Prime Network 4.2.2.
You should add a version number to the Program Manager group; for example, Prime Network 4.2.2.
Step 5
Click Next to start the installation.
Step 6
When the installation is complete, choose the options displayed in the final installation window, according to your
preference:
preference:
•
Create “Quick Launch” icons—Create a Quick Launch icon for Prime Network Vision and Prime Network
Administration on the Quick Launch toolbar.
Administration on the Quick Launch toolbar.
•
Launch Prime Network Vision—Immediately launch Prime Network Vision.
Step 7
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
Network. For information, see the
.
5
Next Steps
After you have installed Prime Network, you must perform the following tasks:
•
•
•
•
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.
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).
(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
assumptions and caveats described in
Following are more specific guidelines for AVM-VNE distribution based on the
for the Quick Start Guide setup: