Users Guide
You will be directed to the compliance report generated in the Compliance Details window. For more details about compliance report,
see View compliance report.
Generating compliance report using offline catalog
OMIMSWAC with or without Internet access allows you to select the Offline - Dell EMC Repository Manager Catalog to generate
compliance report.
Before you generate the latest compliance report of a cluster, ensure the followings. The following prerequisites are required when
OMIMSWAC is not connected to the Internet and the Offline-Dell EMC Repository Manager (DRM) catalog is used to generate a
compliance report and update components.
• Configure the share location details where the DSU and IC applications are placed. See Configure the update compliance tools setting.
• Generate the latest catalog files by using the Dell EMC Repository Manager (DRM) application. The supported version of DRM can be
downloaded from Dell EMC Repository Manager.
To view the compliance details, perform the following actions:
1. Under Update > Update Source, choose Offline - Dell EMC Repository Manager Catalog from the drop-down list. By default,
online catalog is selected.
Offline - Dell EMC Repository Manager Catalog: When the DRM repositories are available in a shared location and is applicable for all
managed devices by OMIMSWAC in data centers with no Internet connectivity.
NOTE: It is recommended that the Azure Stack HCI catalog files be used to generate a compliance report for Azure
Stack HCI.
2. Enter the CIFS share path where catalog files are placed and the user credentials to access the CIFS share path, and then select
Next: Compliance details: to generate compliance report.
The catalog files can be generated by using the Dell EMC Repository Manager (DRM) application. Ensure that in the shared catalog
repository all the required Dell Update Packages (DUP) are available for the target node.
If a new catalog path is provided, the previous path that was used to compute the update compliance may not be available.
OMIMSWAC collects the catalog from the shared path, collects the DSU and IC tools that are configured in the Settings tab, and
generates a Compliance Report. If DSU and IC tools are not configured in the Settings, OMIMSWAC with Internet access will download
them from www.downloads.dell.com to generate the compliance report.
NOTE:
You must provide individual catalog files with the user credentials for server manager, and cluster manager
respectively.
You will be directed to the compliance report generated in the Compliance Details window. For more details about compliance report,
see View compliance report.
Step 2: Viewing compliance report and selecting
components—Target node components in Failover
Clusters and Azure Stack HCI
The update compliance details are computed, and the compliance report is displayed. The doughnut chart represents the number of
components in compliant, urgent, recommended, and optional states using color codes. The Compliance Report provides a detailed view
of all the components that contains component name, current version, type, baseline version, compliance status, criticality, and
Compliance Type.
For HCI and failover clusters, the update compliance of the individual target nodes and the components are represented by using two
doughnut charts—Node Summary and Component Summary. To analyze further, check the individual nodes in the Compliance Report to
get the current version, baseline versions and compliance type of the components, and to view all the nodes and components in non-
compliant, urgent, recommended, and optional states respectively.
Along with compliance information, the license status (OMIMSWAC premium license) for each node is also displayed. All target nodes
participating in the cluster must have valid licenses, otherwise, you cannot proceed to update the cluster. For more information about
OMIMSWAC licensing, refer to OMIMSWAC Installation Guide.
Attribute names
Description
Component Name Specifies component name.
Update PowerEdge servers and nodes of HCI and Failover clusters 23