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

    Looking for documentation to migrate from vSphere 8.0.3 to XCP-ng 8.3 using Cicso Intersight Managed Devices.

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    10 Posts 3 Posters 217 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.
    • T Offline
      TheLastOtter
      last edited by TheLastOtter

      I am running into all kinds of problems trying to setup a test lab for XCP-ng.

      We currently have Cisco UCSX C210-M6 Blade Servers, Cisco UCS Fabric Interconnects, Pure Storage C60 Flash Arrays running vCenter/vSphere/ESXI 8.0.3

      Our Blade servers are managed by Cisco Intersight. I had to duplicate a profile and change a few things for XCP-ng like boot from SAN Volume, etc. In vCenter there are Distributed Switches with Multiple VLans associated. The same VLans are configured in our FI's and Blade profiles. Each host has 4 vNICs associated with it. In vCenter 2 are Management and 2 are for Networking of the hosts. vMotion and Managment is assigned to 2 the networking of the hosts and vms are on the other 2.

      In XCP-NG, I can get the hosts to ping all vlans from the shell of the host. The only way to get our VM's to connect/see our network is to assign an ip staticly (since the management vlan is all static) to the vm on the same VLAN as the Host. I tried creating new Networks for each VLAN and then assigning any VLAN to a VM, but the VM cant access our network outside the Management VLAN (same VLAN as host and XOA). Once the VM has a static IP on the same VLAN of the Host, it can see our network and ping all gateways of other VLANs. Our XOA VM had the same issue.

      Is there any kind of documentation that helps setup an XCP-ng environment with Intersight and going from vSphere?

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

        Hi,

        Let me ping @yann-lebris maybe he can help on this 🙂

        1 Reply Last reply Reply Quote 0
        • yann.lebrisY Offline
          yann.lebris Vates 🪐
          last edited by yann.lebris

          Hi @TheLastOtter,

          Can you share your current network configuration on XOA for the related Pool ?

          You can take a screenshot on XOA > Home > Pool > $POOL_NAME$ > Network

          T 1 Reply Last reply Reply Quote 1
          • T Offline
            TheLastOtter @yann.lebris
            last edited by

            @yann-lebris

            Every VM (including XOA)only works when using the Pool-wide network on VLAN2139 which was created by XOA when setting up the Management Interface

            bcd3c99a-0b62-4b2a-bcf0-b4697a260e2c-image.png

            1 Reply Last reply Reply Quote 0
            • T Offline
              TheLastOtter
              last edited by

              I see what I did wrong. I used the same PIF as the Management VLAN.

              yann.lebrisY 1 Reply Last reply Reply Quote 0
              • yann.lebrisY Offline
                yann.lebris Vates 🪐 @TheLastOtter
                last edited by

                Did this resolve your problem by use the right PIF ?

                T 1 Reply Last reply Reply Quote 0
                • T Offline
                  TheLastOtter @yann.lebris
                  last edited by TheLastOtter

                  @yann-lebris I did, however. I cant assign more than 1 VM to the VLAN. When I migrate a 2nd VM and assign it to the same VLAN it takes the IP from the first vlan.

                  This is under Pools-Network
                  1003cd1c-4d92-4ce9-b961-4241f0f8199a-image.png

                  This is under Hosts-HostName-Network
                  9c61e2d3-74e0-46be-9e54-38324a0703e0-image.png

                  yann.lebrisY 1 Reply Last reply Reply Quote 0
                  • yann.lebrisY Offline
                    yann.lebris Vates 🪐 @TheLastOtter
                    last edited by

                    @TheLastOtter On with vlan you try to attach the VMs ? 2139 or 22 or both ?

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      TheLastOtter @yann.lebris
                      last edited by

                      @yann.lebris 22. It is working now. Not sure what it was.

                      yann.lebrisY 1 Reply Last reply Reply Quote 1
                      • yann.lebrisY Offline
                        yann.lebris Vates 🪐 @TheLastOtter
                        last edited by

                        @TheLastOtter Strange. I think you touch nothing on your side?

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