Cisco Bug: CSCtc18329 - ACL renamed but syslog doesn't reflect new name
Nov 09, 2016
- Cisco ASA 5500-X Series Firewalls
Known Affected Releases
Symptom: When an outbound ACL is renamed using the 'access-list <name> rename' command, syslogs that reference the ACL may still refer to the old ACL name. For example: Before ACL rename: %ASA-6-106100: access-list outside_access_out permitted tcp inside/192.168.110.35(57736) -> outside/172.16.1.40(80) hit-cnt 1 first hit [0x53babf9a, 0x0] After ACL rename: %ASA-5-111008: User '<username>' executed the 'access-list outside_access_out rename NEW_ACL' command. %ASA-6-106100: access-list outside_access_out permitted tcp inside/192.168.110.35(57738) -> outside/172.16.1.40(80) hit-cnt 1 first hit [0xd93cbc6a, 0x0] Conditions: This issue only affects outbound ACLs that are renamed with the 'access-list <name> rename' command. Note that this is a cosmetic issue that only affects the ACL name in the syslog message. The ACL will still continue to be applied correctly.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases