This article explains how to:

1. Verify the configured high‐watermark and low‐watermark values for aggressive session aging.
2. Determine how many sessions have been aged out at runtime.

This operational command shows how many sessions have been early aged out once aggressive session aging is activated.

root@SRX1> show security flow session aging

       Early Ageout Flow Session    Cutoff-Time        Count

       by-defaults           300  secs         5341 >>>>>>>>>>>>

       Total                            5341

root@SRX1> show security flow session aging

       Early Ageout Flow Session    Cutoff-Time        Count

       by-defaults           300  secs         5344 >>>>>>>>>>>>

       Total                            5344

You can also use the vty to retrieve detailed information, including the configured high and low watermarks.

FLOWD_SRX(SRX1 vty)# show usp flow session aggressive

Aggressive aging statistics

Maximum sessions : 62914560

Current sessions : 6932804

High watermark  : 6291456          >>>>> 10% of Total Capacity ( Maximum sessions )

Low watermark  : 3145728           >>>>>>>>>

Early age-out time by defaults            :  300 secs

Early age-out time by deprecated configuration    :  300 secs

Session early-aged by defaults            : 4919

Session early-aged by deprecated config       :   0

Session early-aged total               : 4919                   >>>>>>>> Counter Incrementing

Scan pending   : yes

FLOWD_SRX(SRX1 vty)#