Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

show security forward-options resource-manager

Syntax

Description

Display forward option status and the CPU and memory allocated for the advance services and to verify the CPU allocation between routing engine and flow RT threads.

Options

  • setting —Display resource manager settings

  • node—(Optional) For chassis cluster configurations, display resource manager settings on a specific node.

    • node-id —Identification number of the node. It can be 0 or 1.

    • all—Display information about all nodes.

    • local—Display information about the local node.

    • primary—Display information about the primary node.

  • status—Verify the CPU allocation between routing engine and flow RT threads.

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show security forward-options resource-manager settings command. Output fields are listed in the approximate order in which they appear.

Table 1: show security forward-options resource-manager settings Output Fields

Field Name

Field Description

Owner

Displays owner of the setting. Usually it is the service that requests the resource. The service utilizing resources such as Content Security, IDP, SWRSS, SWRSS-IO, NICRSS_Q, or Routing Engine.

Type

Displays resource type. This can be either CPU core number, CPU core percentage, regular memory, service memory, heap memory, SWRSS mode or value.

Current settings and Next settings

Displays the current effective and next boot effective value. Value “-” indicates that the setting is not effective or takes default value.

Sample Output

show security forward-options resource-manager status

show security forward-options resource-manager settings

show security forward-options resource-manager status (SRX4600)

Release Information

Command introduced in Junos OS Release 19.4R1.

From Junos OS Release 25.2R1, when you launch vSRX 3.0 instances with even numbers of CPU cores configured, then by default two CPU cores are allocated to the Routing Engine. This allocation enhances system stability and ensures the efficient operation of both the Routing Engine and Packet Forwarding Engine. For systems with an odd number of CPU cores, only one core is allocated to the Routing Engine.