系統(tǒng)類老農(nóng)存儲(chǔ)講課sdddsm and hpux sdd

1、DS4000 support -Windows SDDDSM and HPUX SDDStanley Wu 07/11/200882AgendaSDDDSM reviewHPUX SDD reviewDS4000 characteristicSDDDSM specifics for DS4000 HPUX SDD specifics for DS4000HPUX V3Q/A07/11/200883SDDDSM Review07/11/200884SDDDSM supportOS Support:Windows Server 2003 and 200832 bit and x64 No IA64

2、 supportNo web edition supportESS, DS8000, DS6000, SVC, DS4000Cannot co-exist with SDDCannot co-exist with other MPIO driver who claims the same device typeHBA/Driver support: Qlogic, Emulex, Storport miniport driver (storport hotfix required, see readme for detail) 07/11/200885 MPIO/SDDDSM Architec

3、ture Fibre Channel Adapter(HBA)IO Manager / PnP ManagerDisk Class DriverMPIO DriverScsiport/Storport HBA driverStorage SubsystemSDDDSM Driver07/11/200886MPIO/SDDDSM Architecture (Cont.)MPIO framework contains 3 kernel drivers: Multipath bus driver (mpio.sys) Multipath port filter driver (mpspfltr.sy

4、s) Multipath disk driver replacement (mpdev.sys)Note: For W2K8 framework is installed by default, SDDDSM enable it during installation. For W2K3, framework is shipped, installed and enabled by SDDDSM.07/11/200887MPIO/SDDDSM Architecture (Cont.)SDDDSM (sdddsm.sys) is a device specific module, by comm

5、unicating with MPIO through specially designed interface, is responsible for device recognition for multipath device multipath device configuration initialization path selection error handling for multipath-IO accesscontroller failover handling command handling for cluster support 07/11/200888SDDDSM

6、 FunctionalityPath selection policies:Single path policyRound robin policy /w prefered controllerLoad balancy policy /w prefered controllerFailover only policyPath recovery & Error handlingFast recoveryAuto failover/failbackPath probing / reclamation. by MPIO07/11/200889SDDDSM Functionality (Cont.)C

7、luster support (MSCS only)Default SCSI-3 reserve (persistent reserve)can be changed by registry to use scsi-2 but not mendedDynamic path adding/removalSAN Boot07/11/2008810SDDDSM Functionality (Cont.)Trace collectionFirst time data captureMulti-level trace optionsPersistent trace options Run-time tr

8、ace options change 07/11/2008811Path state Datapath can only see states Open, Dead and Closed, these are stable states.All other states are transient, used for path configuration and internal data structure maintenance.Open: when a path in operational stateDead: when a path has more than 3 consecuti

9、ve hard errors or set by running datapath set device path offlineClosed: when a path is removed from system07/11/2008812Path Probing / Reclamation sddsrv is no longer used for path probing / reclamationMPIO periodically calls a SDDDSM provided routine to verify the path state. When this routine is c

10、alled, depending on the return status, SDDDSM set an Open path to Dead, or set a Dead path to Open.By default, this period is 60 seconds, its customizable. 07/11/2008813SDDDSM Trace Data Collection SDDDSM log: %Windir%system32sdd.log%windir%system32sdd_bak.logSDD service log:%windir%system32sddsrv.l

11、og%windir%system32sddsrv.log07/11/2008814Data Collection for Problem Determination SDDDSM trace dataDatapath outputSystem event log / Application event logThe latest trace data collected by pathtestApplication log if possibleCluster log when MSCS installed %windir%clustercluster.logMemory dump when

12、BSOD%windir%memory.dmpRegistryEgather07/11/2008815First Time Data CaptureSDDGETDATA.BATGenerates sddgetdata_%host%_%date%_%time%.cabSDDSDDSrv logsDatapath outputEvent LogsCluster logSDD specific registry entryHBA information07/11/2008816HPUX SDD Review07/11/2008817Supported HP/UX OS levels11.11 PA_R

13、ISC, 32 or 64 bit11.23 IA6411.23 PA-RISC 64 bit07/11/2008818Architecture Layer 07/11/2008819SDD CharacteristicsDLKM, Dynamic Load Kernel Module, no kernel rebuild required SDD automatically load during system startupSDDSRV startup via /etc/inittabConversion from/to PVLINKs, vgextend, vgreduceMost of

14、 LVM commands work directly with vpath devices.Non-disruptive install with concurrent I/OMC/Service Guard07/11/2008820DLKM driverKernel Modules loads/unloads without rebuilding and rebootingReconfigure without system downtimeLoad after kernel is loaded 07/11/2008821SDD device discovery and configura

