Wireless Access

 View Only

  • 1.  Cloning a Mobility Conductor

    Posted Sep 30, 2024 08:33 PM

    I am working on setting up a resilient Mobility Conductor and was wondering if cloning a virtual conductor from one hypervisor to another is an option? Could this cause issues?  Would cloning mean you might replicate some UUIDs in the file system that could cause unexplained failures?

    Wonder if someone has experience with this.



    ------------------------------
    Martijn van Overbeek
    Architect, Netcraftsmen a BlueAlly Company
    ------------------------------


  • 2.  RE: Cloning a Mobility Conductor

    Posted Oct 01, 2024 07:25 AM

    When cloning, the UUID is changed, as a result of which the licenses become invalid.



    ------------------------------
    Regards,

    Waldemar
    ACCX # 1377, ACEP, ACX - Network Security
    If you find my answer useful, consider giving kudos and/or mark as solution
    ------------------------------



  • 3.  RE: Cloning a Mobility Conductor

    Posted Oct 01, 2024 09:36 AM

    You're after operations resiliency?  Why wouldn't you use the available L2 and/or L3 redundancy?



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 4.  RE: Cloning a Mobility Conductor

    Posted Oct 02, 2024 06:01 PM

    This doesn't cover migrating to a different hypervisor, but might find some useful info:

    https://www.hpe.com/psnow/doc/a00107753en_us



    ------------------------------
    Nikunj Naresh Shah
    ------------------------------



Related Content