First Published: June 1, 2020

Introduction

This document describes the updates and installation steps for Cisco WAN Automation Engine (WAE) Design Release 7.2.1.1.


Note

The Cisco WAE Design Release 7.2.1.1 must only be used as a standalone release and must not be used with any Cisco WAE Server or Cisco WAE Live releases.

What's New in Cisco WAE Design 7.2.1.1

Partitioned simulation analysis is enhanced for better performance.

Install Cisco WAE Design 7.2.1.1

This procedure outlines the steps necessary to upgrade to Cisco WAE Design 7.2.1.1:

Procedure

Step 1

Download the digitally signed Cisco WAE Planning software package from the Cisco download site.

Step 2

Verify and extract the digitally signed binary to a location of your choice. See the "WAE Design GUI Installation" chapter in Cisco WAE Design 7.2.1 GUI Installation Guide.

Note 

For both Linux and Mac, the certificates and digital signatures are embedded in the downloaded files - WAE-Design-k9-7.2.1.1-Linux-x86_64.signed.bin and WAE-Design-k9-7.2.1.1-MacOSX-x86_64.signed.bin respectively.

Step 3

To start WAE Design, do one of the following:

  1. On Windows or Linux, double-click the wae_design executable.

  2. On Mac, open the Terminal, enter: 

    cd <directory-where-you-unpacked-the-distribution>
open ./WAE_Design.app

  3. From the CLI, enter:

    ./wae_design

    (Optional) On Windows, you can associate the plan file using the .pln format with the wae_design executable. Double-clicking a .pln file opens the plan in a new instance of the GUI.

Documentation

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


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

Filing a Cisco WAE Bug

While filing CDETS for Cisco WAE, make sure the following information is captured:

  • WAE configuration: supervisord configuration, aggregator configuration and the nimo configuration of concerned network and its source-network, if any.

  • <run-dir>/logs/ directory

  • Plan file(s) for the network(s) of concern

  • <run-dir>/data/stats/ for system stability and resource usage related issues

  • <run-dir>/work/dare/ for aggregation related issues.

  • <run-dir>/data/networks/*.db for issues related to networks configured as ‘native’ and the corresponding aggregator (final-network).

  • CDB dump of the networks of concern for networks of ‘yang’ format.

  • Configuration corresponding to the component of concern. Eg: WMD, archive etc.

  • For collection issues, record file(s) if the nimo supports record-playback.

  • ~/.cariden/logs/ for designapid related issues.

  • Log files from Cisco WAE Diagnotics Tool. For more information, see Cisco WAE User Guide.

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.