ltm persistence persist-records¶

ltm persistence persist-records(1) BIG-IP TMSH Manual ltm persistence persist-records(1)

NAME
persist-records - Displays or deletes persistence records.

MODULE
ltm persistence

SYNTAX
Configure the persist-records component within the ltm persistence module using the syntax in the following sections.

DESCRIPTION
You can use the persist-records component to either display or delete records of persistent connections.

EXAMPLES
show persist-records

Displays all persistent connections on the BIG-IP(r) system.

delete persist-records client-addr 172.19.255.1

Deletes all persistent connections that originate from the client IP address, 172.19.255.1.

OPTIONS
client-addr
Specifies the IP address of the client from which the persistent connections you want to view or delete persist.

key Specifies a string that the system is using to persist the connections you want to view or delete.

mode Specifies the type of persistence of the connections you want to view or delete. The options are:

cookie
Cookie persistence uses an HTTP cookie stored on a client's computer to allow the client to connect to the same
server previously visited at a web site.

destination-address
Also known as sticky persistence, destination address affinity persistence supports TCP and UDP protocols, and
directs session requests to the same server based solely on the destination IP address of a packet.

hash Hash persistence is based on an existing iRule.

msrdp
MSRDP persistence provides an efficient way of load balancing traffic and maintaining persistent sessions between
Windows(r) clients and servers that are running the Microsoft(r) Terminal Services service. The recommended
scenario for enabling the MSRDP persistence feature is to create a load balancing pool that consists of members
running Windows .NET Server 2003, Enterprise Edition, or later, where all members belong to a Windows cluster and
participate in a Windows session directory.

sip Session Initiation Protocol (SIP) persistence is a type of persistence available for server pools. You can
configure SIP persistence for proxy servers that receive SIP messages sent through UDP. The BIG-IP system
currently supports persistence for SIP messages sent through UDP, TCP, or SCTP.

source-address
Also known as simple persistence, source address affinity persistence supports TCP and UDP protocols, and directs
session requests to the same server based solely on the source IP address of a packet. When you specify a source
address as the mode of persistence, you must specify an IP address using the client-addr option.

ssl-session-id
SSL persistence is a type of persistence that tracks non-terminated SSL sessions, using the SSL session ID. Even
when the client's IP address changes, the system still recognizes the connection as being persistent based on the
session ID. Note that the term, non-terminated SSL sessions, refers to sessions in which the system does not
perform the tasks of SSL certificate authentication and encryption/re-encryption.

universal
Universal persistence allows you to write an expression that defines what to persist on in a packet. The
expression, written using the same expression syntax that you use in iRules(r), defines some sequence of bytes to
use as a session identifier.

node-addr
Specifies the IP address of the node with which the client sessions that you want to view or delete remain persistent.

node-port
Specifies the port number of the node with which the client sessions that you want to view or delete remain
persistent.

pool Specifies the pool member with which the client sessions that you want to view or delete remain persistent.

save-to-file
Specifies the file which persist-records information can be save to. With this option, it can write a file larger than
2GB.

virtual
Specifies the virtual server with which the client sessions that you want to view or delete remain persistent.