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

    Get Properties of VxLAN

    Scheduled Pinned Locked Moved Solved Management
    15 Posts 4 Posters 854 Views 4 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.
    • G Offline
      gb.123 @olivierlambert
      last edited by gb.123

      @olivierlambert

      When I create a new Private Network, I can choose Encapsulation, Encrypted (or not), MTU etc.

      Once the Network is created, it does not show if the Network is Encrypted or not.

      Is there any way to know this from CLI ? Or any other way ?

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

        question for @BenjiReis

        1 Reply Last reply Reply Quote 0
        • BenjiReisB Offline
          BenjiReis Vates 🪐 XCP-ng Team @gb.123
          last edited by BenjiReis

          @gb-123 Hi!

          All the info are available on the host by running
          ovs-vsctl show and look a the lines relevant to your bridge.
          Also the following fields are available in your private network other_config:

            - `other_config`:
              - `xo:sdn-controller:encapsulation`       : encapsulation protocol used for tunneling (either `gre` or `vxlan`)
              - `xo:sdn-controller:encrypted`           : `true` if the network is encrypted
              - `xo:sdn-controller:pif-device`          : PIF device on which the tunnels are created, must be physical or VLAN or bond master and have an IP configuration
              - `xo:sdn-controller:preferred-center`    : The host UUID to prioritize as network center (or not defined)
              - `xo:sdn-controller:private-network-uuid`: UUID of the private network, same across pools
              - `xo:sdn-controller:vlan`                : VLAN of the PIFs on which the network is created
              - `xo:sdn-controller:vni`                 : VxLAN Network Identifier,
          

          and the MTU is a field of the network as well.

          So xe network-param-get uuid=<your network uuid> param-name=MTU
          and xe network-param-get uuid=<your network uuid> param-name=other-config param-key=xo:sdn-controller:encrypted

          Or should give everything you need!

          Regards

          G 1 Reply Last reply Reply Quote 2
          • G Offline
            gb.123 @BenjiReis
            last edited by gb.123

            @BenjiReis

            Thank you so much!

            PS: Btw, there is a slight typo in your post. Its other-config instead of other_config

            BenjiReisB 1 Reply Last reply Reply Quote 0
            • BenjiReisB Offline
              BenjiReis Vates 🪐 XCP-ng Team @gb.123
              last edited by

              @gb-123 You're right! I'll edit my post.

              Thx 🙂

              1 Reply Last reply Reply Quote 0
              • olivierlambertO olivierlambert marked this topic as a question on
              • olivierlambertO olivierlambert has marked this topic as solved on
              • planedropP Offline
                planedrop Top contributor
                last edited by

                For what it's worth, @gb-123 you can also view the MTU in both the pool and host network section:

                3366f39c-3683-4617-984b-9da47bbce8e6-image.png

                G 1 Reply Last reply Reply Quote 0
                • G Offline
                  gb.123 @planedrop
                  last edited by

                  @planedrop

                  Yup. I was looking at seeing other properties also (specifically encryption)

                  planedropP 1 Reply Last reply Reply Quote 0
                  • planedropP Offline
                    planedrop Top contributor @gb.123
                    last edited by

                    @gb-123 Yeah I do think it'd be really nice to have all the info exposed in the GUI, not sure if there are any plans for that, but I like the idea.

                    G 1 Reply Last reply Reply Quote 0
                    • G Offline
                      gb.123 @planedrop
                      last edited by

                      @planedrop said in Get Properties of VxLAN:

                      @gb-123 Yeah I do think it'd be really nice to have all the info exposed in the GUI, not sure if there are any plans for that, but I like the idea.

                      +1 for this but I think the Devs are busy with other important features.

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

                        @BenjiReis how difficult to get that info exposed in XO?

                        BenjiReisB 1 Reply Last reply Reply Quote 1
                        • BenjiReisB Offline
                          BenjiReis Vates 🪐 XCP-ng Team @olivierlambert
                          last edited by

                          @olivierlambert Pretty easy since everything is stored in the network other_config field.

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

                            Might worth it then 🙂

                            1 Reply Last reply Reply Quote 1
                            • planedropP Offline
                              planedrop Top contributor
                              last edited by

                              I think this would be awesome, if it's not too much work, would love to see it.

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