| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Sun Alert Sure Solution 1019498.1 : Sun StorageTek 25x0 and 6140 Arrays may send wrong Network packets, causing the Sun StorageTek Common Array Manager (CAM) Host to Lose the Network Connection to the Array
PreviouslyPublishedAs 240105 Bug Id <SUNBUG: 6721662> Product Sun StorageTek 2540 Array Sun StorageTek 2530 Array Sun StorageTek 2510 Array Sun StorageTek 6140 Array Date of Workaround Release 01-Aug-2008 Date of Resolved Release 21-Oct-2008 Sun StorageTek 25x0 and 6140 Arrays may send wrong Network packets, causing the Sun StorageTek Common Array Manager (CAM) Host to Lose the Network Connection to the Array 1. Impact Sun StorageTek 25x0 and 6140 arrays with certain firmware may send wrong network packets to the network. This can cause the Sun StorageTek Common Array Manager(CAM) host to lose the network connection to the array. This may, in turn, prevent out-of-band array management (via the network) when using CAM. 2. Contributing Factors This issue can occur on the following platforms:
When a host with Sun StorageTek Common Array Manager (CAM) installed tries to access an array through CAM, the array may send bad network packets coming from the host (via CAM) back to the network (it forwards the same packets on the network again). If both the CAM host and array controllers are attached to a network switch, the network switch stores the CAM host's MAC address information on the switch port connected to the array, which causes the CAM host to lose the network connection to the array. 3. Symptoms Once the connection is lost, the "sscs list event" command may return messages similar to the following: ("test2540" is the array name of ST2540 in this example): $ sscs list eventOr, the sscs command would return a message similiar to the following: $ sscs list array test2540Or the following error message: $ sscs list array test2540Sun StorageTek Common Array Manager (CAM) would return the following error message when clicking on the array name link of the Sun StorageTek 25x0 array: (!) An error occurred during the operation to retrieve data.Or: 4. Workaround(!) The array test2540 could not be contacted. By default, the CAM host communicates with the arrays out-of-band over Ethernet. To provide temporary avoidance of this issue, configure in-band management (with CAM version 6.0 or later) to travel over the data path (using Fibre Channel, etc.) between the data host and the array instead. To configure In-Band Management with CAM, please refer to "Sun StorageTek Common Array Manager Software Installation Guide" (Version 6.0 or later). Sun StorageTek Common Array Manager Software 6.0 Documentation can be found at: 5. Resolution This issue is addressed in the following releases: The 25x0 and 6140 RAID controller firmware fix is available for CAM version 6.1.0 with the following patches: SPARC Platform
SPARC Platform
SPARC Platform
However, even after upgrading the RAID controller firmware via network, the original network communication issue may happen. In order to temporarily avoid the network communication issue while upgrading RAID controller firmware, please follow the procedure below. 1) Install one of patches listed above to the management host (CAM host). 2) Check the IP address of ST25x0 controller registered on CAM host with the following commands. These commands need to be executed on CAM host: $ sscs login -h localhost -u rootExample: $ sscs list devices3) Run the following ping command with the IP address which you got in the previous step in order to issue ping to the RAID controller every one second repeatedly. (This command needs to be executed on CAM host.) Solaris: $ ping -s <RAID_Controller_IP_address>Windows: > ping -t RAID_Controller_IP_addressLinux: Please contact your Linux OS support provider to ask the method to issue a ping command to the RAID controller every one second repeatedly. 4) While running the ping command , perform the firmware upgrade using CAM's web interface. 5) Once the firmware upgrade ends, then stop the ping command executed in step 3. To stop the ping command, input ^C (Ctrl C) on the shell window where ping command is executed. Modification History 26-Aug-2008: Updated Symptoms and Resolution sections 09-Sep-2008: Updated Product, Impact, Contributing Factors and Resolution sections 12-Sep-2008: Updated Resolution section for clarification 21-Oct-2008: Updated Contributing Factors and Resolution sections; Resolved References<SUNPATCH: 137934-01><SUNPATCH: 137934-02> <SUNPATCH: 137935-01> <SUNPATCH: 137935-02> <SUNPATCH: 137936-01> <SUNPATCH: 137936-02> <SUNPATCH: 139034-01> <SUNPATCH: 139035-01> <SUNPATCH: 139036-01> <SUNPATCH: 139339-01> <SUNPATCH: 139340-01> <SUNPATCH: 139341-01> Internal Comments Please send technical questions to the following email: [email protected] and CC the following persons: Internal Contributor/Submitter Internal Eng Responsible Engineer Internal Services Knowledge Engineer Internal Contributor/submitter [email protected] Internal Eng Responsible Engineer [email protected] Internal Services Knowledge Engineer [email protected] Internal Eng Business Unit Group NWS (Network Storage) Internal Escalation ID 11250405, 38080371, 11230084, 11205155 Internal Resolution Patches 137934-01, 137934-02, 137935-01, 137935-02, 137936-01, 137936-02, 139034-01, 139035-01, 139036-01, 139339-01, 139340-01, 139341-01 ReferencesSUNPATCH:137934-01SUNPATCH:137934-02 SUNPATCH:137935-01 SUNPATCH:137935-02 SUNPATCH:137936-01 SUNPATCH:137936-02 SUNPATCH:139034-01 SUNPATCH:139035-01 SUNPATCH:139036-01 SUNPATCH:139339-01 SUNPATCH:139340-01 SUNPATCH:139341-01 ReferencesSUNPATCH:137934-01SUNPATCH:137934-02 SUNPATCH:137935-01 SUNPATCH:137935-02 SUNPATCH:137936-01 SUNPATCH:137936-02 SUNPATCH:139034-01 SUNPATCH:139035-01 SUNPATCH:139036-01 SUNPATCH:139339-01 SUNPATCH:139340-01 SUNPATCH:139341-01 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||