A10 3030s Detected problem in Health Monitor DataCPU

[renegade310 0]

Доброго дня.

Маємо коробку A10 3030s.

Прошивка:

         64-bit Advanced Core OS (ACOS) version 4.1.4-GR1-P5, build 81 (Sep-08-2020,09:32)
          Booted from Hard Disk primary image
          Number of control CPUs is set to 1
          aFleX version: 2.0.0
          GUI primary image (default) version 4_1_4-GR1-P5-4_1_4-gr1-p5-38
          GUI secondary image version 4_1_4-GR1-P5-4_1_4-gr1-p5-38
          aXAPI version: 3.0
          Cylance version: N/A
          Hard Disk primary image (default) version 4.1.4-GR1-P5, build 81
          Hard Disk secondary image version 4.1.4-GR1-P5, build 81
          Last configuration saved at Feb-9-2023, 18:37
          Hardware: 8 CPUs(Stepping 9), Single 74G drive, Free storage is 34G
          Total System Memory 16350 Mbytes, Free Memory 7692 Mbytes
          Hardware Manufacturing Code: 175211
          Current time is Feb-11-2023, 19:01
          The system has been up 21 days, 1 hour, 9 minutes

 

І недавно сталася проблема що розвалився lag на ньому і в логах було таке:

 

Feb 09 2023 16:54:12 Notice      [Router]:Interface(s)  ethernet 9,  removed from aggregator po2
Feb 09 2023 16:54:12 Notice      [Router]:Interface(s)  ethernet 10,  removed from aggregator po2
Feb 09 2023 16:54:12 Notice      [Router]:Interface(s)  ethernet 11,  removed from aggregator po1
Feb 09 2023 16:54:12 Notice      [Router]:Interface(s)  ethernet 12,  removed from aggregator po1
Feb 09 2023 16:54:11 Error       [Fail Safe]:Failed in thread LWP 6361
Feb 09 2023 16:54:11 Error       [Fail Safe]:Failed in thread LWP 6338
Feb 09 2023 16:54:11 Error       [Fail Safe]:Failed in thread LWP 6340
Feb 09 2023 16:54:11 Error       [Fail Safe]:Failed in thread 0x6f09149
Feb 09 2023 16:54:11 Error       [Fail Safe]:FailSafe timestamp 4704431868, last update time 409464572 
Feb 09 2023 16:54:11 Error       [Fail Safe]:FailSafe detected problem in ALB threads.
Feb 09 2023 16:54:11 Warning     [AXMON]:Detected problem in Health Monitor DataCPU1 (LWP 6216). (Last counter was -1772775275 at time 4704431868 bit 7).
Feb 09 2023 16:54:11 Warning     [AXMON]:Detected problem in Health Monitor DataCPU4 (LWP 6220). (Last counter was -1460486145 at time 4704431868 bit 6).
Feb 09 2023 16:54:11 Warning     [AXMON]:Detected problem in Health Monitor DataCPU0 (LWP 6215). (Last counter was -974207122 at time 4704431868 bit 5).
Feb 09 2023 16:54:11 Warning     [AXMON]:Detected problem in Health Monitor DataCPU3 (LWP 6219). (Last counter was 1747921038 at time 4704431868 bit 4).
Feb 09 2023 16:54:11 Warning     [AXMON]:Detected problem in Health Monitor DataCPU2 (LWP 6217). (Last counter was -1737089530 at time 4704431868 bit 3).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU1 (LWP 6216). (Last counter was -1772775275 at time 4704431789 bit 7).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU4 (LWP 6220). (Last counter was -1460486145 at time 4704431789 bit 6).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU0 (LWP 6215). (Last counter was -974207122 at time 4704431789 bit 5).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU3 (LWP 6219). (Last counter was 1747921038 at time 4704431789 bit 4).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU2 (LWP 6217). (Last counter was -1737089530 at time 4704431789 bit 3).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU1 (LWP 6216). (Last counter was -1772775275 at time 4704431713 bit 7).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU4 (LWP 6220). (Last counter was -1460486145 at time 4704431713 bit 6).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU0 (LWP 6215). (Last counter was -974207122 at time 4704431713 bit 5).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU3 (LWP 6219). (Last counter was 1747921038 at time 4704431712 bit 4).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU1 (LWP 6216). (Last counter was -1772775275 at time 4704431636 bit 7).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU4 (LWP 6220). (Last counter was -1460486145 at time 4704431636 bit 6).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU0 (LWP 6215). (Last counter was -974207122 at time 4704431636 bit 5).
Feb 09 2023 16:54:10 Warning     [AXMON]:Detected problem in Health Monitor DataCPU3 (LWP 6219). (Last counter was 1747921038 at time 4704431636 bit 4).
Feb 09 2023 16:54:09 Warning     [AXMON]:Detected problem in Health Monitor DataCPU1 (LWP 6216). (Last counter was -1772775275 at time 4704431556 bit 7).
Feb 09 2023 16:54:09 Warning     [AXMON]:Detected problem in Health Monitor DataCPU0 (LWP 6215). (Last counter was -974207122 at time 4704431556 bit 5).
Feb 09 2023 16:54:09 Warning     [AXMON]:Detected problem in Health Monitor DataCPU3 (LWP 6219). (Last counter was 1747921038 at time 4704431552 bit 4).

 

Проблема була тимчасова, буквально за хвилину лаг знову зібрався і все працює.

В чому може бути проблема?

[Kiano 616]

The message "Detected problem in Health Monitor DataCPU1" in A10 Networks switch logs indicates that there is an issue with one of the central processing units (CPUs) in the switch. The switch has a built-in health monitor that periodically checks the status of various components, including the CPUs. If the health monitor detects a problem with one of the CPUs, it generates this message in the logs.

The exact reason for the problem with the CPU can vary, but common causes include high CPU utilization, memory leaks, software bugs, or hardware failures. If you are encountering this issue, it is recommended to take the following steps:

Check the switch's performance statistics, such as CPU utilization and memory usage, to determine if there is an issue with resource utilization.

Review the switch's logs for additional messages that may provide more information about the issue.

Update the switch's firmware to the latest version to ensure that any known software bugs have been resolved.

If the issue persists, contact A10 Networks technical support for further assistance.

It's important to address this issue as soon as possible to prevent any potential downtime or degradation of switch performance.