3. Installation

3.1. Start

Login into vCenter. Right click on the directory you want to deploy on and select Deploy OVF Template.

Deploy OVF Template - Start

Fig. 3.1 Deploy OVF Template - Start

3.2. Deploy

Choose how you want to deploy the OVA. You can choose a url or a local device.

Deploy OVF Template - Upload

Fig. 3.2 Deploy OVF Template - Upload

Depending on your vCenter version, you may receive an alert indicating that the SSL Certificate may not be trusted. This is due to Eventide Communications LLC employing self-signed certificates for our OVAs. Please select ‘Yes’ to proceed. (https://kb.vmware.com/s/article/84240)

SSL Alert - Deploy

Fig. 3.3 SSL Alert - Deploy

3.3. Name

Change the Virtual Machine name and select where you want the virtual appliance to deploy.

Deploy OVF Template - Name

Fig. 3.4 Deploy OVF Template - Name

3.4. Computing Resource

Review the requirements in Section 2.3 Computing and select the Computing Resource. If you are unsure, please check with your VMware Administrator.

Deploy OVF Template - Compute Resource

Fig. 3.5 Deploy OVF Template - Compute Resource

3.5. Review

Review the details of your deployment, read the licensing agreement, and accept the licensing agreement.

Deploy OVF Template - Review

Fig. 3.6 Deploy OVF Template - Review

Deploy OVF Template - License Agreement

Fig. 3.7 Deploy OVF Template - License Agreement

3.6. Storage

Select a storage datastore that meets the minimum requirements listed in Section 2.3 Computing. It must have enough free space to support your desired disk size. The virtual disk size is configured in Section 3.9 Post Deployment.

Thick Provision is recommended to prevent the appliance from prematurely running out of disk space.

Caution

Thin Provisioning should only be used by an experienced VMware Administrator, and when appropriate monitoring/alerting of the underlying datastore is configured.

If you are unsure, please check with your VMware Administrator.

Deploy OVF Template - Storage

Fig. 3.8 Deploy OVF Template - Storage

3.7. Network Adapters

Select the Recording Network and Primary Network (These should be different networks). If they are the same, the Recording Network adapter must be disconnected from the virtual appliance in Section 3.9 Post Deployment.

Select Static or DHCP. If you are unsure, please check with your VMware Administrator.

Deploy OVF Template - Network

Fig. 3.9 Deploy OVF Template - Network

3.8. Customize Template

3.8.1. Networking Section

Deploy OVF Template - Network

Fig. 3.10 Deploy OVF Template - Network

If you chose DHCP in Section 2.5 Networking, you can leave the following fields blank: IP Address, Subnet Mask, and Gateway. If you chose Static - Manual in Section 2.5 Networking, you must reserve an IP address and then fill in the necessary information.

Fill in all the networking information specific to your network and NexLog DX-Series (Recorder Name, Hostname, Domain).

3.8.2. Eventide Section

Deploy OVF Template - Eventide

Fig. 3.11 Deploy OVF Template - Eventide

Fill in Site Name and Storage Size (Gb). The maximum size is 18 TB.

The following information is available in the Licenses.txt file and the following fields must be filled in correctly for the NexLog DX-Series virtual appliance to install and function properly:

  • Serial Number

  • Hardware ID

  • Primary License Key

  • Addon License Keys (Multiple keys need to be separated by a space)

  • License Server (See Section 2.5 Networking)

Note

For DX FIPS Licensing, refer to Section 5 FIPS Licensing

3.9. Post Deployment

Wait for the deployment to complete. If you receive an error, please go to Section 6.2 VMware Deployment Failure.

Deploy OVF Template - Post Deployment

Fig. 3.12 Deploy OVF Template - Post Deployment

Before starting/installation of the NexLog DX-Series virtual appliance, select your virtual appliance, and click Edit Settings.

Adjust the size of your Hard Disk 1 to match the Storage (Gb) you selected in Section 3.8.2 Eventide Section. The maximum size is 18 TB.

If the Recording Interface and Primary Interface are the same, disconnect the Network Adapter for the Recording Interface.

3.10. Install the NexLog DX-Series Software

Power on the NexLog DX-Series virtual appliance (please be patient on the first boot) then go through the installer with an Automatic Installation.

3.10.1. Licensing

NexLog DX-Series VMware supports three licensing methods: License Server, Offline Licensing, and License Dongle. Users must use one of these three methods to prevent their recorder from losing functionality.

3.10.1.1. License Server

The NexLog DX-Series VMware appliance must have continuous access to the public internet to connect with the Eventide licensing server. This connection enables ongoing operation and support for the virtual appliance. If the Eventide licensing server becomes unreachable, the virtual appliance will become unlicensed after 30 days, and audio playback will no longer be possible. The license server URL is configured during the OVA setup and can be modified in the NexLog DX-Series Configuration Manager under System -> License Keys -> select the “Primary” license -> click “Modify Key”.

The following may need to be whitelisted on your firewall.

NexLog DX-Series Version greater than 2021.4.1502:

  • License Server URL: license.nexlogdx.host

  • License Server Port: TCP/80

NexLog DX-Series Version less/equal to 2021.4.1502:

  • License Server URL: 1.license.nexlogdx.host

  • License Server Port: TCP/443

3.10.1.2. Offline Licensing

If public internet access is not available, users will need to set up offline licensing with the following procedures:

Download the KeyFile by accessing the NexLog DX-Series Configuration Manager, then go to System -> License Keys -> click “Download KeyFile”. Send this file along with your serial number to Eventide (Email: service@eventidecommunications.com) and make a request for offline licensing in your service ticket.

Download Key File

Fig. 3.13 Download Key File

  • Eventide will provide the primary license key required to license the recorder. To apply, access the NexLog DX-Series Configuration Manager, go to system -> license keys, select the primary key and click “modify key”. Enter the key provided by Eventide in the “license key” field, select “license key file” as the licensing method, then click “save”.

Modifying License Key

Fig. 3.14 Modifying License Key

3.10.1.3. License Dongle

Another method of licensing, if public internet access is not available, is the License Dongle. This method only works if your VMware infrastructure can permanently mount a USB device to the NexLog DX-Series virtual appliance. The virtual appliance will periodically read the smart dongle to maintain a licensed state.

3.10.1.4. DXSUS License Key

Eventide will also provide the DX Software Update Subscription (DXSUS) key. To apply, go to system -> license keys and select “add key”.

Enter the key provided by Eventide in the “license key” field, then select “save”.

3.11. NexLog Access Appliance (VPN)

To access your NexLog DX-Series virtual appliance with the NexLog Access Appliance, you must upload the VPN key. Log into your NexLog DX-Series virtual appliance’s Web Configuration Manager and navigate to Networking → VPN Connections, upload the VPN key, then click Enable, then Save.