– 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
. The workaround is to run only
Juniper routers: Signaled standby LSP path option is not available from the standard MPLS-TE MIB for Juniper routers. Only the active path option name is collected.
IOS XR routers
– IGP topology collected through
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 IOS XR supports IS-IS IPv6 TE extensions. The
tool collects this information.
– MAC Accounting is not supported.
does not set the Standby value in the <LSPPaths> table for signaled backup paths.
does not build BGP pseudo-nodes among internal ASNs.
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.
TE Extended Admin Groups (EAGs), also known as extended affinities, are not supported.
Port circuits are not built for LAG/bundle members whose nodes are not within the same IGP instance as the AS.
SAM-OSS Integration with Snapshots
does not populate the <NodeTraffic> table. This table is derived and populated when
and SNMP tools are used together.
does not populate the NetIntActivePath column in the <LSPs> table.
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.
Web User Management
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.
Starting MATE Design in Linux
directory is not automatically added to $PATH (only
is). If not in
, 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
file on the primary node, as follows.
Change this line:
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
) of naming hardware devices, including the network interfaces. This causes some software that depends on the traditional naming (for example,
) to fail on license checks, including MATE.
The workaround is to append
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
, ...) instead of the
names (such as
Certain tools (such as
, for example) may require more memory to start than what is available. The symptom is an error message similar to the following:
Error occurred during initialization of VM.
Could not reserve enough space for object heap.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
The workaround is to set the maximum memory to a low enough value in the
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.
Cisco MATE Live
– New feature updates in the
Cisco MATE Live User Guide
– Making plan files from multiple networks available to the MATE Live UI
Cisco WAE Platform Configuration Guide,
Manual Collection with Continuous Polling chapter
– 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.