Exec > ACS Configuration > Timedef Configuration
Entering the above command sequence results in the following prompt:
Use this command to create timeslots in a timedef during which rules
have to be active. Timedefs enable activation/deactivation of
ruledefs/groups-of-ruledefs such that they are available for rule matching only
when they are active.
When a packet is received, and a ruledef/group-of-ruledefs is eligible
for rule matching, if a timedef is associated with the
ruledef/group-of-ruledefs, before rule matching, the packet-arrival time is
compared with the timeslots configured in the timedef. If the packet arrived in
any of the timeslots configured in the associated timedef, rule matching is
undertaken, else the next ruledef/group-of-ruledefs is considered.
The time considered for timedef matching is the system's local time.
This release does not support configuring a timeslot for a specific
If in a timeslot, only the time is specified that timeslot will be
applicable for all days.
If for a timeslot "start time" is after "end time", that rule will
span midnight and be considered to be active from the current day until the
If for a timeslot, "start day" is after "end day", that rule will span
the current week until the end day in the next week.
In the following cases a rule will be active all the time:
A timedef is not configured in an action priority
A timedef is configured in an action priority, but the named
timedef is not defined
A timedef is defined but without timeslots