10-26-2022 11:55 AM - edited 10-26-2022 01:41 PM
Update: found the answer that using "system-mac xxxx.xxxx.xxxx" command under vpc. I was hoping it would have less impact on live vPC domain when I have conflict domain IDs but it seems it would have the same impact when assigning a new domain ID...
=============
NX-OS uses vpc domain id to make up the vPC system mac address. I wonder if there is a way to manually define the vpc system mac address?
10-26-2022 11:39 PM
Hi @SIMMN
More or less. If you use LACP, then yes, all the vpc enabled port-channels will be affected, as the vpc system MAC is used for them. However, my recommendation is to change the vpc domain id, not the system mac. And you can do that simply by typing "vpc domain <new-domain-id>" command in "conf t" prompt on both vpc peers. By changing the domain, will save you some trouble of remembering which vpc domain is bound to which system mac - especially in tshoot scenarios, when time is critical and you don't need any confusion.
Take care,
Sergiu
10-27-2022 05:31 AM
Thanks, I agree...Wish there were a less intrusive way of updating vpc domain...
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