In case of Solaris, you must install Prime Cable Provisioning on a Sun SPARC platform that runs a Solaris 10 operating system and 64 bit hardware system with at least 4 GB memory. We recommend that you use a Sun SPARC multiprocessor platform. Also, you must configure coreadm to avoid overriding of core files. For more information, see Solaris documentation.
Before installing Prime Cable Provisioning, download and install the recommended Solaris patches from the Oracle support site.
Prime Cable Provisioning ships with the required JRE version 1.6.0_32, which resides in the <BPR_HOME>/jre directory.
You must also download and install the Java Platform Standard Edition (Java SE) cluster patches recommended by Sun Microsystems to install Prime Cable Provisioning on a system that runs Solaris 10. See the following table:
Table 1 Java Standard Edition Cluster Patches for Solaris 10
||Zones library and zones utility patch
||Install and patch utilities patch, for more information, see Installing and Uninstalling Prime Cable Provisioning
||Solaris crypto framework patch
||Svccfg and svcprop patch
Before you install Prime Cable Provisioning on Solaris, ensure that you install the —SUNWxcu4— package, on the same server. This is an optional package available as part of the Solaris OS installation.
In case of Linux, you must install Prime Cable Provisioning on Red Hat Enterprise Linux 5.8 or 6.3, or on CentOS 5.8 or 6.3, using x86-64 (64-bit version of x86), with at least 4 GB memory. The SELinux should be disabled.
To disable SELinux feature, modify the
config file using the following command:
# vi /etc/selinux/config
where config—File that controls the state of SELinux on the system. In this file, set the value of SELINUX to disabled.
Before you install Prime Cable Provisioning on Linux, ensure that you install the —sysstat— package, which is an optional package, for the proper execution of the diagnostic scripts. You can configure RDU Redundancy (an optional feature) on RHEL 6.3 platform. For more information on RDU Redundancy, see Setting Up RDU Redundancy.