Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 446989
Smarts SAM: Is it possible to suppress "ics-nl-processing.asl" messages in SAM logs?
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
The following ics-nl-processing.asl messages in Smarts SAM logs: [April 15, 2013 7:42:44 AM GMT+00:00 +505ms] t@1372932416 Incharge-SA_NL-Driver-HyperNotif EMS-*-DISCARDED_EVENT_DISP-DISCARDED EVENT: NOTIFICATION-JuniperWX_XTCMB006_WANPerformanceDegraded - Reason: CLEAR received with out a prior NOTIFY or SUSPEND - Source: Incharge-SA [April 15, 2013 7:42:44 AM GMT+00:00 +691ms] t@1345616192 Incharge-SA_NL-Driver-HyperNotif ASL_MSG-*-ASLP-ics/ics-nl-processing.asl: processNLNotifyV2 - DISCARDED NOTIFICATION: NOTIFICATION-SNMPTrap_PGOT062_LinkDown-Ser ial0/2/0_:25 Reason: could not find the notification object [April 15, 2013 7:42:44 AM GMT+00:00 +868ms] t@1366628672 Incharge-SA_NL-Driver-HyperNotif ASL_MSG-*-ASLP-ics/ics-nl-processing.asl: processNLNotifyV2 - DISCARDED NOTIFICATION: ICS_Notification::NOTIFICATION-SNMPTrap_VB RU000_.1.3.6.1.4.1.3043.6.4.0.3_206_202 Reason: no change in occurence count for MOMENTARY [April 15, 2013 7:42:44 AM GMT+00:00 +881ms] t@1366628672 Incharge-SA_NL-Driver-HyperNotif EMS-*-DISCARDED_EVENT_DISP-DISCARDED EVENT: NOTIFICATION-JuniperWX_XTCMB006_WANPerformanceDegraded - Reason: Already Cleared - Source: Incharge-SA [April 15, 2013 7:42:44 AM GMT+00:00 +887ms] t@1366628672 Incharge-SA_NL-Driver-HyperNotif ASL_MSG-*-ASLP-ics/ics-nl-processing.asl: processNLNotifyV2 - DISCARDED NOTIFICATION: ICS_Notification::NOTIFICATION-SNMPTrap_VB RU000_.1.3.6.1.4.1.3043.6.4.0.3_206_203 Reason: no change in occurence count for MOMENTARY
Cause
This messaging was intentionally introduced in Smarts SAM to log all the notifications which are discarded without notifying or without clearing. This functionality was introduced after multiple issues were reported such as notifications being missed. This logging collects information on these types of issues to aid in the analysis and troubleshooting of why notifications are not being processed, to help determine the underlying reason for the issue.
Resolution
There is no way to disable these messages.
