Wireless Access

 View Only
last person joined: 3 days ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Cloning a Mobility Conductor

This thread has been viewed 13 times

  • 1.  Cloning a Mobility Conductor

    Posted 7 days ago

    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 6 days ago

    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
    ------------------------------

    Original Message


  • 3.  RE: Cloning a Mobility Conductor

    EMPLOYEE
    Posted 6 days ago

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



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

    Original Message


  • 4.  RE: Cloning a Mobility Conductor

    EMPLOYEE
    Posted 5 days ago

    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
    ------------------------------

    Original Message