Cisco WAE 7.1.1.1 Release Notes
Available Languages
Table of Contents
Cisco WAN Automation Engine Release Notes, Release 7.1.1.1
What’s New in Cisco WAE 7.1.1.1
Ability to Archive Data from the Cisco WAE Modeling Daemon (WMD)
Using the Cisco Bug Search Tool
License Check Failures on Newer Linux Distributions
WAE Optical Plug-In / Multi-Layer Collection
Cisco WAN Automation Engine Release Notes, Release 7.1.1.1
This document describes the features, limitations, and bugs for Cisco WAN Automation Engine (Cisco WAE) Release 7.1.1.1
Note
This document describes features and changes since Cisco WAE 7.1.1. For information on WAE 7.1, see the Cisco WAE 7.1 Release Notes.
Introduction
Cisco WAN Automation Engine (WAE) provides the tools to create and maintain a model of the current network through the continual monitoring and analysis of the network and the traffic demands that are placed on it. This network model contains all relevant information about a network at a given time, including topology, configuration, and traffic information. You can use this information as a basis for analyzing the impact on the network due to changes in traffic demands, paths, node and link failures, network optimizations, or other changes.
The WAE platform is an open, programmable framework that interconnects software modules, communicates with the network, and provides APIs to interface with external applications.
Note To find related WAE documentation, see the Cisco WAE 7.1 Documentation Roadmap.
What’s New in Cisco WAE 7.1.1.1
Ability to Archive Data from the Cisco WAE Modeling Daemon (WMD)
You now have the option to archive a plan file using data from either WMD or the configuration database (CDB). Prior to WAE 7.1.1.1, you were only able to get data from the CDB. To configure archive, do the following:
1. Navigate to /wae:networks/network/<network_model_name>.
2. Click the plan-archive tab.
3. Enter the archive directory.
4. From the source drop-down list, select cdb or wmd.
6. To save the current network model to a plan file into the archive directory you specified, click run.
b. Enter timestamp and plan format.
Note Hover over fields to view more information.
To save the current network model to a plan file:
(config)# networks network NetworkABC plan-archive get plan-format pln timestamp 20180920_1445
Upgrade from Cisco WAE 7.1.x
Complete the following steps when upgrading from Cisco WAE 7.1.x to this release.
The examples in this procedure use the following variables:
- ~ is the HOME directory
- INSTALL=~/install
- RUN=~/run
- $INSTALL is the Cisco WAE installation directory
- $RUN is the Cisco WAE run directory
Note The following procedure assumes you are familiar with Network Services Orchestrator (NSO) and its related network element drivers (NEDs) and services.
Step 1 Confirm that ncs is not running.
Step 2 Back up your existing Cisco WAE 7.1.x run and install directories. For example:
Step 3 Remove and clean up the previous installation. For example:
Step 4 Install the Cisco WAE package. For example:
Step 5 The installation program creates a bash script file named waerc that sets the environment variables. Source this file to get the settings. For example:
Step 6 Run wae-setup, and untar the NEDs. For example:
Step 7 Reinstall the run directory you backed up in Step 2. For example:
Documentation
To find descriptions of all related Cisco WAE documentation, see the Cisco WAE 7.1 Documentation Roadmap.
Note We sometimes update the documentation after original publication. Therefore, you should always review the documentation on Cisco.com for any updates.
Bugs
Resolved Bugs
The following are descriptions of the resolved bugs in Cisco WAE Release 7.1.1.1.
Topo-igp-nimo affinity information is not saved in the WAE database. |
|
The snmp_find_interfaces tool incorrectly assigns ports to LAGs. |
|
The WAE SR Bandwidth Optimization tool does not optimize the LSP to the shortest path with available bandwidth. |
|
The topo-bgpls-xtc-nimo collection does not collect eBGP links. |
|
The apply_patch tool displays incorrect information for actual path hops. |
|
The as-merger NIMO does not merge multiple links between a pair of AS routers. |
|
The |
|
A "BulkIpAddress" error appears during topo-bgpls-xtc-nimo collection. |
|
A "get_inventory failed with exit status None" error appears when using the run_inventory tool with the |
|
The lsp-config-nimo collection shows unresolved hops in segment lists for LSPs. |
|
A scheduled task that has ENUM as the RPC parameter does not work. |
|
WAE Design crashes when performing explicit LSP optimization in a MAC OS. |
|
The latest Cisco IOS-XR 6.5.1.xx images have an updated "show isis database verbose" output. As a result, the login_find_igp and topo_igp_nimo tools fail to discover the network topology from the seed router. |
|
The WAE Model Manager UI should not be used to configure or view network models. Instead, use the WAE Expert Mode UI or the WAE CLI. For more information on how to use the WAE Expert Mode or WAE CLI, see the Cisco WAE User Guide. |
|
LSPs and paths are missing from the network model coming from WMD. The WMD log contains many patch errors. |
|
Static L3-L1 mapping does not work when using optical UNI links behind muxponder (N:1 association). |
|
PCE computed LSPs are not detected for multiprocess OSPF networks. |
|
The network option that determines the protocol (OSPF, ISIS, etc.) is not set. Since OSPF is the default option, it is always used regardless if the network is using ISIS. |
|
The changes in the aggregated model are not getting picked up by DARE because the topo-vpn-nimo does not advertise capabilities. |
|
The OPM te-path tool uses setupBW=0 post optimization of an RSVP-TE LSP. However, it should use the original setupBW for the modified LSP. |
|
Cisco Network Convergence System 5500 series node transceiver data is missing in the inventory. |
|
The |
|
The external-executable-nimo returns a status "1" when running the snmp_find_nodes task. |
|
When the create_representative_plan option is enabled on an archive with demands, the -archive option does not work. |
|
Network discovery fails when one or more nodes do not have the ip-manage field populated. |
|
Only pseudonodes (PSN) remain in their own PSN site on Design Archive, although ASN and PSN were defined in named Site on Template. |
|
In WAE Design, replace Number of Circuits to Number of L3 Circuits. |
|
In WAE Design, when a L1 circuit is attached to a L3 circuit through L3 ports, the filter in the GUI fails to pick up the association. |
|
There are inconsistencies between traffic simulation and traffic measurements in the plan file. |
Using the Cisco Bug Search Tool
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 click Log In.
Note If you do not have a Cisco.com username and password, you can register here.
Step 3 Use any of these options to search for bugs, and then press Enter (Return) to initiate the search:
- To search for a specific bug, enter the bug ID in the Search For field.
- To search for bugs based on specific criteria, enter search criteria, such as a problem description, a feature, or a product name, in the Search For field.
- To search for bugs based on products, enter or select a product from the Product list. For example, if you enter “WAE,” you get several options from which to choose.
- To search for bugs based on releases, in the Releases list select whether to search for bugs affecting a specific release, bugs that were fixed in a specific release, or both. Then enter one or more release numbers in the Releases field.
Step 4 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.
To export the results to a spreadsheet, click Export Results to Excel.
Known Limitations
This section describes known limitations and restrictions for Cisco WAE:
- WAE System
- NIMO Consolidation
- WAE Collection
- WAE Optical Plug-In / Multi-Layer Collection
- WAE Design
- FlexLM License Server
- WAE Coordinated Maintenance
Startup
The $CARIDEN_HOME directory is not automatically added to $PATH. (Only $CARIDEN_HOME/bin is.) To start the WAE Design GUI from the command line when it is not under $CARIDEN_HOME/bin, you must specify its full path: /opt/cariden/software/mate/current/mate.
License Check Failures on Newer Linux Distributions
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).
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 rebuild tool to rebuild DARE and sync the updated NIMO node information:
WAE Collection
- 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.
- Due to lack of MIB support, SR tunnel type is not collected for Cisco IOS XR routers through SNMP.
- 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.
– 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.
WAE Optical Plug-In / Multi-Layer Collection
- The optical plug-in (optical-nimo) is supported on Oracle JRE 1.8 but not on OpenJDK JRE. Oracle JRE 1.8 is not packaged with WAE. You can download Oracle JRE 1.8 from Oracle’s website.
If you are using a JRE other than Oracle JRE 1.8 for other Java programs and you want to use the optical plug-in, you must download Oracle JRE 1.8 and add the following lines to the beginning of the <WAE_installation_directory> /packages/optical-ctc-plugin/run.sh file:
– Cisco Network Convergence System (NCS) 2000 platforms running versions 10.61, 10.7,and 10.8 for L1 devices.
– Cisco Aggregation Services Routers (ASR) 9000, Cisco Carrier Routing System (CRS), and Cisco NCS 5500 platforms running IOS-XR for L3 devices.
- Multi-layer collection is limited to the collection of unprotected circuits.
- Collection of non-WSON circuits is not supported.
- 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.
- Lambda mapping is currently supported only for circuit paths but not for path hops.
WAE Design
- macOS Sierra 10.12 and later implements an additional security measure for applications that are not distributed through the App Store; this 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 output for a quarantined application:
As a workaround, remove WAE Design from quarantine by entering the following command in the directory where WAE Design is installed:
You can now run WAE Design from macOS Sierra 10.12 and later.
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.
Accessibility Features
For a list of accessibility features in Cisco WAE, visit Cisco's Voluntary Product Accessibility Template (VPAT) website, or contact accessibility@cisco.com.
All product documents except for images, graphics, and some charts are accessible. If you would like to receive the product documentation in audio format, braille, or large print, contact accessibility@cisco.com.
Feedback