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 Foundation on VxRail 3.7.x bringup fails while getting Portgroup details from the vCenter Server (71019)

Last Updated: 4/19/2021Categories: InformationalTotal Views: 1151Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The below messages are seen in /var/log/vmware/vcf/bringup/vcf-bringup-debug.log

2019-06-27T12:38:24.472+0000 [bringup-app-ems,[3f16407a6bcfd003,281d]] ERROR [c.v.e.s.b.a.t.v.MigrateVmsToMgmtPortGroupBringupAdapter,pool-2-thread-10] Failed to get vCenter server network details from vCenter

2019-06-27T12:38:24.472+0000 [bringup-app-ems,[3f16407a6bcfd003,281d]] ERROR [c.v.e.s.o.c.ProcessingTaskSubscriber,pool-2-thread-10] method invocation target not found

java.lang.reflect.InvocationTargetException: null

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.getParams(ProcessingTaskSubscriber.java:266)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:299)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:431)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:96)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:55)

at reactor.bus.EventBus$3.accept(EventBus.java:317)

at reactor.bus.EventBus$3.accept(EventBus.java:310)

at reactor.bus.routing.ConsumerFilteringRouter.route(ConsumerFilteringRouter.java:72)

at reactor.bus.EventBus.accept(EventBus.java:591)

at reactor.bus.EventBus.accept(EventBus.java:63)

at reactor.core.dispatch.AbstractLifecycleDispatcher.route(AbstractLifecycleDispatcher.java:160)

at reactor.core.dispatch.MultiThreadDispatcher$MultiThreadTask.run(MultiThreadDispatcher.java:74)

at org.springframework.cloud.sleuth.instrument.async.LocalComponentTraceRunnable.run(LocalComponentTraceRunnable.java:53)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Caused by: java.lang.IllegalStateException: Failed to get vCenter server network details from vCenter

at com.vmware.evo.sddc.bringup.adapters.toplugin.vxrail.MigrateVmsToMgmtPortGroupBringupAdapter.getVcenterNetworkPortGroupName(MigrateVmsToMgmtPortGroupBringupAdapter.java:131)

at com.vmware.evo.sddc.bringup.adapters.toplugin.vxrail.MigrateVmsToMgmtPortGroupBringupAdapter.toPlugin(MigrateVmsToMgmtPortGroupBringupAdapter.java:87)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

After the VxRail first run the portgroup names created on the management ESXI hosts cannot be changed as automated bringup will look for the pre-defined port group names configured during VxRail first run.

Resolution

This is a expected behavior.

Workaround

To resolve the bringup failure, the portgroup names will need to be reverted to their original names and the Cloud Builder will need to redeployed and the process will need to be started from the beginning.

To change the portgroup names, please see the official documentation here.

To redeploy the Cloud Builder VM, please see the official deployment documentation here. Once the Cloud Builder VM is deployed successfully please continue the bringup process.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
V2 SEG のログ収集 (50116985)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
エンドユーザーへの Workspace ONE 導入の概要 (2960364)

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 Foundation

Related Versions:

VMware Cloud Foundation on VxRail 3.7.x

Take Our Survey

Support Assistant