Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Setting Session Limits Using the Command Line Utility

You can control the maximum number of sessions that are returned when you execute a query. You may want to limit the number of sessions returned if you are concerned that too many sessions may be found with your query and may impact performance. For example, when you execute a query that does not contain any supported search attributes, then the query is unconstrained and may find too many sessions.

Factors Affecting the Number of Sessions Returned

The number of sessions returned from a query depends on five factors:

  • The number you type next to the -sl (session limit) argument.
  • The system-wide session limit. This number defaults to 10,000 but may be changed with the assistance of your Juniper Networks Technical Support representative.
  • The Effective Session Limit. This number is always the lesser of the system-wide session limit and the number you enter next to -sl for the session limit.
  • The number of sessions found to meet the criteria you enter. (For example, if your criteria is User-Name = "A*", then the sessions found are those with usernames beginning with the letter A or a.)
  • Whether or not you use the -force argument. The presence of the -force argument specifies use of the session limit even if the number of found sessions exceeds the session limit. The absence of -force specifies that no sessions be returned or acted upon if the number of matching sessions exceeds the session limit. (See Number of Sessions Returned and Examples of Limiting the Number of Sessions Returned Using the Command Line Utility for more information about the use of -force.)

Number of Sessions Returned

If you use the -force argument, the number of sessions returned is always the lesser of the effective session limit or the number of sessions found. For example, if the session-wide limit is 10,000, you enter a session limit of 100, and the number of sessions found to match your criteria is 150, then 100 sessions (the effective session limit) is returned.

If you do not use the -force argument, the number of sessions returned is the actual number of sessions found if the number of sessions found is less than the effective session limit. If the number of sessions found exceeds the effective session limit, then no sessions are returned. For example, if the session-wide limit is 10,000, you enter a session limit of 100, and the number of sessions found to match your criteria is 150, then no sessions are returned because the effective session limit is exceeded.

Examples of Limiting the Number of Sessions Returned Using the Command Line Utility

Table 110 provides examples in which the session limit rules apply.

Table 110: Number of Sessions Found for Various Examples

-force Argument Present or Absent

Session Limit You Enter

System-Wide Session Limit

Effective Session Limit

Sessions Found

Sessions Returned

Reason

Present

100

10,000

100

200

100

Effective limit prevails

Present

100

10,000

100

50

50

Number of sessions found is within effective limit

Present

10

10,000

10

200

10

Effective limit prevails

Present

Nothing

10,000

10,000

200

200

Number of sessions found is within effective limit

Present

20,000

10,000

10,000

25,000

10,000

Effective limit prevails

Absent

100

10,000

100

200

0

Effective limit exceeded

Absent

100

10,000

100

50

50

Number of sessions found is within effective limit

Absent

10

10,000

10

200

10

Effective limit exceeded

Absent

Nothing

10,000

10,000

200

200

Number of sessions found is within effective limit

Absent

20,000

10,000

10,000

25,000

0

Effective limit exceeded

Modified: 2017-09-27