Hello DataMiner community,
We are planning to do a transfer of the Views and some elements from a system (using DataMiner version 9.6) to a new setup using 10.3.
Regarding the elements, we could already successfully transfer some of them, but we found a couple of issues that we would like your insights.
When importing the ExportData.csv file containing the elements to be created, besides changing the dataminer ID and removing the element IDs, we noticed that from 9.6 to 10.3, there are some differences in the header of the csv file. Namely, in the newer version there were added the following headers: ReplicationMaxBuffer,ReplicationMinBuffer,ProtocolType,CredentialGUID,TLS,AllowedIpAddresses,ConnectTimeoutTime.
Besides that, we couldn’t find any differences between the two headers (neither on naming nor on sorting).
After this brief overview, I am now finding and blocked with an issue:
- When importing elements with more than one connection (2 SNMP and 1 SSH in this case), the first connection works just fine, but the other ones don’t get correctly filled (they are missing the IPs, ports,...). For this one, I suspect that there is a shift in the csv file that it is causing the loss of all the configuration for the other connections. I did a comparison from an export from 10.3 and the export from 9.6, but besides some custom properties and trend/alarm templates, I cannot find what is shifted.
Does anyone already did this and knows what it might be wrong and how can I fix it?
Thanks in advance for your help!
*** This is not an answer to the original post but an addendum to one of the comments above to the response from Joao ***
Hi Joao, on the left are headers and on the right are corresponding values. As you can see it appears we are reusing Serial fields for SNMPv3 values in the .csv export. What would be helpful to clarify is whether header on row 20 and 25 are reused for SNMPv3 values and if so what are they?