This document describes the bugs resolved in Cisco WAN Automation Engine (Cisco WAE) Release 7.1.2 Patch 1.

Cisco WAN Automation Engine (WAE) provides the tools to create and maintain a model of the current network through the continual monitoring and analysis of the network and the traffic demands that are placed on it. This network model contains all relevant information about a network at a given time, including topology, configuration, and traffic information. You can use this information as a basis for analyzing the impact on the network due to changes in traffic demands, paths, node and link failures, network optimizations, or other changes.

The Cisco WAE platform is an open, programmable framework that interconnects software modules, communicates with the network, and provides APIs to interface with external applications.


To find related Cisco WAE documentation, see the Cisco WAE 7.1.2 Documentation Roadmap .

This document contains the following topics:

Upgrade from Cisco WAE 7.1.2

This procedure outlines the steps necessary to upgrade from Cisco WAE 7.1.2:


Step 1

Install Cisco WAE 7.1.2 Patch 1 using the following command:

# ./wae-v7.1.2-patch1-linux.bin  [-i WAE_INSTALL_DIR] [-r WAE_RUN_DIR] [-b BACKUP_DIR]


WAE_INSTALL_DIR is the WAE install directory path.

WAE_RUN_DIR WAE is the run directory path.

BACKUP_DIR is the backup directory to use when creating the patch (Optional).

Step 2

Confirm that ncs is running:

#ps aux | grep ncs.smp


To find descriptions of all related Cisco WAE documentation, see the Cisco WAE 7.1.2 Documentation Roadmap.


We sometimes update the documentation after original publication. Therefore, you should always review the documentation on for any updates.

Open Source

A list of open source software that is used in WAE can be found in Open Source Software Used in Cisco WAN Automation Engine.


Resolved Bugs

The following are descriptions of the resolved bugs in Cisco WAE Release 7.1.2 Patch 1:

Table 1. Resolved Bugs

Bug ID



Deletion of SR Policy fails to update the WMD model. The patch that is sent by DARE to WMD does not remove the SR policy in WMD.


Illegal Reference exception message is displayed when EPNM agent runs collection with circuits having link constraints.


actual_path hops are not available in DARE Aggregator.


DARE does not process changes and Queue full error message is displayed.


Execution of login_find_igp_db sets the value of field AvoidTransit to Strict.


In some deployments, hash (#) character creates issues on the cfg-parse agent and the configurations are not parsed correctly. The hash (#) character must be ignored in device configurations.


Simulation of Multicast Demands is inconsistent between different versions of Cisco WAE application.


lsp-config-nimo or cfg-parse fucntion is unable to parse configs with space in hostname.


cfg-parse agent incorrectly parses LSP paths on Huawei devices.


WAE Daemon crashes without notice.

Using the Cisco Bug Search Tool

You can use the Cisco Bug Search Tool to search for a specific bug or to search for all bugs in a release.


Step 1

Go to the

Step 2

Enter your registered username and password, and click Log In.

The Bug Search page opens.

If you do not have a username and password, you can
Step 3

Use any of these options to search for bugs, and then press Enter (Return) to initiate the search:

  • To search for a specific bug, enter the bug ID in the Search For field.

  • To search for bugs based on specific criteria, enter search criteria, such as a problem description, a feature, or a product name, in the Search For field.

  • To search for bugs based on products, enter or select a product from the Product list. For example, if you enter “WAE,” you get several options from which to choose.

  • To search for bugs based on releases, in the Releases list select whether to search for bugs affecting a specific release, bugs that were fixed in a specific release, or both. Then enter one or more release numbers in the Releases field.

Step 4

When the search results are displayed, use the filter tools to narrow the results. You can filter the bugs by status, severity, and so on.

To export the results to a spreadsheet, click Export Results to Excel.