Search results

I changed two nodes with this setting last night and named the ports enlan0, enlan1, enlan2 and enlan3. However, after this change the guest on one of the nodes still cannot ping a guest on the other node via a SDN VLAN. I did change the /etc/network/interfaces file and rebooted each node. #...

Thanks for checking! Could we do one of two things then please? 1. Create a note in the SDN documentation explaining the limits of nic names used for SDN bridges 2. Allow more options, like lan*, nic*, net* and possibly others Or both? For now, I'm going to name the nics enlan0, enlan1...

I'll have to schedule to test this carefully, since I cannot risk taking down a node (like I did before) and then it doesn't come back up because the ports have different names than I expected. I'd like to report this as a bug, but I'm not sure what is the cause of this. Is it the systemd...

More... VLAN12 is an SDN and vmbr2 is a manually configured bridge to vlan 25. root@FT1-NodeA:~# ethtool VLAN12 Settings for VLAN12: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes...

I see these in the syslog of the nodes. On the nodeA when the standby firewall is starting: Sep 19 17:14:00 FT1-NodeA systemd-udevd[3462078]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 19 17:14:01 FT1-NodeA kernel: [564541.374585] device tap101i6...

I wrote in my OP: Therefor I can't use ethX, the system has the ability to use those names automatically, so it messed the nics up by swapping them randomly.

I will restart a node after hours and see if that makes any difference.

I completely removed VLAN12. I first removed the interfaces from the firewall machines, then I removed the SDN config. I then restarted the firewall, recreated the SDN for VLAN12, then re-added the interface (which is a bridge on vmbr0), recreated the rules on the pfSense after adding the ip...

Yes, before I did that, the SDN's showed an error. After applying the status returned to normal. Yes, I have actually deleted an complete definition and recreated it, but it has not no noticeable effect. I think I'll just do one again.

Surely someone much have some idea of what is wrong?

32 nodes with 2 x AMD 128core Epyc V4 processors = 8192 vCPU's per cluster. Pretty big. But as others have said, the inter-cluster scripts and automations are the key to making it work.

We ran into a very nasty issue a few days ago. Background: Systemd generates ridiculously long interface names (see https://manpages.debian.org/bookworm/udev/systemd.link.5.en.html and referenced here https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES) like...

When viewing a QEMU machine console with noVNC, the options are to either scale the screen locally, or not. When scaled locally, the text is so small that it's not practically usable. Disabling local scaling fixes that, but then the view screen cannot be shifted left / right or up / down, so...

I have since learned that the live migration is a feature of QEMU. This article describes it nicely. I cannot however see how this would casue the problem we're having.

I have a FreeBSD 12.3 guest running a poller node and when it gets installed everything runs just fine. We can stop and start the guest too, no problem. The guest uses VirtIO SCSI and uses an ceph RBD image of 120GB. The FreeBSD qemu-guest-agent is installed. If for some reason the VM is...

However, when I attempt to do this I get an error which is not documented anywhere afaict # lsblk /dev/sdb NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb...

That's excellent, I wasn't aware of it! It will save a lot of time since rebalancing HDD based OSD's is time-consuming to put it mildly!

I got advice from a seasoned ceph expert to do the following: Split the NVMe drive into 3 OSD (with LVM) to really optimise the use the speed the NVMe offers. So I created additional 2 volumes (5% of the NVMe/ 47GB each) in the NVME to hold the RocksDB and WAL for 2 HDD drives. I'm in the...

I need to do something about the horrible performance I get from the HDD pool on a production cluster. (I get around 500KB/s benchmark speeds!). As the disk usage has been increasing, so the performance has been dropping. I'm not sure why this is, since I have a test cluster, which higher...

Did any of you every find what the cause was of the poor performance?