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-71-1991213.1
Update Date:2017-05-05
Keywords:

Solution Type  Technical Instruction Sure

Solution  1991213.1 :   FS System: How to SSH to Drive Enclosure RAID Console  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Goal
Solution
 Procedure to SSH to a Drive Enclosure
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: How to doc

Applies to:

Oracle FS1-2 Flash Storage System - Version 6.1.6 and later
Information in this document applies to any platform.

Goal

This document describes the steps to connect to a Drive Enclosure using SSH.

Solution

Procedure to SSH to a Drive Enclosure

The example below shows how to SSH to ENCLOSURE-05.

STEP 1: Collect a topology report using fscli.

 # fscli topology -download -topomap <filename>

Topology is updated at:
Fri Mar 13 00:06:43 2015
------- CONN MAP FOR /CONTROLLER-01 50800200015922E0 -------
Controller has 3 HBAs installed
HBA IDX 0 is installed in PCI slot 3
/CONTROLLER-01 50800200015922E0 : HBA 0 : Port 0 <==  ==> /ENCLOSURE-08 5080020001689032 [50800200016498FF]: IOM 0 : Port 0
/CONTROLLER-01 50800200015922E0 : HBA 0 : Port 1 <==  ==> /ENCLOSURE-05 5080020001688EC9 [5080020001683F7F]: IOM 0 : Port 0
/CONTROLLER-01 50800200015922E0 : HBA 0 : Port 2 <==  ==> /CONTROLLER-02 50800200015922E1 : HBA 0 : Port 2
/CONTROLLER-01 50800200015922E0 : HBA 0 : Port 3 <==  ==> /CONTROLLER-02 50800200015922E1 : HBA 0 : Port 3
HBA IDX 1 is installed in PCI slot 6
/CONTROLLER-01 50800200015922E0 : HBA 1 : Port 0 <==  ==> /ENCLOSURE-07 5080020001688F01 [50800200016842BF]: IOM 0 : Port 0
/CONTROLLER-01 50800200015922E0 : HBA 1 : Port 1 <==  ==> /ENCLOSURE-04 5080020001688EC4 [5080020001682EBF]: IOM 0 : Port 0
/CONTROLLER-01 50800200015922E0 : HBA 1 : Port 2 <==  ==> /CONTROLLER-02 50800200015922E1 : HBA 1 : Port 2
/CONTROLLER-01 50800200015922E0 : HBA 1 : Port 3 <==  ==> /CONTROLLER-02 50800200015922E1 : HBA 1 : Port 3
HBA IDX 2 is installed in PCI slot 2
/CONTROLLER-01 50800200015922E0 : HBA 2 : Port 0 <==  ==> /ENCLOSURE-06 5080020001688EF9 [5080020001683E7F]: IOM 0 : Port 0
/CONTROLLER-01 50800200015922E0 : HBA 2 : Port 1 <==  ==> /ENCLOSURE-01 5080020001475003 [50800200014B5CFF]: IOM 0 : Port 0
/CONTROLLER-01 50800200015922E0 : HBA 2 : Port 2 <==  ==> /CONTROLLER-02 50800200015922E1 : HBA 2 : Port 2
/CONTROLLER-01 50800200015922E0 : HBA 2 : Port 3 <==  ==> /CONTROLLER-02 50800200015922E1 : HBA 2 : Port 3


