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

    Sdn controller and physical network

    Scheduled Pinned Locked Moved Advanced features
    12 Posts 5 Posters 1.2k Views 5 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
      mbriet @olivierlambert
      last edited by

      @olivierlambert

      To be clear
      In vmware nsxt WE have a Genève network for Host communication and controller communication
      And After we can create network for virtual machine
      And the controler take the rôle if internal router and IS connect to physical network with bgp to advise the New New network and recieve network fromage bgp peer for the external communication

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

        I'm sorry, I'm struggling to understand what what you write 😞 (since I'm not also a network specialist too). But let's wait for someone else in the community to chime in.

        Theoi-MeteoroiT M 2 Replies Last reply Reply Quote 0
        • Theoi-MeteoroiT Offline
          Theoi-Meteoroi @olivierlambert
          last edited by

          @olivierlambert He seems to be referring to some VMware dynamic networking I think. I looked at Tanzu a couple of years ago and see bits of it there. I try to forget about it because its a terribly expensive k8s platform and breaks the spirit of why I like k8s.

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

            @olivierlambert

            Sure no worries i'm not a network Guy only vmware and storage

            It will be to help for the understanding

            1 Reply Last reply Reply Quote 0
            • Theoi-MeteoroiT Offline
              Theoi-Meteoroi
              last edited by

              I forgot to mention - he also talks about Layer 3 features (BGP) and that he has to configure on his switch in the case of XCP. Most folks don't really have an L3 router beyond their firewall appliance. Not needed. And you can't configure BGP there. Boundary Gateway Protocol is for a more serious exposure to the internet and involves interacting with ASN routing tables. Lets just say beyond the scope of the forum. Most folks operate on a L2 network of some sort and don't configure VLANs. There are many exceptions here, I assume but they would tend to be pretty technical already. This stuff is fire and liability to advise about.

              I see lots of questions here that probably would help with some simple configuration drawings to show a typical small network translated ( NAT ) environment for newbies. There are other tricks like router on a stick and such that mimick IP telephone connections to be able to use VLANs.

              M B 2 Replies Last reply Reply Quote 0
              • M Offline
                mbriet @Theoi-Meteoroi
                last edited by mbriet

                @Theoi-Meteoroi
                I understanding a hâte
                But WE have a network with some vlan
                If i create a private network on thé xcp sdn (i understanfd private network liké Genève network on vmware) Can i create a vlan network for the VM sample vlan 1000
                How Can i route my New network to physical network in other term how m'y physical server Can communicate with my vms
                Or it's not possible in this case what IS the rôle if private network ?
                Does it mean all vlan must be exist on my physical network

                I think i must read somes Doc and see somes vidéo to understanding correctly thé sdn and private network

                Regards

                1 Reply Last reply Reply Quote 0
                • B Offline
                  blackliner @Theoi-Meteoroi
                  last edited by

                  @Theoi-Meteoroi

                  Most folks don't really have an L3 router beyond their firewall appliance

                  Ouch, you just excluded all enterprise customers 😅 But I guess they all use the commercial side of XCP-ng and don't read these forums 😉

                  1 Reply Last reply Reply Quote 0
                  • nikadeN Offline
                    nikade Top contributor
                    last edited by

                    You would need a router within that private vlan which also has an external network and act as a router. Something needs to act as a router between the private network and the external network, with ospf or bgp.

                    We do about the same, with VyOS, and it works pretty good.

                    B 1 Reply Last reply Reply Quote 0
                    • B Offline
                      blackliner @nikade
                      last edited by

                      @nikade How do you "pair" the XCP-ng SDN with your routing setup?

                      nikadeN 1 Reply Last reply Reply Quote 0
                      • nikadeN Offline
                        nikade Top contributor @blackliner
                        last edited by

                        @blackliner said in Sdn controller and physical network:

                        @nikade How do you "pair" the XCP-ng SDN with your routing setup?

                        You cant/dont, you'll have to setup each private network on the vyos router and then have the vm private network routed through it manually.

                        For example if you have private network 1 with subnet 192.168.1.0/24 you'd have to add this network to the vyos router and assign 192.168.1.1/24 on the router.
                        Then set 192.168.1.1 as default gateway in your vm's which uses this network.

                        Then you'll setup ospf or bgp on the vyos router manually with your upstream border/core-router or firewall. If the subnet is a private subnet you'll need to setup NAT as well somewhere before it reaches internet to NAT traffic from 192.168.1.0/24.

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