In order to use Delivery monitoring to monitor the network between a source and a target you need to create a network path. In its most basic form, this simply involves specifying a source monitoring point and a target (which may or may not be a monitoring point). The network path is the path through the network between the source and the target. Depending on the type of application data you expect to travel across this path, you may also need to specify quality of service (QoS) parameters in order for the Delivery monitoring packets sent by the monitoring point(s) to accurately emulate the application traffic.

Create a network path

Before creating a network path, there are a number of things you’ll need to consider, like deciding whether it should be a single-ended path or a dual-ended path and how to select a path target. See Considerations for Network Paths for details.

Once you are ready, there are a number of ways to create it.

Single-ended - individual targets - this is the typical method for creating single-ended network paths using the Path Setup Wizard. It allows you to create the paths by selecting individual path targets. Any target type can be used.
Single-ended - mesh - this method allows you to create all possible combinations of paths between selected monitoring points using the Path Setup Wizard. It requires monitoring points on both ends of the path.
Single-ended - hub and spoke - this method allows you to create paths from one monitoring point to selected monitoring points using the Path Setup Wizard. It requires monitoring points on both ends of the path.
Single-ended - Discover My Network - this method is used to create many single-ended network paths at once using network discovery to identify possible targets. Any target type can be used.
Single-ended - Add Demonstration Paths - this method is a very basic version of the Path Setup Wizard using default parameters and a limited number of well-known websites as targets.
Dual-ended - individual targets - this is the typical method for creating dual-ended network paths using the Path Setup Wizard. It allows you to create the paths by selecting individual path targets. It requires monitoring points or AppNeta WAN targets as targets.
Dual-ended - mesh - this method allows you to create all possible combinations of paths between selected monitoring points using the Path Setup Wizard. It requires monitoring points on both ends of the path.
Dual-ended - hub and spoke - this method allows you to create paths from one monitoring point to selected monitoring points using the Path Setup Wizard. It requires monitoring points on both ends of the path.
Dual-ended - from single-ended - this method allows you to create a dual-ended path from a single-ended path.

Single-ended - individual targets

This method is a simple way to create single-ended network paths by specifying targets individually.

To create one or more single-ended network paths:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
    • The Path Setup Wizard tab is selected.
  3. In Step 1:
    • Select source monitoring points for the network paths you want to create.
    • If you want to monitor from a non-default interface on a monitoring point, select the appropriate interface in the Local Network Interface column.
    • Click Next.
  4. In Step 2:
    • Select Choose Targets.
    • Specify path targets and their locations. All target types are valid.
    • Click Next.
  5. In Step 3, pay special attention to the following fields:
    • Group - select the network path group to add the path(s) to.
    • Importance - select the path importance from 1 to 10 (where 10 is most important). This field is used for filtering and grouping.
    • Dual-Ended Path - make sure Set to Dual Ended Path if possible is not selected.
    • Network Type - select LAN.
    • Target Type - select Auto for most cases. Only use a different Target Type if there is a very specific traffic type you are trying to emulate.
    • VoIP Codec - select the codec to be used when taking measurements for voice traffic. This will be ignored if a data-only Target Type is selected.
    • QoS Settings - specify DSCP values that match the type of the traffic that will be traveling via the network path(s).
    • Alert Settings - consider changing the Alert Profile to something other than Connectivity.
    • Click Next.
  6. In Step 4:
    • A list of network paths being created is shown.
    • You can deselect any you don’t want to create.
    • Changes can be made to a subset of parameters on each network path.
    • Paths that can be dual-ended are marked in the last column. If you change any paths to be dual-ended, be sure to check their names as default path names use the variable. Because of this, 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.
    • Click Add Network Paths.
      • The network paths are created in the group specified.

Single-ended - mesh

This method allows you to create all possible combinations of network paths between selected monitoring points. For example, if you select four monitoring points, six paths will be created.

Note: This method only works if the source and target monitoring points can resolve each other by hostname.

