Updates Nimsoft Robots to current version

This package contains the Nimsoft Robot files, and is used to upgrade a running Robot to the latest version.

Installation notes

You are advised to carefully read the document "Upgrading the Nimsoft Robot" before installation.

Do not drop the robot_update package onto a Hub to install to a list of Robots. Installing the package will restart the Robot, and the Robot running the Distribution Server being rebooted will leave Robots in the process of being upgraded in a broken state!

Maintenance mode

On entering maintenance mode the robot will perform a full restart and determine on startup which probes should be started. This involves a restart of a local hub or a reconnect to a remote hub. On leaving maintenance mode the suspended probes are started as if continuing the robot startup.

Note that when entering maintenance mode and the primary hub is down and the secondary hub is set to be found by automatic search, the following might happen:
- The robot reconnects to a different hub.
- The robot seems still to be connected to the previous secondary hub but appears read in Infrastructure Manager.

Note for Nimsoft in an active/passive Microsoft cluster

If upgrading from robot versions older than 3.12 to robot version 3.12 or newer in clustered environments: Install the following files on both cluster nodes before dropping the robot_update package:
vcredist_x64.exe (see link).
vcredist_x86.exe (see link).

See also the section "Installing Nimsoft in an active/passive Microsoft Cluster" in the Infrastructure Manager on-line documentation.

Unix specific notes

If your initial installation version was 2.43 or older then there was code in the startup scripts which checked if Nimsoft was already running and would exit if that were the case. In the case of a power failure or system crash a pid file will hinder Nimsoft starting up again. Recent controllers all have code to handle this case, but the existing startup script still has the code to hinder starting what it thinks is a duplicate instance of Nimsoft from starting. Since the startup scripts may have been modified after installation we cannot do this automatically, so manual modification is required. To fix this potential problem you must edit the startup script, removing the following code from the start section:

if [ -f "$NIM_DIR/robot/pids/" ]
NIM_PID=`cat $NIM_DIR/robot/pids/`
echo Nimsoft seems to be running already (pid=$NIM_PID)"
echo "Run $0 with the 'stop' parameter to stop it, or if it is"
echo "not running remove the file:"
echo "$NIM_DIR/robot/pids/"

When upgrading on Solaris 2.7 by dropping a robot_update on a controller prior to version 2.54, the controller is having difficulties recognizing the OS version. You will get the following message in the log - "Could not figure out what Solaris version you are running!" when this is happening. Stop the Nimsoft processes and do a reinstall of Nimsoft on top of the old installation on the Solaris 2.7 server to get this issue resolved.

When updating HP-UX robots prior to version 2.15 the robot has problems replacing the controller binary automatically. Stop the nimbus processes and copy the file robot/pkg/temp/controller to robot/controller and restart the Nimsoft process.
Revision history
Date Description State Version

Released as part of 23.4 CU1.1

Fixed Defects:

  • Resolved an issue where probe configuration changes were deployed by both the controller and Configuration Reader Service. Such duplicate action corrupted the deployment. Now, all configuration passes through the controller.
SHA-256 Checksum: 3bb2ed0884494ed1ee5e60c0baac4c54f7893cc7bb6d2130a0af6933c2365b03

Released with DX UIM 23.4 CU1.

What's New:

  • Upgraded OpenSSL from v3.0.11 to v3.0.13

Fixed Defects:

  • Resolved an issue where the configuration in the Package Editor in Infrastructure Manager does not match the configuration in the probe definition when the probe definition is of type daemon.
SHA-256 Checksum: 82e50e19d28f443fbb1930679e26bda4c97e9e5b06c4abb6d28fb37403b14c10

Released with DX UIM 20.4 CU10

SHA-256 Checksum: ff59b9afabbad58b55ad788aba61e85ea187483060ac15f1086ffc26d56b61f7

Released with DX UIM 23.4

SHA-256 Checksum: 1a39d7f7fe5c8baf09ec841a96e31c7b9dbed040e9dfa9cda5eac00ecde95a61

Released with DX UIM 20.4 CU9.

SHA-256 Checksum: f2a3cec60fda017f316f0e0df058fa6d6c41c05b20a043441efa36a983ef42c7

Released with DX UIM 20.4 CU8.

SHA-256 Checksum: e956331565a2049cfccd2346e20def33b33d0a28485060cfc9b7252f7efc0db8
  • Released with DX UIM 20.4 CU7.
SHA-256 Checksum: 6d027aea05b2b57249691b92345f0b6752eef3076dd92e972d110e7a355644dd

