Configuring Policy Schedules (Nsm Procedure) - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SCREENOS DEVICES GUIDE REV 01 Manual
Configuring screenos devices guide
Hide thumbs
Also See for NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SCREENOS DEVICES GUIDE REV 01:
- Manual (340 pages) ,
- Administration manual (1026 pages) ,
- Installation manual (244 pages)
Table of Contents
Advertisement
Configuring ScreenOS Devices Guide
Related
Documentation
Configuring Policy Schedules (NSM Procedure)
Related
Documentation
114
Table 29: Session Closings (continued)
ALG
NSRP
AUTH
OTHER
Configuring Policy Schedules (NSM Procedure) on page 114
Configuring Timeouts for Predefined Services (NSM Procedure) on page 115
Example: Defining Forced Timeout (NSM Procedure) on page 112
By associating a schedule to a policy, you can determine when the policy is in effect. You
can configure schedules on a recurring basis and as a one-time event. Schedules provide
a powerful tool in controlling the flow of network traffic and in enforcing network security.
For an example of the latter, if you were concerned about employees transmitting
important data outside the company, you might set a policy that blocked outbound
FTP-Put and MAIL traffic after normal business hours.
NOTE: In the Web UI, scheduled policies appear with a gray background to
indicate that the current time is not within the defined schedule. When a
scheduled policy becomes active, it appears with a white background.
To configure a policy schedule:
In the NSM navigation tree, select Object Manager>Schedule Objects.
1.
Click New and fill in the schedule form.
2.
Click OK to save the schedule.
3.
You can attach a schedule to a policy as you create the policy, or you can bind the schedule
later in the Web UI. For more information on policies and schedules, see the Network and
Security Manager Administration Guide and the Concepts & Examples ScreenOS Reference
Guide.
Configuring Timeouts for Predefined Services (NSM Procedure) on page 115
Configuring Session Cache for Predefined Services (NSM Procedure) on page 115
Identifying Reasons for Session Close in NSM on page 113
ALG forced session close either because of error or other reasons
specific to that ALG.
NSRP session close message received.
Session closed because of authentication failure.
Reason for close not identified.
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
