In TKU July 2008 the key for the VERITAS Cluster Server SI has been simplified and now consists of only 'type' and 'host.key' attributes. The reason is that only one Cluster Server SI can exist per host, hence having 'cluster ID' as part of the key is not required and can at certain times cause confusion (e.g. if cluster ID cannot be obtained on every scan, 2 SIs could be created, one for when the cluster ID was obtained, and another for when it wasn't).
Furthermore, we added an attribute to the Cluster Server SI which allows to monitor whether a certain Cluster Server License was purchased in a bundle with Storage Foundation. This attribute is either set to True or False, and can easily be used in Reporting to filter Storage Foundation Licenses from the Licenses which were bought exclusively for Cluster Server.
For more information, please see the relevant section.
A pattern to identify Symantec VERITAS Cluster Server on Windows platform has been added to the pattern module
Following customer feedback it was realized that the approach taken previously to uniquely identify the clusters the Cluster Server SIs (and hosts) belong to was incorrect. On UNIX, the cluster ID is user settable and is not unique.
The UNIX and Windows patterns have been updated as follows:
To aid in creation of unique ID for the cluster, the pattern does the following:
If the information is obtained to create a cluster key, a Cluster Node is created and all VERITAS Cluster Server instances which belong to this cluster and all hosts belonging to this cluster are added as members of this Cluster Node.
In TKU October we completely reorganized the way that we handle Licensing Data for Cluster Server. Whereas this data used to be stored in Additional Attributes of the SI, it is now stored into Licensing Details, one for each licensed entity present on the host. Each of these details are directly linked from the Cluster Server SI. To make it easier to employ the data present in these details, we outlined a number of sample Reports in the relevant page.
The Windows pattern, added in TKU April 2009, already implemented Licensing Details. However, in TKU October 2009, these were standardized to comply with the new Licensing model guidelines
Furthermore, we reworked the behaviour that the pattern takes when it encounters an entity of Cluster Server which was bundled with Storage Foundation. We no longer set an additional attribute in the Cluster Server SI. Instead, we model a containment link between the Cluster Server Licensing Detail and the Storage Foundation Licensing Detail, the latter containing the first. This condition can be easily identified through a specific Report, outlined in the relevant page.
In TKU November 2009 the ClusterServerWindows pattern was modified in having the nodes in the disappeared_dts list now destroyed individually inside a for loop.
In TKU Feb 2010 The regular expressions which used for License Detail processing were enhanced in order to collect trimmed values (without spaces in the end)
In TKU April an issue that was introduced in TKU October 2009 with the introduction of Detail Nodes was resolved. The initial implementation of storage of license information on Detail Nodes did not create the Detail Node key which was unique enough which could lead to information about multiple licenses linked to a product being lost. The way the Detail Node key is generated has been improved in the update to the pattern.
In TKU June the License Detail Node attribute holding the license key has had its name corrected from 'licenses_key' to 'license_key'.
Furthermore, the License Detail node now contains the version of the product in the 'name' attribute.
In TKU August 2010 there were some slight changes to prevent race conditions that could occur when the Software Instance was searched for before it was added to the datastore
In TKU September 2011 an additional active command method of obtaining the cluster name was added to the Symantec VERITAS Cluster Server UNIX pattern. The UNIX SI's 'name' attribute has been made consistent with Windows platform pattern and other patterns that model clusters. In the Windows pattern, the 'cluster_name' attribute is now displayed in the Atrium Discovery UI and SI attribute 'id' has been renamed as 'cluster_id' to make it consistent with other patterns that model clusters
In TKU November 2011 the VERITASClusterServer pattern had alternative commands, "haclus -list" and "hasys -list", added to get cluster name and hosts in cluster respectively. In addition, it no longer reads the '/etc/llttab' file. In addition, the search to locate licensing detail nodes was modified.
In TKU December 2011 the search to locate licensing detail nodes was reverted and corrected.
In TKU November 2012 the key for the cluster node on the Windows platform only was enhanced in having the host key removed so as to avoid duplicate SIs being created.
In TKU March 2014 added sorting for cluster_hosts in order to make cluster key consistent and trigger was changed to 'hashadow' which is better for product identification
In TKU February 2015 the pattern was updated with the following changes:
In TKU April 2015 the pattern was updated with the following changes:
In TKU July 2015 the pattern was updated with the following changes:
In TKU October 2015 the pattern was updated with the following changes:
In TKU December 2015 the pattern was updated with the following changes:
In TKU February 2016 the pattern was updated with the following changes:
'VERITAS' changed to 'Veritas' in SI name and type but not SI key (DRDC1-5253)
Cluster type changed from 'Symantec VERITAS Cluster' to 'Symantec Veritas Cluster' (DRDC1-5253)
In TKU April 2019 the following changes were made: