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.
Evaluating an event is the last step in the workflow for adding events.
Several factors affect the time it takes to run an evaluation, including the number of objects under evaluation, the duration of the proposed event, and the number of other events that are already scheduled. Therefore, you have the option to schedule evaluations in the background.
Note Unless you are placing events in Pending status while further analyzing other events, it is best practice to schedule events once they pass their evaluations. The reason is because evaluations take time and because the scheduling of new events could affect the validity of the evaluation. Therefore, if running evaluations in the background, it is a good idea to periodically check the Maintenance Events table for their completion.
You can re-evaluate events at any time.
If multiple evaluations are running, they will finish at different times. If an evaluation finishes and its event is scheduled before another evaluation finishes, and if that newly scheduled event overlaps the time slot for one that is under evaluation, you must re-evaluate the second event.
Example: Evaluations for events A, B, and C are running. The time slots for B and C overlap. Event C finishes first and you schedule it. When the evaluation for event B finishes, event C will be listed as an overlapping event. You must re-evaluate event B before you can schedule it. Event A is unaffected by events B and C since they use different time slots.
One of the admission criteria for a new event is that it not violate the admission criteria of a previously scheduled event. Additionally, all scheduled overlapping events must be accounted for in the proposed event’s evaluation. Thus, when a scheduled event is overlapping a newly proposed event, the evaluation process re-evaluates scheduled events for those overlapping windows to ensure their criteria is honored and also conducts evaluations for all possible network states.
Example: Scheduled event A takes down node cr1.fra and is scheduled for November 8 from 3:00 to 5:00 AM. A proposed event B is to take down node cr1.par on November 8 from 4:00 to 6:00 AM. There is one overlapping hour from 4:00 to 5:00 AM. As a result, the following evaluations occur.
If event B is scheduled and automatic re-evaluations are configured, event A is re-evaluated in two segments: once from 3:00-4:00 AM with only cr1.fra taken down and again from 4:00-5:00 with both nodes taken down.
The above is a very simple example that is carried through no matter how complex the overlapping scenarios are. Each test segment displays its results in the Summary Report section on the View page.
The simplest method of handling an evaluation failure is to delete the event if you are certain you do not want to schedule it. Otherwise, you can try re-evaluating it.
|
|
---|---|
Evaluate newly added events that have not been saved as pending or scheduled |
Click the Evaluate button at the end of the workflow for adding an event. |
Click the check-mark icon in the Maintenance Events table. If needed, change the start time and duration interval. No other changes in evaluation can be made to a scheduled event. |
|
Click the check-mark icon in the Maintenance Events table. If needed, change the start time and duration interval. No other changes in evaluation can be made to a pending event. If there are overlapping events, click the eye icon. Change the overlapping evaluations included in the evaluation. For information, see the Re-Evaluate Using Different Overlapping Events section in the Viewing Events and Reading Evaluation Reports chapter. |
|
Click the Stop button in the Maintenance Events table (background events) or in the evaluation process window (foreground). |
|
After running a re-evaluation, click the Discard button on the View page for associated event. The results of the previous evaluation remain in tact. |