On a Sun StorEdge 3510 FC Array, parity checks or Logical Drive (LD) initialization may take a very long time (up to 12 hours) if there is an active telnet session to the array.

This issue can occur in the following releases:

SPARC Platform

• Sun StorEdge 3510 FC Array with firmware revision 3.27K or lower (patch 113723-02)

Notes: The described issue will only occur when there is an active telnet session to the Sun StorEdge 3510 FC Array. Other remote array management tools (e.g. serial connections to the array) will not cause the described issue. An array's current firmware revision can be determined by logging into the array by means of a telnet or serial connection and selecting "view system information" from the menu.

Should the descibed issue occur, initialization of a Logical Drive (LD) on a Sun StorEdge 3510 FC Array will take more than 4 hours with an active telnet connection to the array. Also, paritiy checks will take a very long time when a telnet connection to the array is active. No error messages are generated.

To work around this issue, close the telnet session, and avoid using telnet to access the Sun StorEdge 3510 Array. Manage the array using sccli (Sun StorEdge 3XX0 Command Line Interface), sscs (Sun StorEdge 3XX0 Configuration Service Console) or a serial connection.

This issue is addressed in the following releases:

SPARC Platform

• Sun StorEdge 3510 FC Array with firmware revision 3.27M or later (available in patch 113723-03)

This solution has no attachment