NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Re: MLAG not working - XSM7224
I can't reply on the closed thread, so I am following up to https://community.netgear.com/t5/Managed-Switches/MLAG-not-working/td-p/465708 here
I was experieincing the same issue and eventually...
Alright, I found that disabling VPC mode on both switches and re-enabling caused them both to go through the election process again, which resulted in the switches having the expected VPC mac address of C0-FF-D4-A7-DA-01, rather than 00-00-00-00-00-00 that they should in web UI, CLI and packet captures. After that, MLAG started functioning as expected. So in my situtation it seems I had to upgrade to the same, latest firmware and trigger a fresh state of VPC, rather than allowing a bad state to carry forward. I'm not sure if the bad state came from mismatched firmware or another bug, but things seem to be working as expected now.
Hello alexjhart,
Welcome to the community!
Thank you for this update. I can probably edit the old thread and attach this response of yours. This will help other users if they experience the same issue.
Thanks,
Perhaps opening the other thread back up is the appropriate action. I may have spoken too soon in saying that this is entirely resolved. I will say the firmward upgrade helped in getting the VPC domain operational, however I am still experiencing some issues with getting the MLAG to actually work the same with a host (while LAG configuration does work just fine).
Alright, I found that disabling VPC mode on both switches and re-enabling caused them both to go through the election process again, which resulted in the switches having the expected VPC mac address of C0-FF-D4-A7-DA-01, rather than 00-00-00-00-00-00 that they should in web UI, CLI and packet captures. After that, MLAG started functioning as expected. So in my situtation it seems I had to upgrade to the same, latest firmware and trigger a fresh state of VPC, rather than allowing a bad state to carry forward. I'm not sure if the bad state came from mismatched firmware or another bug, but things seem to be working as expected now.
Hi alexjhart,
Thank you for sharing the workaround. I am also hoping that this will be corrected on future firmware updates. I cannot confirm that this is a bug or issue though, I'll probably have the engineering team look this up.
Thanks,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