(Released with DX UIM 20.4 CU6)

Fixed Defects:

  • SSL vulnerability with robot 9.33HF5. (Support Case: 33255031)
SHA-256 Checksum: 691bed038a0ccb9eba5517640f7fb6ee30c960d68f0702bdc199395efd8aae12

(Released with DX UIM 20.4 CU4)

What's New:

  • OpenSSL upgraded to v1.1.1q for BCI-Nimbus components.
  • Remove Glibc check dependency for robots.
SHA-256 Checksum: 50c9dfcc64bc37316b4089bda58c700ff92f98c2d36468955fd7a5895a7e3617

What's New:

  • OpenSSL upgrade from version 1.1.1k to 1.1.1l
  • Race condition issue resolution while package distribution.

Fixed Defects:

  • Controller binding to 169.x address should be prevented. (Support Case: 32870028)
SHA-256 Checksum: c5b54871bc2b6251f8d76fd44e2fede8e650aeda74820bfbdf18e6e83d2fa65d

For the robot_update 9.34 Release Notes, see

SHA-256 Checksum: 6f5a99b04a8d35efdcf35e338f6563336583065767638bd6625e428897c35499

Fixed Defects:

  • DE505161: 32725529 - Robot restart when editing distsrv config

Reason: Issue is coming as size of key/value is more that 2KB.
Resolution: CFG_MAX_LINE size changed from 2K to 8K.

This is Control Release (robot_update_9.33_TF2).

MD5 Checksum: bb283b94ccdd1b829df887b8fe5fd33a
SHA-1 Checksum: 2b1d948a2ebf5d7e75da80a7ade1938000d38e4a
CR 9.33

(Released as part of UIM 20.3.3)

  • (9.32 HF1) Resolved an issue where robots were not falling back to their primary hub and were staying connected to their secondary hub, until the secondary hub was powered off. This behavior was being observed in those scenarios where both the proxy_mode and strict_ip_binding were enabled for the robot. With 9.32 HF1, this issue has been resolved. (Support Case: 32302280)
  • Fixed an issue where Windows blue screen (BSOD) was coming up during the reboot caused by controller.exe. Upon rebooting a system, during or immediately after the reboot process, users were observing a Windows crash event. (Support Case: 32467624)
  • Fixed an issue where the UIM Server installing was failing while upgrading from 20.1.0 to 20.3.0. The installation was unable to communicate with the controller probe in the allotted time. (Support Case: 32446423)
  • Fixed an issue where duplicate robots were getting reported in the OC UI, but the Admin Console was showing only one robot. (Support Case: 32450799)
MD5 Checksum: e179eecb3b07133060f5e60900a8cf86
SHA-1 Checksum: 7983bc4a6e181bfff185d0b26a1e397c5fada3cf
  • Released as part of the UIM 20.3.1 patch. UIM 20.3.1 is a patch release that contains separate standalone artifacts that let you upgrade to 20.3.1.
MD5 Checksum: 2fdd4b3cd1fe674790647bc839253102
SHA-1 Checksum: 9fe9690c8d54e0ded400091ae7a23b34f7368357
  • Released with UIM 20.3.
MD5 Checksum: f0a1342d755cc14119433297e2ac5c53
SHA-1 Checksum: ac7e2e7dda9329af3f734414a73b29efb982464b

(Included in UIM 20.1)

For the robot_update 9.30 Release Notes, see

MD5 Checksum: 04d3ae8ef528168a38eb01f90b98a74e
SHA-1 Checksum: 4e974403bbfd6d899d41a99ebadc4f3dab5d40f0

For the robot_update 9.20 Release Notes, see

Note: CA UIM 9.2.0 has adopted OpenJDK 8u212 instead of Oracle JDK. Because of this change, CA UIM 9 SP1 (9.1.0) that was using Oracle JDK (JRE) 8u212 is no longer available and has been removed from the Support site. All the functionality that was included in 9.1.0 is now released as part of CA UIM 9.2.0. Consequently, all references to the 9.1.0 release and the probe version 9.10 (released with it) have also been removed from this probe documentation. We recommend that you move to this version 9.20 of this probe, as the previous version 9.10 is no longer available now. For more information about the OpenJDK usage in CA UIM, see Adopting OpenJDK.

