Add a Network Maintenance Task
You can add a network maintenance task to schedule maintenance events for network elements, so that you can perform updates or other configuration tasks. Currently, you can add maintenance events only for nodes with the overload bit set.
Maintenance events are planned failures at specific future dates and times. During a scheduled maintenance event, the selected elements are considered logically down, and the system reroutes the LSPs around those elements during the maintenance period. After the maintenance event is completed, the default behavior is that all LSPs that were affected by the event are reoptimized.
The Path Computation Element (PCE) attempts to reoptimize only PCE-initiated and PCC-delegated LSPs (not PCC-controlled LSPs).
To add a network maintenance task:
Every time the task runs, it first checks the complete condition for the maintenance event created by the task. If all the elements included in the maintenance task satisfy the complete condition (for example, overloadBit = false), it completes the maintenance event. Next, it looks for elements that match the create conditions (for example, overloadBit = true). If it finds such elements, it creates a new maintenance event that includes those elements.
Just as for other maintenance events, the “M” symbol on the topology map indicates the affected nodes. In the Maintenance tab of the network information table, the maintenance event displays the comment Created by maintenance task in the Comment column.
This type of maintenance event completes when the included nodes no longer have the overload bit set, but the event will not be deleted automatically. You must manually delete the completed event from the Maintenance tab of the network information table.
Field |
Description |
---|---|
Step 1 |
|
Name |
Specify a meaningful name for the task. |
Task Group |
From the list, select Utility Tasks. |
Task Type |
From the list, select Network Maintenance. |
Step 2 |
|
Task Options |
Configure the following fields:
|
Event Create Conditions |
Specify what conditions should trigger the creation of the maintenance event. Select one or more conditions displayed in the Available column and click the right arrow to move them into the Selected column. Currently, the only available condition is Node. Once Node has been moved to the Selected column, the Attributes table appears. Click the plus sign (+) to add a property row and then click in the Name field to see the drop-down menu arrow. From the drop-down menu, select the create condition. Currently, the only available create condition is overloadBit. In the Value column, use the drop-down menu to select the value of True for the overloadBit create condition. Note:
For other create conditions available in future releases, False might be the appropriate selection. |
Event Complete Conditions |
Specify what conditions should trigger the completion of the maintenance event. The fields on this tab work the same way as the fields in the Event Create Conditions tab. |
Step 3 |
|
Schedule |
Schedule the task to be triggered once or to recur automatically based on the interval you specify. Startup Options:
Recurrence Options:
Note:
Instead of scheduling recurrence, you can select to chain the task after an already-scheduled recurring task, so that it launches immediately after the other task completes. Select Chain after another task. From the list of recurring tasks that is displayed, select the task after which you want to launch the task that you added. |