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

    Site outage. help?

    Scheduled Pinned Locked Moved Management
    3 Posts 1 Posters 42 Views 1 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.
    • M Offline
      McHenry
      last edited by

      We downed our pool master (no VMs) for testing and the router VM (pfSense) lost internet connectivity.

      When we restarted the master the router VM still has no internet connectivity.
      All VMs,including the router are online in XO.
      8e09b11c-d718-42fb-9aea-2a8ebd9f48b2-image.png

      From the pfSense console I can ping VMs on the LAN however there is internet connectivity.

      Everything looks fine so I am at a loss as to what the issue is.
      50f4713b-1f37-49ee-ac1c-453f9a0364ef-image.png

      M 1 Reply Last reply Reply Quote 0
      • M Offline
        McHenry @McHenry
        last edited by

        When I try to manually configure the management interface as eth0 i get this:
        b3fc2ce7-ba9a-4bf9-a39c-7be82b29d5b8-image.png

        The NIC appears to be there and connected:
        344f8cd0-7d41-464e-a773-3e60c6883a26-image.png

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          McHenry @McHenry
          last edited by

          This problem has since been resolved.
          The issue related to running pfSense as a VM when using an additional IP form OVH Cloud.
          When using an OVH additional IP on pfSense the MAC address of the additional IP needs to be entered in the WAN configuration.
          428e2149-dc16-4f6f-8d60-8f681dd8ab63-image.png

          When we restored this pfSense VM from CR and then migrated it to our production host the MAC address had been changed in XO. Once the correct MAC address was reentered into pfSense everything worked again.
          This is a real gotcha when running pfSense as a VM using CR on a host that is not part of the main pool.

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