virt-manager installed using homebrew defaults to /usr/local/var/run/libvirt/libvirt-sock for the libvirtd socket location on remote hosts. This is not a valid location and the connection fails. The work around is to use a custom connection string and pass the correct socket location. e.g. qemu+ssh://<user name>@<host address>/system?socket=/var/run/libvirt/libvirt-sock
Successfully upgraded my Fedora 35 work station to Fedora 36 today. ❯ cat /etc/redhat-release Fedora release 35 (Thirty Five) ❯ sudo dnf makecache ❯ sudo dnf upgrade --refresh ❯ sudo dnf install dnf-plugin-system-upgrade ❯ sudo dnf system-upgrade download --releasever=36 Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]:y Transaction Summary ============================================================================================================================================= Install 114 Packages Upgrade 1859 Packages Remove 4 Packages Downgrade 1 Package Total download size: 2.1 G DNF will only download packages, install gpg keys, and check the transaction. Is this ok [y/N]:y Total 6.3 MB/s | 2.1 GB 05:34 Fedora 36 - x86_64 - Updates 1.6 MB/s | 1.6 kB 00:00 Importing GPG key 0x38AB71F4: Userid : "Fedora (36) <[email protected]>" Fingerprint: 53DE D2CB 922D 8B8D 9E63 FD18 999F 7CBF 38AB 71F4 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 Is this ok [y/N]:y Key imported successfully Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Complete! Transaction saved to /var/lib/dnf/system-upgrade/system-upgrade-transaction.json. Download complete! Use 'dnf system-upgrade reboot' to start the upgrade. To remove cached metadata and transaction use 'dnf system-upgrade clean' The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. ❯ sudo dnf system-upgrade reboot ❯ cat /etc/redhat-release Fedora release 36 (Thirty Six) ❯ sudo dnf upgrade Last metadata expiration check: 0:00:43 ago on Sun 15 May 2022 01:54:21 PM CDT. Dependencies resolved. Nothing to do. Complete!
Follow the steps below to assign or change the IP address on the management interface on a Arista swtich. localhost> en localhost# configure localhost(config)# interface management 1 localhost(config-if-Ma1)# ip address 192.168.57.2/24 localhost(config-if-Ma1)# show active interface Management 1 ip address 192.168.57.2/24 localhost(config-if-Ma1)# exit localhost(config)# exit localhost# copy running-config startup-config
localhost> en localhost# conf localhost(config)# username admin secret supersecretpassword
Whether logging a support call or planning an upgrade, knowing your current running software version is crucial. Here’s two ways to quickly get the EOS version running on your Arista switch router. Option 1 Use the show version command. ([email protected]) Password: Last login: Thu Feb 24 15:33:07 2022 from 192.168.1.253 SW01(s1)>en SW01(s1)#show version | grep Software Software image version: 4.18.5M SW01(s1)# Option 2 Use the base Linux OS ([email protected]) Password: Last login: Thu Feb 24 15:33:07 2022 from 192.168.1.253 SW01(s1)>en SW01(s1)#bash Arista Networks EOS shell [admin@SW01 ~]$ cat /etc/system-release Arista Networks EOS 4.18.5M SW01(s1)#