For details on cookie usage on our site, read our Privacy Policy
CSV import: Service import changed, does not work in 1.1.22
- LIVEcommunity
- Tools
- Expedition
- Expedition Discussions
- CSV import: Service import changed, does not work in 1.1.22
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report This Content
05-31-2019 06:20 AM
Hi!
I have used CSV import quite a lot lately, and today, running 1.1.22, I imported all CSV files from scratch again. This time there was nothing at all imported for the Services objects. I have not changed that source CSV file in two weeks, so something has happened to the import. I cannot say for sure if it was this last change from 1.1.21 to 1.1.22 that made it, or if it stopped working earlier.
Is there a log file somewhere where I can look for clues? There is always a possibility that the import has changed to be less flexible, and I can change something at my end to make this work again.
/Per
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report This Content
05-31-2019 09:35 AM
The changes to the CSV import for the services was updated in the CSV import guide earlier this week.
The main difference was an addition to include an option for the source port. With the previous setting for 'port' changed to 'dport' to specify the destination port.
https://live.paloaltonetworks.com/t5/Expedition-Articles/tkb-p/ExpeditionArticles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report This Content
05-31-2019 06:25 AM
I just upgraded to 1.1.23, and it is still broken unfortunately.
/Per
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report This Content
05-31-2019 09:35 AM
The changes to the CSV import for the services was updated in the CSV import guide earlier this week.
The main difference was an addition to include an option for the source port. With the previous setting for 'port' changed to 'dport' to specify the destination port.
https://live.paloaltonetworks.com/t5/Expedition-Articles/tkb-p/ExpeditionArticles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report This Content
05-31-2019 01:05 PM
In 1.1.23, there is still something small not quite right.
If I have a column in the first line of the file preset to 'dport', it is not picked up as a key for 'Destination Port', I have to select it by hand.
A small thing to tweak for a future release.
/Per
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report This Content
06-15-2019 02:01 AM
Do you have a sample of the CSV so we can test against your file?
- Parsing issue for service object names containing NEXT as keyword (Fortinet import) in Expedition Discussions
- Importing CSV rules in Expedition Discussions
- Migrating from Cisco ASA, strange DNAT rules in Expedition Discussions
- "merged" tag added to service objects in Expedition Discussions
- Unused ASA Services after Expedition import in Expedition Discussions
Show your appreciation!
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!
