07-12-2017 11:03 PM - edited 03-12-2019 02:41 AM
hi,
can this be considered a 'best practice' for an ASA config clean up?
can someone able to share his/her experience when doing an ASA clean up? any best practice or recommendations? links?
Solved! Go to Solution.
07-13-2017 02:11 AM
It gives that result when the config is already clean (no unused objects or ACLs).
You can put a dummy object into the pasted config if you want to verify the tool catches it.
07-13-2017 01:48 AM
I've used FSM once or twice years back even before SolarWinds acquired it (used to be called FirePac) from Athena. I liked it but now i see SolarWinds is discontinuing it. :(
Lately I use the tunnelsup.com tools for ACL and object cleanup.
Static routes are hard to identify as actively used or not as they depend on whether or not there is traffic presented in the data plane that ever needs them. I suppose one could go to the next hop and see if the downstream network is still reachable.
07-13-2017 02:02 AM
hi marvin,
i tried to use tunnelsup.com cleanup tool but only shows me 'no items found to cleanup.'
anything i miss?
! No items found to cleanup.
! Analyzed 221 lines of code.
07-13-2017 02:11 AM
It gives that result when the config is already clean (no unused objects or ACLs).
You can put a dummy object into the pasted config if you want to verify the tool catches it.
07-13-2017 06:30 PM
yes, you're right. i pasted a 'clean' config.
i tried to put a dummy config and gave me this result.
looks like this might be a handy tool.
! Unused object found; suggest removing it
no object network INSIDE-SUBNET
! Analyzed 2 lines of code.
07-18-2017 08:33 PM
hi marvin,
could you advise how to determine if NAT are unused? they should NOT appear show xlate right?
i could see some NAT translation but idle time is VERY LONG.
flags sIT idle 414:12:19 timeout 0:00:00
i also checked static NAT displayed on show xlate but didn't appear in show conn or show local-host output. which output should i refer or follow in order to remove static NAT config?
07-18-2017 09:08 PM
Unused NAT can be very challenging as it requires more of a business/technical discussion with the customer vs. straight analysis of the configuration.
For instance, consider a VM that is only powered on during certain conditions but when it is up it requires a static NAT. You will not see any output for it from the show commands you mentioned unless it is active. So one might think it is OK to remove. But if next week it is powered up, the firewall will cause the business process to break.
You might get some clues from internal DNS if the host address is unknown and currently not reachable. Also, internal routing or site-site VPN crypto map definitions may highlight NAT rules that point to non-existent subnets or no longer active locations.
07-18-2017 09:40 PM
it's challenging indeed!
i'll just run through it and consult with customer/stakeholders if they still need the NAT line.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide