- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
08-02-2018 02:10 AM
Hi team,
I have to convert Juniper configuration, but when importing configuration file, Expedition tool shows only object, no policy. Does anyone experience that before?
07-23-2019 08:01 AM
I had the same problem: You need to make sure your configs start with and end with the following:
</configuration>
...
...
...
</configuration>
10-06-2020 07:37 AM
Will this work for a file in .txt format?
10-06-2020 07:41 AM
Yes, I used txt format for my firewall migration using expedition.
10-06-2020 01:27 PM
I used an XML file instead and added the <configuration> tags as listed. I'm still getting the same message for both .txt and .xml. Ran it against two browsers and none noticed an xml formatting error.
10-06-2020 01:58 PM
When I pulled the configs from the Juniper it was in XML format but as a Txt file. The XML config print out includes a lot of junk before the configuration tag or <configuration> so you have delete all of that before the configuration and after at the bottom of the config.
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!