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 Coordinated Maintenance > Settings > Data Source tab
Note Since there are multiple users who have equal permissions, be considerate and cautious when making changes to any Settings page.
WAE Coordinated Maintenance uses collections from two sources as input into the evaluation process: the traffic model and the topology template. Note that these two sources can be on the same or different hosts, but they must use the same network for their collection. Figure 4-1 shows an example configuration using a remote archive for the traffic source and WAE Live for the topology source.
Traffic Model —This repository identifies the location of the plan files containing the demand traffic. This information is used for evaluating traffic during the proposed event period based on traffic during similar times and dates in the past.
Topology Template —The template is the most current view of the network topology. The topology template must be well maintained on a regular basis such that it accurately represents the “as-built” network. Best practice is to use the WAE Live Map archive.
The following fields are applicable to both the traffic model and topology template unless otherwise specified.
– If using WAE Live (for a topology template), the path must match the entry in the Map Archive field on the WAE Live Settings > General Settings page.
– Otherwise, the path must match the entries used when configuring archive_init -archive
, archive_insert -archive
, and archive_config -path
to create and populate the repository.
Note Best practice is to not change the traffic model location once the application has used it. If you change the archive location, start with a new database, change the value in the Database Path field (on the Settings > General page), and re-create events.
Note Remote WAE Live is applicable only for the topology template. Remote Archive is applicable to both the traffic model and topology template.
– Server name, protocol, and port—Identifies the remote collection source.
– Network Name (Remote WAE Live)—Name of the WAE Live network that identifies the collection on the server. The network name must match the network name for which the Map archive is configured on the WAE Live Settings > General Settings page.
– Archive Name (Remote Archive) —Archive name that uniquely identifies this collection on the server. The archive name must match the archive name used when configuring archive_config -name
.
– Username and Password—Username and password of the server being accessed.
– (Traffic model only) UTC Offset—The archive’s time zone. If archive_insert -time-zone
was used in the collection process, this UTC offset must be the same UTC value.
Figure 4-1 Example Coordinated Maintenance Configuration