- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-31-2020 02:45 AM
Hi Community,
I'm exploding... did a few Juniper migrations lately and we have an issue, that the address import is not working as expected.
The object names are fine, but all the addresses got value "1.1.1.1" - lot's of manual work or scripting.
So I did CSV Import to got duplicate entries with the right ip-values and merged them (CSV as merge-primary).
That worked.
Now, even a simple CSV import of csv-file "foo;1.2.3.4;255.255.255.255" doesn't work.
I got no values in preview output and when doing the import anyway, I got a address object with empty name and type FQDN.
So, how do I explicitly say, this is an ip-address netmask?
Chaning it to CIDR, doesn't work neither, so CSV input "foo;1.2.3.4;32"
When I use an csv-file from weeks ago with several hundred entries, it works, but this stupid "foo" import for demonstration isn't working.
Any ideas?
Best Regards
Chacko
02-03-2020 12:55 AM
@dgildelaig: Found the issue:
I tried a lot, using notepad++ and looking at control characters etc.
Solution is: open you perfectly well formatted and correct-syntaxed scripted CSV with excel.
Save it as csv and you are fine.
It seems, that the Migration tool is looking at the metadata of files
02-03-2020 12:32 AM
It could be the separation character.
Could you check changing the semicolon ";" for a comma ","?
02-03-2020 12:55 AM
@dgildelaig: Found the issue:
I tried a lot, using notepad++ and looking at control characters etc.
Solution is: open you perfectly well formatted and correct-syntaxed scripted CSV with excel.
Save it as csv and you are fine.
It seems, that the Migration tool is looking at the metadata of files
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!