RE: Indication Filter Association to Indication Subscription Missing

An update of what we have learned:

When a client creates our own, subclassed version of an IndicationFilter, the key fields that we expect to be automatically filled in aren't.  So, for example, the SystemName property is blank.  I am thinking that this should not be the case.  Despite that, finding a IndicationSubscription from that IndicationFilter works.

When a client creates a CIM_IndicationFilter, all the key fields we expect to automatically be filled in are.  Even so, there are no IndicationSubscription associations to traverse from the IndicationFilter, which is wrong.

On testing this further, I created a client that manually filled in the key fields for the subclassed version of the IndicationFilter.  That gave us a IndicationFilter with all the keys filled in, as it should be.  But, when creating the IndicationSubscription for it, the client gets an error of CIM_ERR_NOT_FOUND.  

Note:  I at first dismissed this as an issue since I thought that if having the extra fields set, if anything should help, not hurt finding associations.  

-----Original Message-----
From: Verbrugge, Troy [mailto:[email protected]] 
Sent: Friday, October 02, 2015 11:53 AM
To: [email protected]
Subject: Indication Filter Association to Indication Subscription Missing

We are running into an issue dealing with associations and indications.  My guess is that it is something we are doing wrong, but we can't figure out what that might be.

We have some tests on our provider that act as clients.  One of those tests is trying to create and verify the existence of an subscription.  Here are the steps:

1. We create our own IndicationFilter, which is a subclass of CIM_IndicationFilter in our own namespace 2. We create an event handler (CIM_ListenerDestinationCIMXML) 3. We create a CIM_IndicationSubscription with that event handler and indication filter 4. We then query for association names on the filter where the association class is an indication subscription.
5. We verify that an association exists.

This works fine.  But, when I change step 1 to directly create a CIM_IndicationFilter instead of our subclass, we don't get any associations back in step 5.  

Some other notes:

1) Even without the association being present, we are still getting indications.
2) The created filter for CIM_IndicationFilter has more fields filled out, while our sub-classed version does not:
CIM_IndicationFilter: //127.0.0.1/root/netapp/santricity:CIM_IndicationFilter.CreationClassName="CIM_IndicationFilter",Name="TemporaryPoolNameChange",SystemCreationClassName="CIM_ComputerSystem",SystemName="WICC01P01-00057.ved.eng.netapp.com"

NETAPP_IndicationFilter: //127.0.0.1/root/netapp/santricity:NETAPP_IndicationFilter.CreationClassName="",Name="TemporaryPoolNameChange",SystemCreationClassName="",SystemName=""

Thanks for any help.


Troy Verbrugge
AppAware Engineer
5400 Airport Boulevard Suite 100
Boulder CO 80301
303-381-4293