Description

This article describes the issue of the decrease in the maximum number of sessions, when IPv6 is enabled in the flow mode.

Symptoms

Prior to enabling IPv6, the maximum number of sessions on the SPC for High End SRX devices is:

{secondary:node1}[edit]
root@lab# run show security flow session summary node 1 | match Max

Maximum-sessions: 1048576

After enabling IPv6 in flow mode and rebooting the device, the maximum number of sessions reduces:
root@lab# show security forwarding-options
family {
    inet6 {
        mode flow-based;
    }
}

{secondary:node1}[edit]
root@lab# run show security flow session summary node 1 | match Max

Maximum-sessions: 819200

Solution

For SRX platform, the device capacity for IPv6 sessions is 50% of the maximum IPv4 sessions. This due to each IPv6 session taking up two slots out of the session table. When both IPv4 and IPv6 are enabled (flow mode), the session capacity for IPv4 sessions is reduced by 20%.

The following tables lists the session capacity for IPv4 sessions:
 

 SRX100 (512MB/ 1GB)SRX2100 (512MB/ 1GB)SRX240 (512MB/ 1GB)SRX650
Max Sessions12K/24K24K/48K48K/100K400K
 
 SRX3400SRX3600SRX5600SRX5800
Max sessions per SPU800K800K800K800K
 
 J2320 (512MB/ 1GB)J2350 (512MB/1GB)J4350 (512MB/1GB)J6350
Max Sessions100K/200K100K/200K100K/200K200K


Note : On SRX 3400 and SRX 3600, which are running with a single SPU acting in SPU CP-FLOW combo mode, the maximum number of IP V4 sessions gets reduced by 50 %. Conversely, the maximum number of sessions per SPU CP are found to be:
 
  • IP v4: 409600
  • IP v6: 262144
 
NOTE: "On the newer platforms we do not have memory constrain like earlier and we can accommodate ipv6 sessions. Hence, there will not be any decrease in session count for ipv6."

Modification History

modified on 14 Feb 2024: added update regarding next-gen devices.