topic Invalid Name not functional and Odd Search Behavior in Expedition Discussions

Invalid Name not functional and Odd Search Behavior

dega — Tue, 25 Sep 2018 18:50:39 GMT

I have several invalid address objects that were migrated with a name #.#.#.#/# and i want to replace the '/' with a '-' so that the name is valid, but the replace option is not functioning. The method was to right click and select predefined filters and 'Invalid Name' then going to Tools and trying the listed adjustment. Progress bar shows up then dissapears with no change.

There is another oddity to the Search process, and that is whenever the filter is invoked, it stores the filters, and if additional filters are in place that produce the same results, then they appear multiple times in the search results. I believe this is due to recalling the filter, rather than the database 'key' and retaining that as the search result. The below was a result of the above plus selecting the objects and then right click 'Search&Replace':

Re: Invalid Name not functional and Odd Search Behavior

dega — Tue, 25 Sep 2018 19:25:46 GMT

It appears that this was caused by a ghost object. To resolve, I right clicked and selected Predefined filters then Ghost Objects, then selected them, then right clicked and Select Transform->IPaddress to Object, and then proceeded to replace. For anyone on the Palo team, what is the Transform and are the two options? Also, I saw in another post that a ghost object is caused by panorama however this was a direct ASA conversion, with no Palo config imported yet. Is there a problem with the code or is there another reason for the Ghost object?

Re: Invalid Name not functional and Odd Search Behavior

bagherib — Wed, 26 Sep 2018 16:54:02 GMT

Great post as always. I'm really concerned about continuing to use Expedition. I'm currently importing each project into both MT3.3 and Expedition and have to check everything in a spreadsheet two or three times.