ASA interface name corrupted

Answered Question
Apr 10th, 2010

I performed a maintenance on an ASA last night (simple ACL, static NAT updates) and this morning was suprised to find that the name of my outside interface changed from outside to outside%"#. Every line that referenced outside was updated and from what I can tell, everything is functioning as normal. Anyone have any ideas how this happened? Hardware is a 5550 4GB RAM running 8.2.2. On a similar note, is there any way to change an interface name without blowing away all the config that references it?

I have this problem too.
0 votes
Correct Answer by Kureli Sankar about 6 years 7 months ago

Never heard of this. Do you have syslogs from the time of the problem when you made all the acl, nat changes?

You would have seen this message.

Apr 11 2010 01:15:10 ASA : %ASA-5-111008: User 'enable_15' executed the 'nameif changed_name' command.

You can change the interface name. The telnet, ssh, http and access-g lines will automatically be changed to the new name.

-KS

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Kureli Sankar Sat, 04/10/2010 - 16:19

Never heard of this. Do you have syslogs from the time of the problem when you made all the acl, nat changes?

You would have seen this message.

Apr 11 2010 01:15:10 ASA : %ASA-5-111008: User 'enable_15' executed the 'nameif changed_name' command.

You can change the interface name. The telnet, ssh, http and access-g lines will automatically be changed to the new name.

-KS

joseph.l.wood.iii Wed, 04/14/2010 - 13:24

Thanks for that. I didn't know it would update everything. Now if there was just a way to migrate an interface (i.e. G0/0 -> R1). Unfortunately I don't have any logs, the ASA was set at the default 4k buffer and there is no syslog server. I'll just change it back and monitor.

Actions

This Discussion