Some newer Linux distributions use a new way (using biosdevname) of naming hardware devices, including network interfaces. This causes some software that depends on the traditional naming (for example, eth0 , eth1) to fail on license checks.

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).

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
   

• 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.

• For 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.

• 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 WAE does not support netflow workflow, layout-nimo, and RT apps under HA.

• Multilayer collection for Cisco devices is supported only on the following platforms:

  • Cisco Network Convergence System (NCS) 2000 platforms running versions 11.0, and 11.1 are supported when using the Cisco Evolved Programmable Network Manager optical agent (EPN-M 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 EPN-M 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, the following warning might be seen:

warning: unknown property: `Ice.Default.Timeout'

This warning does not have any impact on the functionality and can be ignored.

The following collections have not beeen verified:

• Multiple OSPF instances collection from ALU router

• Multiple ISIS instances collection from ALU router

• ISIS process ID collection from ALU router

In WAE Live, when creating a new network (with a default network already present), the following 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.