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

SDDC Manager reports that the NSX Manager in a failed state due to the Distributed Logical Router (DLR) in a "grey" status (52528)

Last Updated: 7/31/2018Categories: InformationalTotal Views: 2713Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

VMware Cloud Foundation updates will fail due to the NSX Manager showing in a failed status.

The NSX Edge and Distributed Logical Router (DLR) that were created without a corresponding  appliance (VM) will have a status of GREY

You see the following in the output for the API call from the VRM VM to the NSX Manager to get the Edge status  [GET https://NSX-Manager-IP-Address/api/4.0/edges/edgeId/status ]

id>edge-12</id>
<state>active</state>
<edgeType>distributedRouter</edgeType>
<tenantId>6bc1f775-e09d-4b97-b59b-4830a9c8be35</tenantId>
<apiVersion>4.0</apiVersion>

-<recentJobInfo>
<jobId>jobdata-3921</jobId>
<status>SUCCESS</status>
</recentJobInfo>
<edgeStatus>GREY</edgeStatus>

You see messages similar to the following in the /home/vrack/notemanager/logs/nodemanager.log file.

df71-11e7-9b23-314c8da4633d of type NSX_MANAGER with status FAILED
2017-12-22 22:30:01.303 [080-exec-7] INFO  [    c.v.e.s.l.i.impl.LogicalInventoryServiceImpl]       Updating resource e617fe01-df71-11e7-9b23-314c8da4633d of type NSX_MANAGER with status FAILED
2017-12-22 22:30:01.309 [080-exec-8] INFO  [c.v.e.s.l.i.a.r.c.v.LogicalVRMInventoryController]    Updating resource with id e617fe01-df71-11e7-9b23-314c8da4633d of type NSX_MANAGER with blob {
"vcenterId": "e5f77db1-df71-11e7-9b23-314c8da4633d",
"controllerCluster": {
"clusterElements": [

},
{
"edgeType": "distributedRouter",
"resourceId": "e617fe01-df71-11e7-9b23-314c8da4633d:edge-6:distributedRouter",
"resourceName": "edge-6",
"upgradeAvailable": false,
"status": "GREY"

You see messages similar to the following in the /home/vrack/lcm/logs/lcm.log file:

2018-01-06 00:35:32.411 [pool-12-thread-2] ERROR [com.vmware.evo.sddc.lcm.audit.NsxAuditService]  auditId=9a2e4a1b-5b0b-4e9d-b1d7-997d95f826ba,resourceType=NSX_MANAGER,resourceId=00ebd171-ebfc-11e7-b1be-ed25d3ada4ce, Audit Failed Status:
RESOURCE_NOT_IN_GOOD_HEALTH, errorCode:RESOURCE_NOT_IN_GOOD_HEALTH
errorDescription:null
errorDetails: NSX Edge 00ebd171-ebfc-11e7-b1be-ed25d3ada4ce:edge-1:distributedRouter not 'GREEN' (status is: GREY)

2018-01-06 00:35:32.412 [pool-12-thread-2] INFO  [com.vmware.evo.sddc.lcm.adapter.inventory.impl.InventoryClientImpl]  auditId=9a2e4a1b-5b0b-4e9d-b1d7-997d95f826ba,resourceType=NSX_MANAGER,resourceId=00ebd171-ebfc-11e7-b1be-ed25d3ada4ce,
remove nsx manager 00ebd171-ebfc-11e7-b1be-ed25d3ada4ce due to resource status failed

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

Cause

As part of LCM pre-check it will  check whether the status of edge is Green or not. The NSX Manager will be flagged as in a failed status if any Edge/DLR is not in Green status. This "GREY" status for the DLR edge will stop all LCM update bundles from running, even if it does not include an NSX update .

Resolution

​Note: This is a known issue affecting:

VMware Cloud Foundation for Service Provider versions 2.4 -6889234, 2.3, 2.2 , and 2.1.

VMware Cloud Foundation versions 2.3.0, 2.2.x. and  2.1.x

Resolutions:

Resolution for VMware Cloud Foundation for Service Provider 2.4 6889234: Upgrade to  VMware Cloud Foundation for Service Provider 2.4.1-RELEASE-7541197 (LCM) ID 1334 Production version 2.4.0.4.

Resolution for VMware Cloud Foundation for Service Provider versions 2.3, 2.2, and 2.1:  No resolution. A fresh install of version 2.4 and an upgrade to version 2.4.1 is required.

Resolution for VMware Cloud Foundation versions 2.2.x and 2.3.0:  Upgrade to version 2.3.1 .

Resolution for VMware Cloud Foundation version 2.1.x: Contact VMware Customer Support.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
将 VMware Cloud Foundation 升级到版本 2.3 后，“VDI 工作流：配置 Horizon View Cloud Pod 架构”的任务挂起 (52397)

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