Section 8 Scheduler. Alcatel-Lucent OmniVista 4760 Network Management System

Legal notice: Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright 2011 Alcatel-Lucent. All rights reserved. The CE mark indicates that this product conforms to the following Council Directives: - 2004/108/EC (concerning electro-magnetic compatibility) - 2006/95/EC (concerning electrical safety) - 1999/5/EC (R&TTE)

Chapter 1 Overview Overview... 1.1 Terminology... 1.1 Access to the Application... 1.1 The Scheduler Menu... 1.1 Description of the Interface... 1.1 Tree Structure Window... 1.2 Display Preferences... 1.3 Detailed Information Window... 1.3 Predefined and Current Jobs... 1.3 Jobs to Schedule after Installing the Server... 1.5 Execution Process... 1.5 Execution Reports... 1.5 Description of the Reports... 1.6 Viewing Reports... 1.6 Managing Reports... 1.7 Managing Scheduled Operations... 1.7 Available Commands... 1.7 Common Operations... 1.7 Scheduling Parameters... 1.9 Scheduling... 1.9 Task Definition...1.10 Retry Options...1.10 0-1

Subjob Options...1.10 Status...1.11 Copy a Task in Order to Customize It...1.11 Customizing the Scheduler...1.11 0-2

1.1 Overview The Scheduler is an application of the Alcatel-Lucent OmniVista 4760 Network Management System (called OmniVista 4760 in this document). 1.1.1 Terminology Scheduler: This application manages the automatic execution of tasks. A task can be: - Executed in immediate or deferred mode. - Unique or repeated. - Independent or synchronized with another task. Job: Entity including one or more tasks performed simultaneously. Task: Executable operation or running an OmniVista 4760 internal or external service. For more information, refer to Execution Process. 1.1.2 Access to the Application Direct access: You can run the Scheduler by clicking in the Applications toolbar. Indirect access: When a programmable operation is run, the Scheduler is automatically displayed. You can configure a start time and a possible repetition frequency (time interval) for the task. Example: PCX synchronization is available from the System directory. 1.1.3 The Scheduler Menu The Scheduler has a specific menu: Preferences > Scheduler > Configuration Customizing the Scheduler. 1.2 Description of the Interface The interface is divided into two sections: - A tree structure presenting a list of tasks and jobs is displayed on the left. - A detailed information window with the job and task scheduling and status tabs is displayed on the right side. 1-1

Chapter 1 Figure 1.1: Scheduler Window 1.2.1 Tree Structure Window The items shown in the tree structure are the following: (orange) (red) Job disabled (not scheduled, i.e. has to be run manually) Job active (job waiting to be run) (green) Job running Task scheduled (i.e. waiting to run) 1-2

(blue frame) According to the context this status icon indicates: - Idle task The task must be run manually. - Paused job For software downloads only, this icon indicates a mandatory pause set by the system. Task running (green frame) Execution report successful status. Execution report failed status. (red frame) 1.2.2 Display Preferences By default, the scheduler lists all jobs without applying any filter. You can view other users' jobs and their scheduling. You cannot modify these jobs. A display filter is available to ensure that you only display your own jobs: select the option Preferences > Scheduler > User > Show only my jobs. 1.2.3 Detailed Information Window Jobs and tasks have dedicated tabs: - Job. Scheduling (see Scheduling ). - Subjob options (Options for depending jobs, see Subjob Options ). - Task Retry Options (see Retry Options ). - Task Definition (see Task Definition ). - Status (see Status ). 1.3 Predefined and Current Jobs Any OmniVista 4760 application may use the scheduler to schedule or perform jobs in deferred mode. Possible tasks are listed below. Tasks performed at regular intervals are preprogrammed and their respective frequencies are specified in brackets : 1. Directory Full LDAP/PCX synchronization. Partial LDAP/PCX synchronization [daily, weekly] Import/Export LDAP. 1-3

