Wireless Access

 View Only
last person joined: yesterday 

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

Virtual Mobility Conductor suddenly not reachable

This thread has been viewed 43 times

  • 1.  Virtual Mobility Conductor suddenly not reachable

    Posted May 09, 2023 04:21 AM

    Hello,

    since saturday 06.05.23 is my Virtual Mobility Conductor not reachable.

    Noting was changed.

    The MC is a OS8.9.x and is runing on ESXi8.

    The MC has a IP address in the same range as the other VMs which have no issues.

    I tried to restart the MC, moved it to another Host and to another Cluster.

    That made no difference. The MC is still not reachable.



  • 2.  RE: Virtual Mobility Conductor suddenly not reachable

    MVP GURU
    Posted May 09, 2023 07:32 AM

    Do you have console access to the Mobility Conductor? What does the routing table look like. Can you ping it from another appliance on the same subnet? Have you checked to see if anyone edited the network connections in the VM settings in vmware?



    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 3.  RE: Virtual Mobility Conductor suddenly not reachable

    Posted May 09, 2023 07:43 AM

    Hello,

    only via VM remoteconsol.

    No nothing is reachable. No one had made changes in the VMware.

    The routing table is still the same.

    The interface 0/0/0 ist up Protocol down

    We had testet a copy from an older Backup. It has the same issues.


    Original Message


  • 4.  RE: Virtual Mobility Conductor suddenly not reachable

    MVP GURU
    Posted May 09, 2023 07:52 AM

    If protocol is down you have a connectivity issue on the VM. You may need to get your VM team to take a look at anything that may have changed when it went down. VLANs trunked to the VM Host? vSwitches set up correctly? Etc...



    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 5.  RE: Virtual Mobility Conductor suddenly not reachable

    Posted Nov 19, 2023 08:53 PM

    Hello, Please help. I am at a Clent site. I have installed In Mobility Conductor 8.9 OS on ESXI 8.0

    The MC has a IP address in the same range as the other VMs which have no issues.

    I tried to restart the MC, moved it to another Host and to another Cluster.

    That made no difference. The MC is still not reachable

    As further troubleshooting I installed Mobility Conductor 8.9 OS on an Old server running ESXI 6.7 and it works smoothly. Is there a compatibility issue here, because i nolonger understand. I see a post here someone was having same issue with Conductor 8.9OS on ESXI 8.0.

    Please help with a resolution


    Original Message


  • 6.  RE: Virtual Mobility Conductor suddenly not reachable

    EMPLOYEE
    Posted Nov 20, 2023 02:51 AM
    1. AOS 8.9 is not a supported version of software, 8.10 and 8.11.2 are the currently supported trains.
    2. AOS has not yet been certified for operation on ESXi 8.0, valid versions are specified in the Virtual Appliance Installation Guide.


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

    Original Message