First Published: February 7, 2019

Introduction

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

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.


Note
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:


Note

Cisco WAE 7.1.2 Patch 2 is cumulative of the previous patches. You can directly upgrade to Cisco WAE 7.1.2 Patch 2 from Cisco WAE 7.1.2 or Cisco WAE 7.1.2 Patch 1.

Procedure

Step 1

Stop WAE if it is running.
Step 2

Change permission of the install file using the command:

chmod 755 wae-v7.1.2-patch2-linux.bin
Step 3

Install Cisco WAE 7.1.2 Patch 2 using the following command:

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

where

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 4

Confirm that ncs is running:

#ps aux | grep ncs.smp
Step 5

After Cisco WAE 7.1.2 Patch 2 installation is complete, start the NIMOs that were running earlier and not scheduled (For example, traffic-poller NIMO).

Documentation

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


Note
We sometimes update the documentation after original publication. Therefore, you should always review the documentation on Cisco.com 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.

Bugs

Resolved Bugs

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

Table 1. Resolved Bugs

Bug ID

Description

CSCvn30441

WAE unable to run topo-bgpls-xtc-nim run-xtc-collection and throws missing element error.

CSCvn26138

Unable to run Plan Archive in WAE 7.1.2.

CSCvn79094 is a duplicate bug with similar resolution.

CSCvn88920

WAE 7.1.2 fails to create new plan files.

CSCvo01841

The file that is produced under wae-run/data/network/db, first contains traffic stats and after some time is updated with stats data.

CSCvn78097

topo-bgpls-xtc-nimo does not discover interfaces for large network (500 devices).

CSCvn94403

Optical NIMO fails to import circuits with user properties.

Note

  • topo-bgpls-xtc-nimo is enhanced with two more config options - topo-bgpls-xtc-nimo/advanced/nodes/advanced-options, and topo-bgpls-xtc-nimo/advanced/interfaces/advanced-options. Use these to pass arguments to underlying CLI tools snmp_find_nodes and snmp_find_interfaces respectively.

  • The plan file that is passed to load-plan must always have the Network table and a value populated for Title (Network Name).

Cisco WAE Release 7.1.2 Patch 2 also includes bug fixes released as part of Cisco WAE Release 7.1.2 Patch 1.

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

Table 2. Resolved Bugs

Bug ID

Description

CSCvn18171

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.

CSCvn24095

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

CSCvn51907

actual_path hops are not available in DARE Aggregator.

CSCvm34065

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

CSCvn00892

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

CSCvn04684

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.

CSCvn06202

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

CSCvn07232

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

CSCvn26803

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

CSCvn28694

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.

Procedure

Step 1

Go to the http://tools.cisco.com/bugsearch.

Step 2

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

The Bug Search page opens.

Note 
If you do not have a Cisco.com username and password, you can http://tools.cisco.com/RPF/register/register.do.
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.