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>

Reminder

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

upgrade

S2200T failed to collect logs due to no enough memory resource

Publication Date:  2015-06-15 Views:  146 Downloads:  0
Issue Description

Product: S2200T

Version:V100R005C00SPC500

Symptom:

The customer want to export the System Logs ,but get the below error:

 

The memory is not enough.

Alarm Information

When try to export the System Logs from the ISM ,get the below error.

Handling Process

1:Ask the customer to provide a remote access;

2:During the remote access,we find the storage only have 2 GB memory for each controller,maybe some process take too much memory,and there is no enough memory to support the log collection operation,to know the root cause,we have to analyze the messages logs,but now we can't collect the logs;

3:In this case,we have to reset the controller to release the occupied memory;

4:Run the command "chglun -lun lunid -c b" to change the owning controller of the LUN from controller A to controller B;

5: Run the command "showcache -c a" again and again till there is no dirty data exists in controller A;

6:Login the storage CLI in developer mode and run the command "rebootcontroller -c a" to reset controller A;

7: Repeat step 4 to step 6 to reset controller B;

8: Login ISM,then collect the logs.

 

Root Cause

It requires more than 100MB free memory when collecting the log, so it will cause log collect failed if the free memory is less than 100MB.

The customer network between storage and hosts had network failover happened on 2015.5.5, it occupied a lot of  memory.

cid:image001.png@01D0949B.1EF8ADC0

 

There is only 47MB free memory when customer tried to collect the log, so it failed.

cid:image002.png@01D0949B.1EF8ADC0

cid:image003.png@01D0949B.1EF8ADC0

 

Solution

Reset the controller to release the memory:

1:Run the command "chglun -lun lunid -c b" to change the owning controller of the LUN from controller A to controller B;

2: Run the command "showcache-c a" again and again till there is no dirty data exists in controller A;

3: Login the storage CLI in developer mode and run the command "rebootcontroller -c a" to reset controller A;

4:Repeat step 1 to step 3 to reset controller B.

Suggestions
None

END