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.3.10
Using the Cisco Bug Search Tool
WAE Collector and WAE Network Interface (NI)
Cisco Open SDN Controller (OSC)
License Check Failures on Newer Linux Distributions
Use of App Engine APIs to Deploy SR and RSVP Non-PCEP LSPs
First Published: 2017-06-01
Last Updated: 2017-08-03
This document describes the features, limitations, and bugs for Cisco WAN Automation Engine (Cisco WAE) Release 6.3.10.
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 http://www.cisco.com/go/wae.
A list of open source software used in Cisco WAE can be found in Open Source Software Used in Cisco WAN Automation Engine.
The following are descriptions of the resolved bugs in Cisco WAE Release 6.3.10. The bug ID links you to the Cisco Bug Search tool.
In WAE Live, performance varies greatly on ml_insertions after resizing.
The snmp_find_nodes tool returns incorrect memory usage for Cisco IOS-XR devices.
In WAE Live, the download does not start when attempting to download rows as a CSV file.
Layout is not removed from the source plan after the copy_from_template task is performed.
L1 Link maxL1CircuitPaths cannot be set in the L1 link records.
The snmp_find_nodes tool fails to update the “model” field for some Juniper nodes.
The RSVP TE Optimization tool does not use the simulated delay values.
The newVPNNode method in the VPNNodeManager class crashes if the new VPN node to be created is not assigned a VPN.
When you export an ad hoc report that was generated using the “Download CSV” option, the report contains an additional RowID column.
The Metric Optimization tool does not consider whether or not links are inactive when -optimization-type is set to “global.” This behavior affects the optimization results.
When you use the GUI to create a user property for a table, its display name is used for the ColumnData parameter.
The RSVP TE Optimization tool does not consider “Fit” LSPs when selecting tables in the GUI.
When demands are created for private LSPs, the demand and LSP association is incorrect.
After deleting multiple user properties from tables, the table correctly hides those properties. However, if you later select to show all columns in the table, it does not show all the columns.
In WAE Design, loading a plan file hangs and all links are unavailable (grayed out).
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 then click Log In. The Bug Search page opens.
Note If you do not have a Cisco.com username and password, you can register for them.
Step 3 Use any of these options to search for bugs, and then press Enter (Return) to initiate the search:
Step 4 When the search results are displayed, use the filter tools to narrow the results. You can filter the bugs by status, severity, modified date, and so on.
To export the results to a spreadsheet, click Export Results to Excel.
This section describes the limitations and restrictions for Cisco WAE.
macOS Sierra 10.12 implements an additional security measure for applications that are not distributed through the App Store, which 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 for a quarantined application:
As a workaround, remove WAE Design from quarantine by entering:
– 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
snmp_find_interfaces. The workaround is to run only
– IGP topology collected through
– 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.
– MAC Accounting is not supported.
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.
snmp_find_ospf_dbcannot be used when routers have a large number of links that cannot fit into a single PDU.
find_bgplsdoes not support multi-area OSPF or multi-level IS-IS, non-TE-enabled interfaces, and pseudo-nodes. The workaround is to use SNMP- or login-based discovery.
– Does not collect Juniper multi-chassis router hardware inventory.
– Does not collect hardware inventory with IPv6 addresses.
– SR protected adjacency SIDs are not supported.
– Concurrent RSVP-TE and SR-TE paths are not supported on the same LSP.
sam_getplandoes not populate the <NodeTraffic> table. This table is derived and populated when
sam_getplanand SNMP tools are used together.
sam_getplandoes not populate the NetIntActivePath column in the <LSPs> table.
sam_getplanand SNMP tools are used together in the snapshot process for multi-vendor network collection, then Alcatel-Lucent traffic measurements cannot be aligned with those collected from other router platforms.
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.
– One workaround is to perform an offline installation. For instructions, refer to 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.
http in the following line:
2. Execute yum to clean up makecache.
3. Rerun the installer. For detailed installation instructions, see the Cisco WAE Server Installation Guide.
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,
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
eth1,...) instead of the
biosdevname names (such as
Certain tools (such as
parse_configs) may 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:
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 email@example.com.
For related documentation, see the Cisco WAE 6.3 Documentation Roadmap.