Open Virtual Appliance (OVA) is an OVF
file packaged with a base image Ubuntu image and installed with EFA.
Prerequisites:
- The virtual machine (VM) on which you deploy
the OVA requires a network adapter with a valid IP address and DNS. The IP
address is required to configure the SLX devices to forward syslog entries
back to the VM. The VM needs DNS configuration to resolve the URL during
setup and forwarding of events to the notification subscriber.
- The VM must be able to access switches and the notification subscriber.
- For networks without DHCP, you must assign valid, static IP addresses and
DNS. Then reboot the VM. Ensure that all services are up and running before
running commands.
OVA is compatible with VMware ESXi servers and can be deployed with VMware products. For more
information about supported Ubuntu versions, see Supported Platform Matrix.
Use the OVA image for new installations only.
Warning
- Do not change the host name of the .ova VM after deploying the .ova image.
Doing so prevents EFA PODs from coming online.
- The EFA 2.2.0 OVA is not supported for Oracle VirtualBox. The syslog service
requires port forwarding for port 514 on UDP, but the source IP address of
the syslog message will be changed from the SLX device to the host IP, which
the syslog service ignores.
-
Download the EFA_v2.x.x_<build_number>.ova file.
-
Run the OVA.
-
Start the VM.
The credentials for the OVA installation are:
- Admin/Password:
admin/password
- Root/Password: ubuntu/ubuntu
When the VM starts, a start-up script checks whether the IP address of
the primary interface eth0 has changed since it was last configured. If the IP
address has changed, the script updates the EFA profile and configuration files
appropriately and reapplies the k3s application deployment template. This
operation takes a few minutes to complete. On subsequent VM reboots, if the IP
address has not changed, no operation is performed by the start-up script. The
logs are located under /var/log/efa/installer.
-
Sign in to the VM as the admin
user and then use sudo to run commands (such as sudo efa
supportsave, sudo efa backup, and sudo
efa restore).
The new admin user is added in
the build.
