Release Notes for Cisco WAE, Release 7.6.5
Available Languages
Bias-Free Language
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.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
Cisco WAN Automation Engine (WAE), Release 7.6.5
Cisco WAN Automation Engine (WAE), Release 7.6.5
This document provides information about Cisco WAE 7.6.5, including product overview, bugs fixed in this release, key updates, and known issues and limitations.
There are no new features in this release.
This table lists the resolved issues in this specific software release.
Note: This software release may contain bug fixes first introduced in other releases. To see additional information, click the bug ID to access the Cisco Bug Search Tool.
Table 1. Resolved issues for Cisco WAE, Release 7.6.5
| Bug ID |
Description |
| Vulnerable components cpp curl |
|
| Plan file not populating Delay value for IPv6 interfaces |
|
| Error while integrating support module for interfaces |
|
| XTC agent and NIMO DB files have grown to large sizes |
|
| ML_Demands feature is missing from WAE Live with Smart licenses |
|
| CVE-2025-32433 vulnerability on WAE and NSO |
This section describes the known issues and limitations that should be considered before starting to work with Cisco WAE 7.6.5.
Table 2. Known issues for Cisco WAE, Release 7.6.5
| Issue |
Description |
| WAE collection |
Note these points on WAE collection:
● Inventory collection for Cisco WAE Live is not supported on Cisco 8000 devices.
● LDP data collection can only be performed by executing CLI tools using the external-executable-nimo.
● NetFlow collection is not supported on Alcatel-Lucent devices.
● Due to vendor MIB limitations, WAE cannot represent QoS traffic on interfaces that have more than one VLAN configured. If a network contains such interfaces, their queue traffic statistics are omitted from the collection. The total traffic on these interfaces is still measured. As a result, demands for every class of service estimated through Demand Deduction are less accurate. Estimates of traffic totals over all classes of services, however, are not affected.
● Collection of interface egress shaping rate for Alcatel-Lucent devices does not support LAG interfaces.
● Juniper MIBs do not support P2MP LSPs.
● WAE cannot associate a GRE tunnel with the physical interface it uses to reach the tunnel destination because the IP-Tunnel MIB lacks this information.
● For Juniper routers, the signaled standby LSP option is not available from the standard MPLS-TE MIB. Only the active path option name is collected.
● TE Extended Admin Groups (EAGs), also known as extended affinities, are only supported from Juniper and parse_configs.
● There is no support for building port circuits for LAG members that are not within the same IGP (inter-AS circuits).
● It is not possible to distinguish between physically connected and unconnected LAG ports that are down for LAG port matching.
● With segment routing, concurrent RSVP-TE and SR-TE paths are not supported on the same LSP.
|
| Cisco IOS XR routers |
IGP topology collected through topo-igp-nimo module:
● 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. ◦ MAC accounting is not supported (although you can collect MAC traffic through an external NIMO).
● The lsp-snmp-nimo module does not set the Standby value in the <LSPPaths> table for signaled backup paths or collect named affinities configured with affinity-maps.
|
| BGP peers |
● The topo-bgp-nimo module does not build BGP pseudo-nodes among internal ASNs.
● The topo-bgp-nimo module does not collect BGP peers under PE-CE VRFs.
|
| License check failures on newer Linux distributions |
Some newer Linux distributions use a new way of naming hardware devices, including network interfaces, using biosdevname. This causes issues with software that depends on the traditional naming, such as, eth0, eth1, potentially leading to failures on license checks. The workaround is to append biosdevname=0 to the kernel line of the grub configuration file and then reboot your system. Note that the syntax varies among different distributions. After reboot, you can use the ifconfig command to verify that the NICs are named eth0, eth1, and so on, instead of the biosdevname names, such as p34p1. |
| NIMO consolidation |
The aggregator uses DARE to consolidate NIMOs into one network model. If you update the topo-igp-nimo node-filter configuration, or if a node goes down after running the initial DARE configuration, you must do the following:
1. Update the topo-igp-nimo exclusion or inclusion list.
2. Run collection on the topo-igp-nimo.
3. Run the WAE CLI tool to resync DARE with the updated NIMO node information.
wae@wae# wae components aggregators aggregator <aggregator_network_name> resync aggregator net |
| High Availability |
Cisco WAE does not support NetFlow workflow, layout-nimo, and RT apps under HA. |
| WAE multilayer collection |
Note these points on WAE multilayer collection:
● Multilayer collection for Cisco devices is supported only on the following platforms:
◦ Cisco Network Convergence System (NCS) 2000 platforms running version 11.1.2 are supported when using the Cisco Evolved Programmable Network Manager 7.0 optical agent (EPNM optical agent). ◦ Cisco Aggregation Services Routers (ASR) 9000, Cisco Carrier Routing System (CRS), and Cisco NCS 5500 platforms running IOS-XR for L3 devices.
● Multilayer collection is limited to the collection of unprotected circuits.
● Collection of WSON and SSON circuits are supported.
● Collection of non-WSON circuits is only supported when using the EPNM optical agent.
● L3-L1 mapping by LMP is supported only if the controller interface name is the same as the actual L3 interface name or of the form "dwdmx/x/x/x" where the "x/x/x/x" subscript matches that of the corresponding L3 interface.
● Central Frequency ID mapping is currently supported only for circuit paths but not for path hops.
|
| FlexLM license server |
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. |
| EPNM notification |
The configured constraints are not modelled during notification. Run collection must be used to collect/delete the configured constraints. |
| EPNM multi agent notification |
Cisco WAE does not support simultaneous notification events in case of dual agents. It is recommended to schedule full collection in case of dual agents. |
| Python API |
When using WAE OPM python API and WAE Design API for python, you may receive this error: warning: unknown property: `Ice.Default.Timeout' This warning does not have any impact on the functionality and can be ignored. |
| Multiple OSPF and ISIS instance collection |
These collections are not verified:
● Multiple OSPF instances collection from Alcatel-Lucent routers
● Multiple ISIS instances collection from Alcatel-Lucent routers
● ISIS process ID collection from Alcatel-Lucent routers
|
| WAE Live network creation |
In WAE Live, when creating a new network (with a default network already present), this error is displayed in the catalina.out log file: [ERROR] com.cariden.nextmap.impl.MLMapSnapshotCache: encountered error while updating snapshot cache org.sqlite.SQLiteException: [SQLITE_BUSY] The database file is locked (database is locked) This is a known functionality of SQL and it does not affect the WAE Live functionality. The newly created network updates the database again after sometime with new network configuration. |
This section lists the devices and software versions that have been tested and are known to be compatible with Cisco WAE 7.6.5.
Table 3. Supported devices and software versions
| Cisco IOS XR |
SR-PCE |
Cisco XRv 9000 |
Cisco ASR 9000 |
Cisco NCS 5500 series |
Cisco NCS 540 |
Cisco 8000[1] |
| 25.2.2 |
|
|
|
|
|
|
| 25.1.2 |
|
|
|
|
|
|
| 24.4.2 |
|
|
|
|
|
|
NSO upgrade
In Cisco WAE 7.6.5, NSO has been upgraded to version 5.7.19.1.
RHEL support
Cisco WAE 7.6.5 is validated on RHEL 9.4.
Documentation
To find descriptions of all related Cisco WAE documentation, see Documentation Roadmap.
Cisco Bug Search tool
You can use the Cisco Bug Search Tool to search for bugs.
1. Go to the Cisco Bug Search Tool.
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 register on the registration page.
3. From the Product list, select Routers > Service Provider Infrastructure Software > Cisco WAN Automation Engine (WAE) > Cisco WAN Automation Engine 7.6
4. (Optional) Enter additional criteria (such as bug ID, problem description, a feature, or a product name) in the Search For field.
5. Click Search. 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.
6. To export the results to a spreadsheet, click Export Results to Excel.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2025 Cisco Systems, Inc. All rights reserved.