Oracle Cloud Infrastructure Documentation

Running a Path Analysis Test

A path analysis can be run after it has been saved, or immediately after it has been configured.

Important

An update on February 12, 2024 requires that any on-premises source or destination IP address must also have the This IP address is an on-premises endpoint box selected. If you created a path analysis test with an on-premises IP address before this date that doesn't have the box checked, Edit the test to select the This IP address is an on-premises endpoint box, or the test will fail. See Editing a Path Analysis Test.
    1. To run a previously configured path analysis in the Console, confirm you're viewing the wanted region and compartment.
    2. Open the navigation menu, select Networking, and then select Network Path Analyzer, found in the Network Command Center group.
    3. Click the name of a previously saved analysis, then click Run Analysis.
    4. Allow the analysis to run, which might take up to a minute to complete. Traffic does not need to actually traverse the network. Network Path Analyzer collects and analyzes the network configuration to determine how the paths between the source and the destination function or fail.
    5. After the analysis runs, the screen shows the options configured for the analysis and might produce up to eight possible paths discovered between source and destination.
      Each tab representing a path has a visualization of the forward path and (if configured) the return path for traffic between the source and destination.
      The diagram for a successful test shows green arrows representing each successful hop between nodes in the overall path. The Path Status is Reachable.
      An unsuccessful test shows green arrows representing each successful hop in the overall path, and a red arrow for the hop or network segment that is unreachable.
    6. Click View diagram information to see more detail on each hop. You can determine whether a hop failed because of a misconfiguration in a specific node's routing or security configuration. You can also click a specific arrow to get details about a particular hop.
      Routing info for the hop can be forwarded (when the relevant route table allows the traffic), no route (when the route table does not explicitly allow the traffic or security blocks traffic), or indeterminate (when the route table can't be analyzed). The info provided links directly to the relevant route rule if the node is an OCI resource. Indeterminate states can be caused by your console account not having the required permissions, or because the node routing information is unavailable for any other reason.
      Security info for the hop can be allowed, blocked, or indeterminate. The info provided links directly to the relevant security list or rule if the node is an OCI resource. Indeterminate states can be caused by your console account not having the required permissions, or when the node security information is unavailable for any reason.
    7. (Optional) After you run the test, click Save Analysis to save any changes to the test.
    8. (Optional) After you run the test, click Previous and make changes to the analysis.
    9. (Optional) Click Cancel to exit the workflow without saving the test.

  • Use the get-path-analysis-persisted command and required parameters to run a path analyzer test:

    oci vn-monitoring path-analysis get-path-analysis-persisted --path-analyzer-test-id path_analyzer_test_OCID ... [OPTIONS]

    For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

  • Run the GetPathAnalysis operation to run a path analyzer test.