Chapter 1 Password Policy [weekly] Company Directory Synchronization 2. Accounting/Traffic analysis Archive accounting records [weekly] Purge carrier configuration [weekly] Calculate total counters [daily, weekly] Purge old accounting data [weekly] Purge old traffic analysis counters [daily, weekly] Recalculate costs. Load IP records [daily, weekly] Load accounting records [daily, weekly] Detect exceeding thresholds [daily, weekly] Restoring records Threshold reduction 3. Alarms Purge alarms [daily, weekly] Purge alarm reports [daily, weekly] 4. Maintenance Restart server [weekly] Save OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise Communication Server databases. Defragment OmniVista 4760 databases Save OmniVista 4760 database Alcatel-Lucent OmniPCX Enterprise CS/ OmniPCX 4400 software update 5. Configuration Import/Export PCX. Save/Restore OmniPCX Office databases. Download OmniPCX Office software update 6. Reports Generate reports. 7. Security: search of expired password [weekly] 8. Audit: upload, store and purge of Audit data [daily] 9. SIP Download firmware update Deploy configuration Export of template Import of SIP users, devices, links Tasks linked with an application not included in the license are listed but not performed. Although execution status is always displayed as successful, the log file confirms that the task is inactive. Note: 1-4

Report templates associated with scheduling are not protected and can be modified. If this is the case, the task may fail or give inconsistent results. To purge alarms, parameters are available in the System directory: NMC > Server Name OmniVista 4760 > Servers > Server_name > Alarm server. To purge Accounting and Traffic analysis data, parameters are available in the System directory: NMC > Server_name OmniVista 4760 > Servers > Server_name > NMCDatabase. To purge Audit data, parameters are available in the System directory: NMC > Server Name OmniVista 4760 > Servers > Server_name > Audit server. 1.4 Jobs to Schedule after Installing the Server After installing the software programs, you must schedule two Maintenance jobs: 1. Set parameters for the Maintenance application according to your PC. See module Maintenance - Maintenance - Configuring Settings. 2. Schedule the execution of the two following tasks: Defragmentation of databases and Backup (save) of databases via the Maintenance application. 1.5 Execution Process Figure 1.2: Scheduling Execution Process On the date programmed for job execution, T1, the Scheduler simultaneously runs tasks A and B. When tasks A and B are complete, the Scheduler deals with task T2 and simultaneously runs tasks C and D. Options: Automatic repeats: You can define a number n of automatic repeats so as to be able to relaunch a task that failed. A timer can be used to set the time before each attempt. If failure is confirmed, an internal alarm is displayed in the Alarms application. Stop On Error: A condition for execution can be configured so that a job will only be performed if all tasks in the previous job are run successfully. If this option is selected on job T1, tasks C and D of job T2 must wait until tasks A and B have been correctly processed to be run. Delta between T1 and T2: This is a time-out before launching dependent jobs. In practice, the name of a job created under another job (T2) is specified automatically and cannot be modified. 1.6 Execution Reports 1-5

Chapter 1 1.6.1 Description of the Reports A copy of the structure of each job is placed at the same level of the tree structure. This copy is intended to collect job and task execution reports. When a job is complete (successful or not), a report is created and classified in chronological order. The role of the report is to record the essential steps of job execution and specify the location of the corresponding log file. A report contains the following data: - Status (this can be successful or failed). - The effective duration including any repetitions and delays. - Effective start date. - Effective end date. - The log file, giving the location of the execution report file on the server. 1.6.2 Viewing Reports To view a report: 1. Click the Status tab. 1-6

