default src file

[JHALL3]

Hi, I am relatively new to Expedition. I am in the process of migrating a load of Cisco configs to Palo, and an using Expedition. The Expo is not able to connect to the actual Palo/Panorama due to security, so I am doing this conversion in AWS, and then manually loading the config via a config partial push.

When I create a new project and bring in the cisco config and look at the services I can see some are comming from the actual cisco src file but many are coming from default.... what is this? just a default set of ports built into Expo I had assumed...

but when I look at the service groups, most of them are also against default src File, now these cannot be known by Expo as they are specific to my Cisco config. Can any one explain whats happening here?

At this point I have not loaded a base Palo config to merge into.

Rgs

Jon

[lychiang · Accepted solution]

Hi @JHALL3 This is normal behavior, expedition will try to migrate your ciscoasa config as is , if the objects has "red" dot in front, that means those objects are not being used in any group objects or policies , you can safely remove them, if the object has "green" dot in front, that means objects are being used, you will need to fix the invalid object, for example if service object "echo" is used, you will need to replace it with APP-ID ping or icmp ,  before you can merge with pan-os base config.  

[JHALL3]

Hi Lychiang, I understand that, I am asking about why are almost all the objects shown as coming from a "default" src File, rather than the cisco src file.

[JHALL3]

Hi @lychiang, I understand that, I am asking about why are almost all the objects shown as coming from a "default" src File, rather than the cisco src file.

[lychiang]

Hi @JHALL3 The objets in "default" was created by Expedition , when parsing the cisco config file, if the object is referenced in any ACL but it's not an object in ciscoasa config, Expedition will create them as object in source file "default".