Install of CUCM 8.6.1.10000-43 on VMWare fails on installing progmeter

Hi, Everyone
First time post here, and first time installing CUCM (any version).
I built a VM using a downloaded OVA template for CUCM 6.5.1.10000-43, and the install fails with a critical stop.  Once I figured out how to dump logs to the virtual serial port, and looked at the install.log, I found the following information that looks like where the install failed (these are the only LVL::Error and LVL::Critical messages in the log).
It looks like install failed to install the progmeter application component.
Does anyone know what this app does?  Any ideas on why it might have failed to install and possible workaround?
I may already have the answer to the question, as I'm attempting install on a VM running on VMWare vServer (rather than ESX/ESXi/vSphere).  It is possible that simply being on an unsupported configuration is my problem.  I'm trying to work with the equipment immediately available to me, but fully understand that I may have set myself up for failure by even attempting this.
Any help is appreciated greatly.
Regards,
Sean C
INSTALL LOG SNIPPET
08/17/2011 17:51:51 component_install|File:/opt/cisco/install/bin/component_install:743, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
08/17/2011 17:51:51 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:155, Function: install(), failed to install application components|<LVL::Critical>
08/17/2011 17:51:51 post_install|File:/opt/cisco/install/bin/post_install:869, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)|<LVL::Error>
08/17/2011 17:51:51 post_install|Exiting with result 1|<LVL::Info>
08/17/2011 17:51:51 post_install|INSTALL_TYPE="Basic Install"|<LVL::Debug>
08/17/2011 17:51:51 post_install|File:/opt/cisco/install/bin/post_install:570, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting|<LVL::Error>
08/17/2011 17:51:52 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
08/17/2011 17:51:52 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
"/opt/cisco/install/callmanager/scripts/cm_msa_post.sh install PostInstall 8.6.1.10000-43 8.6.1.10000-43 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " terminated. Exceeded max time (360)
The system will now halt.
Continuing will allow you to dump diagnostic information before halting." "Continue"|<LVL::Debug>

Hi,
Has anyone found a fix for this?
I am trying to run call manager 8.6.1 on the following enviroment
VMware ESXI 4.1
4GB of RAM
80 GB HDD Space
I have allocated the VM one CPU
In regards to vsergeyey reponse I have checked the network adapter and this is flexible.
I have run the OVA template firstly before mounting the image
I have tried installing numerous times.
Each and every time near the "Installing Database Component" I get the following error;

