Cisco MATE and Cisco WAN Automation Engine Release Notes, Release 6.1.6
This document describes the limitations and bugs for Cisco MATE and Cisco WAN Automation Engine (WAE) Release 6.1.6.
Cisco MATE consists of the MATE Design, MATE Live, and MATE Collector products. Cisco MATE delivers the network manageability required for simplifying processes and for delivering cost-efficient, reliable services. Each of these tightly integrated products simultaneously supports planning, engineering, and operational tasks.
Cisco WAE is a powerful, flexible software-defined networking (SDN) platform. It abstracts and simplifies your WAN environment while making it fully open and programmable. Cisco WAE is a network modeling technology that allows for real-time analysis of traffic needs and placement in complex WAN topologies.
This product includes the following open sources:
The following bugs are resolved in Cisco MATE and WAE Release 6.1.6. 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 on.
To export the results to a spreadsheet, click the Export Results to Excel link.
This section describes the limitations and restrictions for Cisco MATE and Cisco WAE.
EIGRP routing simulation is not accurate. This issue will be corrected in a future release. Until then we recommend that it not be used.
2. Restart the web server from a directory that has permissions for the WAE user specified during installation. Use the following command:
Due to vendor MIB limitations, Cisco MATE Collector 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, per class-of-service demands estimated through Demand Deduction are less accurate. Estimates of traffic totals over all classes of services, however, are not affected.
$CARIDEN_ROOT/data/collector/server/snapshots
. $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. If you forget to do so, after installation, stop the web server, remove this file, and then restart the web server. mate_auth_init
. – Does not support association of 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
.
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.
– find_bgp
does not build BGP pseudo-nodes among internal ASNs.
– find_bgp
does not collect BGP peers under PE-CE VRFs.
parse_configs
does not accurately detect the bandwidth of some Juniper ‘ge’ interfaces that have a capacity of 10 Gbps. SAM-OSS Integration with Snapshots
sam_getplan
does not populate the <NodeTraffic> table. This table is derived and populated when sam_getplan
and SNMP tools are used together. sam_getplan
does not populate the NetIntActivePath column in the <LSPs> table. sam_getplan
and SNMP tools are used together in the snapshot process for multivendor network collection, then Alcatel-Lucent traffic measurements cannot be aligned with those collected from other router platforms.When creating tunnels with REST APIs, both primary and secondary tunnels are set to Standby.
Both the System UI and the MATE Design Archive UI have user management capabilities. If both are used to configure users, MATE uses the most recently updated information. The recommendation is to use only the System UI to manage users.
The $CARIDEN_HOME
directory is not automatically added to $PATH (only $CARIDEN_HOME/bin
is). If not in $CARIDEN_HOME/bin
, to start the MATE GUI from the command line, you must specify its full path:
The wae-ha-deploy script is not updated with the proper version, rendering the wae-core modules unable to start in a multiserver (HA) environment. The workaround is as follows:
1. Modify the /wae-platsvcs/confmgmt/roles/wae-core/templates/org.apache.karaf.features.cfg.j2
file on the primary node, as follows.
2. Run the wae-ha-deploy script.
License Check Failures on Newer Linux Distributions
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 use ifconfig to verify that the NIC are named eth0
(or eth1
,...) instead of the biosdevname
names (such as p34p1
).
Certain tools (such as sam_getplan
and parse_configs
, for example) 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:
The following information is missing from the documentation set. For assistance, contact your support representative.
– New feature updates in the Cisco MATE Live User Guide
– Making plan files from multiple networks available to the MATE Live UI
– statsComputingMinimumWindowLengthInSecs example needs a minor change. For convenience, the entire definition and example are given here:
statsComputingMinimumWindowLengthInSecs—Defines the minimum amount of time, in seconds, over which to generate averages of the polled traffic statistics. For example, if set to 300, to determine the rate of incoming packet errors, the Continuous Poller server takes the average of these incoming packet errors over the last 300 seconds. These traffic statistics are added to the plan file each time it is generated. The minimum value is 300 seconds.
For related documentation, see the Cisco MATE and WAE 6.1 Documentation Overview.