MD5 Checksum: 8f98be8192486b7659729cbffed0fd19
SHA-1 Checksum: c747a0cb1c17edc152b0809b10f32472aac2a866
  • Updated to support the Microsoft Visual C++ Redistributable for Visual Studio 2017 package version 1.01 (vs2017_vcredist_x86 1.01 and vs2017_vcredist_x64 1.01). This support helps ensure that the minimum version of the VS 2017 package is equal to or greater than 1.01. With this dependency on the version 1.01, the computer is no longer getting restarted automatically when installing the VS 2017 package. That is, with v1.01, no auto-restart of the computer happens.
  • Better handling of the controller plug-in. For example, when controller 7.96 (compiled with vs2017_vcredist_x86 1.0 or vs2017_vcredist_x64 1.0) tries to load attr_publisher (compiled with Microsoft Visual C++ Redistributable for Visual Studio 2008), the controller stops responding. This happens because of the compiler incompatibility. Now, with this release of the probe, which is dependent on vs2017_vcredist_x86 1.01 or vs2017_vcredist_x64 1.01, controller no longer loads the plugin (attr_publisher) if it is not compatible.
  • Updated to provide support for Amazon Linux 2.
MD5 Checksum: 39718176c576b220f83a79ae8014b549
SHA-1 Checksum: a66b12216228a396cd2f6c976fc9a6fe969aa0d5
04.12.2018 7.96

What's New:

  • (7.92HF5) If you create a new Solaris zone, a robot installed in the global zone is not automatically deployed to the new zone. To install a robot in a new, non-global zone, install the robot into the non-global zone using the same steps that you use to install the robot in the global zone. (Support Case 746015)
  • (7.92) In addition to the operating systems listed below, support for Suse 11 or later secondary hubs and robots is added:
    • If you are installing your hub or robot on one of the following operating systems:
      • CentOS 7 or later
      • Red Hat 7 or later
      • Suse 11 or later
      • openSUSE 13 or later
      • Debian 8 or later
    • You must enable the nimbus service after your nimldr installation is complete. To enable the nimbus service, execute:
    • systemctl enable nimbus.service
  • (7.92HF3) Fixed a problem where VMware templates were not properly created in Windows when audit=on was set. (Support Case 00425378)
  • (7.92HF3) Fixed a problem where sections of a probe configuration file could be lost during editing when AUDIT_DETAIL is enabled, causing the probe to crash.
  • (7.92HF3) Fixed a problem where timed probes showed as inactive when they are active. (Support Case 00633989)
  • (7.92HF3) Fixed a problem where multi-threaded probes could lock the config file on Windows unnecessarily.
  • (7.92HF10) Controller performance improvements.
  • (7.92HF11) The snmpcollector probe can now be successfully deployed through Infrastructure Manager. The controller now distributes the snmpcollector probe vendor certification files.(Support Case 00819546, 00824491, 00683844, 00825054, 00835227, 00818146, 00821694)
md5sum: e91393ace7888680f40743c5262ab01c
sha1sum: b041bcecc15dccbd64e6c24d383606913935090e
03.04.2017 What's New:
  • Ubuntu 16 x64 robot is now supported.
    • Perform a native installation as described in Deploy Robots in Bulk with a Third Party Tool and Native Installers. Note: Deployment with automated_deployment_engine is not supported for Ubuntu 16.
      • When installation completes, execute /opt/nimsoft/install/ enable to enable the robot services on Ubuntu 16. This step is not required for Ubuntu 14.
      • Start the robot with /opt/nimsoft/bin/niminit start
    • To completely uninstall the robot on Ubuntu 16, uninstall the service by executing the command systemctl disable nimbus.service, and delete the file /lib/systemd/system/nimbus.service.
  • Microsoft Cluster is now supported.
  • Windows Server 2016 robot is now supported.
  • Support for Debian 6 robot is discontinued.
  • The probe utility (pu) is distributed as a separate package. Use the pu package to upgrade the probe utility to v7.90.
  • Robot automatic IPv4 address determination is improved. Robotip does not have to be manually set in robot.cfg in order for a robot to start.
  • Robot failover detection prevents unnecessary robot failovers when the hub misses a single response to a robot request (_status, alive, robotup, or probelist). The robot is more tolerant of incomplete _status requests. Two new properties can be specified in robot.cfg.
    • robot_status_check_interval controls how frequently the robot polls the hub with a _status request. Previously, this was not configurable, and the polling occurred at a medium timeout, approximately every 11 seconds. Use this property to approximately specify the new polling interval. The interval is approximate because the status check occurs in the medium timeout that exceeds the requested interval. For example, if the robot_status_check_interval is set to 30 seconds, polling will occur every 33 seconds (3 x 11 second medium timeout). The default value is 60 seconds, which equates to a status check every 66 seconds.
    • robot_failover_count improves the resiliency of the robot. In the past, the robot failover mechanism was invoked when one _status request to the hub failed. Use this property to specify the number of consecutive _status failures that must occur before initiating robot failover to a secondary hub. Default, 2.