To create one or more single-ended network paths using this method:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
    • The Path Setup Wizard tab is selected.
  3. In Step 1:
    • Select monitoring points that will be endpoints in the network paths you want to create.
    • If you want to monitor from a non-default interface on a monitoring point, select the appropriate interface in the Local Network Interface column.
    • Click Next.
  4. In Step 2:
    • Select Set Monitoring Points as Endpoints.
    • In the Network Topology field, select Mesh.
    • In the Network Type field, select LAN.
    • In the Instrumentation field, select Single-Ended (or select Single and Dual-ended to create both single- and dual-ended paths).
    • To change path direction or to remove a path, click a path in the diagram. Change Path Direction and Remove Path buttons appear to the right of the diagram.
    • Click Next.
  5. In Step 3, pay special attention to the following fields:
    • Group - select the network path group to add the path(s) to.
    • Importance - select the path importance from 1 to 10 (where 10 is most important). This field is used for filtering and grouping.
    • Target Type - select Auto for most cases. Only use a different Target Type if there is a very specific traffic type you are trying to emulate.
    • VoIP Codec - select the codec to be used when taking measurements for voice traffic. This will be ignored if a data-only Target Type is selected.
    • QoS Settings - specify DSCP values that match the type of the traffic that will be traveling via the network path(s).
    • Alert Settings - consider changing the Alert Profile to something other than Connectivity.
    • Click Next.
  6. In Step 4:
    • A list of network paths being created is shown.
    • You can deselect any you don’t want to create.
    • Changes can be made to a subset of parameters on each network path.
    • Paths that can be dual-ended are marked in the last column. If you change any paths to be dual-ended, be sure to check their names as default path names use the variable. Because of this, 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.
    • Click Add Network Paths.
      • The network paths are created in the group specified.

Single-ended - hub and spoke

This method allows you to create network paths between one monitoring point and all other selected monitoring points.

Note: This method only works if the source and target monitoring points can resolve each other by hostname.

To create one or more single-ended network paths using this method:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
    • The Path Setup Wizard tab is selected.
  3. In Step 1:
    • Select monitoring points that will be endpoints in the network paths you want to create.
    • If you want to monitor from a non-default interface on a monitoring point, select the appropriate interface in the Local Network Interface column.
    • Click Next.
  4. In Step 2:
    • Select Set Monitoring Points as Endpoints.
    • In the Network Topology field, select Hub and Spoke.
    • In the Hub field, select the monitoring point you want common to all paths.
    • In the Network Type field, select LAN.
    • In the Instrumentation field, select Single-Ended (or select Single and Dual-ended to create both single- and dual-ended paths).
    • To change path direction or to remove a path, click a path in the diagram. Change Path Direction and Remove Path buttons appear to the right of the diagram.
    • Click Next.
  5. In Step 3, pay special attention to the following fields:
    • Group - select the network path group to add the path(s) to.
    • Importance - select the path importance from 1 to 10 (where 10 is most important). This field is used for filtering and grouping.
    • Target Type - select Auto for most cases. Only use a different Target Type if there is a very specific traffic type you are trying to emulate.
    • VoIP Codec - select the codec to be used when taking measurements for voice traffic. This will be ignored if a data-only Target Type is selected.
    • QoS Settings - specify DSCP values that match the type of the traffic that will be traveling via the network path(s).
    • Alert Settings - consider changing the Alert Profile to something other than Connectivity.
    • Click Next.
  6. In Step 4:
    • A list of network paths being created is shown.
    • You can deselect any you don’t want to create.
    • Changes can be made to a subset of parameters on each network path.
    • Paths that can be dual-ended are marked in the last column. If you change any paths to be dual-ended, be sure to check their names as default path names use the variable. Because of this, 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.
    • Click Add Network Paths.
      • The network paths are created in the group specified.

Single-ended - Discover My Network

This method allows you to use Discover My Network to add network paths to multiple targets discoverable from your monitoring point. You can discover targets on the local network or within a range of remote addresses. APM automatically configures paths to every device that the source can reach. You can preview and customize them before adding, but, because this is a bulk configuration, only the essential parameters are available.

Network discovery uses ICMP and UDP to discover hosts. In order to be discovered, hosts must:

  • allow inbound ICMP echo-requests and respond to them with echo-reply
  • allow inbound UDP packets to high port numbers and respond to them with ICMP port-unreachable

To create one or more single-ended network paths using Discover My Network:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
  3. Select the Discover My Network tab.
  4. Specify the parameters for discovery.
    • Make sure Path is selected.
  5. Click Start Discovery.
    • A list of discovered network hosts is created.
  6. Select the hosts you want to use as network path targets.
  7. Specify path configuration (Group, Importance, and QoS Settings).
  8. Click Add Selected Paths.
    • The network path(s) to the selected host(s) is(are) created.

