The AppNeta v35 is a virtual monitoring point that runs as a virtual machine on a host system. This version of the v35 runs on a host system running the VMware ESXi hypervisor.

  1. Prerequisites
  2. Create a v35 virtual machine
    1. Set up a v35 using vCenter
    2. Set up a v35 without using vCenter
  3. Configure for web proxy if required
  4. Assign licenses
  5. Set the monitoring point location
  6. Configure VMware for Usage monitoring
  7. Set up monitoring

Prerequisites

The following are the minimum requirements for an ESXi host:

  • The ESXi host must be running vSphere 5.5.0 or later.
  • The ESXi host must be capable of hosting a guest with the v35 requirements.
  • The ESXi host should have two physical NICs. The first is for connectivity to APM and for Delivery and Experience monitoring. The second is for Usage monitoring.
  • The ESXi host must be connected to your network via the first NIC.
  • Firewall rules must allow the v35 to connect back to APM.

Create a v35 virtual machine

You can install the v35 onto a host running ESXi using vCenter or without it.

Set up a v35 using vCenter

If you are using vCenter to manage your VMware resources, you can use it to create a v35. There are a few steps required:

  1. Download v35 template (vCenter) and generate a configuration file
  2. Create the v35 using the template and configuration file
  3. Power on the v35

Download v35 template (vCenter) and generate a configuration file

To download the v35 template and generate a configuration file:

  1. Log in to APM.
  2. Select the organization you want the monitoring point to be part of.
  3. Navigate to > Manage Monitoring Points > + Add Monitoring Points > Virtual Monitoring Point.
  4. Click Download the v35 for VMware Platform.
  5. Click Download VMware Base Image (vCenter).
    • A .ova image file is downloaded to your computer. This may take a while as the file is large.
  6. Click Continue.
  7. Follow the instructions provided to create a configuration .zip file.
    • Stop once you click Generate.
    • The .zip file is downloaded to your computer.
  8. Unzip the .zip file.

Create the v35 using the template and configuration file

To create the v35 using the template and configuration file:

  1. In a separate tab on your browser, log in to vCenter.
  2. In the inventory list, select the host on which you want to deploy the v35.
  3. Click Actions > Deploy OVF Template.
  4. Select Local file and click Browse.
  5. Browse for the .ova image file you downloaded, select the file and click Open.
  6. Click Next.
  7. Enter a name for the VM and select the deployment location.
  8. Click Next.
  9. Follow the instructions to create a virtual machine until you reach the Customize Template page.
  10. Copy the contents of the .json file you downloaded and paste them into the AppNeta Monitoring Point Configuration field.
  11. Click Next.
  12. Click Finish.
    • Wait for the v35 deployment to complete.

Power on the v35

To power on the v35:

  1. Within vCenter, select the v35 from the inventory in the Navigator panel.
  2. Click the “Power On” button.
  3. Click the “Open Console” button and wait for the login prompt.
    • The v35 is powered on.
  4. Continue at Configure for web proxy if required.

Set up a v35 without using vCenter

If you are not using vCenter to manage your VMware resources, you can create a v35 directly on ESXi using the vSphere Client. There are a few steps required:

  1. Download v35 template (non-vCenter) and generate a configuration file
  2. Create a v35 using the template
  3. Power on the v35 and apply the configuration

Download v35 template (non-vCenter) and generate a configuration file

To download the v35 template and generate a configuration file:

  1. Log in to APM.
  2. Make sure you are using the correct organization
  3. Navigate to > Manage Monitoring Points > + Add Monitoring Points > Virtual Monitoring Point.
  4. Click Download the v35 for VMware Platform.
  5. Click Download VMware Base Image (ESXi).
    • A .ova image file is downloaded to your computer. This may take a while as the file is large.
  6. Click Continue.
  7. Follow the instructions provided to create a configuration .zip file.
    • Stop once you click Generate.
    • The .zip file is downloaded to your computer.
  8. Unzip the .zip file.

