Presentation is loading. Please wait.

Presentation is loading. Please wait.

CHARON storage options and clustering

Similar presentations


Presentation on theme: "CHARON storage options and clustering"— Presentation transcript:

1 CHARON storage options and clustering
Paris, October 11th – 12th, 2011 Stromasys Product Management

2 Contents Modern storage concepts and layout examples
Storage layers relevant to CHARON configuration Legacy storage technologies and their representation in CHARON Controller emulation, Bypass, and Pass Through modes CHARON virtual disks (tapes, CD/DVD) representation Container files, PhysicalDrives, and direct LUN access Clustering Appendix: AXP console operations with KGPSA in Pass Through mode

3 Modern storage layouts
Alpha Hardware Virtualization April 13, 2017 Modern storage layouts Sources: IBM, VMware 3

4 Modern storage layout example
Alpha Hardware Virtualization April 13, 2017 Modern storage layout example Source: Cisco 4

5 Working with CHARON storage
CHARON is like 2 faced Janos one face looks at the direction of legacy VAX and AXP hardware. Another face looks at the modern storage technologies, supported by modern hosting hardware and OS (Windows, Linux, VMware): SATA, SAS, NAS, iSCSI, SAN.

6 Relevant data travel layers
Alpha Hardware Virtualization April 13, 2017 Relevant data travel layers Actions Layers Supplementary: performance tuning of applications VMS / Tru64 Applications and layered software Opportunity: use VMS Bypass driver VMS / Tru64 Storage Device Drivers Mandatory: configure CHARON storage options CHARON: VAX / AXP Storage Controllers Mandatory: configure CHARON storage mapping CHARON: Interface to hosting OS storage functions Opportunity: choose optimal storage allocation Hosting OS (Windows / Linux / VMware) storage management Supplementary: performance tuning of storage options Storage transport and hardware 6

7 Mandatory: storage controllers
Alpha Hardware Virtualization April 13, 2017 Mandatory: storage controllers Opportunity: use VMS Bypass driver VMS / Tru64 Storage Device Drivers Mandatory: configure CHARON storage options CHARON: VAX / AXP Storage Controllers Supplementary: performance tuning of storage options Storage transport and hardware 7

8 Yes, by emulated networking
Alpha Hardware Virtualization April 13, 2017 VAX/AXP storage technologies Legacy storage technologies CHARON-VAX CHARON-AXP /4100/DS/ES/GS CHARON-AXP /SMA(+)/Station MSCP Emulated RQDX3, KDM70, TKQ50, TUK50 - Bypass in VMS – presented as MSCP DSSI Emulated HSD50 Bypass in VMS – presented as DSSI CI Emulated CIXCD, HSJ50 SCSI Emulated KZDDA Emulated KZPBA Emulated KZPBA; also bypass in VMS RAID Bypass in VMS – presented as RAID IDE Emulated AcerLabs 1543C Bypass in VMS – presented as IDE FDDI Storage Network Storage Yes, by emulated networking Fiber Channel Physical KGPSA, or compatible Emulex in Pass Through mode (Windows platform) Bypass in VMS – presented as FC 8

9 Guest OS storage controller driver
Emulation and Bypass methods Emulation Bypass VMS / Tru64 VMS Guest OS storage controller driver VMS Bypass driver Up to ~25%faster Storage controller Emulation No SCSI/RAID/FC Emulation Windows / Linux Windows

10 PCI Pass Through mode In PCI Pass Through mode CHARON is taking full control on a physical PCI adapter, which is installed in the hosting server. Special CHARON driver should be installed. In this case VMS or Tru64 work with the adapter directly, passing through hosting OS and drivers. Only adapters listed below are supported in Pass Through mode. Currently Pass Through mode is only supported on Windows hosting platform. Emu- lex Ether- net SCSI Host PCI Bus Windows CHARON-AXP OpenVMS / Tru64 Emulex driver Pass-Through

11 Hints Configuration is usually defined based on the original VAX/AXP hardware layout, in order to avoid or minimize a need to intervene in the VMS / Tru64 settings Some user configurations does not provide flexibility in selecting the storage method – only one will fit. Go for it If there is flexibility, Pass Through provides the best performance (for a price of additional HBA controller(s) and relatively complex setup and configuration). Recommended (sometimes a must) for high performance system replacements Bypass is a really nice feature of CHARON-AXP/SMA(+) family (provided that requirements are met: Windows hosting platform, supported VMS version, etc.)

12 Mandatory: host OS interface
Alpha Hardware Virtualization April 13, 2017 Mandatory: host OS interface Supplementary: performance tuning of applications VMS / Tru64 Applications and layered software Mandatory: configure CHARON storage mapping CHARON: Interface to hosting OS storage functions Opportunity: choose optimal storage allocation Hosting OS (Windows / Linux / VMware) storage management Supplementary: performance tuning of storage options Storage transport and hardware 12

13 Direct disk addressing Direct SCSI addressing
Interface to host OS storage Storage reliability and performance is defined mostly by the selected access method Container files Direct disk addressing Direct SCSI addressing FC Pass Through CHARON-VAX Yes Yes 2) - CHARON-AXP SMA(+)/Station Yes 1) Yes 2, 3) CHARON-AXP/xS for Windows CHARON-AXP/xS for Linux 1) Booting not always supported from disks if Bypass is used 2) Windows might change the order of the PhysicalDrives in some circumstances. 3) Cannot be used to access disks together with physical Alpha systems

14 Disk controller emulation: MSCP, SCSI, DSSI, …
Alpha Hardware Virtualization April 13, 2017 Container files set dka[0]=“D\CHARON\system.vdisk” set dka[0]=/opt/charon/disks/system.vdisk” Simple and fast to configure. Host OS takes care of the I/O, so any technology could be used: SATA, SAS, SAN, NAS, (i)SCSI Host OS Charon Storage Array NTFS/ext file system CF. vdisk Disk controller emulation: MSCP, SCSI, DSSI, … Disk Volume iSCSI or FC Adapter iSCSI or FC network Containerfile.vdisk 14

15 Disk controller emulation: MSCP, SCSI, DSSI, …
Alpha Hardware Virtualization April 13, 2017 Directly addressing the disks set dka[0]=“\\.\PhysicalDrive0” set dka[0]=/dev/sd0” Important! Host OS should not access those disk(s) CHARON talks to SCSI subsystem on the host OS. Windows OS Charon Emulation Storage Array Physical Disk: \\.\PhysicalDrive0 Disk controller emulation: MSCP, SCSI, DSSI, … Logical Disk Disk Volume \\.\Physicaldrive1 iSCSI or FC Adapter iSCSI or FC Network 15

16 Disk controller emulation: MSCP, SCSI, DSSI, …
Alpha Hardware Virtualization April 13, 2017 Direct SCSI addressing set dka[0]=\\.\SCSIa:b:c:d Not recommended for disks (designed for generic SCSI devices) CHARON talks to SCSI subsystem on the host OS. Windows OS Charon Emulation Storage Array Physical Disk: \\.\SCSIa:b:c:d Disk controller emulation: MSCP, SCSI, DSSI, … Logical Disk Disk Volume \\.\SCSIe:f:g:h iSCSI or FC Adapter iSCSI or FC Network 16

17 Alpha Hardware Virtualization
April 13, 2017 FC Pass Through Storage configuration for the SAN is done from AXP SRM console in exactly the same way as for physical Alpha system. CHARON talks directly to Emulex HBA Windows OS Charon Emulation Storage Array SAN infrastructure FC driver Pass through Driver Disk Volume Emulex HBA 17

18 Options Every device has following options:
Media_type and disk geometry parameters provide guest OS with hardware ID and geometry. Shared. Allows access from two or more CHARON instances and other systems. Shared disk devices could be used for clustering, if the underlying storage also supports shared access, and the access could be physically provided. Cached. CHARON will enable host OS software chache is this option is on. Must be switched off, if set to Shared. Removable. By default, the tapes, floppies, and CDROMs are removable. On some emulated controllers the disks could be made removable too.

19 Hints Reconsider using advanced software options on VMS and Tru64. For example, VMS shadowing or Tru64 LSM might have been implemented for fault tolerance. With the modern storage redundancy could be built in. Performance boost might be achieved by removing redundancy. Underlying storage should provide sufficient redundancy and performance for VMS / Tru64 to have access to the storage at all times. If a timeout happens, the disk could go offline until VMS/Tru64 reboot. Hence: Avoid RAID5 and other slow RAIDs. Mirroring is recommended. Consider fastest possible options (SAN, FC Pass Through). Modern storage features (snapshots, mirroring) should be carefully considered.

20 Clustering VAX/AXP cluster type CHARON capability Cluster traffic
NI (Ethernet) Mixed clusters Network SCSI (Small Computer System Interface) Emulated SCSI link over the network FDDI (Fiber Distributed Data Interface) FDDI link over the network DSSI (Digital Storage Systems Interconnect) CHARON only clusters Emulated DSSI link over the network CI (Computer Interconnect) Emulated CI link over the network FC (Fiber Channel) MC (Memory Channel) Not available - Mixed clusters indicates that CHARON can be clustered with physical systems with shared disk access

21 Clustering Applications Applications VMS/Tru64 VMS/Tru64 Storage Array
Alpha Hardware Virtualization April 13, 2017 Clustering Applications Applications System Utilities System Libraries System Utilities System Libraries VMS/Tru64 VMS/Tru64 CHARON CHARON SCSI disk controller emulation Adapter Emulation Adapter Emulation SCSI disk controller emulation Host OS Host OS Hardware Hardware iSCSI or FC Adapter Ethernet Adapter Ethernet Adapter iSCSI or FC Adapter Cluster admin Ethernet Storage data SCSI, iSCSI or Fibre Channel connection Storage Array MSA1000, MSA2100, iSCSI or EVA etc. 21

22 SAN benefits Standard in modern environment
Alpha Hardware Virtualization April 13, 2017 SAN benefits Standard in modern environment Deploy and scale quickly and easily Simplify management Use latest storage technologies Easy migration for existing data on SAN No local storage / backup needed, centralize it Reduce footprint of servers Ideal when using blade servers

23 Fibre Channel PCI Pass Thruogh
Appendix Fibre Channel PCI Pass Thruogh Avalable since CHARON-AXP/xS

24 Hardware support - Emulex
LP8000 LP9000 LP9002 LP9802 LP10000 LP10000DC LP10000-S LPX1000 LP11002 LPe11002 LPe11

25 Installation Install FC HBA & CHARON-AXP
Map the driver to the HBA, located at: ..\CHARON\Drivers\EMULEX_ \

26 Configure CHARON load KGPSA FGA host_bus_location="PCI Slot 5
(PCI bus 6, device 2, function 0)" load KGPSA PGA host_bus_location="PCI Slot 3 (PCI bus 4, device 0, function 0)" load KGPSA PGB host_bus_location="PCI Slot 3 (PCI bus 4, device 0, function 1)"

27 HSG80 HSG80_1L > sho this full HSG80_1L > sho other full
Controller: HSG80 ZG Software V88F-2, Hardware E12 NODE_ID = FE1-000B-6BF0 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 Configured for MULTIBUS_FAILOVER with ZG In dual-redundant configuration Device Port SCSI address 6 Time: 27-OCT :35:00 Command Console LUN is lun 0 (IDENTIFIER = 98) Host Connection Table is NOT locked Smart Error Eject Disabled Host PORT_1: Reported PORT_ID = FE1-000B-6BF1 PORT_1_TOPOLOGY = FABRIC (fabric up) Address = Host PORT_2: Reported PORT_ID = FE1-000B-6BF2 PORT_2_TOPOLOGY = FABRIC (fabric up) Address = NOREMOTE_COPY HSG80_1L > sho other full Controller: HSG80 ZG Software V88F-2, Hardware E09 NODE_ID = FE1-000B-6BF0 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 Configured for MULTIBUS_FAILOVER with ZG In dual-redundant configuration Device Port SCSI address 7 Time: 27-OCT :35:11 Command Console LUN is lun 0 (IDENTIFIER = 98) Host Connection Table is NOT locked Smart Error Eject Disabled Host PORT_1: Reported PORT_ID = FE1-000B-6BF3 PORT_1_TOPOLOGY = FABRIC (fabric up) Address = Host PORT_2: Reported PORT_ID = FE1-000B-6BF4 PORT_2_TOPOLOGY = FABRIC (fabric up) Address = NOREMOTE_COPY

