|
Date
|
Description
|
State
|
Version
|
|
|
|
|
|
03.04.2017
|
Updated to include Hub and Robot versions 7.91. No longer bundling probe utility with robot installer.
md5sum: a7c57e945fec0d5ff5c5e25ed815191c
sha1sum: 5ed133909e27c8a8e1353ccf86ce8a22dc2ac6a9
|
GA
|
7.91
|
|
|
|
|
|
02.03.2017
|
Updated to include Hub and Robot versions 7.90. No longer bundling probe utility with robot installer.
md5sum: 902edea81ca0763eff61d2511cab2eb1
sha1sum: 24992b7c42fe978069d8ce51974e5dd5719faa32
|
|
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: 1f69190d17e65188ee4b0874cea51e05
sha1sum: 83eb3abf5a8dda7c1229aee2772b7f9158e36e0d
|
|
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: 804c9b720a11ce3caa4904fe20fe5c76
sha1sum: e7915a08bf036046b53a0f4379f74adf4d285b75
|
|
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: c1867d8323b807323c1c59743c9add1a
sha1sum: d7c2c8adc731338db6457e453498e053e5cac75a
*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: 7d264c86a5f79abdf058618570d24fdc
sha1sum: b16050c45bbf008933eefdaab4b7eccff0ea1e55
|
|
8.10
|
|
|
|
|
|
29.09.2014
|
Md5sum: f0df47b89afdd465e9b5fa75f988739b
sha1sum: acf263f83c5130ca9cf9f1aa5b44768112889378
|
|
8.00
|
|
|
|
|
|
23.06.2014
|
Package that is included in the NMS 7.60 distribution.
md5sum: 5e058a46574bbdd4cf2c099a4ea5075ef
sha1sum: aa5d98ee203b62978f8fe37bb5a63ff6a3c4472c
|
|
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: 444b06ce28a317105d3ef23c2a95081a
SHA-1 checksum: 7ee84b199daded9968d25a2aedf360eb09affd6c
|
|
7.50
|
|
|
|
|
|
20.12.2013
|
Archive package for the Nimsoft Monitor 7.10 release.
MD5 checksum: b5180d0ff24d66f16c1f545fec5bd0ce
SHA-1 checksum: ca753bb8ed360e82bec058eb2b91148551077bdc
|
|
7.10
|
|
|
|
|
|
02.10.2013
|
Robot install package for the Nimsoft Monitor 7.0 Release
MD5 Signature: 22d4130465b8d4c77dc25b983af70ce4
|
|
7.00
|
|
|
|
|
|
01.04.2013
|
New versions. This package contains:
Robot 5.70
Hub 5.82
Distsrv 5.30
|
|
6.50
|
|
|
|
|
|
30.09.2012
|
Added support for Debian 5/6 and Ubuntu 10/11/12.
|
|
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 AIX 7.
|
|
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
|
AIX version 6.x is now supported.
|
|
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
|
|
|
|
|