Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
A
- access policy, examples 1
- action threshold, service schedules
- actions. See policy actions
- aggregate services 1
- adding
- before you configure
- fragment services
- infrastructure services
- mandatory services
- Python expressions
- redundancy
- sessions 1
- timers, configuring
- apply-groups statement, routers running Junos OS
C
- captive portal
- using with next-hop action
- classify-traffic condition 1
- application protocol
- application, setting
- application-group, setting
- configuring
- destination grouped network, configuring
- destination network, configuring
- expanded classifiers 1
- extended classifiers 1
- ICMP conditions, setting
- IGMP conditions, setting
- IPSec conditions, setting
- Junos OS filter conditions, setting
- JunosE secondary input policy conditions, setting
- match direction, setting
- multiple classifiers
- packet length, setting
- PCMM I02 and I03 1
- port definitions, overview
- protocol conditions with parameters, setting
- protocol conditions with ports, setting
- protocol conditions, setting
- route class, configuring
- source grouped network, configuring
- source network, setting
- TCP conditions, setting
- term-precedence, setting
- ToS byte conditions, setting
- color actions 1
- configuring
- color mark actions 1, 2
- controlled load service, FlowSpec
- conventions
- CoS (class of service)
- ToS byte, setting
- customer support 1
D
- Data-over-Cable Service Interface Specifications. See DOCSIS
- default policies
- example
- DHCP (Dynamic Host Configuration Protocol)
- access policy example
- Differentiated Services code point, ToS byte
- DOCSIS policy actions 1
- configuring
- documentation
- drop profile maps
- DSCP (Differentiated Services code point), ToS byte
E
- effective period, service schedules
- exclusions to service schedule 1
- defining
- expanded classifiers 1
- configuring
- expressions
- map, application protocol conditions
- parameter definitions
- extended classifiers, PCMM 1
- configuring
- external parent groups
- external parent groups,
- aggregate rate-limit
- configuration statements
- for JunosE policies
- hierarchical policy parameter
- JunosE
- rate-limit profiles
F
G
- gates, PCMM
- gateSpec actions 1
- configuring
- global parameters 1
- guaranteed service, FlowSpec
H
I
J
- Junos OS ASP policy rules 1
- Junos OS filter policy rules 1
- conditions, setting
- Junos OS policer policy rules 1
- policer actions 1
- Junos OS port mirror policy rules
- Junos OS scheduler policy rules 1, 2, See also drop profile maps
- actions 1
- QoS conditions, configuring
- Junos OS shaping policy rules
- JunosE IPv6 policy rules
- JunosE secondary input policy rules
- conditions, setting
L
M
- manuals
- map expressions
- application protocol conditions
- substitutions
- mark actions 1
- configuring
- multiple classifiers, policies
- multitask
- mutex group 1
- adding
N
- NAT (Network Address Translation) policies
- actions 1
- application protocol condition
- next-hop actions 1
- next-interface actions 1
- configuring
- next-rule actions 1
- configuring
- non-real-time polling service.
- notice icons
- NRTPS (non-real-time polling service)
O
P
- packet loss priority. See loss priority actions
- PacketCable Multimedia Specifications. See PCMM
- parameter names
- parameter value acquisition 1, 2, See also substitutions
- parameter values, setting in services
- parameters 1, See also substitutions
- defining
- definition
- fixing
- global. See global parameters
- local. See local parameters
- ranking sources
- runtime. See runtime parameters
- types
- parent groups 1, 2, 3, 4, 5
- PCMM policies
- classifiers
- client type 1 support
- conditions and actions supported
- DOCSIS parameters 1
- extended classifiers 1
- FlowSpec parameters
- gate
- gateSpec parameters, configuring
- I02 and I03 classifiers
- marking packets
- proxied QoS with policy push
- service class name
- service flow scheduling types
- SessionClassId
- traffic profiles
- permanent service 1
- configuring
- plug-ins
- policer actions 1
- configuring
- policies
- policing policies
- example
- policy actions 1
- color 1
- color mark 1, 2
- combining
- configuring
- DOCSIS 1
- dynamic profiles
- filter 1
- FlowSpec 1
- forward 1
- forwarding class 1
- gateSpec 1
- loss priority 1
- mark 1
- NAT 1
- next hop 1
- next interface 1
- next rule 1
- policer 1
- policy rules supported
- QoS profile attachment 1
- rate limit 1
- rate limit hierarchy
- rate limit types
- rate-limit hierarchy
- reject 1
- routing instance 1
- scheduler 1
- service class name 1
- stateful firewall 1
- template activation
- traffic class 1
- traffic mirror 1
- traffic-shape 1
- types
- user packet class 1
- policy components 1
- policy conditions 1, 2, See also classify-traffic condition
- policy engine
- policy examples
- policy folders 1
- configuring
- policy groups 1
- configuring
- policy lists 1
- configuring
- policy management
- policy objects
- policy overview
- actions. See policy actions
- conditions. See classify-traffic condition\
- policy object organization
- policy repository, description
- policy rules 1
- actions supported
- conditions supported
- configuring
- Junos Adaptive Services PIC (ASP). See Junos OS ASP policy rules
- Junos OS filter. See Junos OS filter policy rules
- Junos OS policer. See Junos OS policer policy rules
- Junos OS scheduler. See Junos OS scheduler policy rules
- Junos OS shaping. See Junos OS shaping policy rules
- precedence
- types
- PPP
- access policy example
- precedence
- policy rules
- premium service, example
- preparation time, service schedules
- proxied QoS with policy push
Q
R
- rate-limit actions 1
- rate-limit hierarchy actions
- rate-limit type actions
- configuring
- rate-limiting, with multiple classifiers
- real-time polling service. See RTPS
- reject actions 1
- configuring
- routers running Junos OS
- policy features
- routing instance actions 1
- configuring
- RTPS (real-time polling service) 1
- runtime parameters
S
- scheduleAuth plug-in
- scheduler actions 1, 2, See also drop profile maps
- configuring
- scopes. See service scopes
- script services 1
- service
- 3gpp attributes (Gx router driver)
- Gx service attributes
- service class name actions 1
- configuring
- service flow scheduling types
- service schedules
- action threshold, setting
- authorization schedules, configuring
- configuring
- examples
- exclusions, defining
- guidelines
- overview 1
- planning
- preparation time, setting
- weekly-recur-freq
- service scopes 1, 2
- service-mgm-schedules-nonwork
- services
- activate-only
- adding aggregate
- adding infrastructure
- adding normal
- adding script services
- aggregate. See aggregate services
- assigning to service scopes
- automatic activation
- infrastructure. See infrastructure services
- mutually exclusive
- overview
- premium service example
- restricting availability
- restricting simultaneous activation
- script. See script services
- setting parameter values
- tiered Internet example
- SessionClassId, PCMM policies
- shaping rate. See traffic shaping
- stateful firewall policies
- actions 1
- application protocol conditions
- substitutions 1, See also parameters
- support, technical See technical support
T
- technical support
- template activation actions
- configuring
- text conventions defined
- tiered Internet service, example
- traffic mirror actions 1
- configuring
- traffic profiles, PCMM policies
- traffic shape actions
- configuring
- traffic shaping
- traffic-class actions 1
- configuring
- traffic-shape actions
U
V
- validating
- value acquisition for parameters
Download This Guide
Example: Configuring a Service to Be Active During Nonwork Hours (SRC CLI)
This example shows how to configure a schedule for an Internet gold service to be active:
- Monday–Friday outside the 8:30 AM to 4:30 PM work day
- January 1of the following year—All day
The example uses the Internet-GoldAuth service. This service is based on the Internet-Gold service in the sample data with the addition of the scheduleAuth plug-in defined as the authorization plug-in for the service.
The sample schedule:
- Deactivates the Internet-GoldAuth service from 8:30 AM through 4:29 PM.
- Activates the service at 4:30 PM.
- Does not have a preparation time configured for the SAE.
This configuration avoids schedule overlap.
For demonstration purposes, the sample schedule is configured in the global configuration to make the service schedule available to all subscribers to the Internet-GoldAuth service.
To configure a schedule to make a service available outside work hours and on January 1:
- From configuration mode, access the configuration statement
that configures the service configuration named Internet-GoldAuth
in the global configuration. Specify the default schedule authorization
plug-in. user@host# edit services global service Internet-GoldAuth [edit services global service Internet-GoldAuth] user@host# set authorization-plug-in scheduleAuth
- From configuration mode, access the configuration statement
that configures the service schedule. Enter a unique name for the
service schedule; for example, afterHours. user@host# edit services global schedule afterHours
Enter a description for the schedule.
[edit services global schedule afterHours] user@host# set description description - From configuration mode, access the configuration statement
that configures the schedule entry. Enter a name for the schedule
entry; for example, goldTime. user@host# edit services global schedule afterHours event goldTime
- From configuration mode, access the configuration statement
that configures the time schedule. For the time, specify the day of
the week as Monday through Friday, and specify that the schedule start
at 8:30 AM and end at 4:29 PM (16:29) each day. user@host# edit services global schedule afterHours event goldTime from [edit services global schedule afterHours event goldTime from] user@host# set day-of-week 1 user@host# set hour 8 user@host# set minute 30 user@host# edit services global schedule afterHours event goldTime to [edit services global schedule afterHours event goldTime to] user@host# set day-of-week 5 user@host# set hour 16 user@host# set minute 29
- From configuration mode, access the configuration statement
that configures the exclusion. Enter a name for the exclusion; for
example, exclude-1. Specify a one-time exclusion for January 1. user@host# edit services global schedule afterHours event goldTime except exclude-1 from [edit services global schedule afterHours event goldTime except exclude-1 from] user@host# set month 1 user@host# set day-of-month 1
By excluding January 1 from the schedule, the Internet-GoldAuth service is active all day.
- From configuration mode, access the configuration statement
that configures the action. Enter a name for the action; for example,
action-1. Specify deny-deactivate for the
Internet-GoldAuth service. user@host# edit services global schedule afterHours event goldTime action action-1 [edit services global schedule afterHours event goldTime action action-1] user@host# set type deny-deactivate user@host# set service Internet-GoldAuth
- From configuration mode, access the configuration statement
that configures the schedule entry. Enter a name for the schedule
entry; for example, goldTime2. user@host# edit services global schedule afterHours event goldTime2
- From configuration mode, access the configuration statement
that configures the time schedule. Specify 4:30 PM (that is, 16:30). user@host# edit services global schedule afterHours event goldTime2 from [edit services global schedule afterHours event goldTime2 from] user@host# set hour 16 user@host# set minute 30
- From configuration mode, access the configuration statement
that configures the exclusion. Enter a name for the exclusion; for
example, exclude-2. Specify a one-time exclusion for January 1. user@host# edit services global schedule afterHours event goldTime2 except exclude-2 from [edit services global schedule afterHours event goldTime2 except exclude-2 from] user@host# set month 1 user@host# set day-of-month 1
By excluding January 1 from the schedule, the Internet-GoldAuth service is active all day.
- From configuration mode, access the configuration statement
that configures the action. Enter a name for the action; for example,
action-2. Specify activate for the Internet-GoldAuth
service. user@host# edit services global schedule afterHours event goldTime2 action action-2 [edit services global schedule afterHours event goldTime2 action action-2] user@host# set type activate user@host# set service Internet-GoldAuth
Related Documentation
- Adding a Service Schedule (SRC CLI)
- Example: Configuring Different Service Tiers for Different Days (SRC CLI)
- Example: Configuring a Service to Be Available for a Specified Interval (SRC CLI)
