No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The history memory performance usage percentage of S2600T A controller is almost 400%

Publication Date:  2016-06-17 Views:  119 Downloads:  0
Issue Description

The history memory performance usage percentage of S2600T A controller is almost 400%, but it is normal for B controller.

Diagram 1: History memory performance percentage of A controller

 Diagram 2: History memory performance percentage of B controller

Diagram 3: History memory performance percentage of B controller for one month

        From the performance percentage of recent 1 month, we can find out that this problem is from 27th May when is the GDC power failure date.
Handling Process

1.         Problem reason analysis:

For S2600T performance report, every 5 seconds to collect the data for real time report, but for historical report we get the data every 60 seconds. It means that the cycle for historical is 12 times of the real time;

If the system restarts, the primary controller will synchronize the configuration like the ratio to the standby controller. But as the two controllers are powered on separately, it will have a time gap. At this time it will have the possibility that the primary controller is synchronizing the configuration before the standby controller load the module, so that the configuration can’t be synchronized successfully, and then that the ratio will be default 1. Then the historical performance data will be 12 times of the actual data, this problem happens.

2.         The logs of the server

l  The reason to restart the system.

The S2600T is to shut down automatically because of the high temperature on 2016-05-26 23:26:01;

The system is powered on 2016-05-27 10:09:08B controllerPrimarystart successfully first, then both controller are working

l  The reason of the historical memory usage is almost 400%;

The actual memory usage is 1/12 of the percentage it shows according to the reason analysis. It is about 33%(1/12), and it is normal.

Root Cause

When the system is booting, it only configure the performance module of the primary controller, and standby controller will synchronize the configuration from primary one. If the standby controller booting later than the primary controller configuration process, it will not get the right configuration, then it will use the default configuration, then the historical performance report will be wrong.


Immediate Solution

Restart the performance collecting tool to recovery this issue.

              ssh to controller of S2600T with admin account;

              Execute the command

              chgperfswitch –sw off, stop the performance collecting;

chgperfswitch –sw onstart the performance collecting;


Permanent Solution

This issue will be fixed permanently in V100R005C30SPC500 version.