Hi Susan,
> With CUIR, CP tells the control unit it may not take the last path
offline.
> What happens when CUIR is disabled? What happens if it is enabled, but
> z/VM does not support it? Does the CE have to intervene to prevent the
> last path from being taken offline?
If CUIR is disabled, th
--snip--
CUIR and multipath are different. With CUIR, CP tells the control unit
that it *may not* take the last chpid (path) offline. (That's the whole
point of "concurrent upgrade".) It *avoids* a connectivity outage.
Multipath FC connections allow you to *detect* a connectivity outage and
to t
On Thursday, 01/24/2008 at 02:22 EST, Susan Zimmerman
<[EMAIL PROTECTED]> wrote:
> IBM followed up with the following:
>
> "I have been reviewing your query with defect support level2 and am not
> sure how your setup is but if you have multipath EDEVs configured, that
> should be able to handle the
Hi Listers,
IBM followed up with the following:
"I have been reviewing your query with defect support level2 and am not
sure how your setup is but if you have multipath EDEVs configured, that
should be able to handle the error condition in question without being
taken offline. The system will dis
Hi Susan...
> Whichever way the path is
> taken offline, if I lose access to the device because a path is taken
> offline (either with CUIR or manual), I have a problem. I think I'll go
> force a path off to my EDEVs and see if it recovers.
I agree with you that the multipathing of the EDEVs is
On Thursday, 01/24/2008 at 08:26 EST, Susan Zimmerman
<[EMAIL PROTECTED]> wrote:
> I agree with your [Pieter's] statement that z/VM EDEVs should handle a
failing
> path...providing they are defined with multiple pathssince as you so
> eloquently put it "that is the whole point of multipath".
--snip--
In my opinion that should *not* be that.
=20
CUIR only makes the live of the device ERP's easier by quiescing instead =
of failing a path. But FCP multipathing native with Linux multipath or =
with z/VM EDEV should be able (when set up correctly) to live with =
pathes going down. That is t
On Wednesday, 01/23/2008 at 04:40 EST, Eric R Farman/Endicott/[EMAIL PROTECTED]
wrote:
> You're right, Pieter. The multipathing support in both Linux and z/VM
> (EDEV) should allow each host to react to errors and outages that occur
on
> particular paths during CUIR-like events, but I think CUIR i
> So a path could be taken offline during maintentance for SCSI volumes
and
> the hosts should recover, but from the DASD point of view it's gonna
be
> done in a more brute-force method than is available for CKD.
Could the upgrade process simulate CUIR by generating a permanent I/O
error on a path
r CKD.
Regards,
Eric
Eric Farman
z/VM I/O Development
IBM Endicott, NY
Pieter Harder <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
01/23/2008 03:22 PM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: CUIR and SLES 9
> "We do not su
> "We do not support CUIR on SCSI. CUIR only affects CKD volumes.
> The HW will not give us any quiesce/resume requests for SCSI volumes
> regardless of whether we have a single or multiple path(s) to the LUN. "
> I guess that's that. Thanks to everyone for your input on this.
Hi Susan,
In my o
Hi Listers,
My original posting:
--snip--
We had an issue over the weekend when the microcode was upgraded on all our
DS8000s . According to the CE, about 5 hours after the microcode was
installed, the two PCHIDs connected to our SCSI DS8000 started posting
error messages every 6 seconds.
I l
--snip--
Hi Susan,
=20
I don't remember you told us what VM level you are on. If it is z/VM 520 =
your problem suspiciously looks like VM64072. That one clobbers your =
chpids. VM63985 could be even worse.
--snip--
Hi Pieter,
sorry...should have mentioned it... we're at 5.3. VM64072 does sound
Hi Susan,
I don't remember you told us what VM level you are on. If it is z/VM 520 your
problem suspiciously looks like VM64072. That one clobbers your chpids. VM63985
could be even worse.
Best regards,
Pieter Harder
[EMAIL PROTECTED]
tel +31-73-6837133 / +31-6-47272537
>>> Susan Zi
>We run FCP Linux on DS8000 for several years now and have had several =
>code updates.
>FWIW
>a) we never had a planned outage to do code updates (running multipath =
>on Linux)
>b) I don't remember any problems with concurrent updates
>All our Linux FCP are native, so no EDEV. All SLES9 SP3 for
--snip--
We run FCP Linux on DS8000 for several years now and have had several =
code updates.
FWIW
a) we never had a planned outage to do code updates (running multipath =
on Linux)
b) I don't remember any problems with concurrent updates
All our Linux FCP are native, so no EDEV. All SLES9 SP3 f
Hi listers...
--snip--
CUIR claims it supports z/VM... (not a word about zLinux)... but I must
admit... not sure that this isn't a CKD vs FBA issue. z/VM and zLinux
guests also reside on the other DS8000s (that happen to be formatted as CKD
and that had their microcode updated as well) and conti
--snip--
Susan,
I haven't heard of it before, but that doesn't mean anything. What =
version of SLES are you running on those guests? Have you opened a =
support request on this? I'm checking with out developers to see if they =
might have some ideas.
Mark Post
--snip--
Hi Mark...
We're sti
Susan Zimmerman wrote:
Hi Listers,
We had an issue over the weekend when the microcode was upgraded on all our
DS8000s . According to the CE, about 5 hours after the microcode was
installed, the two PCHIDs connected to our SCSI DS8000 started posting
error messages every 6 seconds.
I logged
>>> On Fri, Jan 18, 2008 at 4:04 PM, in message
<[EMAIL PROTECTED]>,
Susan Zimmerman <[EMAIL PROTECTED]> wrote:
-snip-
> Has anyone experienced this problem before? I've instructed the CE to make
> sure the DEVL and TEST z/VM systems are down when he does any microcode
> updates to this DS8000 i
We run FCP Linux on DS8000 for several years now and have had several code
updates.
FWIW
a) we never had a planned outage to do code updates (running multipath on Linux)
b) I don't remember any problems with concurrent updates
All our Linux FCP are native, so no EDEV. All SLES9 SP3 for the last y
Hi Listers,
We had an issue over the weekend when the microcode was upgraded on all our
DS8000s . According to the CE, about 5 hours after the microcode was
installed, the two PCHIDs connected to our SCSI DS8000 started posting
error messages every 6 seconds.
I logged on to one of our test sys
22 matches
Mail list logo
