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

VMware Cloud on AWS - VMs running on VMC can't communicate with connected Amazon VPC network (76385)

Last Updated: 10/2/2020Categories: TroubleshootingTotal Views: 4966Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Connections from VMs running on VMC to connected Amazon VPC network fail and vice versa.

The status of all routes to the VMC network is shown as "blackhole" in the main route table in connected Amazon VPC.

The "Active Network Interface" id shown in VMC portal is different from the ENI id shown in the main route table in connected Amazon VPC.

Purpose

This article provides information on how to resolve issues if you find connection problem between VMC on AWS and connected Amazon VPC network.

Cause

The established link between VMC and connected AWS VPC will be broken if the necessary role named "vmware-sddc-formation-xxxxxxxx-xxxx-xxx-RemoteRole-xxxxxxxxxxxx" is removed accidentally in your IAM roles. This causes VMC preventing to update the main route table in connected Amazon VPC.

Resolution

To resolve this issue, the following two steps have to be done.

Re-establishing the link between your organization and Amazon VPC network.

Re-establishing the link between your SDDC and Amazon VPC network.

1. Re-linking between your organization and Amazon VPC network.

Login to https://vmc.vmware.com

Select "VMware Cloud on AWS"

Click "CREATE SDDC" button

Enter a temporary name in "SDDC Name" field and click "NEXT" button

Select "Connect to AWS now" and choose "Connect to a new AWS account"

Click "OPEN AWS CONSOLE WITH CLOUDFORMATION TEMPLATE" button

Login to AWS console after the page transition

Select "I acknowledge that AWS CloudFormation might create IAM resources" and click "Create" button

Wait for the stack creation to be completed

Note: You don't have to create a new SDDC. You can quit after the stack creation on AWS side.

2. Re-establishing the link between your SDDC and Amazon VPC network.
Please contact VMware support with the details after you performed the No.1 since the No.2 has to be done from VMware side.

Related Information

Deploying and Managing a Software-Defined Data Center:
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-BC0EC6C5-9283-4679-91F8-87AADFB9E116.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
使用 IWA 标识源时，在域控制器上记录事件 ID 2889 (78644)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
NSX の vSphere with Tanzu 展開で NCP オプション configure_t0_redistribution が True に設定されている (79392)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant