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

  1. Download the static or DHCP config file from here, and save it to an empty, fat32-formatted USB stick.
  2. Uncomment the section you need and specify the items in arrow brackets.
  3. Insert the USB stick into your device, and monitor for device feedback.
  4. Wait for the monitoring point to return to ready.