On the
Repositories page, you can load compliance files, operating system images, and compatibility management files.
You can load compliance files and specify a default version for compliance checking on the
Compliance Versions tab. You can load multiple compliance files into
PowerFlex Manager with different operating system images included. The compliance file includes operating system images for ESXi and
PowerFlex. When you add a compliance file, these images are automatically added to the
OS Images tab. If necessary, you can also create your own operating system image repositories. You can also load the compatibility management file on the
Compatibility Management tab to allow
PowerFlex Manager to determine which upgrade paths are valid and which are not.
On the
Compliance Versions tab, click
Add to load a compliance version. Click
Change to change the default compliance version to a new file.
You cannot make a minimal compliance version the default version for compliance checking, since it includes only server firmware updates. The default version must include the full set of compliance update capabilities.
PowerFlex Manager does not show any minimal compliance versions in the
Default Version drop-down list.
The
Compliance Versions tab displays the following information:
Table 1. Compliance version fieldsDescription of the compliance version fields
Field
Description
State
Displays an icon indicating one of the following states:
Pending—The compliance file download process is in progress.
Downloading—The compliance file is being downloaded and
PowerFlex Manager provides the percentage complete for the download operation.
Unpacking—The compliance file is being unpacked and provides the percentage complete for the unpacking operation.
Synchronizing—The compliance file is being synchronized with the management software after unpacking.
Available—The compliance file is downloaded and copied successfully.
Error—There is an issue downloading the compliance file.
Needs Approval—The compliance file is unsigned and needs approval for use.
Version
Displays the compliance version.
Source
Displays the share path of the compliance version in a file share.
Signature
Displays whether the digital signature on the compliance file is signed or unsigned.
File Size
Displays the size of the compliance file in GB.
Type
Displays
Minimal if the compliance file only contains firmware updates, or
Full if it contains firmware and software updates.
View bundles
Displays details about any bundles added for the compliance version.
Available Actions
Select an option for a compliance file that is in an
Error state:
Delete the compliance version
Resynchronize a compliance version
Select an option for a compliance file that is in a
Needs Approval state:
Allow unsigned file
Delete
Use the
OS Image Repositories tab to create operating system image repositories and view the following information:
Table 2. Operating system image repositoriesDescription of the fields associated with operating system image repositories
Field
Description
State
Displays the following states:
Available—The operating system image repository is downloaded and copied successfully.
Pending—The operating system image repository download process is in progress.
Error—There is an issue downloading the operating system image repository.
Repository
Displays the repository name.
Image Type
Displays the operating system type.
Source Path
Displays the share path of the repository in a file share.
In Use
Displays
True (the operating system image repository is in use) or
False (the operating system image repository is not in use).
Available Actions
Select an option to delete or resynchronize.
You cannot perform any actions on repositories that are in use. However, you can delete repositories that are in an
Available state, but not in use and not set as a default version.
All the options are available only for repositories in an
Error state. The
Resynchronize option appears only when you must perform a backup and restore of a previous image.
Use the
Compatibility Management tab to load the compatibility management file. To facilitate upgrades,
PowerFlex Manager uses information that is provided in the compatibility matrix file to determine which upgrade paths are valid and which are not. When you attempt an upgrade,
PowerFlex Manager warns you if the current version of the software is incompatible with the target version, or if any of the RCM or IC versions that are currently loaded are incompatible with the target compliance versions.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\