Device level alarms correlation to ServiceOffering Impacts in BIM when Interface (Network Adapter Redundancy Groups) are associated with ServiceOffering
search cancel

Device level alarms correlation to ServiceOffering Impacts in BIM when Interface (Network Adapter Redundancy Groups) are associated with ServiceOffering

book

Article ID: 303905

calendar_today

Updated On: 06-08-2025

Products

VMware Smart Assurance

Issue/Introduction

  • How are device level alarms correlated to ServiceOffering Impacts in Smarts Business Impact Manager (Smarts BIM) when Interface (Network Adapter Redundancy Groups) are associated with ServiceOffering?
  • What element in the device notification is used by Smarts BIM to correlate to the service offerings in the BIM topology?

Environment

All supported Smarts releases

Resolution

Whenever BIM driver receives a notification, Smarts SAM receives the OccurredOn device for that notification. Using this OccurredOn device, Smarts SAM recursively gets all the related instances which could be impacted because of this notification and we repeat the same till we reach the top of the hierarchy.

Example:

The following four lines shows how the NetworkAdapterRedundancyGroup, Router and ServiceOffering are related:

  • Router::network:##.##.##.## is composedOf NetworkAdapterRedundancyGroup::NARG-192
  • NetworkAdapterRedundancyGroup::NARG-192 is partOf Router::network:##.##.##.##
  • NetworkAdapterRedundancyGroup::NARG-192 is memberOf ServiceOffering::SRVO-192168
  • ServiceOffering::SRVO-192168 consistsOf NetworkAdapterRedundancyGroup::NARG-192

Now when your environment receives a Router down notification, the OccurredOn device for this notification is Router itself. Since the Router is composedOf NetworkAdapterRedundancyGroup, the NetworkAdapterRedundancyGroup is impacted. And since NetworkAdapterRedundancyGroup is a memberOf ServiceOffering, the ServiceOffering is also impacted and the BIM driver creates a ServiceOffering Impact notification.