The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco WAN Automation Engine Release Notes, Release 6.4.13
Using the Cisco Bug Search Tool
License Check Failures on Newer Linux Distributions
WAE Collector and WAE Network Interface (NI)
Cisco Open SDN Controller (OSC)
This document describes any features, limitations, and bugs for Cisco WAN Automation Engine (Cisco WAE) Release 6.4.13.
Cisco WAE is a model-driven, path visibility and path computation engine that simulates, automates, and optimizes multi-vendor, multi-layer networks by leveraging time-series traffic and flow data. For more information on Cisco WAE, visit www.cisco.com/go/wae.
The following is a high-level summary of tasks that should be performed when upgrading from a WAE 6.4.x release.
Note The following tasks assume you are familiar with WAE and WAE Live installations.
1. Disable snapshot processes configured in the WAE user cron job.
2. As a root user, stop all WAE services.
3. Stop the snapshot process and confirm that plan files have been inserted into the WAE Live data store using the
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.
5. As a root user, install WAE 6.4.13. At the prompt “Migrate WAE Collector files from previous installation?”, enter yes.
6. As a WAE user, stop WAE services, upgrade the WAE Live data store, and restart WAE services.
# service wae-web-server start
To verify that the processes are running:
# service wae-web-server status
7. Enable the snapshot processes in the cron job that you previously disabled.
The following table lists the resolved bugs in Cisco WAE 6.4.13.
The existing WAE NI collection.cfg file is replaced with a default configuration file after an upgrade.
After deleting an archive (
The wae-web-server process information is not displayed in the GUI.
The WAE Design metric optimization tool continues to run with a failure scenario even if it is turned off in the GUI.
In WAE Design, when a site is opened, that site panel stays on top of other windows.
In the WAE Live Map, the traffic graph takes a long time to appear.
WAE Live Map does not update to the previous plan file in Internet Explorer.
The WAE software includes an expired certificate (test.crt).
When an L1 circuit is attached to a L3 circuit through L3 ports, the filter in the GUI fails to pick up the association.
PSN remains in its own PSN site on Design Archive even if ASN and PSN are named Site on Template.
In WAE Design, Source/Destination Site Property of Demands is not populated.
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 Cisco Bug Search Tool.
Step 2 Enter your registered Cisco.com username and password, and click Log In.
Note If you do not have a Cisco.com username and password, you can register here.
Step 3 Use any of these options to search for bugs, and then press Enter (Return) to initiate the search:
Step 4 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.
To export the results to a spreadsheet, click Export Results to Excel.
This section describes the limitations and restrictions for this release.
The WAE installer indicates a conflict with rsync31u and ansible1.9. The WAE Planning platsvcs component has a problem with the ansible1.9 dependency. (This problem is tracked as CSCuy79752.)
This problem occurs because the WAE installer requires an older version of Ansible, which is no longer available on EPEL. If you do 'yum install ansible', version 2 is installed and the WAE installation fails. Note also:
As a workaround, do the following:
1. Ensure that Ansible is not installed. (If necessary, uninstall it with yum uninstall ansible.)
2. Install the EPEL repository, if it is not already present.
3. Download and install ansible1.9-1.9.6-2.el6.noarch.rpm and its dependencies.
4. If necessary, install rsync31u-3.1.2-2.ius.centos6.x86_64.rpm.
A wae-dlc folder is created under $CARIDEN_HOME/wae-platsvcs-server when wae-dlc is installed. If the
yum remove wae-dlc command is used, the wae-dlc folder is not deleted. You must manually remove $CARIDEN_HOME/wae-platsvcs-server/wae-dlc.
– One workaround is to perform an offline installation. For instructions, see the “Offline Installation” chapter in the Cisco WAE Server Installation Guide.
– Another workaround is to change https to http.
Note This is not a secure solution. For information on how to resolve OS security issues, contact your OS vendor.
1. In the /etc/yum.repos.d/epel.repo file, change the first instance of https to http.
Change https to http in the following line:
2. Execute yum to clean up makecache.
3. Rerun the installer. For instructions, see the Cisco WAE Server Installation Guide.
The embedded_web_server tool is deprecated. The recommendation is to use the wae-web-server service, which is constantly monitored to be brought up automatically.
By default, this web service starts upon installation completion. Therefore, if you stop the web server using the embedded_web_server tool (embedded_web_server -action stop), the web server does not stop. The workaround is the following:
The WAE Statistics page does not appear in some web browsers if you do not have the correct SSL certificates. To work around this, install the correct SSL certificates (see the “Installing an SSL Web Certificate” section in the Cisco WAE System Administration Guide) or do the following:
1. Click the WAE Statistics link. The URL format is https:// <server_IP> :8443; for example, https://192.0.2.14:8443.
2. Copy the URL of the page to another browser window.
3. In the new browser, change the URL port from 8443 to 8843; for example, https://192.0.2.14:8843.
4. Follow the browser messages to accept the connection and add it as an exception.
Both the System UI and the WAE Design Archive UI have local user management capabilities. If both are used to configure users, WAE uses the most recently updated information. The recommendation is to use only the System UI to manage local users.
Some newer Linux distributions have started using a new way (via biosdevname) of naming hardware devices, including the network interfaces. This causes some software that depends on the traditional naming (for example, eth0, eth1) to fail on license checks, including MATE.
The workaround is to append biosdevname=0 to the kernel line of the grub configuration file and reboot. (Syntax varies among distributions.)
After reboot, you should be able to use ifconfig to verify that the NICs are named eth0 (or eth1,...) instead of the biosdevname names (such as p34p1).
Certain tools (such as parse_configs) might require more memory to start than what is available. The symptom is an error message similar to the following:
The workaround is to set the maximum memory to a low enough value in the CARIDEN_JAVA_OPTIONS variable before calling the tool. An example setting is as follows:
After deleting an archive (
archive_delete), you must do one of the following to remove the deleted plan file from the Time Navigation in the Live Map:
macOS Sierra 10.12 and later implements an additional security measure for applications that are not distributed through the App Store; this includes WAE Design.
By default, WAE Design is in a quarantine state as shown by the following command on a terminal:
The command returns the following output for a quarantined application:
As a workaround, remove WAE Design from quarantine by entering the following command in the directory where WAE Design is installed:
You cannot run the floating license server on a setup (Linux VM or actual host) that uses bonded virtual interfaces (that is, a setup with multiple interfaces that have the same MAC address but different IP addresses within a VM). If the WAE Design client tries to check out a license from a setup that uses bonded virtual interfaces, the license checkout fails with the error “No license found.”
As a workaround, run the floating license server in a standard Linux VM or host.
– Does not support association of a GRE tunnel with the physical interface it uses to reach the tunnel destination since the IP-Tunnel MIB lacks this information.
– Does not update LAG port status if LAGs are discovered running both parse_configs and snmp_find_interfaces. The workaround is to run only snmp_find_interfaces.
– IGP topology collected through parse_igp and login_find_igp_db
– IS-IS link-state database with TE extensions contains incorrect interface “admin-weights” (TE metric) on Intel-based routers.
– IPv6 IS-IS link-state database does not contain IPv6 interface addresses or parallel interfaces. This information is only available when Cisco IOS XR supports IS-IS IPv6 TE extensions. The snmp_find_interfaces tool collects this information.
– snmp_find_rsvp does not set the Standby value in the <LSPPaths> table for signaled backup paths or collect named affinities configured with affinity-maps.
– find_bgp does not build BGP pseudo-nodes among internal ASNs.
– find_bgp does not collect BGP peers under PE-CE VRFs.
– Does not accurately detect the bandwidth of some Juniper ‘ge’ interfaces that have a capacity of 10 Gbps.
– Collects POS bundles, but has limitations due to unavailability of the port OperStatus property.
– SR protected adjacency SIDs are not supported.
– Concurrent RSVP-TE and SR-TE paths are not supported on the same LSP.
During detailed PCEP tunnel creation or when modifying PCEP tunnels, affinity values are misinterpreted if multiple affinities are specified. This limits you to specifying one affinity for IncludeAffinity, IncludeAnyAffinity, and ExcludeAffinity, and each of these values must be a number within [0,31].
– For Cisco IOS XR, there is no option to give the IP address of the LSP directly; you can only specify a loopback address. There is no option to give tunnel affinity values directly; you can only specify an affinity-map name.
– For Junos, there is no inter-domain keyword, which is used only when an inter-area LSP is created.
For a list of accessibility features in Cisco WAE, visit Cisco’s Voluntary Product Accessibility Template (VPAT) website, or contact email@example.com.
All product documents are accessible except for images, graphics and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact firstname.lastname@example.org.
For related documentation, see the Cisco WAE 6.4 Documentation Roadmap.