Repairing the Cross-Region-Env Environment in vRealize Suite Lifecycle Manager for VMware Validated Design 5.0.x

Products

• VMware Aria Suite

Issue/Introduction

This article provides the steps required to repair the Cross-Region-Env environment card with the correct product inventory and topology. It also ensures that a baseline for each product is created for configuration drift analysis.

Symptoms:

• Greenfield deployments of VMware Validated Design 5.0.x using VMware Cloud Builder contain multiple product cards for vRealize Operations, vRealize Automation, and vRealize Business for Cloud for the the Cross-Region-Env environment card in vRealize Suite Lifecycle Manager.

Environment

VMware Validated Design for Software-Defined Data Center (SDDC)
VMware Validated Design for Software-Defined Data Center (SDDC) 5.0.x

Resolution

You remove the Cross-Region environment that contains vRealize Operations Manager, vRealize Automation, and vRealize Business from the managed vRealize Suite Lifecycle Manager inventory. 
 
IMPORTANT:
 
Ensure that the vRealize Operations Manager, vRealize Automation, and vRealize Business product deployments are NOT deleted from the vSphere inventory. During this procedure, you remove only the Cross-Region-Env environment card and its product card objects from vRealize Suite Lifecycle Manager.
 
You create a new environment in vRealize Suite Lifecycle Manager to import vRealize Operations Manager, vRealize Automation, and vRealize Business product deployments. You input parameters to define the infrastructure details used during the environment import and scaling of the product deployments during day-two operations. 
 
NOTE:

• This artlce uses the example hostnames and IP addressed from the VMware Validated Design. Adjust for your deployment.
• This article is written for a dual-region deployment. If your environment is single-region, skip each step for +Add Another for vCenters.

 
Procedure

1. Log in to vRealize Suite Lifecycle Manager user interface.
   1. Open a Web browser and go to https://vrslcm01svr01a.rainpole.local/vrlcm. 
   2. Log in using the following credentials.

Setting	Value
Username	admin@localhost
Password	vrslcm_admin_password

2. On the Home page, click Manage Environments. 
3. On the Environments page, click the ellipse on Cross-Region-Env environment card and select Delete Environment. 

The following notification message appears: 

The environment Cross-Region-Env and all the products in the environment will be deleted from LCM.

4. In the Delete environment Cross-Region-Env window, click Delete. 

IMPORTANT:

To prevent permanently deleting product deployments from the SDDC, ensure the following: 

• The Delete related virtual machines from vCenter option is NOT selected. 
• The Delete related Windows machines option is NOT selected. 
• If the icon and text area in the modal window change to red, click Cancel. 
• If a list of virtual machines appears, click Cancel. 

The Delete Environment Cross-Region-Env modal window updates to:

Request to delete the environment submitted successfully.

 

5. In the Delete Environment Cross-Region-Env window, click Close.

The Cross-Region-Env environment card is dimmed in the list of environments managed by vRealize Suite Lifecycle Manager.

 

6. Verify that the Cross-Region-Env environment is deleted.
   1. In the Navigator pane, click Requests and validate that the status of DELETE_ENVIRONMENT_FROM_LCM in the All Requests column is COMPLETED.
   2. On the Navigator pane, click Environments and verify that the Cross-Region-Env environment is deleted from vRealize Suite Lifecycle Manager.

 

7. Click Create Environment In the navigation.
8. On the Create Environment page, enter the following information, and click Next.

Setting	Value
Data Center	cross-region-dc
Environment Type	Production
Environment Name	Cross-Region-Env
Administrator Email	deployment_admin_email
Default Password	deployment_admin_password
Confirm Default Password	deployment_admin_password
Join the VMware Customer Experience Improvement Program	Selected

9. On the Products tab, select the check box and the radio button option for the following vRealize Suite products and click Next.

Product	Radio Button Option
vRealize Operations	Import
vRealize Automation	Import
vRealize Business for Cloud	Import

10. On the Product Details page, select the vRealize Business for Cloud tab and enter the following information for Product Properties for Import.

Setting	Value
vRB FQDN	vrb01svr01.rainpole.local
vRB Root Password	vrb_root_password
vRB Standalone	selected
vIDM Enabled	Deselected
vRA Cafe Host Name	vra01svr01.rainpole.local
vTA Cafe SSO Admin User	vra-localdefaultadmin
vRA Cafe SSO Password	vra-localdefaultadmin_password

11. On the vRealize Business for Cloud tab, click +Add Another for vCenters and select lax01m01vc01.lax01.rainpole.local from the vCenter Host drop-down menu.
12. On the Product Details page, select the vRealize Automation tab and enter the following information for Product Properties for Import.

Setting	Value
Primary Node Hostname	vra01svr01a.rainpole.local
vRA Primary Node Root Password	vra_root_password
Default Tenant Administrator Password	default_tenant_admin_password
vRA Tenant Admin User Name	vra-localdefaultadmin
vRA Tenant Admin Password	vra-localdefaultadmin_password
IaaS Username	rainpole.local\svc-vra
IaaS Password	svc-vra_password

13. On the vRealize Automation tab, click +Add Another next to vCenters and select lax01m01vc01.lax01.rainpole.local from the vCenter Host drop-down menu.
14. On the Product Details page, select the vRealize Operations tab and enter the following information for Product Properties for Import.

Setting	Value
vROPS Root Password	vrops_root_password
vROPS Primary Node IP Address	192.168.11.31
vROPS Admin Password	vrops_admin_password

15. On the vRealize Operations tab, cli ck +Add Another next to vCenters, select lax01m01vc01.lax01.rainpole.local from the vCenter Host drop-down menu, and click Next.
16. On the Summary page, review the information and click Submit.
17. In the Navigator pane, click Requests and validate that CREATE_ENVIRONMENT for Environment Name:Cross-Region-Env in the Request Info column is INPROGRESS.
18. In the Requests page, click the INPROGRESS and monitor the steps of the import graph until the request is COMPLETED.
19. Click Environments.
20. On the Environments page, click the ellipse on Cross-Region-Env environment card.
21. Under Configuration Drift, select Save Baseline to save the configuration state.
22. Verify that the Baseline Save Initiated banner appears on the environment card.

Additional Information

Impact/Risks:
Failure to repair the Cross-Region-Env environment card will impact day-two operations in the environment. For example: patching, Marketplace content deployment, certificate management, scale-out, and future upgrades for the VMware Validated Design.