Edge Virtual: Installation and On-Boarding on the Linux KVM Hypervisor
This guide provides instructions to install and on-board Edge Virtual on the Linux KVM Hypervisor. Our guide is based upon KVM deployed on Ubuntu 20.04 LTS.
Note: Edge Virtual is available in a Limited Release at this time.
- A working Linux KVM Hypervisor.
- Available Edge Virtual Licenses.
- Edge Virtual ISO Installer available from download (please contact Big Network for assistance in obtaining the image)
- Capacity to host a VM with 2x CPUs, 4GB RAM, and 20G available disk space.
- Assume 1x WAN Port and 1x LAN Port for Networking
Step 1: Prepare KVM Networking
The Edge Virtual image expects 1x WAN port and 1x LAN port to be configured for KVM networking.
For our example, we assume that you will use the default KVM network for WAN, and a new, dedicated KVM network for LAN.
Use XML to define the LAN network as edge-virtual-lan.xml:
<ip address="192.168.70.5" netmask="255.255.255.0">
- Create and start the network using "virsh":
virsh net-define edge-virtual-lan.xml
virsh net-start edge-virtual-lan
Step 2: Install Edge OS
Use "virt-install" to create your Virtual Machine and begin the OS installation process.
virt-install --name edge-virtual --memory 4096 --vcpus 2 --network network=default --network network=edge-virtual-lan --disk size=20 --noautoconsole --autostart --cdrom ~/Downloads/edge-2021145.iso
This will boot your virtual machine via the installation media. Connect to the device via Serial Console:
virsh console edgevirtual
- Confirm that you wish to proceed is OS installation. The underlying media will be overwritten.
- Select the "prod" environment.
- Select the "KVM libvirt VM" as the device model.
Allow the installation to complete and Edge Virtual to reboot.
Step 3: Obtain Device ID, PIN, and On-Board Edge Virtual
- Once Edge Virtual reboots, the console will display Device ID and PIN. Note those details down.
- Navigate to https://portal.bignetwork.com -> Edge Devices -> Add Device to begin device on-boarding using the Device ID and PIN.
- Once on-boarded, you will have a 2x Port Edge Virtual device available for use.
Step 4: Verify Connectivity from Host OS
Edge Virtual is now online.
- Form the host OS, Edge Virtual will obtain addressing via DHCP on the KVM default network.
- From the host OS, per the KVM edge-virtual-lan.xml configuration, 192.168.70.5 will be bound as an interface in Linux. 192.168.70.2 will be available as an Edge Dashboard from Linux. Finally, 192.168.70.1 will provide NAT / gateway functionality. Ensuring that 192.168.70.2 responds to ICMP pings confirm connectivity to the Host OS means Edge Virtual is alive.
Configure Edge Virtual for your use case as required. Adjust Linux KVM network configuration as required.
Edge Lite On-Boarding Guide
Introduction This guide is designed to assist with the Edge Lite on-boarding process. Assumptions Device Model: Edge Lite Facility Requirements: Available Internet access service with DHCP WAN addressing (see below for Static WAN IP) Existing Big ...
Edge Pro On-Boarding Guide
Introduction This guide is designed to assist with the Edge Pro on-boarding process. Assumptions Device Model: IEI Puzzle Facility Requirements: Available Internet access service with DHCP WAN addressing (see below for Static WAN IP) Existing Big ...
Headless Linux Client (bn-cli) Explained
Introduction Big Network makes a headless linux client, named "bn-cli", available for linux server environments. bn-cli is used in cases where interactive login via our SSO platform may not be viable for use. Licensing To use the headless linux ...
Big Edge: Local Services
Introduction Big Network's Edge Pro and Edge Lite devices feature the ability to host "Local Services" which are virtual network functions (VNFs) natively available on our devices. Local Services include: Local Breakout Dynamic Host Configuration ...
High Availability Networks with Edge Pro and Edge Lite
Introduction Big Network's Edge Pro and Edge Lite include multiple high availability features to assist network architects and engineers in achieving Service Level Objectives (SLOs). These capabilities are realized by applying various policies to ...