resource-monitor
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 (Resource Monitor) number;
no-logging;
no-throttle (Resource Monitor);
resource-category jtree {
resource-type (contiguous-pages | free-dwords | free-pages) {
low-watermark number;
high-watermark number;
}
}
subscribers-limit (Resource Monitor) {
client-type (Subscriber Limits) (any | dhcp | l2tp | pppoe) {
chassis (Subscriber Limits) {
limit limit;
}
fpc (Subscriber Limits) slot-number {
limit limit;
pic (Subscriber Limits) number {
limit limit;
port (Subscriber Limits) number {
limit limit;
}
}
}
}
}
traceoptions (Resource Monitor) {
file filename <files number> <match regular-expression> <size maximum-file-size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
}
Hierarchy Level
[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 only configure the resource-monitoring capability on the BNG User Planes.
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.