Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Unable to mtach any object to the EMC Support Matrix under Administration >> Modules >> Storage Compliance >> Match to EMC Support Matrix. All objects show as not matchedCOMPLIANCE.LOG shows the following error:INFO -- [2014-08-25 12:02:13 IDT] -- ComplianceManager::updateCompliancePolicy(): Policy ID P006 add/updated successfully!INFO -- [2014-08-25 12:02:13 IDT] -- ComplianceDefinitionUpdater$OperationExecutor::run(): Policy data successfully updated into Compliance DBINFO -- [2014-08-25 12:04:28 IDT] -- ChangeGeneratorScheduler::run(): ChangeGenerator comparision started.Mon Aug 25 12:04:28 IDT 2014INFO -- [2014-08-25 12:04:28 IDT] -- ChangeGenerator::comparePropertyStore(): Initiating APG store difference evaluation!INFO -- [2014-08-25 12:04:28 IDT] -- ChangeGeneratorScheduler::run(): ChangeGenerator comparision completed.Mon Aug 25 12:04:28 IDT 2014WARNING -- [2014-08-25 12:04:28 IDT] -- JavaMethodImpl::freeze(): Mismatch between Java model and WSDL model found, For wsdl operation {http://www.watch4net.com/APG/Remote/DatabaseAccessorService}getDistinctPropertyRecords,There is no matching wsdl fault with detail QNameThe following troubleshooting methods were applied: Manually match to the EMC Support Matrix values: In SRM Suite 3.x or Watch4net 6.3, select Operations > Compliance > Storage Compliance > Manage Rules & Policies. Click in the corresponding Matched To column of the configuration item with the status displaying Not Matched. The Match Value dialog appears. In the Match Value dialog, enter/select the appropriate value (field will auto-fill with values as you type), and click Ok. After you click Ok in the Match Value dialog, the status of the configuration item will display as Manual in the corresponding Matched Methods column. Bulk Matching to the EMC Support Matrix: When multiple configuration items have the same discovered value, they cannot be auto-matched and must be matched manually to the EMC Support Matrix using Bulk Matching. The steps to manually bulk-match configuration items are the same as the manual matching procedure described above using the Match Value dialog, with the following exceptions: When multiple configuration items have the same discovered value, bulk-matching is enabled for all items when you manually match one of the configuration items. When the matching is done, the status of the configuration item will appear as Bulk in the corresponding Matched Methods column. When you click the Matched To column of a configuration item for bulk matching that is associated with multiple configuration items that have the same discovered value, you will be prompted to choose the type of Bulk Matching you want to perform. The following troubleshooting was also performed without success:For ViPR SRM 3.5: Stop the Compliance-Backend on the Primary Backend: ./manage-modules.sh service stop compliance-backend Delete the esmdata folder present in /opt/APG/Backends/Compliance-Backend/generic-compliance/esmdata folder of the primary backend VM using the following command: # rm -r edsmdata Navigate to the /opt/APG/bin directory and run the following command to connect to the databases: ./mysql-client.sh At the "Enter username: [apg]" prompt use root At the "Enter database: [apg]" prompt use the default apg At the "Enter password:" prompt use "watch4net" Truncate the matched_data table using the command given below: mysql> truncate table compliance.matched_data; The following message will be displayed: Query OK, 0 rows effect Commit your changes # mysql> commit; Verify that the column matched_attribute_name exists in table matched_data: mysql> desc compliance.matched_data; If the column exists, then drop the column by using the command given below: ALTER TABLE compliance.matched_data DROP matched_attribute_name; Restart compliance-backend: ./manage-modules.sh service restart compliance-backend Wait for 5 minutes for ESM data to get uploaded. Run the EMC Support Matric policy and verify that the Match to EMC Support Matrix screen now displays auto-matched entries.
To resolve this issue reconfigure the Property Store configuration drop-down entry in the Storage Compliance Solution Pack reconfiguration screen. This is located under Administration >> Centralized Management >> SolutionPacks >> Storage >> Storage Compliance.In the Compliance Backend SolutionPackBlock the configuration for the Web-Service user was changed from WS-User to Admin.EMC support matrix matching was able to complete and find values for manual matching.