@olivierlambert Pretty easy since everything is stored in the network other_config
field.
Posts made by BenjiReis
-
RE: Get Properties of VxLAN
-
RE: SDN Controller Errors
@gb-123 AFAIK the host doesn't call XO, if you shut XO off, the private network would continue to work but its state wouldn't change.
It means if you restart an host etc the connection to this host would be lost.The logs depends on how your installed XO or XOA etc so you might want to go through our doc!
Cheers
-
RE: SDN Controller Errors
@gb-123 The tunnel are numbered by order of creation by XAPI, you can't change them.
I don't XCP-ng 8.3 has an issue since we use it internally and the SDN is working fine on our side.
I think some events are triggering the SDN controller to add the host over and over and during the adding of the host the connection might be perturbated. You should take a look a look at XO's logs to see if you can find something that might trigger the SDN controller.Does the host added frequently has another weird behavior?
-
RE: SDN Controller Errors
@gb-123 That's weird
is there another SDN controller connected to your pools? (not necessarily an XO SDN controller) that would override the certificates of XO?
Are there any XAPI error (in
/var/log/xensource.log
) when you restart your VM? -
RE: Get Properties of VxLAN
@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 networkother_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
andxe network-param-get uuid=<your network uuid> param-name=other-config param-key=xo:sdn-controller:encrypted
Or should give everything you need!
Regards
-
RE: New VM MAC address restriction
It's in the backlog indeed but I don't know when the ETA to start this.
I guess an issue in the xen-api repo would be a good first step to see what the XAPI team think of the feature. -
RE: XCP-ng 8.3 beta 🚀
@lethedata Can you share the command you're running and the corresponding SMlog?
Thanks
-
RE: IPv6 support in XCP-ng for the management interface - feedback wanted
@jivanpal you wrote in the 8.3 beta thread:
There is no way to configure IPv6 on the management interface via xsconsole, such as if one wants to switch between static configuration, autoconf via RAs, or DHCPv6.
True but we'll soon release an new version of xsconsole adapted for IPV6 allowing to configure IPv6 for management interface
There is apparently no support for IPv6 DNS servers, only IPv4. For example, if I try to add an IPv6 address like fd00::1 or [fd00::1] as a DNS server via xsconsole, there is apparently no change to the configuration. Editing /etc/resolv.conf works to achieve this (e.g. adding the line nameserver fd00::1), but this is known not to persist across reboots.
Should be solved by the future xsconsole release as well
There is apparently no support for RDNSS (advertisement of DNS servers in RAs rather than via DHCPv6).
DHCPv6 is one of the major blindspot for now indeed, I'm working on it but I don't have much knowledge on this so any hints are welcome if you spot if something is missing somewhere.
The "autoconf" option (available during installation, after choosing IPv6-only or dual-stack, and then being asked which mode to use to configure IPv6 addresses) appears to only be used at installation time to determine values such as the gateway's link-local address, the available address prefixes, and perform SLAAC and DAD, but then the resulting values are hard-coded and don't change according to changes in the environment, such as an upstream change in network prefix. (I will need to do some more testing to really confirm this, but this seems to be the case in my experience.) Compare this to when IPv4 is configured to use DHCP(v4), in which the management interface may have a different IPv4 address at different times, namely if it's assigned a different address by the DHCP server when it attempts to get or renew a lease.
I'm not aware of this issue, i'll try to reproduce in our env.
Some repos are unreachable in IPv6-only environments, which I'm aware is already known, and I can get around this by using NAT64 (either with CLAT to perform 464XLAT; or with DNS64), but this fact is currently a blocker for me to move to being IPv6-only.
We contacted the mirrors many times, still trying to have'em all advertising IPv4 and 6 and also trying to find a solution that could "smartly" redirect towards a compatible mirror.
Speaking of NAT64, this is just a question, I haven't tested or looked into this myself: Does XCP-ng include a CLAT daemon and support for auto-configuring 464XLAT using either the "PREF64" RA option (RFC8781) or resolution of ipv4only.arpa via a DNS64 server (RFC7050)?
Haven't tested either for now, feel free to do and report if you get here before me.
Again, thank you for the report, this is greatly appreciated and any info about what's missing for IPv6 (and perhaps how to achieve it when possible) is welcomed.
Regards!
-
RE: IPv6 support in XCP-ng for the management interface - feedback wanted
In order to upgrade an XCP-ng host and put in IPv6 what could be done also:
- Do the upgrade
xe host-management-disable && xe pif-set-primary-address-type uuid=<udid> primary_address_type=IPv6 ; xe host-management-reconfigure pif-uuid=<uuid>
-
RE: XCP-ng 8.3 beta 🚀
@jivanpal Thx for your report, I'll reply to you in the dedicated IPv6 thread.
Regards
-
RE: IPv6 support in XCP-ng for the management interface - feedback wanted
@lethedata Hi!
Yes indeed it's impossible to change the primary address type of the management interface, it's forbidden by design by XAPI for now. Maybe in the future it'll be allowed but before there still some work to do and then it'd need to be discuss with the XAPI dev team.
I'll try to find a workaround and post here if found but i'm not sure there is for now.
Regards!
-
RE: Adding Master Host to Existing Pool
@Rashid It is normal behavior when you install an host, it is the master of its own 1 host pool so that's not the issue.
Can you post here the results of
cat /etc/xensource-inventory
and check if there's more info in/var/log/xensource.log
when attempting the join? -
RE: Adding Master Host to Existing Pool
@Rashid Hi!
The error seems to indicate the version of your hosts are not at the same level. Can you check?
-
RE: XCP-ng 8.3 beta 🚀
@alex821982 Hi!
We reproduced and find a temporary workaround: on your 8.2 host you can run
xe vm-param-remove uuid=<uuid> param-name=NVRAM param-key=EFI-variables
this will clear the UEFI variables of the NVRAM and so the VM should start after that.
HOWEVER: This does not work on Debian VMs, and on other distro you should make sure to save your VM before in case something goes wrong.We suspect a change in the auth file format between 8.2 and 8.3 is responsible for this issue.
BR
-
RE: XCP-ng 8.3 beta 🚀
@john-c Okay thanks, and are confident in your IPv6 DHCP server etc?
I can't reproduce the issue on my infra and the logs doesn't help much.
-
RE: XCP-ng 8.3 beta 🚀
@john-c It looks like you do have an IPv6 so the issue of start up might be related elsewhere no?