Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1012505.1
Update Date:2013-08-12
Keywords:

Solution Type  Problem Resolution Sure

Solution  1012505.1 :   Sun Storage 3000 Arrays May Lose Data Host Access After Reporting "Memory Not Sufficient to Fully Support Current Config"  


Related Items
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3320 SCSI Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
  •  
  • _Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
217226


Applies to:

Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
All Platforms

Symptoms

Arrays in the Sun Storage 3000 family (3310, 3320, 3510, 3511) running firmware prior to 4.21F may report this error:

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.
 

Cause

This issue can can happen with firmware versions prior to 4.21F.

Solution

This problem is resolved in firmware level 4.21F.

If you are running firmware prior to 4.21F, it is possible to work around this problem.

 

Workaround Using sccli

Use the sccli command 'show protocol' to view current settings.

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

If FTP is enabled, use 'set protocol' to disable FTP.

sccli> set protocol ftp disable

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

 

Workaround Using Firmware Menu via Telnet or 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 statuses. From this list, select "FTP - Enabled" and you will get a message prompting you to select Yes or No to disable FTP. Select Yes to disable FTP. There is no need to reset the array.

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.

 

The following material is internal and preserved from the earlier Sun version of this document.

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.


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
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback