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: Understanding the different EventState values of Notifications in Smarts SAM Domain. (338503)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Understanding the different EventState values of Notifications in SAM.

Resolution

When a notification is created (notified) in SAM, the direct source that notified it is marked as an ACTIVE source for that notification.

A source is one whose name is passed along with notify() function.  There may be multiple sources that report an event in different states (ACTIVE, SUSPENDED, INACTIVE).  The notification state becomes WAS_ACTIVE when a running ACTIVE source disconnects from SAM.

(Note that a source need not be a running InCharge domain server; rather it is the name of a source that is known to report about a given event or notification.)

So the trap manager ("Trap Adapter"), or syslog manager ("Syslog Adapter"), or a source that is specified in sm_ems command are direct sources of OI/SAM notifications.  In case of DXA, the source is a domain manager, which can be AM-PM, OI, or another SAM.

It is responsibility of individual adapter or program to update the state of a notification that is previously notified by it when changes occur.  SAM treats both types of sources (a real domain or a named source) the same way:  If the last state was ACTIVE for a given source, it will be changed to WAS_ACTIVE if:
a) SAM is restarted
b) SAM is disconnected from the domain server.

In either case, all the sources for all notifications are marked as WAS_ACTIVE.  The state of a source of a previously active notification remains WAS_ACTIVE so long as the source provides an update.  The lack of an update is interpreted as CLEAR event only in the case when SAM is reconnected to the InCharge domain manager via DXA after a waiting period.

So, if a domain remains disconnected, or a non-running source does not clear or re-notify the event, WAS_ACTIVE state is maintained forever.  If it is a domain and will no longer run, it should be removed from ics.conf.  If it is an sm_ems source, sm_ems should either clear or re-notify the notification after SAM becomes available again.  In the case of the Trap or Syslog Adapters, a clear or re-notify of the trap or syslog message will correct the state of the notification.  Otherwise, it will remain WAS_ACTIVE.  When OI has a notification as WAS_ACTIVE, SAM suspends it indicating that no updates regarding the notification are currently available (from its sources).

The best approach to avoid these situations is to assign an expiration to Trap or Syslog Adapter sourced notifications.  Expiration should not be so short as to generate multiple notifications.  Notifications generated by sm_ems are custom and have to be updated when SAM is restarted.

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