Symbols
A
- access privilege levels
- accounting
- applications
- description
- TACACS+, configuring
- admin permission
- admin-control permission
- all permission
- announcements at system login
- APIs (application programming interfaces)
- CORBA plug-in SPI
- CORBA remote API
- description
- SAE core API 1, 2
- application programming interfaces. See APIs
- architecture
- authentication 1, See also user accounts
- configuration example
- multiple methods
- RADIUS
- shared user accounts 1, 2
- TACACS+
- TACACS+, configuring
- TACACS+, configuring with C-Web interface
- TACACS+, configuring with SRC CLI
- template accounts
- authentication order
- configuring with C-Web interface
- configuring with SRC CLI 1, 2
- overview 1, 2
- removing authentication method
- removing authentication method with SRC CLI
B
C
- C Series Controller
- C Series Controllers
- C-Web interface
- committing a configuration
- configuration options
- configuring
- HTTP access 1, 2
- HTTPS access 1, 2
- logging properties
- copying an object
- deleting an object
- editing level
- elements
- getting Help
- icons
- layout
- loading configuration values
- logging out
- moving an object
- navigating
- overview 1, 2
- password, changing
- Policies, Services, and Subscribers
- renaming an object
- reverting a configuration
- starting
- updating configuration data
- username, changing
- C2000 Controller
- C3000 Controller
- C4000 Controller
- C5000 Controller
- clear permission
- cli
- client mode, NTP
- commands
- configuration statements
- configure permission
- control permission
- conventions
- customer support 1
- cweb-password
D
- date on system
- deployment scenarios
- DES (directory eventing system)
- differentiated QoS
- digital certificates. See security
- directory
- directory connection properties
- directory eventing system
- directory server
- documentation
- draft RFCs
- dynamic webpages
E
F
G
- Gigabit Ethernet interfaces, configuring IPv4
- Gigabit Ethernet interfaces, configuring IPv6
- GRE tunnel interfaces
- group interfaces, configuring 1
H
I
J
- Java Naming and Directory Interface. See JNDI
- java-heap-size, configuring
- JNDI (Java Naming and Directory Interface)
- Juniper Networks database
- adding Juniper Networks database to community
- changing modes
- community mode
- community mode configuration
- configuration example
- configuration statements
- configuring
- data recovery
- high availability
- loading sample data
- neighbors 1, 2
- overview 1, 2
- redundancy
- roles
- changing secondary to primary, SRC CLI
- overview 1, 2
- standalone mode
- verifying configuration
- Juniper-Allow-Commands attribute (RADIUS)
- Juniper-Allow-Configuration attribute (RADIUS)
- Juniper-Deny-Commands attribute (RADIUS)
- Juniper-Deny-Configuration attribute (RADIUS)
- Juniper-Local-User-Name attribute (RADIUS)
L
- LDAP (Lightweight Directory Access Protocol). See directory; directory server
- LDAP directory. See directory
- leases for licenses. See license server
- license
- license manager
- configuration statements
- configuring
- license server
- license usage
- Lightweight Directory Access Protocol. See LDAP
- load balancing
- local password authentication
- local properties
- logging, See also system log server
- login announcements, system
- login classes
- configuration
- configuration examples
- configuration prerequisites
- configuration statements
- configuration verification
- default classes
- idle timeout values
- options
- overview
- predefined
- privilege level options
- privilege levels
M
- maintenance permission
- manuals
- messages
- MII monitor
- configuring
- Monitoring Agent
- multicast
N
- NAS ID, configuring for SAE
- network
- network information collector. See NIC
- NIC (network information collector)
- notice icons
- NTP (Network Time Protocol)
- NTP,
O
- on-demand services 1, 2
- open interfaces
- operator login class
- operators, regular expression
- OSS integration
P
- passwords
- permissions
- policies
- Policies, Services, and Subscribers CLI. See SRC CLI
- Policies, Services, and Subscribers tasks. See C-Web interface
- policy management
- ports
- predefined login classes
- primary directory
- privilege levels 1
- product features 1, 2
R
- RADIUS
- RADIUS authentication. See authentication
- RADIUS authorization. See authentication
- read-only login class
- redundancy
- references
- regular expressions
- request license import file-name command
- reset permission
- residential portal
- resolving hostnames
- retrieving directory changes
- RFCs 1, 2, 3
- root account 1
- router running Junos OS
- router running JunosE Software
- routing permission
- routing-control permission
S
- SAE (service activation engine)
- configuring groups
- deleting default configurations
- SRC CLI 1, 2
- description 1, 2
- initial properties, overview
- starting
- stopping
- verifying status
- SAE (service activation engine), configuring initial properties
- SAE (service activation engine), configuring NAS ID
- SAE (service activation engine), configuring RADIUS address
- sample data
- secondary directory
- secret permission
- secret-control permission
- security
- digital certificates 1
- clearing certificates 1, 2
- clearing requests
- prerequisites
- requesting certificates 1, 2
- requesting certificates through SCEP
- viewing certificates
- security permission
- security-control permission
- server license. See license
- service activation engine. See SAE
- service permission
- service-control permission
- services
- shared user accounts
- shell permission
- SNMP agent
- access control, configuring on C Series Controllers
- community strings 1, 2
- named views
- SNMP groups
- VACM
- configuration statements 1, 2
- configuring
- description
- directory connection parameters, configuring
- Java Runtime Environment, configuring
- local properties, configuring
- logging, configuring
- monitoring
- named views, defining
- notification targets, configuring
- starting
- stopping
- system information, configuring
- trap history, configuring
- SNMP Agent
- snmp control permission
- snmp permission
- SNMP traps
- notification targets, configuring
- snmp-named-views-cli
- snmp-security-names-cli
- snmp-statements
- software standards
- SRC ACP (SRC Admission Control Plug-In)
- SRC CLI 1
- directory connections
- overview
- Policies, Services, and Subscribers CLI
- starting
- SRC components
- SRC software
- configuration prerequisites
- configuring
- creating, virtualized instance 1
- description
- features and benefits 1, 2
- financial advantages
- OSS integration
- recovering
- services
- snapshot on C Series Controller
- upgrading
- USB Storage Device
- virtualization
- virtualization, requirement
- SSH (secure shell)
- standards 1
- static host mapping
- static routes, configuring
- Steel-Belted Radius/SPE server 1, 2
- subscriber
- subscriber permission
- subscriber-control permission
- superuser login class
- support, technical See technical support
- symmetric active mode, NTP
- system authentication. See authentication
- system log server
- configuration prerequisites
- configuration statements
- message groups
- message severity levels
- messages
- messages, file
- messages, server
- messages, user notification
- overview
- system login
- system permission
- system-control permission
T
- TACACS+ authentication. See authentication
- tariff models
- technical support
- Telnet connection to remote host
- template authentication accounts
- text conventions defined
- third-party URLs
- tunnel interfaces
- tunnel interfaces, configuring
U
- UIDs
- unauthorized login class
- unresponsive directories
- usage data
- user accounts 1, See also login classes
- authentication
- configuring passwords
- configuring SSH authentication
- root password 1, 2
- authentication method and password
- configuration
- configuration verification 1, 2
- example
- overview 1, 2, 3
- shared
- user notification messages
V
W
- Web application server
- application deployment 1, 2
- channel stack
- configuration statements
- configuring the Web application server
- installing Web applications inside
- local properties
- multicast-address
- node-id
- overview
- removing Web applications from
- restarting
- shared cluster name
- shared cluster nodes
- shared cluster properties
- starting
- stopping
- viewing cluster history
- viewing cluster status
- viewing statistics
- Web Services Gateway
Download This Guide
Related Documentation
- SRC Script Services Overview
- SRC CLI Overview
Configuring a Schedule for Executing the Commands or Scripts (SRC CLI)
To periodically execute the SRC CLI commands or scripts according to a given schedule, use the system schedule schedule-name command. You can use the redirection operator (>) with the commands or scripts to redirect the command execution output to a file.
Use the following statements to schedule a repetitive task on an SRC system:
To periodically execute the commands or scripts according to a given schedule:
- In configuration mode, enter the name of the schedule
that is capable of adding schedule entries for the executable scripts
or commands. A schedule name can contain alphanumeric characters only.
In this sample procedure, src1cron is the
name of the schedule.[edit]user@host# edit system schedule src1cron
- (Optional) Enter the day of the week on which you want
the command or script sequence to execute. The default value is *
(asterisk).[edit system schedule src1cron]user@host# set day-of-week day-of-week
- (Optional) Enter the month of the year in which you want
the command or script sequence to execute. The default value is *
(asterisk).[edit system schedule src1cron]user@host# set month month
- (Optional) Enter the day of the month on which you want
the command or script sequence to execute. The default value is *
(asterisk).[edit system schedule src1cron]user@host# set day-of-month day-of-month
- (Optional) Enter the hour of the day at which you want
the command or script sequence to execute. The default value is *
(asterisk).[edit system schedule src1cron]user@host# set hour hour
- (Optional) Enter the minute at which you want the command
or script sequence to execute. The default value is * (asterisk).[edit system schedule src1cron]user@host# set minute minute
Table 8 lists the values allowed for the periodic strings (such as day-of-week, month, day-of-month, hour, and minute).
Table 8: Values Allowed for the Periodic Strings
Options
Values
day-of-week
0-7 (where both 0 and 7 mean Sunday) or SUN-SAT
month
1-12 or JAN-DEC
day-of-month
1-31
hour
0-23
minute
0-59
You can use multiple combinations of the special characters described in Table 9.
Table 9: Available Special Characters
Special Characters
Meaning
*
Indicates all values.
For example, to execute the command or script every hour:
user@host# set hour *
/
Indicates the increments of ranges.
For example, to execute the command or script at the third minute of the hour and every 15 minutes thereafter:
user@host# set minute 3-59/15
,
Indicates to separate the values of a list.
For example, to execute the command or script on Mondays, Wednesdays and Fridays:
user@host# day of week MON,WED,FRI
-
Indicates the ranges.
For example, to execute the command or script every hour from 3 through 10:
user@host# set hour 3-10
- (Optional) Enter the special string values such as reboot, yearly, annually, monthly, weekly, daily, midnight, and hourly at which you want the command or script sequence to
execute.
For example, to execute the command or script at midnight on the first day of each month:
[edit system schedule src1cron]user@host# set special-string monthly
Note: If you configure both special string values and periodic string values (such as day-of-week, month, day-of-month, hour, or minute options), a message indicating that both special strings and periodic strings cannot be defined is displayed when you commit the changes.
Table 10 lists the special string options.
Table 10: Special String Options
Options
Description
reboot
Executes the command or script at boot and reboot of the system.
yearly
Executes the command or script at midnight, January 1 each year.
annually
Executes the command or script at midnight, January 1 each year.
monthly
Executes the command or script at midnight on the first day of each month.
weekly
Executes the command or script at midnight each Sunday.
daily
Executes the command or script at midnight each day.
midnight
Executes the command or script at midnight each day.
hourly
Executes the command or script at on the first second of every hour.
- Configure the complete path of the script to be executed
for the schedule.
Note: The script and command options are mutually exclusive. You cannot configure both options at the same time.
[edit system schedule src1cron]user@host# set script scriptNote: The CLI editing level must be set to expert by using the set cli level expert command for this option.
- Configure the CLI command to be executed for the schedule.
Note:
- The script and command options are mutually exclusive. You cannot configure both options at the same time.
Before you configure a CLI command for the schedule, perform the following steps to make sure that you can configure the CLI command as part of the schedule execution:
- Enter the CLI command in the shell with the cli –c “command name” option.
- Verify whether the CLI command returns the expected output.
[edit system schedule src1cron]user@host# set command command - (Optional) Verify your configuration.user@host# show src1cron {command show;day-of-month 7;day-of-week 5; hour 11;minute 0; month 12;}
Related Documentation
- SRC Script Services Overview
- SRC CLI Overview
