install_LINUX_23_64
Nimsoft Infrastructure for 64 Linux (clibc 2.3 or higher on x86 64 bit)

Nimsoft Infrastructure for Linux (clibc 2.3 or higher on x86 64 bit)
Revision history
Date Description State Version
07.03.2024

Released with DX UIM 20.4 CU10

SHA-256 Checksum: 59529684a7a2259f93f134f90690d5e836ee0b1131054edc5aaecf209c4a941a
9.41
09.01.2024

Released with DX UIM 23.4

SHA-256 Checksum: a13427800c538f1ca501c4857a9029d6366aea50ff1f7055637e2d150b142cc6
GA 23.4.0
28.09.2023

Updated to include hub and robot versions 9.40.

SHA-256 Checksum: 48b999a38aa3f3c56e7b4c6978f68c256c3d1f5cba27acbf818e53b801f4b412
9.40
05.07.2023

Updated to include hub and robot versions 9.39.

SHA-256 Checksum: f1a5606a28d87075fed815376f5a96b96fed663f4c6770cb64403e9f4c395648
9.39
02.05.2023
  • Updated to include hub and robot versions 9.38.
SHA-256 Checksum: 3f5138daca91fb561445ac5510e3f1c739ba62a332ab3141f2912dead0d23276
9.38
13.02.2023
  • Updated to include hub and robot versions 9.37.
SHA-256 Checksum: 1e7f6bff5f38e34b6dd8cfd2b6987c6bceb62b0e67e421b3f49405bafbe0c3aa
9.37
22.09.2022
  • Updated to include hub and robot versions 9.36.
SHA-256 Checksum: 4c5942a381b04c847a36d0edb4b3ae62f997b80654676cde5ca21be3825d667f
9.36
19.05.2022
  • Updated to include hub and robot versions 9.35.
SHA-256 Checksum: 0b68b18b0b8c227e8eaf9621b384cc0ea87d3a38bb9cea25a7f553fa3c0eedf2
9.35
22.12.2021
  • Updated to include hub and robot versions 9.34.
SHA-256 Checksum: dbec22443c5c02184b88f633f5197d254c389ff7dbac8d2fa434dcfe4e56c6d8
9.34
25.03.2021
  • Updated to include hub and robot versions 9.33.
MD5 Checksum: 6647e8f879b920897d3db769a1164683
SHA-1 Checksum: 0ba0aeca3924e9cf548986f374bcd13b428990fd
9.33
21.10.2020
  • Updated to include hub and robot versions 9.31.
MD5 Checksum: e5fb1dd2b3c3b3e33e4bc724f0850630
SHA-1 Checksum: 3c03abc4d9f21b97ad44bb423c57baafcb4cd535
9.31
24.03.2020
  • Updated to include hub and robot versions 9.30.
MD5 Checksum: 1b7b2b20b394c060f2c8af0ecf594009
SHA-1 Checksum: 486bc2f59b6e8f384be7c165f7501c5b2e19727e
9.30
20.08.2019
  • Updated to include hub and robot versions 9.20.
MD5 Checksum: 00951d14b9dc0bfb58b97f4537aa3058
SHA-1 Checksum: 42c4bd8c467327f4282429c01317340d6a5ee714
9.20
04.12.2018
  • Updated to include hub and robot versions 7.97.
MD5 Checksum: 3f18c2a1649be27fec46e3a50f2aa364
SHA-1 Checksum: f823d1fab2a4921e50a1768e0419a0173ce0953d
7.97
04.12.2018 7.96
06.09.2018

This package includes support for Ubuntu 18.04 LTS (Bionic Beaver)

MD5 Checksum: 4c4a0670c7a521d34d62265798ca4589
SHA-1 Checsum: df843e4db8c6298765ea5cb48c8460ac8f4dd04e
7.93
01.11.2017 md5sum: 1a86ede52760212736188d10b498f208
sha1sum: e1291e5ea4d3b2eb6510dd09af1cd900801de5ed
7.93
02.03.2017 Updated to include Hub and Robot versions 7.90. No longer bundling probe utility with robot installer.

md5sum: a070ad54e4362449a449b9c12fa875d5
sha1sum: 81509c36ff7ffefb333d28ff9f775f5973f99aef
7.90
29.06.2015

• 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: bd313acef141392b5635127454a2ebc9
sha1sum: 82ac0a7b184baf3fa36241580d860e1d4a3cf044
7.80
08.04.2015 7.71 fixes an issue seen with hub 7.70 in assigning ports for tunnel client connections. Prior to 7.70, the tunnel client connections would consistently use the 48xxx port range (based on the controller’s default first_probe_port setting of 48000). An issue in hub 7.70 caused the tunnel client connections to use a system-assigned port number, which would not be reliably fall in the 48xxx range. This caused issues with firewalls where the tunnel ports were explicitly allowed and expected to be in the specific range.

With hub 7.71, the default port range for tunnel client connections will again fall in the 48xxx range. The specific ports for tunnel connections can be overridden (as previously) by setting tunnel/ignore_first_probe_probe = 1 and tunnel/first_tunnel_port = in the hub.cfg.

md5sum: f93b1b1544f824650fbfd0a8f517b919
sha1sum: dcd93ac530cb4d8144da5b388d369ca6fb078658
7.71
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: 82dd72d6cb05f5756ee969a4243e45e9
sha1sum: 2a9007f0828830c9edf9f7b9dcd3c5efd86c12f7

