DX Unified Infrastructure Management

  • 1.  error while  deploying vmware probe

    Broadcom Employee
    Posted Mar 16, 2018 09:05 AM

    I am getting following error while deploying vmware probe.Any clues  or known solution would be helpful.

     

    Mar 15 02:51:43:609 [pool-5-thread-1, mon_config_service] NimsoftProbeDeployer.deployProfiles:273: Received status (1) on response (for sendRcv) for cmd = 'probe_config_set'
    (1) error, Received status (1) on response (for sendRcv) for cmd = 'probe_config_set'
    at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:615)
    at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:561)
    at com.nimsoft.nimbus.NimClientSession.send(NimClientSession.java:170)
    at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:263)
    at com.nimsoft.nimbus.pool.NimRequestPool.sendImpersonate(NimRequestPool.java:92)
    at com.nimsoft.nimbus.pool.NimRequestPool.sendImpersonate(NimRequestPool.java:74)
    at com.nimsoft.nimbus.pool.NimRequestPool.send(NimRequestPool.java:66)
    at com.ca.uim.mcs.nimbus.McsNimRequestPool.send(McsNimRequestPool.java:48)
    at com.ca.uim.mcs.nimbus.RetryNimRequest.send(RetryNimRequest.java:36)
    at com.ca.uim.mcs.nimbus.RetryNimRequest.retryOnCommSessionError(RetryNimRequest.java:117)
    at com.ca.uim.mcs.nimbus.RetryNimRequest.send(RetryNimRequest.java:38)
    at com.ca.uim.mcs.probe.deployment.DefaultProbeConfigApplier.deployPdsUsingConfigSet(DefaultProbeConfigApplier.java:179)
    at com.ca.uim.mcs.probe.deployment.DefaultProbeConfigApplier.apply(DefaultProbeConfigApplier.java:57)
    at com.nimsoft.selfservice.v2.deployer.NimsoftProbeDeployer.deployToRobot(NimsoftProbeDeployer.java:503)
    at com.nimsoft.selfservice.v2.deployer.NimsoftProbeDeployer.deployToRobot(NimsoftProbeDeployer.java:520)
    at com.nimsoft.selfservice.v2.deployer.NimsoftProbeDeployer.deployProfiles(NimsoftProbeDeployer.java:260)
    at com.nimsoft.selfservice.v2.deployer.NimsoftProbeDeployer.deploy(NimsoftProbeDeployer.java:239)
    at com.nimsoft.selfservice.v2.deployer.NimsoftProbeDeployer.deploy(NimsoftProbeDeployer.java:216)
    at com.nimsoft.selfservice.v2.controller.ProfileController.doDeployProfile(ProfileController.java:888)
    at com.nimsoft.selfservice.v2.controller.ProfileController.deployProfileNow(ProfileController.java:455)
    at com.nimsoft.selfservice.util.DeployProfileTask.run(DeployProfileTask.java:52)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

     



  • 2.  Re: error while  deploying vmware probe

    Broadcom Employee
    Posted Mar 16, 2018 09:30 AM

    I would suggest you open a case with support on this.

    Are you trying to deploy using MCS?

    Or are you deploying manually?

    We need a little more information to help



  • 3.  Re: error while  deploying vmware probe

    Broadcom Employee
    Posted Mar 16, 2018 09:35 AM

    I am trying to deploy through UMP using MCS.The status of deployment is always new and not deployed with the below error in UMP

     

     Received status (1) on response (for sendRcv) for cmd = 'probe_config_set'



  • 4.  Re: error while  deploying vmware probe

    Broadcom Employee
    Posted Mar 16, 2018 09:52 AM

    I would make sure all your hubs re running 7.93

    with the prescribed setting in the following KB.

    UIM hub tunnel disconnects after a very short time - CA Knowledge 

    hub and tunnel connection settings in 7.x and 8.x - CA Knowledge 

     

    make sure the target robot is running 7.93

    and make sure all the pre-requisites for Vmware are met on the robot.

    vmware (VMware Monitoring) Release Notes - CA Unified Infrastructure Management Probes - CA Technologies Documentation 

     

    If that does not help resolve the issue please open a case with support as they will need to dig in deeper to your logs that is really feasible on the forums.