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-71-1188053.1
Update Date:2010-10-25
Keywords:

Solution Type  Technical Instruction Sure

Solution  1188053.1 :   How to find the host port loop id on a Sun Storage[TM] 2540 ?  


Related Items
  • Sun Storage 2540 Array
  •  
  • Sun Storage Common Array Manager (CAM)
  •  
Related Categories
  • GCS>Sun Microsystems>Storage Software>Modular Disk Device Software
  •  




In this Document
  Goal
  Solution


Applies to:

Sun Storage Common Array Manager (CAM) - Version: 6.0 to 6.5 - Release: 6.0 to 6.5
Sun Storage 2540 Array - Version: Not Applicable to Not Applicable   [Release: NA to NA]
Information in this document applies to any platform.

Goal

Due to the <SunBug 6880697> Incorrect loop ID returned by the getObjectGraph_MT in a 2540, when a Sun Storage[TM] 2540 is directly connected to a server, Sun StorageTek[TM] Common Array Manager is returning N/A for the loop ID of the corresponding host port.

The intend of this document is to provide you with the procedure to find the effective loop ID for the host ports connected in Direct Attach to the server.

Solution

  1. Collect a supportdata from the array. Reference <Document 1002514.1> Collecting Support Data for Array Using Sun StorageTek[TM] Common Array Manager.

  2. Extract the file stateCaptureData.dmp from the supportdata zip file.

  3. Open this file with your text editor and look for the entry "FunctionId: FC_DUMP Function: fcDump". This will give you two outputs, one for the controller A and the second for the controller B. The loop ID is indicated under the "Our Port ID" column.


    Example:

    Controller A
    FunctionId: FC_DUMP Function: fcDump on controller A

    Executing  fcDump(0,0,0,0,0,0,0,0,0,0):


    fcAll (Tick 0014681055) ==> 01/15/09-01:28:30 (GMT)

    1932-A          Our  Num  ::...Exchange Counts...:: Num  ..Link Up..
    Chip  LinkStat  Port Port ::                     :: Link  Bad  Bad
                     ID  Logi ::Open    Total  Errors:: Down  Char Frame
    2-Src Up-Loop     ef    2 ::  0         94     33::    2     0     2
    3-Src Down---      0    0 ::  0          0      0::    1     0     0


    Controller B
    FunctionId: FC_DUMP Function: fcDump on controller B

    Executing  fcDump(0,0,0,0,0,0,0,0,0,0):


    fcAll (Tick 0014675460) ==> 01/15/09-01:28:49 (GMT)

    1932-B          Our  Num  ::...Exchange Counts...:: Num  ..Link Up..
    Chip  LinkStat  Port Port ::                     :: Link  Bad  Bad
                     ID  Logi ::Open    Total  Errors:: Down  Char Frame
    2-Src Down---      0    0 ::  0          0      0::    1     0     0
    3-Src Down---      0    0 ::  0          0      0::    1     0     0



    The host ports are indicated by "Src" (aka Source) and there is two host ports per ST2540:

    2-Src
    3-Src

    In the above example, the first host port from controller A uses the loop ID 0xef, while the other host ports from this controller A or the controller B are not connected (reported as Down---).




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