This article documents a product defect and fix for an issue with configuring the SQLServer probe via MCS results in unwanted alerts being created.
Problem Summary:
- We applied the template “SQL Server (Enhanced)” on a device, during application of the profile “SQL Server (Enhanced)”, we did not enable any QoS in the OC of profile “SQL Server (Enhanced)”, however we see the default alarm policy created and alerts were generated through the default checkpoints active in the config file but not from OC alarm policies.
Release : 20.3
Component : UIM - SQLSERVER
Please be aware the latest sqlserver_mcs_templates_5.47 is now GA and available for download via the below link:
- https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU03769&os=MULTI-PLATFORM
Description:
Stop unwanted alarm generated by probe when profile got created through MCS with no QOS enabled
Steps to apply the patch:
1. Import the Probe template package(v5.47) into the local archive.
2. Deploy the imported package to the robot system.
3. Migrate the probe template package from 5.46 to 5.47
Fixed Defects:
DE515833 : sqlserver probe 5.45.1 mcs template - Alarms generated with no QOS enabled in MCS profile
DE506174 : MCS profile trigger alerts for not configured parameters
Note: Default alarm policy should be disabled to avoid unwanted alarms
SHA256 Checksums:
sqlserver_mcs_templates_5.47.zip
19eebad31e812fb1a6d1595047268b978b3a7e9dc9be88ecb7d0466094e7e019
sqlserver_mcs_templates_5.47.txt
2f81eca4114dc1d0f7b7e01401215460f41118c7157fa9759ee428166d8e2830