PDF(79.7 KB) View with Adobe Reader on a variety of devices
ePub(75.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(70.7 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 19, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the procedure to install a Cisco Policy Suite (CPS) All in One (AIO) solution on a VMware Workstation Player.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
Computer that runs MicroSoft Windows. The procedure can be applied, with small variations for MAC OS as well.
VMware Workstation of VMware Workstation Player software (VMware Fusin for MAC OS)
At least 4GB RAM (better 8GB) available on host machine
Four available CPU cores.
Two virtual network interfaces (it is ok to use the Network Address Translation (NAT) and Host-Only virtual networks)
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Such a deployment can be useful to get familiar with the solution itself, for training purposes or as a lab for pre-production feature testing.
The procedure applies to CPS version 10.1.0, but can be adapted for other versions as well. Check the official documentation for specific instructions.
Step 1. Download CPS software from cisco.com, namely CPS_10.1.0.release.iso and CPS_10.1.0_Base.release.tar.gz files.
Step 2. Extract. CPS_10.1.0_Base.release.tar.gz. Inside you must find a base.vmdk file (VM disk image). This is used in a later step as the hard drive for Virtual Machine (VM).
Step 3. Create a new VM of CentOS 64-bit type. Chose a very small Hard Disk Drive (HDD), which you can delete later.
Customize hardware, so it includes two Network Interface Controller or Card (NICs), one for internal and one for management.
This the way to edit the VM settings:
Add at least 4GB RAM.
Add four CPU cores and enable the Virtualize Intel VT-x/EPT or AMD-V/RVI option.
Insert the CPS_10.1.0.release.iso in the virtual CD Rom.
Remove the old HDD.
Add the earlier downloaded base.vmdk file as HDD as follows:
Open the virtual machine settings editor (VM > Settings) and click Add. The Add Hardware Wizard guides you through the steps to create your virtual disk.
Click Hard Disk, then click Next.
Select Use an existing virtual disk, then click Next.
Enter the path and filename for the existing disk file, or click Browse to navigate to the file.
Note: The Hard Disk size is 100GB, but it actually occupies much less (it's dynamic size).
Close the VMWare player and browse towards the folder where the VM was created (must be something like C:\Users\<username>\Documents\Virtual Machines)
Open the .vmx file with a text editor and modify the virtualHW.version to 8 as listed here:
virtualHW.version = "8"
Save the file and boot the VM.
Note: This message may be reported on the Cluster Manager VM console. You can disregard this message 'Probing EDD (edd=off to disable)'.
It can take around ten minutes until the CPS boots and provides the log in prompt.When it is available, log in with root/cisco123.
Step 4. Configure the network settings.
Assign the eth0 interface to a LAN (alias private) by modifying /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:
Ensure that the IP addresses are configured in line with the IP addresses associated to virtual host adapters to which they connect in VMware Player.
For example, if the first interface is attached to the VMware Network Adapter VMnet 8 which is configured as a part of 192.168.119.0/24 network (as depicted here), then you must chose an IP address from this range.
Step 14. Run these commands to publish configuration and restart CPS.
restartall.sh script process prompts for either Y/N to restart the process. Enter Y to restart the process.
Step 15. Reset the password for Control Center. Run the change_passwd.sh script. As this is a fresh installation, before you run change_passwd.sh script, run source /etc/profile.d/broadhop.sh to source the broadhop scripts in the PATH. This is applicable for first time only.