The set configuration operation cpu-limit command reduces the rate to some extent in response to the CPU overhigh caused by NMS data collection.
The undo set configuration operation cpu-limit command deletes the threshold configured for CPU rate decreasing.
By default, no threshold is configured for CPU rate decreasing.
| Parameter | Description | Value |
|---|---|---|
| percent-value |
Specifies a threshold for CPU rate decreasing. |
The value is an integer ranging from 30 to 100, in percentage. |
| access-type |
Specifies a protocol access type. |
- |
| snmp |
Specifies the access type protocol is snmp. |
- |
| ncf-percent-value |
Specifies a threshold for CPU rate decreasing. |
The value is an integer ranging from 30 to 100, in percentage. |
| netconf |
Specifies the access type protocol is netconf. |
- |
Usage Scenario
Data collection by an NMS consumes many CPU resources. To ensure that other service runs properly, the device must reserve some resources for other services. To resolve this issue, run the set configuration operation cpu-limit command to configure a threshold for CPU rate decreasing. If the CPU usage reaches the configured threshold, the device reduces CPU resources allocated to the NMS when the NMS collects data. In this case, CPU pressure can be relieved to some extent.
Configuration Impact
After the set configuration operation cpu-limit command is run, CPU resources that are allocated to MIB operations decrease, which increases the service processing time. If multiple NMSs are involved, an operation timeout may occur. As a result, the NMS that determines a disconnection based on a timeout is disconnected from the device.
Precautions
This command reduces the rate to some extent only in response to the CPU overhigh caused by NMS data collection, instead of limiting the overall peak CPU rate.
In VS mode, this command is supported only by the admin VS.