Time Ranges

You can use time ranges to control when an ACL rule is in effect. For example, if the device determines that a particular ACL applies to traffic arriving on an interface, and a rule in the ACL uses a time range that is not in effect, the device does not compare the traffic to that rule. The device evaluates time ranges based on its clock.

A time range contains one or more rules. The two types of rules are as follows:

Absolute
Periodic

Diagram

Classes

route_control (vxlan.overlay_extensions)

Name	Type	Constraint	Mandatory	Default Value
time_range	List	`[time_range]`	No

time_range (vxlan.overlay_extensions.route_control)

Name	Type	Constraint	Mandatory	Default Value
name	String		Yes
entries	List	`[entries]`	No

entries (vxlan.overlay_extensions.route_control.time_range)

Name	Type	Constraint	Mandatory
seq_number	Integer	min: `1`, max: `4294967295`	Yes
periodic	Class	`[periodic]`	No
absolute	Class	`[absolute]`	No
remark	String		No

periodic (vxlan.overlay_extensions.route_control.time_range.entries)

Name	Type	Constraint	Mandatory
day	List	Choice[`Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, `Saturday`, `Sunday`, `daily`, `weekdays`, `weekend`]	Yes
start_hours	Integer	min: `0`, max: `24`	Yes
start_minutes	Integer	min: `0`, max: `59`	No
start_seconds	Integer	min: `0`, max: `59`	No
end_hours	Integer	min: `0`, max: `24`	Yes
end_minutes	Integer	min: `0`, max: `59`	No
end_seconds	Integer	min: `0`, max: `59`	No

periodic (vxlan.overlay_extensions.route_control.time_range.entries)

Name	Type	Constraint	Mandatory
day	List	Choice[`Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, `Saturday`, `Sunday`, `daily`, `weekdays`, `weekend`]	Yes
start_hours	Integer	min: `0`, max: `24`	Yes
start_minutes	Integer	min: `0`, max: `59`	No
start_seconds	Integer	mint: `0`, max: `59`	No
end_hours	Integer	mint: `0`, max: `24`	Yes
end_minutes	Integer	mint: `0`, max: `59`	No
end_seconds	Integer	mint: `0`, max: `59`	No

absolute (vxlan.overlay_extensions.route_control.time_range.entries)

Name	Type	Constraint	Mandatory
start_day	Integer	min: `1`, max: `31`	No
start_month	Choice	`January`, `February`, `March`, `April`, `May`, `June`, `July`, `August`, `September`, `October`, `November`, `December`	No
start_year	Integer	min: `2000`, max: `2037`	No
end_day	Integer	min: `1`, max: `31`	No
end_month	Choice	`January`, `February`, `March`, `April`, `May`, `June`, `July`, `August`, `September`, `October`, `November`, `December`	No
end_year	Integer	min: `2000`, max: `2037`	No
start_hours	Integer	min: `0`, max: `24`	No
start_minutes	Integer	min: `0`, max: `59`	No
start_seconds	Integer	min: `0`, max: `59`	No
end_hours	Integer	min: `0`, max: `24`	No
end_minutes	Integer	min: `0`, max: `59`	No
end_seconds	Integer	min: `0`, max: `59`	No

absolute (vxlan.overlay_extensions.route_control.time_range.entries)

Name	Type	Constraint	Mandatory
start_day	Integer	min: `1`, max: `31`	No
start_month	Choice	`January`, `February`, `March`, `April`, `May`, `June`, `July`, `August`, `September`, `October`, `November`, `December`	No
start_year	Integer	min: `2000`, max: `2037`	No
end_day	Integer	min: `1`, max: `31`	No
end_month	Choice	`January`, `February`, `March`, `April`, `May`, `June`, `July`, `August`, `September`, `October`, `November`, `December`	No
end_year	Integer	min: `2000`, max: `2037`	No
start_hours	Integer	min: `0`, max: `24`	No
start_minutes	Integer	min: `0`, max: `59`	No
start_seconds	Integer	mint: `0`, max: `59`	No
end_hours	Integer	mint: `0`, max: `24`	No
end_minutes	Integer	mint: `0`, max: `59`	No
end_seconds	Integer	mint: `0`, max: `59`	No

Examples

Example-1

This example will create a time-range named: workday-daytime. There is a description: workday at the entry 10. At the entry 20, we configure a periodic time-range for weekdays from 00:00:00 to 23:59:59.

This time-range is used in group named TimeRange_RCtrlGrp, which is consumed by switch named: netascode-leaf1.

switch(config)# time-range workday-daytime
switch(config-time-range)# 10 remark workday
switch(config-time-range)# 20 periodic weekdays 00:00:00 to 23:59:59

---
vxlan:
  overlay_extensions:
    route_control:
      time_range:
        - name: workday-daytime
          entries:
            - seq_number: 10
              remark: 'workday'
            - seq_number: 20
              periodic:
                day:
                  - weekdays
                start_hours: 00
                start_minutes: 00
                end_hours: 23
                end_minutes: 59
                end_seconds: 59
      groups:
        - name: TimeRange_RCtrlGrp
          time_range:
            - name: workday-daytime
      switches:
        - name: netascode-leaf1
          groups:
            - TimeRange_RCtrlGrp

Example-2

This example will create a time-range named: independance-day. At the entry 10, we configure a absolute time-range from the July 4, 00:00:00 to July 4, 23:59:59.

This time-range is used in group named TimeRange_RCtrlGrp, which is consumed by switch named: netascode-leaf1.

switch(config)# time-range independance-day
switch(config-time-range)#10 absolute start 00:00 4 July 2024 absolute end 23:59:59 4 July 2024

---
vxlan:
  overlay_extensions:
    route_control:
      time_range:
        - name: independance-day
          entries:
            - seq_number: 10
              absolute:
                start_day: 4
                start_month: July
                start_year: 2024
                start_hours: 00
                start_minutes: 00
                start_seconds: 00
                end_day: 4
                end_month: July
                end_year: 2024
                end_hours: 23
                end_minutes: 59
                end_seconds: 59
      groups:
        - name: TimeRange_RCtrlGrp
          time_range:
            - name: independance-day
      switches:
        - name: netascode-leaf1
          groups:
            - TimeRange_RCtrlGrp