------- CONN MAP FOR /CONTROLLER-02 50800200015922E1 -------
Controller has 3 HBAs installed
HBA IDX 0 is installed in PCI slot 3
/CONTROLLER-02 50800200015922E1 : HBA 0 : Port 0 <==  ==> /ENCLOSURE-08 5080020001689032 [508002000164C23F]: IOM 1 : Port 0
/CONTROLLER-02 50800200015922E1 : HBA 0 : Port 1 <==  ==> /ENCLOSURE-02 50800200014758F4 [508002000144063F]: IOM 1 : Port 0
/CONTROLLER-02 50800200015922E1 : HBA 0 : Port 2 <==  ==> /CONTROLLER-01 50800200015922E0 : HBA 0 : Port 2
/CONTROLLER-02 50800200015922E1 : HBA 0 : Port 3 <==  ==> /CONTROLLER-01 50800200015922E0 : HBA 0 : Port 3
HBA IDX 1 is installed in PCI slot 6
/CONTROLLER-02 50800200015922E1 : HBA 1 : Port 0 <==  ==> /ENCLOSURE-07 5080020001688F01 [508002000148EA7F]: IOM 1 : Port 0
/CONTROLLER-02 50800200015922E1 : HBA 1 : Port 1 <==  ==> /ENCLOSURE-04 5080020001688EC4 [508002000168543F]: IOM 1 : Port 0
/CONTROLLER-02 50800200015922E1 : HBA 1 : Port 2 <==  ==> /CONTROLLER-01 50800200015922E0 : HBA 1 : Port 2
/CONTROLLER-02 50800200015922E1 : HBA 1 : Port 3 <==  ==> /CONTROLLER-01 50800200015922E0 : HBA 1 : Port 3
HBA IDX 2 is installed in PCI slot 2
/CONTROLLER-02 50800200015922E1 : HBA 2 : Port 0 <==  ==> /ENCLOSURE-03 5080020001475924 [50800200014C2AFF]: IOM 1 : Port 0
/CONTROLLER-02 50800200015922E1 : HBA 2 : Port 1 <==  ==> /ENCLOSURE-01 5080020001475003 [50800200014B64FF]: IOM 1 : Port 0
/CONTROLLER-02 50800200015922E1 : HBA 2 : Port 2 <==  ==> /CONTROLLER-01 50800200015922E0 : HBA 2 : Port 2
/CONTROLLER-02 50800200015922E1 : HBA 2 : Port 3 <==  ==> /CONTROLLER-01 50800200015922E0 : HBA 2 : Port 3

Or

# fscli topology -list  >output.txt

Search ouput.txt for ENCLOSURE-05

EnclosureConnectivity
    Controller
        Fqn      : /CONTROLLER-01
        Id       : 50800200015922E0
        HbaSlot  : 3
        Port     : 1
        Enclosure
            Fqn      : /ENCLOSURE-05
            Id       : 5080020001688EC9
        Enclosure
            Fqn      : /ENCLOSURE-02
            Id       : 50800200014758F4

 

EnclosureConnectivity
    Controller
        Fqn      : /CONTROLLER-02
        Id       : 50800200015922E1
        HbaSlot  : 3
        Port     : 1
        Enclosure
            Fqn      : /ENCLOSURE-02
            Id       : 50800200014758F4
        Enclosure
            Fqn      : /ENCLOSURE-05
            Id       : 5080020001688EC9

 


STEP 2: Identify the connection for the Drive Enclosure.

The output above shows ENCLOSURE-05 is connected to Controller-01, HBA slot 3 and Controller-02, HBA slot 3.

Note: It may not be the same HBA for each Controller, so check

  

STEP 3: SSH to the Pilot as root. 

 

STEP 4: Determine the appropriate Controller and RAID console. Use the following for reference when determining which raidconsole to use.

  • raidconsole0 = Any Enclosures plugged into slot 3 on the Controller
  • raidconsole1 = Any Enclosures plugged into slot 6 on the Controller
  • raidconsole2 = Any Enclosures plugged into slot 2 on the Controller

Because ENCLOSURE-05 is plugged into slot 3 on the Controller, the correct choice in this example is raidconsole0.

Find the appropriate Controller from /etc/nodemames.

 [root@pilot1 ~]# cat /etc/nodenames
172.30.80.2 WN2008fffffffffff2 WN2008000101000000 mgmtnode
172.30.80.3 WN2009fffffffffffa
172.30.80.129 WN50800200015922E1 WN2008000101000001
172.30.80.128 WN50800200015922E0

STEP 5: Log in to the appropriate Controller and raidconsole from the pilot

[root@pilot1 ~]# ssh raidconsole0@172.30.80.128
raidconsole0@172.30.80.128's password:

OK
FCRoot>SES::PollEnclosureStatus: Mon Mar 23 09:40:07 2015 976.660739 msec

