First Published: February 28, 2019

Introduction

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

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.15

Option to cleanup the cache for Map display

By default, the cache for Map display is cleaned up every 3 days. To clean up the cache more frequently, you can configure as follows:

  1. Stop the WAE web server.

  2. Log in to your local server and open config.xml file for editing. The default location is /opt/cariden/etc/config/config.xml.

    Your location might differ if you chose a different installation directory.

  3. In the config.xml file, locate the following section: 

    <application name="Map">

  4. Under <application name="Map">, do one of the following, depending on whether you are upgrading or performing a fresh installation:

    • If you are upgrading from an earlier release to WAE 6.4.15, add the following line:

      <property name="Map.UiCacheTTL" type="String"><value> <unit></property>

    • If you are performing a fresh installation of WAE 6.4.15, edit the existing line:

      <property name="Map.UiCacheTTL " type="String"><value> <unit></property>

      where

      <value> is a float (a floating-point number, or a number that has a decimal place).

      <unit> is either hour, or day. The unit can be singular or plural and is not case-sensitive. For example, “hour” can be expressed in all of the following ways: hour, Hour, Hours, HOURS.

      For example, to purge time-series data that is older than 1 hour, enter:

      <property name="Map.UiCacheTTL" type="String">1 hour</property>

  5. Save your changes and close the config.xml file.

  6. Restart the WAE web server.

Capacity Planning Optimization for Cisco WAE Design

The Capacity Planning Optimization tool controls how L1 Circuits and their corresponding paths are created. However, it automatically mimics the L1 Circuit characteristics of existing parallel L1 Circuits when upgrading capacity.

Currently, users can select to either not create L1 Circuits or to create L1 Circuits with no secondary paths or to create L1 Circuits with non-Standby secondary paths.

The CLI options for Capacity Planning Optimization tool is enhanced with the following options:

  • -match-existing-l1-circuits: This is a new option that is added. If set to T, when existing L3 adjacencies are upgraded (by adding parallel Port Circuits or L3 Circuits), corresponding L1 Circuits are created based on associated L1 Circuits of parallel Port Circuits or L3 Circuits. This includes replicating primary and secondary paths with respect to their Standby property as well as their associated Actual L1 Circuit Path Hops and L1 Circuit Path Hops. Default is F.

  • -create-l1-circuits: This is a modified option. If F (default), do not create L1 circuits for new port circuits. If T, create L1 circuits for new port circuits. If match-existing-l1-circuits is set to T, this option is only considered for new adjacencies.

  • -primary-l1-circuit-paths: This is a modified option. If F (default), create primary L1 circuit paths are dynamically routed. If T, assign L1 circuit path hops to new primary L1 circuit paths to match the explicitly specified routes of existing parallel L1 circuits. Ignored if -create-l1-circuits is F or if match-existing-l1-circuits is set to T.

  • -secondary-l1-circuit-paths: If F (default), do not create secondary non-standby L1 circuit paths. If T, create secondary non-standby L1 circuit paths. Ignored if -create-l1-circuits is F. If match-existing-l1-circuits is set to T, this option is only considered for new adjacencies.

Cisco WAE Design GUI is modified as follows:

Tools > Capacity Planning Optimization > Layer 1 tab has new options - Do not create L1 circuits, Basic L1 Circuit Creation, and Advanced L1 Circuit Creation.

Upgrading to 6.4.15

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.15. 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.15:

Table 1. Resolved Bugs

Bug ID

Description

CSCvm17916

WAE Server does not detect LSPs.

CSCvm62102

In an SNMPv3 node time out, the logs do not say what IP address causes that time out. NetIntSNMP_error is also not updated to report SNMP issues.

CSCvm98818

topo-igp-nimo does not collect AdjSIDs from an ISIS network.

CSCvk62975

In WAE 6.4.9 snmp_find_interfaces incorrectly assigns ports to lags.

CSCvm07474

Minor bug in WAE 6.4.13 installer script.

CSCvm12286

WAE Live UI does not load Map UI page.

CSCvm42186

WAE 6.4.10 Live Map UI does not show world map or correct node positioning.

CSCvm58508

If OS level permissions are changed on DBspace, engine does not start.

CSCvm62365

Plot demands show demnands are routed through an extra hop.

CSCvm74623

login_find_igp_db unable to parse new field 'SubTLV len: 74' in Juniper Junos 17.2R4.

CSCvn00892

login_find_igp_db output sets nodes::AvoidTransit value to \"Strict\".

CSCvn06202

Simulation of Multicast Demands is not consistent between WAE 6.4.13 and 6.4.14.1.

CSCuv86124

WAE Live Map peering panel is not updated after traffic widget change.

CSCvc99860

Mate Live insertion fails during LSP actual path internal processing.

CSCvg57253

Cisco WAE Design GUI Installation Guide has incorrect path information for WAE Design License Server Software page. See Documentation Errata

CSCvm62382

Multicast demands must participate in Demand Deduction but need to be held as fixed demands.

CSCvm74654

MLD data file size must be reduced in WAE Live Server file system.

CSCvn72882

Unable to discover multi-topology ISIS from Alcatel device.

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.

Documentation Errata

The following information will be incorporated in the Cisco WAE Design 6.4.15 GUI Installation Guide document at its next revision.

WAE Design Floating License Server Pre-Installation

Step 8 in the "Pre-Installation" section of WAE Design Floating License Server chapter will be updated with the following information:

To enable borrowed licenses:

  • You must download the License Server Software Release 6.4.15 package. From the Cisco download site, navigate to Routers > Service Provider Infrastructure Software > WAN Automation Engine (WAE) > WAE Automation > WAE Automation Software - 6.4.15.

  • If you have a floating license that was generated prior to May 2015, you must acquire a new floating license.