![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||
Solution Type Technical Instruction Sure Solution 1433014.1 : Sun Storage 7000 Unified Storage System: How to verify that the multipathing software ( MPxIO / VxDMP) is optimal
In this Document
Applies to:Sun ZFS Storage 7420 - Version All Versions and laterSun Storage 7310 Unified Storage System - Version All Versions and later Sun Storage 7410 Unified Storage System - Version All Versions and later Sun ZFS Storage 7320 - Version All Versions and later Sun Storage 7110 Unified Storage System - Version All Versions and later 7000 Appliance OS (Fishworks) GoalHow to verify that the multipathing software (MPxIO / VxDMP) used to connect to the 7000 appliance is optimal SolutionThe functionality of FC target devices was added to the Sun 7000 series with the introduction of appliance software 2010.Q1. Properly configuring an FC initiator in an ALUA environment requires an ALUA-aware driver, and may require initiator-specific tuning. The following initiators have been tested and are known to work in a cluster: Sun Storage Traffic Manager(STMS or MPxIO)Even though FC target on a clustered appliance was qualified with OpenSolaris 2010.03 and Solaris 10 10/09 ( S10U8 ), users must also apply MPxIO Patch:143120-03 (sparc), Patch:143121-03 (x86) or later to get fixes for luxadm display /dev/rdsk/c4t600144F0F8D6944400004E6090280004d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c4t600144F0F8D6944400004E6090280004d0s2 Vendor: SUN Product ID: ZFS Storage 7320 Revision: 1.0 Serial Num: Unformatted capacity: 3072.000 MBytes Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0x0 Device Type: Disk device Path(s): /dev/rdsk/c4t600144F0F8D6944400004E6090280004d0s2 /devices/scsi_vhci/disk@g600144f0f8d6944400004e6090280004:c,raw Controller /dev/cfg/c2 Device Address 21000024ff2e4ec7,1 Host controller port WWN 21000024ff2a967c Class secondary State STANDBY Controller /dev/cfg/c2 Device Address 2101001b323baa4c,1 Host controller port WWN 21000024ff2a967c Class primary State ONLINE Controller /dev/cfg/c3 Device Address 21000024ff2e4ec6,1 Host controller port WWN 21000024ff2a967d Class secondary State STANDBY Controller /dev/cfg/c3 Device Address 2100001b321baa4c,1 Host controller port WWN 21000024ff2a967d Class primary State ONLINE
1.To enable MPxIO:
# stmsboot -D fp -e 2.To disable MPxIO: # stmsboot -D fp -d 3.To verify the state: # mpathadm show LU
vxdmpadm settune dmp_fast_recovery=off
vxdmpadm settune dmp_health_time=0 vxdmpadm settune dmp_path_age=0 vxdmpadm settune dmp_lun_retry_timeout= <atleast as much as the MPxIO's timeout > , say 200
Veritas Dynamic Multi-Pathing(DMP)Please refer to Symantec's guidelines in the following Symantec technote: Disable MPxIO on the Solaris hostFor Solaris 9, this is done by setting mpxio-disable="yes" in /kernel/drv/scsi_vhci.conf file and rebooting. Install the required Storage Foundation VRTSvxvm patches.Required Storage Foundation 5.1 RP2 Patches Install the latest Storage Foundation ASL/APM package supporting the 7000 seriesRequired Storage Foundation 5.1 ASL/APM package For Clustered 7000s, set DMP parameters to support takeover / failback commands.In order to support clustered Sun ZFS Storage Appliance takeover / failback commands, the following DMP tunables need to be set: vxdmpadm settune dmp_health_time=0
vxdmpadm settune dmp_path_age=0 vxdmpadm settune dmp_lun_retry_timeout=200
Check the multipathed device paths# vxdisk list sun_73100_0
Device: sun_73100_0 devicetag: sun_73100_0 type: auto hostid: xxxx disk: name=sun_73100_0 id=1270229856.12.isv-2000a group: name=7310-h2-dg id=1270236420.52.isv-2000a info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 flags: online ready private autoconfig autoimport imported pubpaths: block=/dev/vx/dmp/sun_73100_0s2 char=/dev/vx/rdmp/sun_73100_0s2 guid: {6d62c284-3e7e-11df-8e71-00144f0f13da} udid: SUN%5FSun%20Storage%207310%5FSUN%5F7x10%5FSeries%5F600144F0FA053DEA00004BB682060002 site: - version: 3.1 iosize: min=512 (bytes) max=2048 (blocks) public: slice=2 offset=65792 len=209482176 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 update: time=1275076440 seqno=0.264 ssb: actual_seqno=0.1 headers: 0 240 configs: count=1 len=48144 logs: count=1 len=7296 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 enabled config priv 000256-048207[047952]: copy=01 offset=000192 enabled log priv 048208-055503[007296]: copy=01 offset=000000 enabled lockrgn priv 055504-055647[000144]: part=00 offset=000000 Multipathing information: numpaths: 4 c2t2100001B32145466d2s2 state=enabled type=primary c2t2100001B32148966d2s2 state=enabled type=secondary c1t2101001B32345466d2s2 state=enabled type=primary c1t2101001B32348966d2s2 state=enabled type=secondary
*** Checked for relevance on 13-Aug-2013 *** References<BUG:15653992> - SUNBT6966496-SOLARIS_11 PATHS REPORTED AS STANDBY ARE ENUMERATED AS ONLINE<BUG:15714961> - SUNBT7043998 FAILBACKS WITH FW 2010.08.17.3.0,1-1.25 CAN TAKE 45 MINUTES OR MORE <BUG:15752346> - SUNBT7107552-SOLARIS_11U1 A FLAG VLUN_KEEP_HELD CONFLICTS WITH ANOTHER TWO FLAGS <BUG:15767902> - SUNBT7132238-AK-2011.04.24 PHYLOCK LIKE PROBLEMS AFTER UPGRADE TO 2011.1.1.0 ON <BUG:15578613> - SUNBT6865431-SOLARIS_11 SCSI_VHCI LOSES PATH STATE AWARENESS UNDER FAILOVER/LOAD <BUG:15614422> - SUNBT6915604-SOLARIS_11 PATH STATE IS NOT UPDATED AFTER FAILOVER SUCCESS <BUG:15642153> - SUNBT6951173 7310 FC TARGET LUN TAKING OVER 10 MINUTES TO COME BACK AFTER TAKEOV <BUG:15648815> - SUNBT6959914-SOLARIS_10U10 ANAGO: FC LUN BECAME INACCESSIBLE TO CLIENT DURING TA Attachments This solution has no attachment |
||||||||||||||||||||||||||||||
|