The Microsoft Cluster Server (MSCS) clustering software allows multiple Microsoft Windows servers to be linked together and perform as one virtual server. AppManager for MSCS provides Knowledge Scripts designed to give you a comprehensive view of how MSCS performs.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials website.
This release of AppManager for Microsoft Cluster Server provides the following enhancements:
Support for Windows Server 2019: With this hotfix release, AppManager for Microsoft Cluster Server provides a support for Windows Server 2019.
New option in KS to exclude MSCS groups from monitoring: With this hotfix release, a new option is added in the MSCS_Groupdown Knowledge Script to exclude MSCS groups from monitoring. (ENG348144)
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.
This release of AppManager for Microsoft Cluster Server replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Microsoft Cluster Server has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the MSCS computers you want to monitor (agents), and on all console computers |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later One of the following AppManager agents are required
|
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
Microsoft Cluster Server on the agent computers |
Supports 32-bit and 64-bit systems |
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the computers you want to monitor (agents), and on all console computers |
7.6.170.0 or later |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
For more information on hardware requirements and supported operating systems and browsers, see the AppManager for Microsoft Cluster Server Management Guide, included in the download package.
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
Microsoft Cluster Server includes a managed object, qMSCSa4.dll, and Knowledge Scripts to discover and monitor Microsoft Cluster Server resources. The download package includes these release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-MSCS-7.2.88.0.msi, the module installer.
AM70-MSCS-7.2.88.0.ini, a configuration file used with the AppManager setup program.
AM70-MSCS-7.2.88.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-MSCS-7.2.88.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckMSCS.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_MSCS.xml, a configuration file used for deploying the module with Control Center.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On the Microsoft Cluster Server computers you want to monitor (agents) to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
IMPORTANT:If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for Microsoft Cluster Server Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Remote deployment fails on Microsoft Windows Server 2012 computers with versions of AppManager prior to 8.2. When you remotely deploy this module to a computer running Windows Server 2012, AppManager displays the following error: Unknown operating system detected for machine IPAddress. To work around this issue on Microsoft Windows Server 2012 computers with versions of AppManager prior to 8.2, install this module manually. (ENG319069)
This module does not discover Cluster Shared Volume disks in Microsoft Windows Server 2012 environments. If you are running Microsoft Windows Server 2012, the AppManager for Microsoft Cluster Server does not discover Cluster Shared Volume (CSV) disks. (ENG325080)
The ResourceDown Knowledge Script incorrectly displays events for a resource that has a comma in its name. When AppManager raises an event for a resource object that has a comma in its name, such as SANDISKF,G,H,I, AppManager displays events for that object on the Master tab, but not on the Module tab. (ENG303646 and DOC304437)
This release of Microsoft Cluster Server includes enhancements added in previous releases.
This release of AppManager for Microsoft Cluster Server provides the following enhancement:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Microsoft Cluster Server provides support for TLS 1.2.
Add KS option to monitor all cluster IPs: This release of AppManager for Microsoft Cluster Server enhances MSCS_ResourceDown Knowledge Script to report when all clustered IPs are down. (ENG341165)
This release of AppManager for Microsoft Cluster Server resolves the following issue:
New option in KS to exclude MSCS resource from monitoring: With this release of AppManager for Microsoft Cluster Server, a new field "List of resource to exclude" is added in the Knowledge Script.(ENG347425)
This release provided the following enhancement:
Support for Microsoft Windows Server 2016: This release supports Windows Server 2016. For more information, see the System Requirements.
This release provided the following enhancement:
Support for Microsoft Windows Server 2012 R2: This release supports Windows Server 2012 R2.
This release resolved the following issue:
MSCS_HealthCheck and MSCS_NodeDown Knowledge Scripts do not raise events if a node is down or unavailable: This release resolves an issue in which the MSCS_HealthCheck and the MSCS_NodeDown script failed to raise an event when a node was down or unavailable. With this release, an update to both the MSCS_HealthCheck and the MSCS_NodeDown scripts allow the scripts to properly raise an event in this situation. (ENG330455)
MSCS_HealthCheck Knowledge Script generates an incorrect event message about restarting groups and resources: This release resolves an issue in which the MSCS_HealthCheck script generated an event incorrectly reporting that a group and resource had been restarted, even though the script was not set to automatically start groups and resources. This error occurred if all the event severities for this script had been set to the same value, such as 15. With this release, an update to the MSCS_HealthCheck script prevents this issue from occurring. (ENG262786)
This release provided the following enhancement:
Support for Windows Server 2012: This release now supports computers running Microsoft Windows Server 2012.
This release also resolved the following issue:
Discovery fails and reports 5079 error: This release resolves an issue in which the Discovery_MSCS Knowledge Script failed with the error Err 5079: The specified node does not support a resource of this type when you attempted to discover an unavailable resource type, such as a resource type that had not been added to the cluster. This issue only occurred when the unavailable resource type was the last item in the MSCS list of resource types. With this release, the module ignores all unavailable resource types regardless of where they appear in the list of resource types. (ENG319997)
This release resolved the following issue:
The ResourceDown Knowledge Script does not recognize multiple drives on a single resource: This release resolves an issue in which the ResourceDown Knowledge Script did not recognize all the drives available on the resource, such as a SanDisk resource. This release lists each drive on a resource separately in the TreeView pane so you can monitor each drive on the resource as needed. (ENG301097)
This release provided the following enhancements:
Support for Windows Server 2008: This release supports MSCS running on Windows Server 2008.
Support for Windows Server 2008 R2: With this release, AppManager monitors MSCS installed on Microsoft Windows Server 2008 R2.
Support for 64-bit operating systems: This release supports MSCS running on 64-bit versions of Windows Server 2003 and Windows Server 2008.
Support for IPv6: This release offers the first of several phases of support for Internet protocol version 6. In this release, AppManager for MSCS recognizes the 128-bit addresses provided by IPv6. The larger IP addresses are visible in the AppManager Operator Console and Control Center Console wherever IP addresses are displayed.
This release resolved the following issues:
Paused MSCS nodes reported as Down: Before you install this release, the MSCS_NodeDown Knowledge Script reports nodes that are paused as down, causing an event to be raised. After you install this release, a code change prevents the script from reporting paused nodes as down. (ENG273456)
MSCS_Health Check Knowledge Script incorrectly raises events as Severity 40: Before you install this release, an error in the code causes the MSCS_Health Check Knowledge Script to set the severity for a successful failover event to 40, regardless of the severity parameter. After you install this release, a code change causes the script to raise an event correctly, based on the severity parameter. (ENG274194)
This version of AppManager for MSCS checks whether a cluster node, network, resource, group, or a network interface is down using a new Knowledge Script called HealthCheck. This Knowledge Script also checks if a group ownership has changed.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
Copyright (C) 2019 NetIQ Corporation. All Rights Reserved.