Cisco Cisco ASR 5700
ACS Timedef Configuration Mode Commands
start ▀
Command Line Interface Reference, StarOS Release 17 ▄
1251
In specifying the start/end time:
hh
: Specifies the start/end hour, and must be an integer from 0 through 23.
mm
: Specifies the start/end minute, and must be an integer from 0 through 59.
ss
: Specifies the start/end second, and must be an integer from 0 through 59.
Usage
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.
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.
Important:
The time considered for timedef matching is the system’s local time.
This release does not support configuring a timeslot for a specific date.
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 next day.
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:
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 next day.
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
Example
The following command specifies a timeslot that starts on
Tuesday
at
09:00:00
and ends on
Friday
at
21:30:00
:
start day tuesday time 9 0 0 end day friday time 21 30 0
The following command specifies a timeslot that starts at
15:00:00
and ends at
17:00:00
on all days of the
week:
start time 15 0 0 end time 17 0 0
The following command specifies a timeslot that starts on
Friday
at
22:00:00
and ends on
Tuesday
at
08:00:00
. This timeslot spans the complete week until the end day, up to
Tuesday
.
start day friday time 22 0 0 end day tuesday time 8 0 0
The following command specifies a timeslot that starts at
16:00:00
and ends at
09:00:00
on all days of the
week. Also, as start time > end time, this timeslot spans midnight too (that is, from
16:00:00
to
23:59:59
and from
00:00:00
to
09:00:00
).
start time 16 0 0 end time 9 0 0