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 SAM: How long do notifications remain in WAS_ACTIVE state in Presentation SAM before clearing, after underlying SAM is disconnected? (324985)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

How long do Smarts SAM notifications remain in WAS_ACTIVE state in Presentation SAM before clearing, after underlying SAM is disconnected?

Time taken for notifications in WAS_ACTIVE state to clear is inconsistent.

Cause

A notification can be WAS_ACTIVE state when a SAM server disconnects from the underlying domain that is the event source, or when a Presentation SAM disconnects from its underlying aggregation SAM. In this case, all active notifications from the disconnected, underlying SAM domains are marked WAS_ACTIVE.

Resolution

How long a notification remains in WAS_ACTIVE is based on a number of metrics and an underlying algorithm. WAS_ACTIVE notifications remain in this 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 'attachTime' determines the delay before reconnected but un-renotified WAS_ACTIVE Notifs are auto-cleared.

Default = 6000.

There are also two hard coded parameters to be considered:

attachFlappingTime (1200)

attachTimeShort (900 )

Depending on what type of disconnect occurs, one or the other of these parameters will be added to your configured attach time plus the smoothing interval.

When the uptime for the underlying servers is less than the attachTime, the value is attachTime minus uptime plus the smoothing interval. Therefore, about the best you can achieve by the configuration above is a WAS_ACTIVE auto-clear time of about 20+ minutes.

Since the move to xml config, attachTime is defined as below in the ics-config.dtd ( /conf/ics/ics-config.dtd )

<!ELEMENT domaintype (description?, hook?, domainname*,

update?)>

<!ATTLIST domaintype

name CDATA #REQUIRED

dxaConfFile CDATA #REQUIRED

MinimumCertainty CDATA #REQUIRED

SmoothingInterval CDATA #REQUIRED

attachTime CDATA #IMPLIED

detachTime CDATA #IMPLIED

timeOut CDATA #IMPLIED

timeOutBE CDATA #IMPLIED

timeOutFE CDATA #IMPLIED

enable (TRUE " FALSE " true " false " True

" False) "FALSE"

timestamp CDATA "0"

>

These values cannot be edited here, but can be added to the <domainType> section of the domain type xml file of interest. (see Example below). You can confirm a change to this configuration, by checking the  'attachTime' attribute of the InChargeDomain (SAM) of interest in the Topology Browser module.

Example of the syntax of a change to ics-default.xml

<ics_config version="2">

<domainconfig>

<domaintype

name="INCHARGE-AM-SUITE"

dxaConfFile="dxa-conn.conf"

MinimumCertainty="0.01"

SmoothingInterval="65"

attachTime="XXXX"

detachTime="XXXX">

<description>Type for INCHARGE-AM-SUITE</description>

<hook enable="False">ics/dxa-sample-hook.asl</hook>

<domainname>INCHARGE-AM</domainname>

<domainname>NCM</domainname>

<domainname>INCHARGE-AM2</domainname>

</domaintype>

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