Identifying Reasons For Session Close In Nsm - 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
Related
Documentation
Identifying Reasons for Session Close in NSM
Copyright © 2010, Juniper Networks, Inc.
In the following example, if you change the authentication idle timeout value from the
default (10 minutes) to 30 minutes and the RADIUS retry timeout from 3 seconds to 4
seconds, the session could theoretically remain open indefinitely (as long as one keystroke
is sent every 30 minutes). You can limit total session time by setting forced-timeout to
60 minutes. With this setting, after one hour the authentnication table entry for the user
is removed, as are all associated sessions for the authentication table entry, and the user
needs to reauthenticate.
NOTE: For detailed information on changing authentication server settings,
see Concepts & Examples ScreenOS Reference Guide.
To define forced timeout:
In the NSM navigation tree, select Device Manager>Security Devices.
1.
Select a security device and then double-click the device on which you want to define
2.
forced timeout. The device configuration appears.
In the device navigation tree, select Auth>Default Servers.
3.
Specfiy a valid range in minutes for the Local Auth Server Timeout.
4.
Specify a valid range in minutes for the Local Auth Server Forced Timeout.
5.
Click OK to apply your settings.
6.
Identifying Reasons for Session Close in NSM on page 113
Configuring Policy Schedules (NSM Procedure) on page 114
Configuring Advanced Device Settings Overview on page 112
NSM supports the log reason for the session close feature. NSM displays the reason for
session close so that you can differentiate session creation messages from session close
messages. If you do not want the reason to display, you can explicitly configure the device
not to display the field. Table 29 on page 113 lists the reasons for session close that NSM
identifies. Any session that cannot be identified is labeled OTHER.
Table 29: Session Closings
TCP FIN
TCP RST
RESP
ICMP
AGE OUT
TCP connection torn down because of FIN packet.
TCP connection torn down because of RST packet.
Special sessions, such as PING and DNS, close when response is
received.
ICMP error received.
Connection aged out normally.
Chapter 4: Advanced Network Settings
113
Advertisement
Table of Contents