Known Issues:
  • Install the v7.90 robot_update package before upgrading the hub probe to v7.90. When the hub package is installed first, the hub appears to go offline in Admin Console and Infrastructure Manager. A communication error is reported, but the hub upgrade is successful even when the error occurs.
  • Update robotip manually on Debian platform
      By default, Debian uses as the name resolution address. When a robot is deployed to a Debian system with automated_deployment_engine and the system is restarted, the robot attempts to bind to To avoid contention for on Debian systems, take the following actions:
      • After installing the robot manually or with automated_deployment_engine, add or update the following key in the robot.cfg file to ensure that the robot binds to the correct IP address:
        • robotip = debian_ip_address
      • When preparing an XML file for bulk deployment to Debian systems, explicitly set the robotip in the XML file as follows:
        • <robotip>debian_ip_address</robotip> where debian_ip_address is the IP address that the robot should bind to on the target system
md5sum: 9de99bfb892ef6f20971e87891c1f701
sha1sum: 668248be81ad87eeeaa917e2690003aa62365926
02.03.2017 Controller plugin infrastructure for Application Discovery, Windows Server 2016 Robot, Debian 8 Robot, and Ubuntu 16 Robot.

md5sum: 8b5a4053356db5cf6c22fff49f6e2f6e
sha1sum: ccb356981f8dab1ceb3324879b9b157f9fabc87b

• Proxy mode for robot will now allow the robot spooler to start. In hub-7.7x, the spooler will not start on a controller restart when the controller is configured in proxy mode, due to a port assignment conflict. In hub-7.80, this issue was resolved.

• In SSL mode 0, the robot spooler will not attempt to communicate using SSL.

• AIX java probes will now start up. Previously, on AIX, the controller did not start java probes correctly, so that the java probes process failed to launch. The fix changes the way the system calls to start java probes allowing them to start.

• Controller pre-install exit codes are now correctly interpreted. Previously, POSIX systems were incorrectly utilizing the exit code which would cause improper behavior.

• Added longer output from the command line probe utility. The individual item character line limit is now 300 characters.

md5sum: e7cf470c3380b21b4820b15c1598419e
sha1sum: 614ca5a2b69ed46bd2d4675b85d90ec44254169d
31.03.2015 New features:
• When a robot fails over to a secondary hub, the robot retains its origin. The origin is attached to each QoS message generated by a probe and routed through its robot. By default, the origin is the robot’s designated parent hub. With hub v7.63 and earlier, the robot's default origin upon failover changed to the name of the failover hub. As of hub v7.70, the origin remains the name of the robot’s designated parent (specified by the hub attribute in robot.cfg). Icon
Note: UIM administrators can override the default value by defining the origin in the robot configuration. In multi-tenant environments, for example, an admin can specify the origin in order to group data and control user access to the data. If the origin attribute exists in robot.cfg, the robot’s spooler attaches it to the message, and the hub’s spooler does not alter it. This behavior has not changed.
• A hub can be configured to send an alarm to report dropped messages. All messages generated by probes have a subject that is used to route the message on the message bus. If the hub does not have an attach or post queue configured for a particular subject, any message with that subject is dropped by the spooler. Hub 7.70 has the ability to send an alarm to provide a summary of how often this occurs. This behavior is disabled by default. To enable it, specify in hub.cfg: subjects_no_destination_alarm_interval=< seconds >
• Username and password limitations are consistently enforced. Username must be 1 to 254 characters long and cannot contain control characters, right or left arrows (< or >), or forward slashes (/); password must be 5 to 254 characters long.
• Removed the ability to provide SID to command line probe utility. In past releases, the -S option of the pu command (which lets you execute probe commands from a command prompt) could be used to explicitly set a session identification (SID). This capability has been removed to prevent security from being bypassed through SID injection.
• Improved behavior of SSL mode. If a controller is managed by a hub that has SSL mode=0, the controller no longer creates the robot.pem file upon startup. Any UIM components installed on that system will not accept SSL connections.
• Improved DNS lookup during tunnel setup. DNS lookup, which maps the hostname to an IP address, will retry on DNS failures, making tunnels more tolerant of temporary or intermittent failures.
• Robot user tags are propagated in bus-generated messages and alarms. These values are specified in robot.cfg by configuring the controller probe in Admin Console or Infrastructure Manager.
• Robot can automatically pull probes with ADE. Upon startup, controller looks forrequest.cfg, a text file you can create to enable automatic deployment of the probes to the robot. Previously, these requests could only be facilitated by distsrv, which still handles them by default. With the release of automated_deployment_engine v8.1, the ADE probe also has the ability to handle these requests. To direct request.cfg files to ADE, use the Raw Config utility to add the deploy_addr parameter (which specifies the UIM address of the ADE probe) to robot.cfg: deploy_addr=/<domain>/<hub>/<robot>/automated_deployment_engine

