I have imported rules from a Cisco ASA to expedition in prep for putting them on a Palo Alto. Expedition made the zones that the rules are tied to into tags. I have tried editing the tag to the new design but I find that I can only choose an existing tag in expedition and if I try to make a new tag by just typing in the new name it generates a null tag and now the rules have 2 tags.
Do I need to make the new tags in my test palo and import that config as a new baseline before I merge to generate the option of the new tag or is there a way to create new tags in expedition.
Which version of Expedition are you using to experience this issue?
If not the latest one 1.1.51, try to update. We will look into it
Can you contact us via email (fwmigrate at paloaltonetworks dot com)?
I would like to get an export of your project to work with your settings and check what the reasons could be for this issue.
This subject seems have been dropped. Through experimentation it seems that I cannot create new items that did not already exist in the base image on the palo alto that I import. If I create the Tag on my test palo and import it, it is now an option, but I still can't create a net new tag through expedition.
Sorry for that. Did you contact us to fwmigrate?
You are experiencing something strange. We never had issues to create new objects in expedition is:
1- Your user has permits to create objects in the project
2- You have selected a DG/VSYS in where you want to create the objects.
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 Live Community as a whole!
The Live Community thanks you for your participation!