Robot Installation Error

Document ID : KB000033997
Last Modified Date : 14/02/2018
Show Technical Document Details
The answer file used contained the following:
<controller>
?? domain = NIMSOFTdom
?? hubip = 1.8.1.1
?? hub = NIMSOFThub
?? hubrobotname = NIMSOFT
?? hubport = 48002
?? first_probe_port =
?? secondary_domain =
?? secondary_hub =
?? secondary_hubrobotname =
?? secondary_hubip =
?? secondary_hubport =
?? secondary_hub_dns_name =
?? secondary_robotip_alias =
?? robot_mode =
?? robotname =
?? robotip =
?? robotip_alias =
?? controller_port =
?? spooler_port =
?? hubdomain =
?? os_user1 =
?? os_user2 =
?? set_qos_source =
?? system_uptime_qos =
?? autoremove =
?? default_priority_level =
?? proxy_mode =
?? proxy_log =
?? hub_update_interval =
?? loglevel =
?? logsize =
?? logfile =
?? config_lock_timeout =
?? port_alive_check =
?? port_alive_include_local =
?? startup_timeout =
?? suspend_on_loopback_only =
?? temporary_hub_broadcast =
?? do_not_broadcast =
?? unmanaged_security =
?? send_alive =
?? alarm_level_comfail_restart =
?? alarm_level_dispatch_error =
?? alarm_level_max_restarts =
?? alarm_level_start_error =
?? alarm_level_suspended =
?? alarm_level_timed_not_finished =
?? alarm_level_timed_error_return =
?? alarm_level_unregister =
?? alarm_level_request_error =
?? alarm_level_postinstall =
?? audit =
?? audit_max_config_size =
?? audit_checkpoint_count =
?? alarm_timeout =
?? wait_after_unregister =
?? tz_offset =
?? config_locking =
?? capture_output =
?? default_fail_window =
?? max_restarts =
?? ip_version =
?? access_0 = 0
?? access_1 = 1
?? access_2 = 2
?? access_3 = 3
?? access_4 = 4
?? <environment>
????? NIM_JRE_HOME = jre/jre7
????? NIM_JRE_HOME_1_7 = jre/jre7
?? </environment>
</controller>

The robot.cfg file generated after the install completed was as follows:

<controller>
?? access_0 = 0
?? access_1 = 1
?? access_2 = 2
?? access_3 = 3
?? access_4 = 4
?? domain = NOC
?? hub = DQR
?? hubrobotname = app
?? hubip = 1.8.1.5
?? hubport = 48002
</controller>

You cannot use a current robot.cfg file with modifications for the nms-robot-vars.cfg answer file used for third party/Native robot installations.? The robot.cfg file contains section tags:

<controller>
</controller>
<environment>
</environment>

and fields which are not interpreted correctly by the installer.? This causes it to bypass any settings that are defined in the answer file and will result in unexpected robot configuration settings.

The answer file must be a text file that follows the following syntax and format. Replace all text in brackets with actual values and do not include spaces between the parameter and value (for example, domain=UIMdomain).
?
domain=<domain_to_which_the_robot_will_belong>hub=<name_of_desired_parent_hub>hubip=<parent_hub_IP_address>hubrobotname=<parent_hub_local_robot>hubport=<parent_hub_port_number>(optional fields)Other guidelines for the content of the answer file are:
  • There should be no spaces between the field name and value
  • You must specify the?domain,?hub,?hubip,?hubrobotname, and?hubport.
  • Optional parameters with no answer are valid. However, it is better to omit a parameter from the answer file rather than include it with an empty setting.
  • The default port for a hub is 48002.
  • A best practice is to prepare a simple answer file with only?required?fields during initial robot deployment, and add optional fields later. Bulk changes to robot configuration are quickly accomplished using drag and drop in Infrastructure Manager.
  • Any robot attribute can be configured in the answer file by following the format parameter=<value>. For a complete list of robot parameters, see the?Robot Attribute Reference.? Only robot parameters in this list can be included in the answer file.