md5sum: 067cf94c8cfd41fbe900d2db6a2e9cab
sha1sum: 3a4cd3af1475803d3411e6ef81d02491f7adb83d
30.12.2014 • OpenSSL 1.0.0m
• Removal of a potential crash condition at shutdown
• Improvements to port free checks under various circumstances

md5sum: dcc58b6f910ff594fc000feecfd9e0b7
sha1sum: 44f0a112726c0b6a1ea1fd1e89c3d9a804e676a7

-get_info now includes MAC address information for AIX, Solaris and HP-UX as well as the previously provided support for Linux and Windows. -Resolved core dump issue on controller shutdown. -Fixes a bug that caused the robot to always de-register from the hub on shutdown. -A socket leak in the get_info callback on Linux has been resolved.

md5sum: f2745f0b39e1f76c1dd9844fdd69183b
sha1sum: 1ffb6e08ea3980a6d79b8f531e3d229318580646


Fixes issue for non root robots where robot would not start properly.

md5sum: 57dc307a1fb68d746492e15b83cc55f9
sha1sum: 466de82b08d29cd6bbb71f6752a8dff255289b69


Package that is included in the NMS 7.60 distribution.

md5sum: f450137a2c08a2b2c713c3259fe99e0a
sha1sum: 0885c91d220af1aac00df107e63d791bc81c3e01


