Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 notification in a state called WAS_ACTIVE. (382918)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3281Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

SMARTS notification in a state called WAS_ACTIVE

After re-starting the OI server or SAM server, previously active events are now showing as WAS_ACTIVE
A notification remains active in AM (state is actually WAS_ACTIVE) for a long time although the underlying domain hasn't got it anymore

Cause

Notifications marked as WAS_ACTIVE remain in the WAS_ACTIVE state until the Global Manager can verify their status.

Resolution

If the Global Manager is not able to reconnect to the underlying domain(s) that generated these notifications in 1800 seconds (30 minutes), the value of the severity attribute is set to 4, changing the color of the notification in a Notification Log to blue.  The value of 1800 seconds is referred to as the detachTime.  When the connection between the Global Manager and the underlying domain(s) is re-established, the Global Manager does the following:

Notifications that are still active in the underlying domain have their Event State changed to ACTIVE and their severity value updated accordingly.

Notifications that have cleared in the underlying domain remain in the WAS_ACTIVE state until the attachTime has elapsed.  The default value of attachTime is 6000 seconds (100 minutes).  However, the actual value that is used to calculate when to clear the notifications is determined as follows:
When the uptime for the underlying domain is greater than the attachTime, then the value is 240 seconds plus the smoothing interval.  The smoothing interval is specified in the DomainType section of the ics.conf file.
When the uptime for the underlying servers is less than the attachTime, the value is attachTime minus uptime.  For temporary disconnects, this value is typically used to determine the state of WAS_ACTIVE notifications.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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