First Published: September 30, 2019

Introduction

This document provides information regarding Cisco WAN Automation Engine (Cisco WAE) Release 6.4.16.

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.

This document contains the following topics:

What's New in Cisco WAE 6.4.16

pmacct upgrade

pmacct (a set of network monitoring tools) used by the flow collection server is upgraded from version 1.7.1 to version 1.7.3.

Upgrading to 6.4.16

The following is a high-level summary of tasks that should be performed when upgrading from a WAE 6.4.x release. For more information, see WAE Server Installation Guide.


Note

The following tasks assume you are familiar with WAE and WAE Live installations.

Procedure

Step 1

Disable snapshot processes configured in the WAE user cron job.
Step 2

As a root user, stop all WAE services.

# /etc/init.d/wae-svcs-boot stop
# wae-svcs-boot stop
Step 3

Stop the snapshot process and confirm that plan files have been inserted into the WAE Live data store using the ml_insert_ctl -status command. The output should look like this: 

Last Collection Status: success
Last Collected Filename: The last plan file collected by the snapshot process
Job Queue Status: Healthy
Step 4

Back up the WAE Live data store.

Note 

If WAE is running on a VM, you have the option to take a VM snapshot.
Step 5

As a root user, install WAE 6.4.16. At the prompt “Migrate WAE Collector files from previous installation?”, enter yes. 

# sudo bash <package>.bin
Step 6

As a WAE user, stop WAE services, upgrade the WAE Live data store, and restart WAE services.

# service wae-web-server stop
# mld -action upgrade
# service wae-web-server start

To verify that the processes are running:

# service wae-web-server status
# mld -action status
Step 7

Enable the snapshot processes in the cron job that you previously disabled.

Documentation

To find descriptions of all related Cisco WAE documentation, see the Cisco WAE 6.4 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 6.4.16:

Table 1. Resolved Bugs

Bug ID

Description

CSCvh68600

ML insertions fail with an error code: 255.

CSCvo45650

Multiple node perf data issues reported in topo-igp-nimo.

CSCvq15406

[flow_get] [13689] timeout waiting inside compute() error message displayed.

CSCvq69457

Simulation Analysis tool displays segmentaion fault when -suppress-progress false flag is used.

CSCvq87842

topo-bgp-nimo collection is unable to complete the upload to CDB due to an "Invalid Value" error for peer-id.

CSCvr11538

Unable to login to ALU routers unless using "force-login-platform alu".

CSCvn89056

Peering Panel from the WAE Live Settings does not work.

CSCvo10172

IAS data computation does not commence if any single one of those is down though Master-Agent knows of several receivers.

CSCvo56409

WAE Live 6.4.14 Report aborts when running Traffic Interface Reports with certain interfaces included.

CSCvo67222

Missing AS in node Edit dialog on windows.

CSCvo96947

Interfaces in Collapsed State cannot change.

CSCvp06654

WAE netflow - pmacct Log file runs overtime. A process is needed to rotate/clean up the log file.

CSCvp27926

Export Routes has issues with exporting routes for Circuits in terms of L1 Links if the L1 Circuits are indirectly associated to the Circuit using its Port Circuits.

CSCvp51511

WAE Live 6.4.5 - Not possible to add a new network to Web UI Network Manager or using mld CLI commands.

CSCvp90288

SNMPv3 support to be provided for inventory collection.

CSCvq01121

External Endpoint traffic balance rounded off during import.

CSCvq61955

If LSP tunnels (using signaled-name) start with '#' , they are omitted in WAE Design in LSPs table.

CSCvr26321

[WAE 6.4.15] Simulation Analysis takes a week to complete.

CSCvo83872

In WAE Live > Map > Events Widget, there a discrepancy between Events Widget data and the data presented in the Map.

CSCvq78732

[WAE Live 6.4.11] By default, mate_cfg prioritizes $HOME's config.xml over $CARIDEN_ROOT. But if the user has pre-defined configurations in $CARIDEN_ROOT, $HOME still takes precedence and the configurations will not be used by WAE Live.

CSCvp44310

WAE Design application is slow to recompute.

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.