Administrator Guide

Switch Management Commands 2291
• time—The first occurrence of this argument is the starting
hours:minutes which the configuration that referenced the time range
starts going into effect. The second occurrence is the ending
hours:minutes at which the configuration that referenced the time range
is no longer in effect.
The hours:minutes are expressed in a 24-hour clock. For example, 8:00 is
8:00 am and 20:00 is 8:00 pm.
Default Configuration
This command has no default configuration.
Command Mode
Time Range Configuration
User Guidelines
Multiple periodic entries can exist in a time range, but periodic time entries
cannot overlap each other. Periodic time entries can also coexist with an
absolute time entry in a time range.
When both periodic and absolute time entries are specified within a time
range, the periodic time entries limit the time range to only those times
specified within the periodic time range and bounded by the absolute time
range. In this case, the absolute time entry specifies the absolute start and
end dates/times and the periodic entries specify the start/stop times within
the limits of the absolute time entry dates and times.
If a periodic time entry is added to an active time-range with an existing
absolute time entry, the absolute time entry immediately becomes inactive.
For example, an administrator applies a absolute time-range configured for a
week's work hours (08/09-08/13 9am to 6pm) and later adds multiple periodic
entries for same days configured individually (Monday, Tuesday, Wednesday,
Thursday, Friday) but with after-work hours (9pm to 11pm). The
administrator wants to permit/deny HTTP traffic for this time-range, but the
entire time-range is invalid due to conflicting entries. The absolute entry is
forced to inactive because the periodic entry time is not yet in effect.
Examples
console#time-range timeRange_2
console(config-time-range)#periodic monday 00:00 to tuesday 12:30