This table lists the bugs resolved in the Cisco WAE 7.6.4 release.

This table lists the supported devices and software versions for Cisco WAE 7.6.4.

Cisco WAE 7.6.4 is validated on RHEL 9.4.

In Cisco WAE 7.6.4, the support for Call Home transport setting is deprecated. It supports only SmartTransport URL. The URL is in the format: http://<SSM-ONPREM-IP>/SmartTransport.

The Tomcat version used in the Cisco WAE Live application has been upgraded to 9.0.93.

Cisco WAE 7.6.4 does not support Multi WAE collection.

To install a DNF cluster on Cisco WAE 7.6.4, you must install the Ansible that is compatible with Python 3.7.6.

sudo pip3.7 install ansible

For more information on DNF configuration, see the NetFlow Data Collection chapter in the Cisco WAE 7.6.x User Guide.

Cisco WAE 7.6.4 supports the installation of Python 3.7.6 and Supervisor 4.2.5 on RHEL 9.4.

If you are using Smart Licensing and Cisco WAE is restarted or packages are reloaded, then after the restart, you must restart all the agents to avoid license errors.

In Cisco WAE 7.6.4, NSO has been upgraded to version 5.7.17.1.

Cisco WAE Design has discontinued support for Windows and MacOS platforms since the 7.6.0 release. For more information, see End-of-Life and End-of-Support for the Cisco WAE Design Windows and MacOS Platforms.

Make a note of these points if your network has multiple OSPF instances configured with different OSPF router IDs for each instances:

• Network access should have an entry for all router-id IP addresses with management IP of that router.

• Under waeinstall/etc/, ensure that the routerldMapping.txt file is present, with all OSPF router IDs in a router mapped to a single IP which will be shown in the Nodes table.

  Example:

  [wae-user@wae-xtc-rhel etc]$ more routerldMapping.txt
  <OspfRouterldToManagement>
  OSPFRouterld     IPAddress
  1.1.105.1        1.1.5.1
  1.1.115.1        1.1.5.1
  1.1.106.1        1.1.6.1
  1.1.116.1        1.1.6.1
  1.1.107.1        1.1.7.1
  1.1.117.1        1.1.7.1
  1.1.108.1        1.1.8.1
  1.1.118.1        1.1.8.1

  Note	IP addresses are Tab separated in the routerldMapping.txt file.

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.

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.

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
   

Cisco WAE does not support netflow workflow, layout-nimo, and RT apps under HA.

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.

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.

The configured constraints are not modelled during notification. Run collection must be used to collect/delete the configured constraints.

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.

These collections have not been 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

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.