Single-ended - Add Demonstration Paths

This method allows you to use Add Demonstration Paths to create one or more paths from a source monitoring point to one or more well-known websites. All other path parameters are defaulted.

To create one or more single-ended network paths using Add Demonstration Paths:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
  3. Select the Add Demonstration Paths tab.
  4. In the Monitor From field, select the source monitoring point.
  5. Select the target(s) from the list of well-known websites.
  6. Click Submit.
    • The network path(s) is(are) created.

Dual-ended - individual targets

This method is a simple way to create dual-ended network paths by specifying targets individually.

To create one or more dual-ended network paths:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
    • The Path Setup Wizard tab is selected.
  3. In Step 1:
    • Select source monitoring points for the network paths you want to create.
    • If you want to monitor from a non-default interface on a monitoring point, select the appropriate interface in the Local Network Interface column.
    • Click Next.
  4. In Step 2:
  5. In Step 3, pay special attention to the following fields:
    • Group - select the network path group to add the path(s) to.
    • Importance - select the path importance from 1 to 10 (where 10 is most important). This field is used for filtering and grouping.
    • Dual-Ended Path - make sure Set to Dual Ended Path if possible is selected.
    • Network Type - select LAN.
    • Target Type - select Auto for most cases. Only use a different Target Type if there is a very specific traffic type you are trying to emulate.
    • VoIP Codec - select the codec to be used when taking measurements for voice traffic. This will be ignored if a data-only Target Type is selected.
    • QoS Settings - specify DSCP values that match the type of the traffic that will be traveling via the network path(s).
    • Alert Settings - consider changing the Alert Profile to something other than Connectivity.
    • Click Next.
  6. In Step 4:
    • A list of network paths being created is shown.
    • You can deselect any you don’t want to create.
    • Changes can be made to a subset of parameters on each network path.
    • Paths that don’t have a unique combination of source, target, and QoS will not be created.
    • Click Add Network Paths.
      • The network paths are created in the group specified.

Dual-ended - mesh

This method allows you to create all possible combinations of network paths between selected monitoring points. For example, if you select four monitoring points, six paths will be created.

Note: This method only works if the source and target monitoring points can resolve each other by hostname.

To create one or more dual-ended network paths using this method:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
    • The Path Setup Wizard tab is selected.
  3. In Step 1:
    • Select monitoring points that will be endpoints in the network paths you want to create.
    • If you want to monitor from a non-default interface on a monitoring point, select the appropriate interface in the Local Network Interface column.
    • Click Next.
  4. In Step 2:
    • Select Set Monitoring Points as Endpoints.
    • In the Network Topology field, select Mesh.
    • In the Network Type field, select LAN.
    • In the Instrumentation field, select Dual-Ended (or select Single and Dual-ended to create both single- and dual-ended paths).
    • To change path direction or to remove a path, click a path in the diagram. Change Path Direction and Remove Path buttons appear to the right of the diagram.
    • Click Next.
  5. In Step 3, pay special attention to the following fields:
    • Group - select the network path group to add the path to.
    • Importance - select the path importance from 1 to 10 (where 10 is most important). This field is used for filtering and grouping.
    • Target Type - select Auto for most cases. Only use a different Target Type if there is a very specific traffic type you are trying to emulate.
    • VoIP Codec - select the codec to be used when taking measurements for voice traffic. This will be ignored if a data-only Target Type is selected.
    • QoS Settings - specify DSCP values that match the type of the traffic that will be traveling via the network path.
    • Alert Settings - consider changing the Alert Profile to something other than Connectivity.
    • Click Next.
  6. In Step 4:
    • A list of network paths being created is shown.
    • You can deselect any you don’t want to create.
    • Changes can be made to a subset of parameters on each network path.
    • Paths that don’t have a unique combination of source, target, and QoS will not be created.
    • Click Add Network Paths.
      • The network paths are created in the group specified.

Dual-ended - hub and spoke

This method allows you to create network paths between one monitoring point and all other selected monitoring points.

Note: This method only works if the source and target monitoring points can resolve each other by hostname.

