Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

Cannot convert Juniper configuration

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Cannot convert Juniper configuration

L1 Bithead

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? 

6 REPLIES 6

L7 Applicator

for further analysis it will be better to send an email to fwmigrate at paloaltonetworks dot com and go from there...

L1 Bithead

I had the same problem:  You need to make sure your configs start with and end with the following:

</configuration>

...

...

...

 </configuration>

 

 

Will this work for a file in .txt format?

Yes, I used txt format for my firewall migration using expedition.  

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. 

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. 

  • 5420 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!