Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1002465.1 : Verifying STMS (mpxio) Health
PreviouslyPublishedAs 203438 Description In order to provide you the most accurate fix, please validate that each statement under the symptoms below is true for your environment. These symptoms will hyperlink you into a relevant content that will 1) tell you how to validate the listed symptom and 2) how to fix the symptom if it is true for your environment. The listed symptoms are ordered in the most appropriate sequence to isolate the issue and be certain about the related fix. Please do not skip a step. Symptoms: - Device path is disabled - Can't fail over device path - Can't see both device paths - STMS is disabled Environmental Considerations: - This document assumes the customer is trying or is using STMS/MPXIO. Steps to Follow Verifying STMS (mpxio) Health NOTE: This document is a sub-set of <Document: 1009557.1> : "Troubleshooting Fibre Channel Devices from the OS." The steps below will help confirm that STMS is being used and both paths are seen. 1. Validate that STMS is enabled: Check that the mpxio-disable parameter is set to "no". *Solaris[TM] 7,8,9 check /kernel/drv/scsi_vhci.conf *Solaris[TM] 10 only /kernel/drv/fp.conf Example: mpxio-disable="no"; If mpxio-disable is set to "yes" in the scsi_vhci.conf or fp.conf file, STMS is disabled for the entire system, no matter what. Change the value to "no" to enable mpxio for the entire system and reconfigure reboot the host if STMS is the desired failover software. 2. Validate that the Logical paths exist: Use the "luxadm probe" command to verify that the logical paths to the devices are available. T3 Example: # luxadm probe No Network Array enclosures found in /dev/es Found Fibre Channel device(s): Node WWN:50020f200000c21e Device Type:Disk device Logical Path:/dev/rdsk/c3t60020F200000C21E43E8E3BA00029D48d0s2 Node WWN:50020f20000035df Device Type:Disk devive Logical Path: /dev/rdsk/c3t60020F200000C21E43E8E3DC0008B758d0s2 3510 Example: # luxadm probe No Network Array enclosures found in /dev/es Found Fibre Channel device: Node WWN:206000c0ff000f26 Device Type:Disk device Logical Path:/dev/rdsk/c2t600C0FF000000000000F264CBFBA6F00d0s2 3. Validate paths using the "luxadm display <logical path>" command. Check that the primary and secondary paths are configured. T3 Example: # luxadm display /dev/rdsk/c3t60020F200000C21E43E8E3BA00029D48d0s2 DEVICE PROPERTIES for disk:dev/rdsk/c3t60020F200000C21E43E8E3BA00029D48d0s2 Vendor: SUN Product ID: T300 Revision: 0301 Serial Num: Unsupported Unformatted capacity: 51205.500 Mbytes Write Cache: Enabled Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0x0 Device Type: Disk device Path(s): /dev/rdsk/c3t60020F200000C21E43E8E3BA00029D48d0s2 /devices/scsi_vhci/ssd@g60020f200000c21e43e8e3ba00029d48:c,raw Controller /devices/pci@1f,0/pci@1/SUNW,qlc@3/fp@0,0 Device Address 50020f23000035df,0 Host controller port WWN 210000e08b09b58c Class secondary State STANDBY Controller /devices/pci@1f, 0/pci@1/SUNW,qlc@3,1/fp@0,0 Device Address 50020f230000c21e,0 Host controller port WWN 210100e08b29b58c Class primary State ONLINE 3510 Example: # luxadm display /dev/rdsk/c2t600C0FF000000000000F264CBFBA6F00d0s2 DEVICE PROPERTIES for disk: /dev/rdsk/c2t600C0FF000000000000F264CBFBA6F00d0s2 Vendor: SUN Product ID: StorEdge 3510 Revision: 415F Serial Num: 000F264CBFBA Unformatted capacity: 241332.000 Mbytes Write Cache: Enabled Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0xffff Device Type: Disk device Path(s): /dev/rdsk/c2t600C0FF000000000000F264CBFBA6F00d0s2 devices/scsi_vhci/ssd@g600c0ff000000000000f264cbfba6f00:c,raw Controller /devices/pci@1f,4000/SUNW,qlc@4,1/fp@0,0 Device Address 256000c0ffc00f26,0 Host controller port WWN 210100e08b27eaa6 Class primary State ONLINE NOTE: If the steps above are true then STMS is being used and both paths are seen, return to step 4 in the <Document: 1009557.1> "Troubleshooting Fibre Channel Devices from the OS." If both paths are not seen from luxadm proceed to step 4. 4. Validate the out of band connection to the array: Log into the array. If you are unable to connect, refer to <Document: 1012660.1> : "Can't Connect to Sun StorEdge [TM] Array" 5. Validate that the correct array is being accessed. For T3 , compare the output of "port list" with the WWN recorded ( luxadm -e dumpmap <device> ) in step 2 of <Document: 1009556.1> How to verify HBA Connectivity. Example: storage-t3b:/:<1>port list port targetid addr_type status host wwn u1p1 1 hard online sun 50020f230000c21e u2p1 2 hard online sun 50020f23000035df For 351x , compare the output of "show port" with the WWN recorded ( luxadm -e dumpmap <device> ) in step 2 of <Document: 1009556.1> : How to verify HBA Connectivity. Example: # luxadm -e dump_map dev/rdsk/c2t600C0FF000000000000F264CBFBA6F00d0s2 Pos AL_PA ID Hard_Addr Port WWN Node WWN Type 0 1 7d 0 210100e08b27eaa6 200100e08b27eaa6 0x1f (UnknownType,Host Bus Adapter) 1 9f 2c 9f 256000c0ffc00f26 206000c0ff000f26 0x0 (Disk device) sccli> show port Ch Id WWPN ------------------------- Sun StorageTek Traffic Manager 4.5 Software (Localized) Internal Comments For internal Sun use only. This document contains normalized content and is managed by the the Domain Lead (s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below: [email protected] The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK MPXIO, STMS, path offline, scsi_vhci, failover, T3, T3+, 3510, 3511, 351x, audited Previously Published As 86544 Change History Date: 2007-11-13 User Name: 7058 Action: Approved Comment: External section of doc had reference to an internal link (sunsolve2.central). Fixed. Version: 9 Date: 2007-11-13 User Name: 7058 Action: Update Started Comment: Fix links Version: 0 Attachments This solution has no attachment |
||||||||||||
|