Operational Defect Database
BugZero updated this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 462743
Smarts SAM: Why does SAM display Notifications with Occurrence count as 0 and traps have firstnotify and lastnotify as Never?
Last update date:
4/16/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
SAM displays notifications with Occurrence count as 0 and the "firstnotify" and "lastnotify" as never.
Resolution
SAM started without underlying Adapter Platform domain manager which caused traps to have Never for first notify and last notify. There also was a bug identified with the First Notify and Last Notify attrributes of the trap notifications. The fix is now available, Please install Smarts 9.2.2 Patch 8.Please read the below info15063801 [ PR 19188 ] RP 8 Problem Description: The Global Manager does not update the FirstNotify and LastNofity times for notifications received from Adapter Platform if the event state in Adapter Platfrom is WAS_ACTIVE. In the Console, this time is displayed as Never. Description of Fix: Modified the notification processing to enable the Global Manager to update SUSPENDED notification after reconnecting to Adapter Platfrom or an underlying Global Manager. Also, made a relevant change in DXA to update occurrence count when a SUSPENDED notification becomes ACTIVE. Changed Components: rules/ics/ics-nl-processing.asl lib/sm_ics_ems
Related Information
Need to start underlying domain.