Entering: SES::ParseSesPage_02 for Enclosure 0x02D0
Entering: SES::ParseSesPage_02 for Enclosure 0x02D3
Entering: SES::ParseSesPage_02 for Enclosure 0x02D1

 

Note: After providing the password a second return is needed to see the raidconsole prompt.

 

STEP 6: Type "scsi" to access the SCSI submenu.

 

STEP 7: Type "chk" to display output showing the target numbers for the Drive Enclosures on this string. Use the WWNN discovered in Step 1 above to identify the correct target. In this case, WWNN 5080020001688EC9 for ENCLOSURE-05 indicates Target 1.

NOTE:  "scsi> chk" will produce a lot of output. Cut and paste this into a notepad or word document and search for the WWNN of the Drive Enclosure in question.

Target 0000-0001 ,  WWNN: 50.80.02.00.01.68.8E.C9

 Scroll down to see the LUNs and drives

============================================
Target 0000-0001 ,  WWNN: 50.80.02.00.01.68.8E.C9

LUN 0000    Online          01 Idle      Media 00   BSize   520.    StorageClass 02
     RAID 5         02 Clean  
     RAID 5_1MB     00 Invalid  
     RAID 10        02 Clean  
     RAID 10_1MB    00 Invalid  
     RAID 5S        02 Clean  
     RAID 10S       02 Clean  
     RAID 6         02 Clean  
     RAID C         02 Clean  

LUN 0001    Online          01 Idle      Media 00   BSize   520.    StorageClass 02
     RAID 5         02 Clean  
     RAID 5_1MB     00 Invalid  
     RAID 10        02 Clean  
     RAID 10_1MB    00 Invalid  
     RAID 5S        02 Clean  
     RAID 10S       02 Clean  
     RAID 6         02 Clean  
     RAID C         02 Clean  
------------------------------------------------------
totalDrives 0000-0018
Drv  Owner Media BSize   AccessOn  PhySt      LogSt
00   00    00    520.     CU0CU1    64_Online  06_InUse    
01   00    00    520.     CU0CU1    64_Online  06_InUse    
02   00    00    520.     CU0CU1    64_Online  06_InUse    
03   00    00    520.     CU0CU1    64_Online  06_InUse    
04   00    00    520.     CU0CU1    64_Online  06_InUse    
05   00    00    520.     CU0CU1    64_Online  06_InUse    
06   00    00    520.     CU0CU1    64_Online  06_InUse    
07   00    00    520.     CU0CU1    64_Online  06_InUse    
08   00    00    520.     CU0CU1    64_Online  06_InUse    
09   00    00    520.     CU0CU1    64_Online  06_InUse    
0A   00    00    520.     CU0CU1    64_Online  06_InUse    
0B   00    00    520.     CU0CU1    64_Online  06_InUse    
0C   00    00    520.     CU0CU1    64_Online  06_InUse    
0D   00    00    520.     CU0CU1    64_Online  06_InUse    
0E   00    00    520.     CU0CU1    64_Online  06_InUse    
0F   00    00    520.     CU0CU1    64_Online  06_InUse    
10   00    00    520.     CU0CU1    64_Online  06_InUse    
11   00    00    520.     CU0CU1    64_Online  06_InUse    
12   00    00    520.     CU0CU1    64_Online  06_InUse    
13   00    00    520.     CU0CU1    64_Online  06_InUse    
14   00    00    520.     CU0CU1    64_Online  06_InUse    
15   00    00    520.     CU0CU1    64_Online  06_InUse    
16   00    00    520.     CU0CU1    64_Online  06_InUse    
17   00    00    520.     CU0CU1    64_Online  06_InUse    
--------------------------------------------
Target   1. Temperatures:   0.   0.   0.   0.
============================================

 

 CTRL+C to return to the Pilot SSH session and type  exit  to end the session.

 

 

 

References

<NOTE:1989554.1> - FS System: How to Manually Fail a Drive from the Drive Enclosure RAID Console
<NOTE:1970990.1> - FS System: How to Read and Interpret the FS1-2 CLI Topology Command

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback