Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Failed CUCM 9.0(1) installation

Posted on 2014-03-03
5
1,217 Views
Last Modified: 2014-06-07
Hello Experts,
I am have serious issues trying to get Cisco Unified Call Manager v 9.0 (1) installed into a test lab and am looking for assistance.

I am using VMPlayer v10 (latest available as of this time), configured with 4gb memory, 180gb scsi hard drive, 1 processor, network bridged adapter, OS set as Red Hat Linux enterprise v5. I have also tried Red had v4 and then v6 as well.

I continue to get prompted several times for a logon after the installation. I enter my information three times and on the third time I get in as admin (so I know my credentials are correct). But, I also get "Permission Denied" errors at "/usr/local/platform/bin/cliscript.sh:" at various lines such as 135, 145, 17, and 18. I also get an IOException: hardware API:Cannot run program "/usr/local/bin/base_scripts/ihardware_iml": java.io.ioexception: error=13, Permission denied"

I've searched high and low on the Internet for some answers and am usually pretty successful with research, but am truly stuck this time. Any assistance on this is appreciated. I am very new to CUCM and am trying to get it going in a lab.

Thank you.
0
Comment
Question by:kevster5
  • 3
  • 2
5 Comments
 
LVL 20

Expert Comment

by:José Méndez
ID: 39900820
Sounds like when you were creating the virtual machine you let VMPlayer automate the install as if it was a regular redhat install. This usually leads to VMP finding the root installer executable instead of letting the Cisco one guide you through the install. Reinstall the machine by booting from the ISO and let it go through again, it should complete and the prompt will look like:

login as:

Open in new window


Not sure if VMP has the option to open an OVA/OVF template, that would be the safest way to run your virtual hardware.

cucm_9.0_vmv8_v1.5.ova
0
 

Author Comment

by:kevster5
ID: 39900858
Hi Willy,
Thanks for your comment. You are correct that I did define Red Hat as the OS in the install. I'll see what other options I have to not specify that and repost results. It will take a while as it is a long installation process.

Another question I had is regarding the recovery ISO and IME recovery ISO that Cisco provides customers. Are these both used for recovery only and if so, what is the difference? In some of my download areas within my Cisco account, I only see these two ISOs as being available.

Thanks again!
0
 

Author Comment

by:kevster5
ID: 39900998
Willy,
I checked through the configuration and also used the OVA file as a template. It does have Linux Red Hat defined under the General Options area already. There is no way not to define the OS in the VMware image.

I appreciate any additional thoughts. Is this something in the permissions of those files that are not being set correctly by the installer?

Thanks again.
0
 
LVL 20

Accepted Solution

by:
José Méndez earned 500 total points
ID: 39901269
Redhat is your OS of choice. What I am saying is that sometimes when the virtual machine wizard guides you through, it takes ownership of the installation to make it as fast as possible. That is what leads to failure.

The recovery discs are meant to scan hard drives for filesystem errors and allow you to revert to a previous CM version after an upgrade is something goes south. These are meant for troubleshooting purposes mostly.
0
 

Author Closing Comment

by:kevster5
ID: 40119244
Never was ever able to resolve this. Thank you for your help though.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question