Recently I had to upgrade an HPE DL325 server which was running on VMWare ESXi 6.7U3 HPE Custom ISO, to VMWare ESXi 7.0.2 HPE Custom ISO
Doing so I got an “MISSING_DEPENDENCY_VIBS ERROR” on module HPE_bootbank_ssacli_184.108.40.206-220.127.116.11355516 at the end of the installation process.
To solve this, you have to reboot your ESXi host, enable SSH on it and then disable the problematic module so the upgrade process can proceed without an error:
[root@esxi1ng:~] esxcli software vib list | grep ssacli
ssacli 18.104.22.168-22.214.171.12435516 HPE PartnerSupported 2020-05-05
[root@esxi1ng:~] esxcli software vib remove --vibname ssacli
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Removed: HPE_bootbank_ssacli_126.96.36.199-188.8.131.5235516
Done, that’s all there is to it, you can now upgrade.
In our previous post, we showed how to automatically generate and activate/renew a Let’s Encrypt TLS certificate on a Mikrotik device: https://www.amd-k6.com/automate-letss-encrypt-tls-certificate-on-mikrotik-routeros/
Today, we look at configuring an SSTP VPN server which uses this certificate so you can remotely connect to your Mikrotik router from a Windows PC, for example.
The first step is to create a VPN user, this is done in PPP > Secrets. The options are mostly straightforward:
Name: you username
Password: select a strong password
Service: select sstp
Local address: set the IP address of you mikrotik device on the LAN-side
Remote address: this is the IP address you will get from the VPN, select an address that is available on your LAN
To configure an SSTP or OpenVPN service on my Mikrotik Router, I had the need to generate and upload a real TLS certificate to the device. Some solutions exist in various blog posts but they are either too complicated, outdated or badly documented. So I made my own post and script. I hope it helps someone!
The goal here is to generate a Let’s Encrypt certificate and upload/activate it on a Mikrotik router. What you will need to do manually is:
Generate a Let’s Encrypt certificate
Create an user to SSH to your Mikrotik
Run the script to transfer and activate the certificate
If you ever installed a Kubernetes cluster, you probably know that the minimal setup is composed of 2 nodes: a Control Plane Node (previously called master) and a Worker Node. This is a good thing as we usually don’t want workloads interfering with the API in production environments.
But what about lab environments where you want to run everything in a single VM for example? Well, it’s absolutely possible and actually very simple to configure a Control Plane Node to also accept workloads (pods).
This is managed by “taints”, which is a configuration string applied to nodes. On your Control Plant Node, you can see this by running:
This post has nothing to do with the usual content of this website (not K6 related) but I’m sharing my experience of configuring a CentOS Stream 8 Linux software RAID 1 installation on an UEFI system that actually boots when you replace a failed disk.
Most of the tutorials and articles online are about such installations where the the disks are in MBR (legacy) mode and not GPT (UEFI) and this has a huge impact on how your system boots and how you act when a disk fails. We’ll have a look at a scenario where we:
Start by installing CentOS Stream 8 in software RAID 1 (on 2 disks) mode
Simulate the failing of one drive
Replace the drive so the RAID arrays are synchronized again
Configure the UEFI to be able to boot on this new replacement drive
For demonstration purposes, this will be done using a VM in VirtualBox, but it also applies to any PC or Server booting in UEFI mode, as most machines do nowadays.
One of the hardest things to get right when currently installing a K6 machine is to have a working Windows/DirectX/Drivers combination. Well after some sweat I’m happy to say that I finally found the perfect sweet-spot:
Windows 2000 with unofficial SP5
nVidia GeForce FX 5700 with series-50 drivers
DirectX 9.0c from july 2006 (later versions may require SSE and crash on a K6 without telling you that)
This great success has lead to the update of the OS Support page with all the info one may want and need…the system doesn’t BSOD on nv4_disp.dll when running DirectX 8/9 applications and OpenGL also works fine!
If like me you are (or are looking to) running an SATA HDD/SSD in you K6 machine, you are probably wondering if you should buy a dedicated bootable SATA host-bus adapter PCI card or maybe use an IDE to SATA converter to plug your SATA drive on the motherboard’s IDE ports.
A good Promise PCI card will cost you around 30€ and it works flawlessly and performs very well, but what about these adapters from China you can get for 10€? Well, I tested 2 of them; they all use the same chipset and only the PCB differs a bit. Both adapter’s PCB look like shit with soldering marks all over the place; they are cheaply made but at first glance they work well.
Unfortunately, they perform horribly bad to the point where I had the feeling my K6 system was 4-5 slower doing any action using the disk…so do yourself a favour and avoid them. Buy a good SATA controller instead!