*Note: Package version was deprecated to 7.70 to match the embedded hub and robot versions.
7.70
30.12.2014 • OpenSSL 1.0.0m
• Removal of a potential crash condition at shutdown
• Improvements to port free checks under various circumstances

md5sum: 4d48a8193811319c0f44002d3a4ad4fb
sha1sum: 33ca91d0449a661580e84a9c5a9f178eaa6bb806
8.10
29.09.2014
  • Packaged with 8.0

Md5sum: 007adeec8246310a104ddac9b30b7ae0
sha1sum: 26e560abe837611881d2cb925931aa5e11c40f9d
8.00
20.06.2014

Package that is included in the NMS 7.60 distribution.

md5sum: b6906a881e93d28eb50660623754634d
sha1sum: c9f65640e1f20867afb96cfe032b0989b28079a7

7.60
31.03.2014

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: 4b77ef85f66551b1a0a93b34bb4ca71f
  • SHA-1 checksum: 43c5f1ab30a8b1983b4f21b30cfe2198e513b7c0
  • 7.50
    20.12.2013
  • Archive package for the Nimsoft Monitor 7.10 release.
  • MD5 checksum: bd12dd729ffb42fcd227f7cde288f018
  • SHA-1 checksum: 57526b85739d85c6ed1a1969f3830ac54d0cf404
  • 7.10
    02.10.2013
  • Robot install package for the Nimsoft Monitor 7.0 Release
  • MD5 Signature: c98e8cecba32dc309493226e5e6688c6
  • 7.00
    01.04.2013 New versions. This package contains:
    Robot 5.70
    Hub 5.82
    Distsrv 5.30
    6.50
    02.10.2012 Adds installation support for Debian versions 5 and 6 systems, and Ubuntu versions 10, 11 and 12 systems.
    This package contains:
    Robot v5.70
    Hub v5.81
    Distsrv v5.23
    6.10
    05.07.2012 Removed nas. This package contains: Robot v5.70 Hub v5.80 Distsrv v5.22 6.00
    30.12.2011 New versions. This package contains:
    Robot v5.51
    Hub v5.66
    Nas v3.72
    Distsrv v5.21
    4.71
    28.10.2011 New versions. This package contains:
    Robot v5.51
    Hub v5.64
    Nas v3.71
    Distsrv v5.21
    4.70
    01.07.2011 New versions. This package contains:
    Robot v5.42
    Hub v5.60
    Nas v3.63
    Distsrv v5.14

    Included support for GLIBC 2.13-2.19.
    4.60
    01.03.2011 New versions. This package contains:
    Robot v5.32
    Hub v5.44
    Nas v3.54
    Distsrv v5.11
    4.51
    19.01.2011 New versions. This package contains:
    Robot v5.30
    Hub v5.42
    Nas v3.53
    Distsrv v5.10
    4.50
    08.12.2010 New versions. This package contains:
    Robot v5.23
    Hub v5.34
    Nas v3.52
    Distsrv v5.04
    4.49
    01.11.2010 New versions. This package contains:
    Robot v5.22
    Hub v5.31
    Nas v3.51
    Distsrv v5.03
    4.47
    01.10.2010 Fix for recognizing Linux GNU libc (GLIBC) version 2.10 to 2.12. New versions. This package contains:
    Robot v5.21
    Hub v5.31
    Nas v3.50
    Distsrv v5.02
    4.46
    08.07.2010 New versions. This package contains:
    Robot v5.11
    Hub v5.12
    Nas v3.43
    Distsrv v5.00
    4.42
    11.06.2010 New versions. This package contains:
    Robot v5.10
    Hub v5.10
    Nas v3.43
    Distsrv v4.95
    4.41
    31.03.2010 New versions. This package contains:
    Robot v5.00
    Hub v5.01
    Nas v3.41
    Distsrv v4.91
    4.40
    10.02.2010 New versions. This package contains:
    Robot v4.05
    Hub v4.90
    Nas v3.31
    Distsrv v4.90
    4.33
    17.12.2009 New versions. This package contains:
    Robot v4.02
    Hub v4.90
    Nas v3.31
    Distsrv v4.90
    4.32
    11.12.2009 New versions. This package contains:
    Robot v4.01
    Hub v4.90
    Nas v3.31
    Distsrv v4.90
    4.31
    07.12.2009 New versions. This package contains:
    Robot v4.00
    Hub v4.89
    Nas v3.30
    Distsrv v4.90
    4.30
    19.06.2009 New versions. This package contains:
    Robot v3.52
    Hub v4.88
    Nas v3.27
    Distsrv v4.74
    4.21
    16.06.2009 New versions. This package contains:
    Robot v3.51
    Hub v4.87
    Nas v3.24
    Distsrv v4.73
    4.20
    16.03.2009 Minor fixes. 4.13
    19.12.2008 Server 3.60. This package contains:
    - Robot v3.12
    - Hub v4.73
    - Nas v3.22
    - Distsrv v4.72
    4.12
    12.09.2008 New versions. This package contains:
    - Robot v3.11
    - Hub v4.71
    - Nas v3.15
    - Distsrv v4.71
    4.11
    Requirements
    Platform: None
    Software: None
    Hardware: None