BrianCunnie's Posts

@obsidianindy  Oops—my bad. The last step should be the key, not bundle:   Private Key: click Browse File and select vcenter_domain_co.ca-bundle vcenter_domain_co.key Click Replace.   Thanks for finding it—I'll update the instructions next break.

Thanks so much! I had to tweak your for-loop to get it to work on vCenter 8: for store in $(/usr/lib/vmware-vmafd/bin/vecs-cli store list | grep -v TRUSTED_ROOT_CRLS); do echo "[*] Store :" $store; /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store $store --text | egrep -i "Alias|Subject:|Issuer:"; done

This is what I had to do to fix it for my Sectigo/Comodo certificate: edit the .ca-bundle replace the bad PEM with the good PEM (see attached files) Longer story: the bad & good certificates have the same key (their RSA Modulus is the same) and the same CN ("USERTrust RSA Certification Authority"), so they can be interchanged, but the bad PEM has been cross-signed (issued) by the old, bad "AAA Certificate Services" (which is self-signed with the weak SHA1 algorithm). The good cert is self-signed with the strong SHA-384 algorithm. If you feel uncomfortable downloading the cert from a forum (and you should feel uncomfortable), you can view the details of the good certificate here: https://crt.sh/?id=1199354 And you can download a copy of the PEM here: https://crt.sh/?d=1199354  

Hi Raudi, I was able to get it to work with a clever use of the [Address] and [Route] sections; here's my /etc/systemd/network/10-eth0.network. Yes, I rebooted after I made the changes, yes, I was able to ping6 2600:: and ping 8.8.8.8 after reboot. Yes I was able to successfully kick off a completed backup. Here's a good source for the layout of the file: https://wiki.archlinux.org/index.php/Systemd-networkd#network_files [Match] Name=eth0 [Network] Address=10.0.9.67/24 Gateway=10.0.9.1 IPv6AcceptRouterAdvertisements=false DHCP=no Domains= [Address] Address=2601:646:100:69f0::67/64 [Route] Gateway=2601:646:100:69f0:20d:b9ff:fe48:9249 [DHCP] UseDNS=false

On VCSA 6.7, ssh into your VCSA and run the following commands after you've configured both the IPv4 and IPv6 addresses; after the VCSA reboots both interfaces should be working properly: cp /etc/sysctl.d/99-sysctl.conf{,-orig} # backup file just in case sed -i s/disable_ipv6=1/disable_ipv6=0/ /etc/sysctl.d/99-sysctl.conf shutdown -r now

Thanks peetz, you saved me: I spent hours trying to determine why my 1TB Crucial MX300 M.2 2280 SSD had such abysmal performance (updating BIOS on my skull canyon, updating ESXi, etc...), and now, thanks to your post, I'm getting ~500MB/s read write.