XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Cannot connect to XOA VM

    Scheduled Pinned Locked Moved Management
    11 Posts 5 Posters 420 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • isdpcman 0I Offline
      isdpcman 0
      last edited by

      We have XCP-ng setup with two VMs. I have assigned a static IP to the XOA machine. Sometimes it works, other times it is unreachable (this has happened several times, now). If I restart the VM host I can get back in. But I can't keep doing this to manage the VM host machine! When I try to connect to the XOA machine (https://192.9.91.8) I get "Unable to connect" in the browser.

      How can I resolve this so it's reliable to connect to the console and manage these VM's?

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        In order to assist, we need more context. However, my guess is likely an IP conflict. Be sure that your XOA VM doesn't have the same IP than any other equipment on your network.

        isdpcman 0I 1 Reply Last reply Reply Quote 0
        • isdpcman 0I Offline
          isdpcman 0 @olivierlambert
          last edited by

          @olivierlambert

          It has a DHCP reservation specifically for the MAC of the virtual network adapter. There are no other devices on the LAN in this section of the IP range (the DHCP scope is 100-249). There are 6 devices in the 6-21 range, This is one of them. However, for shits and giggles I changed the reservation IP to .9 and restarted the XOA VM. I can ping the 192.9.91.9 address on the LAN now (when I pinged before there were no replies). Now I get 4 with <1ms delay. However, when I try to access the XOA machine at the new IP address I get "This site can't be reached, 192.9.91.9 refused to connect"

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            DustinB @isdpcman 0
            last edited by

            @isdpcman-0 Does something else on the network have the same DHCP address or reservation? If so that would explain why the interface works for a bit and then stops working.

            I 1 Reply Last reply Reply Quote 0
            • I Offline
              ISDPCMAN @DustinB
              last edited by

              @DustinB
              As stated, I reassigned the IP to an address I couldn't ping (192.9.91.9). So, no, there are no other devices on the LAN with the same address.

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                DustinB @ISDPCMAN
                last edited by DustinB

                @ISDPCMAN So to confirm, your DHCP scope and subnet are

                192.9.91.0/24
                Your XOA is using DHCP and there is a reservation for this VM's MAC address
                Your DCHP Scope is 192.9.100-249
                Subnet is 255.255.255.0
                

                On the XOA VM are you able to run ip -a and see what it's pulled, and on your DHCP server can you validate the MAC address aligns to the VM?

                isdpcman 0I 1 Reply Last reply Reply Quote 0
                • isdpcman 0I Offline
                  isdpcman 0 @DustinB
                  last edited by

                  @DustinB
                  Yes, I have logged into the DHCP server and I can see the IP address was allocated to the specified MAC address. And right now I can connect to the XOA device. The problem is, after a while I am no longer able to access that device. It's like once it hits 24 hours old (speculating...I haven't timed it) the connection no longer happens. I get denied. When I check the XCP-ng host, I can see that the XOA device is in a running state. Very odd to me...

                  D DanpD 2 Replies Last reply Reply Quote 0
                  • D Offline
                    DustinB @isdpcman 0
                    last edited by

                    @isdpcman-0 said in Cannot connect to XOA VM:

                    @DustinB
                    Yes, I have logged into the DHCP server and I can see the IP address was allocated to the specified MAC address. And right now I can connect to the XOA device. The problem is, after a while I am no longer able to access that device. It's like once it hits 24 hours old (speculating...I haven't timed it) the connection no longer happens. I get denied. When I check the XCP-ng host, I can see that the XOA device is in a running state. Very odd to me...

                    This to me would indicate that something else on your network is attempting to use that 192.9.91.9 ip address that you're unaware of.

                    If you power of XOA (after validating that it's using your assigned IP address) can you still ping 192.9.91.9 with an active response?

                    Ofcourse it's possible whatever else is on your network is configured to not reply to ICMP, but that is another matter entirely.

                    1 Reply Last reply Reply Quote 0
                    • DanpD Offline
                      Danp Pro Support Team @isdpcman 0
                      last edited by

                      @isdpcman-0 I would recommend troubleshooting the XO VM by checking the logs. Are you running XOA or XO from sources? Which commit or version?

                      isdpcman 0I 1 Reply Last reply Reply Quote 0
                      • isdpcman 0I Offline
                        isdpcman 0 @Danp
                        last edited by

                        @Danp XOA

                        DanpD 1 Reply Last reply Reply Quote 0
                        • DanpD Offline
                          Danp Pro Support Team @isdpcman 0
                          last edited by

                          @isdpcman-0 Which version are you running (XOA > Updates)? You can check the logs by connecting to the VM via SSH and then running the command journalctl -u xo-server -f -n 50.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post