Your need for additional physical interfaces really depends on your network environment. For example, DNS or AppNeta Performance Manager (APM) might be reachable via a gateway that is not on the subnet that has the targets you want to monitor. In this case you would want to set up a second physical interface: set one as the default interface, which will be used for monitoring point connectivity, and use the other as the source interface for a path. On some device models additional interfaces can be setup up for usage monitoring, such as a bridge interface.

Don’t put two interfaces on the same subnet! It’s not an AppNeta limitation, just one of the fundamentals of routing.

Web admin

  1. Complete monitoring point setup.
  2. Log in to Web Admin.
  3. Click ‘network configuration’.
  4. Click ‘add new interface’.
  5. Make your changes.
  6. Restart networking.

Web admin

  1. Complete monitoring point setup.
  2. Log in to Web Admin.
  3. Click ‘network settings’.
  4. Click ‘network interfaces’.
  5. Click ‘add network interface’.
  6. Make your changes.
  7. Restart networking.

Admin API

  1. Complete monitoring point setup.
  2. Discover your monitoring point hostname at > Manage Monitoring Points.
  3. Find out what interfaces are already configured by plugging the monitoring point hostname into this url, under the interface resource open GET /interface/ and click submit.
  4. Open POST /interface/.
  5. Sub in an interface name and method into this json, paste it into the white box, and click submit. The interface name should begin with ‘eth’ and the options for method are ‘manual’, ‘static’, or ‘dhcp’.

    {
      "name": "IFNAME",
      "method": "METHOD"
    }
    
  6. In the response, look for 'success': true, which lets you know that the interface was successfully created and configured.
  7. Next we’ll need to restart the networking service in order to apply the changes. Under the service resource open PUT /service/{service_name}/, set ‘service_name’ to ‘networking’, ‘action’ to ‘restart’, and then click submit. You will briefly lose connectivity to the admin API.
  8. Verify that your new interface exists by repeating Step 3.

curl

  1. Complete monitoring point setup.
  2. Discover your monitoring point hostname at > Manage Monitoring Points.
  3. Find out what interfaces are already configured.

    curl -X GET --header "Accept: application/json" "https://HOSTNAME/api/v1/interface/?config_state=active"
    
  4. Add a new interface. The interface name should begin with ‘eth’ and the options for method are ‘manual’, ‘static’, or ‘dhcp’.

    curl -k -X POST --header "Content-Type: application/json" -d '{"name": "IFNAME", "method": "METHOD"}' https://admin:ADMINPASS@HOSTNAME/api/v1/interface/
    
  5. Verify that your changes are pending.

    curl -k https://admin:ADMINPASS@HOSTNAME/api/v1/interface/?config_state=pending
    
  6. Restart networking. You will briefly lose connectivity to the admin API.

    curl -k -X PUT --header "Content-Type: application/json" -d {} https://admin:ADMINPASS@HOSTNAME/api/v1/service/networking/?action=restart
    
  7. Verify that your new interface exists by repeating Step 3.

USB

To add a physical interface:

  1. Download the appropriate physical interface config file.
  2. Edit the downloaded config file for your needs.
    • Uncomment sections to be used.
    • Replace content in arrow brackets.
  3. Copy the file onto a USB stick.
  4. Make sure the monitoring point is ready.
  5. Insert the USB stick into the monitoring point.
    • The monitoring point reads the configuration from the USB stick and indicates that it is doing so.
  6. Wait until the monitoring point is finished.
  7. Remove the USB stick.
    • The monitoring point configuration is updated.
    • Any problems updating the configuration are logged in the usb.log file on the USB stick.
  8. Verify that the interface acquired an IP address.
    1. In APM, navigate to > Manage Monitoring Points.
    2. Select the monitoring point you are interested in.
    3. On the right side panel, check Local Network Interfaces for an IP address on the interface.