Solved: Modifying Startup-Config to Move ASA Interface

Jared Burton · ‎09-13-2016

Hello Everyone!

I believe I have a fun one here.

I have two ASA5550 (failover environment), running 8.4, with both inside and outside interfaces in the same bus. I'm oversubscribed and would like to migrate the inside interface over to the other bus.

I understand that issuing a "no nameif" Will royally screw my config up by removing any config lines calling "inside".

So I would like to pull the startup-config, make the changes I want in a text editor, push it back, and then reload.

I'm just wondering if that is all there really is to it. Should I remove the Checksum at the bottom of the config? Leave it? Am I missing something?

Will this work at all?

Other words of wisdom?

Any and all advice will be greatly appreciated.

-Thanks and Cheers!

jburton1103

Marvin Rhoads · ‎09-13-2016

Depending on how complex your configuration is, removing and replacing nameif isn't terribly awful if you anticipate it and have copied off the ACLs, NAT and any other configuration bits that referred to it originally. Those can just be pasted back in as they were once you have migrated the nameif to a new physical interface.

That said, if your 5550 is oversubscribed, you will see significant performance gains only a a few cases by moving interfaces around to be on separate bus. You'd have to have an expansion module installed (the only thing that uses Bus 1) and be hitting the cap currently solely based on interface capacity (and not the more common memory or CPU constraints).

View solution in original post

Marvin Rhoads · ‎09-13-2016

Depending on how complex your configuration is, removing and replacing nameif isn't terribly awful if you anticipate it and have copied off the ACLs, NAT and any other configuration bits that referred to it originally. Those can just be pasted back in as they were once you have migrated the nameif to a new physical interface.

That said, if your 5550 is oversubscribed, you will see significant performance gains only a a few cases by moving interfaces around to be on separate bus. You'd have to have an expansion module installed (the only thing that uses Bus 1) and be hitting the cap currently solely based on interface capacity (and not the more common memory or CPU constraints).