Setting the session aging time for different protocol states

IMPORTANT:

If more than 800000 sessions exist, do not set the aging time shorter than the default for a certain protocol state. Short aging time settings can make the device slow in response.

If a session in a certain protocol state has no packet hit before the aging time expires, the device automatically removes the session.

To set the session aging time for different protocol states:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the session aging time for different protocol states.	session aging-time state { fin \| icmp-reply \| icmp-request \| rawip-open \| rawip-ready \| syn \| tcp-close \| tcp-est \| tcp-time-wait \| udp-open \| udp-ready } time-value	The default aging time for sessions in different protocol states is as follows: FIN_WAIT: 30 seconds. ICMP-REPLY: 30 seconds. ICMP-REQUEST: 60 seconds. RAWIP-OPEN: 30 seconds. RAWIP-READY: 60 seconds. TCP SYN-SENT and SYN-RCV: 30 seconds. TCP CLOSE: 2 seconds. TCP ESTABLISHED: 3600 seconds. TCP TIME-WAIT: 2 seconds. UDP-OPEN: 30 seconds. UDP-READY: 60 seconds.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Set the session aging time for different protocol states.

session aging-time state { fin | icmp-reply | icmp-request | rawip-open | rawip-ready | syn | tcp-close | tcp-est | tcp-time-wait | udp-open | udp-ready } time-value

The default aging time for sessions in different protocol states is as follows:

FIN_WAIT: 30 seconds.
ICMP-REPLY: 30 seconds.
ICMP-REQUEST: 60 seconds.
RAWIP-OPEN: 30 seconds.
RAWIP-READY: 60 seconds.
TCP SYN-SENT and SYN-RCV: 30 seconds.
TCP CLOSE: 2 seconds.
TCP ESTABLISHED: 3600 seconds.
TCP TIME-WAIT: 2 seconds.
UDP-OPEN: 30 seconds.
UDP-READY: 60 seconds.

prev	up	next
Session management task list	home	Setting the session aging time for different application layer protocols or applications