Introduction
This document provides information regarding Cisco WAN Automation Engine (Cisco WAE) Release 7.2.1.
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 Cisco WAE platform is an open, programmable framework that interconnects software modules, communicates with the network, and provides APIs to interface with external applications.
This document contains the following topics:
What’s New in Cisco WAE 7.2.1
The following features are new in Cisco WAE 7.2.1
Feature | Description | ||
---|---|---|---|
Smart Licensing |
Cisco WAE now supports both Cisco Smart Licensing and traditional licensing. Cisco Smart Licensing is a standardized licensing platform that enables you to automate time consuming manual licensing tasks, track the status of your license and software usage trends. Some of the benefits that Cisco Smart Licensing offers are:
WAE UI → Smart Licensing is added to enable you to configure and manage all details related to smart licenses. For more information, see "Cisco Smart Licensing" chapter in the Cisco WAE 7.2.1 User Guide. |
||
HA with automatic failover |
Cisco WAE now supports High Availability (HA) with automatic failover. If a primary node fails, the secondary node takes over as Master node. WAE UI → HA configuration page is updated to enable you to configure master and slave nodes. For more information, see "Administration" chapter ("Configure High Availability" topic) in the Cisco WAE 7.2.1 User Guide. |
||
Online Help |
Cisco WAE now comes with embedded online help. Use the Help button on WAE UI to access the related help topics.
|
||
Changeover tool enhancements |
The Changeover tool is enhanced to allow you to group Interface Metric changes together into steps. You can:
For more information, see "Changeover" chapter ("Running the Changeover Tool" topic) in the Cisco WAE Design 7.2.1 User Guide. |
||
Enhancement to SR policy modelling to support multiple candidate path |
SR policy is enhanced to support multiple candidate path along with preference. If an SR LSP contains multiple SR Candidate paths, the demand is routed on the LSP path with the highest preference option for which the demand can be routed from source to destination. For more information, see "Segment Routing Simulation" chapter ("SR LSP Routing" topic) in the Cisco WAE Design 7.2.1 User Guide. |
||
RSVP-TE Optimization Tool enhancemets |
In Cisco WAE Design, the RSVP-TE Optimization Tool is enhanced to allow you to set avoidance constraints. Navigate to Tools → RSVP LSP Optimization → RSVP-TE Opt. Avoid Objects section in the Advanced tab lets you to select Nodes, Interfaces, L1 Links, L1 Nodes, SRLGs to be avoided when optimizing LSPs. For more information, see "RSVP-TE Optimization" chapter ("Optimization Input" topic) in the Cisco WAE Design 7.2.1 User Guide. |
||
WAE Live Database management |
Cisco WAE Live database management now provides you with the following options:
The dependency on Oracle Java is also removed. For more information, see "Performing Administrative Tasks" chapter ("Database Management" topic) in the Cisco WAE Live 7.2.1 User Guide. |
||
Inventory data collection timestamp |
On WAE Live → Inventory page, the Table view is updated to include Last Collected field at the bottom of the page which displays the date and time of last collected data. For more information, see "Viewing Inventory" chapter ("Viewing the Inventory Table" topic) in the Cisco WAE Live 7.2.1 User Guide. |
||
Digital Signing |
Cisco WAE software (including WAE Design and WAE Live) now come with digital signatures. The verifiable digital signatures ensure that the Cisco WAE software running on your systems is secure and has not been tampered with, and that the software originated from a trusted source. For more information, see Cisco WAE 7.2.1 Installation Guide and Cisco WAE Design 7.2.1 GUI Installation Guide. |
||
Enhancement to SR policy modelling to support multiple SID type |
Cisco WAE is now updated to support additional SID types - Interfaces, Nodes, Node Groups, LSPs. |
||
Cisco WAE scaling |
WAE is now enhanced to support 3000 nodes for modeling, simulation and optimization. |
||
EPNM 3.0 support for optical collection |
WAE now supports EPNM 3.0 with NCS2K (11.0/11.1). |
||
WAE performance improvements |
NIMOs are now enhanced to support native format. |
||
Inter AS BGP enhancement |
AS-merge is enhanced to handle dropped demands. |
||
WMD - Increase in robustness |
Performance of WMD interacting with SAGE is improved. |
Upgrade to Cisco WAE 7.2.1
Follow the below workflow to install or upgrade to Cisco WAE 7.2.1:
Install and Configure Supervisor
Install and configure supervisor before installing WAE.
Note |
The following configuration steps work only when supervisor is installed using yum. If supervisor is installed using any other method, it has to be configured to run supervisorctl as a non root user. |
Procedure
Step 1 |
Install supervisor and verify.
|
||
Step 2 |
Create directories with write permissions for the OS user running WAE.
|
||
Step 3 |
Update supervisor configuration to not run as a root user. Point the pid file to /opt/supervisor/run/supervisor.pid and user as the OS user running WAE. Open /etc/supervisord.conf as root and edit.
|
||
Step 4 |
Start Supervisor.
|
||
Step 5 |
Enable supervisor to start during system startup.
|
Verify WAE Image
Procedure
Step 1 |
Download the Cisco WAE 7.2.1 software package from Cisco Download Software site. |
Step 2 |
The certificate and digital signature are both embedded in the downloaded file - |
Step 3 |
Run the self-extracting signed binary. This extracts the Release Binary and validates using the signature file. Verification of signed image
|
Step 4 |
The generated |
Install Cisco WAE
Before you begin
-
If one does not yet exist, create a UNIX user (assigned to a group). You must be this UNIX user to run installation.
-
Make sure supervisor is installed and configured. See Install and Configure Supervisor.
-
Download and verify the digitally signed Cisco WAE 7.2.1 image. See Verify WAE Image.
-
Make sure Java-8 is installed on the system and
JAVA_HOME
environment variable is pointing to jdk-1.8. -
Make sure that
requests.auth
python package is installed for the BW-OPT application to function in WAE. -
For migrating the existing 7.1.x configurations to 7.2.1 please go through the README file provided with “Cisco WAE upgrade script for migrating configurations from WAE 7.1.x to WAE 7.2.1” package from CCO.
Procedure
Step 1 |
Stop WAE if running. |
||
Step 2 |
Change permission of the install file using the command:
|
||
Step 3 |
Run the installer specifying the target directory.
|
||
Step 4 |
Setup environment and create a runtime directory specifying the path.
|
||
Step 5 |
You are prompted to set the Cisco WAE admin password.
|
||
Step 6 |
After installing and setting up wae (i.e. after running wae-setup), create a soft link to the
|
||
Step 7 |
Update supervisor configuration.
|
||
Step 8 |
Start WAE process
|
||
Step 9 |
Check status of WAE process
|
Supported Node Versions
The following table lists the supported node versions for Cisco WAE 7.2.1
Feature |
Product |
Tested with version |
Notes |
---|---|---|---|
SRTM |
IOS-XR |
6.6.2 + SMU, 6.5.3 + SMU |
|
Netconf LSP |
IOS-XR |
6.5.1 |
NED Version: ncs-4.7.4-cisco-iosxr-7.11.1 |
IOS-XR |
15.3 |
NED Version: ncs-4.7.4-cisco-ios-6.22.1 |
|
Juniper Junos Mx960 |
18.1R1.9 |
NED Version: ncs-4.7.1-juniper-junos-4.1 |
|
RT Apps, Multi XTC, Reactive polling. |
IOS-XR |
6.6.2 + SMU, 6.5.3 + SMU |
|
Multilayer |
NCS2K |
10.9, 11.0 |
|
EPNM |
3.0.3 |
Documentation
To find descriptions of all related Cisco WAE documentation, see 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.2.1:
Bug ID |
Description |
---|---|
CSCvn17584 |
Running |
CSCvp60520 |
Unable to keep active connection with XTC. |
CSCvp62803 |
WMD does not get traffic from |
CSCvq34672 |
|
CSCvq36413 |
|
CSCvq54725 |
Interfaces with Util Sim higher than 100% due to demands coming from netflow. |
CSCvq59755 |
|
CSCvq70190 |
|
CSCvq74682 |
WAE High Availability does not work as expected. |
CSCvq79488 |
Java Exception in |
CSCvq86258 |
WAE XTC agent keeps multiple connections with XTC and is not consuming the information sent by XTC, increasing XTC memory usage. |
CSCvq87842 |
|
CSCvr09357 |
|
CSCvr12252 |
The final network model does not have the layout coming from |
CSCvr85317 |
The DARE aggregation fails after few hours. |
CSCvr86225 |
|
CSCvm34065 |
DARE does not process changes, displays 'Queue full' error message. |
CSCvm57253 |
Packages reload when simultaneous collections are scheduled. |
CSCvn49160 |
Following error is seen while loading plan file with L1 and L3 information: wae@wae# wae components load-plan run plan-file /home/wae/bonn-agg_v30.pln network-name bonn-archive Error: Python cb_action error. external error (19): Error on line 588: unknown element: dispaly-name |
CSCvo78480 |
DARE rebuild creates another DARE network when one network gets sourced to multiple DARE network. |
CSCvq01121 |
The traffic balance of external endpoint member is rounded off when a plan file is imported. |
CSCvq26753 |
WAE DARE does not consolidate NIMOs when node-filter configuration is changed |
CSCvq38200 |
|
CSCvq39102 |
|
CSCvq53205 |
|
CSCvq54298 |
WAE is unable to discover Huawei CX600 boxes and hardware inventory |
CSCvq56906 |
Intermittent Failures while writing plan files to Archives. |
CSCvr51385 |
Maximum opened files option in netflow agent or flow collector tools is always set to 4096 when WAE is started using |
CSCvr84760 |
Kafka issue impacting multiple components. |
CSCvp44310 |
WAE Design application is slow to recompute simulated traffic numbers when the Multicast tables are included. |
CSCvq57634 |
On WAE Design, Save to -> Template option must be enhanced to allow the operator to update |
CSCvq84759 |
Introduce |
CSCvr24303 |
On WAE Design, introduce Save option to WAE server to improve performance. |
CSCvr38394 |
When trying to execute |
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.
Procedure
Step 1 |
Go to the http://tools.cisco.com/bugsearch. |
||
Step 2 |
Enter your registered Cisco.com username and password, and click Log In. The Bug Search page opens.
|
||
Step 3 |
Use any of these options to search for bugs, and then press Enter (Return) to initiate the search:
|
||
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
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:
-
Update the topo-igp-nimo exclusion or inclusion list.
-
Run collection on the topo-igp-nimo.
-
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
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.
-
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.
High Availability
Cisco WAE does not support netflow workflow and layout-nimo under HA.
WAE Multilayer Collection
-
The optical plug-in is supported on Oracle JRE 1.8 but not on OpenJDK JRE. Oracle JRE 1.8 is not packaged with Cisco 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:
#!/bin/bash
export JAVA_HOME=<path_to_JRE_installation_directory>
export PATH=$JAVA_HOME/bin:$PATH
-
Multilayer collection for Cisco devices is supported only on the following platforms:
-
Cisco Network Convergence System (NCS) 2000 platforms running version 10.61, 10.7, and 10.8 for L1 devices when using the CTC optical agent. NCS 2000 platforms running version 10.9 is 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. It is not supported when using the CTC 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.
Filing a Cisco WAE Bug
While filing CDETS for Cisco WAE, make sure the following information is captured:
-
WAE configuration: supervisord configuration, aggregator configuration and the nimo configuration of concerned network and its source-network, if any.
-
<run-dir>/logs/ directory
-
Plan file(s) for the network(s) of concern
-
<run-dir>/data/stats/
for system stability and resource usage related issues -
<run-dir>/work/dare/
for aggregation related issues. -
<run-dir>/data/networks/*.db
for issues related to networks configured as ‘native’ and the corresponding aggregator (final-network). -
CDB dump of the networks of concern for networks of ‘yang’ format (‘yang’ is the default storage-format).
-
Configuration corresponding to the component of concern. Eg: WMD, archive etc.
-
For collection issues, record file(s) if the nimo supports record-playback.
-
~/.cariden/logs/
for designapid related issues.
Accessibility Features
For a list of accessibility features in Cisco WAE, visit https://www.cisco.com/c/en/us/about/accessibility/voluntary-product-accessibility-templates.html (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.