Configuring the Stale Session Cleanup Using the Unique Key

The section describes how to configure stale session cleanup using the unique key.

To configure the stale session cleanup, use the following configuration:

config 
  cdl  
    datastore session datastore_name 
      features   
             index-overwrite-detection [ max-tps | queue-size | unique-keys-prefix [ SupiDnnKey | FramedIpv6PrefixKey ] 
             action [ notify-record | log-record | delete-record ] 
             exit 
              end 

NOTES:

  • cdl —Enter the CDL configuration mode.

  • datastore session datastore_name —Specify the CDL datastore session.

  • index-overwrite-detection [ max-tps | queue-size | unique-keys-prefix ] —Configures the index keys overwrite detection capability. The parameter has the following subparameters:

    • max-tps —Specify the TPS per cdl-endpoint at which the stale record notification is sent. This parameter is applicable only when the action is "notify-record". The accepted value range is 1..2000. The default value is 200.

    • queue-size —Specify the queue size for each cdl-endpoint. The default value is 1000.

    • unique-keys-prefix [ SupiDnnKey | FramedIpv6PrefixKey ] —Specify the list of uniqueKey prefixes for the index overwrite detection and the action that must be performed on successful detection.

  • action [ log-record | delete-record ] —Specify the action that must be taken on detecting a stale record.

    Note

    If configuring the stale session cleanup feature for the first time on your system, Cisco recommends performing the configuration after both the GR sites are upgraded to the same software version.

    Important

    The delete-record action on key SupiDnnKey command takes effect only when the required key SupiDnnKey is added in the CDL sessions.