Similar Messages

  • Party Entrance Tone not working on CUCM 10.5(1.10000.7)

    Party Entrance Tone not working on CUCM 10.5(1.10000.7) . This is an intermitent issue for Meet Me conference.
    ++On the CUCM Service Parameter Party Entrance Tone has is TRUE .
    ++On Directory number Party Entrance Tone is ON . However the Party entrance tone (Beep tone) not coming when Meet Me conference going on .
    Gateway 3945 with IOS Version 15.3(3)M5, RELEASE SOFTWARE (fc3).
    The conference Configureation as below.
    sccp local GigabitEthernet0/0
    sccp ccm 172.20.0.152 identifier 1 priority 1 version 7.0
    sccp ccm 172.20.0.153 identifier 2 priority 2 version 7.0
    sccp ccm 172.22.0.110 identifier 3 priority 3 version 7.0
    sccp ccm 172.22.0.111 identifier 4 priority 4 version 7.0
    sccp
    sccp ccm group 1
     bind interface GigabitEthernet0/0
     associate ccm 1 priority 1
     associate ccm 2 priority 2
     associate ccm 3 priority 3
     associate ccm 4 priority 4
     associate profile 2 register ASB-DR-GW04CFB
     associate profile 1 register ASB-DR-GW04XCO
    dspfarm profile 1 transcode 
     codec g711ulaw
     codec g711alaw
     codec g729ar8
     codec g729abr8
     codec g729br8
     codec g729r8
     maximum sessions 60
     associate application SCCP
    dspfarm profile 2 conference 
     codec g729br8
     codec g729r8
     codec g729abr8
     codec g729ar8
     codec g711alaw
     codec g711ulaw
     maximum conference-participants 32
     maximum sessions 12
     associate application SCCP
    Can any one tell me how the party entrance tone happening when a confernce session open.Is it generated from the hardware Confernce resource which configured on the gateway while mixing the RTP streams ? Is there anything to do with CUCM or any service in CUCM to generate the Party entrance tone ?

    Hi,
    It looks like the following bug
    https://tools.cisco.com/bugsearch/bug/CSCup27560/?referring_site=bugquickviewredir
    MeetMe Party Entrance Tones stop working
    CSCup27560
    Description
    Symptom:
    - MeetMe party entrance tones stop getting played to participants when they join/leave
    - The issue will go away for a few weeks if the CCM service is restarted, but then will come back.
    - When the issue comes back, it fails 100% of the time.
    Conditions:
    This problem would occur when we have user having a call from user in different node initiate transfer and also initiate MeetMe and dial user in different node. When transfer completes, we will have a leak in current node MeetMe. This issue should have been there in all CCM versions.
    Workaround:
    Restarting the CCM service will correct the problem temporarily.
    You can either try the workaround or upgrade to one of the fixed versions.
    HTH
    Manish

  • While installing CUCM 9.0.1.1000-37 on Vmware Workstation 8.0 m getting default gateway name/address is invalid or gateway is.

    Hi,
    while installing CUCM 9.0.1.1000-37  on Vmware Workstation 8.0 m getting  default gateway name/address is invalid or gateway is not properly configured. Can any1 help me to get out of this issue.
    Want to install  CUCM 9.0 on Vmware Workstation 8.0..

    Er... is there a chance your network is not properly configured? Can you please shed some light on the details of your network?
    By the way, I doubt that CUCM would ever be able to start up in VMWare Workstation.
    G.

  • CUCM 10.0.1.10000-24 Active Directory Sync - Directory URI cleared after sync

    Hi,
    I would like to know if it is intended or bug when AD sync is performed each time it clears Directory URI field even I have selected it in mapping to <None>.
    Because I have different domain for Jabber URI dialing than email domain I need to fill it up manually, but performing sync other data from AD.
    Thanks

    isn't there any workaround how to sync users from LDAP but have Directory URI for user set manually?
    I need to set it up due IM and Presence as I have domain in email format for Lync Server 2013 and now I need another domain for CUCM and IM and Presence as it couldn't coexist on same domain. Or it could?

  • EBS Install on OEL 5.4 using vmware fails with RC-50004 RW-50010

    Hello ALL,
    I am trying to install EBS R1212 on Linux OEL 5.4 using vmware on windows xp pro and i am getting the below err in Please help...
    I tried the setup with R1212 x86 and R1212 x86-64 on vmware i am getting the same error with both versions... can you please help/assist..
    RC-50004: Fatal: Error occurred in ApplyDatabase:
    Control file creation failed
    Cannot execute configure of database using RapidClone
    RW-50010: Error: - script has returned an error: 1
    RW-50004: Error code received when running external process. Check log file for details.
    Running Database Install Driver for VIS instance
    Processing DriverFile = /home/oracle/EBS/startCD/Disk1
    Thanks,
    Arshad

    Thanks...
    I am installing R1212 i did not find any userful info...
    I am trying disabling oom how to disable it in OEL 5.4 echo “0? > /proc/sys/vm/oom-kill (turn off) there is no such file....
    also i am tying couple of things like...
    # sysctl vm.lowmem_reserve_ratio
    vm.lowmem_reserve_ratio = 256 256 32
    Thanks for very quick reply... I hope it goes through this time..

  • Installing VMWare fails trying to MAKE vmmon module.

    Hey Arch users, thanks for reading.  I've tried this on two different machines now.  Both of which yield the same error.  I untar vmware like and run the vmware-install.py script after creating the rc0.d through rc6.d directories.  It works up to where it tells me there's no vmmon modules for Server that're suitable.  It then asks em if I want to have the script build them and well the rest is in between the code brackets:
    What is the location of the directory of C header files that match your running
    kernel? [/lib/modules/2.6.30-ARCH/build/include]
    Extracting the sources of the vmmon module.
    Building the vmmon module.
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config5/vmmon-only'
    make -C /lib/modules/2.6.30-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.30-ARCH'
    CC [M] /tmp/vmware-config5/vmmon-only/linux/driver.o
    In file included from /tmp/vmware-config5/vmmon-only/linux/driver.c:31:
    /tmp/vmware-config5/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait'
    include/linux/poll.h:67: note: previous declaration of 'poll_initwait' was here
    In file included from /tmp/vmware-config5/vmmon-only/./include/vmware.h:38,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:99:
    /tmp/vmware-config5/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/./include/vcpuset.h:103,
    from /tmp/vmware-config5/vmmon-only/./include/modulecall.h:37,
    from /tmp/vmware-config5/vmmon-only/./common/vmx86.h:33,
    from /tmp/vmware-config5/vmmon-only/linux/driver.h:29,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:101:
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:460:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:551:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:640:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:729:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:816:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:903:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:986:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1069:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1313:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86_64.h:39,
    from /tmp/vmware-config5/vmmon-only/./include/vm_asm.h:41,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:103:
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/./include/vm_asm.h:41,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:103:
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/linux/driver.c:119:
    /tmp/vmware-config5/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined
    /tmp/vmware-config5/vmmon-only/linux/driver.c: In function 'LinuxDriverSyncCallOnEachCPU':
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1423: error: too many arguments to function 'smp_call_function'
    /tmp/vmware-config5/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl':
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:2007: error: too many arguments to function 'smp_call_function'
    make[2]: *** [/tmp/vmware-config5/vmmon-only/linux/driver.o] Error 1
    make[1]: *** [_module_/tmp/vmware-config5/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.30-ARCH'
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-config5/vmmon-only'
    Unable to build the vmmon module.
    For more information on how to troubleshoot module-related problems, please
    visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and
    "http://www.vmware.com/go/unsup-linux-tools".
    Execution aborted.
    Now, I've tried the any-to-any patch, or at least the latest version I could find.  It gives me other similiar "________ is not defined" errors and still doesn't build.  I made sure that all three of the xlib files are up to date, as well as xinitd and base-devel and still I'm having this problem.  I frankly don't know where to go from here.  Is it something I've left out of ALL of my Arch installs?

    Hey Arch users, thanks for reading.  I've tried this on two different machines now.  Both of which yield the same error.  I untar vmware like and run the vmware-install.py script after creating the rc0.d through rc6.d directories.  It works up to where it tells me there's no vmmon modules for Server that're suitable.  It then asks em if I want to have the script build them and well the rest is in between the code brackets:
    What is the location of the directory of C header files that match your running
    kernel? [/lib/modules/2.6.30-ARCH/build/include]
    Extracting the sources of the vmmon module.
    Building the vmmon module.
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config5/vmmon-only'
    make -C /lib/modules/2.6.30-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.30-ARCH'
    CC [M] /tmp/vmware-config5/vmmon-only/linux/driver.o
    In file included from /tmp/vmware-config5/vmmon-only/linux/driver.c:31:
    /tmp/vmware-config5/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait'
    include/linux/poll.h:67: note: previous declaration of 'poll_initwait' was here
    In file included from /tmp/vmware-config5/vmmon-only/./include/vmware.h:38,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:99:
    /tmp/vmware-config5/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/./include/vcpuset.h:103,
    from /tmp/vmware-config5/vmmon-only/./include/modulecall.h:37,
    from /tmp/vmware-config5/vmmon-only/./common/vmx86.h:33,
    from /tmp/vmware-config5/vmmon-only/linux/driver.h:29,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:101:
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:460:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:551:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:640:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:729:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:816:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:903:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:986:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1069:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1313:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86_64.h:39,
    from /tmp/vmware-config5/vmmon-only/./include/vm_asm.h:41,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:103:
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/./include/vm_asm.h:41,
    from /tmp/vmware-config5/vmmon-only/linux/driver.c:103:
    /tmp/vmware-config5/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config5/vmmon-only/linux/driver.c:119:
    /tmp/vmware-config5/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined
    /tmp/vmware-config5/vmmon-only/linux/driver.c: In function 'LinuxDriverSyncCallOnEachCPU':
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1423: error: too many arguments to function 'smp_call_function'
    /tmp/vmware-config5/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl':
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid'
    /tmp/vmware-config5/vmmon-only/linux/driver.c:2007: error: too many arguments to function 'smp_call_function'
    make[2]: *** [/tmp/vmware-config5/vmmon-only/linux/driver.o] Error 1
    make[1]: *** [_module_/tmp/vmware-config5/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.30-ARCH'
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-config5/vmmon-only'
    Unable to build the vmmon module.
    For more information on how to troubleshoot module-related problems, please
    visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and
    "http://www.vmware.com/go/unsup-linux-tools".
    Execution aborted.
    Now, I've tried the any-to-any patch, or at least the latest version I could find.  It gives me other similiar "________ is not defined" errors and still doesn't build.  I made sure that all three of the xlib files are up to date, as well as xinitd and base-devel and still I'm having this problem.  I frankly don't know where to go from here.  Is it something I've left out of ALL of my Arch installs?

  • SIP ITSP on CUCM 10.5.2 (No CUBE) Incoming calls fail, outgoing are fine

    Hi,
    I am in the process of upgrading a customer who is on 8.0.3. They have an ITSP terminating SIP Trunk directly on the CCM Server
    I upgraded the system to 10.5.2. During cutover I was able to make outgoing calls but all incoming calls were failing.
    After reverting back to the old system, everything is working fine again, and I dont understand what could be the possible issue that it doesnt work on 10.5.2 but it works well on 8.0.3.
    I checked almost everything and dont find anything that stands out, which may be contributing to the issue.
    Any idea what could be missing here?
    Thanks

    Thanks for all your tips.
    It was turned out that, the URI was a FQDN and during the first install of the 8.0.3 (in the sandbox) I had not bothered to get the DNS Services replicated and then didnt check if the ITSP was sending the invite on URI based on FQDN or IP Address
    Thanks

  • CUCM 10 Install Subscriber Error

    Hi All,
    I have plan to install  CUCM 10 in 2 sites :
    - sites A : Publiser , Subscriber 1
    - sites B : Subscriber 2 , Subscriber 3
    When I Install in Sites A there is no problem , but when i Install in Sites B for Subscriber 2 and Subscriber 3 there is always this error :
    I had try using ova template from different sites and installer , but no result ,
    any help ?
    Best Regards,
    Tommy

    Hi Tommy,
    did you already upgrade to the fixed version on pub & sub 1 ?
    if you already upgrade from v10.0.1.10000-24 to v10.0.1.11006.1 on publisher & sub1, before you install subs 2 & 3, you must install first cucm v10.0.1.10000-24 and then you choose the patch menu when the starting CUCM installer. and then you put the ISO fixed version v10.0.1.11006.1 into DVD.
    some error interrupt when installing the secondary node on cucm because the primary node having 2 version active & incative CUCM after doing upgraded. you need make it same version on secondary node.
    you can contact me with YM : biemabbit
    to make sure this problem clearly :)
    Regards,
    Habibi

  • CUCM Upgrade to 9.1.2.13900-10

    Dear Team,
    I am planning to upgrade CUCM  from 9.1.2.10000-28   to  UCSInstall_UCOS_9.1.2.13900-10.sgn .
    Please share with me the upgradation steps and documents  ?
    Thanks

    Hi Waqas,
    please follow the steps for doing minor upgrade
    a. You need to take the backup of existing CUCM 9.1.2.10000-28
    b. After u download the patch, do verify the MD5 checksum.
    c.Upload first it in Publisher through OS administration: Software Upgrades--Install/upgrade
    d. Upload now in Subscriber.
    e. Switch over  to 9.1.2.13900-10  from CLI using command utils system  switch version
    f. follow the same for Subscriber as well.
    http://www.cisco.com/web/software/282074295/122683/cucm-readme-912su3.pdf
    regds,
    aman

  • CUCM 8 demo - there is no advance features VPN

    Hi,
    I have just installed
    CUCM_UNRST_8.6.2.10000-14 on VMWare
    Questions :
    - There is no advance features -> VPN
    is that something that not availabile on demo license ?
    Thanks

    Hi David,
    The newer versions of the Security guide do show this caveat/restriction
    Note The VPN menu and its options are not available in the U.S. export  unrestricted version of Cisco Unified Communications Manager. We see from above that you have installed the unrestricted version so this is why you are hitting this;
    CUCM_UNRST_8.6.2.10000-14
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/security/8_6_1/secugd/secuvpn.html
    Cheers!
    Rob
    "go easy...step lightly...stay free " 
    - The Clash

  • CUCM Upgrade to 10.5 from 8.5

    Just curious, has anybody ugraded their CallManager to 10.5 from 8.5 without using the Prime Collaboration Deployment tool.  I have uploaded the necessary cop files already and have been trying to figure out how to do the upgrade without PCD.  I know I will be asked why not use PCD.  Consultants we have talked to recommended not using PCD for various reasons, mainly lack of familiarity.  If anybody can give me some info on doing this upgrade, both with and without PCD, it would be appreciated.

    Junior,
    Good question! Below you will find a guide through I created for one of my customers:
    The actual upgrade process, you will need to upgrade to any 8.6(2) release first before going to 10.5 The link below lists the versions from which you can perform a direct upgrade:
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/10_x/CUCM_BK_CD1DB914_00_compat_matrix/CUCM_BK_CD1DB914_00_compat_matrix_chapter_01.html#CUCM_RF_U4CE0DAF_00
    Also, there is a documentation defect that talks about this, see below:
    https://tools.cisco.com/bugsearch/bug/CSCus62385/?reffering_site=dumpcr
    Having mentioned this, the plan should be as follows:
    1) Install "ciscocm.refresh_upgrade_v1.5.cop.sgn" on all nodes (Starting with the Publisher then, the remaining nodes).
    2) Backup current CUCM version the system is running.
    3) Upgrade current CUCM version to any 8.6(2) version.
    4) Install "ciscocm.version3-keys.cop.sgn" on all nodes (Starting with the Publisher then, the remaining nodes).
    5) Install UCOS_10.5.2.10000-5.sgn (on the inactive partition) (Starting with the Publisher then, the remaining nodes).
    6) Perform "switch version" starting with the Publisher server. (Starting with the Publisher then, the remaining nodes).
    7) Verify cluster replication is good on all nodes once all servers are in CUCM 10.5.2.10000-5.
    8) Perform a backup of the system.
    9) Download and deploy OVA template "cucm_10.5_vmv8_v1.8.ova" (from Cisco's website) to create new VM's for the cluster.
    10) Re-Install CUCM 10.5.2.10000-5 cluster in the newly deployed VM's created using the correct OVA template.
    11) Perform a restore on 10.5.2.10000-5 from previous backup taken on step 8.
    Since you are upgrading from a non 10.X version, once you upgrade to this version you will get "partitions un-alingned" error because hardware requirements are different for CUCM 8.6 and CUCM 10.5. This is explained on the following document:
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_2/CUCM_BK_C9FFFCD0_00_cucm-release-notes-912/CUCM_BK_C9FFFCD0_00_cucm-release-notes-912_chapter_011.html#CUCM_RF_C48E7BDE_00
    That's the reason why I added Step 9, 10 and 11 to this plan.
    Hope this information helps,
    Regards,
    Marco Rojas

  • CUCM 8.6.2 to 9.1.2 Upgrade fails

    I am trying to complete an upgrade of CUCM 8.6.2 to 9.1.2 however the upgrade fails at the very end - I have attempted this 4 times in various different ways from using SFTP to local media I get the following error;
    HWModel=7835I3
    CPUCount=1
    CPUType= Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
    CPUSpeed=2000
    MEMSize=4096
    BIOSVer=IBMCorp. -[D6E150CUS-1.11]- 02/08/2011
    ObjectId=1.3.6.1.4.1.9.1.585
    OSVersion=UCOS 5.0.0.0-2
    SerialNumber= ********
    VendorOID=1.3.6.1.4.1.2]|<LVL::Info>
    05/17/2014 13:54:49 upgrade_install.sh|Cleaning up download...|<LVL::Info>
    05/17/2014 13:54:49 upgrade_install.sh|Cleanup upgrade source area.|<LVL::Info>
    05/17/2014 13:54:49 upgrade_install.sh|Ejecting DVD (/dev/sda1)|<LVL::Debug>
    05/17/2014 13:54:51 upgrade_install.sh|Removing /common/download/9.1.2.10000-28>
    05/17/2014 13:54:51 upgrade_install.sh|Started auditd...|<LVL::Info>
    05/17/2014 13:54:52 upgrade_install.sh|Started setroubleshoot...|<LVL::Info>
    05/17/2014 13:54:52 upgrade_install.sh|Changed selinux mode to enforcing|<LVL::>
    05/17/2014 13:54:52 upgrade_install.sh|Cleaning up rpm_archive...|<LVL::Info>
    05/17/2014 13:54:52 upgrade_install.sh|Removing /common/rpm-archive/9.1.2.10000>
    05/17/2014 13:55:02 upgrade_install.sh|File:/usr/local/bin/base_scripts/upgrade>
    05/17/2014 13:55:02 upgrade_install.sh|set_upgrade_result: set to 1|<LVL::Debug>
    05/17/2014 13:55:02 upgrade_install.sh|is_upgrade_lock_available: Upgrade lock >
    05/17/2014 13:55:02 upgrade_install.sh|is_upgrade_in_progress: Already locked b>
    05/17/2014 13:55:02 upgrade_install.sh|release_upgrade_lock: Releasing lock (pi>
    Installation of UCSInstall_UCOS_9.1.2.10000-28.sgn.iso failed
    An unknown error occurred while accessing the upgrade file.
    A system reboot is required when the upgrade process completes or is canceled. .
    I have previously used this ISO for other clients without an issue and have checked the MD5 is correct
    Has anyone else experienced this issue?
    Thanks,
    Richard

    We have got this resolved, after raising a case with TAC they identified that we were hitting the following bug;
    CSCub53409
    The detail on the bug is very limited but in our case it was caused by an issue with the numbering plan, GBNB 1.1(21) - we upgraded to the latest version 1.1(29) and the upgrade has now completed.

  • CUCM 10 Barge/CBarge with shared line between phone and a remote device

    Is it possible to configure CBARGE/BARGE feature if shared line is between a cisco phone and a remote device.
    When remote device picks up the phone, red light comes up on the phone, if we press the line button to Cbarge, dial tone comes up and the call does not go into a conference.
    Has anyone used that feature? Can it be configured?

    We are using Lync for tesing purposes.
    we tried scenario with Remote device as a mobile phone.  Where calls are being sent through SIP trunk to CUBE and then to our provider. Maybe I should add some commands on CUBE router?
    Is that feature (CBARGE) designed to work in that scenario when shared line is answered via remote device on CUCM 10.5.1.10000-7.  I am suspecting that its not designed to work that way (If its designed to work that way, we will continue on with collecting traces, etc). 

  • CUCM upgrade from 6.1(2) to 6.1(3b) - rollback problems...

    Hi all,
    I have upgraded our test lab CUCM server from 6.1(2) to 6.1(3b). Although we have a genuine MCS server bought from Cisco, we run only the demo licencing on the server (simply because we only have a few test phones and gateways running on the server).  We have rebuilt this server a few times so we may have had more licences installed previously - the 'demo' licencing seems to allow me test all i need to.
    The upgrade to 6.1(3b) seemed to go ok.   My only concern was the time it took after the CUCM server restarted for the IP phones to 'register' - seemed to take 30 mins or more before they jumped into life and re-registered etc?  Is that normal?  (I suspect the CallManager Service took a while to start?)
    However, I have had a few problems when trying to rollback the upgrade to the older partition. I followed the Cisco doco and all seemed to work ok, the CLI showed it selecting the old partition on the reboot, and then starting services for 6.1(2) [lots of green [OK] messages etc)
    Upon the full restart of the server, i noticed that the CallManager Service and the Cisco Messaging Service were NOT running!   I tried all i could think of to get these to restart:Went to Service Activation – stopped and restarted the CallManager service and the other one.  Then went back to Feature Services. CallManager was ‘running’ then after i refresh the page it reverts to ‘Not Running’ !   IP Phones therefore do NOT register.
    Tried a restart of the server (same partition) - Watching CLI during reboot – all green [OK] messages. No errors reported that i can see. IP phones still dont register when server restarts. The two services remain 'Not Running'
    I then restarted using 'switch' and ran the upgraded CUCM version - this started fine, and all ran ok!  Phones regsitered, all seems fine!
    I have attached a few screenshots, not sure if they are relevant or of any use.
    Has anyone seen this issue before after an upgrade?  I am not overly comcerned becaue the 'upgrade' worked, but it would be nice to know i can rollback if i need to do incase of any issues.
    Is there anywhere in CUCM i can check to see if the failed services are generating an error message or a reason for them not starting?
    Thoughts appreciated
    Rgds

    Hey Andy,
    Hope all is well buddy!
    The problems you are seeing here are most likely "purely" License related due to the changes
    that were implemented between 6.1(2) and 6.1(3). I don't see this being a problem with permanent
    "production" Licenses. Have a look;
    Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) introduce these licensing enhancements.
    Description
    Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) identify the state of a license; that is, if it is missing, if it is a demo license, or if it is an uploaded license. In addition, Cisco Unified Communications Manager Administration warns you whether Cisco Unified Communications Manager currently operates with demo licenses, with an insufficient number of licenses, or with an incorrect software feature license.
    GUI Changes
    The following windows display the state of licenses in Cisco Unified Communications Manager
    Administration:
    - Cisco Unified Communications Manager currently operates with demo licenses, so upload the appropriate license files.
    - Cisco Unified Communications Manager currently operates with an insufficient number of licenses, so upload additional license files.
    - Cisco Unified Communications Manager does not currently use the correct software feature license. In this case, the Cisco CallManager service stops and does not start until you upload
    the appropriate software version license and restart the Cisco CallManager service.
    License File Upload (System > Licensing > License File Upload)-This window displays a message
    that uploading the license file removes the demo licenses for the feature.
    http://www.aironet.info/en/US/docs/voice_ip_comm/cucm/rel_notes/6_1_3/cucm-rel_note-613a.html#wp472518
    Now for the Cisco Messaging Service
    This is only used in "Legacy" integrations which I'm guessing is not
    the setup for your lab, so you should be good to go here.
    Cisco Messaging Interface Service
    The Cisco Messaging Interface allows you to connect a simplified message desk interface (SMDI)-compliant external **Third Party** voice-mail system with the Cisco CallManager. The CMI service provides the communication between the voice-mail system and Cisco CallManager. The SMDI defines a way for a phone system to provide a voice-mail system with the information needed to intelligently process incoming calls.
    Hope this helps!
    Rob
    Please support CSC Helps Haiti
    https://supportforums.cisco.com/docs/DOC-8895
    https://supportforums.cisco.com/docs/DOC-8727

  • Rtmt error exception in publish content on Critical Services cucm

    Hi everybody, i have a problem with RTMT version 8.7 over CUCM 8.5.1.10000, when i try see the Critical Services of my cluster, i see a error "Exception in publish content", and it not show my service list, another functions of my RTMT have not any problem, only this. i attach an image.
    Can  anybody help to me or suggest what is the problem.
    Thanks for advanced.

    i found the problem just now, this occurs when you have a mixed cluster UCS/MCS, the reference of this bug is presented in the next link,
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCty47592
    this was fixed in the release  8.6(2.23061.1) and up.

Maybe you are looking for