OMEVV users can access the UMP Repository Profiles to manage the baselines of the vSphere Cluster.
Prerequisites
Following are the pre-requisites to perform prior accessing the UMP Repository Profiles and managing the baselines of the cluster.
Ensure to install UMP on OpenManage Enterprise.
Ensure to create UMP ESXi and vSAN repositories.
About this task
After installing and creating the UMP Repository Profile, user can perform the following to associate UMP repositories to OMEVV.
Steps
On the OMEVV home page, click
Compliance & Deployment > Profiles > Repository Profile.
User can view UMP repositories supporting only ESXi and vSAN.
Suppose, user does not see the supported UMP repositories, perform the following steps.
On the
Repository Profile page of the wizard, click
RESYNC UMP/ DEFAULT REPO PROFILES.
To check the status, refer logs page.
Next steps
Any changes (Create, Edit, Delete) at UMP will be synced to OMEVV once in 24 hours. Users can trigger this synchronization if needed.
Deleting the repository at UMP, and the repository profile is associated with the Baseline Profile, then that repository reference is deleted from OMEVV. Update the Baseline Profile with any other Repository Profile and then delete the stale UMP repository.
Changes in the UMP catalog are reflected at OMEVV (either based on daily job or user-triggered synchronization), and the baseline version will be updated. Therefore, if the baseline is associated with the vLCM image, ensure to update the vLCM image with the latest baseline version.
By deleting the repository at UMP, and if the repository does not trigger a re-sync job, a stale entry of the repository profile will be present at OMEVV till the next daily synchronization job completes.
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: <>()\