15、tioncfgvpath:Invoked during installation and bootConfigure or dynamic reconfigure devices with the current ioscan outputExclude boot device /etc/vpathexcl.cfg during installIssues SCSI Inquiry, bundle the devices with the same LUN serial number into a vpathDetermine the Active/Passive controller aff

16、inity and preferred path settingsPersistent binding via /etc/vpathsave.cfgSave the current configuration in /etc/vpath.cfgManual exclude device /etc/vpathmanualexcl.cfg07/11/2008822SDD PVLINK conversionPerform hd2vp conversion after SDD installationCheck and perform hd2vp conversion if needed at sys

17、tem startup.Bypass vp2hd conversion during system shutdown 07/11/2008823Working with LVM commandspvcreate, pvchange, vgcreate vgextend, vgreduces work directly with SDD devicePV timeout change via vpath is replicated through all underlying paths LV timeout = (PV timeout)*(# of paths)vgimport command

18、 only imports scsi devicesNote: some HP native command interface with h/w path only 07/11/2008824Non-disruptive Install for v2Allow the application I/O running while upgrading SDD:vp2hd conversion Unload driverRemove SDD packageInstall SDD packageReload driverhd2vp conversionNote: resource concern 0

19、7/11/2008825MC/Service GuardMC/Service Guard is an application, the cluster nodes are transparent to SDDVolume access is controlled by LVM and MC configurationSDD vpcluster tool Scan the cluster configuration file and extract cluster VG configuration, vgexport from primary nodevgimport the cluster V

20、G in adoptive nodesPerform hd2vp conversion in adoptive nodes 07/11/2008826DS4000 Characteristic Host view07/11/2008827DS4000 ConfigurationRedundant I/O path through controller A and B. Each controller has one or more portsStorage partition is a group of LUNs access by the same host or host groupThe

21、 controller can be set to AVT or non-AVT mode but can operate in one mode per Storage partitionActive/Active Asymmetric or Active/Passive 07/11/2008828LUN and Controller relationship Preferred set during the LUN creation and can be changed through SM interfaceOwnership The controller which was last

22、activated or has the last successful I/OOwnership changes can take a few seconds Frequent ownership changes has performance impactPreferred setting does not change when ownership changes07/11/2008829AVT and non-AVT mode AVT Both controller are active. I/O requests can be driven to either controllerT

23、he ownership changes to the controller who receives the last I/O which causes controller failoverFailover is per LUNnon-AVT Only one controller is activeOwnership change require host issue Mode Select command to activate the controller before the I/O request Mode Select can activate one LUN or a gro

24、up of LUNsI/O fails to the standby controller if it has not been activatedIn multi host environment, failover from one host forces failover over from another hostFailover can be per LUN or per group of LUNsFailback is not automaticRDAC mode = non-AVT mode.07/11/2008830Service mode vs. Offline mode A

25、 controller can be placed in offline mode or service mode through SM Offline mode All I/O requests will fail as if the controller has failedService mode - allow the controller to respond to some I/O requests for host diagnostic purpose. Normal read/write I/O will fail but certain SCSI commands will

26、be successfulConcurrent firmware upgrade 07/11/2008831AVT Storm/Ping-Pong Phenomenon Host I/O requests have been bouncing around or round robin between two controllersIn a single host environment where the multi-path driver is unaware of the preferred controller settingsIn a multi host environment w

27、here the ownership is out of sync among hosts. This can caused by “false controller failure”“false controller failure” means a path failure being recovered as controller failoverRedundant paths to each controller is mended 07/11/2008832AVT Storm, a real case07/11/2008833How many paths from HP#1 to c

28、ontroller-A ?How many paths from HP#2 to controller-A ?HP#1HP#2sw-2ABsw-107/11/2008834How many paths from HP#1 to controller-A ?How many paths from HP#2 to controller-A ?HP#1HP#2sw-2ABsw-107/11/2008835What happens when the same path broke ?HP#1HP#2sw-2ABsw-107/11/2008836What happens when the path to

29、 controller-A broke ?HP#1HP#2sw-2ABsw-107/11/2008837SDDDSM support for DS400007/11/2008838SDDDSM support for DS4000Version 2.3.0.0-2Support both AVT and non-AVT modeLoad Balance on active pathsAuto Controller Failback in AVT modeManual Controller Failback via Storage Manager in non-AVT modeCan not co-exist with LSIDSMNo MSCS support07/11/2008839HPUX SDD support for DS400007/11/2008840SDD DS4000 Support Version 1.7.0.3 for v1 and v2Install DS4000 enablement depotSupport AVT mode onlyAuto Controller failbackLoad Balance on active paths sddsrv probing thread uses SCSI Inquiry page C9 Not