System Requirements
Review the system requirements before installing the Cisco Prime IP Express 8.3.7 software:
-
Java—You must have the Java Runtime Environment (JRE) 1.6 or later, or the equivalent Java Development Kit (JDK) installed on your system. (The JRE is available from Oracle on its website.)
-
Operating system—We recommend that your Cisco Prime IP Express machine run on the Windows operating system as described in the "Server Minimum Requirements" table below. Cisco Prime IP Express is supported on 32-bit or 64-bit operating systems.
Cisco Prime IP Express supports running in VMWARE ESXi 5.0 or later environment.
Note
Cisco Prime IP Express applications are 32-bit executable programs and the system should support 32-bit applications (Java JRE/JDK, OpenLDAP library (for RedHat)).
-
User Interface—Cisco Prime IP Express currently includes two user interfaces: a web UI and a CLI:
-
The web UI has been tested on Microsoft Internet Explorer 9 and Mozilla Firefox 21 and later. Internet Explorer 8 is not supported.
-
The CLI runs in a Windows command window.
-
Tip |
Include a network time service in your configuration to avoid time differences between the local and regional clusters. This method ensures that the aggregated data at the regional server appears consistently. The maximum allowable time drift between the regional and local clusters is five minutes. If the time skew exceeds five minutes, then the installation process will not be able to correctly register the server with the regional. In this case, unset and set the password on the regional cluster, and sync again. |
Component | Operating System | |
---|---|---|
Windows | ||
OS version1 |
Windows Server 20082 |
|
Disk space3 |
With basic DHCP and optimal hardware configuration:
|
|
Memory5 |
Small networks-4 GB, Average networks-8 GB, or Large networks-16 GB |
Recommendations
When Cisco Prime IP Express is deployed on virtual machines, review the following recommendations:
- Do NOT deploy HA DNS or DHCP failover partners on the same physical server (in separate VMs). This will not provide high availability when the server goes down. Ideally, the high available/failover partners should be sufficiently "separate" that when one fails (because of a hardware, power, networking failure), the other does not.
- When deploying multiple CPIPE VMs on the same physical server (or servers served by a common set of disk resources), you should stagger the automatic nightly shadow backups (by default, they occur at 23:45 in the server's local time). To know how to alter this time, see the "Setting Automatic Backup Time" section in Cisco Prime IP Express 8.3 Administrator Guide.
Note |
It may be acceptable to not follow the above recommendations for lab environments; but they must be followed for production. |