Before calculating a path, you can configure the following settings:
The following protocols are supported for path calculation in the system.
Protocol |
Description |
---|---|
IPv4 (default option) |
Calculate a path for IPv4. |
TCP |
Calculate a path for TCP. Additional port information needs to be filled in. |
UDP |
Calculate a path for UDP. Additional port information needs to be filled in. |
More |
View more protocols that you can use to calculate a path. |
When the protocol is selected as TCP or UDP, additional port information needs to be filled in.
The following data sources can be selected for path calculation in the system.
Data Source |
Description |
---|---|
Use the latest device data saved in the database. It includes the following two options: ▪Calculate L3 Active Path — calculate the Layer 3 path by using live data. With this option selected, the system calculates the exact path between Cisco IOS devices (including Cisco IOS Routers, Cisco IOS Switch, and Cisco IOS XR) by inquiring the CEF table instead of load-balancing. ▪Use CLI command with arguments — use commands with configured parameters (such as show ip route 1.1.1.1) instead of retrieving the complete route table (show ip route), MPLS VPNv4 Label table, and MPLS LFIB table (except for Cisco IOS XR). |
|
Live Network |
Log in to the device instantly to retrieve live data. It includes the following three options: ▪Use configuration in Current Baseline (enabled by default) — use the configuration files that have been saved in the Current Baseline, rather than retrieving real-time configuration data. ▪Calculate L3 Active Path — calculate the Layer 3 path by using live data. With this option selected, the system calculates the exact path between Cisco IOS devices (including Cisco IOS Routers, Cisco IOS Switch, and Cisco IOS XR) by inquiring the CEF table instead of load-balancing. ▪Use CLI command with arguments — use commands with configured parameters (such as show ip route 1.1.1.1) instead of retrieving the complete route table (show ip route), MPLS VPNv4 Label table, and MPLS LFIB table (except for Cisco IOS XR). |
Use the saved device data that is nearest to the specified historical time point. Search scope: ± 2 hours. |
You can define the ways to handle with ACL or Policy and gateway during a path calculation in the Advanced Settings:
▪Continue calculation even if denied by interface-level policy (such as ACL) — If this option is enabled, the system ignores the ACL or other interface policy checks during a path calculation.
▪Continue calculation even if denied by device-level policy (such as policy) — If this option is enabled, the system ignores the device-level policy checks during a path calculation.
▪Enable Path IP and Gateway Fix-up Rule (enabled by default) — Whether to enable the path gateway fix-up during a path calculation. See Path IP and Gateway Fix-up for details.
There are two types of execution logs for a path calculation:
▪Production (default option) — In this mode, the system prints common execution logs when calculating a path.
▪Debug — In this mode, the system prints the built-in debug messages to help troubleshoot execution issues of a path.
The system cannot recognize and retrieve the first hop information of an end system from a live network. Such as QoS information So, when the source device is an end system with QoS configured, you can specify the values of QoS parameters for the source device before calculating a path.
With the parameters configured, the system checks the ingress and egress QoS information at each hop and calculates the path based on QoS policies. The following figure is a sample QoS path:
Tip: The parameters displayed in the path settings can be predefined on the Domain Management page (Operations > Domain Settings > Path Parameters Settings). See Built-in QoS Parameters for more details.