Deploy vSZ on rXg via bhyve virtualization
October 13, 2024
Navigate to Services :: Virtualization.
If not already present, create a virtualization host with at least 1 virtual switch. It is almost always the case that you will want to deploy the vSZ on the LAN. Thus it will make the most sense for your virtualization host to have at least a virtual switch on the LAN.
Ensure that you have the .ova (ESXi) version of the vSZ file downloaded from RUCKUS. Run a checksum against the file. (e.g., md5sum vscg-6.1.2.0.441.ova) and note the checksum.
Click Disk Images for the virtualization host and create a new disk with the vSZ .ova file. It is helpful to use the actual filename as the name, because a name value which fails validation will notify you after the upload completes and you will have to await the upload a second time. Let it upload. This will take a while as the vSZ .ova file is 2 GB.
Login via ssh to the rXg and go to /space/disk_images, repeat the checksum and ensure that the checksum matches. If the checksum does not match, retry the upload.
Create a VM.
If not already present, create a virtualization host with at least 1 virtual switch. It is almost always the case that you will want to deploy the vSZ on the LAN. Thus it will make the most sense for your virtualization host to have at least a virtual switch on the LAN.
Ensure that you have the .ova (ESXi) version of the vSZ file downloaded from RUCKUS. Run a checksum against the file. (e.g., md5sum vscg-6.1.2.0.441.ova) and note the checksum.
Click Disk Images for the virtualization host and create a new disk with the vSZ .ova file. It is helpful to use the actual filename as the name, because a name value which fails validation will notify you after the upload completes and you will have to await the upload a second time. Let it upload. This will take a while as the vSZ .ova file is 2 GB.
Login via ssh to the rXg and go to /space/disk_images, repeat the checksum and ensure that the checksum matches. If the checksum does not match, retry the upload.
Create a VM.
- UEFI-CSM bootloader
- give it at least 12 GB of RAM and 2 cores
- name the virtual interface (and attach it to the LAN unless you know you want to do otherwise)
- assign the VM virtual disk to use the vSZ .ova that you uploaded (there is no need to specify a disk size or to resize the disk)
Wait for the VM to be created.
If desired, enable autostart for the VM. This is almost certainly something that you want to do especially for a production environment.
Once created, click start on the scaffold for the new VM.
In the rXg CLI, su into root. Type "vm list" to see all bhyve VMs managed by the rXg.
Type "vm console <vm_name>" to enter the console and setup the vSZ.
The default credentials are admin / admin. Once you enter those you will get the CLI for the vSZ.
Once you are in the CLI for the vSZ, run the "setup" command. This will enable you to configure the IP address.
Once you have configured the IP address, we recommend setting up a virtual host on the rXg for remote access to the vSZ. Keep in mind the vSZ is accessed via HTTPS on port 8443.
