John,
I'm not aware of the XIV requiring any particular kind of card on the
processor side of the SAN. Just the standard hardware requirements, such
as not mixing LX/SX ports, apply as they do for any storage subsystem.
The SVC is not needed to use the XIV as an EDEVICE, and in fact a switch
FLASHCOPY SYNC is only useful for older (Version 1) FlashCopy hardware.
Modern storage subsystems, such as DS8000, will not change their behavior
with this parameter. From the FLASHCOPY helpfile:
SYNChronous
(For FlashCopy Version 1 hardware) tells CP to process the command
@LISTSERV.UARK.EDU] Im
Auftrag von Eric R Farman
Gesendet: Mittwoch, 4. Mai 2011 17:28
An: IBMVM@LISTSERV.UARK.EDU
Betreff: Re: AW: Problems with SCSI FBA device under z/VM
Have you removed the configuration of the LUN from Linux before you varied
the EDEVice online? z/VM will not be able to open a LUN
Have you removed the configuration of the LUN from Linux before you varied
the EDEVice online? z/VM will not be able to open a LUN R/W if it is
already open on another FCP CHPID/WWPN pair. Doesn't matter if it's a
different subchannel, if it's on the same CHPID.
If that's not it, I would
Steve,
There is a difference between a key LABEL and a key ALIAS. Your console
suggests that the latter is not defined to VM:
set tape 704 rekey EKMCERT030911A
HCPSTA9968E Key alias not found: EKMCERT030911A
The LABEL is what is defined to the key store, and is what shows up in the
output
Tom,
As Rick states, it depends on both software and hardware. From our side,
z/VM's EDEVice support is entirely multipath capable. An EDEVice created
and brought online with a single path can be modified via command to have
multiple paths. Those new paths will immediately be usable for I/O
Hi Ed,
Tape encryption is enabled on z/VM via operands on the ATTACH command. It
can also be enabled by setting up the encryption settings with the SET
RDEVice command, where they would be picked up automatically on the
ATTACH.
Details are available in the appropriate help files, the CP
Hi Mark,
When you say the real LUN number, are you referring to the SVC's MDISK
LUN ID, which is representing the backing storage? If so, I do not
believe any host OS has the ability to see these identifiers, as the SVC
only uses that internally, as part of his MDISK-to-VDISK mapping. This
Hi Dave,
Can't speak to CMS file support, but the existing requirement for
DDR/PIPES is sufficient for us to complete that work.
Regards,
Eric
Eric Farman
z/VM I/O Development
IBM Endicott, NY
From:
David Boyes dbo...@sinenomine.net
To:
IBMVM@LISTSERV.UARK.EDU
Date:
05/04/2010
configured correctly on the switch.
On Thu, Apr 15, 2010 at 9:38 AM, Eric R Farman far...@us.ibm.com wrote:
Hi Daniel,
The WWPN listed in your Q FCP outputs and that from the SCSIDISC tool are
similar enough that I suspect they are different subchannels on the same
FCP card, and not of your
Hi Daniel,
The WWPN listed in your Q FCP outputs and that from the SCSIDISC tool are
similar enough that I suspect they are different subchannels on the same
FCP card, and not of your target DASD subsystem. Are there other WWPNs
listed in the SCSIDISC output beyond what you have sent? If so,
Hi Frank,
A FlashCopy relationship created with the FLASHCOPY ESTABLISH command is
persistent, and will be unaffected by any ATTACH or DETACH commands, or
even VM IPLs. It can only be terminated by a FLASHCOPY WITHDRAW command,
though it doesn't have to be the same user that initiated the
Hi Crispin,
The intent was to prevent CP-owned volumes from being the TARGET of a
FlashCopy relationship, as it means there's another writer of data to
the pack that CP will be using and Bad Things will surely result. If your
pack is a SOURCE in the FlashCopy relationship, then I suspect we
Hi Crispin,
This is fine. When I do RESYNC to update change from SOURCE to TARGET ,
it overwrites label of TARGET volume. This is not what I need. Any
suggestions as to what I am doing wrong ?
You're not doing anything wrong, but RESYNC may indeed not be doing what
you want. If that's the
Hi Crispin,
Take a look at z/VM 5.4 APAR VM64449. It expands the existing Class B
FLASHCopy command to allow privileged users to establish and manage
Persistent Flashcopy relationships. (The existing command creates
point-in-time copies, where the relationships are destroyed as soon as the
Hi Raymond,
I believe the reason you're not getting any TRF files in this scenario is
that the SET EDEVICE command is very analogous to the SET RDEVICE command.
You can define whatever you would like for either command, but VM will
not attempt to do anything with the device created from
Hi Lee,
The biggest EDEV you can have is 1TB minus one page, with some exceptions
depending on the application of the EDEV:
DRCT, PAGE, SPOL allocations must reside in the first 64GB (minus one
page) of the volume
CMS volumes are technically limited to 381GB, but will be less than that
in
Hi Lee,
We're trying to define a bunch of EDEVs and finding things not as we'd
expect...
We have a z10 running NPIV to an XIV (IBM SCSI) box.
Be aware that XIV is not currently supported for attachment to a System z
processor.
...snip...
Anyone else seen anything similar?
I haven't
Hi Dave,
Have you talked to the product owner? There is an open requirement
against DDR that you could be a hero by helping them close it.
Yep, George has been working on this project with that exact requirement
in mind. Considering the recent discussions here on this very topic, we
Hi JR,
I'm a little confused by your description of the experiences you've been
having with PAV, so have interjected my commentary on the matter below in
hopes of understanding it better...
Imler, Steven J wrote on 07/03/2008 09:32:13 PM:
Well ... for me ... it's not an issue of what benefit
and
delete the e-mail from your system.
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Steve Wilkins
Sent: Wednesday, November 21, 2007 3:43 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Questions about LUN DASD volumes
Compliments of Eric R. Farman, a sample of the SCSIDISC
] On
Behalf Of Eric R Farman
Sent: Monday, November 26, 2007 9:06 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Questions about LUN DASD volumes
How large is large? I can't put my hands on one larger than 70GB at the
moment, and it looks fine. Will look for the huge disks tomorrow to try
them
Hi Leland,
So, the Discovery Tool cannot open the WWPN of the Hitachi (it makes sense
that it cannot open the port it is leaving from, so that error is okay).
The error seems to suggest that perhaps the request is being blocked by a
zoning/masking scheme within the Hitachi? That's what it
Hi Don,
What you have looks fine, though I have a few minor points to offer:
- Newer IBM DASD contains an Access Control List that identifies which
HOST WWPNs (associated with the FCP CHPID) can access which LUNs within
the box, so you won't always be able to get to every LUN in the box as
Hi Paul,
When issuing a SET EDEV TYPE
FBA ATTR [paths] command, the value should
be an unused RDEV number that will be created. The FCP RDEV number
(D200) is used later in the command, following the FCP_DEV
operand.
Hope this helps you avoid your maintenance
window.
Regards,
25 matches
Mail list logo
