I have a device that holds 5 SDMPs all with the same IP address as the chassis, currently the drivers connect to each SDMP using the bus address filed in the element settings.
I’m looking for a way to carry out one Discovery query to create the (up to) 5 SDMP elements. The 5 elements can be each 1 of three apps depending on the response. How do I use the response to populate the provisioning configuration?
I can see in my response that the Slot, (bus address for the element) the app name, (could be used to select a driver) and device name (could be used to name the element) are all present. Also. ‘populated’ ‘true’ could be used to decide whether an element needs to be created or not.
Is it possible in the CI type manager to use data from the response as a bus address placeholder, for example. Below I have the Discovery GET JSON, the response (just the first slot responses to save a lot of text) and an example of what I’m trying to do.
Hi Ross,
IDP is able to use keywords and perform replacement with values from discovery (see this question Element name configuration in IDP - DataMiner Dojo for more details on keyword replacement)
However, you cannot link the replacement to a keyword within a list
So for your use case, the best option I see is for you to create 5 CI Types (one for each value of the Bus Address) and configure the specific Bus Address and discovery conditions in each of them.
You can use the duplicate feature to create the first and then just adapt the subsequent ones
And this way you add all of them to a discovery request and IDP will take care of matching and creating with the correct settings.
Hi Ross,
Regarding the issue you are experiencing with the Bus Address not getting set correctly when creating an element, it was indeed an issue but it got addressed in IDP version 1.1.14 as documented in DMS RN 7 of the following link
https://community.dataminer.services/documentation/dataminer-idp-1-1-14-release-notes/#29868
Could you please confirm if the version of IDP you are currently running?
Hello, our IDP version is 1.1.12-2103
In that case, I would advise the update to 1.1.14-2112 CU1 and double-check that it solves the issue you are facing
Thanks Joao that is useful, I didn’t think about adding all the Discovery requests into 1 Discovery Profile which might help me. One thing I’ve noticed on a test today, the Bus address element settings don’t write to the element that’s created. Is there a known bug for this at all?