Cisco Cisco WAE Planning

To search for bugs in the current release:

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.)

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:

Open the help files from a terminal in the 

$CARIDEN_HOME/docs

 directory.

Install a default browser.

Install the following packages:

yum install evince

yum groupinstall "X Window System"

yum groupinstall "Desktop"

yum groupinstall "General Purpose Desktop"

Due to vendor MIB limitations, 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.

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.

Shared Risk Link Groups (SRLGs) are not supported in Alcatel-Lucent Service Aware Manager 
(SAM) collection.

The interval for continuous LSP discovery in WAE NI cannot be less than 60 seconds.

LSP's ActualPathHop cannot be resolved when using continuous collection. As a workaround, use 
interval-based collection.