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.
Access: WAE Live > Settings > Map tab
The Settings > Map tab lets you configure the WAE Live Map panels and set a default layout for the weathermap. These configurations apply to all networks and are not configurable for a specific network.
WAE Live automatically creates the template (template.pln) file from the most recently collected plan file if no template exists. These templates and plan files are stored in map archives for use in the Map component. If visual elements have not been applied, the plan file is visualized in the default, unprocessed state. To create the visual elements of a template file and save it to a map archive, use the WAE Design GUI.
A unique map archive name and path are automatically created and configured for a network when the network is added. These map archives are stored in $WAE_ROOT/data/mldata/archives
as <network_name> -archive
.
Access: WAE Live > Settings > Map tab > Advanced Config (in lower-left corner)
A s is the case with the WAE server, the Map tab includes an advanced configuration (Advanced Config) link. Clicking this link displays configuration details for the Map component. While you can edit this file, be advised that any changes you make could adversely impact your Map setup. We recommend that you consult with your support representative for as sistance before changing any parameters.
Assuming that you are using the default map archive path setting and the default installation directory /opt/cariden
, the property that defines the path to the map file is:
"Map.ArchivePath": "/opt/cariden/data/mldata/archives/default-archive"
You can override the default map archive setting. The Map.ArchivePath property controls the location and map archive name. It uses the following format:
"Map.ArchivePath": "
<map_archive_path>/
<network_name>-archive"
For example, if you want to change the name of the default archive to reflect the “Acme” network’s weathermap, change this property to:
"Map.ArchivePath": "/opt/cariden/data/mldata/archives/acme-archive"
Map archives are automatically created when you change the Map.ArchivePath property.
The Traffic Widget section lets you configure the Peering panel on the Map page. This panel shows the highest traffic utilization per peer and per site. The far left column lists the peers, while each top column lists the associated sites. The icons in the panel represent the traffic flowing between the two.
For this panel to have data, you must configure the collection of BGP.
– Top ___ ASNs by Traffic Utilization—The ASNs with the highest traffic utilization. Enter a whole number from 1 to 20.
– Except—To exclude specific ASNs that would be captured by the highest utilization, enter one or more ASNs separated by commas.
– Only These—To use only a specific set of ASNs, regardless of their traffic utilization, enter one or more ASNs separated by commas.
– Top ___ Sites by Traffic Utilization—The sites with the highest traffic utilization. Enter a whole number from 1 to 20.
– Only These—To use only a specific set of sites, regardless of their traffic utilization, enter one or more site names separated by commas.
The Events Widget lets you configure which events appear on the Map page. This panel tracks a set of current events and the number of changes since the last plan file was received.
Configuration of this panel is a combination of this UI and the default_timeplot_summary_format.txt
file located in the $CARIDEN_HOME/etc/matelive
directory.
For an event to appear, it must be configured in both locations. Combining the examples in this section would result in two events in the panel: Circuits down and Nodes down.
default_timeplot_summary_format.txt
file—Defines the metrics used for the events. Each metric is listed in the “Queries” section. For information on how to configure this file, see the comments at the end of the file. Example: This is an excerpt from the default file.
default_timeplot_summary_format.txt
file. – Metric—The name of the event metric that appears in the default_timeplot_summary_format.txt
file.
– Display Name—The event name that appears in the panel on the Map page.