Thursday, August 27, 2009

Installing CUCM 7 on Hyper-V

*Updated at the bottom*

#WARNING#
Information here is for educational purposes, do not apply to any production environment! This blog post is a result of me wanting to run CUCM in an environment not supported by Cisco or Microsoft in any way, and is intended for LAB purposes only.

If you have read my earlier posts, you know I am trying to study to a CCIE Voice certification. I have been forced to slow down a bit by things at work and in my life, but the goal is still there.

As Cisco has moved to their v3 blueprint, one of the first things I have to do is to install CUCM 7 into a virtual environment. We already have a Hyper-v installation at work, and that's where I wanted to install the server. This proved harder than I though.

If you have tried the same thing, you'll probably end up with the error message:

'The hardware you are using is not supported for this product. Installation will now halt.'

I know CUCM is supported as a virtual machine, but it is obviously not supported by hyper-v. Since I do not have a license for vmware server, I found myself in a tight spot. But I found a way around my problem, and I do have CUCM 7 running on Hyper-V. Here is a short drill down of what I did:

- My first obstacle was not having a virtual server where I could create a machine, I only have the free player at my disposal. After a few attempts at Google, I found a site called easyvmx where i can create a blank VMware machine online (then download and mount it with player). With the empty machine (remember to allocate enough ram (2gig), disk space (120Gig) and to create it as a RED HAT ent. image) it was easy to start the player and boot from the CD-ROM (mounted ISO image of CUCM 7). The installation was straight forward, but my USB disk was to slow. I ended up installing the vmware image on my local HD instead of the USB drive. Don't know why, other VM's been ok on the USB.

- Next I had to convert the virtual HD from VMDK to VHD. I came across a tiny tool called Vmdk2Vhd from the vmtoolkit. Make sure you get v 1.0.13, as the version I found first was unable to read my VMDK.

- After converting and moving to hyper-v I was then stopped by an error message during "starting local" which prompted me: "Hardware not supported" and an option to shutdown the computer.

This is where I needed to get creative. I booted the Hyper-v image with an Ubuntu live CD and edited the file /usr/local/bin/base_scripts/hardware_check.sh by adding Exit0 as the first command in "function hardware_check_display_error_shutdown()".

I am uncertain if could have skipped the entire hardware_check.sh script, so I just ignored the error.

Thank you colleagues for helping me with the Linux stuff... You know who you are :)

**I'm sorry, there was a typO in this post. It is supposed to be "exit 0" not exit0.**

13 comments:

  1. Hello,

    despite doing all that you've written here, I still receive this error: "the hardware you are using does not support the cisco unified communications manager product suite..."
    any suggestions?
    thanks for your effort

    ReplyDelete
  2. Hi,

    At which step are you stuck? Do you get to install at all?

    ReplyDelete
  3. Hello,

    sorry for confusion.
    - successfully installed in vmware
    - converted to vhd
    - loaded into Hyper-V
    - edited hardware_check.sh

    finally, when I run CUCM after all this steps, I get the error MSG described above.

    anyway, my edited script looks like this http://dl.getdropbox.com/u/402266/hardware_check.sh.png

    suppose there might be a problem?

    ReplyDelete
  4. Sorry for the typO....

    it should spell exit 0 not exit0:
    function hardware_check_display_error_shutdown()
    {
    exit 0
    local tmp_msg="$@"

    ReplyDelete
  5. Hello Lasse,

    perfect, works like a charm :) many thanks for the entire post.

    PS: Ever tried to run ASA Project (http://asa_project.gromnet.net) in Hyper-V?

    ReplyDelete
  6. I got to the point of converting the VMHD to a VHD and attempted to run in Hyper-V. I could not run it. I then created a virtual machine in Virtual Server and booted. It was extremely slow with many errors. TOMCAT service was not running and I could not start it manually. I can't even run the command 'utils system shutdown' as the result is unsuccessful. I really want to get this installed on Hyper-V.

    The only thing I did differently was upgrade to 7.1.x in VMware before coverting to the VHD. All is fine with the VMware guest.

    Any suggestions?

    ReplyDelete
  7. For those of you who have had issues:

    I used WinImage to convert the VMDK to VHD. Worked incredibly smoothly.

    Download the iso of Ubuntu 9 and boot to that. Select Boot without changing my computer. When it comes up:

    1) Press Alt+F1 and open Terminal
    2) cd /media/_/usr/local/bin/base_scripts
    3) sudo chmod 777 hardware_check.sh
    4) gpedit hardware_check.sh

    Add the "exit 0" line and Alt+F, Save. Now you can reboot, eject the iso and run smooth.

    Thanks for the tutorial Lasse!! Very much appreciated.

    ReplyDelete
  8. Thanks Guys, but J can you expand even more on the Ubuntu steps...once I've booted Ubuntu and opened terminal - surely the cd command needs to include the location of my VHD file? I don't get quite where or how the VHD is referenced....

    ReplyDelete
  9. Hi,
    I am struck please help!
    Having installed CUCM 8 on Linux Enterprise Red Hat 64 bit. I stopped CUCM and converted VMDK to VHD using VMDK2VHD tool and also tried WinImage for the purpose. I created virtual machine in Hyper V and attached the newly converted .vhd file to this virtual machine. Now once I start this virtual machine I get error during boot saying "/common: UNEXPECTED INCONSIATENCY: Run fsck Manually.
    *** An error occured during the file system check.
    *** Dropping you to shell..........

    Please help!
    I am new to Linux

    ReplyDelete
  10. Hi I need your help!
    After installing CUCM 7 in Linux Ent. Red Hat 5 (64 bit) using vmware, I used Vmdk2Vhd v 1.0.13 to convert it to VHD. Then I copied .vhd and moved to Hyper-V new guest machine. Once I boot the machine, during the boot process I get the error "No such file or directory while trying to open /dev/sda1" *** An error occured during the file system check.
    Please advise..... I struggling for last 4 days :(

    ReplyDelete
  11. I truly wished I could help you. But sadly I'm not a Linux guy.
    If you have the original file, have you tried to convert it again?

    ReplyDelete
  12. Very interesting post

    How about preventing the hardware detection even during the initial install.

    Any ideas on how to do that? For some reason even with 160Gb disk and 2 Gb Ram and multiple processors it simply will not install into my VMWARE machine.

    Your solution appears to prevent the error from blocking the startup of an already installed CUCM. I kinda need to prevent it from blocking the install.

    Or is the same script used for both functions?

    ReplyDelete
  13. I have not been able to block the verification upon installation. That is why I installed it on a supported version, then moved it to an unsupported solution. (And disabled the boot check).

    I recommend you check the documentation on the CUCM version you are installing at the moment. The exact VMWARE versions will be listed there.

    ReplyDelete

Comments on old posts will be moderated.
Comments on new posts will appear immediately..