Access: WAE Live > Settings and select General Settings tab
The General Settings page enables you to configure where the Map archive plan files are stored, how often to collect the data and from where, status of the latest data set collected, and which interface types are used in reports.
Note For information on configuring collection, see the WAE Platform Configuration Guide.
The Application Data and Collection Data sections are applicable on a per-network basis. Prior to configuring or making changes to either of these sections, select the appropriate network from the Network list (top left).
Multi-network collection is only supported in the following instances.
- The Collection Source is External Archive wherein a snapshot was configured to use
archive_insert to insert data into that external archive.
- The Collection Source is None wherein a snapshot was configured to use
ml_insert_plan to insert data into the datastore and to use
archive_insert to insert plan files into the Map archive.
For information on configuring multiple networks, see the Multi-Network Management chapter.
Use the Application Data section to configure where to put plan files used by the Map component so that WAE Live can extract them.
- Map Archive—The local directory in which collected plan files and the template file (template.pln) are stored for display in the Map. You must configure a unique Map archive for each network, and it is required only if using the Map component for that network.
If you are manually inserting plan files into the Map archive, this must match the case-sensitive path used in the MAP_ARCHIVE_INSERT task (that calls
WAE Live automatically creates the template.pln file from the most recently collected plan file if no template exists. To create the visual elements of a template file and save it to this location, use the WAE Design GUI. (For information, see the WAE Network Visualization Guide.) If visual elements have not been applied, the plan file is visualized in the default, unprocessed state.
Note If you are using an external archive for the collection method, the Map archive must be a different location than that of the external archive.
Data collection is the process of getting the plan files from WAE Collector and storing them in the internal datastore.
This area identifies the source and status of data collection. For the WAE Network Interface (NI) server, it also identifies the frequency of collection.
By default, WAE Live checks for a plan file every 30 seconds. The Insertplan.Source.Pollfrequency property in the Advanced Config feature sets this default. If none is defined, the default applies.
- If using the Collector server, WAE Live receives the plan file at this interval only if it has been updated with changes.
- If using the WAE NI server, WAE Live receives the plan file based on the value in the Frequency field regardless of whether it has changed.
Note There may be times when the collection status (accessed by clicking Check Status) shows no errors, but the number of plan files being collected does not increase. To troubleshoot this and other plan file insertion issues, use the
ml_insert_ctl tool. For information, see
You must select one of these source options.
- Server—Use a server to collect the data. This can be the Collector server or the WAE NI server. The server must be running.
– Server URL—The location of the server. The format is https://<server_IP>:<port>. The default port for the Collector server is 8443, and the default port for the WAE NI server is 8086.
– Username—An administrative username for the server.
– Password—The password for the username of the server.
The Collector server username and password are set in the System > User Management page and require an admin role. For information, see the WAE System Administration Guide. For assistance with the WAE NI server password, contact your support representative.
- External Archive—Select this option if you are collecting data through an augmented snapshot or a manual snapshot. The archive must exist. That is, you must have created the archive using
archive_init and that path and the one entered here must be the same. This must be a different location than the map archive.
If using external archives for multiple networks, each network must have a unique archive location.
- None—Do not collect data. If you are collecting data through snapshots and if you are manually inserting data into WAE Live using
ml_insert_plan, select this option. For snapshots, however, the recommendation is to use the External Archive option.
Additionally, you must identify the frequency to check for and receive plan files, and whether you are using the WAE NI server.
- Continuous—Identifies whether to collect plan files from the WAE NI server or not.
- Frequency—The frequency, in minutes, in which WAE Live receives the plan file from the WAE NI server. WAE Live receives the plan file regardless of whether it has been updated. The value must be a factor of 60 (1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, 60). The recommended value is 15 minutes.
- Check Status—Shows the status of the most recently collected data by WAE Live.
- Advanced Config—This is for advanced configuration editing only. Consult your support representative for assistance.
This page must be configured to collect the plan files containing topology and statistics for the same network used in the inventory collection process. WAE Live must get these plan files from the same server as does the inventory collection process.
Given the inventory collection process gets this same plan file (
collector_getplan) and inserts the inventory into the same network (
ml_insert_ctl -network), there are no required inventory configurations on the WAE Live Settings > General Settings page.
Note These networks must be the same: the network for which WAE Live is configured to get plan files and the network into which the inventory is inserted.
In this section, specify the default interface type showing on the Explore Interface page. These can then be used in reports on selected interfaces of one or more types. Note that this is not configurable on a per-network basis.
- Individual physical interface—An interface that is not in a LAG and does not have an IP address. These interface names do not have a decimal.
Example: so-0/2/2, g2/0/0
- Individual logical interface—An interface with an IP address that is not in a LAG. These names might have a decimal.
Example: et-0/1/2.0, g2/0/0
- LAG logical interface—An interface with an IP address that contains member interfaces.
Examples: ae0.0, Bundle-Ether1, Port-Channel7
- LAG physical interface—The physical representation of an aggregated interface to which a LAG logical interface (such as ae0.0) is assigned.
Example: ae0 for Juniper interfaces
- LAG member interface—An interface that is in a LAG.
- Unknown—None of the above interface types.