NFM-P-based schedules

General information

An NFM-P-based schedule is only retained in the NFM-P db and is not deployed to the target NEs. When a configured schedule run time arrives, the NFM-P executes the associated task and compiles the task results for presentation to NFM-P clients.

A delay time for executing NFM-P-based scheduled runs can be configured to delay the execution of a run within a scheduled task in cases when a previously scheduled run is still executing. The NFM-P attempts to execute the new run at the configured delay time; if the run cannot execute at the delay time, the NFM-P skips the scheduled run. When a previous run completes and the next scheduled run is triggered, the run executes and is not delayed, whether a delay time is configured.

The NFM-P-based schedule functionality uses the NFM-P server time zone to trigger the scheduled tasks.

NFM-P-based schedules design considerations

Consider the following when you create an NFM-P-based schedule or add a scheduled task.

• Ensure that scheduled tasks are run sufficiently far apart to allow one task to finish before the next starts. Otherwise, the next occurrence of the task is skipped or delayed, if the delay time is configured.

• Do not create schedules that overlap, because no validation is performed to ensure that a newly configured schedule does not overlap with an existing schedule.

• A new scheduled task is shut down by default and must be turned up before it can be executed with one exception. Scheduled software upgrade tasks associated with all NE types are auto-enabled by default.

• Users with write access permissions to a specific schedule package can view or delete all the created schedules and scheduled tasks related to the package. Other users can only view schedules. See the section on NFM-P user security in the NSP System Administrator Guide for more information about user permissions.

• By default, the NFM-P associates a scheduled task with the user account that is used to create the scheduled task. You can assign a different user account to a scheduled task. The user account must have the assigned scope of command role that is appropriate for the task, or the NFM-P does not execute the scheduled task.

• NFM-P-based schedules are not distributed to the target NEs.

• You cannot delete a schedule that has a dependency, for example, one that is associated with a task. You must first delete the scheduled task from the schedule, then delete the schedule.

• One minute is added to the default start and end time values of an NFM-P-based schedule to allow time for schedule configuration.

• A monthly NFM-P-based schedule with the Run Every Month or Run Every Months parameter configured uses a 30-day interval.

• When you create a monthly NFM-P-based schedule using the Run Every parameter and specify a date that does not exist for the specified months, the last date of the month is used. For example, if you create a monthly scheduled task, starting January 31st, the scheduled task will run on February 28th, March 31st and April 30th when those months are specified in the schedule.