To create one or more dual-ended network paths using this method:

  1. Navigate to Delivery > Network Paths.
  2. Click + Network Path.
    • The Path Setup Wizard tab is selected.
  3. In Step 1:
    • Select monitoring points that will be endpoints in the network paths you want to create.
    • If you want to monitor from a non-default interface on a monitoring point, select the appropriate interface in the Local Network Interface column.
    • Click Next.
  4. In Step 2:
    • Select Set Monitoring Points as Endpoints.
    • In the Network Topology field, select Hub and Spoke.
    • In the Hub field, select the monitoring point you want common to all paths.
    • In the Network Type field, select LAN.
    • In the Instrumentation field, select Dual-Ended (or select Single and Dual-ended to create both single- and dual-ended paths).
    • To change path direction or to remove a path, click a path in the diagram. Change Path Direction and Remove Path buttons appear to the right of the diagram.
    • Click Next.
  5. In Step 3, pay special attention to the following fields:
    • Group - select the network path group to add the path(s) to.
    • Importance - select the path importance from 1 to 10 (where 10 is most important). This field is used for filtering and grouping.
    • Target Type - select Auto for most cases. Only use a different Target Type if there is a very specific traffic type you are trying to emulate.
    • VoIP Codec - select the codec to be used when taking measurements for voice traffic. This will be ignored if a data-only Target Type is selected.
    • QoS Settings - specify DSCP values that match the type of the traffic that will be traveling via the network path(s).
    • Alert Settings - consider changing the Alert Profile to something other than Connectivity.
    • Click Next.
  6. In Step 4:
    • A list of network paths being created is shown.
    • You can deselect any you don’t want to create.
    • Changes can be made to a subset of parameters on each network path.
    • Paths that don’t have a unique combination of source, target, and QoS will not be created.
    • Click Add Network Paths.
      • The network paths are created in the group specified.

Dual-ended - from single-ended

You can create a dual-ended network path from a single-ended path, but the existing path source and the path target must both be monitoring points.

To create a dual-ended path from a single-ended path:

  1. Navigate to Delivery > Network Paths.
  2. Next to the single-ended path you want to modify, navigate to > Configure.
  3. Click Create this path with dual-ended instrumentation.
  4. Update the path name (optional).
  5. Click Submit.
    • A dual-ended network path is created and the single-ended path still exists.

Edit a network path

You can edit a network path configuration after it has been created. Any time you change a path attribute, monitoring is restarted and the change is indicated on performance charts with a vertical grey line.

APM prevents you from combining conflicting attributes (for example, configuring a data target type with voice alert threshold). If there is a conflict, the change is not applied to the path.

To edit a network path configuration:

  1. Navigate to Delivery > Network Paths.
  2. For the network path you want to edit, select > Configure.
  3. Follow the Path Setup Wizard and update the path configuration as required.
  4. Click Save.
    • The updated network path configuration is saved.

Reset a network path name

When a monitoring point’s name changes or paths are moved between monitoring points, the path names are not changed. This can be confusing if paths are named using the default naming convention (<SourceName> <-> <TargetName>) because the “SourceName” still reflects the old monitoring point name. In these cases, the path names should be changed to use the new monitoring point name as the “SourceName”.

You can reset one network path at a time or several at once.

To reset a network path name to use the correct “SourceName”:

  1. Navigate to Delivery > Network Paths.
  2. For the network path you want to rename, select > Reset Path Name.
    • The name of the selected path is updated to use the correct “SourceName”.

To reset one or more network path names to use the correct “SourceName”:

  1. Navigate to Delivery > Network Paths.
  2. Select the network paths you want to rename.
  3. From the Action drop-down, select Reset Name.
  4. Confirm the network paths you want to rename.
  5. Click OK.
    • The names of the selected paths are updated to use the correct “SourceName”.

Delete a network path

You can delete one network path at a time or several at once.

You can delete one network path at a time or several at once.

To delete a network path:

  1. Navigate to Delivery > Network Paths.
  2. For the network path you want to delete, select > Delete.
    • The network path is deleted.
    • Note: If the Delete option is disabled, it’s because the path is being used by a web path in Experience monitoring and cannot be deleted directly. Instead, remove the monitoring point from the web app group definition or delete the web app group.

