To enable checksum verification for protocol packets:
Step
1.
Enter system view.
2.
Enable checksum verification.
Specifying the persistent session rule
You can set sessions with specific characteristics as persistent sessions. The aging time of a persistent
session does not change with session state transitions, and the session will not be removed even when no
packets match it.
You can configure a persistent session by configuring an aging time that is longer than those of common
sessions, or by configuring the session as a permanent connection. A permanent connection can be
cleared only when the session initiator or responder sends a request to close it or you clear it manually.
You can set the persistent session criteria by specifying a basic or advanced ACL. All sessions permitted
by the ACL are persistent sessions.
For more information about the configuration of basic and advance ACLs, see ACL and QoS
Configuration Guide.
To specify the persistent session rule:
Step
1.
Enter system view.
2.
Specify the persistent session
rule.
Clearing sessions manually
Task
Clear sessions.
Command
system-view
session checksum { all | { icmp |
tcp | udp } * }
Command
system-view
session persist acl acl-number
[ aging-time time-value ]
Command
reset session [ slot slot-number ] [ source-ip source-ip ]
[ destination-ip destination-ip ] [ protocol-type { icmp |
raw-ip | tcp | udp } ] [ source-port source-port ]
[ destination-port destination-port ] [ vpn-instance
vpn-instance-name ]
457
Remarks
N/A
Disabled by default.
Remarks
N/A
Not specified by default.
A persistent session rule can
reference only one ACL.
Only basic and advanced IPv4
ACLs are supported.
Remarks
Available in user
view.