Wireless Access

I was in the process of building an active and standby VMM setup using master redundancy and VRRP, however, our VM environment will not allow this to work properly, so we've decided to scrap the standby as our VM environment is pretty robust and redudant already. Now I see the Standby's MAC address under the Mobility Master folder, is there a way for me to clear that out? I've performed a factory-reset on the standby and shut down the VM, so it's not actively communicating with the primary VMM anymore.

 

Thanks for the help

It is an existing, unfixed bug.

 

I will update this space when it is fixed.

Edit:

 

If you cannot remove it by changing to /mm and executing:

no configuration device <MAC address>

 

...then it is a bug that is unfixed.

That did it! Thanks for the help

Hello,

 

I have the same problem after rebuilding the Primary MM.

 

I still have this phantom MAC of the old MM in the GUI and the command "no configuration device 00:50:56:BC:10:23" under the /mm did NOT do the job in my case. The MM are running 8.3.0.7

 

Any other advice

 

Regards

I was able to remove the "phantom" Standby MM. Don't recall exactly how I did it, but we've done code upgrades since. I didn't rebuild the environment as far as I remember, so maybe a code upgrade or rebooting the MM would do it? Our's wasn't in production so I had the ability to toy around a bit to clean it up.


________________________________

Please note that if you have received this message in error, you are hereby notified that any dissemination of this communication is strictly prohibited. Please notify me immediately by reply e-Mail and delete all copies of the original message.

Hello,

 

I have already tried to reboot both Primary & Standby MMs without success.

 

Also the strange thing is that when MM1 (the one that has been rebuild) is Primary I can see the "phantom" MM but when I switch Primary role to MM2 (still original build) I only see the two actual MMs. I have tried to synchronize DB in this situation then switch back Primary to MM1 but the third "phantom" MM is still there.

 

Funny

I have now upgraded both MMs to version 8.3.0.8 and I can still see the "phantom" MM, only on the GUI, this node is not visible through the CLI

 

Any advice how to clean it ?

 

Kind regards

 

Christian Chautems

Bug still exists in 8.6.0.4

Same here, code 8.6.0.5.

 

- /mm "no configuration device mac" (not work/not found).

- reboot both MMs (not work).

- When failover to MM02 standby, all looks fine. When fail back to MM01 the issue is back.

 

Somebody with a solution for this?

Seems like this is a known issue in 8.6.0.4 and 8.6.0.5 at least. I solved the issue the hard way. I do it the hard way because its a LAB environment, take special care in production!!

 

- When i make the MM02 master and MM01 standby the issue was gone, when make MM01 master again the issue was back. In my situation.

 

- Make MM02 the master again.

- Stop the database synchronization.

- Change the vrrp priority so MM02 keep priority.

- write erase all MM01.

- Restore vrrp settings.

- enable the database synchronization where MM02 is master and synced to the new MM01.

- Make MM01 master again.

- Problem solved, without downtime or loosing licences.

 

Better contact TAC support if you have this issue in production.