Sun StorEdge[TM] 3000 family: Resolving "Memory Not Sufficient to Fully Support Current Config" problem.

Asset ID:	1-72-1012505.1
Update Date:	2009-09-21
Keywords:

Solution Type Problem Resolution Sure

Solution 1012505.1 : Sun StorEdge[TM] 3000 family: Resolving "Memory Not Sufficient to Fully Support Current Config" problem.

Related Items


Sun Storage 3510 FC Array
 Sun Storage 3310 Array
 Sun Storage 3511 SATA Array
 Sun Storage 3320 SCSI Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays

PreviouslyPublishedAs
217226

Symptoms
On a Sun StorEdge[TM] 3310, 3320, 3510, or 3511 array, a "Memory Not Sufficient to Fully Support Current Config" event may be followed by a loss of access to the array.

Should the described issue occur, the host will suddenly start receiving timeouts for the LUNs configured on the affected array, and the event log of the array will record events similar to the following:
Tue Jan 24 14:03:06 2006
[Primary]   Warning
Memory Not Sufficient to Fully Support Current Config
These messages are logged continuously on the affected array and although the array can be accessed using the 'sccli' interface and telnet, the host will continue to receive timeouts until finally the target driver gives up and offlines the instance. At this point the array is running low on memory resources and needs to be reset to bring operations back to normal.
This issue can can happen with all versions of currently available firmware versions including 4.13.

Resolution
A final resolution is pending completion. Please see Relief/Workaround.

Relief/Workaround

From sccli, first use show protocol to show protocol status:
sccli> show protocol
Identifier      Status    Port  Parameters
--------------------------------------
telnet          enabled   23    inactivity-timeout=disabled
http            enabled   80    n/a
https           disabled  n/a   n/a
ftp             enabled   21    n/a  <--- FTP is enabled
ssh             disabled  n/a   n/a
priagent        enabled   58632 n/a
snmp            disabled  n/a   n/a
dhcp            enabled   68    n/a
ping            enabled   n/a   n/a
Then use the following to disable FTP:
sccli> set protocol ftp disable
and verify the status again:
sccli> show protocol
Identifier      Status    Port  Parameters
--------------------------------------
telnet          enabled   23    inactivity-timeout=disabled
http            enabled   80    n/a
https           disabled  n/a   n/a
ftp             disabled   21    n/a  <--- FTP is now disabled
ssh             disabled  n/a   n/a
priagent        enabled   58632 n/a
snmp            disabled  n/a   n/a
dhcp            enabled   68    n/a
ping            enabled   n/a   n/a
To disable FTP via telnet/serial port access:
From the main menu, choose:
View and edit Configuration parameters --> Communication Parameters -->
--> Network Protocol Support
You will find a list of protocols and their status. From this list, select:
FTP - Enabled
and you will get a message prompting you to select "Yes" or "No" to Disable FTP. Select "Yes" and this should disable FTP. There is no need to reset the array.
Note: If this issue has already occurred, the only workaround is to reset the array and then disable ftp on the array to avoid further occurrence.

Additional Information
A bug exists in the FTP code which is part of the LAN protocol stack one in which, under certain conditions, it will allocate memory but not free it. Since this memory is being allocated in small chunks and the polling frequency of the attack program is relatively low, it can take a very long time to finally run out of memory and after the reboot of the array, it will be some time that we may see this problem again.

Product
Sun StorageTek 3511 SATA Array
Sun StorageTek 3510 FC Array
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3320 SCSI Array

Internal Comments
If one encounters the following, do not forget to add this customer to bug 6382051 and also open a PTS escalation so that this issue can be tracked.

3510, 3511, 3310, 3320, 3.25, 3.27, 4.11, 4.13, NVRAM, Memory, insufficient, ftp
Previously Published As
83991

Change History
Date: 2006-04-06
User Name: 95826
Action: Approved
Comment: - verified metadata
- changed review date to 2007-04-06
- checked for TM - 1 added
- checked audience : contract
Publishing
Version: 3
Date: 2006-04-06
User Name: 95826
Action: Accept
Comment:
Version: 0
Product_uuid
9fdbb196-73a6-11d8-9e3a-080020a9ed93|Sun StorageTek 3511 SATA Array
58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array
3db30178-43d7-4d85-8bbe-551c33040f0d|Sun StorageTek 3310 SCSI Array
95288bce-56d3-11d8-9e3a-080020a9ed93|Sun StorageTek 3320 SCSI Array

Attachments

This solution has no attachment