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.2.5
Cisco WAE Network Interface Server
License Check Failures on Newer Linux Distributions
This document describes the bugs and limitations for Cisco WAN Automation Engine (Cisco WAE) Release 6.2.5.
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 WAE can be found in Open Source Software Used in Cisco WAN Automation Engine.
The following tables list the open and resolved bugs in Cisco WAE Release 6.2.5. The bug ID links you to the Cisco Bug Search tool.
LSPs collected from Huawei NE40E-X16 routers version V600R008C10SPC300 using SNMP are "Unrouted" and the collected IP addresses from hops are not populated in the plan file.
A “404 Page Not Found” error appears when launching WAE Coordinated Maintenance after restarting the web server and logging back in.
To work around this problem, click the Cisco icon and then refresh the page.
PCEP LSPs are not listed in the plan file when the enablePcepLspCollection parameter is set to true in the collection.cfg file.
WAE Design hangs after borrowing a license. This occurs if WAE Design is shut down and a borrowed license is obtained.
Interfaces do not correlate to the correct remote interface.
The WAE inventory collector doesn’t work. The
The WAE Live map freezes because the plan file is cached indefinitely.
When the Map.AuthEnabled parameter is set to false in the config.xml file, you still must enter credentials.
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Step 1 Go to http://tools.cisco.com/bugsearch.
Step 2 At the Log In screen, enter your registered Cisco.com user name and password; then, click Log In. The Bug Search page opens.
Note If you do not have a Cisco.com user name and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 3 To search for a specific bug, enter the bug ID in the Search For field and press Return.
Step 4 To search for bugs in the current release:
a. In the Search For field, enter a problem, feature, or a product name (for example, Cisco WAN Automation Engine) and press Return. (Leave the other fields empty.)
b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth.
To export the results to a spreadsheet, click the Export Results to Excel link.
This section describes the limitations and restrictions for Cisco WAE.
In some Linux installations with Xfce desktop installed, the documentation does not open from the WAE Design GUI Help menu. The workaround is to do one of the following:
This problem occurs when executing snmp_find_rsvp on XE devices running Cisco IOS Release 15.2. This problem is not reproducible using a similar configuration on a local XE node running Cisco IOS Release 15.4. Therefore, the recommendation is to upgrade the XE device to Cisco IOS Release 15.4 or later.
$CARIDEN_ROOT/etc/collector/server/db-persistence/DiscoveryEngineImplementation.dbfile must be removed prior to starting the web server. Since installation automatically starts the web server, the recommendation is to remove this prior to installation.
Continuous PCEP LSP collection does not support SR tunnels. Note that you can collect SR tunnels through PCEP using the Collector server or snapshots.
– 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.
get_inventorydoes not collect Juniper multi-chassis router hardware inventory.
– SR LAN adjacency SIDs and pseudo-node creation are not supported.
– 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, 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. Re-run 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 open in all browsers. The workaround is the following:
1. Click the WAE Statistics link. The URL format is https:// <server_IP> :8443. Example:
2. Copy the URL of this page to another browser window.
3. In the new browser, change the URL port from 8443 to 8843. Example:
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:
The Cisco WAE Design GUI Installation Guide does not identify WAE Design as being part of the WAE Planning software package.
WAE Collector inventory collection configuration is documented accurately, but it is not based on the use of the shipped default hardware inventory configuration files.
The documentation is missing the following. For information, contact your support representative.
For related documentation, see the Cisco WAE 6.2 Documentation Roadmap.