Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1000221.1
Update Date:2011-03-04
Keywords:

Solution Type  Sun Alert Sure

Solution  1000221.1 :   Sun StorEdge T3 and Sun StorEdge 3310 SCSI Array's Controller May Disable Without Warning When Probed with Third Party Network Security Software  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage T3 Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 6120 Array
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
200296


Product
Sun StorageTek T3 Array
Sun StorageTek 6120 Array
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3510 FC Array

Bug Id
<SUNBUG: 4356418>, <SUNBUG: 4435299>, <SUNBUG: 4527674>, <SUNBUG: 4912150>, <SUNBUG: 6350194>

Date of Workaround Release
17-APR-2001

Date of Resolved Release
23-SEP-2003

Impact

The ethernet port and associated TCP/IP services provided by the Sun StorEdge T3/T3B/6120, Sun StorEdge 3310 and 3510 Arrays are critical to maintaining and monitoring its overall health. The TCP/IP services provided with the T3/T3B/6120, 3310 and 3510 embedded real-time operating system lack certain security features. This makes the T3/T3B/6120, 3310 and 3510 arrays vulnerable to possible network issues or deliberate attacks. Probing a T3/T3B/6120, 3310 and 3510 array's ethernet connection using network security software, has been shown , in some cases, to cause the master controller to disable. As a result, performance can decrease or data may become inaccessible.


Contributing Factors

This issue can occur in the following platforms:

  • Sun StorEdge T3/T3B/6120
  • StorEdge 3310 SCSI Array
  • StorEdge 3510 FC Array

Note: This only occurs when any T3/T3B/6120, 3310 and 3510 array units are probed by third party network security software running a security scanner on TCP/IP ethernet port of storage array controllers.


Symptoms

The use of a third party network security software applications that probe Sun StorEdge T3/T3B/6120 Arrays may result in the following conditions:

A. StorEdge T3 Partner Group Configurations:

A Sun StorEdge T3/T3B/6120 and Sun StorEdge 3310 SCSI Array in a partner group configuration; the Master Controller may disable. This will cause the alternate Master Controller to perform a fail-over and it will be promoted to the master role. As long as multi-pathing software is installed and properly configured on the data host, I/O will fail-over to the remaining controller path. This could cause a performance impact due to the loss of I/O bandwidth and the Sun StorEdge T3 partner group cache mode shifting to write through for all LUNs on the partner group.

On 6120 controller with firmware 3.2.1, syslog shows data access exception:

Nov 15 14:05:12 ROOT[1]: N: 6120 Release 3.2.1 Tue Jul 19 11:21:33 PDT 2005 (10.15.3.15)
Nov 15 14:05:12 ROOT[1]: N: u1ctr Reset (2000) CPU data access exception (3)
Nov 15 14:05:12 ROOT[1]: N: CPU trap exception (2048) frame...
Nov 15 14:05:12 ROOT[1]: N: [  IP    ] 0027c66c [ LR   ] 002683e0

B. StorEdge T3 Single Array Configurations:

For Sun StorEdge T3s configured as single arrays, the controller may disable and any LUNs defined on the T3 will be inaccessible to its attached host(s) until the T3 is rebooted.

Sample error messages:

Mar 28 10:29:52 [ ... ] ISR1[2]: N: u2ctr ISP2100[1] Fatal timeout on target 0.1
Mar 28 10:29:52 [ ... ] ISR1[2]: N: u2ctr ISP2100[1] QLCF_ABORT_ALL_CMDS: Command Timeout
Pre-Gauntlet Initiated
Mar 28 10:29:52 [ ... ] ISR1[2]: N: u2ctr ISP2100[1] Received LIP(f7,e8) async event
Mar 28 10:29:59 [ ... ] HBTT[2]: N: u1ctr: Master controller failed; takeover process starts
Mar 28 10:30:00 [ ... ] IPCS[2]: N: u1ctr: Inter-controller communication failed: Receiver offline
Mar 28 10:30:02 [ ... ] ISR1[2]: N: SVD_DONE: Command Error = 0x3(lid = 19)
Mar 28 10:30:02 [ ... ] ISR1[2]: N: u2ctr mirror failed
Mar 28 10:30:02 [ ... ] ISR1[2]: N: SVD_DONE: Command Error = 0x3(lid = 19)
Mar 28 10:39:29 [ ... ] IPCS[2]: N: u2ctr Internal Command error (Aborted via time-out)