28 CHARON SRM FCMGR fcmgr rescan show set clear fcmgr show adapters
ports devices fcmgr set boot dump

29 FCMGR P00>>>fc sho adapter
pga PGA WWN C F P00>>>fc sho port [0] WWN fe1-000b-6bf1 (N0) via adapter pga [1] WWN fe1-000b-6bf4 (N1)

30 FCMGR P00>>>fc sho port run init first run fcmgr rescan first

31 FCMGR P00>>>fc sho device
UDID:110 WWID: :6000-1fe1-000b-6bf (ev:none) via adapter via fc_port con [0] pga fe1-000b-6bf1 yes (ev:none) [1] pga fe1-000b-6bf4 yes (ev:none) UDID:108 WWID: :6000-1fe1-000b-6bf (ev:none) [12] pga fe1-000b-6bf1 yes (ev:none) [13] pga fe1-000b-6bf4 yes (ev:none)

32 FCMGR P00>>>fc rescan
polling for units on kgpsa0, slot 5, bus 0, hose 1 ... pga PGA WWN C F fabric WWN directory WWN 20fc port WWN fe1-000b-6bf1 lun e DEC HSG V86F …… lun c DEC HSG V86F UDID: WWID: :6000-1fe1-000b-6bf UDID: WWID: :6000-1fe1-000b-6bf lun port WWN fe1-000b-6bf4 ……. lun d DEC HSG V86F

33 FCMGR (pre-boot) P00>>>fc set boot udid 108
P00>>>sho dev sys SYS System ROOT Device pka PKA Q-Logic/ISP PCI SCSI HBA ewa EWA F-E8-65 pkb PKB Q-Logic/ISP PCI SCSI HBA pqa PQA ALi 1553C Integrated IDE Controller pqb PQB ALi 1553C Integrated IDE Controller pga PGA WWN C F dqa DQA Virtual ATAPI - TEAC DW-224E-V dka DKA DEC RZ (C)DEC dka DKA COMPAQ RZ1ED-LS dka DKA DEC RZ1DA (C)DEC dka DKA DEC RZ (C)DEC dka DKA DEC RZ (C)DEC dga $1$DGA DEC HSG V86F  dga $1$DGA DEC HSG V86F 

34 Booting P00>>>b $1$dga108 (boot dga108.1001.0.5.1 -flags 0,1)
jumping to bootstrap code

35 VMS CLMB01::SYSTEM>sh dev /multi Device Device Error Current
Name Status Count Paths path $1$DGA100: (CLMB01) Online / 3 PGA FE1-000B-6BF4 $1$DGA108: (CLMB01) Online / 3 PGA FE1-000B-6BF4  $1$DGA110: (CLMB01) Online / 3 PGA FE1-000B-6BF1 $1$DGA199: (CLMB01) Online / 3 PGA FE1-000B-6BF4 $1$DGA200: (CLMB01) Online / 3 PGA FE1-000B-6BF1 $1$DGA208: (CLMB01) Online / 3 PGA FE1-000B-6BF4 $1$DGA300: (CLMB01) Online / 3 PGA FE1-000B-6BF1 $1$DGA400: (CLMB01) Online / 3 PGA FE1-000B-6BF1 $1$DGA500: (CLMB01) Online / 3 PGA FE1-000B-6BF4 $1$GGA98: Online / 2 PGA FE1-000B-6BF1

