v7.7 controller AC Configuration
This section describes the configuration information and options available through the Admin Console controller configuration GUI. For an overview of the probe, see controller. The navigation pane organizes configuration into the following nodes:
To access the controller configuration interface, select the robot in the Admin Console navigation pane. In the Probes list, click the arrow to the left of the controller probe and select Configure.
Controllernode lets you view information about the hub and adjust log file settings.
- Probe Information(read only) provides the probe name, start time, version, and vendor.
- Hub Connectivity(read only) provides the name of the hub, the names of the primary (parent) hub and secondary hub that this hub's robots will attach to during failover.
- General Configurationlets you configure the following items.
- Identification property User Tag 1andIdentification property User Tag 2:User tagsare optional values that can be attached to probe-generated messages to control access to the data in USM. On a robot system, user tags are specified in robot.cfg. As of hub v7.70, user tags on a hub system are specified in hub.cfg, and user tags defined in robot.cfg are ignored. Prior to hub v7.70, user tags on a hub system were read from robot.cfg. Default:blank
- Log Level:Sets 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. Default:0 - Fatal
- Log Size (KB):Allows you to change the size of the log file according to your needs. When the log file size is reached, new entries are added and the oldest log file entries will be deleted. Default:1024 KB
- Hub update interval (minutes):Determines at what interval the hub is contacted with an "alive" message. The range is 1 to 180 minutes. Note that the hub is notified on a shorter interval when changes occur in the probe list.
- On Robot uptime, reported as state changes:If this option is selected, QoS messages on robot uptime will be sent. 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 host name:Select this option to use the robot name for the QoS source when sending alarms. By default, the host name of the computer hosting the probe is used as the QoS source. Default:Disabled
- Statusprovides the status of the robot and is read-only.
controller > Setupnode lets you view and modify robot configuration settings.
- Nimsoftlets you specify:
- Robot Name:The default name is the computer host name, and is auto-detected by default (recommended). Default: Auto Detect (recommended).
- Secondary Hub Robot Name:Defines the method used to locate a temporary parent hub if the robot's own parent hub is unavailable. By default, the robot will auto-detect the nearest active hub (recommended).Search the subnet for a temporary hub when primary and secondary hubs are unavailable:Select this option to enable the robot process and port controller to search the internet for a temporary hub. Default: not selected.
- Advancedlets you specify:
- Automatically unregister from hub at shutdown:When 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 available:When 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. Default: selected (recommended).This function is available only on Windows platforms.
- Configuration file locking:Locks the configuration.
- First Probe port number:Daemon type probes normally register a command port, which is allocated run-time on probe start-up. Setting the probe port number makes 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 or firewall purposes.
- Time offset from UTC (override the local time zone setting) sec:Overrides the local time zone setting. The time specification must be entered as time offset from UTC (in seconds).
- When no contact with hub:Set limitations for attempts to connect an unmanaged robot (a robot that has lost the contact with the hub) to a hub.Default: Allow move only within domain (recommended)
- Environment Variables
- Variable Name:Environment variable for your UIM system. This variable is inherited by all the probes managed by this robot.
- Variable Value:The value assigned to the variable name.
- Probe restart when the probe does not respond:Select the alarm to be sent when a probe is not responding and is restarted.
- Dispatch error (internal):Select the alarm to be sent when there is a dispatch error for the probe.
- Max restart attempts reached for the probe:Select the alarm to be sent when the maximum restart attempts have been reached.
- Error starting probe:Select the alarm to be sent when there is an error starting the probe.
- Timed probe did not return 0 on termination:Select the alarm to be sent when the probe does not return a value of 0.
- Probe unregisters port but keeps running:Select the alarm to be sent when the probe unregisters the port but continues to run.
- Probe distribution request error:Select the alarm to be sent when there is an error during probe distribution.
- Distribution post-install error:Select the alarm to be sent when there is an error after the probe is distributed and installed.
- Time interval at which alarm will be resent (minutes):Select the length of time (in minutes) when an alarm will be resent.
- Virtualenables the controller to set up the communication between the robot and the virtual probe running a remote probe. Virtual robots, using the proxy probe, will be created for 'remote' probes. remote probes are installed and running on computers without a robot. The remote probe is configured with the path to the robot.The Netware System probe is the only probe that can be set up on a virtual robot.
- NATlets you allocate an external IP address to a robot that resides on another IP network with incompatible addressing. The robot will be able to send alarms and QoS messages, but the hub will not be able to communicate back to the robot. When Network Address Translation (NAT) is in effect between the robot and the hub, the robot must be configured to provide the correct address to the hub. All communication from the hub to the robot will use this address. NAT can be set for the primary and secondary hubs.
- IP of the Robot as seen from the primary hub:Enter the name of the robot as shown in the primary hub configuration.
- IP of the Robot as seen from the secondary hub:Enter the name of the robot as shown in the secondary hub configuration.
- Robot IP Address:Select the option for detecting the IP address, either automatically detect or enter a specific hub address.
- IP version support:Select the IP version support for the robot.
- Local IP validation:Select this option if you want local IP validation performed.
- Data origin
- Origin:Enter the origin name you would like associated with this robot.
- Update button:Click this button to update the origin name associated with this robot.