- Table of Contents
-
- 07-System
- 01-High availability group
- 02-VRRP
- 03-Track
- 04-BFD
- 05-NQA
- 06-Basic log settings
- 07-Session log settings
- 08-NAT log settings
- 09-AFT log settings
- 10-Threat log settings
- 11-Application audit log settings
- 12-NetShare log settings
- 13-URL filtering log settings
- 14-Attack defense log settings
- 15-Bandwidth alarm logs
- 16-Configuration log settings
- 17-Security policy log
- 18-Heartbeat log settings
- 19-IP access logs
- 20-WAF log settings
- 21-Bandwidth management logs
- 22-Context rate limit logging
- 23-Report settings
- 24--Session settings
- 25-MAC authentication online users
- 26-Signature upgrade
- 27-Software upgrade
- 28-License management
- 29-IRF
- 30-IRF advanced settings
- 31-Contexts
- 32-Administrators
- 33-Date and time
- 34-MAC address learning through a Layer 3 device
- 35-SNMP
- 36-Configuration management
- 37-About
- 38-Reboot
- 39-Ping
- 40-Tracert
- 41-Packet capture
- 42-Webpage Diagnosis
- 43-Diagnostic Info
- 44-Packet trace
- 45-Load balancing test
- 46-IPsec diagnosis
- 47-Fast Internet Access
- 48-IP reputation log settings
- 49-Load balancing logging
Title | Size | Download |
---|---|---|
24--Session settings | 29.28 KB |
Session settings
This help contains the following topics:
¡ Session management operation
¡ Session management functions
Introduction
Session management is a common module, providing basic services for service modules to implement session-based services.
Session management defines packet exchanges at transport layer as sessions. It updates session states and ages out sessions according to data flows from the initiators or responders. Session management allows multiple features to process the same service packet.
Session management operation
Session management tracks the session status by inspecting the transport layer protocol information. It performs unified status maintenance and management of all connections based on session tables and relation tables.
When a connection request passes through the device from a client to a server, the device creates a session entry. The entry can contain the request and response information, such as:
· Source IP address and port number.
· Destination IP address and port number.
· Transport layer protocol.
· Application layer protocol.
· Protocol state of the session.
A multichannel protocol requires that the client and the server negotiate a new connection based on an existing connection to implement an application. Session management enables the device to create a relation entry for each connection during the negotiation phase. The entry is used to associate the connection with the application. Relation entries will be removed after the associated connections are established.
If the destination IP address of a packet is a multicast IP address, the packet will be forwarded out of multiple ports. When a multicast connection request is received on an inbound interface, the device performs the following operations:
· Creates a multicast session entry on the inbound interface.
· Creates a corresponding multicast session entry for each outbound interface.
Unless otherwise stated, "session entry" in this document refers to both unicast and multicast session entries.
In actual applications, session management must work with other service modules. It only tracks connection status. It does not block potential attack packets.
Session management functions
Session management enables the device to provide the following functions:
· Creates sessions for protocol packets, updates session states, and sets aging time for sessions in different protocol states.
· Supports port mapping for application layer protocols (see APR online help), enabling application layer protocols to use customized ports.
· Sets aging time for sessions based on application layer protocols.
· Supports ICMP/ICMPv6 error packet mapping, enabling the device to search for original sessions according to the payloads in the ICMP/ICMPv6 error packets.
· Supports session management for the control channels and dynamic data channels of application layer protocols, for example, FTP.
Restrictions and guidelines
· The aging time for sessions of different applications are valid for stable session TCP sessions in ESTABLISHED state or UDP sessions in READY state.
· For a session in a stable state, the priority order of the associated aging time is as follows:
¡ Aging time for sessions of application layer protocols.
¡ Aging time for sessions in different protocol states.