<< Click here to display Table of Contents >>

Path Settings

Contents

Before calculating a path, you can configure the following settings:

▪Protocol

▪Data Source

▪Calculation Logic

▪Log Mode

▪Parameters

Protocol

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.
UDP	Calculate a path for UDP.
More	View more protocols that you can use to calculate a path.

Data Source

The following data sources are supported for path calculation in the system.

Data Source	Description
Current Baseline (default option)	Use the latest device data saved in the database directly.
Live Network	Log in to the device instantly to retrieve live data. ▪Use configuration in Current Baseline (default option) — use the configuration files that have been saved in Current Baseline, not 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).
Historical Data	Use the saved device data that is nearest to the specified historical time point. Search scope: ± 2 hours.

Data Source

Description

Current Baseline
(default option)

Use the latest device data saved in the database directly.

Live Network

▪Use configuration in Current Baseline (default option) — use the configuration files that have been saved in Current Baseline, not 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).

Historical Data

Use the saved device data that is nearest to the specified historical time point. Search scope: ± 2 hours.

Calculation Logic

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) — (disabled by default) If 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) — (disabled by default) If 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.

Log Mode

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.

Parameters

The Parameters settings are used to configure values for QoS parameters of the source device during a QoS path calculation. Before calculating a QoS path, you need to manually configure the QoS values when the source device is an end system with QoS configured because the system cannot recognize and retrieve the QoS information of an end system.

The QoS parameters displayed in the Path Settings are built-in QoS parameters that are predefined in the Domain Management page. See Built-in QoS Parameters for details.

The following is a sample QoS path calculated in the system. The system checks the ingress and egress QoS information at each hop and calculates the path based on QoS policies.