Why is the CPU usage of a CE series switch reduced after the interface information obtaining method used by the NMS is changed

21

The NMS can use either the get-next or get mode to access interface information.
In the get-next mode, a switch receives a request for interface information from the NMS, obtains the interface information from the buffer, and then reports the information to the NMS.
In the get mode, a switch receives a request for interface information from the NMS, collects information about the specified interface in real time, and then reports the information to the NMS.
If the NMS needs to frequently obtain interface information or a huge amount of information, the get mode will cause a high CPU usage because the switch collects information in real time. Therefore, the get-next mode is recommended.

Other related questions:
CE series switches have high CPU usage, then how to quickly locate the cause and collect CPU information
If the CPU usage of the device is high, perform the following steps to locate and collect information, and then send the information to Huawei technical support personnel. 1. Run the display cpu command to view the services with the high CPU usage. display cpu CPU utilization statistics at 2016-02-02 02:07:22 366 ms System CPU Using Percentage : 6% CPU utilization for five seconds: 6%, one minute: 6%, five minutes: 6%. Max CPU Usage : 38% Max CPU Usage Stat. Time : 2016-02-01 12:29:26 821 ms State: Non-overload Overload threshold: 90%, Overload clear threshold: 75%, Duration: 480s --------------------------- ServiceName UseRate --------------------------- SYSTEM 6% AAA 0% ARP 0% CMF 0% ...... 2. Run the display system service service-name command repeatedly in the diagnostic view to check the service components with the high CPU usage. system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system service SYSTEM Service : SYSTEM -------------------------------------------------------------------------------- Component CID CGID Process HaState CpuUsage MemUsage -------------------------------------------------------------------------------- DFS 0x81DE271D 0x1DE271B 10003 PRIMARY 0% 4006312 TELC 0x8091271F 0x91271D 10001 PRIMARY 0% 19000 SSHC 0x80922720 0x92271E 10001 PRIMARY 0% 41208 SSHS 0x80932723 0x932721 10001 PRIMARY 0% 48844 3. Run the display system thread process process-id command repeatedly in the diagnostic view to check the processes with the high CPU usage. system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system thread process 10003 Info: This operation needs several seconds. Info: Operating, please wait for a moment......done. ------------------------------------------------------------------------------- Process ID Thread ID Thread Type BindComp BindCpu BindFlag Usage ------------------------------------------------------------------------------- 10003 1210525456 main thread Bind all Free 0% 10003 1227637888 DefSch0200 Free all Free 0% 10003 1227506816 IPC0000 Free all Free 0% 10003 1227768960 DefSch0300 Free all Free 0% 10003 1237476480 DefSch0100 Free all Free 0% 10003 1237607552 DefSch0101 Free all Free 0% 10003 1226847360 DMS_PIPE_RECV_TASK Free all Free 0% 10003 1218028672 TICK Free all Free 0% 10003 1226716288 DMS_TIPC_SEND Free all Free 0% 10003 1217766528 BOX_Out Free all Free 0% 10003 1217897600 VCLK Free 0 Free 0% 10003 1237738624 CliGetThreadCpu Free all Free 0% ------------------------------------------------------------------------------- Total = 12 4. Run the display system thread callstack process process-id thread-id command in the diagnostic view to check process call stack information. system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system thread callstack process 10003 1210525456 Thread 1210525456 (Thread MainThread): #00 libc.so.6(epoll_wait) #01 location(Frame_FdMainThread) #02 location(Frame_Main) #03 location(main) #04 libc.so.6() #05 libc.so.6()

MIB node of CPU usage
The HUAWEI-CPU-MIB file is used to query CPU usage information of the SRU and interface card. The hwCpuDevTable is used to describe CPU usage. The OID prefix of the table is 1.3.6.1.4.1.2011.6.3.4.1. The indexes of the table are hwFrameIndex, hwSlotIndex, and hwCpuDevIndex. hwCpuDevIndex [1] Integer32 This node is used for expansion. On a single-CPU router, this value is 0. not-accessible For the SRU, the value 0 indicates the information of the primary core, and a value from 1 to 255 indicates the information of a secondary core. Example: 5 indicates that the CPU usage of the primary core of the SRU is 27% and the CPU usage of the secondary core 1 is 1%. ***** SNMP QUERY STARTED ***** 1: hwCpuDevDuty.0.0.0 (integer) 27 2: hwCpuDevDuty.0.0.1 (integer) 1 3: hwAvgDuty1min.0.0.0 (integer) 27 4: hwAvgDuty1min.0.0.1 (integer) 1 5: hwAvgDuty5min.0.0.0 (integer) 27 6: hwAvgDuty5min.0.0.1 (integer) 1 ***** SNMP QUERY FINISHED *****

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top