Supporting ICMP error packet mapping and allowing the system to search for original sessions
•
according to the payload of these packets.
Because error packets are generated due to host errors, the mapping can help speed up the aging
of the original sessions.
Supporting persistent sessions, which are not aged within a long period of time.
•
Supporting session management of control channels and dynamic data channels of application
•
layer protocols, for example, FTP.
•
Supporting limiting the number of session-based connections. For more information, see
"Configuring connection limits."
Session management task list
Task
Setting session aging times based on protocol state
Configuring session aging time based on application layer protocol type
Configuring early aging for sessions
Setting the maximum number of sessions
Enabling checksum verification
Specifying the persistent session rule
Clearing sessions manually
These tasks are mutually independent and can be configured in any order. You can configure them as
required.
Setting session aging times based on protocol state
If the application layer protocol of a session supports session aging time configuration, the session takes
the session aging time set based on the application layer protocol type as its aging time when it is in the
READY/ESTABLISH state. For more information about the configuration, see
time based on application layer protocol
If a session entry is not matched with any packets in a specified period of time, the entry will be aged out.
IMPORTANT:
For a large amount of sessions (more than 800000), do not specify too short aging time. Otherwise, the
console might be slow in response.
To set the session aging times based on protocol state:
Step
1.
Enter system view.
type."
Command
system-view
454
Remarks
Optional
Optional
Optional
Optional
Optional
Optional
Optional
"Configuring session aging
Remarks
N/A