05-30-2018 07:17 AM - edited 02-21-2020 07:49 AM
I have 2 ASAs in a active/standby failover cluster. They are running in Multi Context mode. Currently, there are no interfaces shared between contexts. All contexts have sub interfaces of a port channel allocated. However, now I have a few contexts created that will need to share interfaces and my understanding is the mac-address command is what is needed. What will be the impact of issuing the Mac Address auto command? I don't want to disrupt any of the current production contexts, and being that it's a global command it seems it may cause some unintended changes.
05-30-2018 07:33 AM
There is an extensive explanation of the command here:
https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/I-R/cmdref2/m1.html
, but basically it changes the way asa generates the mac addresses for its own interfaces and in case of shared interfaces you don't have to configure the macs manually.
When activated the asa should change the mac address on the interfaces, this could cause a short outage until arp will learn the new mac addresses.
HTH
Bogdan
05-30-2018 07:52 AM
Thanks for the information. I think the safe bet would be to manually configure the mac addresses per context. That way it avoids any unintended changes.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide