Hi,
Since you arent using any "no" form commands the only situation I can think of is the following
- You already had an ACL on the "outside" interface but its NOT named "outside_in"
- You configured the above ACL
- You attached this new ACL to the "outside" interface and it removed the old ACL that was attached to the interface
So lets say you have the following
You originally have
access-list OUTSIDE-IN permit ip any host x.x.x.x
access-group OUTSIDE-IN in interface outside
Now you are planning on adding rules to the firewall from "outside"
You instead enter
access-list OUTSIDE-in permit ip any host y.y.y.y
access-group OUTSIDE-in in interface outside
This would mean that the previous ACL "OUTSIDE-IN" and its rule would be removed from use and the new ACL "OUTSIDE-in" (with different name would be taken into use)
Though normally when you create an ACL to an interface and attach it with the "access-group" command then theres no real reason to use the "access-group" command again in the future when adding simple ACL rules to an already existing ACL.
The commands you listed however dont delete any ACL rules otherwise. Only other option I can think of now would be that something went wrong with the NAT configuration.
Notice that if you use ASDM to configure Static NAT and insert that Static NAT between some rules the ASDM will actually tell the ASA to
Remove some Static NAT rules -> Insert new Static NAT rule -> Insert all the removed Static NAT rules back
This is because there is no line numbers in older software for NAT rules. They are gone through in the order they are configured. So this requires removing commands and inserting them again to change their order.
Hopefully the above was of some help
- Jouni