Create a v35 using the template

To create a v35 using the template:

  1. Use the vSphere Client to login to the ESXi host.
  2. Click File > Deploy OVF Template.
  3. Click Browse.
  4. Browse for the .ova image file you downloaded, select the file and click Open.
  5. Click Next.
  6. Click Next.
  7. Enter a name for the VM and select the deployment location.
  8. Click Next.
  9. Follow the instructions to complete the VM deployment as you would other VMs.
  10. Click Finish.
    • Wait for the v35 deployment to complete.

Power on the v35 and apply the configuration

To power on the v35 and apply the configuration:

  1. Select the v35 from the inventory list.
  2. Click the “Power On” button.
  3. Click the “Launch Virtual Machine Console” button and wait for the login prompt.
  4. Log in as admin using the password you specified when creating the configuration.
  5. At the command prompt, enter sudo ifconfig eth0. Note the IP address.
  6. In a new browser tab, enter “https://<IP address>” to access the monitoring point Web Admin interface.
  7. Log in as admin using the password you specified when creating the configuration.
  8. Navigate to > API to load the monitoring point Admin API interface.
  9. Navigate to Batch > POST /batch/.
  10. Click Try it out.
  11. For the appliance_config_file parameter, click Choose File.
  12. Select the .json file you downloaded and click Open.
  13. Click Execute.
  14. Sign in as admin using the password you specified when creating the configuration.
    • Confirm that the response code is 200 and that there are no errors.
  15. In the monitoring point Web Admin interface tab in your browser, click > Restart Monitoring Point.
    • Wait for the monitoring point to restart (wait for the login prompt in the Virtual Machine Console).

Configure for web proxy if required

If internet traffic on your network is forwarded by a web proxy, you must configure the monitoring point with the proxy details.

Assign licenses

Every monitoring point is sold with a base license that allows it to monitor a certain number of applications. The base license must be assigned to the monitoring point in APM before it can be used. Optionally, add-on licenses can be assigned.

To license a monitoring point:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. Wait for the new monitoring point to show up in the list (you may need to refresh your screen).
    • The monitoring point status should show “Connection Established” (Green circle with white check mark).
    • If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
  3. Assign a base license to the monitoring point.
  4. Optionally, assign add-on licenses as required.

Set the monitoring point location

When adding a new monitoring point to APM, you need to specify its location. This setting provides essential geographical context for the data that the monitoring point collects.

To set the location of the monitoring point:

  1. Enter the monitoring point location if prompted during the setup procedure.

Configure VMware for Usage monitoring

If you plan to use Usage monitoring, you need to associate the pre-configured Usage monitoring interface on the v35 (eth1) with the appropriately configured physical NIC on the ESXi host. The instructions below provide high level guidance. Consult the VMware documentation for detailed instructions.

  1. Configure an upstream physical switch to mirror the traffic you want to monitor to one of its ports.
  2. Using an Ethernet cable, connect this physical switch port to the physical NIC on the ESXi host to be used for Usage monitoring (Network Adapter 2).
  3. Within VMware, create a standard virtual switch and assign it the physical NIC to be used for Usage monitoring.
  4. On this virtual switch, create a portgroup dedicated to Usage monitoring.
  5. On the portgroup, configure promiscuous mode so that interfaces defined within it can detect all traffic passed on the switch and allowed under the VLAN policy for the portgroup.
  6. Configure the portgroup to limit traffic to the desired VLANs or set it to “ALL (4095)” to enable all VLANs.
  7. Assign eth1 to the portgroup by editing the hardware settings of your v35:
    1. Assign the port group to Network Adapter 2.
    2. Make sure the Connected option is enabled.

Set up monitoring

At this point the monitoring point setup is complete. Continue the APM setup procedure at Set up monitoring.

Call Support: 800-664-4401
Contact Us