H3C MSR Series Command Reference Manual page 933

•
RAS sessions: 300 seconds.
•
RIP sessions: 120 seconds.
•
RSH sessions: 60 seconds.
•
RTSP sessions: 3600 seconds.
•
SCCP sessions: 3600 seconds.
•
SIP sessions: 300 seconds.
•
SNMP sessions: 120 seconds.
•
SNMPTRAP sessions: 120 seconds.
•
SQLNET sessions: 600 seconds.
•
STUN sessions: 600 seconds.
•
SYSLOG sessions: 120 seconds.
•
TFTP sessions: 60 seconds.
•
TACACS-DS sessions: 120 seconds.
•
WHO sessions: 120 seconds.
•
XDMCP sessions: 3600 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
application-name: Specifies an application layer protocol or an application by its name, a
case-insensitive string of 1 to 63 characters. Valid characters can be digits, letters, hyphens (-), and
underscores (_). The names invalid and other are not allowed. The application layer protocol or
application must exist on the device.
time-value: Specifies the aging time in seconds. The value range 1 to 100000.
Usage guidelines
This command sets the aging time for stable sessions of the specified application layer protocol or
applications. For TCP sessions, the stable state is ESTABLISHED. For UDP sessions, the stable
state is READY.
For sessions of application layer protocols or applications that are not supported by this command,
the aging time is set by the session aging-time state command. For persistent sessions, the aging
time is set by the session persistent acl command.
Supported application layer protocols or applications specified in this command depend on the APR
module. For information about APR, see Security Configuration Guide.
Examples
# Set the aging time for FTP sessions to 1800 seconds.
<Sysname> system-view
[Sysname] session aging-time application ftp 1800
# Set the aging time for 126_Web_Email_Send_Email_HTTP sessions to 1800 seconds.
<Sysname> system-view
[Sysname] session aging-time application 126_Web_Email_Send_Email_HTTP 1800
Related commands
display session aging-time application
910