36 VMS CLMB01::SYSTEM>sho dev/full $1$DGA100:
Disk $1$DGA100: (CLMB01), device type HSG80, is online, file-oriented device, shareable, device has multiple I/O paths, served to cluster via MSCP Server, error logging is enabled. Error count Operations completed Owner process "" Owner UIC [SYSTEM] Owner process ID Dev Prot S:RWPL,O:RWPL,G:R,W Reference count Default buffer size Current preferred CPU Id Fastpath WWID :6000-1FE1-000B-6BF Host name "CLMB01" Host type, avail AlphaServer GS80, yes Alternate host name "CLMB02" Alt. type, avail AlphaServer GS80, yes Allocation class I/O paths to device Path PGA FE1-000B-6BF1 (CLMB01), primary path. Error count Operations completed Path PGA FE1-000B-6BF4 (CLMB01), current path. Path MSCP (CLMB02). Error count Operations completed

37 VMS …. Volume label "DISK100" Relative volume number 0
Cluster size Transaction count Free blocks Maximum files allowed Extend quantity Mount count Mount status Process Cache name "_$1$DKA0:XQPCACHE" Extent cache size Maximum blocks in extent cache File ID cache size Blocks in extent cache Quota cache size Maximum buffers in FCP cache Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

38 Tru64 # scu show edt CAM Equipment Device Table (EDT) Information:
Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W Direct SCSI-2 Virtual SCSI Disk (C)SRI W CD-ROM SCSI-2 TEAC DW-224E-V CA W Sequential SCSI-2 DEC TZ (C) DEC CD50 N RAID SCSI-2 DEC HSG80CCL V88F W Direct SCSI-2 DEC HSG V88F W Direct SCSI-2 DEC HSG V88F W  RAID SCSI-2 DEC HSG80CCL V88F W Direct SCSI-2 DEC HSG V88F W Direct SCSI-2 DEC HSG V88F W Direct SCSI-2 DEC HSG V88F W Direct SCSI-2 DEC HSG V88F W CD-ROM SCSI-3 TEAC DW-224E-V CA N

39 Tru64 # hwmr gr =n -view device HWID: Device Name Mfg Model Location
8: /dev/dmapi/dmapi 9: /dev/scp_scsi 10: /dev/kevm 86: /dev/disk/dsk0c Virtual SCSI Disk (C)SRI bus-0-targ-1-lun-0 96: /dev/ntape/tape0 DEC TZ (C) DEC bus-0-targ-6-lun-0 97: /dev/cport/scp HSG80CCL bus-2-targ-0-lun-0 98: /dev/disk/dsk4c DEC HSG IDENTIFIER=110 99: /dev/disk/dsk5c DEC HSG IDENTIFIER=100 100: /dev/disk/dsk6c DEC HSG IDENTIFIER=200 101: /dev/disk/dsk7c DEC HSG IDENTIFIER=300 102: /dev/disk/dsk8c DEC HSG IDENTIFIER=400 103: /dev/disk/dsk9c DEC HSG IDENTIFIER=108 104: /dev/disk/dsk10c DEC HSG IDENTIFIER=208 105: /dev/disk/dsk11c DEC HSG IDENTIFIER=500 106: /dev/disk/dsk12c DEC HSG IDENTIFIER=199 

40 Tru64 (Multipath) # hwmgr -show scsi
SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH 86: gs160tru64 disk none dsk0 [0/1/0] 92: gs160tru64 cdrom none cdrom0 [0/5/0] 97: gs160tru64 raid none scp0 [2/0/0] 98: gs160tru64 disk none dsk4 [2/0/110] 99: gs160tru64 disk none dsk5 [2/0/1] 106: gs160tru64 disk none dsk12 [2/0/199]  112: gs160tru64 tape none tape1 [0/6/0]

41 Multipath SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH 106: gs160tru64 disk none dsk12 [2/0/199] WWID: :6000-1fe1-000b-6bf BUS TARGET LUN PATH STATE valid valid stale stale

42 Tru64 # mkfdmn /dev/disk/dsk12c test_dmn # mkfset test_dmn test
# mount -t advfs test_dmn3 #test /test


Download ppt "CHARON storage options and clustering"

Similar presentations


Ads by Google