HPE Aruba Networking UXI sensors will now run Path Analysis whenever there is an issue encountered while performing internal or external tests.
You can read more about the types of issues here.
You will now see the Path view and raw output from the path analysis for the complete failed tests issue triage and path view for the threshold violation page.
In the above example, you will see that we have two new things added in issue triage:
Raw output: We have replaced the classic traceroute command's raw output with our path analysis raw output, such that you can now see raw output from our path analysis tool. The RTT that you see beside the node is the average RTT from 3 probes RTT as we send 3 probe packets to each hop.
Note: If you do not have Path Analysis test enabled, then you will see the old classic traceroute in triage.
Path Analysis view: We have added the path view at the bottom of issue triage, where you will see the path taken at the time of the issue, and if the issue is ongoing, then you will see the last confirmed issue path. We have also added "Before", "During", and "After" views to give the user a path before the issue, during the issue, and after the issue. For ongoing issues, the After button will be disabled.
We showcase timestamp(time at which the path has been executed), avg RTT (average round trip time in ms), and average number of hops for the below path.
There is an option to "Explore Paths" to investigate this further in more detail on the global path analysis page.
Using "Filters", you can now change the interface - WiFi & Ethernet, and protocol - ICMP, TCP, UDP (if available).
You can also see paths for threshold violation issues, such as High Latency.
Note:
If you zoom into the timeline under time series charts of latency under threshold violation, then before, during, and after windows will disappear, and you will see the path for the selected time window.
You can't select the specific test result inside the time series chart of latency and see the path for the exact datapoint at this time.
You will sometimes see TCP path in before, during, or after window for ICMP-based thresholds like high packet loss or latency; hence, please use the "filters" to switch it to the correct protocol.
"After" window is disabled for "ongoing" threshold violations and issues.