v7.7 controller IM Configuration
This article describes the Infrastructure Manager controller configuration GUI and provides information on advanced configuration. To open the GUI, double-click the controller probe in the Infrastructure Manager. For an overview of the probe, see .
This article describes the Infrastructure Manager controller configuration GUI and provides information on advanced configuration. To open the GUI, double-click the controller probe in the Infrastructure Manager. For an overview of the probe, see controller.
See the following topics for details:
Setuptab contains the following sections:
Nimsofttab allows you to set up the robot and a secondary hub.
The tab contains two sections:
- Robot Name
- Automatically detectuses the system host name as the robot name.
- Set specific name (override)lets you specify the robot name to be used.
- Secondary HUBdefines the method used to determine the secondary hub. The secondary hub will be used if the primary hub is unavailable. Options are:
- Wait for primary hub to become availableprevents the robot from attaching to another hub. It will attach to its parent hub when the hub is active.This option is replaced by theAutomatically detectoption if theSearch the subnet for a temporary huboption is selected.
- Automatically detect (searches the subnet)allows the robot to search the subnet for a responding hub within the domain when the parent and secondary hubs are unavailable.Note: This option is displayed if theSearch the subnet for a temporary huboption is selected.
- Specify Hub (IP/name)allows the robot to attach to the specified hub.
- Specify Hub (domain name)allows the robot to attach to the specified hub.
- Search the subnet for a temporary hub when primary and secondary hubs are unavailableallows the robot to search for a temporary hub if the parent and secondary hubs are unavailable. Selecting this option changes theWait for the primary hub to become availableoption toAutomatically detect (searches the subnet)option.
Misctab allows you to set logging information, identification properties, quality of service and robot interaction mode.
- Identification propertieslets you specifyUser tag 1andUser tag 2, which are user-defined tags to be used as a grouping/locating mechanism. The tags are displayed in various lists in Infrastructure Manager.
- Log Levelsets the amount of detail to be logged to the log file. Log as little as possible during normal operation to reduce disk consumption, and increase the level of detail when debugging.
- Log Sizeallows you to change the size of the log file according to your needs. The default size of the log file is 1024 KB.
- Hub update Intervaldetermines at what interval the hub is contacted with an "alive" message. The range is 1 to 180 minutes. Note that the hub is notified at a shorter interval when changes occur in the probe list.
- Quality of Service:
- On Robot uptime, reported as state changesends QoS messages on robot uptime. The QoS messagestatus = upis sent when the robot starts;status downis sent when the robot stops.
- Set QoS source to robot name instead of computer hostnameuses the robot name specified on the Setup > Nimsoft tab.This option is disabled unless theSet specific name (override)option is selected on the Setup > Nimsoft tab.
- Robot modeis normal or passive. Passive robots cannot initiate communication with a hub. All contact must be initiated by the hub.
The Advanced tab allows you to set robot options and the data origin.
- Robot optionsallows you to 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. This will make the robot disappear from Infrastructure Manager. If this is not selected, the stopped robot will appear with a red icon, enabling the operator to detect the situation.
- Suspend all probes when no network connection is availableWhen running the robot on a computer with no network connection, you can determine whether the robot should be active or enter a sleep mode where all probes are suspended until a network connection is again available. If this option is not selected the alarm messages will be spooled and flushed when a network connection is again available.This function is available only on Windows platforms.
- First probe port numberDaemon type probes will normally register a command port, which is allocated run-time on probe start-up. Setting the probe port number will make the robot allocate specific port numbers for the probes as they are started. Use this option if you want the probes to have port numbers in a specific range for router / firewall purposes.
- Time offset from UTCThis option lets you override the local time zone setting. The time specification must be entered as time offset from UTC (in seconds).
- When no contact with hubsets limitations for attempts to connect an unmanaged robot (a robot that has lost the contact with it’s hub) to a hub, using theTools > Connect Robotoption in Infrastructure Manager. The options are:
- Do not allow robot to be moved
- Allow move only within domain
- Data Origin (override origin set by the Hub)lets you specify theOrigin, which is a string attached to
The robot controller will read the variable/value pair in the list and insert it into the robot environment. This environment is inherited by the probes managed by the robot.
You can add, edit or delete these environment variables by right-clicking in the screen and selecting the appropriate menu option. Only add environment variables that you want all probes on this robot to use.
This tab lists
virtual robotsserved by the robot controller. The netware probe is the only probe that can be set up on a virtual robot.
Virtual robots will, via the
proxyprobe, be created for ‘remote’ probes (probes installed and running on computers without a robot). The ‘remote’ probe is configured to know which robot to be served by.
In Infrastructure Manager, the ‘remote’ probe will appear as a probe on a virtual robot.
To add user tags for a virtual robot:
- Select the hub in Infrastructure Manager, and the robots will be listed in the Main Window.TheVersioncolumn will notify if it is a virtual robot or not.In the example below, lab 5 isvirtualon xpkost, which means that the robot xpkost serves the virtual robot lab 5.
- Right-click the xpkost robot in the Navigation Pane and select Properties to bring up the controller configuration tool.Now you may select theSetup > Virtualtab, right-click and define user tags for the virtual robot.
This tab contains the internal alarm messages issued by the controller on the different error situations that may occur. You are allowed to select the severity level for each alarm message. For the condition ‘Probe restart when the probe does not respond’, you can also select that no alarm message is issued.
The option ‘Time interval at which alarms will be resent’ defines the time interval in minutes between alarms being sent on an error condition.
If this field is left blank, the controller will never attempt to resend the alarms.
The feature allows you to allocate an external IP address to a robot that resides on another IP network with incompatible addressing.
This tab contains the setup for NAT (Network Address Translation).
If the robot is separated from the hub by a NAT (Network Address Translation) device, the robot will be able to send alarms and QoS messages, but the hub will be unable to communicate back. One solution is to setup static NAT mappings for each robot behind the NAT device. Using Raw Configure, you can then add the key
robotip_aliasto the controller section of the
robot.cfgfile on the robot computer. This key changes the IP address that gets registered when the robot initially connects to the hub.
robotip_aliasshould specify the static NAT mapping IP address that the hub and the clients on the other side of the NAT device should use to access the robot. For example:
<controller>robotip_alias = 188.8.131.52...<\controller>
The IP tab allows you to configure the IP information for this robot.
- Robot IP-address:
- Automatically detectThe host IP address will be used.
- Set specific address(es) (override)Specify an IP-address or set of IP-addresses for the robot. This is typically used when a host has more than one network interface.For more than one IP-address, the addresses must be separated by a comma. IP addresses can also contain wildcards (*).Valid entries:
- 184.108.40.206, 220.127.116.11
- 198.2.*.*, 18.104.22.168
- IP version support– Select the appropriate IP version you are running.
- Local IP validation– With this option enabled, if the robot IP address is not set to localhost, it is checked against a list of IP addresses that are known valid for that server before it is used.
- Listen only on the first valid address from configured IP addressesYou can only select this option if you set a specific address in the Robot IP-address section of this screen. The controller will only list ON a specific IP address on servers with multiple NICs.
This section describes the properties for the Status tab.
- Robot nameThe actual/current name of the robot.
- Robot IP-addr.The actual/current ip-address of the robot.
- Robot versionThe version of the robot.
- Op. Sys.Operating system name.
- Op. Sys. typeThe type of the operating system (UNIX/Windows etc.).
- Op. Sys descrOperating system description.
- Indicator and status informationThe status indicator will, together with a status message, give information about the current controller status (Green icon means OK, Red icon means an error situation).Right-clicking on the indicator lets you set the robot into maintenance mode for the period specified. See the section for more information.
- Installed packagesLists all packages installed on the robot in a separate window.
- Robot environmentOpens the Robot Environment window. This window displays the variables and values for the computer running the robot.The values are inherited by any probe started by this robot.
- Hub connectivityDisplays the current, primary and secondary hubs.
Using DNS Names for the Hub Computer in robot.cfg
Version 2.80 or higher of the probe allows the DNS name of the hub machine to be used in the
robot.cfgfile in two ways: using the full DNS name instead of the IP address in the hubip parameter or using the full DNS name in the hub_dns_name parameter.
Using the full DNS name of the computer instead of the IP address (as the
hubipparameter) allows the robot to recognize its main hub and return to it after a failover situation.
The hubip parameter will be replaced by an IP address on a robot move operation. The robot can fail over to a different hub if the DNS is down.
Using the full DNS name in the parameter hub_dns_name allows the robot to attempt to use the hub_dns_name to look up the hub IP address. If this fails, the hubip parameter is used. When the DNS name lookup is successful and the ip address found is different from the hubip parameter, this parameter is replaced.
The same functionality is available for the secondary hub, using the secondary_hub_dns_name parameter.
Note that the hub_dns_name is lost on robot move and secondary_hub_dns_name is lost on change of secondary hub initiated by the controller configuration tool.
<controller> hubip = hub_dns_name = secondary_hub_dns_name =</controller>
Limiting the Number of Open Ports
You can limit the number of open ports in your environment (for example, in a network with a firewall) by setting the
proxy_modekey in the
In the robot.cfg, set the
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-clicking one or more robots in the Infrastructure Manager main window pane and selecting
Maintenance,lets you set the selected robot (s) into maintenance mode for the period specified.
The robot will stop all probes and stop sending messages. The robot does a full restart and only starts the core components (
proxy). In Infrastructure Manager the probe icon of other probes will indicate that these probes are suspended while the robot is in maintenance mode.
On entering maintenance mode, the end time of the maintenance mode period must be given. When this time is reached the robot will go back to normal operation and start up any suspended probes.
Probe distribution and activation can be performed while the robot is in maintenance mode, however the affected probes will be suspended and not actually started.