10-28-2014 10:20 AM - edited 07-05-2021 01:49 AM
10-28-2014 08:08 PM
Prime and WCS are completely different beasts.
Based on what you have in your environment you need a much beefier VM. Remember these are not customizable either. Only one .OVA can be customized (2.0- and later). You have to assign it the resources it requests or it may not function correctly.
I would also go to prime 2.0 because they changed the OVA sizing around and based on what you had you will have to blow it away and deploy a new .OVA.
The link below is to the 1.3 - You should be running at least a medium or large. 2.0 you would be able to get away with the custom ova.
http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/prime-infrastructure/deployment_guide_c07-721232.html
10-29-2014 02:34 AM
I'm finding it very difficult to justify a business case for the system resources this product requires. It uses more resources than most of our business application servers! We have just a handful of network engineers using it. We are not asking it to do any more than WCS was which ran very well with a fraction of the resources. As a dedicated linux appliance, it seems to have more overheads than a Windows server which I find baffling.
At the moment I simply cannot give it more disk space, so will have to make do. I have extended the partitions by 50GB which has helped.
I need to work out what is maxing our the cpu and the errors with the web interface as a priority.
Can I look at CPU time and find the bad process?
11-11-2014 02:16 PM
Chris,
You really need to get into the 2.x Prime series. 1.3 / 1.4 are just pure garbage in terms of speed, disk mgmt and bugs. It's not a fun upgrade either. I recommend doing a clean install of Prime 2.x and leaving 1.x behind completely.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide