ZyXEL Communications P-660R-Tx v2 Series Support Notes page 59

wan callsch index
(Set call schedule index #= 1. You must apply this command first before you
begin to configure call schedule)
wan callsch name
(Set the schedule name as Test)
wan callsch active
(Enable schedule)
wan callsch startdate
(Set schedule start date as 2005-12-27)
wan callsch oncedate
(Set the schedule used just once, it works on 2005-12-27)
wan callsch starttime
(Set the schedule start time as 12:00)
wan callsch duration
(Set schedule duration time as 16 hours)
wan callsch action
(Set action as dial-on-demand)
wan callsch save
(Save the current call schedule set)
Key Settings:
Start date of this schedule rule. It can be unmatched with weekday
Start Date setting. For example, if Start Date is 2000/10/02(Monday), but Monday
setting in weekday can be No.
The node will always keep up during the setting period. It is equivalent
Forced On
to diable the idel timeout.
The node will always keep doen during the setting period. The
Forced Down
connected remote node will be dropped.
Enable
The remote node accepts Dial-on-demand during this period.
Dial-On-Demand
The remote node denies any demand dial during the period. For the
Disable
existing connected nodes, it will be dropped after idle timeout and no
Dial-On-Demand
triggered up.
Start Time/
Start Time and Duration of this schedule
Duration
•
Apply the schedule to the Remote node
Multiple scheduling rules can program in a Remote node, and they have
priority. For example, if we program the sets as 1,2,3,4 in remote node, then
the set 1 will override set 2,3,4. set 2 will override 3,4, and so on.
We can apply the schedule to the remote node in CLI by the commands:
wan node index []index#]
All contents copyright © 2006 ZyXEL Communications Corporation.
1
Test
Yes
2005 12 27
2005 12 27
12 00
16 00
2
P-660R-Tx v2 Series Support Notes
.
59