Cisco WAN Automation Engine Release Notes, Release 6.4
WAE Collector and WAE Network Interface (NI)
License Check Failures on Newer Linux Distributions
This document describes the features, limitations, and bugs for Cisco WAN Automation Engine (Cisco WAE) Release 6.4.
Cisco WAE is a model-driven path visibility and path computation engine that simulates, automates, and optimizes multi-vendor, multi-layer networks by leveraging time-series traffic and flow data. For more information on Cisco WAE, visit http://www.cisco.com/go/wae.
This section contains the following new features:
The following table describes all new features related to WAE Design.
New tool to perform capacity planning optimization on plan files. |
Enables capacity planning to address increased traffic and congestion. To alleviate congestion, the optimizer enables:
The optimizer operates on both Layer 3 and Layer 1 and provides failure set optimization options. For more information, see the “Capacity Planning Optimization” chapter in the WAE Design User Guide. |
Creates/removes LSPs for specified LSP groups and shares Setup BW evenly within each group. For more information, see the “LSP Setup Bandwidth Optimization” chapter in the WAE Design User Guide. |
|
The Segment Routing (SR) TE Bandwidth (BW) Optimization tool enables:
For more information, see the “SR-TE Bandwidth Optimization” chapter in the WAE Design User Guide. |
|
Extended support for LSP disjointness includes:
For more information, see the “LSP Disjoint Path Optimization” chapter in the WAE Design User Guide. |
|
It is possible to specify a subset of interfaces whose utilization should be optimized. The produced reports are enhanced. |
|
Enhancement to optimize inter-AS SR LSPs. See also the Simulation of Inter-AS SR LSPs. |
The SR-TE Optimization tool is extended to create Segment Lists for inter-AS SR LSPs. For more information, see the “SR-TE Optimization” chapter in the WAE Design User Guide. |
Ability to set the number of new L1 circuits that are created when they are being duplicated. |
For more information, see the “Simulation” chapter (“Duplicate L1 Objects”) in the WAE Design User Guide. |
For more information, see the “Layer 1 Simulation” chapter (“Create L1 Nodes”) in the WAE Design User Guide. |
|
Enhancement to find L1 links that are causing lambda blocking. |
For more information, see the “Layer 1 Simulation” chapter (“Lambda Assignments”) in the WAE Design User Guide. |
Addition of a Network Option that controls whether Layer 1 rerouting has converged under failures. |
The Simulation tab includes the new option: “Layer 1 rerouting convergence under failures.” |
Option to fail the L1 object causing the Worst Case L1 Utilization on a selected L1 Link. |
|
The Simulator includes L1 simulation enhancements with respect to parallel L1 Links and routing and Lambda assignment. |
|
Enhancement to easily view association between L1 links and LSPs and demands. |
Selecting a Demand in the network plot automatically highlights the associated L1 Links that are carrying the Demand. Selecting an LSP in the network plot automatically highlights the associated L1 Links that are carrying the LSP. For more information, see the “Layer 1 Simulation” chapter (“Multi-Layer Views”) in the WAE Design User Guide. |
The text displayed for L1 Links is easier to read especially in cases where L1 Links are colored with darker colors. |
|
L1 Links are colored based on their utilization and worst-case utilization. The thresholds and corresponding colors are the same as in L3. |
|
Additional plan attributes for LSP-related objects are now supported. |
The |
New location and improvements to creating, applying, and viewing patches. |
For more information, see the “Patch Files” chapter in the WAE Design User Guide. |
SR LSPs can now be specified as segment list hops in segment lists associated to SR LSPs (Binding SIDs). |
For more information, see the “Segment Routing Simulation” chapter in the WAE Design User Guide. |
It is possible to simulate inter-AS SR LSPs. For more information, see the “Segment Routing Simulation” chapter (“Routing Inter-AS SR LSPs”) in the WAE Design User Guide. |
|
For more information, see the “RSVP TE Simulation” chapter (“Affinities”) in the WAE Design User Guide. |
|
In the WAE Design main window, users can now close tabbed windows by clicking on the “X” in the top right corner of the tab, instead of having to explicitly select the File > Close menu. |
|
Ability to simultaneously plot multiple demands in the same Demand Plot. |
For more information, see the “Traffic Demand Modeling” chapter (“View Demand Plots”) in the WAE Design User Guide. |
Usability enhancement to the SR-TE Optimization tool when setting up constraints. |
Users no longer need to pre-tag nodes that should be avoided and then type in the name of the tag in the Constraints dialog box. For more information, see the “SR-TE Optimization” chapter (“Constraints”) in the WAE Design User Guide. |
Usability enhancement to improve L1 Circuit creation and association to Port Circuits. |
For more information, see the “Layer 1 Simulation” chapter (“Create L1 Circuits”) in the WAE Design User Guide. |
Layer 3 and Layer 1 simulation convergence modes are grouped together in the Simulation tab of the Network Options. |
|
The following table describes all new features related to WAE Live.
Ability to select which network on the Collector Server to insert a plan file into WAE Live. For more information, see the “Multi-Network Management” chapter in the WAE Live Administration Guide. |
|
Ability to add a remote network link in a multi-network environment. For more information, see the Multi-Network Management” chapter (“Adding a Remote Network Link”) in the WAE Live Administration Guide. |
|
The WAE Live and WAE Collector server plan files can be separate from each other for the purpose of collecting plan file data from external archives. For more information, see the “Data Source Settings” chapter (“Collecting Plan Files from External Archives”) in the WAE Live Administration Guide. |
|
Ability to filter Interface Queues based on interface descriptions in the Explore view. |
The Explore Interfaces UI includes a new description column in the Interfaces table that enables: |
The Explore table includes the following enhancements: – Enables hop selection in the Actual Path column, which takes you to the appropriate interfaces in the Interfaces table. – The Related Objects button enables filtering on both LSP source and destination nodes. – Enables filtering on the LSP destination and actual path. – The Related Objects menu LSPs menu changed LSPs to explicitly state LSPs Source. |
|
Performance is improved for the initial loading of WAE Live graphs with more than one month worth of data by sending sampled data rather than sending every data point to the UI. |
The following table describes all new features related to collection configuration.
All WAE Collector UI configuration features are described in the “Collecting Network Information” chapter (“Collecting Basic Information Using the WAE Collector UI”) in the WAE Platform Configuration Guide. |
|
Ability to configure collection on more than one network. For more information, see the “Add Additional Networks for Collection” section. |
|
New management IP editing capability on the Node List table. |
Ability to edit the Management IP address for one or more nodes directly on the Node List table. For more information, see the “View and Manage the Node List” section (“Edit Node Credentials”). |
Ability to configure how long or how many collections to store in the collector server. For more information, see the “Configure Collection History” section. |
|
Ability to collect inventory and topology information from a multi-layer (Layer 1 and Layer 3) network. Layer 1 (optical) collection has been tested with Cisco DWDM networks with Cisco Network Convergence Systems (NCS) 2000 and Cisco ONS 15454. For more information, see the “Collecting Multi-Layer Information” chapter in the WAE Platform Configuration Guide. |
|
Option to remove amplifier L1 links and nodes from topology collection. |
For more information, see the “Collecting Multi-Layer Information” chapter in the WAE Platform Configuration Guide. |
Option to collect feasibility metric and limit information in L1 circuits. |
For more information, see the “Collecting Multi-Layer Information” chapter (“Collecting Feasibility Properties for L1 Circuits”) in the WAE Platform Configuration Guide. |
For more information, see the “Collecting Multi-Layer Information” chapter (“Collecting Inactive or Failed L1 Circuit Objects”) in the WAE Platform Configuration Guide. |
|
Support for point-to-multipoint (P2MP) RSVP LSP collection from Cisco IOS XR and Juniper devices. |
The |
Extended support for Segment Routing (SR) LSPs and paths from IS-IS to OSPFv2. |
The following table describes all new features related to the WAE System.
Ability to show or hide components from the WAE System Settings page. |
Administrators can configure which applications can be hidden from the WAE UI. For more information, see the “User Management” chapter in the WAE System Administrator Guide. |
You can now view and monitor database information such as space usage, read/write cache rate percentage, and disk input/output performance from the WAE Statistics > Database Info page. For more information, see the “Services and Statistics” chapter in the WAE System Administrator Guide. |
|
For more information, see the “User Management” chapter in the WAE System Administrator Guide. |
The Network Model Manager is a new WAE UI tool that can be used to augment the network model generated by the Collector Server with traffic demand and visual layout information (by applying a template plan file). It then stores the augmented plan file in WAE Design Archive. For more information, see the “Viewing a Network Model” chapter in the WAE Platform Configuration Guide.
Refer to the /opt/cariden/software/mate/current/docs/table_schema.html file for a complete reference.
WAE Design, WAE Live, and WAE Collector CLI tools are located in the /opt/cariden/software/mate/current/bin. For available CLI options and descriptions, execute the CLI tool with the -help option.
Optimizes capacity planning by upgrading existing circuits and creating new circuits to meet maximum utilization thresholds. L1 circuits may be optionally created. |
|
Adds or removes LSPs for each LSP group and shares the setup bandwidth evenly within each group. |
|
Optimizes routing of LSPs to respect disjoint path requirements and to minimize the specified path metric. |
|
Mitigates congestion by rerouting demands via private SR LSPs with optimized routings. Interfaces whose utilization exceed the given threshold are considered to be congested. |
|
Provides segment routing congestion mitigation analysis across different scenarios. More detailed information on SR congestion mitigation can be found in the |
|
Provides the multi-layer services needed for multi-layer data collection. This tool is available in $WAE_ROOT/bin. For more information, see the “Collecting Multi-Layer Information” chapter in the WAE Platform Configuration Guide. |
|
The following table describes all new CLI options.
The following table describes all new API features. WAE Design API documentation is located in $CARIDEN_HOME/docs/api/design.
The following table describes all removed or deprecated API features.
The Cisco WAE Plan Table Schema and CLI Reference document has been removed from the Cisco WAE documentation set. The Cisco WAE Server Installation Guide is available only on Cisco.com: http://www.cisco.com/c/en/us/support/routers/quantum-wan-automation-visibility-engine/products-installation-guides-list.html.
A list of open source software used in WAE can be found in Open Source Software Used in Cisco WAN Automation Engine.
The following are descriptions of the open and resolved bugs in Cisco WAE Release 6.4. The bug ID links you to the Cisco Bug Search tool.
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Step 1 Go to http://tools.cisco.com/bugsearch.
Step 2 At the Log In screen, enter your registered Cisco.com user name and password; then, click Log In. The Bug Search page opens.
Note If you do not have a Cisco.com user name and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 3 To search for a specific bug, enter the bug ID in the Search For field and press Return.
Step 4 To search for bugs in the current release:
a. In the Search For field, enter a problem, feature, or a product name (for example, Cisco WAN Automation Engine) and press Return. (Leave the other fields empty.)
b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth.
To export the results to a spreadsheet, click the Export Results to Excel link.
This section describes the limitations and restrictions for Cisco WAE.
In some Linux installations with Xfce desktop installed, the documentation does not open from the WAE Design GUI Help menu. The workaround is to do one of the following:
$CARIDEN_ROOT/etc/collector/server/db-persistence/DiscoveryEngineImplementation.db
file must be removed prior to starting the web server. Since installation automatically starts the web server, the recommendation is to remove this prior to installation. snmp_find_interfaces
– Does not support association of a GRE tunnel with the physical interface it uses to reach the tunnel destination since the IP-Tunnel MIB lacks this information.
– Does not update LAG port status if LAGs are discovered running both parse_configs
and snmp_find_interfaces
. The workaround is to run only snmp_find_interfaces
.
– IGP topology collected through parse_igp
and login_find_igp_db
– 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. The snmp_find_interfaces
tool collects this information.
– MAC Accounting is not supported.
– snmp_find_rsvp
does not set the Standby value in the <LSPPaths> table for signaled backup paths or collect named affinities configured with affinity-maps.
– find_bgp
does not build BGP pseudo-nodes among internal ASNs.
– find_bgp
does not collect BGP peers under PE-CE VRFs.
– Does not accurately detect the bandwidth of some Juniper ‘ge’ interfaces that have a capacity of 10 Gbps.
– Collects POS bundles, but has limitations due to unavailability of the port OperStatus property.
snmp_find_ospf_db
cannot be used when routers have a large number of links that cannot fit into a single PDU. find_bgpls
does not support multi-area OSPF or multi-level IS-IS, non-TE-enabled interfaces, and pseudo-nodes. The workaround is to use SNMP- or login-based discovery. get_inventory
does not collect Juniper multi-chassis router hardware inventory.– SR protected adjacency SIDs are not supported.
– Concurrent RSVP-TE and SR-TE paths are not supported on the same LSP.
During detailed PCEP tunnel creation or when modifying PCEP tunnels, affinity values are misinterpreted if multiple affinities are specified. This limits you to specifying one affinity for IncludeAffinity, IncludeAnyAffinity, and ExcludeAffinity, and each of these values must be a number within [0,31].
– For Cisco IOS XR, there is no option to give the IP address of the LSP directly; you can only specify a loopback address. There is no option to give tunnel affinity values directly; you can only specify an affinity-map name.
– For Junos, there is no inter-domain keyword, which is used only when an inter-area LSP is created.
– One workaround is to perform an offline installation. For instructions, refer to the “Offline Installation” chapter in the Cisco WAE Server Installation Guide.
– Another workaround is to change https to http.
Note This is not a secure solution. For information on how to resolve OS security issues, contact your OS vendor.
1. In the /etc/yum.repos.d/epel.repo
file, change the first instance of https to http.
Change https
to http
in the following line:
2. Execute yum to clean up makecache.
3. Rerun the installer. For detailed installation instructions, see the Cisco WAE Server Installation Guide.
The embedded_web_server
tool is deprecated. The recommendation is to use the wae-web-server
service, which is constantly monitored to be brought up automatically.
By default, this web service starts upon installation completion. Therefore, if you stop the web server using the embedded_web_server
tool ( embedded_web_server -action stop
), the web server does not stop. The workaround is the following:
The WAE Statistics page does not open in all browsers. The workaround is the following:
1. Click the WAE Statistics link. The URL format is https:// <server_IP> :8443. Example:
2. Copy the URL of this page to another browser window.
3. In the new browser, change the URL port from 8443 to 8843. Example:
4. Follow the browser messages to accept the connection and add it as an exception.
Both the System UI and the WAE Design Archive UI have local user management capabilities. If both are used to configure users, WAE uses the most recently updated information. The recommendation is to use only the System UI to manage local users.
Some newer Linux distributions have started using a new way (via biosdevname
) of naming hardware devices, including the network interfaces. This causes some software that depends on the traditional naming (for example, eth0
, eth1
) to fail on license checks, including MATE.
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
).
Certain tools (such as parse_configs
) may require more memory to start than what is available. The symptom is an error message similar to the following:
The workaround is to set the maximum memory to a low enough value in the CARIDEN_JAVA_OPTIONS
variable before calling the tool. An example setting is as follows:
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 are accessible except for images, graphics and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact accessibility@cisco.com.
For related documentation, see the Cisco WAE 6.4 Documentation Roadmap.