To use AppNeta Performance Manager (APM), you need two things: an app to monitor, and somewhere to monitor from. That ‘somewhere’ is a device that we provide you, which we call a monitoring point. The first thing you need to do is install it within your network.
You can use this setup procedure whether the monitoring point is currently, or has ever been connected to APM. The previous configuration does not need to be erased first, it will be erased automatically.
- Decide where to deploy
- Adjust your firewall rules
- Download a config
- Install the config
- Cable your device
- Assign licenses
- Set the device location
- Advanced network configs
Decide where to deploy
You need to be strategic about where you position your monitoring point:
- Make sure the paths you end up monitoring overlap as much as possible with the end-to-end application delivery path—from the user, through the network, to the server. This means matching your users in terms of geography and maybe even network segment.
- Make sure you’re monitoring from perspective of the people using the app so that your results are relevant to their actual experience. This means thinking about vlan tags and qos in addition to geography.
- Make sure the monitoring point can access an upstream aggregation point so that APM can capture the full variety of applications in use. This typically means being able to mirror traffic passing through a gateway or vlan trunk, or allowing that traffic to pass through your AppNeta monitoring point.
- Make sure that the aggregation point you choose is before any address translation so that private IPs are viewable.
Our recommendation: For ease of deployment, and to get the most out of APM with only one monitoring point, we recommend deploying at the distribution layer.
Adjust your firewall rules
Once you’ve decided where you want to deploy your monitoring point, consult your network administrator to make sure that devices in that part of the network have sufficient access to the internet. This table lists the ports and protocols that need to be allowed through your firewall.
Download a config
You need to install a custom config that helps the device come online and connect back to our servers. You generate this config and a script to install it from inside APM. During that process you’ll include options for custom network settings like static ip, ntp, etc. Anything that is not addressed by the config can be done afterwards by one of our other management tools, e.g., admin API or web admin.
- Log in to login.appneta.com.
- Select an organization if you belong to more than one.
- If you’re setting up your first monitoring point, you’ll automatically be taken to the first step of the ‘add monitoring point’ wizard.
- If your organization already has monitoring points, you’ll have to navigate to the first step:
- Log in.
- Select an organization.
- Navigate to > Manage Monitoring Points.
- Click ‘+ add monitoring points’.
- Click ‘physical monitoring point’.
- Choose ‘usb configuration’—you’ll need a usb stick.
- Follow the instructions that APM provides to generate the config and install script. You’ll need a usb stick.
- Keep APM open. We’ll come back to it later.
Install the config
In the previous step you should have downloaded a .zip file from APM.
- Save the .zip to a fat32-formatted usb stick.
- Making sure that your monitoring point is on and fully-booted, insert the usb stick.
- Look for the status LED to change from heartbeat to rapid beat.
- When the status LED returns to a heartbeat, go back to APM and click ‘assign licenses’.
If your network requires internet traffic to be forwarded by web proxy, the monitoring point won’t be able to connect to APM immediately after the config script runs. This is because the monitoring point doesn’t yet have the proxy details.
If you find yourself outside the add monitoring point workflow, log out and log back in. APM will take you back to the assign licenses step. Or, you can assign the monitoring point a license from > Manage Licenses.
Cable your device
At this point, you can cable your device.
- Verify that the switch you’ll be connecting to has its default port speed and duplex set to auto-negotiate.
- Using a standard ethernet cable, connect the monitoring point to the switch using the port labeled ‘to AppNeta’ in this table.
- Cable the monitoring point for usage monitoring. Choose from either:
All monitoring points need a license before they can do anything. Every monitoring point comes with a base license that allows you to monitor a certain number of applications. Other licenses may be added as needed.
- Go back to APM where you should be prompted to assign the monitoring point a license.
- Assign it at least a base license—called ‘small’, ‘medium’, or ‘large’ depending on your device model.
If you find yourself outside the add monitoring point workflow and there is an unlicensed monitoring point in your organization, navigate to > Manage Licenses to assign it one.
Set the device location
When adding a new monitoring point to APM, you are prompted to enter the it’s location. This setting provides essential context for the data that the monitoring point collects. APM is all about monitoring from the perspective of your end users, and the location setting effectively declares where those users are geographically.
If you find yourself outside the add monitoring point workflow and there is a monitoring point in your organization without a location set, you can set it from > Manage Monitoring Points > > Edit Location.
Advanced network configs
Consider any advanced network or device configs the monitoring point might need. For example, this is where you can add an 802.1Q tag. If you want to monitor over wireless, you need to set up a wireless interface first. If you want to monitor on multiple subnets, you’ll need to configure a second interface, possibly a static route and default gateway.
|Enable ipv6||m25, m35, r45|
|Static routes||m22, m25, m30, m35, r40, r45, r400|
|Wireless interface||m22, m25, m30, m35|
|Bridge interface||r40, r45, r400|
|Physical interface||m25, m30, m35, r40, r45, r400|
|VLAN interface||m22, m25, m30, m35, r40, r45, r400|
|Default gateway||m25, m30, m35, r40, r45, r400|
|Enable TACACS+||m22, m25, m30, m35, r40, r45, r400|