Package that is included in the NMS 7.50 distribution. Note that this is a package version. The actual robot version is 7.05.

  • MD5 checksum: 5d2b4175647cf0ebc789ede133e3eb4b
  • SHA-1 checksum: e32a2e67979c97584ef57181b3863ab02db1d6f1
  • 7.05
  • Archive package for the Nimsoft Monitor 7.10 release.
  • MD5 checksum: 9eef341627bc6cdac2d90b5e20ccabfd
  • SHA-1 checksum: d32734ab782089a3b59fba76c29a2c356c507f10
  • 7.10
  • Robot install package for the Nimsoft Monitor 7.0 Release
  • MD5 Signature: db790c69b5eb5f3de3e469a32985381f
  • 7.00
  • Improved general stability
  • Resolved issues with properly detecting Windows 2012 and Windows 8
  • Improved detection of spooler origin value
  • MD5 signature: 897f1ad1ba1e05b121591c5c4c389723
  • 5.90
    05.07.2012 - Added policy based, strict IP binding mode where robot and all probes now only bind to a specified IP address.
    - Moved to online help system.
    29.03.2012 Improved logging.
    Changed Controller request queues to FIFO data structures.
    NIS cache read fixed for memory leak problem with large NIS cache.
    Internal alarm fixed for passive robots.
    Fixed problems with passive robots losing connection.
    Changed buffer size for fetching ip addresses to support systems with large number of interfaces.
    Fixed a problem where controller would report back previous value of origin after the user edits in GUI. Now we write origin to spooler.cfg before we restart controller.
    Spooler: Fix for messages expired count erroneously 0 in alarm messages.
    Enhancement to allow passive robots to issue SID for local use.
    30.12.2011 Fix name lookup when using hdb. 5.52
    15.11.2011 SSL communication mode fixes.
    Fix for garbled internal alarms from the spooler.
    25.09.2011 Spooler fix: Detect problem and skip on corrupt (partial) message header in queue file.
    On robot startup, print running as user information to log.
    Support for IPv6.
    01.07.2011 Unix/Linux pidfile problem fixed. Robot would not start if pidfile was empty.
    Support for AIX7.
    Support for glibc versions 2.13-2.19.
    06.06.2011 Variable expansion fix.
    Fixed log position problem on probe_tail_logfile_session.
    Added functionality to enable NIS cache maintenance.
    Added 'interfaces' option to the 'get_info' callback to include a list of known network interfaces.
    proxy mode fix: if used with first probe port, the internal controller port gets assigned the first probe port. Note that it is not normally recommended to use these options together as all communication should go throught the proxy port.
    Spooler storm protection improvement: saves subject, probe, severity and suppression key of last message discarded message in a message storm.
    Added spooler option to set alarm level for queueing problem alarms.
    Spooler error situation on Linux due to ip misconfiguration handled.
    Added support for using proxy mode in passive robots. This requires hub version 5.53 or newer.
    Changed potentially misleading alarm texts for spooling problem situations.
    Made default fail window configurable and changed default from 10 to 15 seconds.
    Fix for distribution requests over tunnel.
    More detailed error logging in spooler.
    Bulk transfer problem in spooler with not emptying buffer on multiple bulks fixed.
    Input fields changed to allow spaces in user tags in the controller configuration tool.
    Increased buffer for nimGetIpList to 512 bytes in nametoip and iptoname callback routines.
    Upgraded OpenSSL library.
    01.03.2011 Fixed crash situation on error return from timed probe.
    Improved storm protection, support added for setting storm thresholds per item.
    19.01.2011 Added 'post_raw' callback to spooler command interface.
    'file_put_start' and 'file_put_next' commands will write to a temporary file if the file already exists. The file is renamed to the destination name on 'file_put_end'.
    Added ability to alarm on post-install error situations.
    Added support for scheduling maintenance mode.
    Added validation of specified robotip against known local interfaces, with alarm and reversion to last known good ip on error. Add 'local_ip_validation = no' if you need to turn off this functionality.
    Added alarm on missing or disabled spooler.
    Added alarm on communiaction error between controller and spooler.
    In log and configuration tool, renamed 'maintenance mode' to 'suspend mode'.
    Spooler locking problem on message expiration fixed. The problem can be avoided on previous versions of the spooler by adding 'expire_size_severity = 0' to the spooler section of the spooler configuration file.
    Daylight Savings Time change recalculation fix to avoid disruptive recalculations on slow machines.
    'proxy_mode' fixes.
    Dynamic size of os_user tags.
    09.12.2010 Dynamic size of os_user tags. 5.23
    01.11.2010 Fixed problem with license expiration for probe on server.
    Implemented bulk message transfer to hub in robot spooler.
    01.10.2010 Force hub update if maintenance period is changed.
    Implemented "iptoname" callback.
    Modifed spooler to check against local ip list for incoming messages to add correct source.
    Sending of System Uptime QoS message is not attempted until the spooler is confirmed to be up.
    Prepare robot to be able to get audit setting from hub.
    Handle duplicate rejection return on robot registration with hub by appending ip to name and rejecting the license issued by the hub.
    07.07.2010 Find package version from probe for inst_list_summary callback when needed.
    Clean NIS cache on cloud startup.
    11.06.2010 Changed interaction with discovery_server.
    Added functionality to capture probe output.
    Added process start check for probe type daemon - this should fix problem where on_demand probe could be not be started right after installation.
    Added support for probe restart on dependency package update.
    Added _audit_send callback.
    Modified logic for spooler message queue size limit.
    Added alarm on message expiration.
    On probe startup; Try again if depending on a suspended probe and not in maintenance mode.
    Passive robot: hubupdate when leaving maintenance mode even when no probes are present.
    26.03.2010 Fixed problem with Controllers on LINUX systems under certain conditions would go inactive during distribution of probes.
    Introduced configurable max disk space used by spooler.
    Added support for passive mode Robot.(Where firewall is prohibiting access in direction from Robot to HUB, only allows access in direction from HUB to Robot.)
    Added support for encrypted SSL communication.
    Bugfix for distribution request; distsrv can now be specified in request.cfg file.
    License expiration information security fix.
    10.02.2010 Excluded loop back interfaces when binding to IP interface (127.x.x.x).
    Added option for cloud.cfg in setup section:
    expect_ip_change = yes
    This option is for compatibility with OpSource cloud. (VMWare clouds)
    17.12.2009 Detect clock change back in time of more than 10 minutes and restart. (Requirement for cloud instanciation.) 4.02
    11.12.2009 Added support for detection of gLibc up to version 2.12 on Linux systems.
    07.12.2009 Added cloud initiation option.
    Added 'edit' option for configuration file merge. This option will change keys in the section without moving the section.
    Fixed timer recalculation for timezone changes to resolve side effects when stopping or starting several probes simultaneously.
    Allow regular expression for OS matching in packages.
    Fix for license lookup in NAT environment, distsrv ip is checked against hub ip.
    Fixed potential UNIX/Linux problem with audit for probes without configuration file.
    20.10.2009 Temporary upgrade version for UNIX systems. 2.71
    24.09.2009 Fixed timer recalculation for timezone changes to resolve side effects when stopping or starting several probes simultaneously.
    Added package dependency information to installed information.
    Added optional package argument to the inst_list call.
    Added option to set separate robotip_alias for secondary hub.
    Added support for ip aliases in configuration tool.
    Added timestamp in information sent to hub to indicate the time of the last package change.
    Added callback 'inst_list_summary'.
    Added support for Linux systems with glibc 2.2.
    19.06.2009 Added origin to robot information sent to hub.
    Modifed internal clear alarm text for probe start to include probe name.
    Added 'origin', 'user_tag_1' and 'user_tag_2' to internal messages.
    Fixed robotip_alias / nametoip consitency for local and remote calls.
    Changed default 'wait_after_unregister' from 10 to 60 seconds to avoid erroneously setting probes to the alarm state when they need some time to clean up on restart or termination.
    Audit change to handle ldap user the same as a normal user.
    Fixed mainetance mode problem introduced in controller version 3.50.
    Fixed missing robot status update to hub on leaving maintenance mode with no probes present.
    Improved error handling, the spooler will abort if unable to maintain local spooling files.
    16.06.2009 Added support for Windows on Itanium 2 systems (IA64).
    Added support for controlled shutdown.
    Added audit functionality.
    Modified 'on_demand' functionality.
    Added 'start_after' option for probes.
    Added code to probe_deactivate that will send _stop to a probe if it has a port but no process.
    Modified restart of probe after failure so that deactivate works on the failing probe.
    Added regular next event time check to avoid skipping events on daylight saving or timezone changes.
    30.03.2009 New Nimsoft library versions. 2.91
    16.03.2009 Added support for AIX 6.x and LINUX GLIBC versions 2.8 and 2.9.
    Fixed problem with controller restarting when using logmon probe on HPUX Itanium 64-bit system.
    19.12.2008 NimBUS library changes.
    Fixed package so that hdb configuration file setup is not lost on robot_update deployment on UNIX/Linux.
    Resolved CRLF problem with configuration packages distributed from Linux/UNIX.
    Added "controller/" to suppression key of internal alarm messages to avoid conflict with hub alarms.
    Added support for maintenance mode.
    Added support for specifying primary and secondary hubs by dns name.
    Modified configuration file merge on probe distribution so that modified sections are moved to the end of the containing section.
    Added the proxy probe to the list of probes to be started first.
    On restart - added _restart call to local hub to make it use updated user tag information.
    Set robot install dependency for Windows to version 2.90, which is a special upgrade robot to ensure successful upgrade on Windows.
    Fixed package installation problem on LINUX systems (note does not apply to systems with gLibc 2.3 or higher).
    Added 64bit unix ports.
    19.12.2008 Special version intended for version 3 upgrade on Windows. Distribute this version first before deploying robot_update version 3.xx. 2.90
    11.09.2008 Fixed package so that hdb configuration file setup is not lost on robot_update deployment on UNIX/Linux.
    Resolved CRLF problem with configuration packages distributed from Linux/UNIX.
    Added "controller/" to suppression key of internal alarm messages to avoid conflict with hub alarms.
    Added support for maintenance mode.
    Added support for specifying primary and secondary hubs by dns name.
    Modified configuration file merge on probe distribution so that modified sections are moved to the end of the containing section.
    Added the proxy probe to the list of probes to be started first.
    On restart - added _restart call to local hub to make it use updated user tag information.
    Set robot install dependency for Windows to version 2.90, which is a special upgrade robot to ensure successful upgrade on Windows.
    Fixed package installation problem on LINUX systems (note does not apply to systems with gLibc 2.3 or higher).
    Added 64bit unix ports.

    You are advised to carefully read the document "Upgrading the NimBUS Robot" before installation.

    05.05.2008 Changed spooler port check to detect when the hub spooler is used. 2.71
    29.02.2008 Fixes to use correct network address on a multi-network server. Should together with probe fixes help resolve the occasional 'Illegal SID' problem.
    More robust handling of configuration file merges.
    Modified hub port check so that the controller is able to handle a situation where the hub registers its port but never responds.
    Extended hub ip fields to 256 bytes so that fully qualified hostnames can be used for the initial hub contact.
    Probe scheduler fix for date specifications.
    26.11.2007 Added option to explicitly set time zone offset.
    Fixed memory leaks for audit and probe_config_get.
    Spooler updated to add timezone information to the messages sent.
    Alarm levels configurable through configurator.
    Clear on successful prpobe start of previous validation, license and start errors.
    Option to set interval for alarm resend if a probe is in an error state.
    Added logic to be able to handle license changes.
    Modified support for Vista / Vista x64.
    Corrected problem with moving unmanaged robot.
    03.08.2007 Fixed potential memory overrun in hdb, which would cause a segmentation fault.
    The probe_config_get callback is threaded out so that the controller can do its tasks even if a very large configuration file is requested.
    Added variable to control after how much time action is taken on unregister: wait_after_unregister.
    Modified behaviour on hub port check (if the hub unregisters its port but does not terminate and timed probe restart (when the probe is not finished on the next interval) - The process is killed after the wait_after_unregister timeout period.
    Modified behaviour when running with robotip_alias to allow callbacks used locally to return local ip-addresses.
    Fixes problem with controller's connection to the hub not being reestablished immediately if there is a communication error.
    Fixed variable expansion.
    11.05.2007 Fixed 'preserve active state' option on initial probe distribution so that the initial probe actice state is as specified.
    Added code to clean up hanging asynchronous calls.
    Modified '_restart' callback to also send '_restart' to the spooler to ensure that user tag changes are picked up.
    Modified to support multiple NimBUS instances on Windows.
    Added callback to request package distribution.
    Run postinstall command asynchronously on package installation.
    Full restart on modification of first port number.
    Package build number added to probe_list output.
    Added parameter checking to inst_pkg callback.
    Modified probe_checkin callback to always give real (local) ip address of robot.
    Modified directory_list callback to list local drives on Windows when no directory is specified.
    Added support for Windows Vista.
    Modified the inst_pkg callback to recognize package sections where exact OS Minor is specified as operating system.
    Added optional robotip_alias parameter in robot.cfg for using an alternative ip address in NATed networks.
    Correctly identify Solaris 7 systems.
    Added support for setting the logsize.
    Added set_qos_source option to enable the overridden robot name to be used as the QoS source.
    Added support for grouping sections in installation packages.
    Added delay on robot rename when running on a local hub to ensure that the hub has time to remove the original robot name.
    Modified port alive check so that 'on_demand' probes are not started.
    Internal alarms are now sent with correct robot and host parameters.
    The controller can now act as a PROXY for all the local probes. This is done by setting 'proxy_mode=1' in the robot.cfg file. All communication to the controller will use port 48000 and all communication from the controller should be on port 48001 and 48002.
    Added function to support dependency checking for '.NET Framework' and 'Window Installer'.
    Added missing termination of NIM_PROBE_KEY.
    Added code to enable license requests from robots where the license has expired to work over tunnels.
    Note that 'controller' must be added to Security/Probe Administration.
    Changed probe login to use private encryption key.
    Added support for nimLoginBase64(); this login is designed for languages that has non-binary libraries for the NimBUS API (e.g. Java and .NET)
    31.03.2006 Modified algorithm to determine 'Error' state on probe unregister to avoid alarms during normal operation.
    Added ability to set priority_level for individual probes to handle startup order and timing problems. Default priority can be set explicitly.
    Added 'temp_directory' field to probe definition which is used on probe removal to remove a temporary directory (with its contents) or file created by the probe during operation.
    Added 'port_reserve' callback for use by probes that need to get available port numbers from the range defined in the controller.
    Modified logic to better handle restart of the local hub.
    Added port alive checking of the hub port.
    Added a NIM_SECURITY_KEY environment variable used for security handshake between robot and probe.
    Probe security mechanism fix.
    Modified license validation so that only failed validations are used for code-breaker detection. This allows any number of consecutive license validation calls to be made as long as the licenses are ok.
    Modified variable export mechanism to correct problems on AIX 5.3.
    Probe state set to error when probe unregisters its port, but keeps running.
    Enabled use of a cfg-package for updating controller settings.
    Fixed checksum problem of the expiration file when the robot name was set.
    30.11.2005 Increased timeout for asynchronous calls. Modified validation algorithm. Windows: Modified to find ActiveState Perl binary correctly 2.41
    Platform: Please refer to the Platform Support Matrix located in the Download section of
    Software: Nimsoft Robot
    Hardware: 5 MB free disk-space