Alarms are not picked up by AlarmNotifier Filter, if the devices are resources of Services, the alarms that are affecting the UIM devices are not sent.
A SANM policy filter is in place, to send only alarms that are affecting devices in the Global Collection
If the devices are directly in a Global Collection, all notifications are sent.
If the devices are resources of Services, the alarms that are affecting the UIM devices are not sent.
This can be observed when any devices are added as resources of Services.
When a service/device added to any Global collection, CollectionUniqueKeyString (0x12e58) attribute of service/device will be updated with the unique key of the Global Collection.
But, this attribute of devices that are added as resources of services won’t get updated as devices are not directly associated to Global Collection.
Only CollectionUniqueKeyString of services will be updated.
If a SANM policy filter by Severity and based on Global Collection name, notification will be sent for the alarms raised on devices that have CollectionUniqueKeyString (0x12e58) as Global Collection name.
An alarm is generated on devices directly associated to a Global Collection, which contains CollectionUniqueKeyString value as Global Collection name and notifications will be sent for these devices.
If an alarm generated on service rather than devices of service, then notifications will be sent for the service.
But here, alarms generated on devices that are part of service, these devices do not have CollectionUniqueKeyString attribute value as Global Collection name.
Hence, alarm fails to pass through SANM policy filter and notifications won’t be sent. This behavior is functioning as designed.
To achieve customer requirement, to get alarm notifications of devices added as resources of a service, a SANM filter must be created, based on either model type/model name of those devices, instead of Global Collection name.