Wireless Access

I have an engagement coming up to migrate a 2 node Mobility Conductor cluster from VM to hardware appliances. My original thought was to migrate the backup MM first but then I realized you can't have a VM and hardware in the same cluster (I think - I know that's true for controllers, trying to find the doc for MMs now). I will still do it that way, but break the dependency first. My question is  what kind of gotchas might I get from the controller side? When you initially set up a controller to point to an MM, it asks if the MM is VM or HW. That leads me to believe I may need to make a change on the controllers when I migrate.  For a point of reference, the new MM instance will have all of the old IP addresses, VIP, etc as the old

So to put it in a nutshell, I have 2 main questions
1) What is the best practice to migrate this (restore new HW from flashbackup of old VM, create new instance and copy-and-past and then change the IPs, something else)
2) Is there anything I need to do on the controller side if the MM it is pointing to changes from VM to HW?

Thanks

Jeff Johnston

I have an engagement coming up to migrate a 2 node Mobility Conductor cluster from VM to hardware appliances. My original thought was to migrate the backup MM first but then I realized you can't have a VM and hardware in the same cluster (I think - I know that's true for controllers, trying to find the doc for MMs now). I will still do it that way, but break the dependency first. My question is  what kind of gotchas might I get from the controller side? When you initially set up a controller to point to an MM, it asks if the MM is VM or HW. That leads me to believe I may need to make a change on the controllers when I migrate.  For a point of reference, the new MM instance will have all of the old IP addresses, VIP, etc as the old

So to put it in a nutshell, I have 2 main questions
1) What is the best practice to migrate this (restore new HW from flashbackup of old VM, create new instance and copy-and-past and then change the IPs, something else)
2) Is there anything I need to do on the controller side if the MM it is pointing to changes from VM to HW?

Thanks

Jeff Johnston

I have an engagement coming up to migrate a 2 node Mobility Conductor cluster from VM to hardware appliances. My original thought was to migrate the backup MM first but then I realized you can't have a VM and hardware in the same cluster (I think - I know that's true for controllers, trying to find the doc for MMs now). I will still do it that way, but break the dependency first. My question is  what kind of gotchas might I get from the controller side? When you initially set up a controller to point to an MM, it asks if the MM is VM or HW. That leads me to believe I may need to make a change on the controllers when I migrate.  For a point of reference, the new MM instance will have all of the old IP addresses, VIP, etc as the old

So to put it in a nutshell, I have 2 main questions
1) What is the best practice to migrate this (restore new HW from flashbackup of old VM, create new instance and copy-and-past and then change the IPs, something else)
2) Is there anything I need to do on the controller side if the MM it is pointing to changes from VM to HW?

Thanks

Jeff Johnston

I have an engagement coming up to migrate a 2 node Mobility Conductor cluster from VM to hardware appliances. My original thought was to migrate the backup MM first but then I realized you can't have a VM and hardware in the same cluster (I think - I know that's true for controllers, trying to find the doc for MMs now). I will still do it that way, but break the dependency first. My question is  what kind of gotchas might I get from the controller side? When you initially set up a controller to point to an MM, it asks if the MM is VM or HW. That leads me to believe I may need to make a change on the controllers when I migrate.  For a point of reference, the new MM instance will have all of the old IP addresses, VIP, etc as the old

So to put it in a nutshell, I have 2 main questions
1) What is the best practice to migrate this (restore new HW from flashbackup of old VM, create new instance and copy-and-past and then change the IPs, something else)
2) Is there anything I need to do on the controller side if the MM it is pointing to changes from VM to HW?

Thanks

Jeff Johnston

I have an engagement coming up to migrate a 2 node Mobility Conductor cluster from VM to hardware appliances. My original thought was to migrate the backup MM first but then I realized you can't have a VM and hardware in the same cluster (I think - I know that's true for controllers, trying to find the doc for MMs now). I will still do it that way, but break the dependency first. My question is  what kind of gotchas might I get from the controller side? When you initially set up a controller to point to an MM, it asks if the MM is VM or HW. That leads me to believe I may need to make a change on the controllers when I migrate.  For a point of reference, the new MM instance will have all of the old IP addresses, VIP, etc as the old

So to put it in a nutshell, I have 2 main questions
1) What is the best practice to migrate this (restore new HW from flashbackup of old VM, create new instance and copy-and-past and then change the IPs, something else)
2) Is there anything I need to do on the controller side if the MM it is pointing to changes from VM to HW?

Thanks

Jeff Johnston

I have an engagement coming up to migrate a 2 node Mobility Conductor cluster from VM to hardware appliances. My original thought was to migrate the backup MM first but then I realized you can't have a VM and hardware in the same cluster (I think - I know that's true for controllers, trying to find the doc for MMs now). I will still do it that way, but break the dependency first. My question is  what kind of gotchas might I get from the controller side? When you initially set up a controller to point to an MM, it asks if the MM is VM or HW. That leads me to believe I may need to make a change on the controllers when I migrate.  For a point of reference, the new MM instance will have all of the old IP addresses, VIP, etc as the old

So to put it in a nutshell, I have 2 main questions
1) What is the best practice to migrate this (restore new HW from flashbackup of old VM, create new instance and copy-and-past and then change the IPs, something else)
2) Is there anything I need to do on the controller side if the MM it is pointing to changes from VM to HW?

Thanks

Jeff Johnston