Smarts SAM: Hookscript for MBIM domain does not seem to execute even though it is enabled; Hookscript details do not show in the Smarts SAM domain logs

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




The following conditions, events or system behaviors may be observed with this issue:

• Tried to enable a hookscript for MBIM domain to process the ServiceOffering/ServiceSubscriber alarms before those alarms are passed on to Smarts SAM.
• Hookscript does not seem to be executed although it is enabled in Smarts SAM Configuration (GMAC) and Reconfigure has been run in Smarts SAM.
• Hookscript details for MBIM domain are not showing in the Smarts SAM domain logs.
• Restarting both SAM and MBIM domains also doesn't resolve the problem.

Environment

VMware Smart Assurance - SMARTS

Cause

Impacted notifications are generated for Smarts SAM by the MBIM server. These notifications are not processed by ics-nl-processing.asl, which actually triggers a hook Script to process notifications.

Even though there is an option for enabling Hook Script for MBIM server as is done for the other Smarts Domain managers, the notifications are not processed by the hook scripts for Smarts SAM since they are created in Smarts SAM itself.

Resolution

To generate these notifications, you may be able to use sm_notify or a custom adapter script as an alternative to the hook script. ICS_BusinessImpact.asl is the file that MBIM uses to create Business Impacted notifications.