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

Smarts: Fail-over server has domains set to unmanaged when it was deployed as managed (329741)

Last Updated: 12/17/2018Categories: TroubleshootingTotal Views: 8022Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts domains configured to be managed by the Smarts fail-over manager are in an unmanaged state

Cause

This issue can occur because the Smarts domains were not available when the Smarts fail-over manager was started. When the fail-over manager is started, it checks to see if domains are started and available for communication. If the domains are not available for communication when the fail-over manager is started, the fail-over manager will set the domains to explicitly unmanaged. This behavior is by design, because if there are not two domains to pair up and monitor, then there is nothing to synchronize with the active domain nor to fail over to a standby domain.

If the standby domain becomes unavailable, the fail-over domain will also explicitly unmanage the fail-over pair.

Resolution

This is the designed behavior of the product. There is no automation in the fail-over manager that checks for availability and the whether to re-manage the domains when the domains were not available for communication upon start up of the fail-over manager, nor will it re-manage the domains if a standby domain becomes available for communication after being unavailable.

When there is an issue that causes the Smarts fail-over manager to unmanage Smarts domains, the users/administrators have to manually and explicitly re-manage the domains in the fail-over manager when the domain is available again.

Related Information

There is an internal request to improve the functionality of the fail-over manager that will allow it to be Smart enough to look for domains for a period time before unmanaging them.  If the customer also desires this ability then they will need to submit an enhancement request using the information in knowledge base article https://emc--c.na5.visual.force.com/apex/KB_HowTo?id=kA0700000004HGx

The more requests for this feature the greater the likelihood it will be added to the product.

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant