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 > Evaluations tab
Note Since there are multiple users who have equal permissions, be considerate and cautious when making changes to any Settings page.
|
|
---|---|
1. Configure the shortest amount of time (in minutes) that can be scheduled for an event. |
Set Minimum Evaluation Interval section |
2. Optional: Configure evaluations to run automatically as the event date draws near. |
Automatically Re-Evaluate Events section |
Creating User-Defined Tests chapter |
|
4. If you want to modify the default evaluation, which consists of a single congestion test, configure which tests are run in the evaluation and in what sequence. You can also configure which tests must pass for the evaluation to pass, and whether to continue the evaluation if a test fails. |
Configure Evaluations and Tests section |
The Minimum Evaluation Interval is the amount of time (in minutes) that an evaluation occurs.
Note The Minimum Evaluation Interval must be no less than the minimum gap between plan files stored in the traffic model repository. For example, if there is a cron job running to execute a snapshot every 30 minutes, then the Minimum Evaluation Interval must be at least 30. Setting this interval smaller is possible, but doing so potentially results in evaluations using the same plan file when the application is searching for available event time slots.
This consistent interval, which cannot be changed elsewhere in the application, ensures that networks can be completely modeled for the evaluation process. If you change this value, the scheduled events that are in progress finish their evaluation. The status of scheduled events remains the same.
This value is also used in last-minute re-evaluations. See the Last-Minute Re-Evaluations section.
Since network topology and traffic changes, while an event may have passed its initial evaluation, it might prove beneficial to re-evaluate it as close to its scheduled time as possible. The Automatic Re-evaluation option enables you to create automatic re-evaluations for such purposes. If the scheduled event fails the re-evaluation, its state changes to Pending.
To enable or disable, select the Enable Automatic Re-evaluation option. If enabled, the re-evaluations apply in the following order.
Example: For example, if today were April 7 and you scheduled an event to start April 29 at 8:00 PM, automatic re-evaluations would occur weekly on April 8, 15, and 22, daily April 23-28, and again on April 29 at 8:00 AM and 4 PM.
If you are performing automatic evaluations, you can optionally perform last-minute re-evaluations on imminent events. An imminent event is an event whose scheduled start time is less than two times the Minimum Evaluation Interval value (in minutes).
Example: If the current time is 7:00 PM, the event start time is 7:30 PM and the Minimum Evaluation Interval is 20 minutes, then the event is imminent since 2 x 20 > 30 (difference between 7:00 and 7:30).
Imminent events are re-evaluated using the most recent traffic matrix available. Provided all automatic evaluations have completed and there is still sufficient time to run an evaluation, imminent events are evaluated twice: once at 2xM, where M is the Minimum Evaluation Interval value, and again at M.
Example: If the event start time is 7:30 PM and the Minimum Evaluation Interval is 20 minutes, the imminent event is automatically evaluated at 6:50 PM and again at 7:10 PM.
The Settings > Evaluations page is where you configure the default evaluation. However, you can modify the evaluation when adding an event.
Note This information pertains both to this Settings > Evaluations page, as well as when adding an event.
Each evaluation consists of one or more groups, and each group contains one or more tests.
WAE Coordinated Maintenance has the following built-in tests.
Note Built-in tests execute as described here. Changing their operators results in inaccurate evaluations and therefore, is not recommended.
All tests have these configurable parameters.
Note Do not change the operator of built-in tests.