Opswise Automation Center Outboard 5.1.0 Maintenance
Introduction
Opswise Automation Center Outboard 5.1.0 consists of a family of components that address distributed systems management and automation. The components are packaged together as product installation packages. Product installation packages are provided for a variety of operating systems and hardware.
Stonebranch provides product maintenance in the form of updated product installation packages that contained the latest maintenance levels of product components. This document lists the product installation package and component maintenance history for Opswise Automation Center Outboard 5.1.0.
Product Packaging
Opswise Automation Center Outboard components are bundled together into production installation packages, simply referred as packages in this document. Each package is identified with a package version number and each component within a package is identified with a component version number.
Each package and component maintenance level is identified with a version number. The component maintenance level is incremented whenever a new component is made available that contains defect fixes or feature enhancements. A package maintenance level is incremented when a product component within the package changes or the package installation changes.
Package maintenance levels are not necessarily made available for all platforms. Package maintenance may be released for a subset of supported platforms. For example, Opswise Automation Center Outboard for UNIX may be at maintenance level 5.1.0.1, but Opswise Automation Center Outboard for Windows may be at 5.1.0.0.
Stonebranch changes product version, release, or modification identifiers at its discretion when it deems an appropriate number of enhancements or capabilities have been introduced to warrant the change.
Versioning
Package version numbers are comprised of four numeric identifiers: version, release, modification level, and maintenance level.
For example, for Opswise Automation Center Outboard 5.1.0.1:
- 5 = Version 5
- 1 = Release 1
- 0 = Modification Level 0
- 1 = Maintenance Level 1
Although each product component within the package is uniquely identified with its own version, release, modification level, and maintenance level, component version numbers are identical to the package version numbers.
Packaging Methods
Packaging methods vary among platforms based on the installation conventions and vendor recommendations for the platform. The purpose of this section is to describe the packaging and distribution methods used for the Opswise Automation Center Outboard package on its supported platforms.
Windows |
All packages are created with a Windows packaging tool. |
|---|---|
UNIX |
All UNIX platform varieties are packaged as binary shell scripts. |
Package Maintenance Levels
This section lists the component levels included in the Opswise Automation Center Outboard packages for each release.
Opswise Automation Center Outboard Packages
Windows
Release |
Release Date |
Message Hub |
Transporter |
Command Line Interface (CLI) |
|---|---|---|---|---|
5.1.0.18 |
April 3, 2014 |
|||
5.1.0.17 |
September 16, 2013 |
|||
5.1.0.16 |
July 10, 2013 |
|||
5.1.0.14 |
March 28, 2013 |
|||
5.1.0.12 |
January 28, 2013 |
|||
5.1.0.10 |
January 7, 2013 |
|||
5.1.0.5 |
September 12, 2012 |
|||
5.1.0.3 |
June 27, 2012 |
|||
5.1.0.1 |
March 16, 2012 |
|||
5.1.0.0 |
January 30, 2012 |
5.1.0.0 |
5.1.0.0 |
5.1.0.0 |
UNIX
Release |
Release Date |
Message Hub |
Transporter |
Command Line Interface (CLI) |
|---|---|---|---|---|
5.1.0.18 |
April 3, 2014 |
|||
5.1.0.17 |
September 16, 2013 |
|||
5.1.0.16 |
July 10, 2013 |
|||
5.1.0.14 |
March 28, 2013 |
|||
5.1.0.12 |
January 28, 2013 |
|||
5.1.0.10 |
January 7, 2013 |
|||
5.1.0.5 |
September 12, 2012 |
|||
5.1.0.3 |
June 27, 2012 |
|||
5.1.0.1 |
March 16, 2012 |
|||
5.1.0.0 |
January 30, 2012 |
5.1.0.0 |
5.1.0.0 |
5.1.0.0 |
Component Maintenance Levels
This section identifies the component changes in each maintenance release.
Message Hub, Transporter, Command Line Interface (CLI)
Release 5.1.0.18 - April 3, 2014
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-02988 |
Transporter |
All |
Transporter does not handle hostnames in transportN.ipaddr option. |
D-04017 |
Message Hub |
All |
Message processing may fail in HA setup. |
Release 5.1.0.17 - September 16, 2013
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-03681 |
Transporter |
Windows |
Tasks may continue to show running when they are complete. |
D-03888 |
Message Hub |
All |
Message Hub may crash when retrieving large output. |
D-03926 |
Message Hub |
All |
Message Hub may send a malformed message if output size is greater than 6mb. |
D-03928 |
Message Hub |
All |
Limit the task output length to avoid problems constructing messages. |
Release 5.1.0.16 - July 10, 2013
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-03550 |
CLI |
All |
CLI does not support SSL communications with the Transporter. |
B-03614 |
CLI |
All |
Add Version option to CLI to identify program version. |
B-03643 |
CLI |
All |
Add support of encrypted credentials for CLI. |
B-03687 |
CLI |
All |
Add new CLI commands to support enhancements in the 5.1.1.7 Controller. |
D-03765 |
Transporter |
All |
SSL connection may be dropped during session establishment. |
D-03877 |
Transporter |
All |
Transporter on Windows cannot handle more than 57 Agents, and issue with simultaneous connections. |
Release 5.1.0.14 - March 28, 2013
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-03639 |
All |
All |
Potential for buffer overrun with logging set to TRACE. |
D-03603 |
Message Hub |
All |
Message Hub does not always reconnect to the Transporter when the Controller is restarted. |
D-03514 |
Transporter |
AIX |
Network interfaces are not enumerated correctly on AIX. |
D-03495 |
Transporter |
All |
Establishing an idle TCP session to the Transporter port 4803 blocks packets from other clients. |
Release 5.1.0.12 - January 28, 2013
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-03501 |
Message Hub |
All |
Potential for duplicate launch messages under heavy load. |
Release 5.1.0.10 - January 7, 2013
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-03304 |
Transporter |
All |
Transporter should allow an Agent to reconnect if the Agent's IP address changed after a network failure. |
D-03342 |
Transporter |
All |
Agents remain offline after Transporter was unavailable for a long period of time (>10 mins). |
D-03463 |
Message Hub |
All |
Message Hub may connect to the Transporter before it is active. |
D-03464 |
Message Hub |
Windows |
Message Hub may not exit cleanly when the Controller/Core closes the connection. |
Release 5.1.0.5 - September 12, 2012
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
B-03069 |
CLI |
All |
Outboard: Add ops-update-resource-limit capability to CLI. |
D-03172 |
Message Hub |
All |
Message Hub resiliency during Controller connection close. |
D-03059 |
All |
All |
Additional resiliency for Outboard components and guardians. |
Release 5.1.0.3 - June 27, 2012
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-02987 |
Transporter |
All |
Transporter does not handle hostnames in the transportN.ipaddr option. |
D-03022 |
Message Hub |
Solaris SPARC |
Message Hub crash when connecting to Transporter. |
Release 5.1.0.1 - March 16, 2012
Change ID |
Component |
Platform |
Description |
|---|---|---|---|
D-02874 |
UAG |
All |
UAG ends abnormally when unrecognizable data is sent to the TCP/IP logging port. |