Planning Service Schedules
Before you configure service schedules, carefully plan individual rules for the schedule to avoid conflicts between the rules. The rules become entries when you configure the schedule. The SAE evaluates each schedule entry independently of the others.
Schedule Configuration Guidelines
Use the following guidelines when you plan and configure service schedules:
- Do not configure schedules for services that are configured as persistent services on the router.
- If activate-on-login is configured for a subscription, do not configure an effective period in a schedule for the associated service.
Consider changing the configuration for this subscription to use an effective period, rather than activate-on-login.
- Make sure you know the values for preparation time and action threshold that have been configured for the SAE.
- Do not configure an effective period to overlap with an excluded time.
- To avoid schedule conflicts, configure one service schedule to include all rules that control a service.
- Determine whether or not a service to be scheduled has an authorization plug-in configured. If an authorization plug-in is configured for a service, you can create an authorization schedule for that service.
- Create a schedule for a service under one of the following:
- The subscriber tree (for example, o=Users)
- The global service configuration (for example, o=Services)
- A defined service scope (for example, o=Scopes)
- Do not specify the time in a schedule entry that is more than 5 years in the past or 15 years in the future.
Planning Schedules
The following list of planning activities applies to both event-based and authorization schedules unless otherwise indicated.
- Decide whether to configure the schedule for a group of subscribers. Configure a schedule that includes rules for the same service under only one of the following:
- For each rule in a service schedule, list the following information for each service included in the schedule:
- Time to activate the service and any effective time associated with this action.
- Time to deactivate the service.
(Optional for authorization schedules) Time to deny or to deny and deactivate the service.
Times can include a date and day of the week.
- (Event-based schedules) Make sure that the scheduled times take into consideration a preparation time or an action threshold that has been configured for the SAE.
For example, if a schedule entry activates a service at 8:00, a schedule entry to deny access to the service should have a time before 8:00, such as 7:59. If a preparation time of 15 minutes is configured for the SAE, a schedule entry to deny access to the service should have a time before 7:45. The deny period ends before the service can be activated, with the time between the end of the deny interval and the activation time greater than the preparation time.