controller AC Configuration
This section describes the configuration information and options available through the Admin Console controller configuration UI. For an overview of the probe, see . The controller probe does not require configuration after deployment. If needed, you can fine-tune the controller configuration. The navigation pane organizes the configuration options into the following nodes:
This section describes the configuration information and options available through the Admin Console controller configuration UI. For an overview of the probe, see controller. The controller probe does not require configuration after deployment. If needed, you can fine-tune the controller configuration. The navigation pane organizes the configuration options 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 checkmark icon to the left of the controller probe and select
Version 7.9 of the controller probe includes the Admin Console Probe UI. Admin Console will attempt to match the probe version to its archive file. If the probe UI exists in the archive file, then it is used. Otherwise, the ppm version of the probe UI is used.
Controllernode lets you view information about the hub and adjust settings.
- Probe Information(read only) provides the probe name, start time, version, and vendor.
- Hub Connectivity(read only) provides the name of the current hub, the names of the primary (parent) hub and nonprimary hub that this robot attaches to during failover.
- General Configuration
- 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.
- In hub v9.10S, when one user tag is defined, both user tags must be defined.
- In hub v7.80, if user tags do not exist in thehub.cfgfile and theos_user_retrieve_from_robotoption is true (default):
- The user tags are copied from therobot.cfgfile to thehub.cfgfile when the hub restarts.
- After the user tags are copied, theos_user_retrieve_from_robotoption is set to false in thehub.cfgfile. When the option is set to false, a user can clear the user tags in thehub.cfgfile later.
- In hub v7.70, user tags on a hub system are specified inhub.cfg. User tags that are defined inrobot.cfgare ignored.
- Before hub v7.70, user tags on a hub system are read fromrobot.cfg. Default,blank
- Log Level
- Sets the amount of detail to be logged in the log file
- Log as little as possible during normal operation to reduce disk consumption
- Increase the log level for debugging. Default, 0 - Fatal
- Log Size (KB)
- Change the size of the log file
- When the log size is reached, new entries are added and the oldest log file entries are deleted. Default, 1024 KB
- Hub update interval (minutes)
- The interval at which the hub is contacted with analivemessage.
- The range is 1 through 180 minutes. Default, 15 minutes
- The hub is notified on a shorter interval when changes occur in the probe list.
- On Robot uptime, reported as state changesIf this option is selected, QoS messages on robot uptime are sent.
- The QoS messagestatus = upis sent when the robot starts.
- The QoS messagestatus = downis sent when the robot stops. Default, not selected
- Set QoS source to robot name instead of computer host name
- Select this option to use the robot name for the QoS source for alarms.
- By default, the host name of the computer hosting the probe is used as the QoS source. Default, Enabled
- Status(read only) provides information about the status of the robot.
controller, Setupnode lets you view and modify robot configuration settings.
- Robot Name
- The default name is the computer host name, and is auto-detected by default. Default, Auto Detect (recommended)
- Secondary Hub Robot Name
- Hub v7.80
- If the robot parent hub is unavailable, specify the method to use to locate a temporary parent hub.
- By default, the robot auto-detects 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,Automatically Detect (Search the subnet)
- Automatically detect (searches the subnet)
- Search the subnet for a temporary hub when primary and secondary hubs are unavailable
- All Hub Versions:
- Automatically unregister from hub on shutdown
- When the robot stops, anunregistermessage is sent to the parent hub.
- When selected, the robot disappears from Infrastructure Manager.
- When not selected, the stopped robot displays a red icon, enabling the operator to detect the situation.
- Suspend all probes when no network connection is available
- When a robot does not have a network connection, the robot can remain active or can enter a sleep mode. In sleep mode, all probes are suspended until a network connection is available.
- If this option is not selected, the alarm messages are spooled and flushed when a network connection becomes available. Default, selected (recommended)
- Configuration file locking
- Lock the configuration.
- First Probe port number
- Daemon type probes typically register a command port, which is allocated at runtime during probe start-up.
- Use this option to specify a specific range of port numbers for router or firewall purposes. Default, 48000
- Time offset from UTC (override the local time zone setting) sec
- This option overrides the local time zone setting
- The time specification must be entered as a time offset from UTC in seconds
- When no contact with hub
- Anunmanagedrobot is one which has lost connection with a hub. Default,Allow move only within domain(recommended)
- Environment Variables
- Variable NameThe name of an environment variable that is defined in the robot. The robot manages the probes that inherit the variable.
- Variable ValueThe value that is assigned to the variable name.
- Probe restart when the probe does not respondSelect the alarm to send when a probe does not respond and is restarted. Default, no alarm
- Dispatch error (internal)Select the alarm to send when there is a dispatch error for the probe. Default, major
- Max restart attempts reached for the probeSelect the alarm to send when the maximum number of restart attempts are reached. Default, major
- Error starting probeSelect the alarm to send when there is an error starting the probe. Default, major
- Timed probe not finished at the next start timeSelect the alarm to send when a timed probe is not complete at the next start time. Default, warning
- Timed probe did not return 0 on terminationSelect the alarm to send when the probe does not return a value of 0. Default, warning
- Probe unregisters port but keeps runningSelect the alarm to send when a running probe unregisters the port. Default, major
- Probe distribution request errorSelect the alarm to send when there is an error during probe distribution. Default, major
- Distribution post-install errorSelect the alarm to send when there is an error after the probe is distributed and installed. Default, no alarm
- Time interval at which alarm will be resent (minutes)Select the number of minutes elapsed before resending an alarm. Default, 0
- VirtualRemote probes install and run on computers without a robot. The remote probe is configured with the path to the robot.Virtualenables the controller to set up the communication between the robot and the virtual probe running a remote probe. Virtual robots, using theproxyprobe, are created for remote probes.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 residing on an IP network with addressing which is incompatible to the hub. The robot is able to send alarms and QoS messages. The hub is not able to communicate with the robot. WhenNetwork Address Translation(NAT) is used, the robot must be configured to provide the correct address to the hub. All communication from the hub to the robot uses this address. NAT can be set for the primary and the nonprimary hubs.
- IP of the Robot as seen from the primary hub- Enter the name of the robot as shown in the primary hub configuration. Default,Real_IP
- IP of the Robot as seen from the secondary hub- Enter the name of the robot as shown in the secondary hub configuration. Default,Real_IP
Robot IP Addresssection:
- 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 to perform local IP validation.
- Listen only to first valid address from configured Ip addresses
- Data origin
- Origin- Enter the origin name to associate with the robot.
Changing the origin might cause probes (other than hub, controller, and spooler) to restart to pick up the changes.
- Marketplace SettingsMarketplace Settingsare removed in hub v9.10S. Secure hubs do not support passive robots.
- Marketplace Username- The username that is used to run the marketplace probes.The username applies to all marketplace probes on the same robot. We highly recommend that you donotuse the root or the Administrator account. Grant to the marketplace user the least privileges required to run the probes. Changing the marketplace settings might cause marketplace probes to start or restart to pick up the changes.
- Password (Windows Only)- The password for the marketplace username
- Passive Mode Required- The robot must be in passive mode for the marketplace probes to run. Default, SelectedIf the controller isnotin passive mode, selectPassive Mode Required. If passive mode is not required, the robot allows marketplace probes to run anyway. For security reasons, we highly recommend that marketplace probes run on passive robots. Changing the marketplace settings might cause marketplace probes to start or restart to pick up the changes.
You must use Infrastructure Manager to convert a controller to passive mode.