C. Sun StorEdge 3310 SCSI Array:

Should the Controller failover issue occur, messages similar to the following may be experienced:

Mon Sep  8 12:03:31 2003
[0111] #9: StorEdge Array SN#326400 Controller ALERT: redundant controller failure detected

 


Workaround

Customers that utilize a third party network security software application that probes a T3/T3B/6120, 3310 or 3510 array can avoid the above mentioned issue by doing the following:

Connect the T3/T3B/6120, 3310 and 3510 array to a private ethernet network. A Private network is a network directly attached to a host and is not directly accessible from the public network. The private network can only be accessed by the host it is directly attached to.

The described issue can be avoided by ensuring that access to Sun StorEdge 3310 SCSI or T3/T3B/6120's administrative network is properly controlled. Do not allow network security software to probe the Sun StorEdge 3310 SCSI or StorEdge T3/T3B/6120's Ethernet port.

 


Resolution

Please see the above Workaround section for the final resolution to this issue.



Modification History
Date: 23-SEP-2003
  • State: Resolved
  • Updated Impact, Product, BugID, Contributing Factors, Symptoms and Resolution sections

Date: 09-OCT-2003
  • Updated Impact

Date: 22-NOV-2005
  • Added Bug ID 6350194
  • Updated Contributing Factors and Relief/Workaround from T3 to T3/T3B/6120

 



Previously Published As
100840
Internal Comments


 




Relief/Workaround for Sun StorEdge 3310 SCSI and Sun StorEdge 3510 FC Array :

To work around the described issue, provide the array with an IP address
that is not accessible from a publicly routeable network.

To work around the described issue, use the below steps to change the IP address:

From the <Main Menu>

Select view and edit Configuration parameters and press <Return>
Select Communication Parameters and press <Return>
Select Internet Protocol (TCP/IP) and press <Return>
Press <Return>at the LAN0 interface prompt
Select Set IP address and press <Return>
Enter new IP address and press <Return>
Select NetMask and press <Return>
Enter new NetMask and press <Return>
Select Gateway and press <Return>
Enter new Gateway and press <Return>


Respond YES to Change/Set IP Address inquiry.

Respond YES to the below NOTICE:

Do you want to reset the controller now ? Yes

NOTE: Change made to this setting will NOT be in effect until the controller is RESET.
Prior to resetting the controller, operation may not proceed normally. For best practices
refer to the Sun StorEdge 3000 Family Manual,Part No. 816-7325-12, dated Sept 2003, Revision A.

-----------

Any Sun StorEdge T3 unit probed by third party network security software. Sun StorEdge T3s
being installed on a public network and the networking module of the pSOS operating system
not having the ability to handle certain types of probes against the IP address of the T3.


 


Internal Contributor/submitter
dave.bruce@sun.com

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
caroline.kahn@sun.com, Kuswandi.Kohar@Sun.COM

Internal Services Knowledge Engineer
karen.edwards@sun.com

Internal Escalation ID
529331, 527479, 548117, 1-130729422

Internal Sun Alert Kasp Legacy ID
100840, 26464 (Sun Alert)

Internal Sun Alert & FAB Admin Info
Critical Category: Availability ==> Pervasive
Significant Change Date: 2001-04-17, 2003-09-23
Avoidance: Workaround
Responsible Manager: rupinder.judge@ebay, Chuck.Campbell@Sun.COM
Original Admin Info: [WF 22-Nov-2005, karened: updated per Kuswandi.Kohar of PTS Storage with new Bug, CF etc]