Figure 1.3: Scheduler Window Viewing Reports 1.6.3 Managing Reports Reports are created automatically. Old reports are regularly deleted by maintenance. Only job reports are manually deleted. This results in any reports on associated tasks being deleted. To delete reports: 1. Click the desired report(s) to select it (them). Select multiple reports using the Ctrl or Shift keys. 2. Select the Delete command from the shortcut menu. The selected report(s) is (are) removed from the list after confirmation. To print a report: 1. Click the report to select it. 2. Select the Print command from the shortcut menu in the editing area. The report is sent to the default printer. 1.7 Managing Scheduled Operations 1.7.1 Available Commands Jobs and tasks are managed via shortcut menus: 1. For a job: New Job: Adds a new blank inactive job to the tree. New task: Adds a task to the job. Execute Now: Executes a pending job immediately. Abort: Stops a job in the course of execution. Enable: Activates a selected inactive job. Disable: Deactivates a pending job. Delete: Deletes a job or task. Paste: Pastes a copy of a previously copied task into the tree structure. 2. For a task: Cut: Deletes a task for a subsequent move to another job. Copy: Copies a task for a subsequent copy to another job. Delete: Deletes a task. Refresh: Updates the display. 1.7.2 Common Operations To execute a programmed task immediately without it being necessary to reschedule it: 1. Select the desired job in the tree structure. 2. Open the shortcut menu by right-clicking, 3. Select Execute Now. The first tasks are run. 1-7

Chapter 1 When execution is complete, a report is created, then placed in the dedicated structure. To create a job, you can either create it directly via the Scheduler (see Available Commands ) or indirectly via one of the other OmniVista 4760 applications. In the latter case, two choices for creation are offered via the dialog box: - Simple job: 1. Check this option if you want to create a job that is neither dependent on nor included in another job. This is equivalent to creating a job with a single task. The programming, definition, retry, and status tabs are displayed in a dialog box. 2. Update the different tabs and apply your entries. - Synchronized task 1. Check this option if you want to include your task in a job (present or not present in the Scheduler). A dialog box with three tabs is displayed. 2. You can view programming of the various Scheduler tasks and jobs by using the shortcut menus. 3. If you want to include your new task in one of the jobs in the Scheduler, click it in the tree structure, then click Apply. The task is added. 4. If you want to include your new task in a job that has not yet been created: Select the parent job from which you want to create your job. Run the New Job command. A Properties window is displayed. Complete the window and confirm. The new job is displayed in the tree structure. Select the new job and complete the three tabs, then confirm. To deactivate a job: 1. Select the desired job in the tree structure. 2. Right-click to open the shortcut menu. 3. Select Disable, the task switches to idle. To activate a job: 1. Select the desired job in the tree structure. 2. Right-click to open the shortcut menu. 3. Select Enable: Start date is exceeded and the job is not to be repeated: the associated tasks switch to idle. Start date is compatible with current server time and with start delay: the first associated tasks switch to Running status. Start date is later than current server time (the maximum start delay is included): the associated tasks switch to Waiting status. To abort a running job: 1. Select the desired running job. 2. Right-click to open the shortcut menu. 3. Select Abort, the job switches to idle status as do associated tasks. 1-8

1.8 Scheduling Parameters A job can be reprogrammed at any time, provided that it is not running. Jobs and tasks have dedicated tabs: - Job. Scheduling, - Task Definition. - Subjob options (Options for depending jobs). - Task Retry Options. - Status. 1.8.1 Scheduling An execution interval can only be configured for a job via the Scheduling tab, that contains the following information: 1. A Description of the task shown in the Scheduler tree structure. 2. Maximum Start Delay. This is the maximum delay allowed to run a task that was not performed on the scheduled date. Example: the defragmentation scheduled for Saturday with a maximum delay of one day will not be performed if the PC is shut down on Friday and restarted on Monday. 3. The Start Date can be either Now or As Scheduled for a deferred launch. Specify a date on the calendar (accessed via ). 4. The Repeat interval is configured by various criteria, as desired. Example 1: Repetition: Weekly Every: 3 Week(s) The job is launched every 3 weeks, on the same day of the week as that of the first execution. Example 2: Repetition: Monthly Every: 1 Month(s) Date : Day: First Sunday The job is launched on the first Sunday of every month. Example 3: Repetition: Monthly Every: 1 Month(s) Date : Day: Last day The job is launched on the last day of every month. Leap years are included to ensure permanent execution. 5. An Ending Date if the job repetition interval is to be limited over time. Check the As Scheduled option, then use the calendar to specify the desired date and time. When 1-9

Chapter 1 the date limit is reached, the job automatically switches to idle state. 6. Exclude Days is to be completed if you do not want the task to be run on one or more specified days of the week. Check consistency between excluded days and repeated interval settings. If a start date coincides with an excluded day, it is automatically put back to the first authorized day. 1.8.2 Task Definition This tab is dedicated to advanced settings for experienced users. - Description: This field displays the name of the tasks listed in the tree structure. It must be completed. - Host Name: the name of the OmniVista 4760 server. - Service type: Service: Default value - select this option if the task is performed by an NMC service to be specified in the list located under the option. The Action field contains the command corresponding to the service. NMC Process: Select this option if the task is performed by an NMC process. Then enter the name of the process. You can also specify execution options in the Arguments field. External Process: Select this option if the job is performed by an NMC external process. Then, update the Executable and Arguments fields. To simplify use, scripts that open an MS-DOS window are not supported. However, pop-up messages can be sent with the net send command. Note: With some external processes like net send, to avoid display problems in case of accentuated characters in executives reports add "-oem_output" in the Executable field before the executable name. - Job Owner: Indicates task owner name. This parameter cannot be modified. 1.8.3 Retry Options - Number of retries: Specify the number of attempts for a job to be relaunched automatically after execution fails. - Time Between Retries:* Specify time between two attempts in number of days, hours, minutes and seconds. - Maximum execution time*: Enter an execution time limit so that you can control total job execution time. (*) These two parameters cannot be less than Scheduler configuration preferences (see Customizing the Scheduler ). 1.8.4 Subjob Options Delay dependent job start: Time for end of execution of current job before processing the next job. The specified time does not include the seconds. Stop On Error: Enable this option if you want a task to be aborted when one of its sub-tasks is executed incorrectly. By default, this option is enabled. 1-10

1.8.5 Status This tab presents status during job execution or the task currently selected in the tree structure. It also presents the name of the licensed application that the currently selected job in the tree structure depends on. 1.9 Copy a Task in Order to Customize It By combining Copy/Paste operations, you can customize a predefined task separately. Example of customization with alarm purge: 1. Create a job at the root of the tree structure and name it New purge. Confirm creation 2. In the predefined Daily job, cut the Purge alarms job, and paste it in New purge. 3. Schedule the New purge job according to your needs and confirm. 1.10 Customizing the Scheduler Reserved to experienced administrators. This interface is exclusively reserved to members of the Administrators group of the Scheduler application (module Security - Overview). To configure the Scheduler, some settings must be configured via the interface (accessed from the menu Preferences > Scheduler > Configuration). Scheduler Preferences: Scheduling Start Delay (sec.) : The NMC scheduler service is among the first services to be launched when the computer is started up. However, some NMC services that are liable to run jobs defined in the Scheduler require more time to start. Thus, it is necessary to postpone scanning for jobs to be run, in order to leave more time for these services to start. Execution report storage duration (duration to be kept): Parameter to be defined in terms of days and hours. This avoids saturating the hard drive with an increasing number of reports. Task preferences: Minimum repeat interval: To be defined in terms of days, hours, minutes, and seconds. This parameter sets a limit for the Time Between Retries field in the task retry options. Tasks with a time interval less than this parameter cannot be scheduled. Minimum "maximum duration": Parameter to be defined in terms of days, hours, and minutes. No task can be scheduled with a Maximum execution time lower than this value. Max No. of retries: Limits the maximum number of retries that can be scheduled for a task. Tasks with a number of retry attempts higher than this parameter cannot be scheduled. All these settings can be displayed (read-only) by clicking at the top of the tree structure. 1-11

Chapter 1 1-12