When applying a different protocol (not a different version or range, so a protocol with a different name) to an existing element, the DB element data for the specified element is deleted.
This causes settings as credentials no longer being available and the operator needing to re-enter the credentials.
Use case:
When upgrading a device using IDP the outcome is that a different protocol (CI type) needs to be applied to the element. These protocols are in-line with each other (similar PIDs, etc.) and are having their own production version as we can only have 1 production version per protocol.
Is the expected behavior that the element at startup reeds its element data from the DB and has the stored parameters at startup, no matter whether a new protocol was applied?
Or is it indeed intended when applying a new protocol, the element data is removed for the particular element?
On an additional note, the element data is only deleted when changing the protocol on an active element. When you stop the element first and then change the protocol to then activate it again, the element data is still available.
Hi Brecht,
I am not sure what is the expected behavior, but I will expect indeed that the element data is deleted to avoid inconsistencies.
Regarding your specific case, I remember that IDP provides a way to update values after an element is provisioned (see Update Property Script). Basically you can run a script that can be used to set parameters once the element is provisioned. You can run the script to set the credentials again once the element is provisioned.
The drawback in this case is that you will need to store the credentials in another place. I believe that the best place to store credentials should be the Credential Library. However, as far as I know, it is not possible (from a script) to read credentials from the credentials library.
Currently IDP supports the option to read credentials from the Credential Library (IDP 1.1.18), but this is only valid for SNMP credentials (that are used in the element settings).
Hi Miguel,
I would expect that the element data is NOT deleted.
As a user you’re provided with the popup by which you need to acknowledge possible impacts in case of using the same element. In case you do not want to acknowledge this, you simply select the option that creates a new element instead.
By so, what would be the point of asking the user for the acknowledge of impact if we’re cleaning up everything to avoid certain issues?
At this point, the outcome whether the element data should or should not be deleted still remains a mystery.