Engineering Notification Interval: 30

This document has been imported from KMS Creator and may need adjustment before re-publishing.

This imported document has been reviewed/adjusted by:
Review Name:
Review Date:

Original KMS Creator attributes below:

--- PLEASE DO NOT MAKE ANY CHANGES BELOW THIS LINE! ---

Sun Alert ID: 26464
Synopsis: Sun StorEdge T3 and Sun StorEdge 3310 SCSI Array's Controller May Disable Without Warning When Probed with Third Party Network Security Software
Category: Availability
Product: Sun StorEdge T3, Sun StorEdge 3310 SCSI Array, Sun StorEdge 3510 FC Array
BugIDs: 4356418, 4435299, 4527674, 4912150
Avoidance: Workaround
State: Resolved
Date Released: 17-Apr-2001, 23-Sep-2003
Date Closed: 23-Sep-2003
Date Modified: 23-Sep-2003, 09-Oct-2003
Escalation IDs: 529331, 527479, 548117
Pending Patches:
Resolution Patches: none, -, see, above
FIN: I0667-1
FCO:
Date Submitted: 12-Apr-2001
Submitter: dave.bruce@sun.com
Responsible Engineer: caroline.kahn@sun.com
Responsible Manager: rupinder.judge@ebay, Chuck.Campbell@Sun.COM
CTE group: CPRE NWS US
Responsible Writer: karen.edwards@central.sun.com
Distribution: Public SunSolve

Workflow History:

WF State: Issued, 09-Oct-2003, Karen Edwards
WF Note: updated per younan

WF State: Issued, 23-Sep-2003, Karen Edwards
WF Note: Resolved and put to Public SunSolve

WF State: Issued, 22-Sep-2003, Karen Edwards
WF Note: have been given updates - but is it resolved or not?

WF State: Issued, 13-Jun-2003, Karen Edwards
WF Note: This issue was resolved a long time ago.

WF State: Issued, 31-Jan-2002, Karen Edwards
WF Note: spoke w/ Bob and he said there is no short term resolution. Asked to have email notification set to 30 days

WF State: Issued, 16-Jan-2002, Karen Edwards
WF Note: ok for contract sunsolve

WF State: Issued, 15-Jan-2002, Karen Edwards
WF Note: have asked eng for update on final solution

WF State: Issued, 13-Aug-2001, Karen Edwards
WF Note: [oldtodo 05-Sep-2001: waiting for reply from eng]

WF State: Issued, 18-May-2001, Karen Edwards
WF Note: [oldtodo 15-Jul-2001: check status of resolution]

WF State: Issued, 17-Apr-2001, Karen Edwards
WF Note: got approval

WF State: Draft, 16-Apr-2001, Karen Edwards
WF Note: requesting sfa-signoff

WF State: Draft, 16-Apr-2001, Karen Edwards
WF Note: [oldtodo 15-May-2001: check status of resolution]

WF State: Draft, 13-Apr-2001, Karen Edwards
WF Note: sent to sunalert_review

WF State: Draft, 13-Apr-2001, Karen Edwards
WF Note: Article created.

Exported from KMS Creator Sat May 21 08:41:38 2005 GMT, olaf.reineke@sun.com
Internal SA-FAB Eng Submission
Sun StorEdge T3 and Sun StorEdge 3310 SCSI Array's Controller May Disable Without Warning When Probed with Third Party Network Security Software

Product_uuid
2a6d7d50-0a18-11d6-8e0b-f0bd33b24928|Sun StorageTek T3 Array
2cd2e7d2-2980-11d7-9c3f-c506fe37b7ef|Sun StorageTek 6120 Array
3db30178-43d7-4d85-8bbe-551c33040f0d|Sun StorageTek 3310 SCSI Array
58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback