Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to configure DNS within a VMware Cloud Foundation DR impementation (53216)

Last Updated: 4/16/2018Categories: InformationalTotal Views: 2872Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides instructions for configuring DNS resolution in a disaster recovery configuration within VMware Cloud Foundation.

Resolution

About the vcfvrdrhelper.py utility

In a standard VCF deployment without DR protection, the vRealize Automation as well as the vRealize Operations components perform DNS resolution from the sddc-manager-controller and sddc-manager-utility VMs in the same Protected Site, referred to as Region A. When DR is configured, these components can failover to the Recovery Site, referred to as Region B.. When CMP components are running in RegionB, these components will perform DNS resolution from the sddc-manager-controller and sddc-manager-utility VMs in RegionB. The vcfvrdrhelper.py utility provides synchronization of the DNS records from the sddc-manager in RegionA to RegionB. Thus allowing sddc-manager in RegionB to resolve DNS queries for RegionA VCF components.

The synchronization is performed in one direction only. It is not supported to have RegionB synchronize back to RegionA.

It is expected that there is a 1:1 mapping from one RegionA to one RegionB. It is not supported to have multiple RegionA's synchronizing to the same RegionB.

vRealize Automation and vRealize Operations components should be deployed in RegionA only. RegionB should not have any vRealize Automation and vRealize Operations components deployed.

Installation

Prerequisites:

Network connectivity between management VLANs in RegionA and RegionB

IP address of sddc-manager-controller VM in RegionA

root password of sddc-manager-controller VM in RegionA

IP address of sddc-manager-controller VM in RegionB

root password of sddc-manager-controller VM in RegionB

Download the attached 53216_vcfvrdrhelper.py.zip file.

Use a file transfer utility to copy the 53216_vcfvrdrhelper.py.zip file to the /root directory on the RegionA sddc-manager-controller VM.

Log on to the sddc-manager-controller VM in RegionA as the root user.

Issue the following commands to extract and install the vcfvrdrhelper.py script:

unzip 53216_vcfvrdrhelper.py.zip
python vcfvrdrhelper.py --action install --region_b_hostname <RegionB sddc-manager-controller IP>

Note: The program will prompt for the RegionB sddc-manager-controller password. The root password is required only during installation and is not saved. The program is installed into the /opt/vmware/vcfvrdr directory in both regions. The program is started as systemd service during installation.

Update vRealize portgroup

In the VVD guidance documentation, one of the steps is to move the vRealize VMs from the original VREALIZE VLAN to a VXLAN created on the NSX vRealize-Edge. The VXLAN portgroup created for the vRealize-Edge must be updated in the Cassandra database. Issue a command similar to the following on the sddc-manager-controller VM in RegionA to update the portgroup in Cassandra:

/opt/vmware/vcfvrdr/bin/vcfvrdrhelper --action update-portgroup --portgroup vxw-dvs-9-universalwire-2-sid-12002-Mgmt-xRegion01-VXLAN

Note: Replace the portgroup name in the previous command, vxw-dvs-9-universalwire-2-sid-12002-Mgmt-xRegion01-VXLAN, with the name that was created in the vSphere Web Client.

Uninstallation

In the event that the utility needs to be uninstalled, thus removing the synchronization of DNS records from RegionA to RegionB, perform the following procedure.

Note: Uninstall must be performed separately in each Region.

Log on to the sddc-manager-controller VM in RegionA as the root user.

Issue the following command:

/opt/vmware/vcfvrdr/bin/vcfvrdrhelper --action uninstall

Repeat the previous step on the sddc-manager-controller VM in RegionB as the root user.

Note: Uninstallation does not remove DNS records from RegionA in the sddc-manager in RegionB.

Related Information

Checking sync status

Log in to the sddc-manager-controller VM in RegionA as the root user.

Display high level logs and error messages using the journalctl command.

journalctl -u vcfvrdr

Display the status file.

cat /opt/vmware/vcfvrdr/config/vcfvrdr_status.json

Note: You will see output similar to the following:

{
"last_logs": [
"2018-03-05T20:52:34.916648: vsr: cmd is /opt/vmware/vcfvrdr/bin/vcfvrdrhelper --action receive-records --region_a_hostname 20.1.0.5",
"2018-03-05T20:52:34.916944: vsr: rc is 0",
"2018-03-05T20:52:34.917046: vsr: out is Receive records completed",
"2018-03-05T20:52:34.917131: vsr: err is "
],
"max_sync_interval": 3600,
"min_sync_interval": 60,
"region_b_hostname": "20.2.0.5",
"syncer_consecutive_failures": 0,
"syncer_last_attempt": "2018-03-05T20:52:34.917331",
"syncer_last_success": "2018-03-05T20:52:34.917331",
"syncer_start": "2018-03-02T23:56:21.229713"
}

Explanation of fields in previous output:

min_sync_interval - minimum wait time in seconds between syncs to RegionB.
max_sync_interval - maximum elapsed time in seconds before a sync to RegionB.
region_b_hostname - the IP address of RegionB sddc-manager-controller
syncer_start - program start time
syncer_stop - program stop time. Program does not stop. If it is stopped, it is due to user requested stop using the systemctl command, or an abnormal failure. If the program terminated due to failure, systemd will restart the program in 10 seconds after failure.
syncer_last_attempt - time of last attempt to sync to RegionB
syncer_last_success - time of last successful sync to RegionB
syncer_consecutive_failures - number of consecutive times sync has failed. It is reset to 0 after a successful sync to RegionB.
last_logs - the latest logs that are relevant to the sync process.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

53216_vcfvrdrhelper.py.zip

Additional Resources

KB
•
Se produce el siguiente error al conectarse al escritorio mediante RDP: Su sesión de escritorio remoto finalizó (2100086)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

Take Our Survey

Support Assistant