DX Unified Infrastructure Management

 View Only
  • 1.  Doamin name not picked while silent installtion on winodws robot

    Posted Sep 12, 2018 05:23 AM

    Hi,

     

    We are testing silent installation on windows server for uim 8.51.

    We followed following procedure as is present in below link:

    Deploy Robots in Bulk with a Third-Party Tool and Native Installers - CA Unified Infrastructure Management - 8.5.1 - CA … 

    We have mentioned domain name as per our environment.

    domain=UIM_domain_to_which_the_robot_will_belong

    hub=name_of_parent_hub

    hubip=parent_hub_IP_address

    hubrobotname=parent_hub_local_robot

    hubport=parent_hub_port_number

    After running the command as provided in the link, robot is installed but there is no data in robot.cfg file.

    And when we checked controller.log file it showed that installer was picking all data except domain .

    I took domain = none

    All ports are open(48000-50) between hub and robot and we tested this on 2 servers but we found same issue.

    What could be causing this behavior.

     

     

    Thanks

    Aditi



  • 2.  Re: Doamin name not picked while silent installtion on winodws robot

    Broadcom Employee
    Posted Sep 12, 2018 09:29 AM

    Was this a silent install on a Linux/UNIX system?  If so, did you execute the RobotConfigurer.sh script after completing the robot install itself?  This is the script that is supposed to configure the robot and is a manual step executed after executing the command to perform the installation of the robot files.



  • 3.  Re: Doamin name not picked while silent installtion on winodws robot

    Posted Sep 14, 2018 04:54 AM

    no Kathryn, this is for Windows robot



  • 4.  Re: Doamin name not picked while silent installtion on winodws robot

    Posted Sep 14, 2018 05:00 AM

    Hi kathryn ,

     

    I have one more question regarding robot ip.

    I tried silent installation on windows server , it executed but picked up the backup ip instead of the preferred one.

    Since we cant give IP in case of bulk deployement , what can be done to make sure correct ip is picked up by the robot ?

     

    Thanks

    Anmol



  • 5.  Re: Doamin name not picked while silent installtion on winodws robot

    Broadcom Employee
    Posted Sep 14, 2018 05:33 AM

    Asterisk can be used for robotip. (for example, robotip = 192.168.*.*)

    It might help to limit matching when primary ip scope and secondary ip scope can be differently definitive.



  • 6.  Re: Doamin name not picked while silent installtion on winodws robot

    Posted Sep 14, 2018 05:48 AM

    Hi Yu ,

     

    do you want me to hardcode robotip in answer file ?

     

    thanks



  • 7.  Re: Doamin name not picked while silent installtion on winodws robot

    Broadcom Employee
    Posted Sep 17, 2018 10:48 PM

    Thank you for response. Yes. You can limit ip range.



  • 8.  Re: Doamin name not picked while silent installtion on winodws robot

    Posted Sep 17, 2018 06:45 AM

    - How did you start the silent installation?

    - Where did you store/copy: nms-robot-vars.cfg and nimsoft-robot-x64.exe 

    - Do you see any log file on the target machine?



  • 9.  Re: Doamin name not picked while silent installtion on winodws robot

    Broadcom Employee
    Posted Sep 18, 2018 03:54 AM

    Thank you for script posting. Very useful.

    Windows robot installation script example 



  • 10.  Re: Doamin name not picked while silent installtion on winodws robot
    Best Answer

    Posted Sep 18, 2018 05:08 AM

    hi chrlu, the issue got resolved, in answer file we found some spaces which might b creating the issue,once spaces was removed , domain name got populated while installing again.