To delete one or more network paths:

  1. Navigate to Delivery > Network Paths.
  2. Select the network paths you want to delete.
  3. From the Action drop-down, select Delete.
  4. Confirm the network paths to be deleted.
    • Note: If the checkbox for a path is disabled, it’s because the path is being used by a web path in Experience monitoring and cannot be deleted directly. Instead, remove the monitoring point from the web app group definition or delete the web app group.
  5. Click Delete.

Customize the UDP port range

Specifying the port range used for dual-ended paths allows you to monitor engineered traffic patterns. Using a custom, narrow port range, enables network administrators to classify UDP probes between the source and target using extended ACLs so that the probes can be influenced by policy-based QoS, policy-based routing, and port-based traffic filtering.

Note: This capability is available only on m22, m30, r40, and r400 monitoring points.

To customize the UDP port range:

  1. Log in to Web Admin.
  2. Navigate to Appliance Configuration > Sequencer Configuration.
  3. Uncomment the line “# UDP Port Range: 45056,49151”.
  4. Change the port range.
  5. Click Save.
  6. Click OK to restart the sequencer process.
    • The updated UDP port range is active.

Configure a dual-ended path to use a non-default return path for diagnostics

When a dual-ended path is defined using the default interfaces on both the source and the target monitoring points, the target monitoring point knows how to create a return path to the source based on information provided by APM. If you need to use interfaces on the source or target other than the defaults, a separate configuration is required as this information is not available to APM.

Configuring a non-default return path also requires that both the source and target monitoring points need to be Enterprise Monitoring Points that you control. They cannot be AppNeta WAN Targets.

To specify a non-default return path for diagnostics, you need to use the APM API.

  1. Log in to APM.
  2. Confirm you are using the correct organization.
    • The organization name appears under your name on the top right. If you need to change it:
      1. Click your name.
      2. Click Change Organization.
      3. Select your organization in the dropdown.
      4. Click Change.
  3. Navigate to > API.
  4. Get the organization ID.
    1. Navigate to organization > GET /v3/organization.
    2. Click Try it out!
    3. In the Response Body section, find your organization name in a displayName field.
    4. The organization ID is in the associated id field. Record it.
  5. Get the path ID.
    1. Navigate to path > GET /v3/path.
    2. In the orgId field of the Parameters section, enter the organization ID.
    3. In the sourceAppliance field, of the Parameters section, enter the source monitoring point name.
    4. Click Try it out!
    5. In the Response Body section, find the path you are using in a pathName field.
    6. The path ID is in the associated id field. Record it.
  6. Get the target appliance ID.
    1. Navigate to appliance > GET /v3/appliance.
    2. In the orgId field of the Parameters section, enter the organization ID.
    3. Click Try it out!
    4. In the Response Body section, find the target monitoring point name in a name field.
    5. The appliance ID is in the associated id field. Record it.
  7. Get the target appliance interface to use for the return path.
    1. Navigate to appliance > GET /v3/appliance/{id}.
    2. In the id field of the Parameters section, enter the target appliance ID.
    3. Click Try it out!
    4. In the Response Body section, find the interface to use for the return path in the localNetworkInterfaces field. Record it. Make sure to record the full string inside the double quotes.
  8. Get the IP address or hostname of the source monitoring point to use as the target of the return path.
    • If the source and target devices are separated by a public network, use the public IP address or hostname of the interface on the source monitoring point you want the return path targeted to. Otherwise, use the private IP address or hostname of that interface.
  9. Set up the return path using the information gathered.
    1. If you are creating the reverse path for the first time:
      • Navigate to path > POST /v3/path/{id}/diagnosticSettings.
    2. If you are updating an existing configuration:
      • Navigate to path > PUT /v3/path/{id}/diagnosticSettings.
    3. Within the Parameters section, do the following:
      1. In the Id field, enter the path ID recorded above.
      2. In the Parameters section, click the box under Model Schema on the right.
        • The text is copied to the body field.
      3. Edit the text in the body field as follows:
        1. Set pathId to the path ID recorded above.
        2. Set the targetApplianceID to the target appliance ID recorded above.
        3. Set the returnPathApplianceInterface to the target appliance interface recorded above.
        4. Set the returnPathTargetAddress to the source monitoring point IP address or hostname recorded above.
    4. Click Try it out!
    5. Confirm that the configuration change was made successfully.
      • The Response Body section should contain the values you entered.
      • The Response Code should be 200.