Contents

Managing sessions· 1

About session management 1

Session management operation· 1

Session management functions· 1

Restrictions and guidelines: Session management configuration· 2

Setting the session aging time for different protocol states· 2

Setting the session aging time for different application layer protocols· 3

Specifying persistent sessions· 3

Enabling session statistics collection· 4

Display and maintenance commands for session management 4

 

Managing sessions

About session management

Session management is a common module, providing basic services for NAT and attack detection and protection to implement their 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.

Session management 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.

·     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.

Because error packets are generated due to host errors, the mapping can help speed up the aging of the original sessions.

·     Supports persistent sessions, which are kept alive for a long period of time.

·     Supports session management for the control channels and dynamic data channels of application layer protocols, for example, FTP.

Restrictions and guidelines: Session management configuration

For a TCP session in ESTABLISHED state, the priority order of the associated aging time is as follows:

·     Aging time for persistent sessions.

·     Aging time for sessions of application layer protocols.

·     Aging time for sessions in different protocol states.

If the device has excessive sessions, do not set the aging time shorter than the default for a certain protocol state or an application layer protocol. Short aging time settings can make the device slow in response.

Setting the session aging time for different protocol states

About this task

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

Procedure

1.     Enter system view.

system-view

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

session aging-time state { fin | icmp-reply | icmp-request | icmpv6-reply | icmpv6-request | rawip-open | rawip-ready | syn | tcp-est | 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.

¡     ICMPv6-REPLY: 30 seconds.

¡     ICMPv6-REQUEST: 60 seconds.

¡     RAWIP-OPEN: 30 seconds.

¡     RAWIP-READY: 60 seconds.

¡     TCP SYN-SENT and SYN-RCV: 30 seconds.

¡     TCP ESTABLISHED: 240 seconds.

¡     UDP-OPEN: 30 seconds.

¡     UDP-READY: 240 seconds.

Setting the session aging time for different application layer protocols

About this task

The aging time for sessions of different application layer protocols are valid for TCP sessions in ESTABLISHED state or UDP sessions in READY state. For sessions used by other application layer protocols, the aging time for sessions in different protocol states applies.

Procedure

1.     Enter system view.

system-view

2.     Set the session aging time for different application layer protocols.

session aging-time application { dns | ftp | gtp | h225 | h245 | ils | mgcp | nbt | pptp | ras | rsh | rtsp | sccp | sip | sqlnet | tftp | xdmcp } time-value

By default, the session aging time is as follows:

¡     DNS: 1 second.

¡     FTP: 240 seconds.

¡     GTP: 60 seconds.

¡     H.225: 3600 seconds.

¡     H.245: 3600 seconds.

¡     ILS: 3600 seconds.

¡     MGCP: 60 seconds.

¡     NBT: 3600 seconds.

¡     PPTP: 3600 seconds.

¡     RAS: 300 seconds.

¡     RSH: 60 seconds.

¡     RTSP: 3600 seconds.

¡     SCCP: 3600 seconds.

¡     SIP: 300 seconds.

¡     SQLNET: 600 seconds.

¡     TFTP: 60 seconds.

¡     XDMCP: 3600 seconds.

Specifying persistent sessions

About this task

This task is only for TCP sessions in ESTABLISHED state. You can specify TCP sessions that match the permit statements in the specified ACL as persistent sessions, and set longer lifetime or never-age-out persistent sessions.

A persistent session is not removed until one of the following events occurs:

·     The session entry ages out.

·     The device receives a connection close request from the initiator or responder.

·     You manually clear the session entries.

Procedure

1.     Enter system view.

system-view

2.     Specify persistent sessions.

session persistent acl [ ipv6 ] acl-number [ aging-time time-value ]

Enabling session statistics collection

About this task

This feature enables the device to collect session-based outbound and inbound packets and bytes. You can display session statistics based on different criteria.

·     To display statistics per unicast session, use the display session table command.

·     To display statistics per unicast packet type, use the display session statistics command.

Procedure

1.     Enter system view.

system-view

2.     Enable session statistics collection.

session statistics enable

By default, session statistics collection is disabled.

Display and maintenance commands for session management

Execute display commands in any view and reset commands in user view.

 

Task	Command
Display the aging time for sessions of different application layer protocols.	display session aging-time application
Display the aging time for sessions in different protocol states.	display session aging-time state
Display IPv4 unicast session table entries.	display session table ipv4 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ source-ip start-source-ip [ end-source-ip ] ] [ destination-ip start-destination-ip [ end-destination-ip ] ] [ protocol { dccp | icmp | raw-ip | sctp | tcp | udp | udp-lite } ] [ source-port source-port ] [ destination-port destination-port ] [ vpn-instance vpn-instance-name ] [ verbose ]
Display IPv6 unicast session table entries.	display session table ipv6 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ source-ip start-source-ip [ end-source-ip ] ] [ destination-ip start-destination-ip [ end-destination-ip ] ] [ protocol { dccp | icmpv6 | raw-ip | sctp | tcp | udp | udp-lite } ] [ source-port source-port ] [ destination-port destination-port ] [ vpn-instance vpn-instance-name ] [ verbose ]
Display unicast session statistics.	display session statistics [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display IPv4 unicast session statistics.	display session statistics ipv4 { source-ip source-ip | destination-ip destination-ip | protocol { dccp | icmp | raw-ip | sctp | tcp | udp | udp-lite } | source-port source-port | destination-port destination-port } * [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display IPv6 unicast session statistics.	display session statistics ipv6 { source-ip source-ip | destination-ip destination-ip | protocol { dccp | icmpv6 | raw-ip | sctp | tcp | udp | udp-lite } | source-port source-port | destination-port destination-port } * [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display relation table entries.	display session relation-table { ipv4 | ipv6 } [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Clear IPv4 unicast session table entries.	reset session table ipv4 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ source-ip source-ip ] [ destination-ip destination-ip ] [ protocol { dccp | icmp | raw-ip | sctp | tcp | udp | udp-lite } ] [ source-port source-port ] [ destination-port destination-port ] [ vpn-instance vpn-instance-name ]
Clear IPv6 unicast session table entries.	reset session table ipv6 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ source-ip source-ip ] [ destination-ip destination-ip ] [ protocol { dccp | icmpv6 | raw-ip | sctp | tcp | udp | udp-lite } ] [ source-port source-port ] [ destination-port destination-port ] [ vpn-instance vpn-instance-name ]
Clear IPv4 and IPv6 unicast session table entries.	reset session table [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Clear unicast session statistics.	reset session statistics [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Clear relation table entries.	reset session relation-table [ ipv4 | ipv6 ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

‌