Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1010467.1 : Sun StorEdge[TM] 33x0 and 35x0:Symptom:SCCLI Fails to Find Controller
PreviouslyPublishedAs 214381 When using the Storage 3000 Family command line interface(CLI) to manage either the 33x0 or 35x0 array, the CLI fails to discover the array.
Applies to:Sun Storage 3310 SCSI ArraySun Storage 3510 FC Array Sun Storage 3320 SCSI Array - Version: Not Applicable and later [Release: NA and later] Sun Storage 3511 SATA Array - Version: Not Applicable and later [Release: NA and later] All Platforms SymptomsWhen attempting to attach to the array inband, may receive the followingmessage: # /usr/sbin/sccli sccli: no manageable devices found sccli: Type "sccli help" for valid commands. ChangesThis message is typically seen when no logical drives are available .CauseIn order for the host running the sccli command to discover the array controller, at least one logical drive must be lun mapped and available to the server.Note – Some versions of operating system software or utilities might not display all mapped LUNs if there is no partition or logical drive mapped to LUN 0. SolutionTo check the status of logical drives and map a lun: 1) Establish a serial connection to array controller's serial port 2) Start tip session to array controller # tip -38400 /dev/term/[a or b] 3) Refresh screen with cntrl-l 4) Select VT100 --> "view and edit host luns" 5) Select host channel to host lun map 6) Select option to lun map a logical drive 7) Host lun map a logical drive 8) End tip session Enter key, "~", and followed by "." For 33x0: 9) Ensure host's /kernel/drv/sd.conf have an entry to support the target ID and lun number for the logical drive that was just host lun mapped For example, if logical drive was host lun mapped to lun 1 with host channel PID or SID set to 18, then the following entry is needed in sd.conf name="sd" class="scsi" target=18 lun=1; 10)Initiate a reconfiguration reboot if any changes were made to sd.conf # init 0 ok boot -r 11)If sd.conf was not modified, then use "devfsadm -Cv" # devfsadm -Cv For 35x0 : 12)Run format to look for the host lun 13)Execute a "luxadm probe" to have Solaris[TM] Operating environment scan for device entries # luxadm probe 14)Run format to check the status of 35x0 logical drive on the host 15)Determine WWN of host channel that logical drive was host lun mapped to 16)Start tip session to array controller # tip -38400 /dev/term/[a or b] 17)Refresh screen with cntrl-l 18)Select VT100 --> "view and edit SCSI channels" 19)Select host channel --> "view channel host-id/Wwn" 20)End tip session Enter key, "~", and followed by "." 21)Execute "cfgadm -al" to determine which fibre-channel controllers to configure in the logical drive # cfgadm -al Ap_Id Type Receptacle Occupant Condition c2 fc-fabric connected unconfigured unknown c2::266000c0ffe01589 ESI connected unconfigured unknown The controller number associate with 35x0's host channel WWN is the one to configure (ie c2 since 266000c0ffe01589 is WWN of 3510 host channel) 22)Use "cfgadm -c configure" to configure in the logical drive # cfgadm -c configure c2::266000c0ffe01589 23)Run format to confirm 35x0 logical drive is there 24)Execute sccli to discover array controller # sccli sccli: selected device /dev/rdsk/c4t0d0s2 [SUN StorEdge[TM] 3310 SN#0000A8] sccli> # sccli sccli: selected device /dev/rdsk/c12t216000C0FF801589d1s2 [SUN StorEdge[TM] 3510 SN#001589] sccli> sccli is now able to find the array controller Product Sun StorageTek 3510 FC Array Sun StorageTek 3511 SATA Array Sun StorageTek 3310 SCSI Array Sun StorageTek 3320 SCSI Array 3310, 3320, 3510, 3511, sccli Previously Published As 71641 Change History Date: 2010-08-10 User Name: Vickie Williams-Eli Action: Approved Comment: KE quality checklist applied - Published Version: 0 Action: Approved Comment: Looks good, approved. Version: 0 Attachments This solution has no attachment |
||||||||||||
|