controller IM Configuration
The article describes the Infrastructure Manager controller configuration UI. It provides information about advanced configuration options. To open the UI, double-click the controller probe in Infrastructure Manager.
The article describes the Infrastructure Manager controller configuration UI. It provides information about advanced configuration options. To open the UI, double-click the controller probe in Infrastructure Manager. For an overview, see controller.
Set up the robot and a secondary failover hub in the
The tab contains two sections:
- Robot Name- attaches to the parent hub when the hub is active.If theSearch the subnet for a temporary huboption is selected, this option changes to theAutomatically detectoption.
- Automatically detect (searches the subnet)- the robot searches the subnet for a responding hub within the domain when the parent and secondary hubs are unavailable.This option is displayed if theSearch the subnet for a temporary huboption is selected.
- Specify Hub (IP/name)- The robot attaches to the hub specified by IP address or hostname.
- Specify Hub (domain name)- The robot attaches to the hub within the specified CA UIM domain.
- Search the subnet for a temporary hub when primary and secondary hubs are unavailable- If the parent and secondary hubs are unavailable, the robot searches the subnet for a failover hub.
Selecting this option changes the
Wait for the primary hub to become availableoption to the
Automatically detect (searches the subnet)option.
For 9.10S, the following changes are applicable in the
- In theSecondary HUBsection, theAutomatically detect (searches the subnet)option is not available.
- In theSecondary HUBsection, theSearch the subnet for a temporary hub when primary and secondary hubs are unavailableoption is not available.
For more information about how to upgrade to secure hub and robot, see Secure Hub and Robot in CA UIM DocOps.
Misctab to set logging information, identification properties, quality of service, and the robot interaction mode.
- Identification properties- specifyUser tag 1andUser tag 2.User tags are user-defined tags that are used as a grouping and locating mechanism. The tags display in various lists in Infrastructure Manager.
- Log Level- set the amount of detail to be logged to the log file. Log as little as possible during normal operation to reduce disk consumption. Increase the level of detail when you are debugging.
- Log Size- change the maximum size of the log file. The default size of the log file is 1024 KB.
- Hub update interval- the interval, in minutes, that the hub is contacted with analivemessage. The range is 1 through 180 minutes. The hub is notified at a shorter interval when changes occur in the probe list.
- Quality of Service
- On Robot uptime, reported as state change- sends QoS messages for robot uptime. The QoS messagestatus = upis sent when the robot starts, andstatus = downis sent when the robot stops.
- Set QoS source to robot name instead of computer hostname- use the robot name that is specified on theSetup, Nimsofttab.This option is disabled unless theSet specific name (override)option is selected on theSetup, Basictab.
- Robot mode- select Normal or Passive. Passive robots do not initiate the communication with a hub. The hub initiates all contact with the robot.
Advancedtab to set robot options, and the data origin.
- Robot options- set options for the robot:
- Automatically unregister from HUB at shutdownWhen the robot is stopped, an unregister message is sent to the hub on which it is registered. The robot disappears from Infrastructure Manager. If this option is not selected, the robot appears with a red icon, enabling the operator to detect the situation.
- Suspend all probes when no network connection is availableWhen the robot does not have a network connection, specify whether the robot is in active mode or sleep mode. In sleep mode, all probes are suspended when a network connection is not available. If this option is not selected, the alarm messages are spooled and flushed when a network connection becomes available.
- First probe port numberDaemon type probes typically register a command port. The port is allocated at run time during probe startup. Setting the probe port number makes the robot allocate specific port numbers for the probes as they start. Use this option to allocate probe port numbers in a specific range for router and firewall purposes.
- Time offset from UTCUse this option to override the local time zone setting. Enter the time specification as a time offset from UTC in seconds.
- When no contact with hub- Anunmanagedrobot is a robot that has lost contact with the parent hub. This option sets limitations on attempts to connect to a hub, using theTools, Connect Robotoption in Infrastructure Manager.
- Data Origin (override origin set by the Hub)- Specify the Origin.The origin is a string that is attached to
The robot controller reads the variable, value pair in the list and inserts it into the robot environment. The probes inherit the environment from the robot.
You can add, edit, or delete environment variables. Right-click and select the appropriate menu option. Only add environment variables that all probes on the robot use.
The Netware probe is the only probe that can be set up on a virtual robot. The Netware probe has reached end of life.
The controller issues alarms for error conditions. The
Alarmstab lists the internal alarm messages. Select the severity level for each alarm message. You can select
no alarmfor the following conditions:
- Probe restart when the probe does not respond
- Timed probe did not return 0 on termination
- Probe distribution request error
- Distribution post-install error
Time interval at which alarms will be resent- the time interval in minutes between alarms which are sent for an error condition.
If this field is left blank, the controller does not resend the alarms.
Use the Network Address Translation (NAT) feature to allocate an external IP address to a robot. Use NAT when the network addresses of the hub and robot are incompatible.
If the robot and the hub are separated by a NAT device, the robot can send alarms and QoS messages, but the hub cannot respond. To solve the problem, set up static NAT mappings for each robot behind the NAT device. Use
Raw Configureto add the key
robotip_aliasto the controller section of the
robotfile on the robot.
robotip_aliassets the IP address that is registered when the robot connects to the hub.
robotip_aliasspecifies the static NAT to IP address mapping. The hub and the clients on the other side of the NAT device use the mapping to access the robot. For example:
<controller>robotip_alias = 126.96.36.199...<\controller>
IPtab to configure the IP information for the robot.
- Robot IP address:
- Automatically detectThe host IP address is used
- Set specific address(es) (override)Specify an IP address or set of IP addresses for the robot. An override is typically used when a host has more than one network interface.Separate multiple IP addresses with a comma. IP addresses can contain asterisk wildcards.Valid entries:
- The controller and the probes it starts only listen for connections on the NIC addressed by198.2.If there are no198.2addresses, the controller and the probes listen on188.8.131.52.
- IP version support- Select the IP version that you are using
- Local IP validation- When this option is enabled, and the robot IP address is not set tolocalhost, the robot IP address is checked against a list of known, valid IP addresses for that server before it is used.
- IP binding:
- Listen only on the first valid address from configured IP addressesThis option is available when an override robot IP address is specified. If servers have multiple NICs, the controller only listens on the specific IP address on servers with multiple NICs.
For 9.10S, the following change is applicable:
- In theIPtab, theIP bindingoption is not available.
For more information about how to upgrade to secure hub and robot, see Secure Hub and Robot in CA UIM DocOps.
Statustab displays a summary of robot properties, and indicates the status of the robot.
- Status indicator iconThe status indicator icon, together with a status message, gives information about the current controller status.
- Green - OK
- Red - error condition
Right-click the icon to suspend the robot for maintenance for a specified period.
- Installed packagesThe Installed Packages button lists all the packages that are installed on the robot.
- Robot environmentThe Robot Environment button displays the variables and values for the computer running the robot.Any probes that the robot starts inherit the environment.
- Hub connectivityDisplay the current, primary, and secondary hubs
Using DNS Names for the Hub Server in robot.cfg
Version 2.80 or higher of the controller, allows the DNS name of the hub server to be used in the
robot.cfgfile in two ways:
- use the full DNS name instead of the IP address in thehubipparameter
- use the full DNS name in thehub_dns_nameparameter
Use the full DNS name of the server as the
hubipparameter to allow the robot to recognize the main hub and return to it after a failover.
The robot move operation replaces the
hubipparameter with an IP address. If the DNS server is down, the robot can fail over to a different hub.
Use the full DNS name in the parameter
hub_dns_nameto allow the robot to use the
hub_dns_nameto look up the hub IP address. If the lookup fails, the
hubipparameter is used. When the DNS name lookup is successful, and the IP address is different from the
hubipparameter, the parameter is replaced.
The same functionality is available for the secondary hub, using the
hub_dns_nameis lost on a robot move.
secondary_hub_dns_nameis lost when the controller configuration tool changes the secondary hub. For example,
<controller> hubip = hub_dns_name = secondary_hub_dns_name =</controller>
Limiting the Number of Open Ports
proxy_modekey in the
robot.cfgto limit the number of open ports in the environment (for example, in a network with a firewall).
proxy_mode = 1to send all the traffic through a specific port, for example, port 48000.
Robot Maintenance Mode
Controller version 2.80 or higher supports
maintenance mode. Right-click one or more robots in the Infrastructure Manager main window and select
Maintenanceto put the selected robots into maintenance mode for the period specified.
The robot stops all probes and stops sending messages. The robot does a full restart, and only starts the core components (
proxy). Any other probes are suspended while the robot is in maintenance mode.
When the maintenance mode is invoked, supply the stop time for the maintenance mode. When the stop time is reached, the robot returns to normal operation. Any suspended probes are restarted.
Probe distribution and activation can be performed while the robot is in maintenance mode. When the maintenance mode is complete, the affected probes are started.