The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This guide is for administrators who configure and manage the WAE Live application. WAE Live is a web-based application that provides visibility into the network infrastructure, state, and traffic utilization captured by the Collector. It includes the following components:
WAE Live depends on data collected by the Collector server and other collection mechanisms to store network data in data stores for processing and displaying in the web UI.
To configure WAE Live, it is assumed that you already have:
This guide assumes that you are familiar with the CLI commands to configure the WAE Live server and to troubleshoot operations on your WAE server installation.
Note
$WAE_ROOT
is the directory in which the software is installed. On Linux, the default $WAE_ROOT
is /opt/cariden
. ($WAE_ROOT
and $CARIDEN_ROOT
are the same.) $CARIDEN_HOME
is the directory in which the WAE Design, WAE Live, and WAE Collector executables and binaries are installed. On Linux, the default is /opt/cariden/software/mate/current
.
WAE Live collects data from WAE Collector, which can include the creation and addition of a simulated demand traffic matrix. The data is stored in plan files. WAE Live uses two internal mechanisms, a time-series optimized data store and an internal Map archive, to store this data and make it available for use in the application. The Map component accesses the Map archive and shows the visualization of these plan files in a weathermap layout. The Explore and Analytics components access the data store.
If a newly discovered node cannot be assigned to an existing site, WAE Live creates an ExtraNodes site and places the unassigned node there.
To enhance the visualization of these plan files, you can create and edit multiple plan file layouts using the WAE Design GUI. After saving the plan file as a template back to WAE Live, it is applied to the most recently collected plan file and stored for use in the Map. For information on how to assign nodes to sites, how to create and edit layouts, and how to save these layouts to WAE Live as templates, see the Cisco WAE Network Visualization Guide.
Access: WAE Live > Settings > General tab
The General tab includes an advanced configuration (Advanced Config) link. Clicking this link displays data configuration details (config.xml) for your WAE server. While you can edit this file, be advised that any changes you make could adversely impact your WAE Live setup. We recommend that you consult with your support representative for assistance before changing any properties or parameters in this file.
Relevant log files are located in $WAE_ROOT/logs/wae-live
and $WAE_ROOT/logs/wae-web-server
. You can also access wae-web-server
log files from the Statistics UI.
ml_insert_ctl
tool. For information, see ml_insert_ctl -help
. If this does not reveal the issue, troubleshoot the actual collection process of WAE Collector. mate_tech_support
tool to create a tar file of support information. The output is stored in the /tmp/MATE_TS
directory by default. To change the directory in which the results are stored, use the -tar-path
option. Example: This creates a tar file of support information and stores the output in the /troubleshooting
directory.
The next sections describe how to use the web UI to set up and configure WAE Live:
– Data Source Settings —Describes how to configure WAE Live to get plan files from the Collector server, WAE Network Interface (NI) server, or an external archive.
– Explore and Analytics Settings —Describes how to specify default interface types and how to create user-defined properties for use on Explore and Analytics pages.
– Map Settings —Describes how to configure the Map page, including its panels.