Re: FCP device
Oh, and if this is a reference to running 2nd level with SCSI, then you simply ATTACH/DEDICATE the FCP subchannels from the 1st level system to your 2nd level guest. They can be attached with virtual addresses that match your configuration at home, but your 2nd level system and its guests still must be configured to work with the DR storage configuration. Regards, Alan Alan Altmark Senior Managing z/VM Consultant IBM Technology Services 1 607 321 7556 (Mobile) alan_altm...@us.ibm.com > -Original Message- > From: Linux on 390 Port On Behalf Of Peter > Sent: Tuesday, June 28, 2022 5:04 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [EXTERNAL] [LINUX-390] FCP device > > Hello > > Good morning > > How do we create WWPN or FBA device in DR site ? > > As this is the first time we are planning to replicate Linux guest to DR site. > > Is there a way to assign or attach a FBA device to the Linux guest ? > > Peter -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: FCP device
The term "FBA" is ambiguous in this context. Are you using z/VM FBA EDEVICEs or are you giving Linux guests direct access to SCSI LUNs? I know this sounds trite, but you do it in DR the same way you do it at home. To connect to a SCSI device, there are 4 elements: 1. The initiator (client) WWPN assigned to a specific FCP subchannel on the Z/LinuxONE box 2. The target (server) WWPNs assigned to the storage controller 3. The LUN within the storage controller 4. The permissions within the SAN fabric that allows the initiator WWPNs to talk to the target WWPNs. So at home your z/VM and/or Linux configurations include the target WWPNs and LUNs. The storage controller configuration gives one or more initiator WWPNs access to one or more LUNs. And of course the SAN fabric is configured to allow the WWPN pairs to talk to each other. All of that must be done in DR where the equipment is different and so are the WWPNs and, possibly, LUN numbers. On top of that you have the mechanism that copies the application data from home to DR and back. How you handle the differences between home and DR depend on whether you maintain a separate system for each site with its own configuration or whether you use a single system (or set of systems) that adapt themselves to their location when they IPL based on environmental information that can tell it whether it is in DR or at home. Regards, Alan Alan Altmark Senior Managing z/VM Consultant IBM Technology Services 1 607 321 7556 (Mobile) alan_altm...@us.ibm.com > -Original Message- > From: Linux on 390 Port On Behalf Of Peter > Sent: Tuesday, June 28, 2022 5:04 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [EXTERNAL] [LINUX-390] FCP device > > Hello > > Good morning > > How do we create WWPN or FBA device in DR site ? > > As this is the first time we are planning to replicate Linux guest to DR site. > > Is there a way to assign or attach a FBA device to the Linux guest ? > > Peter > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email to > lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > INVALID URI REMOVED > 3A__www2.marist.edu_htbin_wlvindex-3FLINUX- > 2D390&d=DwIBaQ&c=jf_iaSHvJObTbx- > siA1ZOg&r=XX3LPhXj6Fv4hkzdpbonTd1gcy88ea- > vqLQGEWWoD4M&m=D7M27xBYK0kyVF6ngfV1WiIGu_PJ9Z_KoI0R7oMo954 > k1nBVU2orBFoqyC6G-BZv&s=8-u-w3BBig5CkivElIL3wR7AY4Im8kHBBri- > iCPhvEM&e= -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: FCP device
Hi Peter, On 6/28/22 11:03, Peter wrote: How do we create WWPN or FBA device in DR site ? As this is the first time we are planning to replicate Linux guest to DR site. Is there a way to assign or attach a FBA device to the Linux guest ? What's replicated in the DR site? IBM Z CPC, storage (using e.g. PPRC), or both? Which WWPN: initiator of the host, or target of the storage? The host initiator WWPNs are managed by the machine and can e.g. be exported on the SE (example for non-DPM machine): https://public.dhe.ibm.com/software/dw/linux390/lvc/zFCP_Best_Practices-BB-Webcast_201805.pdf#page=40 I suppose you use z/VM EDEV to represent multiple paths to an FCP-attached volume as emulated FBA DASD to a guest as opposed to dedicated FCP devices? If so, I think you would just use a different set of FCP devices on the DR CPC to assemble the EDEV device and dedicate that resulting FBA DASD to the "replicated" guest for use on cold failover, i.e. on IPL of the guest on the DR CPC. -- Mit freundlichen Gruessen / Kind regards Steffen Maier Linux on IBM Z and LinuxONE https://www.ibm.com/privacy/us/en/ IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Gregor Pillen Geschaeftsfuehrung: David Faller Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
FCP device
Hello Good morning How do we create WWPN or FBA device in DR site ? As this is the first time we are planning to replicate Linux guest to DR site. Is there a way to assign or attach a FBA device to the Linux guest ? Peter -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: EVMS question for FCP device
Thank you, that worked. I saw that reply earlier but when I searched the logs I couldn't find it. This would also suggest that this is fixed with SP1 then. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Robert J Brenneman Sent: Thursday, January 27, 2005 3:25 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: EVMS question for FCP device Try mounting /dev/evms/md/md0 with the barrier option turned off. for reiser like this: mount /dev/evms/md/md0 / -o barrier=none for ext3 like this: mount /dev/evms/md/md0 / -o barrier=0 Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] "Wiggins, Mark" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 27/01/2005 13:40 Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject EVMS question for FCP device I've been trying to get a multipath FCP device attach to my SLES9 instance on z/VM 5.1. I feel as though I've followed the directions (Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up getting either a "broken pipe" error when trying to mount it from EVMSGUI and I get "wrong fs type, bad option, bad superblock on /dev/evms/md/md0, or too many mounted file systems" when I try to mount it on linux. Quickly, let me go through the steps and see if anyone can see where I've went wrong. ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP). ATT A310 to LINUX1 in VM >From YAST, HARDWARE, ZFCP, ADD 0.0.a210WWPN1LUN 502f 0.0.a310WWPN2LUN 502f The WWPN's are different but the LUN's are the same. These are defined correctly, because I've been able to use each path individual, just not as multipath. Then from EVMSGUI - add DOS segment manager to a210 - select freespace object and create segment for a210 - create region MD Multipath Region Manager and select a210 and a310 - I skip the RAID0 part because I've only got 1 LUN - create compatability volume - Make filesystem (ReiserFS) - Of course I've "saved" after each step as directed - chkconfig evms.boot on Actually, it will mount if I use EXT3 instead of ReiserFS, but I can only get it to mount "read-only". With ReiserFS it won't mount at all. In my searching I did notice suggestions of applying BD-Claim Patch, which sounds like it might resolve my problem. In addition to that, is this possibly fixed with SP1? I noticed a section in there stating "* Added patches for OES to EVMS.", just wondering if that would help. Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: EVMS question for FCP device
Try mounting /dev/evms/md/md0 with the barrier option turned off. for reiser like this: mount /dev/evms/md/md0 / -o barrier=none for ext3 like this: mount /dev/evms/md/md0 / -o barrier=0 Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] "Wiggins, Mark" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 27/01/2005 13:40 Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject EVMS question for FCP device I've been trying to get a multipath FCP device attach to my SLES9 instance on z/VM 5.1. I feel as though I've followed the directions (Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up getting either a "broken pipe" error when trying to mount it from EVMSGUI and I get "wrong fs type, bad option, bad superblock on /dev/evms/md/md0, or too many mounted file systems" when I try to mount it on linux. Quickly, let me go through the steps and see if anyone can see where I've went wrong. ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP). ATT A310 to LINUX1 in VM >From YAST, HARDWARE, ZFCP, ADD 0.0.a210WWPN1LUN 502f 0.0.a310WWPN2LUN 502f The WWPN's are different but the LUN's are the same. These are defined correctly, because I've been able to use each path individual, just not as multipath. Then from EVMSGUI - add DOS segment manager to a210 - select freespace object and create segment for a210 - create region MD Multipath Region Manager and select a210 and a310 - I skip the RAID0 part because I've only got 1 LUN - create compatability volume - Make filesystem (ReiserFS) - Of course I've "saved" after each step as directed - chkconfig evms.boot on Actually, it will mount if I use EXT3 instead of ReiserFS, but I can only get it to mount "read-only". With ReiserFS it won't mount at all. In my searching I did notice suggestions of applying BD-Claim Patch, which sounds like it might resolve my problem. In addition to that, is this possibly fixed with SP1? I noticed a section in there stating "* Added patches for OES to EVMS.", just wondering if that would help. Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: EVMS question for FCP device
This probably won't make you feel much better, but I messed with exactly the same thing off and on for about a week, and finally gave up. I saw identical symptoms. I'm hoping SP1 fixes it, too. If it doesn't, I'll have to dig deeper. Scott Ledbetter StorageTek -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wiggins, Mark Sent: Thursday, January 27, 2005 11:40 AM To: LINUX-390@VM.MARIST.EDU Subject: EVMS question for FCP device I've been trying to get a multipath FCP device attach to my SLES9 instance on z/VM 5.1. I feel as though I've followed the directions (Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up getting either a "broken pipe" error when trying to mount it from EVMSGUI and I get "wrong fs type, bad option, bad superblock on /dev/evms/md/md0, or too many mounted file systems" when I try to mount it on linux. Quickly, let me go through the steps and see if anyone can see where I've went wrong. ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP). ATT A310 to LINUX1 in VM >From YAST, HARDWARE, ZFCP, ADD 0.0.a210WWPN1LUN 502f 0.0.a310WWPN2LUN 502f The WWPN's are different but the LUN's are the same. These are defined correctly, because I've been able to use each path individual, just not as multipath. Then from EVMSGUI - add DOS segment manager to a210 - select freespace object and create segment for a210 - create region MD Multipath Region Manager and select a210 and a310 - I skip the RAID0 part because I've only got 1 LUN - create compatability volume - Make filesystem (ReiserFS) - Of course I've "saved" after each step as directed - chkconfig evms.boot on Actually, it will mount if I use EXT3 instead of ReiserFS, but I can only get it to mount "read-only". With ReiserFS it won't mount at all. In my searching I did notice suggestions of applying BD-Claim Patch, which sounds like it might resolve my problem. In addition to that, is this possibly fixed with SP1? I noticed a section in there stating "* Added patches for OES to EVMS.", just wondering if that would help. Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
EVMS question for FCP device
I've been trying to get a multipath FCP device attach to my SLES9 instance on z/VM 5.1. I feel as though I've followed the directions (Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up getting either a "broken pipe" error when trying to mount it from EVMSGUI and I get "wrong fs type, bad option, bad superblock on /dev/evms/md/md0, or too many mounted file systems" when I try to mount it on linux. Quickly, let me go through the steps and see if anyone can see where I've went wrong. ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP). ATT A310 to LINUX1 in VM >From YAST, HARDWARE, ZFCP, ADD 0.0.a210WWPN1LUN 502f 0.0.a310WWPN2LUN 502f The WWPN's are different but the LUN's are the same. These are defined correctly, because I've been able to use each path individual, just not as multipath. Then from EVMSGUI - add DOS segment manager to a210 - select freespace object and create segment for a210 - create region MD Multipath Region Manager and select a210 and a310 - I skip the RAID0 part because I've only got 1 LUN - create compatability volume - Make filesystem (ReiserFS) - Of course I've "saved" after each step as directed - chkconfig evms.boot on Actually, it will mount if I use EXT3 instead of ReiserFS, but I can only get it to mount "read-only". With ReiserFS it won't mount at all. In my searching I did notice suggestions of applying BD-Claim Patch, which sounds like it might resolve my problem. In addition to that, is this possibly fixed with SP1? I noticed a section in there stating "* Added patches for OES to EVMS.", just wondering if that would help. Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
