On here, I think I get paid in kudos.
Original Message:
Sent: Oct 07, 2024 03:50 PM
From: msantangelo
Subject: Mobility Master VM Replacement?
THAT WAS IT! You are a godsend. How can I thank you!?!
Original Message:
Sent: Oct 07, 2024 03:43 PM
From: chulcher
Subject: Mobility Master VM Replacement?
Make sure promiscuous mode and forged transmits are enabled on the vSwitch/port group.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 07, 2024 03:39 PM
From: msantangelo
Subject: Mobility Master VM Replacement?
VRRP is definitely not working but the new conductors are both seemingly online and communicate as they are in the list of mobility masters.
Original Message:
Sent: Oct 07, 2024 03:22 PM
From: chulcher
Subject: Mobility Master VM Replacement?
Certificate error can be bypassed by using some browsers or forcing unsafe usage. Otherwise, update the certificate; usually this is done by adding/updating the certificate at the Mobility Conductor level in the configuration and then assigning that certificate for usage by the WebUI.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 07, 2024 03:00 PM
From: msantangelo
Subject: Mobility Master VM Replacement?
Yeah I realized that I had to login via CLI. When we access the Web Interface for the secondary, we just got a X509 cert error.
Original Message:
Sent: Oct 07, 2024 02:48 PM
From: chulcher
Subject: Mobility Master VM Replacement?
Just log in to the secondary?
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 07, 2024 02:44 PM
From: msantangelo
Subject: Mobility Master VM Replacement?
How do I grab the flashbackup of the standby though? I can grab it of the primary using the WebUI. Do I have to do it via the CLI on the standby?
Original Message:
Sent: Oct 07, 2024 02:27 PM
From: chulcher
Subject: Mobility Master VM Replacement?
Ah.
- Deploy new virtual appliances using ISO
- Grab flashbackup of standby
- Power off standby MCR
- Bring up new standby MCR appliance, configuring with the same IP address as the old
- Restore flashbackup to new MCR appliance
- Validate functionality, database synchronization, and VRRP/conductor failover
- Repeat above steps with the other MCR
- Validate licensing, should require re-issuing the licenses as the MCR passphrase will have changed
Obviously, do this during a maintenance period to avoid client issues.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 07, 2024 02:11 PM
From: msantangelo
Subject: Mobility Master VM Replacement?
The VMs are being moved from a Hyperflex converged environment to a single standalone ESXi node. We have tried migrating the VMs but it never works properly. The advice we received was to deploy new VMs via OVA and migrate the config over, though they would not provide explicit steps.
Original Message:
Sent: Oct 07, 2024 01:58 PM
From: chulcher
Subject: Mobility Master VM Replacement?
First, don't use the OVA, use the ISO to build the virtual appliance. That way you for sure have the correct configuration for the MCR, including storage requirements, for your deployed appliance sizing.
Second, if you already have the VMs, and the desire is just to change the IP addresses, why are you deploying new VMs rather than just re-addressing the existing appliances?
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 07, 2024 12:05 PM
From: msantangelo
Subject: Mobility Master VM Replacement?
Hello all,
Forgive me if I use the wrong terminology here or if I'm posting in the wrong area, I am trying to muddle my way through this process which we normally use an outside contractor for but my boss has said that's not an option at this time.
We have two Aruba 7220 Controllers (#1 is .41, #2 is .40). We have two Aruba Mobility Master VMs in a Active/Standby configuration (#1 is .37, #2 is .38, and they have a VRRP IP of .39). We are on version 8.10.0.8 (for both the physical controllers and the VMs). We have deployed two replacement OVA files of the same exact version of the existing VMs (new #1 is .182, and new #2 is .183). We want to replace .37 and .38 with .182 and .183. I for the life of me can't figure out where to begin with this process.
I tried to follow the steps here: Replacing a Controller
Arubanetworks | remove preview |
| Replacing a Controller | The procedures below describe the steps to replace an existing stand-alone and/or a redundant . Best practices are to replace the backup first, and replace the active only after the new backup is operational on the network. When you remove the active from the network to replace it, the new backup takes over the active role. | View this on Arubanetworks > |
|
|
but I think it's talking about the physical controller, and not the actual VM.
Can someone please point me in the correct direction for replacing the two Mobility Master VMs? My understanding is that we will need to replace the standby VM first, let a sync occur, and then replace the primary, and then ensure the licensing is still correct, which will likely require a license conversion with HPE/Aruba. I just can't find explicit steps to replace the VMs.