I have some large Cisco ASA 9.8 configs which I'm convering in Expedtion 1.0.104. I always seem to get many duplicate host objects which Expedition automatically creates. For example, object host 10.1.1.1 becomes H-10.1.1.1-32 with the value 10.1.1.1/32. I select the duplicate object and do a "Search and Replace". Once filtered, all the objects are green and in use. So I have to pick one, select to replace them, choose the Address object, then the host entry created by Expedition (H-10.1.1.1-32). Once I do that, one of the two duplicate objects becomes unused (red dot) and I can delete it. This can be very time consuming when several objects are duplicated.
1. Why does this happen? Is there anything in the ASA config I can modify to fix this before importing.
2. Is there a way to fix this by using regex or some other way?
Thank you in advance,
Solved! Go to Solution.
Over the weekend I did this import in MT3 and it did not have any duplicate IP addresses. I don't think I can continue to use Expedition if it going to add several hours of work by fixing duplicate IP address objects.
Secondly, for some reason the L4 ports are translated differently. For example in MT3 tcp/8443 is "tcp-8443". In Expedition it is "tcp_8443". Why?
I was in 1.0.104 when you gave me that tip. It didn't merge them all in one shot, but I was able to pick each pair and marge them. It took about two hours but it was still much faster than search+replace.
I now have 1.0.105 and I can go back to a snapshot before the duplicates and see if that works. I'll follow up on this post.
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!