cancel
Showing results for 
Search instead for 
Did you mean: 

WiNG vx9000 not clustering since being relocated to new HyperV host

WiNG vx9000 not clustering since being relocated to new HyperV host

Eric_Burke
New Contributor III

We recently deployed a pair of vx9000’s in HyperV. The controllers are each on a different host. When we started building, we only had one host ready so we built the pair on that box. Now that both hosts are up, we exported and imported one of the units,  Same IP address, just a new host. We found that mistakenly we didn’t clone the MAC and lost the licensing. We then set the MAC back, and confirmed that the vx9000’s coudl still ping eachother. They’re sending hello’s via MINT. A support engineer helped us to realize that the license got dropped, presumably when getting the wrong MAC, so we re-licensed it. Still, we could not get the cluster back up. The engineer dropped the node we’d moved and manually rejoined the cluster. This seemed to work for a brief couple of minutes, but then we kept seeing the active role shifting back and forth between controllers. On the relocated unit, we’re seeing the following message:

CMASTER_CFG_UPDATE_FAIL: Cluster Master Rejecting Config from unknown host. Not sure what else we need to do to resolve the issue?  Any guidance?

20 REPLIES 20

ckelly
Extreme Employee

Matt, so the two controllers are clustered?

 

#show cluster members

 

 

Matt_Unger
New Contributor

@Chris Kelly I removed the Mint Level 1 entries and now both controllers are able to see each other using Mint Level 2.  Thank you for you help with this, it is very much appreciated!

Matt_Unger
New Contributor

Original East VM is definitely offline. 

ckelly
Extreme Employee

Understood.  In that case, just ensure that the original EAST controller is shut down. 

GTM-P2G8KFN