A path is the series of routers that packets take to get from one network device to another. But, in the context of AppNeta Performance Manager (APM), a path not only the series of hops between device A and device B, but also by the quality of service (QoS) the packets receive en route. This is because APM is not just about performance along a path, but performance along a path from the perspective of the application data taking the path.
The recommended method, path setup wizard, is the most involved of the three add-path methods in APM. You can configure one or more paths at a time, target any reachable IP address world-wide, including other monitoring points, and it makes all path attributes available for customization.
- Navigate to Delivery > Path List.
- Click ‘+ add path’.
- Complete the path setup wizard.
- Choose monitoring points. In APM, all paths originate from an AppNeta monitoring point. The monitoring point you select here will be the device that sends out test packets and collects performance information. Select multiple to create more than one path.
- Choose targets. Select the network devices that will be the target of test packets by entering either the ip address or hostname of any network device in the world, including AppNeta monitoring points.
- For best results, enter a computer workstation, server, or AppNeta monitoring point, not a router or switch.
- Be sure to set the target location because it impacts the default path description.
- If you selected multiple monitoring points in Step 1, you can make those monitoring points the end points.
- Before you move to Step 3, the path setup wizard verifies that the source monitoring point can reach the target. You may skip it.
- Customize settings (Optional). This step is totally optional. If you’re creating your first path, and you just want to see how everything works, skip it. You can always go back and change these parameters later. The settings shown here will be applied to all of your new paths, but some individual customization will still be available in the next step. There are a lot of options in this step, but the tooltips contain all the information you need.
- Preview. This step lists all of the paths that are about to be created. Unlike Step 3, where any changes you make are applied to every path, this step lets you make changes to each path individually. The ones you don’t want to add can be de-selected. Paths eligible to be dual-ended are marked in the last column. If you change any paths to dual-ended, be sure to double-check their names. Default path names use the variable, which means that you could end up with a dual-ended path that says ‘(single)’ instead of ‘(dual)’ in the path name. Paths that don’t have a unique combination of source, target, and qos will not be created.