close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

resource-monitor

date_range 20-Nov-23

arrow_backward

arrow_forward

Syntax

resource-monitor {
    free-fw-memory-watermark number;
    free-heap-memory-watermark number;
    free-nh-memory-watermark number;
    high-cos-queue-threshold number;
    high-threshold number;
    no-logging;
    no-throttle;
    resource-category jtree {
        resource-type (contiguous-pages | free-dwords | free-pages) {
            low-watermark number;
            high-watermark number;
        }
    }
    subscribers-limit {
        client-type (any | dhcp | l2tp | pppoe) {
            chassis {
                limit limit;
            }
            fpc slot-number {
                limit limit;
                pic number {
                    limit limit;
                    port number {
                        limit limit;
                    }
                }
            }
        }
    }
    traceoptions {
        file filename <files number> <match regular-expression> <size maximum-file-size> <world-readable | no-world-readable>;
        flag flag;
        no-remote-trace;
    }
}

Hierarchy Level

content_copy zoom_out_map
[edit system services]

Description

Enable the resource monitoring capability to provision sufficient headroom (memory space limits that are set for the application or virtual router) for monitoring the health and operating efficiency of DPCs and MPCs. This feature also enables the memory resource monitoring mechanism to avoid the system operations from compromising on the health and traffic-handling stability of the line cards by generating error logs when a specified watermark value for memory regions and threshold value for the jtree memory region are exceeded. A trade-off on the system performance can be detrimental for supporting live traffic and protocols.

The variable number in the Syntax section represents a percentage.

You can configure the resource-monitoring capability on MX240, MX480, MX960, MX2010, and MX2020 routers with I-chip-based DPCs and Trio-based FPCs.

The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 15.1.

high-cos-queue-threshold option introduced in Junos OS Release 17.4R1.

arrow_backward PREVIOUS resource-manager (Forwarding-options)

NEXT arrow_forward resource-profiles (Analytics)

Junos CLI Reference

ON THIS PAGE

resource-monitor

Syntax

Hierarchy Level

Description

Required Privilege Level

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos CLI Reference

ON THIS PAGE

resource-monitor

Syntax

Hierarchy Level

Description

Required Privilege Level

Release Information

Related Documentation

Stay in touch