v7.8 controller IM Configuration

This article describes the Infrastructure Manager controller configuration UI, and provides information about advanced configuration. To open the UI, double-click the controller probe in the Infrastructure Manager. For an overview, see .
uimpga-ga
controller_7.8_IM
This article describes the Infrastructure Manager controller configuration UI, and provides information about advanced configuration. To open the UI, double-click the controller probe in the Infrastructure Manager. For an overview, see controller.
3
Setup
Nimsoft
Set up the robot and a secondary failover hub in the 
Nimsoft
 tab. 
controllerIMConfig01.png
The tab contains two sections:
  • Robot Name
    - attaches to the parent hub when the hub is active.
if the
Search the subnet for a temporary hub
option is selected, this option changes to the
Automatically detect
option.
 
    • 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 the 
      Search the subnet for a temporary hub
       option is selected.
    • Specify Hub (IP/name)
      - the robot attaches to the hub specified by IP address or host name
    • 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 available
       option to the
      Automatically detect (searches the subnet)
       
      option.
Misc
Use the 
Misc
 tab to set logging information, identification properties, quality of service, and the robot interaction mode.
controllerIMConfig02.png
  • Identification properties
    - specify
      User tag 1
     and 
    User tag 2.
    User tags are user-defined tags which 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, the hub is contacted with an
    alive
    message. 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 Robot mode
    - select
    normal
    or
    passive
    . Passive robots do not initiate the communication with a hub. The hub initiates all contact with the robot.
    • On Robot uptime, reported as state change
      - sends QoS messages for robot up time. The QoS message 
      status = up
       is sent when the robot starts, and
      status = down
       is sent when the robot stops.
    • Set QoS source to robot name instead of computer hostname
      - use the robot name that is specified on the
      Setup, Nimsoft
      tab. 
      This option is disabled unless the
      Set specific name (override)
      option is selected on the
      Setup, Nimsoft
      tab.
Advanced
Use the
Advanced
tab to set robot options, and the data origin.
controllerIMConfig03.png
  • Robot options
    - set options for the robot:
    • Automatically unregister from HUB at shutdown
      When 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 available
      When 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 number
      Daemon 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 UTC
      Use 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
    - An
    unmanaged
    robot is a robot that has lost contact with the parent hub. This option sets limitations on attempts to connect to a hub, using the 
    Tools, Connect Robot
     
    option in Infrastructure Manager.
  • Data Origin (override origin set by the Hub)
    - specify the Origin
    .
    The origin is a string that is attached to
     
    QoS data from probes. The origin identifies the originator of the data. The default origin is the name of the parent hub.
Environment
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.
Virtual (Deprecated)
Virtual probe configuration is deprecated. The Netware System probe has reached end of life and is no longer supported. The Netware System probe is the only probe that can be set up on a virtual robot.
 
Alarm
The controller issues alarms for error conditions. The
Alarm
tab lists the internal alarm messages. Select the severity level for each alarm message. You can select
no alarm
for the condition
Probe restart when the probe does not respond
.
controllerIMConfig05.png
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.
NAT
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.
Use the
Setup, NAT
tab to setup NAT.
controllerIMConfig06.png
If the robot and the hub are separated by a NAT device, the robot can send alarms and QoS messages. The hub cannot respond. To solve the problem, set up static NAT mappings for each robot behind the NAT device.  Use
Raw Configure
to add the key 
robotip_alias
 to the controller section of the 
robot
.
cfg
 file on the robot. 
robotip_alias
sets the IP address that is registered when the robot connects to the hub.
robotip_alias
specifies 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 = 193.71.55.153
...
<\controller>
Disable IP Validation for the Hub
Sometimes, when a request from a robot does not match with what is configured in the hub, security can break. This usually happens when a system is using NAT in someway. In these cases, IP validation must be disabled on the hub with disabling it in the security.cfg file, which is done with a PU call back.
Use the Probe Utility, which is accessed by selecting the probe and pressing Ctrl-P, to do the following:
  1. Add 
    ignore_ip = yes
     (key=ignore_ip , value=yes) by using the hub probe callback 
    hubsec_setup_put
     on the tunnel server.
  2. Verify the setting by using 
    hubsec_setup_get
     callback with the key as 
    ignore_ip
    .
On the tunnel client's hub.cfg, add 
check_cn = no
 under the tunnel entry. Or, use the hub GUI and uncheck 
Check Server common name
 in the tunnel client entry.
IP
Use the
IP
tab to configure the IP information for the robot.
controllerIMConfig07.png
  • Robot IP address:
    • Automatically detect
      The 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:
198.2.3.5, 138.3.4.10
198.2.*.*, 138.3.4.10
    • The controller and the probes it starts only listen for connections on the NIC addressed by
      198.2.
      If there are no
      198.2
      addresses, the controller and the probes listen on
      138.3.4.10
  • 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 to
    localhost
    , 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 addresses
      This 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.
Status
controllerIMConfig08.png
  • Robot name
    The actual or current name of the robot
  • Robot IP address
    The actual or current IP address of the robot
  • Robot version
    The version of the robot
  • Op. Sys.
    Operating system name
  • Op. Sys. type
    The type of the operating system (UNIX, Windows)
  • Op. Sys descr
    Operating system description
  • Indicator and status information
    The status indicator, together with a status message, gives information about the current controller status.
    • Green - OK
    • Red - error condition
Right-click the indicator to put the robot into maintenance mode for the period specified.
  • Installed packages
    The Installed Packages button opens a window which lists all the packages which are installed on the robot.
  • Robot environment
    The Robot Environment button opens the Environment window, which displays the variables and values for the computer running the robot.
    Any probes that the robot starts inherit the environment.
  • Hub connectivity
    Display the current, primary, and nonprimary hubs
Advanced Configuration
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.cfg
 file in two ways:
  • use the full DNS name instead of the IP address in the
    hubip
    parameter
  • use the full DNS name in the
    hub_dns_name
    parameter
Use the full DNS name of the server as the 
hubip
 parameter to allow the robot to recognize the main hub and return to it after a failover.
The robot move operation replaces the
hubip
parameter 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_name
to allow the robot to use the
hub_dns_name
to look up the hub IP address. If the lookup fails, the
hubip
parameter is used. When the DNS name lookup is successful, and the IP address is different from the
hubip
parameter, the parameter is replaced.
The same functionality is available for the secondary hub, using the
secondary_hub_dns_name
parameter.
The
hub_dns_name
is lost on a robot move.
the
secondary_hub_dns_name
is lost when the controller configuration tool changes the secondary hub.
<controller>
 hubip =
 hub_dns_name =
 secondary_hub_dns_name =
</controller>
Limiting the Number of Open Ports
Set the 
proxy_mode
 key in the 
robot.cfg
to limit the number of open ports in the environment (for example, in a network with a firewall).
In the
robot.cfg
, set
proxy_mode = 1
 to 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
Maintenance
to 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 (
controller
spooler
hdb
hub
distsrv
nas
, and 
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.