Hi,
We are still using elements Generic Ping v2.1.0.11 and need to upgrade them to v3.1.2.15 without recreating the elements as they are linked to services, etc. However, upon changing the protocol version in the same element, the first index’s description from v2 is used as parameter description in v3, best explained on below screenshots. This affects all rows in the v3 ping element as it is a parameter description that is different. Even the Description in Ping v2 first line is set to “None” (Not initialized) or empty string “”, the column parameter description is still “Ping 01 Status”.
The rows are not migrated, but that's not the issue, we have script that can export before/import after upgrade.
Can this be fixed with some special SetParameter() method or other SLNet message while still in v2 or after upgrade to v3?
To replicate, create a Generic Ping element v2, add one row with description, change version to v3, see column header and parameter description.
Thank you.
Ping v2
Ping v3
Hi Martin,
I was able to replicate the behavior.
Going from Generic Ping v2.1.0.11 to v3.1.2.15 is a big jump. Usually, we reserve the first number (2 to 3) to indicate that the two versions differ significantly from each other. That is certainly the case for these two drivers. Despite bearing the same name, they are very different from each other.
DataMiner even shows a warning when trying to change the version.
I think it is safer in this case to recreate the element.
On top of losing the rows and the issue with the columns, who knows what other problems might be found later?
I know this is not the answer you wanted, but I truly believe it will be faster and less problematic (even with the changes to the services).
Consult with your TAM, who understands your system and can give you more tailored advice.
Regards
Hi Miguel,
Thanks for your response and guidance. We discussed with TAM separately.