Batch Host Object CIDR Change Capability

[KarimAlazzawi]

I have found a workaround for batch host object CIDR changes (from 0 to 32) and am reaching out to see if there is a feature planned in Expedition to accomplish this.

SITUATION:  After importing an ASA config, I noticed two things.  First, the newly created host records beginning with "H-" which are duplicates of the imported host objects.  Second, the imported ASA host objects have a zero (0) as their CIDR and are invalid.  I would like to keep the ASA host object names.  For the firewall which is being migrated, the total invalid object with CIDR of zero is over 1500.

WORKAROUND: First, I had to export the project, extract the SQL file, perform regular expression replacement of 0 with 32, place the SQL file back into the zip file, and import the zip file into the project.  Second, I had to spend the time setting the ASA-named host objects as primary for a merge operation.

I have many more firewalls to migrate.  Your assistance in creating a so to speak "easy button" would be greatly appreciated.

[azuniga]

Hello @KarimAlazzawi 

What version of expedition are you using? Can you supply a screenshot as an example of what you mean?

[KarimAlazzawi]

I am using Expedition version 1.1.10.

[azuniga]

Hello @KarimAlazzawi ,

You are over 100 revisions behind please update your expedition server and re-import the configuration back in.

[KarimAlazzawi]

You are SO correct.  I updated the version to 1.2.3 and most all my issues went away.  All I will now have to do is assign the ASA host names as primary and merge.  Thank you. 

Can you qualify the CIDR mismatch of network objects?  There still seems to be a small issue.