Hi,
I kind of wonder what the actual situation is.
I would think that the WARNING message means that you were trying to enter a single ACL rule (= ACE) that already existed in the ACL.
To my understanding the only way you can have identical ACEs in a single ACL when you have one ACE using a simple permit statement mentioning the IPs/ports in the command and when you have the same done with "object-group". In this situation to my understanding the ASA will actually have 2 identical rules (even though configured differently)
For example
access-list TEST permit tcp host 1.1.1.1 host 2.2.2.2 eq 80
or
object-group network SOURCE
network-object host 1.1.1.1
object-group network DESTINATION
network-object host 2.2.2.2
access-list TEST permit tcp object-group SOURCE object-group DESTINATION eq 80
This will produce the following ACL
access-list TEST extended permit tcp host 1.1.1.1 host 2.2.2.2 eq www
access-list TEST extended permit tcp object-group SOURCE object-group DESTINATION eq www
When we look at the ACL in opened form we see that the actual rules are identical
access-list TEST; 2 elements; name hash: 0xd37fdb2b
access-list TEST line 1 extended permit tcp host 1.1.1.1 host 2.2.2.2 eq www (hitcnt=0) 0xd82b1952
access-list TEST line 2 extended permit tcp object-group SOURCE object-group DESTINATION eq www 0xbcf2cfe7
access-list TEST line 2 extended permit tcp host 1.1.1.1 host 2.2.2.2 eq www (hitcnt=0) 0xd82b1952
Yet you say that you were moving an previous configuration to the device so it should be valid configuration as it was already used on an ASA.
Are you sure that you have not just copy/pasted same lines again or perhaps used somekind of "show access-list" output as the base of some configuration? That what I was thinking with the above example I mentioned that the access-list output might have identical rules even though the configuration format is different.
- Jouni
