eG Monitoring
 

Measures reported by CisSDWCpuTest

Among the four components of the Cisco SD-WAN, the vEdge router can either be a Cisco SDWAN hardware device or software that runs as a virtual machine, and the remaining three are software-only components. Generally, the software vEdge router, Cisco vManage, and Cisco vSmart Controller software run on servers, and the vBond orchestrator software runs as a process (daemon) on a vEdge router. These software-only components run on a VM with multiple vCPUs.

CPU contentions on the components can significantly degrade the performance of the that component. To avoid this, administrators must track the CPU usage of each component over time, proactively detect potential CPU contentions, and accurately isolate what is causing excessive CPU usage on each component-system processes? or user processes? or being idle? This can be achieved using the CPU Usage test.

This test monitors the CPU usage of the each component of the target Cisco SD-WAN appliance and alerts administrators to erratic usage patterns on the component and what is causing them. This way, the test helps administrators isolate and pre-empt CPU contentions on the component, and thus improve the performance of the appliance.

Outputs of the test : One set of results for each component of the target Cisco SD-WAN being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
User_CPU Indicates the percentage of CPU consumed by the user process of this component. Percent By comparing the value of this measure with that of the System CPU and Idle CPU measures, you can instantly determine whether system processes are CPU-hungry or user processes or the idle time the cause of CPU contention.
System_CPU Indicates the percentage of CPU consumed by the system process of this component. Percent By comparing the value of this measure with that of the User CPU and Idle CPU measures, you can instantly determine whether system processes are CPU-hungry or user processes or the idle time the cause of CPU contention.
Idle_CPU Indicates the percentage of CPU that is idle for this component. Percent Compare the value of this measure with the value of the System CPU and User CPU, measures to understand where the component spent the maximum CPU time-in serving user requests? in systemlevel processing? or being idle? In the event of a slowdown, you can use the results of this comparative analysis to determine what caused the CPU contention.